An Accelerated Content Services (ACS) server is a light-weight server that is automatically created during a Content Server installation. The ACS server reads and writes content for web-based client applications using HTTP and HTTPS protocols. ACS servers do not modify object metadata but write content to storage areas.
Each Content Server host installation has one ACS server that communicates with one Content Server per repository and the Documentum Message Services (DMS) server. A single ACS server can serve content from multiple repositories. WDK-based applications can use the ACS server if the ACS server is enabled in the app.xml file of the applications.
Most ACS server properties can be modified using Documentum Administrator. Certain ACS server behavior is configured the acs.properties file on the ACS server host and cannot be modified by Documentum Administrator.
The Distributed Configuration Guide provides information on modifying the acs.properties file and additional information about the ACS server.
The ACS server is configured on the ACS Servers Configuration page that can be accessed in the Administration > Distributed Content Configuration > ACS Servers node. The ACS Servers Configuration page displays information about the ACS server, as described in Table 3.2.
Table 3.2. ACS Server Configurations
Column | Description |
---|---|
Name | The name that is assigned to the ACS server during the Content Server installation. The name cannot be modified. |
Content Server | The name of the Content Server the ACS server is associated with. |
Content Access | Specifies how the ACS server can access content. Valid values are:
|
Projections & Stores from | Specifies the connection broker projections, network locations, and local stores information for the ACS server. |
Description | A description of the ACS server. |
Dormancy Status | The current dormancy status of the ACS server. Valid values are:
NoteThe Dormancy Status column is only visible for 7.0 and later versions of repositories. |