Upgrade Guide for Content Manager OnDemand Server V9.0.0

Technote (FAQ)


Question

This guide contains step by step instructions and information to migrate your IBM® Content Manager OnDemand server to V9.0.0. Follow the instructions for the version of OnDemand server you currently have installed.

To ensure you have the latest APAR fixes, stay current with maintenance by applying the latest OnDemand server fixpack.

Answer

Tab navigation





Prerequisites
Upgrading from V8.5.0.X
Upgrading from V8.4.1.X
Upgrading from V8.4.0.X
How to Uninstall OnDemand Server V9.0.0
Miscellaneous

Prerequisites


Requirements for Content Manager OnDemand for Multiplatforms V9.0.0
This document describes the minimum system requirements for Content Manager OnDemand for Multiplatforms V9.0.0.

The installation requires:
  • Linux® and Unix®: 400MB of free space in /tmp and 400MB in /opt
  • Windows®: 800MB of free space in C:\

Upgrading from V8.5.0.X


  1. Perform the Pre-upgrade Tasks in the Planning tab. Ensure you have a current database backup.

    Note: If using an ACIF user exit, it must be recompiled after upgrading to V9.0.0 to utilize the current version of ICU and new OnDemand server installation directory.

    Note: OnDemand server V8.5.0 and later is now a 64-bit application on Windows. The operating system, database, Tivoli® Storage Manager client API, and all customized OnDemand user exits must be 64-bit. ACIF user exits must remain 32-bit. See the Miscellaneous section for information regarding migrating to 64-bit DB2 on Windows.

  2. Download the required target OnDemand server software.
    1. Download the V9.0.0.0 full install package.
    2. Download your target V9.0.0.X fixpack. For example, V9.0.0.1.

  3. Stop your OnDemand library and object server.

  4. Upgrade the OnDemand server software on your library and object server. The fixpack is an executable installer. For example, to install the fixpack via command line on Linux and Unix, run odaix.bin -i console. On Unix and Linux, this step must be performed as root. On Windows, use the account OnDemand server runs under.
    1. Run the V9.0.0.0 installer.
    2. Run your desired target V9.0.0.X fixpack installer.

  5. Alter the OnDemand database for use with V9.0.0 and later by running the following commands on your library server. These commands must be run as the OnDemand instance owner specified in the OnDemand Configurator on Windows or the ars.ini on all other platforms.
    1. Mandatory. Alter the OnDemand database for V9.0.0 and later:

      arsdb -I instance_name -uv

    2. Mandatory if you have Report Distribution installed and V9.0.0.1 or later. Run this command to correct Report Distribution folder field to application group field mappings:

      arssyscr -I instance_name -r

    3. Optional, but recommended. Update the System Log and System Load application groups and folders to support new style dates.

      Important: Once this is performed, older clients (prior to V9.0.0) will not be able to query the System Log or System Load folders.

      Note: When the System Log and System Load application groups are updated, the current table will be closed and a new one will be opened once a new message or load is generated.

      1. Update the System Log application group and folder:

        arssyscr -I instance_name -l -u

      2. Update the System Load application group and folder:

        arssyscr -I
        instance_name -a -u

  6. Update the indexes for the OnDemand system tables. Run these arsdb commands to drop and recreate the indexes for these tables:
    1. Drop the indexes:

      arsdb -I instance_name -efv

    2. Create the new indexes:

      arsdb -I instance_name -rv

    3. Reorg and update statistics on all the OnDemand system tables:

      arsdb -I instance_name -mv

      If using Oracle®, run the following command instead:

      arsdb -I instance_name -sv

  7. Verify the appropriate ulimit settings are in place for the OnDemand instance owner. Since the OnDemand server is a 64-bit process, the soft and hard limits for the user running the server process should be set to unlimited for data (-d), memory (-m), and stack (-s).

  8. Start your OnDemand library and object server.

