IBM Support

Upgrade guide for Content Manager OnDemand server V9.5.0

Technote (FAQ)


Question

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

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

Answer

Tab navigation






Prerequisites


Requirements for Content Manager OnDemand for Multiplatforms V9.5.0
This document describes the minimum system requirements for Content Manager OnDemand for Multiplatforms V9.5.0. Further information can be found in the product README.


Upgrading from V9.0.0.X


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

    Note: The OnDemand server install now also contains and installs the Content Manager OnDemand Web Enablement Kit (ODWEK).

    Note: The OnDemand server does not support OnDemand Clients (e.g. Windows Client, ODWEK, CICS, etc.) prior to V8.5.

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

  2. Download the required target OnDemand server software.
    1. Download the V9.5.0.0 full install package from IBM Passport Advantage.
    2. Download your target V9.5.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.5.0.0 installer.
    2. Run your desired target V9.5.0.X fixpack installer.

  5. On Linux and Unix platforms, update the IBM Global Security Kit Crypt and IBM Global Security Kit SSL software for OnDemand V9.5. A newer version is included and required by OnDemand V9.5.
    1. Uninstall your current Global Security Kit Crypt and IBM Global Security Kit software. Refer to the product README for platform specific uninstallation steps.
    2. Install the updated Global Security Kit Crypt and IBM Global Security Kit software. Refer to the product README for platform specific installation steps.

  6. Restore your OnDemand server configuration files (ars.ini, ars.cfg, ars.cache, ars.dbfs, arsload.cfg) and custom user exits to your OnDemand V9.5 directories. By default, V9.5 will be installed to a different directory than V9.0.

  7. Alter the OnDemand database for use with V9.5.0 by running the following commands on your library server as the OnDemand instance owner specified in the OnDemand Configurator on Windows or the ars.ini on all other platforms.
    1. Mandatory. Drop the OnDemand system table indexes:

      arsdb -I instance_name -efv

    2. Mandatory. Alter the OnDemand database:

      arsdb -I instance_name -uv

    3. Mandatory. Recreate the OnDemand system table indexes:

      arsdb -I instance_name -rfv

    4. Mandatory. 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

    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

  8. Migrate the OnDemand Report Distribution Facility (RDF) definitions to the new OnDemand Distribution Facility (ODF). This step should only be performed if you have the OnDemand Report Distribution Facility installed.

    Note: RDF has been deprecated and replaced with ODF. Although it has been deprecated, RDF is still provided in V9.5 in order for customers to transition to ODF. You can continue to run RDF, however it will no longer exist in any future release of OnDemand, therefore customers are expected to migrate as soon as possible to ODF.
    1. Create the ODF tables and definitions:

      arsdb -I instance_name -Ortv

    2. Convert and export the RDF definitions to XML files:
      1. On AIX® and Solaris®:

        export CLASSPATH=/opt/IBM/ondemand/V9.5/jar/rdf2odf.jar:${CLASSPATH}

      2. On Linux and Linux for System z:

        export CLASSPATH=/opt/ibm/ondemand/V9.5/jar/rdf2odf.jar:${CLASSPATH}

      3. On Windows®:

        set CLASSPATH=C:\Program Files\IBM\OnDemand\V9.5\jar\rdf2odf.jar;%CLASSPATH%

      4. Using Java 1.7, run the migration utility to export your RDF definitions:

        java com.ibm.cm.od.rdf2odf.MigrateRDF -h source_cmod_hostname -p port -e db_engine -i source_db_name -d output_directory

        Note: Run the command with no parameters for the full command syntax and options.

    3. Import the XML file contents to your OnDemand instance. Take the four files (odfRecipients.xml, odfRecipientsLists.xml, odfReportIDs.xml, and odfDistributions.xml) created in the output directory and use the ARSXML command to import your new ODF definitions:
        1. arsxml add -h instance_name -u userid -p password -e cu -i odfRecipients.xml
        2. arsxml add -h instance_name -u userid -p password -e cu -i odfRecipientsLists.xml
        3. arsxml add -h instance_name -u userid -p password -e cu -i odfReportIDs.xml
        4. arsxml add -h instance_name -u userid -p password -e cu -i odfDistributions.xml

  9. 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).

  10. Start your OnDemand library and object server.

  11. Optional. Uninstall your OnDemand V9.0 software. By default, OnDemand V9.5 will be installed to a different directory than V9.0 and does not automatically uninstall OnDemand V9.0.


