Configuring distributed transfer settings

The distributed transfer object is created when the repository is created. The distributed transfer configuration object controls whether reading and writing content through ACS is enabled for the repository and whether BOCS pre-caching is also enabled. Administrators cannot create new distributed transfer objects; however, administrators with superuser privileges can configure the default object.

To configure the distributed transfer settings:

  1. Connect to the repository as a user with superuser privileges.

  2. Navigate to Administration > Distributed Content Configuration > Distributed Transfer.

    The Distributed Transfer Settings list page appears. You do not see the distributed transfer setting listed if you are not connected to the global registry.

  3. Locate the distributed transfer setting and select View > Properties > Info.

    The Distributed Transfer Settings Properties - Info page appears.

  4. Modify the properties:

    • Name: Read only. Indicates the name of the content transfer object assigned by the system when the repository is created. There can be only one distributed transfer setting in a repository.

    • ACS Read: Select to enable users to read content in this repository through the ACS.

      If not selected, users requesting documents must go directly to the repository to obtain the requested content.

    • ACS Write: Write content in this repository through ACS. Options are:

      • Synchronous write

      • Synchronous and Asynchronous write

      • None (disabled): This is the default.

    • BOCS Pre-caching: Select to enable the repository to process pre-caching requests. Clear the checkbox to not pre-cache content in the repository.

  5. BOCS Encryption: Select to allow, disable, or require content encryption.

    If you use a default type-based business object (TBO) and content is in an encrypted store, the Require BOCS to always encrypt option is used, regardless of which option you select on the Distributed Transfer Settings Properties - Info page.

    If you write your own TBO, content is encrypted based on what the doGetContentEncryptionMode method returns, regardless of what option you select on the Distributed Transfer Settings Properties page.

    Options are:

    • Use BOCS encryption setting: Select to encrypt content only if the encryption.mode parameter in BOCS acs.properties file is set to Required.

    • Require BOCS to always encrypt content: Select to encrypt content on BOCS. Content is not stored on BOCS if BOCS version does not support encryption or if the encryption.mode parameter in BOCS acs.properties file is set to Disabled.

    • Disable BOCS content encryption: Select to not encrypt content on BOCS.

  6. Click OK to save changes made to the distributed transfer settings properties or Cancel to exit without saving the changes.

    The Distributed Transfer Settings list page appears.