Chapter 2. Setting up a Content Manager OnDemand instance 39
ARS.CFG
When an instance is started, Content Manager OnDemand reads the ARS.INI file to 
determine where the server configuration file is. Each instance must have its own ARS.CFG file 
that is determined by the SRVR_OD_CFG parameter in ARS.INI.
For a distributed library server or object server, you must configure a copy of the ARS.CFG file 
on each distributed server.
When you configure the parameters, the default values are sufficient for most installations. 
However, you might need to adjust and tune them to meet the requirements of your 
environment.
Figure 2-8 shows the content of a sample ARS.CFG file.
Figure 2-8   ARS.CFG file sample
ARS.CACHE
The ARS.CACHE file identifies the file systems on the server that can be used by Content 
Manager OnDemand for the cache storage. The file system is in the HFS or z/OS file system 
(zFS) storage.
Figure 2-9 shows an example of an ARS.CACHE file that specifies two cache storage file 
systems.
Figure 2-9   ARS.CACHE file sample
ARS_ORIGINAL_CODEPAGE=
ARS_LOCAL_SRVR=
ARS_NUM_DBSRVR=20
ARS_NUM_LICENSE=1
ARS_NUM_OAMSRVR=20
ARS_OAM_DB2SSID=DSNA
ARS_OAM_PLAN=CBRIDBS
ARS_PRINT_PATH=/ars/tmp
ARS_SRVR=
DB_ENGINE=DB2
ARS_LDAP_ALLOW_ANONYMOUS=TRUE /* Allow anonymous bind connections */
ARS_LDAP_BASE_DN=foo /* Specifies ’foo’ as base distinguished name 
*/
ARS_LDAP_BIND_ATTRIBUTE=bar /* Specifies ’bar’ as bound attribute */
ARS_LDAP_BIND_MESSAGES_FILE=’$ONDEMAND/LDAP/msg_string.txt’ /* 
Specifies location of LDAP message string file */
ARS_LDAP_MAPPED_ATTRIBUTE=foonly /* Specifies attribute ’foonly’ 
returned to \
OnDemand as user ID */
ARS_LDAP_PORT=389 /* Specifies port on which LDAP listens */
ARS_LDAP_SERVER=127.0.0.1 /* Specifies IP address of LDAP server */
/ars1
/ars2