Migrating the DBB server
If you are upgrading the DBB server from a previous release, the configuration from the old server must be merged into the new server configuration and the database must be migrated before starting the new server.
Procedure
-
Stop the DBB server:
wlp/bin/server stop dbb
-
Rename the current DBB server directory:
mv wlp wlp.old
-
Install the new version of the DBB server:
tar -zxvf dbb-server-<release>.tar.gz
-
Review the server configuration changes that were made to the original installation. Changes can include ports and user registry customizations and database configurations.
Note: Database and user registry configurations in 1.0.x are in or included inserver.xml
. Starting in 1.1.x, the database and user registry configuration is located inwlp/usr/servers/dbb/configDropins/overrides
. If you migrate from 1.0.x to 1.1.x, either remove the configuration files inoverrides
or move the configurations fromserver.xml
to the respective file inoverrrides
.Make sure that the following server configuration changes were made:
- The
jdbcdriver
anddatasource
tags must have been copied from the oldserver.xml
file to the newdatabaseConfig.xml
file. - The
ADMIN
user ID must have been replaced in the newserver.xml
file with theweb.admin
ID from thedbb.properties
file. - The content of the
dbb.properties
file must have been copied from the old configuration to the newdbb.properties
file. - The Lightweight Directory Access Protoco (LDAP) must have been configured again, based on the information from the old
server.xml
andldapUserRegistry.xml
.
- The
-
Merge the configuration changes into the new installation.
-
Back up the current database by following established and verified procedures for your database. For example, for distributed Db2, use the backup command to backup your database.
-
Run the appropriate upgrade script located in
/wlp/usr/servers/dbb/DDL
. For example, for distributed Db2:
db2 connect to DBB; db2 -stvf /path/to/install/wlp/usr/servers/dbb/DDL/upgrade_DB2_1.1.1.sql; db2 disconnect DBB
Notes:- Not every version has its corresponding upgrade script. Check directory
/wlp/usr/servers/dbb/DDL
for all the available upgrade scripts. - You must run all the upgrade scripts, if they exist, between your currently installed version up to and including the target version.
- The database must be in sync with the code. Therefore, failure to run all the upgrade scripts that apply will cause the server to terminate with an error that specifies which table is out of sync.
- Not every version has its corresponding upgrade script. Check directory
-
Review the output and verify that all the database commands run successfully.
-
If it is necessary to roll back changes to the database, restore the database from the backup. For distributed Db2, use the restore command to restore the backup to the database.
-
Start the DBB server:
wlp/bin/server start dbb