Defining the Scheduled Delivery Queue
To define a scheduled delivery queue for delivering EDI documents to a VAN, you define a Trading Networks public queue using My webMethods. You define one queue for each VAN to which you want to deliver documents. For example, if you want to connect to GXS and MCI, you must define a public queue for GXS and MCI. If you want, you can set up more than one queue for a VAN. For example, you might define multiple queues for a single VAN if you have more than one account for the VAN.
When you define the queue, you:
Assign the queue a name. You can give the queue any name you want. When you define a processing rule to place outbound EDI documents in the queue, you will select the queue by the name you assign it.
Associate the queue with a scheduled delivery service. You associate the queue with the
VANFTP scheduled delivery service. The
VANFTP scheduled delivery service is the
VAN.VANConnectivity:putToVAN service.
Module for EDI registers the
putToVAN service as a
Trading Networks scheduled delivery service and assigns it the name
VANFTP in
Trading Networks. The
VANFTP service uses FTP to deliver documents to a specific VAN.
Assign a state. Define whether
Trading Networks can add delivery tasks into a queue and deliver the documents that correspond to the delivery tasks in the queues.
Assign the input values for the VANFTP service. Set the values for the
VANFTP service to indicate the VAN to which you want to connect and to set optional actions you want the
VANFTP service to perform. For example, you can indicate that you want to retrieve VAN-generated reports.
Associate the queue with a schedule. You specify the times that you want to deliver the outbound EDI documents to the VAN. At the times specified by the schedule,
Trading Networks invokes the
VANFTP scheduled delivery service to send the outbound EDI documents that are in the queue to the VAN.
The following table describes information that you need to supply when defining the public queue in My webMethods.
Public Queue Setting | Description |
Queue name | The name you want to give the scheduled delivery queue. For example, if you are defining a queue to hold EDI documents to be sent to the MCI VAN, you might name the queue "MCI Queue". |
Delivery service | The delivery service you want to associate with the queue. Select VANFTP. |
Inputs | The inputs for the VANFTP service. When Trading Networks invokes the VANFTP service, Trading Networks passes the inputs that you specify in the input parameters. The input parameters that you specify for the VANFTP service identify the VAN to which you want to connect to deliver the EDI documents in the queue. The following describes other input parameters to the VANFTP service that you can use to specify optional actions that you might want the VANFTP service to perform in addition to delivering the outbound EDI documents. To learn about all the input parameters to the VANFTP service, see the description of the VAN.VANConnectivity:putToVAN service in webMethods Module for EDI Built-In Services Reference . |
| Use this input parameter... | To have the VANFTP service perform this optional action... |
| getReport | Get VAN-generated reports after delivering the outbound EDI documents. |
| getInbound | Retrieve inbound EDI documents from the VAN after it delivers the outbound EDI documents from the queue. The VANFTP service always submits the inbound EDI documents that it retrieves to Trading Networks for processing. |
State | The state of the queue. Select Enable, Disable, Drain, or Suspend Delivery. For more information about these states, see the webMethods Trading Networks Administrator’s Guide for your release. |
Schedule | When you want Trading Networks to invoke the VANFTP service to deliver the EDI documents in the queue you are defining. |
Note: You should not set private queues for delivering EDI documents to VANs. You can only use a private queue for a specific trading partner while public queues can be used by multiple trading partners.