How to change the URL attribute from the Identity Governance data source
Article ID: 247694
Updated On:
Products
Issue/Introduction
The current string configured in the standalone XML file is for Oracle dedicated server, below are the steps to change it to point to a Load Balance.
You can use this article to change the JDBC URL to another database (Oracle or SQL Server).
Environment
Virtual Appliance 14.x
Resolution
For Virtual Appliance 14.4 version:
- You can change the data source information from the Virtual Appliance dashboard.
For Virtual Appliance 14.3 version:
Note: Before performing the steps below, please, do a backup of the "/opt/CA/wildfly-ig/standalone/configuration/standalone-full-ha-ca-gm.xml" file
Below are the steps to change the connection URL for all data sources from Identity Governance:
If you do not have the user configured to connect to JBoss CLI, please see the steps in the "How to add user to JBoss-CLI" section, if you already have the user, proceed with the steps below:
To the eurekifyDS, eurekifyReportdbDS, and eurekifyTmsDS data source follow the steps below:
- From vApp, go to the "/opt/CA/wildfly-ig/bin" folder and run the "./jboss-cli.sh" command to open JBoss CLI
- Type connect and enter the user and password
- After that, enter the three lines above, one by one.
/subsystem=datasources/data-source=eurekifyDS/:write-attribute(name=connection-url,value=<The-New-Value>)
/subsystem=datasources/data-source=eurekifyReportdbDS/:write-attribute(name=connection-url,value=<The-New-Value>)
/subsystem=datasources/data-source=eurekifyTmsDS/:write-attribute(name=connection-url,value=<The-New-Value>)
Where:
<The-New-Value> = the new JDBC URL
You will receive a message like that after each command.
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
- To disconnect, run the "exit" command
- To confirm you can check the /opt/CA/wildfly-ig/standalone/configuration/standalone-full-ha-ca-gm.xml
- Restart the Identity Governance service
Note:
Depending on the string you are trying to add, the string can not be inserted totally, only a part of it, in this case, put the string between double-quotes, for example:
"jdbc:oracle:thin:@(description=(address_list=(address=(protocol=tcp)(host=<ora01-scan>)(port=1521))(address=(protocol=tcp)(host=<ora02-scan>)(port=1521)))(failover=on)(load_balance=off)(connect_data=(server=dedicated)(service_name=<oracle service name>)))"
To the XA data sources, WPDS, WPDS2, and WPDS3 follow the steps below:
- From vApp, go to the "/opt/CA/wildfly-ig/bin" folder and run the "./jboss-cli.sh" command to open JBoss CLI
- Type connect and enter the user and password
- After that change the directory to the data source you want to change, below the command for WPDS. To WPDS2 and WPDS3, just change the data source name in the command below
cd /subsystem=datasources/xa-data-source=WPDS/xa-datasource-properties=URL
- Run ls to check the current URL value
value=jdbc:oracle:thin:@database_srv:1521/xe
- Run the command below to remove the current value, we need to remove it because the URL value is read-only
Note: Do NOT copy the ":remove()" command below to avoid an error while trying to remove
:remove()
{
"outcome" => "success",
"response-headers" => {"process-state" => "reload-required"}
}
- After removing, run the command below the add the new value
:add(value="<The-New-Value>")
{
"outcome" => "success",
"response-headers" => {
"operation-requires-reload" => true,
"process-state" => "reload-required"
}
}
- Run the exit command to terminate the JBoss-CLI session
- Restart the Identity Governance service to the change take effect.
You can compare the backup of the old standalone-full-ha-ca-gm.xml with the "/opt/CA/wildfly-ig/standalone/configuration/standalone-full-ha-ca-gm.xml"
How to add a user to JBoss-CLI
Note: the user "<username>" below is just an example, you can use any name for the user
> /opt/CA/wildfly-ig/bin > sudo /opt/CA/wildfly-ig/bin/add-user.sh
What type of user do you wish to add?
a) Management User (mgmt-users.properties)
b) Application User (application-users.properties)
(a): a
Enter the details of the new user to add.
Using realm 'ManagementRealm' as discovered from the existing property files.
Username: <username>
Password recommendations are listed below. To modify these restrictions edit the add-user.properties configuration file.
- The password should not be one of the following restricted values {root, admin, administrator}
- The password should contain at least 8 characters, 1 alphabetic character(s), 1 digit(s), 1 non-alphanumeric symbol(s)
- The password should be different from the username
Password :
JBAS015267: Password must have at least 1 non-alphanumeric symbol.
Are you sure you want to use the password entered yes/no? yes
Re-enter Password :
What groups do you want this user to belong to? (Please enter a comma-separated list, or leave blank for none)[ ]:
About to add user '<username>' for realm 'ManagementRealm'
Is this correct yes/no? yes
Added user '<username>' to file '/opt/CA/wildfly-ig/standalone/configuration/mgmt-users.properties'
Added user '<username>' to file '/opt/CA/wildfly-ig/domain/configuration/mgmt-users.properties'
Added user '<username>' with groups to file '/opt/CA/wildfly-ig/standalone/configuration/mgmt-groups.properties'
Added user '<username>' with groups to file '/opt/CA/wildfly-ig/domain/configuration/mgmt-groups.properties'
Is this new user going to be used for one AS process to connect to another AS process?
e.g. for a slave host controller connecting to the master or for a Remoting connection for server to server EJB calls.
yes/no? no
Now you have the user associated with the Management Realm.
Feedback
