Update database properties for migration
If the earlier portal installation is configured to use...
- Member Manager lookaside
- database
- 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.
Procedure
- Determine the repository configuration that the earlier portal installation uses. Open...
earlier_portal_wp_root/wmm/wmm.xml...and 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" ... <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"/>- If the earlier portal uses a Member Manager lookaside repository...
- create a property extension database.
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
- Update the la.* parameters in wkplc.properties
You do not need to complete the other steps in the topic.
- Set the WMM DB parameters in WmmVmmDBMigration.properties.
For migration.wmm.database.driver.path, use the same driver used for the V6.1 lookaside or database repository. The driver should match the driver for your database type in wkplc_dbtype.properties.
- If the earlier portal uses...
- Member Manager database repository
- Member Manager database federation repository
...complete these steps on the new portal...
- Create a database user registry to store user account information.
Define DbDriver and DbLibrary in wkplc_dbtype.properties
- Update federated.db.* parameters in wkplc.properties.
- You may also need to update federated.db.DbSchema, 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.
- Set the WMM DB parameters in the WmmVmmDBMigration.properties file.
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...
- Member Manager Lookaside repository
- 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 the same machine
Previous topic:
Exporting configuration for migration to the same machineNext topic:
Import configuration for migration to the same machine