|
|
|
To use TCP/IP protocols for a CA XCOM Data Transport transfer, CA XCOM Data Transport must have the port specification for the remote system and an indication that you wish to use TCP/IP protocols.
The port is specified by the PORT parameter. The default value in the xcom.glb file should be valid for most remote hosts. However, when executing transfers that specify an IPv6 remote address and/or the parameter SECURE_SOCKET=YES for secure transfers using OpenSSL, then the PORT parameter value would need to be changed accordingly. For more information about configuring CA XCOM Data Transport for secure transfers, see the chapter “Generate SSL Certificates” later in this guide.
If you need to change the port value of the local system, see the CA XCOM Data Transport Installation Guide for UNIX and Linux.
The choice of protocol to use is indicated by the PROTOCOL parameter. This can be specified at the command line, in a configuration file, or in the xcom.glb file, depending upon your installation's needs. If the protocol is not specified at the command line, the defaults specified in the configuration file or in xcom.glb are used.
In addition, CA XCOM Data Transport uses other parameters for TCP/IP functionality. These parameters are of interest to system administrators for tuning and performance considerations. They are described in the section on xcom.glb parameters in the chapter "Operating Environment" and are also listed in the appendix "Parameters."
Example 1:
In this example, the xcomtcp command is used to queue a file for a send file transfer, using TCP/IP. The configuration file is myconfig.cnf, the local file is named testa.aaa, and the remote file is named testb.bbb. The remote system is indicated by the host name goodsys in the REMOTE_SYSTEM parameter. QUEUE is set to YES, so the transfer is queued. TCP/IP is indicated by the value TCPIP in the PROTOCOL parameter. The port is determined by the value of the PORT parameter in the xcom.glb file.
xcomtcp -c1 -f myconfig.cnf LOCAL_FILE=testa.aaa REMOTE_FILE=testb.bbb REMOTE_SYSTEM=goodsys QUEUE=YES PROTOCOL=TCPIP
Example 2:
In this example, the xcomtcp command is used to submit a transfer directly, without sending it to the queue, using TCP/IP. The configuration file is myconfig.cnf, the local file is named testa.aaa, and the remote file is named testb.bbb. The remote system is indicated by the fully qualified domain name goodsys.goodsite.com in the REMOTE_SYSTEM parameter. QUEUE is set to NO, so the transfer starts immediately after you press Enter. TCP/IP is indicated by the value TCPIP in the PROTOCOL parameter. (If the default value in the configuration file or the xcom.glb file is TCPIP, you do not need to specify this value here.) The port is indicated by the value 8044 in the PORT parameter.
Note: The default value of PORT should be valid for most hosts, and you should only specify a value for this parameter when needed.
xcomtcp -c1 -f myconfig.cnf LOCAL_FILE=testa.aaa REMOTE_FILE=testb.bbb REMOTE_SYSTEM=goodsys.goodsite.com QUEUE=NO PROTOCOL=TCPIP PORT=8044
The number of the TCP/IP port on the remote CA XCOM Data Transport server. Used for TCP/IP transfers only.
Range: 1 to 65535
Default: 8044
| Copyright © [set copyright date variable] CA. All rights reserved. |
|