Upgrading from V8.5.0.X


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

    Note: The OnDemand server install now also contains and installs the Content Manager OnDemand Web Enablement Kit (ODWEK).

    Note: The OnDemand server does not support OnDemand Clients (e.g. Windows Client, ODWEK, CICS, etc.) prior to V8.5.

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

  2. Download the required OnDemand server software.
    1. Download the V9.5.0.0 full install package from IBM Passport Advantage.
    2. Download your target V9.5.0.X fixpack. For example, V9.5.0.1.
    3. If you have OnDemand Report Distribution installed:
      1. Download the V9.0.0.0 full install package.
      2. Download the V9.0.0.1 fixpack.

  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. If you have OnDemand Report Distribution installed:
      1. Run the V9.0.0.0 installer.
      2. Run the V9.0.0.1 installer.
      3. Run this command to correct Report Distribution folder field to application group field mappings:

        arssyscr -I instance_name -r

      4. Uninstall V9.0.0.1.
    2. Run the V9.5.0.0 installer.
    3. Run your desired target V9.5.0.X fixpack installer.

  5. On Linux and Unix platforms, update the IBM Global Security Kit Crypt and IBM Global Security Kit SSL software for OnDemand V9.5. A newer version is included and required by OnDemand V9.5.
    1. Uninstall your current Global Security Kit Crypt and IBM Global Security Kit software. Refer to the product README for platform specific uninstallation steps.
    2. Install the updated Global Security Kit Crypt and IBM Global Security Kit software. Refer to the product README for platform specific installation steps.

  6. Restore your OnDemand server configuration files (ars.ini, ars.cfg, ars.cache, ars.dbfs, arsload.cfg) and custom user exits to your OnDemand V9.5 directories.

  7. Alter the OnDemand database for use with V9.5.0 by running the following commands on your library server as the OnDemand instance owner specified in the OnDemand Configurator on Windows or the ars.ini on all other platforms.
    1. Mandatory. Drop the OnDemand system table indexes:

      arsdb -I instance_name -efv

    2. Mandatory. Alter the OnDemand database:

      arsdb -I instance_name -uv

    3. Mandatory. Recreate the OnDemand system table indexes:

      arsdb -I instance_name -rfv

    4. Mandatory. 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

    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

  8. Migrate the OnDemand Report Distribution Facility (RDF) definitions to the new OnDemand Distribution Facility (ODF). This step should only be performed if you have the OnDemand Report Distribution Facility installed.

    Note: RDF has been deprecated and replaced with ODF. Although it has been deprecated, RDF is still provided in V9.5 in order for customers to transition to ODF. You can continue to run RDF, however it will no longer exist in any future release of OnDemand, therefore customers are expected to migrate as soon as possible to ODF.
    1. Create the ODF tables and definitions:

      arsdb -I instance_name -Ortv

    2. Convert and export the RDF definitions to XML files:
      1. On AIX and Solaris:

        export CLASSPATH=/opt/IBM/ondemand/V9.5/jar/rdf2odf.jar:${CLASSPATH}

      2. On Linux and Linux for System z:

        export CLASSPATH=/opt/ibm/ondemand/V9.5/jar/rdf2odf.jar:${CLASSPATH}

      3. On Windows:

        set CLASSPATH=C:\Program Files\IBM\OnDemand\V9.5\jar\rdf2odf.jar;%CLASSPATH%

      4. Using Java 1.7, run the migration utility to export your RDF definitions:

        java com.ibm.cm.od.rdf2odf.MigrateRDF -h source_cmod_hostname -p port -e db_engine -i source_db_name -d output_directory

        Note: Run the command with no parameters for the full command syntax and options.

    3. Import the XML file contents to your OnDemand instance. Take the four files (odfRecipients.xml, odfRecipientsLists.xml, odfReportIDs.xml, and odfDistributions.xml) created in the output directory and use the ARSXML command to import your new ODF definitions:
      1. arsxml add -h instance_name -u userid -p password -e cu -i odfRecipients.xml
      2. arsxml add -h instance_name -u userid -p password -e cu -i odfRecipientsLists.xml
      3. arsxml add -h instance_name -u userid -p password -e cu -i odfReportIDs.xml
      4. arsxml add -h instance_name -u userid -p password -e cu -i odfDistributions.xml

  9. 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).

  10. Start your OnDemand library and object server.


How to Uninstall OnDemand Server V9.5.0


To uninstall OnDemand server V9.5.0:
  • On Linux: /opt/ibm/ondemand/V9.5/_uninst950/uninstallod -i console
  • On Windows: Use Programs and Features in the Control Panel
  • All other platforms: /opt/IBM/ondemand/V9.5/_uninst950/uninstallod -i console

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

Miscellaneous


  • To upgrade to OnDemand server V9.5.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

CMOD V9.5 README
What's new in CMOD
CMOD V9.5.0 Publication Library

Document information

More support for: Content Manager OnDemand for Multiplatforms

Software version: 9.5

Operating system(s): Platform Independent

Reference #: 1686051

Modified date: 27 April 2017