Configuring Policies for Onward File Transfer › Policy Configuration

Policy Configuration

You can use the Process Policies page to add policies to the policy database.

Note: You need to have Super Admin authority.

To add new policies

1. Log in to CA XCOM Gateway.

   The Home page appears.

2. Click Admin.

   The Admin page appears.

3. Click Process Policies.

   The Process Policies page appears.

4. Click Add New Policies.

   The Add New Policy page appears.

5. Enter the following details for a new policy:

   Realm Name

   The realm name that is specified for a policy defines the realm to which the policy is to belong, which in turn defines the physical storage location to be used to store all files associated with the policy. After a policy has been defined, the designated realm may be changed. However, in this situation, although new files will be stored in the physical location defined for the new realm, files that have already been stored will remain in their current location (that is, they will not be moved to the storage location defined for the new realm).

   File Limits

   The total file limits define limits that apply to stored files of all types that are associated with this realm. In contrast, user file limits define limits for files associated with this realm that have been uploaded into CA XCOM Gateway by registered users by means of either http(s) or ftp(s) upload, and XCOM file limits define limits for files associated with this realm that have been transferred into CA XCOM Gateway from CA XCOM Data Transport.

   When a file limit is set to a value other than UNLIMITED, it restricts the number of files that can coexist in CA XCOM Gateway at any given time. When a size limit is set to a value other than UNLIMITED, it restricts the total size of the files that can coexist in CA XCOM Gateway at the same time. Size limits can be specified in bytes, or in kilobytes, megabytes, gigabytes, or terabytes, suffixed by K, M, G, or T respectively.

   Note: The specified value is always rounded to the nearest number of kilobytes. For example, if 700 is entered as a size limit, it is automatically changed to 1024.

   Retention

   The two retention periods define a number of days for which stored files associated with this policy are to be retained by CA XCOM Gateway. The unextracted retention period (also known as the long retention period) applies to files when they have not been downloaded by one or more of the subscribed users of the policy. The extracted retention period (also known as the short retention period) applies to files after they have been downloaded by all subscribed users of the policy. For more information about user subscription, see Configure User Permissions for a Policy, later in this chapter.

   Retry

   The Schedule Retry Interval and Schedule Retry Limit values influence the action to be taken when CA XCOM Gateway needs to schedule a data transfer to distribute a file across the CA XCOM Data Transport server network. If CA XCOM Gateway is unable to contact the local CA XCOM Data Transport server, in order to schedule a transfer, it retries repeatedly at the specified interval (in seconds), up to the number of times specified by the limit value. If either or both of these values are omitted, the corresponding value defined in the global parameters is used by default.

   User File Sharing

   User File Sharing specifies whether files that are uploaded by a user, for this policy, should be made available for download by other users who are authorized to download files for the policy. If User File Sharing is set to No, user-uploaded files are eligible for data transfer using CA XCOM Data Transport, but are not available for other users to download.

   Cipher

   The cipher parameter defines the algorithm to be used to encrypt all stored files associated with this policy. If this parameter is set to None, files for the policy are stored unencrypted.

   Digest

   The digest parameter defines the algorithm to be used to create a hash value of file content when storing a file associated with the policy. Subsequently, whenever the file is accessed (for user download or data transfer), the file content is analyzed and the saved hash value checked, thus ensuring the integrity of the file data. If this parameter is set to None, files for this policy are not hashed.

   Policy Transfer XML

   Two sets of TRANSFERCONTAINER xml can be configured for a policy, to define transfers to be initiated on arrival into CA XCOM Gateway of a new file associated with the policy:

   • The first set of xml is used for files that have been uploaded by a registered user by using either HTTP(S) or FTP(S).
   • The second set is used for files that have been transferred into CA XCOM Gateway by using CA XCOM Data Transport.

   In each case, the xml is optional and can be omitted if there is no requirement for onward data transfer of files by using CA XCOM Data Transport. You can use the export facility of the CA XCOM Data Transport GUI to generate TRANSFERCONTAINER xml, after defining transfer requirements by using the GUI. The file created by this export facility can then be copied and pasted into the boxes on the policy configuration screen.

   For more information about Policy Transfer XML, see the following section.

   For more information about Policy Transfer XML fields, see Policy Transfer XML Schema.

6. Click Save.

   The new policy is added to the policy database and a confirmation message is displayed.