E
dit
A
ttach
P
rintable
r7 - 2023-04-17 - 15:37:02 -
SusanWu
You are here:
TWiki
>
Deployment Web
>
DeploymentMigratingAndEvolving
>
MigratingYourJazzAuthorizationServerFromDerbyToAnEnterpriseDatabase
<div id="header-title" style="padding: 10px 15px; border-width:1px; border-style:solid; border-color:#FFD28C; background-image: url(<nop>https://jazz.net/wiki/pub/Deployment/WebPreferences/TLASE.jpg); background-size: cover; font-size:120%"> ---+!! Migrating Your Jazz Authorization Server From Derby To An Enterprise Database <img src="https://jazz.net/wiki/pub/Deployment/WebPreferences/uc.png" alt="uc.png" width="50" height="50" align="right"> %DKGRAY% Authors: Main.DavidNoecker, Main.MirkoHartwig <br> Build basis: Jazz Authorization Server 6.0.x+ %ENDCOLOR%</div></sticky> <!-- Page contents top of page on right hand side in box --> <sticky><div style="float:right; border-width:1px; border-style:solid; border-color:#DFDFDF; background-color:#F6F6F6; margin:0 0 15px 15px; padding: 0 15px 0 15px;"> %TOC{title="Page contents"}% </div></sticky> <sticky><div style="margin:15px;"></sticky> ---++ 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: [[https://jazz.net/jazz/resource/itemName/com.ibm.team.workitem.WorkItem/463705][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.). <br> 1. On JTS export JTS *.json file with <verbatim>./repotools-jts.sh -prepareJsaSsoMigration adminUserId=<your Admin User> adminPassword=<your Admin Password> repositoryURL=https://[public-url]:[port]/jts toFile=JTS_output.json </verbatim> 2. Repeat on all other Applications, such as CCM, for example: <verbatim>./repotools-ccm.sh -prepareJsaSsoMigration adminUserId=<your Admin User> adminPassword=<your Admin Password> repositoryURL=https://[public-url]:[port]/ccm toFile=CCM_output.json </verbatim> 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, base on your DB choice, follow the "Setting up a Jazz Authorization Server DB instruction under the following Database Setup pages: Db2: https://www.ibm.com/docs/en/elms/elm/7.0.2?topic=database-setting-up-db2 <br> Oracle: https://www.ibm.com/docs/en/elms/elm/7.0.2?topic=database-setting-up-oracle <br> SQL Server DB: https://www.ibm.com/docs/en/elms/elm/7.0.2?topic=database-setting-up-sql-server 4. Start JAS and test your configuration as described in this link: https://www.ibm.com/docs/en/elm/7.0.3?topic=server-deploying-starting-jazz-authorization 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 <verbatim> ./repotools-jts.sh -migrateToJsaSso authServerUrl=https://[jas-url]:9643/oidc/endpoint/jazzop authServerUserId=<your Admin User> authServerPassword=<your Admin Password> jtsSsoDataFile=JTS_output.json </verbatim> 7. Then migrate all other application using as example fo CCM: <verbatim>./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</verbatim> 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: [[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][Deploying and starting Jazz Authorization Server]], [[PerformanceClusteredJAS][Setting up a cluster of Jazz Authorization Servers]] ---+++++!! External links: * [[https://www.ibm.com][IBM]] ---+++++!! Additional contributors: Main.ShubjitNaik, Main.PaulEllis, Main.TobiasBurkhardt <sticky></div></sticky>
E
dit
|
A
ttach
|
P
rintable
|
V
iew topic
|
Backlinks:
We
b
,
A
l
l Webs
|
H
istory
: r7
<
r6
<
r5
<
r4
<
r3
|
M
ore topic actions
Deployment
Deployment web
Planning and design
Installing and upgrading
Migrating and evolving
Integrating
Administering
Monitoring
Troubleshooting
Community information and contribution guidelines
Create new topic
Topic list
Search
Advanced search
Notify
RSS
Atom
Changes
Statistics
Web preferences
NOTE: Please use the Sandbox web for testing
Status icon key:
To do
Under construction
New
Updated
Constant change
None - stable page
Smaller versions of status icons for inline text:
Copyright © by IBM and non-IBM contributing authors. All material on this collaboration platform is the property of the contributing authors.
Contributions are governed by our
Terms of Use.
Please read the following
disclaimer
.
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more
here
.