+

Search Tips   |   Advanced Search

Portal, V6.1

 

Sharing JCR domain data

To migrate from IBM WebSphere Portal V6.0.1.1 or V6.0.1.3, connect to a copy of the earlier portal's JCR database domain before running the migration tasks.

If the new portal installation uses the same DBMS as the earlier portal, use the same database driver to connect to the copy of the earlier portal's JCR database domain. For example, if you configured the new portal's release domain to use DB2 with a DB2 Type 4 driver, and the earlier portal's JCR database domain also uses DB2, use a DB2 Type 4 driver to connect to the copy of the earlier portal's JCR database domain. If the new portal uses Oracle for the release domain and the earlier portal's JCR database domain uses a different DBMS such as DB2, you do not need to use the same database driver to connect to the copy of the earlier portal's JCR domain.

The entire set of database properties specified in the file WP_PROFILE/ConfigEngine/properties/wkplc.properties must be valid for the current configuration of all database domains. If you plan to connect or transfer a single database domain, you should modify only the database properties for that domain before running the connect-database or database-transfer tasks.

  1. Create a separate copy of the earlier WebSphere Portal JCR domain.

  2. On the new portal, locate and update the files listed below to reflect a connection to the JCR domain copy that you created in the previous step:

    • WP_PROFILE/ConfigEngine/properties/wkplc.properties

    • WP_PROFILE/ConfigEngine/properties/wkplc_comp.properties

    • WP_PROFILE/ConfigEngine/properties/wkplc_dbtype.properties

    Use the earlier portal installation's properties files as a reference to determine the appropriate values.

  3. Change to the WP_PROFILE/ConfigEngine directory and then enter the following commands to validate the configuration properties:

    Operating System Command
    Windows

    ConfigEngine.bat validate-database-driver -DTransferDomainList=jcr
    ConfigEngine.bat validate-database-connection -DTransferDomainList=jcr

    UNIX

    ./ConfigEngine.sh validate-database-driver -DTransferDomainList=jcr
    ./ConfigEngine.sh validate-database-connection -DTransferDomainList=jcr

    i5/OS

    ConfigEngine.sh validate-database-driver -DTransferDomainList=jcr
    ConfigEngine.sh validate-database-connection -DTransferDomainList=jcr

  4. Connect WebSphere Portal V6.1 to the copy of the earlier JCR domain:

    Operating System Command
    Windows ConfigEngine.bat connect-database-jcr-migration
    UNIX ./ConfigEngine.sh connect-database-jcr-migration
    i5/OS ConfigEngine.sh connect-database-jcr-migration

  5. If you are migrating WCM also run the following task:

    Operating System Command
    Windows ConfigEngine.bat create-wcm-persistence-tables
    UNIX ./ConfigEngine.sh create-wcm-persistence-tables
    i5/OS ConfigEngine.sh create-wcm-persistence-tables

  6. Verify that the new portal server starts.

 

Parent topic

Preparing for migration

 

Related tasks


Migrating V6.0.x personalization data