Migrating Your Jazz Authorization Server From Derby To An Enterprise Database

How to migrate your database from Derby to another COTS (Common Off The Shelf) database

Procedure for preparing for, then migrating the applications to use the new database vendor

Additional background details to follow. For now, this procedure has been tested internally and at multiple client sites. Also see: Documentation on Jazz Authorization Server DB configuration missing in Knowledge Centre which will address how to setup Jazz Authorisation Server.

A non-clustered JAS installation may want to use an enterprise database. The enterprise DB setup instructions are in the clustered JAS wiki topic because a clustered JAS absolutely requires an enterprise database. A non-clustered deployment may consider using one for various reasons (e.g. ability to manage using existing IT staff/infrastructure), but the requirements for the JAS DB are not extensive (it hardly grows at all; performance is not critical; etc.).

1. On JTS export JTS *.json file with

./repotools-jts.sh -prepareJsaSsoMigration adminUserId=<your Admin User> adminPassword=<your Admin Password> repositoryURL=https://[public-url]:[port]/jts  toFile=JTS_output.json 

2. Repeat on all other Applications, such as CCM, for example:

./repotools-ccm.sh -prepareJsaSsoMigration adminUserId=<your Admin User> adminPassword=<your Admin Password> repositoryURL=https://[public-url]:[port]/ccmtoFile=CCM_output.json 

Attention: please check twice when you create *.json files for all existing applications (use the corresponding repotools-xxx.sh for each application)

3. Stop JAS and move to your DB choice described with this link: https://jazz.net/wiki/bin/view/Deployment/PerformanceClusteredJAS

4. Start JAS and test your configuration as described in this link: https://jazz.net/help-dev/clm/index.jsp?re=1&topic=/com.ibm.jazz.install.doc/topics/c_jsasso_jas_deploy_start.html&scope=null

5. Stop all applications JTS, CCM, RM, QM etc.”. This step is necessary as if the applications are running you can not execute the migration command.

6. Migrate created *.json files starting with JTS using

 ./repotools-jts.sh -migrateToJsaSso authServerUrl=https://[jas-url]:9643/oidc/endpoint/jazzop authServerUserId=<your Admin User> authServerPassword=<your Admin Password> 
jtsSsoDataFile=JTS_output.json 

./repotools-ccm.sh -migrateToJsaSso authServerUrl=https://[jas-url]:9643/oidc/endpoint/jazzop authServerUserId=<your Admin User> authServerPassword=<your Admin Password> 
jtsSsoDataFile=JTS_output.json appSsoDataFile=CCM_output.json

8. After migration, startup all Application beginning with JTS

9. Test availability of all Application after startup

Attention: please be aware that LDX/LQE/JRS may not be available so please try to unregister and reregister these applications after your Test step 9.)

Related topics: Deploying and starting Jazz Authorization Server, Setting up a cluster of Jazz Authorization Servers

External links:

• IBM

Additional contributors: ShubjitNaik, PaulEllis, TobiasBurkhardt