Migration process overview: Using new hardware for the database server

Applies to: On premises

You can migrate IBM OpenPages® to the latest 9.2.x release and use new hardware for the database server.

Important: If you use a custom keystore, do the steps in Preparing the encryption keystore before you migrate.

Do the following tasks.

  1. Install the installation server. For more information, see Setting up the installation server on Windows or Setting up the installation server on Linux.
  2. Ensure that the installation server is updated to the latest release and fix pack version. For more information, see Updating the installation server.
  3. Upgrade to a supported version of IBM® Cognos® Analytics. See IBM Cognos Analytics upgrade process.
  4. If you use global search, prepare the search server. See Preparing the search server in the source environment.
  5. Back up your existing OpenPages environment (the source environment). See Backing up your source environment.
  6. Custom helpers that use Apache Tiles do not work in 9.0.0.3 and later versions. If you are upgrading from a release prior to 9.0.0.3, you must make changes to these customer helpers before you install. For more information, see the technote Custom helpers that use Apache Tiles no longer work after upgrading to 9.0.0.3.
  7. Install OpenPages. See Install IBM OpenPages.
    If you are using your existing environment, ensure that it meets the software prerequisites. See Upgrade prerequisite software.
    Note: You must use a new, empty directory for OpenPages.
    If you are using IBM Db2®
    You must use the same database instance name as the database in your source environment.

    Ensure that you complete the database server and OpenPages database setup tasks. See Checklist for the database server (Db2).

    If you are using Oracle
    You can use a pluggable database (PDB) for the OpenPages and Cognos databases. For more information, see Oracle PDB.
    You can use different names for the OpenPages schema and Cognos schema. When you restore the databases from your source environment, you must remap the schema names.
    Note: If you use a different name for the OpenPages schema in the target environment, the change might impact your reports. You might need to do some remediation steps. If your reports contain references to the schema, update the reports to use the new schema name. Out-of-the-box reports are not impacted by this issue because they do not reference the schema name.

    Ensure that you complete the database server and OpenPages database setup tasks. See Checklist for the database server (Oracle).

  8. Restore the OpenPages database from your source environment into the target environment. See one of the following topics:
  9. Upgrade the OpenPages database. See Upgrade the OpenPages database.
  10. Update the database connection information.

    When you restore the database, the connection information from your source environment is imported. You need to update the connection information to use the new database.

    See one of the following topics:
  11. Restore the <OP_HOME>/openpages-storage directory. See Restore the storage directory in the target environment.
  12. Update the URL host pointers for Cognos reports. See Updating URL host pointers for reports.
  13. Migrate files, such as JSPs and other custom deliverables. from the source environment to your upgraded environment. See Migrating files and directories.
  14. Upgrade the application data. See Upgrading application data.
  15. Do the post-migration tasks. See Post migration tasks.
  16. If you use IBM OpenPages solutions, do the post-migration tasks for solutions. See OpenPages solutions post-migration tasks.
  17. Test the deployment.
  18. Review the new and changed features for this release to check whether there is anything that affects your installation after the migration.
Figure 1. Migration process overview: Using new hardware for the database server
A flow diagram of the tasks listed in this topic.