<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 <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]/ccmtoFile=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 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.) 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> 6.) 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> 7.) After migration, startup all Application beginning with JTS 8.) Test availability of all Application after start up 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>
This topic: Deployment
>
WebHome
>
DeploymentMigratingAndEvolving
>
MigratingYourJazzAuthorizationServerFromDerbyToAnEnterpriseDatabase
History: r2 - 2018-08-20 - 12:24:41 -
PaulEllis
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
.