Support
Are you an Otonet customer and would you like to be assisted by our support service? Please connect it. A technician will review your message and contact you to identify your needs and provide you with all the necessary help for the proper functioning of our products.
FAQ
Does your PeSIT Client Connector and PeSIT Server Connector support the PeSIT Store & Forward feature?
It’s up to your MFT product or your business application to organize this feature. Both solutions provide all means necessary to do it.
Our MFT product supports protocols like FTP, SFTP and HTTPS and our customers want a solution offering PeSIT protocol support. We are looking to implement this protocol in our product and your PeSIT Server Connector and PeSIT Client Connector seem to fit our needs. Please tell us more about the connectors and what we have to do to integrate them in our product.
The PeSIT protocol is more complex than common file transfer protocols. To implement all PeSIT functions you will need to integrate both PeSIT Connectors. (You can find the last official specification of the supported PeSIT protocol version E at www.pesit.org).
Our PeSIT Connectors can transfer any serialisable object which can be presented as an InputStream or OutputStream, not only flat files as defined by the protocol.
PSIT Server Connector and PeSIT Client Connector are delivered as java jars with a common API interface allowing your MFT to:
– request to establish or close the connection with a PeSIT partner,
– be notified of any request or message/request/rejection incoming from the partner of any network event,
– accept or reject (specifying PeSIT reason code) any request from PeSIT requestor.
All partner’s, file’s, transfer’s definitions must be managed by your MFT. PeSIT Connectors don’t use any persistence.
Does your PeSIT Client Connector and PeSIT Server Connector support the PeSIT Store & Forward feature?
It’s up to your MFT product or your business application to organize this feature. Both solutions provide all means necessary to do it.
Our MFT product supports protocols like FTP, SFTP and HTTPS and our customers want a solution offering PeSIT protocol support. We are looking to implement this protocol in our product and your PeSIT Server Connector and PeSIT Client Connector seem to fit our needs. Please tell us more about the connectors and what we have to do to integrate them in our product.
The PeSIT protocol is more complex than common file transfer protocols. To implement all PeSIT functions you will need to integrate both PeSIT Connectors. (You can find the last official specification of the supported PeSIT protocol version E at www.pesit.org).
Our PeSIT Connectors can transfer any serialisable object which can be presented as an InputStream or OutputStream, not only flat files as defined by the protocol.
PSIT Server Connector and PeSIT Client Connector are delivered as java jars with a common API interface allowing your MFT to:
– request to establish or close the connection with a PeSIT partner,
– be notified of any request or message/request/rejection incoming from the partner of any network event,
– accept or reject (specifying PeSIT reason code) any request from PeSIT requestor.
All partner’s, file’s, transfer’s definitions must be managed by your MFT. PeSIT Connectors don’t use any persistence.
Our subcontracted printing company needs us to send our print files using the PeSIT protocol. We will have to send them no more than five 100kb files per day and 3 files of a few megabytes at the end of each month. We will not use this protocol for any other partner. Can your Light PeSIT Client ensure these file transfers or it will be better to implement the PeSIT Client Connector?
Any of our 2 solutions will work in the case of your limited and well defined traffic.
The decision which of them should be used will depend on your requirement with the level of control and follow-up of your transfers, and the means that you can allocate to implement the chosen solution. Both solutions offer the same transfer functions. The difference is in their APIs.
Light PeSIT Client is an « independent » jar which can be launched by a simple batch/shell command where all connection/security/transfer parameters are presented in a flat text file. The execution of the jar ends after the end of the transfer or at the first detected error and the only result of the connection/transfer is the return code of the jar.
It’s an affordable and easy to implement solution but you’ll have to find the reason for the connection/transfer failure, if any.
The PeSIT Client Connector is a good choice when you need to follow-up, control your transfers. You can and will not have difficulties building an application to control it to do the job. With the API of the PeSIT Client Connector you must provide all parameters for your connection or transfer request. Your application will be notified of the result of your requests and of any event with all information allowing, for example, generate alert e-mails and send them respectively to corresponding network/security or business service depending on detected local or remote PeSIT diagnostic code. You can chain several transfers in the same connection.
Be sure that your subcontractor doesn’t absolutely need to send you a PeSIT acknowledgement for the file you will send because in this case your application should offer the PeSIT Server facilities.
We have to send a few files per week to our business partner using PeSIT. We don't know the protocol or products for implementing it. Can we use your Light PeSIT Client for this purpose?
Yes, you can. The product is done to send files or PeSIT messages or to receive files to/from a PeSIT partner. If your partner doesn’t send any PeSIT acknowledgments after your file’s reception (or it can avoid it) our Light PeSIT Client should fully respond for your needs.
We would like to replace our old MFT PeSIT solution to migrate all our incoming flows without changing the protocol used to limit the impact of this migration on the IT environment of our many partners/customers. At the same time we plan to modernize our business application to make it more interactive. All these modernization and migration works cannot impact our operations. What do you advise? Should we migrate to an MFT type solution like your MFT X-Protocols or can we integrate your PeSIT Sever Connector into our new application?
Both solutions are possible. You can replace your old MFT by the new one and you’ll benefit from the full MFT file transfer services, (it integrates not only PeSIT Server Connector but also PeSIT Client Connector). At this moment you’ll have to assume future product’s operating costs. If your PeSIT flow is really limited to only PeSIT responder (Server) functions and you anticipate that your PeSIT traffic needs will not go beyond your application, you can implement our PeSIT Server Connector which will work as a black-box. PeSIT Server Connector will be delivered with our sample user application and we can assist you to integrate it in your application for the best result.