Receiving of OFTP Messages

1. Configure the profile of the receiving partner in Trading Networks if not already done.

2. Call the service wm.oftp.gateway.Gw:fetchAndUpdateStatus which fetches the files sent by the partner OFTP station to your OFTP server.

For each file the wm.oftp.gateway.Gw:fetchAndUpdateStatus service parses the payload data and tries to recognize its format.

For each file the service creates an oftpMessageIn message type, adds a <format> identifier and saves the document as XML file in the inbound folder for further processing.

Note:
This service has to be configured as a scheduled service within webMethods Integration Server. The time interval determines when the Adapter for OFTP will fetch all new files available. For information on scheduling services, see webMethods Integration Server Administrator’s Guide.

Note:
To be able to receive OFTP messages, rvsEVO must be started.

3. For receiving messages in Trading Networks, you should invoke the service wm.oftp.tn:receiveOftp to retrieve the messages from the inbound folder.

The wm.oftp.tn:receiveOftp service stores the message in the Trading Networks database.

The wm.oftp.tn:receiveOftp service automatically pulls the sender and receiver information for Trading Networks out of the message header.

Next, the service wm.oftp.tn:receiveOftp parses the message for the content in the following formats:

Known format – The Adapter for OFTP routes contents of a known format, for example, ANSI X.12, EDIFACT, EANCOM, IDOC, as edidata to the service wm.tn:receive. If the format is XML or HTML the service routeXml is used to send the base64 encoded content to Trading Networks.

Unknown format – The Adapter for OFTP stores contents of an unknown format, for example, VDA, ODETTE, UNKNOWN, as the TN document type oftpPayload. The oftpPayload document contains the OFTP IDs of sender and receiver, the format identifier UNKNOWN, VDA or ODETTE and the base64-encoded content.

This service has to be configured as a scheduled service within webMethods Integration Server. The time interval determines when the Adapter for OFTP will fetch all new files available. For information on scheduling services, see webMethods Integration Server Administrator’s Guide.

The Alias name of the remote Integration Server has to be set through a Designer map step at the beginning of the service wm.oftp.tn:receiveOftp if the OFTP Gateway does not reside on the local machine.

Note:
A set of Trading Networks processing rules has to be defined to process the resulting documents.

4. The Adapter for OFTP creates a Transactions relationship between the original message retrieved from the Inbound folder and the extracted, whether the content part is of known or unknown format.

To see relationships go to My webMethods > Monitoring > Integration > B2B > Transactions, search for a transaction and click on the icon in the column Related Documents.

5. The Adapter for OFTP sets the Trading Networks user status of the original message retrieved from the Inbound folder to OFTP received.