Hi Webspherians
I want to share with you the basic steps of migration of derby/cloudscape
database of websphere portal server into standard databases as Oracle or DB2.
1: Setting up Databases:
Followings are the 7 internal databases of Websphere Portal.
- release
- customization
- community
- jcr
- feedback
- likeminds
- wmm
We need to create these 7 databases in the intended
DB.(DB2/Oracle) by following script:
db2 "CREATE DB dbname using codeset UTF-8 territory us COLLATE USING UCA400_NO PAGESIZE 8192"
db2 "UPDATE DB CFG FOR dbname USING applheapsz 2048"
db2 "UPDATE DB CFG FOR dbname USING app_ctl_heap_sz 1024"
db2 "UPDATE DB CFG FOR dbname USING stmtheap 8192"
db2 "UPDATE DB CFG FOR dbname USING dbheap 2400"
db2 "UPDATE DB CFG FOR dbname USING locklist 1000"
db2 "UPDATE DB CFG FOR dbname USING logfilsiz 1000"
db2 "UPDATE DB CFG FOR dbname USING logprimary 12"
db2 "UPDATE DB CFG FOR dbname USING logsecond 20"
db2 "UPDATE DB CFG FOR dbname USING logbufsz 32"
db2 "UPDATE DB CFG FOR dbname USING avg_appls 5"
db2 "UPDATE DB CFG FOR dbname USING locktimeout 30"
db2 "UPDATE DB CFG FOR dbname using AUTO_MAINT off"
replace dbname with RELEASE,JCR...etc
On DB2 client machine, run the following commands to
catalogue the databases.
db2 "catalog db remote_db_name_release as release_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_community as comm_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_customization as cust_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_fdbkdb as fdbkdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_lmdb as lmdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_jcrdb as jcrdb_alias_name at node remote_db_node_alias"
db2 "catalog db remote_db_name_wmmdb as wmmdb_alias_name at node remote_db_node_alias"
2. Updating properties file: Update following
properties files as per our databases.
wpconfig_dbdomain.properties
wpconfig_dbtype.properties
wpconfig.properties
wpconfig_sourceDb.properties
3. Validating properties files: Run the following commands to validate entries of configuration properties
done in previous step.
(These commands are for Unix plateform)
./WPSconfig.sh validate-database-connection-wps -Drelease.DbPassword=password -Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password
./WPSconfig.sh validate-database-connection-jcr -Djcr.DbPassword=password
./WPSconfig.sh validate-database-connection-feedback -Dfeedback.DbPassword=password
./WPSconfig.sh validate-database-connection-likeminds -Dlikeminds.DbPassword=password
./WPSconfig.sh validate-database-connection-wmm -Dwmm.DbPassword=password
./WPSconfig.sh validate-database-driver
Check the output of each command.
4. Stop the Servers: Stop Websphere portal as well as application server by following
commands:
- ./stopServer.sh
WebSphere_Portal -user username -password password
- ./stopServer.sh server1
-user username -password password
5. Transfer the database: To transfer the database, perform this step:
- Change to
the directory portal_server_root/config.
- Enter the
following commands to run the configuration task.
./WPSconfig.sh database-transfer -Drelease.DbPassword=password-Dcustomization.DbPassword=password -Dcommunity.DbPassword=password -Djcr.DbPassword=password -Dwmm.DbPassword=password -Dfeedback.DbPassword=password -Dlikeminds.DbPassword=password
check the output of the command.
Successful outcome of above command insures that Database transafer is
successful.
6. Start Servers: Start Websphere portal as well as
application server by following commands:
- ./startServer.sh
WebSphere_Portal
- ./startServer.sh server1
Now you can Login to the Websphere portal and start
exploring it more!
Cheers!
Pragati