Customizing your RDBMS server

About this task

You can perform several operations to customize your database, such as:

Upgrading the JDBC drivers. For more information, see How can I customize the JDBC drivers for the database?
Changing the instance owner, by editing the db.user property in the datasource_<db_vendor>.xml file. For more information, see Changing the properties for the database.
Relocating the DB to the another host by editing the db.serverName property in the datasource_<db_vendor>.xml file. For more information, see Changing the properties for the database.
Changing the database port, database name, or database access credentials by editing the db.portNumber, db.databaseName, db.user, and db.password properties in the datasource_<db_vendor>.xml file. For more information, see Changing the properties for the database.

If you want to upgrade your database version, change the instance owner, or relocate it to a different host, complete the following steps:

If you are changing DB2®, check the node directory and database directory and make a note of the current configuration. To do this, issue the following commands at the DB2® command-line:
```
db2 list database directory
```
where the show detail attribute is specified to give the full information in the directory.
Make a note of the displayed details.
Stop the application server, using the command
```
conman stopappserver ;wait
```
Make the upgrade, instance owner change, or relocation, of the database following the instructions from your database supplier.
If you have changed the database access credentials, you will need to update the application server's security properties, as described in Changing the security settings.
Reconfigure the database for HCL Workload Automation, as follows:
DB2®
1. Check the node directory and database directory, as you did in step 1
2. If necessary, modify the data displayed by these commands to match the data you noted in step 1. If you are not certain of how to do this, contact HCL Software Support for assistance.
Oracle

Check the Oracle Listener and make sure that the service name is correctly specified.
Restart the database.
Restart the application server, using the command:
```
conman startappserver ;wait
```