+

Search Tips   |   Advanced Search

Portal V7.0 stand-alone: Use copies of source database domains to minimize downtime


The recommended way to keep the earlier portal environment in production and reduce the amount of downtime during migration is to copy the earlier portal server JCR and Release domains. Then update the new portal server using the domain copies. The process of connecting to the domain copies must be done after you upgrade the ConfigEngine tool but before you upgrade the Portal profile.

  1. Use the Database tools to copy the source portal JCR domain and Release domain.

    For IBM DB2 Universal Databaseā„¢ for z/OS:

    • To use the DB2 Administration Tool to copy the database domains, make sure APAR PM16847 is applied.

    • Make sure that you verify the databases are not in a COPY PENDING state before you connect to the database copies described in the following step.

  2. DB2 only: On the database copies, verify the Statement Heap size is set to at least 32k.

    1. List the database manager configuration parameters by running the following command db2 get db cfg for dbname.

    2. If the Statement Heap size is smaller than 32k, increase it by running the following commanddb2 "UPDATE DB CFG FOR dbname USING stmtheap 32768"

  3. On the target portal, update wkplc_dbdomain.properties located in...

      WP_PROFILE/ConfigEngine/properties

    1. Update the jcr.* and release.* database properties to point to the JCR and Release domain copies that you created in the previous step.

    If the source portal uses the default Apache Derby database, the migration tools automatically copy the database for you. However, if you have modified or customized the default Derby database, you must copy the entire Derby directory to a new directory. Then update all database properties to point to the copy of the Derby database. Ensure that derby.DBLibrary is set to use the WAS v7 derby.jar as the JDBC driver class and includes the directory location of the file.

    For example: derby.DBLibrary=WAS7_root\derby\lib\derby.jar

  4. When migrating with coexistence, that is both source and target environments are running on the same machine, change the WAS and WebSphere Portal port numbers. You must change ports before connecting to the domain copies. For details on changing ports, see the Related section for performing platform-specific, post-installation steps.


Parent: Portal V7.0 stand-alone: Migrating databases
Related:
Standalone: Post-installation tasks
Standalone: Perform post-installation tasks on IBM i
Standalone: Perform post-installation tasks on Linux
Standalone: Perform post-installation tasks on Solaris
Standalone: Perform post-installation tasks on Windows