5.12 How to Change the Configuration Options for the Databases

Identity Governance allows you to change some of the configuration options for the databases that you define during the installation. The options that you can change are:

JDBC driver for the database
URL of the database
Database names
Password for the databases

Identity Governance stores this information in multiple locations. You must update this information in all of the locations to have Identity Governance see the changes. Use the following information to update the database configuration information in Identity Governance.

5.12.1 Updating the Identity Governance Configuration Update Utility for the Database Changes

The database changes must be updated in the properties file of the Identity Governance Configuration Update utility. You must edit the properties file to update the database changes.

Make the appropriate corresponding changes in the main database (igops) on the database server for the:
- JDBC driver for the database
- URL of the database
- Database name
- Password for the database
Log in to the server running Identity Governance as an administrative user.
Stop Apache Tomcat. For more information, see Section 3.4.3, Starting and Stopping Apache Tomcat.
Open the properties file for the Identity Governance Configuration Update utility in a text editor. The default location is:
- Linux: /opt/netiq/idm/apps/configupdate/configupdate.sh.propteries
- Windows: c:\netiq\idm\apps\configupdate\configupdate.bat.properties
Make the appropriate changes to the following parameters:

dbDriver

Specify the name of the new JDBC driver. You would change this if you were adding a patched driver.

dbURL

Specify the updated URL and port to access the database.

dbUser

Specify the new name for the database.

dbPassword

Specify the new password for the database.
(Conditional) You do not want to have the password set in clear text.
1. Encode the password by running the following script:
  - Linux: /opt/netiq/idm/apps/idgov/bin/encode-password.sh password
  - Windows: c:\netiq\idm\apps\idgov\bin\encode-password.sh password
2. Copy the new value and replace the value in the dbPassword property.
Save and close the file.
Restart Apache Tomcat on the Identity Governance server. For more information, see Section 3.4.3, Starting and Stopping Apache Tomcat.

5.12.2 Updating the Identity Governance Configuration Utility for the Database Changes

You must edit the Identity Governance Configuration utility to update the database changes.

Make the appropriate corresponding changes in the main database (igops) on the database server for the:
- JDCB driver for the database
- URL of the database
- Database name
Log in to the server running Identity Governance as an administrative user.
Open the Identity Governance Configuration utility in a text editor. The default location is:
- Linux: /opt/netiq/idm/apps/idgov/bin/configutil.sh
- Windows: c:\netiq\idm\apps\idgov\bin\configutil.bat
Make the appropriate changes to the following parameters:

_db_driver

Specify the name of the new JDBC driver. You would change this if you had a patched version of the driver.

_db_url

Specify the updated URL and port to access the database.

_db_user

Specify the new name for the database or encode the password.
Save and close the file.

5.12.3 Updating the Identity Governance Database Initialization File for the Database Changes

You must edit the Identity Governance database initialization file to make Identity Governance aware of what changes you made to the database in case you ever have to reinitialize the schema. For more information, see Section 11.2, Manually Generating the Database Schema after the Installation.

To change the database information in the database initialization file:

Make the appropriate corresponding changes in the main database (igops) on the database server for the:
- JDCB driver for the database
- URL of the database
- Database name
Edit the database initialization file to change the database names or the URL and port for the database server.
1. Access the databased initialization file. The default location is:
  - Linux: /opt/netiq/idm/apps/idgov/bin/db-init.sh
  - Windows: c:\netiq\idm\apps\idgov\bin\db-init.bat
2. Open the database initialization file in a text editor.
3. Change the following entries in the file for your database:
  Database name
  
  Change each entry that lists a database name. Change the following entries:
  
  _db_name_ops=
  
  _db_name_arc=
  
  _db_name_dcs=
  
  _db_name_wf=
  
  _db_name_ara=
  
  Database URL
  
  Specify the URL and port for your database for each of the following lines:
  
  _db_url_ops=
  
  _db_url_arc=
  
  _db_url_dcs=
  
  _db_url_wf=
  
  _db_url_ara=
  
  Database Driver
  
  Specify the new JDBC JAR file in the following entry: _dc_jdbc_jar=
Save and close the file.

5.12.4 Updating the Apache Tomcat sever.xml File

You must update the server.xml file for the Apache Tomcat instance that you use for Identity Governance.

Make the appropriate corresponding changes in the database for the:
- JDCB driver for the database
- URL of the database
- Database names
- Password for the databases
Log in to the server running Identity Governance as an administrative user.
Stop Apache Tomcat. For more information, see Section 3.4.3, Starting and Stopping Apache Tomcat.
Open the Apache Tomcat server.xml file for Identity Governance in a text editor. The default location is:
- Linux: /opt/netiq/idm/apps/tomcat/server.xml
- Windows: c:\netiq\idm\apps\tomcat\server.xml
Make the appropriate changes to the following parameters:

username

Specify the name of the database names in the username= entries.

url

Specify the updated URL and port to access the database for the url= entries.
(Conditional) You do not want to have the password set in clear text.
1. Encode the password by running the following script:
  - Linux: /opt/netiq/idm/apps/idgov/bin/encode-password.sh password
  - Windows: c:\netiq\idm\apps\idgov\bin\encode-password.sh password
2. Copy the new value and replace the value in the password field.
Save and close the file.
Start Apache Tomcat. For more information, see Section 3.4.3, Starting and Stopping Apache Tomcat.