text: **2.3 Implementing a Content Manager OnDemand instance on a**
  **multiplatform UNIX environment**
  
  In this section, we describe how to set up a single instance in a Content Manager OnDemand 
  for a multiplatform UNIX environment. Always refer to the product documentation of your 
  release for the specific steps to follow. 
  
  **2.3.1 Defining a single instance**
  
  By default, the initial instance on any library server is named archive. Creating a single 
  instance can be summarized by the following steps: 
  
  1. Creating a user 
  2. Creating a DB2 instance 
  3. 
  4. Setting up Secure Sockets Layer (SSL) 
  5. Storing user IDs and passwords in a stash file 
  6. 
  7. Configuring the instance 
  8. Creating a Content Manager OnDemand database 
  Initializing the system log and system load facility 
  9. 
  
  Installing IBM Global Security Kit 
  
  Installing and configuring Tivoli Storage Manager 
  
  **Creating a user**
  New installations (instances) of Content Manager OnDemand can be configured to run under 
  a user other than the root user. If you plan to run an instance under a user other than root, 
  complete the following steps: 
  
  1. Create the user for the Content Manager OnDemand instance owner that is a member of 
  the database owners group. 
  
  2. Give the user administrator authority to the database. 
  
  3. Set permissions for the cache storage file systems. 
  
  4. Set permissions for the Content Manager OnDemand configuration and script files. 
  
  5. Give the instance owner permission to write to the system console. 
  
  6. Specify the instance owner in the ARS.INI file. 