Upgrading from V8.4.1.X


  1. Perform the Pre-upgrade Tasks in the Planning tab. Ensure you have a current database backup.

    Note: If using an ACIF user exit, it must be recompiled after upgrading to V9.0.0 to utilize the current version of ICU and new OnDemand server installation directory.

    Note: OnDemand server V8.5.0 and later is now a 64-bit application on Windows. The operating system, database, Tivoli® Storage Manager client API, and all customized OnDemand user exits must be 64-bit. ACIF user exits must remain 32-bit. See the Miscellaneous section for information regarding migrating to 64-bit DB2 on Windows.

  2. Download the required target OnDemand server software.
    1. Download the V9.0.0.0 full install package.
    2. Download your target V9.0.0.X fixpack. You must download and apply the V9.0.0.1 or later fixpack as part of the upgrade process from V8.4.1.

  3. Stop your OnDemand library and object server.

  4. Uninstall your OnDemand server software. This step is optional, but recommended to clean remnant uninstall and product registry entries as OnDemand V8.5.0 and later now uses InstallAnywhere to perform the product installation and uninstallation instead of InstallShield.

  5. Upgrade the OnDemand server software on your library and object server. The fixpack is an executable installer. For example, to install the fixpack via command line on Linux and Unix, run odaix.bin -i console. On Unix and Linux, this step must be performed as root. On Windows, use the account OnDemand server runs under.
    1. Run the V9.0.0.0 installer.
    2. Run your desired target V9.0.0.X fixpack installer.

  6. Install IBM Global Security Kit Crypt V8 and IBM Global Security Kit SSL V8 to support encryption and Secure Sockets Layer (SSL) in OnDemand server. Instructions for each platform can be found in the OnDemand README file. This step is required regardless of whether SSL will be used. OnDemand server loads the encryption and SSL libraries on startup. On Windows, this is installed automatically and this step can be skipped.

  7. Set the ARS_ORIGINAL_CODEPAGE ars.cfg parameter. Refer to the OnDemand README section titled "1.3) ARS_ORIGINAL_CODEPAGE" for instructions on this mandatory step.

  8. Alter the OnDemand database for use with V9.0.0 and later by running the following commands on your library server. These commands must be run as the OnDemand instance owner specified in the OnDemand Configurator on Windows or the ars.ini on all other platforms.
    1. Mandatory. Alter the OnDemand database for V9.0.0 and later:

      arsdb -I instance_name -uv

    2. Mandatory if you have Report Distribution installed and V9.0.0.1 or later. Run this command to correct Report Distribution folder field to application group field mappings:

      arssyscr -I instance_name -r

    3. Optional, but recommended. Update the System Log and System Load application groups and folders to support new style dates.

      Important: Once this is performed, older clients (prior to V9.0.0) will not be able to query the System Log or System Load folders.

      Note: When the System Log and System Load application groups are updated, the current table will be closed and a new one will be opened once a new message or load is generated.

      1. Update the System Log application group and folder:

        arssyscr -I
        instance_name -l -u

      2. Update the System Load application group and folder:

        arssyscr -I
        instance_name -a -u

  9. Update the indexes for the OnDemand system tables. Run these arsdb commands to drop and recreate the indexes for these tables:
    1. Drop the indexes:

      arsdb -I instance_name -efv

    2. Create the new indexes:

      arsdb -I instance_name -rv

    3. Reorg and update statistics on all the OnDemand system tables:

      arsdb -I instance_name -mv

      If using Oracle®, run the following command instead:

      arsdb -I instance_name -sv

  10. Verify the appropriate ulimit settings are in place for the OnDemand instance owner. Since the OnDemand server is a 64-bit process, the soft and hard limits for the user running the server process should be set to unlimited for data (-d), memory (-m), and stack (-s).

  11. Start your OnDemand library and object server.

