Adding and Configuring WebLogic Server Data Sources

When you run the TMS Installer, it sets up a connection or data source, which is used by TMS Reports generation, from the WebLogic Server to the default database.

If you plan to use more than one database, you must create a data source for each additional database.

Note:

In addition, you must modify tnsnames.ora at <ORACLE_HOME>\network\admin and <ORACLE_HOME>\user_projects\domains\FRDomain\config\fmwconfig. Ensure that it contains an entry for each database.

It is recommended to maintain a master tnsnames.ora file and copy it to each location—database and application servers— whenever you add a database.

For more information, see:

• Add Data Sources
  
• Change Data Source Account Password
  
• Configure Maximum Connections
  
• Configure Inactive Connection Timeout
  

Add Data Sources

Go through these instructions for one data source at a time.

1. Log in to the WebLogic Server Administration Console at:

   http://host:7101/console/login/LoginForm.jsp
   

2. Select Services > Data Sources > Lock & Edit to enable the New button, then select New > Generic Data Source.
3. Enter a name for the data source.
4. Enter the JNDI name as:

   • For TMS: jdbc/tmsdatabase_nameDS

   Note:

   For TMS Reports generation add the new JNDI name in the REPORTS_CONFIG local reference codelist, JDBC_DATA_SRC setting.

5. On the next screen:

   • If the database you want to connect to is a RAC database, choose Oracle's Driver (Thin) for RAC Service-Instance connections; Versions: Any

   • If the database is not a RAC database, choose Oracle's Driver (Thin) for Service connections; Versions: Any

6. On the next screen, deselect Supports Global Transactions.
7. On the next screen, enter the database name, host name, and port for the database. For the user, enter tmsproxy and the password for the account.
8. On the next screen, select Test Configuration to validate if you can connect using the pool setup.
9. On the next screen, assign opa_cluster - All servers in the cluster as the target.
10. Click Finish.
11. Select the newly created Data Source, click the Connection Pool tab, and then click Advanced.
12. Uncheck Wrap Data Types and save.
13. Review and set additional parameters in Advanced Settings as appropriate for your expected data load.
14. Activate your changes and restart managed server <server_name>_opa_1 for the changes to take effect.

Change Data Source Account Password

After changing the password for tmsproxy account on the database, you need to update the password of the account on the data source of the WebLogic too.

1. Log in to the WebLogic Server Administration Console at:

   http://host:7101/console/login/LoginForm.jsp
   

2. Select Services, Data Sources, and then select the data source whose password you want to modify.

3. Select the Connection Pool tab, and click Lock & Edit.

4. Scroll down to find the password field and enter the new password.

5. Re-enter the password in the Confirm Password field.

6. Save.

7. Activate your changes.

You must then restart the OPA Server:

1. In the same OPA domain WebLogic Server Administration Console, click on Servers, then the Control tab.
2. Select managed server <server_name>_OPA_1, and then Shutdown - Force Shutdown now.
3. Click Refresh to ensure the State changes to Shutdown.
4. Select managed server <server_name>_OPA_1, and then Start.
5. Click Refresh to see the State change to Running.

Configure Maximum Connections

By default, the value for the Maximum Capacity parameter for each data source, which determines the maximum number of concurrent connections, is 15.

The value for the Maximum Capacity parameter should be equal to or greater than the maximum number of concurrent users you expect for TMS Reports.

To change this value:

1. Log in to the WebLogic Server Administration Console at:

   http://host:7101/console/login/LoginForm.jsp
   

2. Select Services, Data Sources, then select the data source whose setting you want to modify. For example, DS_1_tms for TMS or DS_1_ops for OPA (TMS reports).

3. Click the Connection Pool tab, and then click Lock & Edit.

4. Scroll down to find the parameter Maximum Capacity.

5. Enter a value as described above.

6. Save.

7. Activate your changes.

You must then restart the OPA Server:

1. In the same OPA domain WLS Administration Console, click on Servers, then the Control tab.
2. Select the managed server <server_name>_OPA_1, and then Shutdown - Force Shutdown now.
3. Click Refresh to ensure the State changes to Shutdown.
4. Select the managed server <server_name>_OPA_1, and then Start.
5. Click Refresh to see the State change to Running.

Configure Inactive Connection Timeout

To ensure that a connection is available for a user who needs to run a report, change the default setting of the Inactive Connection Timeout of 0 to 5 or a similar value. This is the number of seconds of inactivity that is allowed before the connection is made available to another user. If set to zero, the feature is disabled.

To change this value:

1. Log in to the OPA domain WebLogic Server Administration Console at:

   http://host:7101/console/login/LoginForm.jsp
   

2. Select Data Sources, then select the data source whose setting you want to modify.

3. Click the Connection Pool tab, and then click Lock & Edit.

4. Scroll down to find the parameter Inactive Connection Timeout.

5. Enter a value; for example, 5.

6. Save.

7. Activate your changes.

You must then restart the OPA Server:

1. In the same OPA domain WLS Administration Console, click on Servers, then the Control tab.
2. Select the managed server <server_name>_OPA_1, and then Shutdown - Force Shutdown now.
3. Click Refresh to ensure the State changes to Shutdown.
4. Select the managed server <server_name>_OPA_1, and then Start.
5. Click Refresh to see the State change to Running.