Checklist for installation on Linux™

You should review the pre-installation instructions checklist before installing the product on Linux.

About this task

Figure 1. Pre-installation tasks
Flow of pre-installation tasks

Before beginning the installation, you should complete the following tasks:

Procedure

  1. Contact the IBM® Support Center for the latest maintenance levels of Db2®, Content Manager OnDemand, and optionally, Tivoli® Storage Manager and Infoprint Manager (Infoprint).
  2. Obtain a copy of the latest Content Manager OnDemand README file. Print and read the entire file before you begin.
  3. Check the Content Manager OnDemand prerequisites and verify the required and optional hardware and software products (see Linux™ server requirements).
  4. Check the hardware and software requirements for all system components and features. See Hardware and software requirements for IBM Content Manager OnDemand for details.
  5. Determine the type of system configuration that you need to install (see Choosing a configuration).
  6. If you are upgrading to a new version of Content Manager OnDemand, save the configuration files used by the system (see Saving configuration files on Linux™).

Results

Figure 2. Installing Content Manager OnDemand and related software
Flow of installation tasks
Configuring a Content Manager OnDemand system typically requires that you do the following tasks:
  1. (Optional) Create a user account for the Content Manager OnDemand instance owner (see Creating a root or non-root user for the Content Manager OnDemand instance owner on Linux).
  2. Install and configure the database manager product on the library server (see Installing the database manager on Linux™).
  3. Install the IBM Global Security Kit (GSKit) (see Installing IBM® Global Security Kit on Linux™).
  4. If you plan on using SSL for security, set up SSL on the Content Manager OnDemand server and client (see Setting up SSL on a Content Manager OnDemand Linux server).
  5. If you plan to maintain data in archive storage, install and configure Tivoli Storage Manager on the library server or on each object server that will be used to maintain data in archive storage (see Installing and configuring Tivoli Storage Manager on Linux™).
  6. Install the Content Manager OnDemand software on each workstation that is part of the Content Manager OnDemand system (see Installing the Content Manager OnDemand software on Linux).
  7. Configure an instance of Content Manager OnDemand on each workstation that is part of the Content Manager OnDemand system (see Configuring instances on Linux™). This step includes the following tasks:
    1. Specify the instance in the ARS.INI file (see Specifying instances in the ARS.INI file)
    2. Specify the ARS.CFG file for the instance (see Specifying the ARS.CFG file for the instance)
    3. Specify the ARS.DBFS file for the instance (see Specifying the ARS.DBFS file for the instance)
    4. Specify the ARS.CACHE file for the instance (see Creating the ARS.CACHE file for the instance)
  8. Create the instance of Content Manager OnDemand (see Creating an instance of Content Manager OnDemand on Linux). This step includes the following tasks:
    1. Specify permissions for the database directories (see Specifying permissions for the database directories)
    2. Create the instance by running the ARSDB program (see Creating an instance of Content Manager OnDemand on Linux™)
    3. Initialize the system logging facility by running the ARSSYSCR program (see Initializing the system logging facility)
    4. (Optional) Initialize the system migration facility by running the ARSSYSCR program (see Initializing the system migration facility)
    5. (Optional) Initialize the system load logging facility by running the ARSSYSCR program (see Initialize the system load logging facility).
  9. Automate instance operations (see Automating instance operations on Linux™). This step includes the following tasks:
    1. Start the database on the library server (see Starting the database)
    2. Start the instance on the library server (see Starting the instance on the library server)
    3. Start the instance on an object server (see Starting the instance on an object server)
    4. Start the data loading programs (see Starting the data loading programs)
    5. Schedule application group maintenance on the library server (see Scheduling application group maintenance on the library server)
    6. Schedule application group maintenance on an object server (see Scheduling application group maintenance on an object server)
    7. Schedule system table maintenance (see Scheduling system table maintenance)
    8. Schedule a backup of the Content Manager OnDemand database (see Scheduling the Content Manager OnDemand database backup)
Figure 3. Verifying the installation
Flow of verification tasks

Verify the installation of Content Manager OnDemand (see Verifying the installation):

  1. After installing and configuring each Content Manager OnDemand server, restart the system. The operating system reinitializes and starts the services required by Content Manager OnDemand.
  2. Log in to the library server with a Content Manager OnDemand client program. (To access the system, you must install at least one of the Content Manager OnDemand client programs on a PC running Microsoft Windows. See the IBM Content Manager OnDemand: Client Installation Guide for installation information about the OnDemand Client or the IBM Content Manager OnDemand for Multiplatforms: Administration Guide for installation information about the OnDemand Administrator client.)
Figure 4. Preparing the system for use
Flow of verification tasks
Prepare the system for use:
  1. Define storage sets (see Define storage sets). Before you add application groups or load data into the system, you must define storage sets.
  2. Configure the System Log application group (see Configuring the System Log application group). Before you define reports to the system, load data, or let users access the system, you should configure the System Log application group.
  3. If you plan to migrate index data to archive storage, configure the System Migration application group (see Configure the System Migration application group).
  4. Back up the databases (see Backing up the Content Manager OnDemand database). After configuring the system, you should create a full backup image of the Content Manager OnDemand database and the Tivoli Storage Manager database.
Installing and configuring optional software:
  1. If you plan to use Download for the z/OS® feature (Download) to transmit data from z/OS systems to Content Manager OnDemand servers, then you must install and configure Download. Follow the instructions in PSF for z/OS: Download for z/OS to plan, install, configure, and verify the installation of the Download software. Then configure Download on each Content Manager OnDemand server. Complete the following tasks:
    1. Obtain a copy of PSF for z/OS: Download for z/OS.
    2. Check the prerequisites and verify the z/OS and TCP/IP software levels for Download.
    3. Install and configure the Download software.
    4. Configure Download on each Content Manager OnDemand server that will receive data sets from an z/OS system. (see Starting the data loading programs).
  2. If you plan to reprint documents using the Content Manager OnDemand server print function, you must install Infoprint on a workstation that belongs to the same network as the Content Manager OnDemand library server. Follow the instructions in the Infoprint documentation for your operating system to plan, install, configure, and verify the installation of the Infoprint software. Then configure the server print function on the library server. Complete the following tasks:
    1. Obtain a copy of the Infoprint documentation for the server operating system.
    2. Install and configure Infoprint.
    3. Verify that all of the resources and fonts that your organization requires to reprint the reports that you plan to store in Content Manager OnDemand are installed on the Infoprint server.
    4. Define the print queues and devices that Infoprint uses to manage the Content Manager OnDemand server print environment.
    5. Obtain the TCP/IP host name or IP address of the Infoprint server.
    6. On the library server, edit the ARSPRT file and insert the host name or IP address of the Infoprint server. The ARSPRT file can be found in the /opt/ibm/ondemand/V10.5/bin directory.
    7. Define a server printer on the Content Manager OnDemand library server with the OnDemand Administrator client.
  3. If you need to customize and enhance the standard functionality within the product, see the user exit documentation in the Appendix of this publication. A user exit is a point during processing that enables you to run a user-written program and return control of processing after your user-written program ends. Content Manager OnDemand provides the following user exit points:
    1. Download user exit
    2. Report specifications archive definition user exit
    3. Retrieval preview user exit
    4. Security user exit
    5. System log user exit
    6. Table space creation user exit