Immediate Delivery

Immediate delivery uses immediate delivery methods, immediate delivery services, and, if you use reliable delivery, delivery tasks. An immediate delivery method invokes an immediate delivery service that delivers a single document to the receiving partner. A delivery task is a task Trading Networks creates to keep track of its attempts to redeliver a document when you are using reliable delivery. The options for immediate delivery are as follows:

Trading Networks provides standard FTP, FTPS, HTTP, HTTPS, SMTP, and Web service delivery methods. You can create custom immediate delivery methods from these methods; you create the custom method in one profile, and then you can select the method in other profiles. When you create a custom method from a standard method, Trading Networks automatically creates the corresponding immediate delivery service. If that service does not meet your needs, you can create a custom service to replace it.

Trading Networks provides built-in immediate delivery methods for primary and secondary email, FTP, FTPS, HTTP, and HTTPS, and provides the corresponding built-in delivery services. If the services do not meet your needs, you can create custom services to replace them.

You can create custom immediate delivery services. For example, you might want to create a custom service that delivers a message into a message queuing system. After you create a custom service, you register it with Trading Networks, and Trading Networks automatically creates the corresponding immediate delivery method.

Trading Networks provides ActiveTransfer as a delivery method. By using the managed file transfer capabilities of ActiveTransfer, you can leverage the B2B capabilities of Trading Networks to manage and deliver documents to partners securely and efficiently as follows:

Configure Trading Networks as a central partner management to use ActiveTransfer Server depending on whether ActiveTransfer is installed on a local, remote, or clustered environment, as the preferred document delivery method. For more information, see Configuring Alias for ActiveTransfer on Remote Server.

Select an ActiveTransfer VFS path for the partners. Using the VFSPath, senderPartnerID, receiverPartnerID, and VFSID parameters, ActiveTransfer sends the BizDocument to the partners.

View the status of the document delivery and the delivery details from ActiveTransfer on the Transactions and Activity Log pages.

Note:

Trading Networks does not support the delivery of large documents to ActiveTransfer on a remote Integration Server instance. For more information about handling large documents in Trading Networks, see Large Document Handling.

To use immediate delivery for a partner, define one or more immediate delivery methods in the partner’s profile. You can then specify the method to use for a document on the Deliver Document By action.

You can designate one immediate delivery method as the partner’s preferred protocol, and specify using the partner’s preferred protocol for a document on the Deliver Document By action. The preferred protocol option is primarily for use with webMethods eStandards Modules.

To use reliable delivery, you specify the Save Document to Database pre-processing action on the processing rule. In the receiving partner's profile, you specify the number of times to try to deliver a document to the partner and the amount of time to wait between attempts. If Trading Networks retries the maximum number of times and delivery is unsuccessful, it changes the delivery task status to FAILED. If you correct the problem, you can restart the task and Trading Networks will start trying to deliver the document again.