Installation and configuration overview

To install the Content Manager OnDemand software, you must configure the server control files, create and initialize the database, verify the installation, and prepare the system for use.

About this task

To make it easier to track your progress, print a copy of the list and mark the tasks you have completed.

Procedure

To install and configure the Content Manager OnDemand software, do the following tasks:

Review the IBM Content Manager OnDemand for z/OS: Introduction and Planning Guide.
Review all of the information in Before you begin
Review the current Preventive Service Planning (PSP) information. PSP buckets are identified by UPGRADEs, which identify product levels and SUBSETs, which specify the FMIDs for a product level. The UPGRADE value for Content Manager OnDemand is ODMP95. The SUBSET value for Content Manager OnDemand is H272950.
Determine the type of system configuration that you need to install. To learn more about system configurations, see Server configurations.
Verify that your site has installed the required and optional hardware and software products. For a list of the Content Manager OnDemand prerequisites, see Hardware and software requirements.
Contact the IBM® support center for the latest maintenance levels of the required and optional software, including z/OS®, DB2®, and Content Manager OnDemand.
Print, read and perform any required tasks in Installing the server software.
Install the Content Manager OnDemand software. For installation instructions, see Installing the server software.
Configure the server control files. For an overview of this task, see Configuring a single instance of Content Manager OnDemand.
1. Copy the control files. For more information, see Copy server control files.
2. Verify the ARS.INI file. For more information, see Verify the ARS.INI file.
3. Verify the ARS.CFG file. For more information, see Verify the ARS.CFG file.
4. Modify the ARS.CACHE file. For more information, see Modify the ARS.CACHE file.
5. Optional: Verify the LDAP configuration files. For more information, see Configure LDAP (optional).
6. Optional: Verify the CLI.INI file. For more information, see Verify the CLI.INI file.
7. Modify the ARSSOCKD procedure. For more information, see Modify the ARSSOCKD procedure.
8. Modify the ARSLOAD procedure. For more information, seeModify the ARSLOAD procedure.
Create and initialize the database. For an overview of this task, see Creating and initializing the database.
1. Create the storage group and database. For more information, see Creating the storage group and database.
2. Create a table space for the Content Manager OnDemand system tables. For more information, see Creating the table spaces.
3. Create the Content Manager OnDemand system tables. For more information, see Creating the Content Manager OnDemand system tables.
4. Initialize the system log component. For more information, see Initializing the system log.
5. Optional: Initialize the system load logging facility by running the ARSSYSCR program. For more information, see Initializing the system load logging facility.
6. Initialize the system migration component. For more information, see Initializing system migration.
Prepare the system for use. For an overview of this task, see Preparing the system for use.
1. Define storage sets. You must define storage sets before you can add application groups or load data into the system. For more information, see Preparing the system for use.
2. Configure the System Log application group. Before you define reports to the system, load data, or let users access the system, IBM recommends that you configure the System Log application group. For more information, see Configuring the System Log application group.
3. Optional: Configure the System Load application group. For more information, see Configuring the System Load application group.
4. Configure the System Migration application group. If you plan to migrate index data to archive storage, then you must configure the System Migration application group. For more information, see Configuring the System Migration application group.
5. Backup the Content Manager OnDemand database. After configuring the system, IBM recommends that you create a full backup image of the Content Manager OnDemand database. For more information, see Back up the Content Manager OnDemand database.
Verify the installation. For an overview of the steps in this task, see Verifying the installation.
1. Restart the system.
2. Start the server program (ARSSOCKD).
3. Install at least one of the Content Manager OnDemand client programs. For information about installing the Content Manager OnDemand Windows client software, see the IBM Content Manager OnDemand: Client Installation Guide.
4. Log on to the library server with the Content Manager OnDemand client program.
Do any optional configuration tasks.
- Configure multiple instances of Content Manager OnDemand as described in Defining multiple instances.
- Configure the server print component as described in Server print.
- Configure server programs to start automatically and run on a regular schedule as described in Server tasks.
- Enable large object support as described in Migrated indexes.
- Configure the system to delete OAM and VSAM objects by using SMF records and the ARSEXPIR program as described in Storage manager expiration (deleting OAM and VSAM objects).
- Configure the following Content Manager OnDemand exits:
  - Configure the Content Manager OnDemand system log user exit as described in System log exit.
  - Configure the Content Manager OnDemand security system interface exit as described in User security exit.
  - Configure the Content Manager OnDemand command line programs (such as ARSLOAD) to run without specifying a userid and password as described in Unified login (ARS.PTGN) exit.
  - Configure the system to allow CICS® users to logon without a password as described in CICS client unified login.
  - Configure the system to modify some of the parameters that are used by Content Manager OnDemand when document data is being captured (loaded) by the ARSLOAD program as described in Report specifications archive definition exit.
  - Configure the Content Manager OnDemand client preview user exit, an exit point that allows an installation to modify documents before they are presented to clients as described in Client preview exit.
  - Configure the exit point that is called when Content Manager OnDemand creates table spaces, tables, and indexes for the Content Manager OnDemand data tables as described in Table space creation exit.
- Do the following tasks to install and configure the Structured APIs:
  - Review the structured API installation requirements described in Structured APIs overview.
  - Install the structured APIs as described in Content Manager OnDemand structured API installation instructions.
  - Review the API request and response code messages described in Using the structured APIs.
  - Review the sample drivers described in Structured APIs sample drivers.