B2B Integration 10.2 | Administering and Monitoring B2B Transactions | webMethods Module for EDI | Creating Clients that Send EDI Documents to Integration Server | Sending EDI Documents to Integration Server via FTP | Logic to Include in the FTP Client
 
Logic to Include in the FTP Client
 
Example of Input Parameters for the pub.client:ftp Service
When using FTP, the client must include logic to:
*Initiate an FTP connection to Integration Server's FTP listening port, for example, 8021.
*Change to the directory that represents the service you want to invoke using the cd command.
For example,
cd \ns\myEDIServices\v1\processEDIDoc
Note: The root directory for this operation is your Integration Server's namespace directory (ns), not the root directory of the target machine. Therefore, if you want to send a file to a service in the myEDIServices.v1 folder, you use \ns\myEDIServices\v1\ ServiceName as the path to that service, not Integration Server_directory \instances\$instance_name\packages\myEDIServices\v1\ServiceName.
*Send the EDI document to this directory using the following put command:
put localFileName filename;content type:content sub-type
For example,
put x12_850 x12_850;application:EDIstream
In this example, the local EDI document's name is X12_850, the document's content type is application, and the document's content sub-type is EDIstream.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.