Customizing Built-In Services to Connect to Another VAN
When connecting to a VAN other than GXS, ICC.NET, or MCI, always begin by attempting to connect to the VAN using the information described in
Preparing to Retrieve Documents from a
VAN. If you encounter problems executing the
VAN.VANConnectivity:getFromVAN service and/or the
VAN.VANConnectivity:putToVAN (
VANFTP) service, you need to create customized services.
Create your customized services using the VAN.VANConnectivity:getFromVAN and the VAN:VANConnectivity:putToVAN (VANFTP) services as templates. Be sure to give the customized services different names. Your customized services should use the FTP connectivity services that are provided in the VAN.VANConnectivity folder of the WmEDIforTN package.
If you created a customized service to replace the
VAN.VANConnectivity:getFromVAN service, you can create a scheduled user task to have the service executed at the times you want to retrieve the EDI documents from the VAN. For information about how to use
Integration Server Administrator to set up a user task, see the
webMethods Integration Server Administrator’s Guide for your release.
If you created a customized service to replace the
VAN.VANConnectivity:putToVAN (
VANFTP) service, do the following:
1. Register your customized service as a Trading Networks scheduled delivery service. To do so, invoke the wm.tn.delivery:registerService service. For information about this service, see the webMethods Trading Networks Built-In Services Reference for your release.
2. Update the definition for the scheduled delivery queue that you created for sending EDI documents to VANs by replacing the VANFTP delivery service with the registered service name of your customized service. In My webMethods, do this on the Public Queue Information page (Administration > Integration > B2B > Public Queues, select the queue, and click Edit).