Previous Topic: Upload a Policy

Next Topic: CA XCOM Data Transport Gateway Schedule Parameters

Test the Onward Transfer

To check the CA XCOM Gateway onward transfer

  1. Set up SMTP notification in the CA XCOM Gateway policy and in the Delivery Transfer XML.

    You will receive email notification about the CA XCOM Gateway upload and the CA XCOM Data Transport delivery status.

  2. Verify the delivery.

    The easiest way is to check if file is delivered. Check the location shown as the file name under Remote System Parameters.

    In our example, this is C:\temp\delivered.txt.

  3. Verify the Files Pending Download status of the policy.

    When a file is uploaded, CA XCOM Gateway increments the Files Pending Download count.

    Example

    Displays status of files pending download

    When CA XCOM Gateway delivers the file, the Files Pending Download count is decremented.

  4. On the local system mentioned in the Delivery Transfer XML, do the following:
    1. Open the CA XCOM Data Transport GUI.
    2. Go to the Get History tab.
    3. Change the End Date Time to the current time and click Submit.

      Some records appear, as follows:

      Displays history records for an onward transfer

      Notes:

      • CA XCOM Gateway takes some time to retransmit the file. Retry history retrieval again after some time. If you do not receive any record, verify your Delivery Transfer XML file.
      • In the example, the local CA XCOM Data Transport system and the remote CA XCOM Data Transport system both are same; so there are two records listed. If the remote CA XCOM Data Transport system is a different system, you will have only one record (SENDFILE).
    4. Click the Req. No. (SENDFILE) to get the detailed history record.
    5. Check the sending side details.

      Note the file name, which is set by CA XCOM Gateway. While configuring the Policy Transfer XML, we had set this to ANY.

  5. On the remote system mentioned in the Delivery Transfer XML, do the following:
    1. Open the CA XCOM Data Transport GUI.
    2. Go to the Get History tab.
    3. Change the End Date Time to the current time and click Submit.

      Some records appear, as follows:

      Displays history records for an onward transfer

      Notes:

      • CA XCOM Gateway takes some time to retransmit the file. Retry history retrieval again after some time. If you do not receive any record, verify your Delivery Transfer XML file.
      • In the example, the local CA XCOM Data Transport system and the remote CA XCOM Data Transport system both are same; so there are two records listed. If the local CA XCOM Data Transport system is a different system, you will have only one record (RECEIVEFILE).
    4. Click the Req. No., on the row showing a transfer type of RECEIVEFILE, to get the detailed history record.
    5. Check the receiving side details.

      Note the file name, which is the file delivered by CA XCOM Gateway.

      Displays receiving system information for history records

  6. To check the log, do the following:
    1. Open the CA XCOM Gateway log file, which is located at your <<Gateway_Home>> \log.

      Example

      C:\Program Files\CA\XCOMGW\Logs

    2. Search for the file name you uploaded:
      12-21-2010/12:52:55.701/GMT+05:30 INFO [nalma04] XCOMA2039I C:\sample.txt uploaded successfully 
      
    3. The CA XCOM Gateway daemon starts the process cycle periodically:
      12-21-2010/12:52:55.721/GMT+05:30 INFO [nalma04] XCOMA6119I Process cycle execution starts
      
    4. The CA XCOM Gateway daemon starts the processing:
      12-21-2010/12:52:55.721/GMT+05:30 INFO [nalma04] XCOMA6120I Process cycle transfer schedule execution starts
      
    5. Policy processing starts by submitting the Delivery Transfer XML for your policy:
      12-21-2010/12:52:59.997/GMT+05:30 INFO [] XCOMA5041I Policy PolicyWithOnwardTransfer, returns SubmissionHandle=6 for the transfer <transfer xml stripped….>
      
    6. Finally, when your file gets downloaded:
      12-21-2010/12:53:30.962/GMT+05:30 INFO [] XCOMA2037I 0a12819c-4da8-45f8-85ad-51e8fdbb03c3 downloaded successfully
      
    7. Check that the GUID matches the uploaded file.