ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Change external DB in vApp

book

Article ID: 111743

calendar_today

Updated On:

Products

CA Identity Manager CA Identity Governance CA Identity Portal

Issue/Introduction

We had to change our SQL databases used by the Identity Suite vApp to another SQL server.
We now need to update the vApp so all relevant deployments (Identity Manager / Identity Governance / Identity Portal) reference and utilize the new DB

Environment

Identity Suite 14.x

Resolution

As of Identity Suite 14.2 vApp CP2 as well as Identity Suite 14.3 CP2, changes to the external DB details do not require a redeployment - as per the official documentation
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/identity-suite/14-2/virtual-appliance/Change-the-Password-of-Identity-Suite-Components.html#concept.dita_6599601b-9f72-4020-924e-461f4ce8109c_ChangeDatabasePassword

and
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/layer7-identity-and-access-management/identity-suite/14-3/virtual-appliance/Change-the-Password-of-Identity-Suite-Components.html#concept.dita_6599601b-9f72-4020-924e-461f4ce8109c_ChangeDatabasePassword

For older releases, the following procedure is valid.
As a prerequisite, all the data should be manually migrated from the old DB to the new DB for all deployed applications.
Once done:

1. Login to the vApp Dashboard
2. Choose Setup from the top left Menu
3. Edit DB details and reference the new DB server
4. Redeploy with the updated details

Additional Information

Important note:
DB details should be updated / re-entered for all applications, even if the change is only applicable for one specific application and not the others.
When choosing "Skip" for any other application DB details (as no update is required for current connection information), then vApp will ignore monitoring those "Skipped" applications.
It has been designed in such a way that one needs to mention details of all DBs for all services which are deployed, regardless of whether they require a change in the DB details.
Skipping any section will make vApp assume that the DB has been removed and will will no longer be monitoring the DB, even though applications are deployed.