Update database properties for migration

 

+

Search Tips   |   Advanced Search

 

If the earlier portal installation is configured to use a Member Manager lookaside, database, or database federation repository, modify the appropriate property files in...

WP_PROFILE/ConfigEngine/properties

...on the new portal before you run the portal-post-upgrade task to import data.

1. To determine the repository configuration that the earlier portal installation uses...

   previous_wp_root/wmm directory

2. Locate the <repositories> section in wmm.xml.

   If the portal uses a Member Manager lookaside repository, the file defines a lookAsideRepository element. For example:

   <repositories>
     <lookAsideRepository name="wmmDBLookAside"
       UUID="LA"
       supportTransactions="true"
       adapterClassName="com.ibm.ws.wmm.lookaside.db.LookAsideAdapter"
   ...
   

   If the portal uses a Member Manager database repository, the file defines a databaseRepository element. For example:

   <repositories>
   
     <databaseRepository name="wmmDB"
       UUID="DB1"
       supportTransactions="true"
       wmmGenerateExtId="true"
       adapterClassName="com.ibm.ws.wmm.db.DatabaseRepository"
   ...
   

   If the portal uses a Member Manager database federation repository, the file defines a federationRepository element. For example:

   <repositories>
   ...
       <federationRepository name="wmmDBFederation"
          UUID="FD"
          supportTransactions="true"
          adapterClassName="com.ibm.ws.wmm.db.DataBaseFederationAdapter"
          dataSourceName="jdbc/wp60DSwm"
          databaseType="oracle"
          dataAccessManagerClassName="com.ibm.ws.wmm.db.dao.oracle.WMMOracleDao"/>
   

3. If the earlier portal uses a Member Manager lookaside repository, complete these steps on the new portal:

   1. Create a property extension database. Then set the database information in wkplc_dbtype.properties and update the la.* parameters in wkplc.properties.

      Complete only the steps that explain how to install the .ear file for adding properties, set up a new database, define the DbDriver and DbLibrary parameters values, and update the la.* parameters in wkplc.properties.

      You do not need to complete the other steps in the topic.

   2. Set the WMM DB parameters in WmmVmmDBMigration.properties.

      When setting migration.wmm.database.driver.path use the same driver that is used for the V6.1 lookaside or database repository. The driver specified here should match the driver for your database type in wkplc_dbtype.properties.

4. If the earlier portal uses a Member Manager database repository or a Member Manager database federation repository, complete these steps on the new portal:

   1. Create a database user registry to store user account information. Then set the database information in wkplc_dbtype.properties and update the federated.db.* parameters in the wkplc.properties file.

      For example complete only the steps that explain how to set up a new database, define the DbDriver and DbLibrary parameters values, and update the federated.db.* parameters in wkplc.properties.

      You may also need to update federated.db.DbSchema, which is located in the Advanced Properties section of wkplc.properties.

      This parameter defines the VMM Federated DB domain database schema name, and is set, by default, to federate. You do not need to complete the other steps in the topic.

   2. Set the WMM DB parameters in WmmVmmDBMigration.properties.

      When setting migration.wmm.database.driver.path use the same driver that is used for the V6.1 lookaside or database repository. The driver specified here should match the driver for your database type in wkplc_dbtype.properties.

If the portal uses both a Member Manager Lookaside repository and a Member Manager federated repository (or database repository) update the la.* parameters and the federated.db.* parameters to use the same configuration values. You cannot split the locations of the VMM DB tables across database types.

 

Parent topic

Migrating to a remote machine

 

Previous topic:

Exporting configuration for migration to a remote machine

Next topic:

Import configuration for migration to a remote machine