Configuring Policies for Onward File Transfer › Policy Transfer XML Schema › How Files Are Distributed

How Files Are Distributed

For Policy Transfer XML, files are always sent from the CA XCOM Gateway environment. So, for a SENDFILE, SENDJOB, or SENDREPORT action, CA XCOM Gateway always overrides the local file to identify the file within the CA XCOM Gateway environment that is to be distributed. Any local file specification within the configured Policy Transfer XML is therefore disregarded, but the configured remote machine and remote file name determine the destination of the distributed file. Similarly, for a RECEIVEFILE action, CA XCOM Gateway always overrides the remote file specification within the configured Policy Transfer XML, and the local machine and file name determine the destination of the distributed file.

To enable successful distribution, the CA XCOM Data Transport server that will be transmitting a file needs to be able to access the file from the CA XCOM Gateway realm storage area. So, for the SENDFILE, SENDJOB, and SENDREPORT actions, the local machine defined for the TRANSFERCONTAINER must specify one of the following:

• The localhost machine (that is, the same machine that is running CA XCOM Gateway)
• A machine whose file system can access the CA XCOM Gateway realm storage area by using network access

When using the RECEIVEFILE action, this same rule applies to the remote machine defined for the TRANSFERITEM.