Upgrading from V8.4.0.X


  1. Perform the Pre-upgrade Tasks in the Planning tab. Ensure you have a current database backup.

    Note: If using an ACIF user exit, it must be recompiled after upgrading to V9.0.0 to utilize the current version of ICU and new OnDemand server installation directory.

    Note: OnDemand server V8.5.0 and later is now a 64-bit application on Windows. The operating system, database, Tivoli® Storage Manager client API, and all customized OnDemand user exits must be 64-bit. ACIF user exits must remain 32-bit. See the Miscellaneous section for information regarding migrating to 64-bit DB2 on Windows.

  2. Download the required target OnDemand server software.
    1. Download the V9.0.0.0 full install package.
    2. Download your target V9.0.0.X fixpack. You must download and apply the V9.0.0.1 or later fixpack as part of the upgrade process from V8.4.0.

  3. Stop your OnDemand library and object server.

  4. Uninstall your OnDemand server software. This step is optional, but recommended to clean remnant uninstall and product registry entries as OnDemand V8.5.0 and later now uses InstallAnywhere to perform the product installation and uninstallation instead of InstallShield.

  5. Upgrade the OnDemand server software on your library and object server. The fixpack is an executable installer. For example, to install the fixpack via command line on Linux and Unix, run odaix.bin -i console. On Unix and Linux, this step must be performed as root. On Windows, use the account OnDemand server runs under.
    1. Run the V9.0.0.0 installer.
    2. Run your desired target V9.0.0.X fixpack installer.

  6. Install IBM Global Security Kit Crypt V8 and IBM Global Security Kit SSL V8 to support encryption and Secure Sockets Layer (SSL) in OnDemand server. Instructions for each platform can be found in the OnDemand README file. This step is required regardless of whether SSL will be used. OnDemand server loads the encryption and SSL libraries on startup. On Windows, this is installed automatically and this step can be skipped.

  7. Set the ARS_ORIGINAL_CODEPAGE ars.cfg parameter. Refer to the OnDemand README section titled "1.3) ARS_ORIGINAL_CODEPAGE" for instructions on this mandatory step.

  8. Alter the OnDemand database for use with V9.0.0 and later by running the following commands on your library server. These commands must be run as the OnDemand instance owner specified in the OnDemand Configurator on Windows or the ars.ini on all other platforms.
    1. Optional, but recommended. Update the System Log application group for the longer 2000 character Message Text. If not performed SQL truncation warnings may be issued for certain System Log messages.

      arssyscr -I instance_name -l
      arstblsp -I
      instance_name -a 1 -g "System Log"

    2. Optional. Create the System Load Application Group. Creating this application group will impact loading performance because a new row is inserted for every load.
      1. Run the following SQL query:

        SELECT id FROM arssys

      2. If the value returned is less than 5000, run the following SQL command:

        UPDATE arssys SET id=5000


      3. Run the following command:

        arssyscr -I instance_name -a

    3. Mandatory. Alter the OnDemand database for V9.0.0 and later:

      arsdb -I instance_name -uv

    4. Mandatory if you have Report Distribution installed and V9.0.0.1 or later. Run this command to correct Report Distribution folder field to application group field mappings:

      arssyscr -I instance_name -r

    5. Optional, but recommended. Update the System Log and System Load application groups and folders to support new style dates.

      Important: Once this is performed, older clients (prior to V9.0.0) will not be able to query the System Log or System Load folders.

      Note: When the System Log and System Load application groups are updated, the current table will be closed and a new one will be opened once a new message or load is generated.

      1. Update the System Log application group and folder:

        arssyscr -I
        instance_name -l -u

      2. Update the System Load application group and folder:

        arssyscr -I
        instance_name -a -u

  9. Update the indexes for the OnDemand system tables. Run these arsdb commands to drop and recreate the indexes for these tables:
    1. Drop the indexes:

      arsdb -I instance_name -efv

    2. Create the new indexes:

      arsdb -I instance_name -rv

    3. Reorg and update statistics on all the OnDemand system tables:

      arsdb -I instance_name -mv

      If using Oracle®, run the following command instead:

      arsdb -I instance_name -sv

  10. Verify the appropriate ulimit settings are in place for the OnDemand instance owner. Since the OnDemand server is a 64-bit process, the soft and hard limits for the user running the server process should be set to unlimited for data (-d), memory (-m), and stack (-s).

  11. Start your OnDemand library and object server.

How to Uninstall OnDemand Server V9.0.0


To uninstall OnDemand server V9.0.0:
  • On Linux: /opt/ibm/ondemand/V9.0/_uninst900/uninstallod -i console
  • On Windows: Use Add/Remove Programs in the Control Panel
  • All other platforms: /opt/IBM/ondemand/V9.0/_uninst900/uninstallod -i console

To uninstall Global Security Kit Crypt V8 and Global Security Kit SSL V8, refer to the OnDemand README file.

Miscellaneous


  • To upgrade to OnDemand server V9.0.0, the full install package must be downloaded from IBM Passport Advantage.
  • On Windows, instructions to migrate to 64-bit DB2 are here.

Related information

Best practices: Using Full Text Search with CMOD
Enhancement Retention Management Guide
CMOD V9.0.0 Publication Library
CMOD V9 New Date Types
CMOD V9 Installation Considerations

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Content Manager OnDemand for Multiplatforms
Installation / Upgrading Hints and Tips

Software version:

9.0

Operating system(s):

Linux, Linux zSeries, UNIX, Windows

Reference #:

1620754

Modified date:

2014-01-31

Translate my page

Machine Translation

Content navigation