Adapter for OFTP 9.0 | webMethods Adapter for OFTP Documentation | webMethods Adapter for OFTP Installation and User’s Documentation | OFTP Message Processing | Sending Outbound Messages | Receiving of Inbound Notifications
 
Receiving of Inbound Notifications
*To process inbound notifications from your OFTP partner station
1. Call the service wm.oftp.gateway.Gw:fetchAndUpdateStatus. This service queries the rvsEVO database for the status of sent jobs as listed in the cross-reference table.
For each job in rvsEVO with status sp_processing, it generates a notification message oftpStatusIn with statusType transmitStatus and saves it in the inbound folder. For information on the structure of oftpStatusIn, see Structure of Sent Message.
For each job in rvsEVO with status deleted, it generates a notification message oftpStatusIn with status type nonTransmitStatus and saves it in the inbound folder.
For each completed job in rvsEVO with status ended, it
*generates a notification message oftpStatusIn with statusType positiveEERPin and saves it in the inbound folder.
*deletes the entry in the reference table.
Note:
The service wm.oftp.gateway.Gw:fetchAndUpdateStatus 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.
2. Call the service wm.oftp.tn:receiveOftp. The service takes the oftpStatusIn documents and stores it in the Trading Networks database.
The sender and receiver information for Trading Networks is gained out of the message header automatically.
After receiving an inbound notification, the Adapter for OFTP then sets the actual value of the user status of the related oftpMessageIn within Trading Networks document to
*OFTP transmit status when value of statusType is transmitStatus.
*OFTP non-transmit status when value of statusType is nonTransmitStatus.
*OFTP positive-EERP when value of statusType is positiveEERPin.
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:
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.
3. The Adapter for OFTP creates a Trading Networks relationship between the original oftpMessageOut message sent to the OFTP partner station and the particular oftpStatusIn notification messages.