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 | Example of Input Parameters for the pub.client:ftp Service
 
Example of Input Parameters for the pub.client:ftp Service
The following example describes the values that you would set if you used the webMethods pub.client:ftp service to send an EDI document to a service with the fully-qualified name myEDIServices.v1:processEDIDoc. For a complete description of this service, see the webMethods Integration Server Built-In Services Reference for your release.
Set this parameter...
Of data type...
To...
serverhost
String
The name of the machine running Integration Server.
serverport
String
The port on which Integration Server listens for FTP requests.
username
String
A valid user name of an Integration Server user account.
password
String
The password for the user name.
command
String
put
dirpath
String
The path representing the service to invoke, for example, \ns\myEDIServices\v1\processEDIDoc.
localfile
String
The name of the source file containing the EDI document, for example, x12_850.
remotefile
String
The name to assign the file on Integration Server and the content type. Use the following format:
filename;content type:content sub-type
For example,
x12_850;application:EDIstream
secure
Document
Indicates whether the FTP session is with a secure FTP server. The auth parameter specifies the kind of authentication mechanism to use (SSL, TLS, or TLS-P), and the securedata parameter specifies whether the client is sending PROT C (Data Channel Protection Level Clear) or PROT P (Data Channel Protection Level Private).
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.