39.5 Changing the Default Context Name for User Application

Instead of using the default context name, you can create a new context based on your organizational requirements. You can change the context name in the console or in the GUI by performing the following actions:

Stop the Tomcat service.
```
/etc/init.d/idmapps_tomcat_init stop
```
Navigate to the User Application directory located in /opt/netiq/idm/apps/UserApplication.
Launch the configupdate utility in GUI mode.

Ensure that the use_console option is set to false in configupdate.sh.properties or configupdate.bat.properties file.

Alternatively, launch the configupdate utility and pass an additional command line argument on Linux.

./configupdate.sh use_console=false
In the User Application tab, click Show Advanced Options and perform the following steps:
1. Select Change RBPM Context Name.
2. Specify the custom context name in RBPM Context Name. For example, IDMProvCustom.
3. Browse to and select the Roles Driver DN. For example, cn=Role and Resource Service Driver,cn=Driver Set,o=system.
4. Click OK.
Verify that the war file is renamed.
- Navigate to /opt/netiq/idm/apps/tomcat/webapps and check if IDMProvCustom.war entry is updated.
- Navigate to ism-configuration properties file located in /TOMCAT_INSTALLED_HOME/conf and check if portal.context entry specifies the new context name.

Update your database with the new context name by using the update-context.sh script located in /opt/netiq/idm/apps/UserApplication.

Execute the following command to run the update-context.sh script.

ua:/opt/netiq/idm/apps/UserApplication # vi update-context.sh

You should see the following entries on your screen:

# copy and paste or execute this script before changing context name

# Substitute your new context where indicated

/opt/netiq/idm/apps/jre/bin/java -Xms256m -Xmx256m  -Dwar.context.name=[New Context Here] -Ddriver.dn=[UA Driver DN] -jar /opt/netiq/idm/apps/UserApplication/liquibase.jar --databaseClass=liquibase.database.core.PostgresDatabase  --driver=org.postgresql.Driver  --classpath=/opt/netiq/idm/apps/postgres/postgresql-9.4.1212.jdbc42.jar:/opt/netiq/idm/apps/tomcat/webapps/IDMProv.war --changeLogFile=UpdateProducerId.xml   --url="jdbc:postgresql://localhost:5432/idmuserappdb?compatible=true" --contexts="prov,updatedb" --logLevel=debug --username=******** --password=******** update

For example, run the following script if you are using a PostgreSQL database:

/opt/netiq/idm/apps/jre/bin/java -Xms256m -Xmx256m  -Dwar.context.name=IDMProvCustom  -Ddriver.dn= cn=Role and Resource Service Driver,cn=driverset1,o=system -jar /opt/netiq/idm/apps/UserApplication/liquibase.jar --databaseClass=liquibase.database.core.PostgresDatabase  --driver=org.postgresql.Driver  --classpath=/opt/netiq/idm/apps/postgres/postgresql-9.4.1212.jdbc42.jar:/opt/netiq/idm/apps/tomcat/webapps/IDMProv.war --changeLogFile=UpdateProducerId.xml   --url="jdbc:postgresql://<Database Server:5432/idmuserappdb?compatible=true" --contexts="prov,updatedb" --logLevel=debug -–username=dbadmin --password=******** update

where

-Dwar.context.name=IDMProvCustom specifies the new context.

-Ddriver.dn ="cn=User Application Driver,cn=driverset1,o=system" specifies the User Application driver DN.

--username=dbadmin specifies the database administrator username that can create database tables, views, and other artifacts.

IMPORTANT:Do not change the database driver details in the script for other supported databases.

Verify that the database tables have the new context name.

Table Name	Column to Check
PORTALPRODUCERS	producerid
PORTALPRODUCERREGISTRY	producerid
PORTALREGISTRY	producerid
PORTALPORTLETSETTINGS	producerid
PORTALPORTLETHANDLES	producerid
PROFILEGROUPPREFERENCES	elementid

For example, run the following SQL command to verify the new context name in the PORTALPRODUCERS table:

Select * from PORTALPRODUCERS;

The command should return only the new context name.

Start the Tomcat service.
```
/etc/init.d/idmapps_tomcat_init start
```