Using setdbparms utility to update the db.properties file.

Products

• DSERIES- SERVER
• CA Workload Automation DE - System Agent (dSeries)

Issue/Introduction

Question:  

If the database connection properties change after you install the server, can you modify the properties on the server to continue connecting to the database?

Answer: 

 

Yes, to modify the database connection properties, use the setdbparm utility that is installed with the server.

Note: If CA WA High Availability is configured, complete these steps on both Primary and Standby servers. Before you modify these properties, ensure that you coordinate these changes with your database administrator.

Follow these steps:

1. Log in to the computer where the server is installed.
2. Change to the following directory at the command prompt:
   • On Windows:

     install_dir\bin

   • On UNIX:

     install_dir/bin

   install_dir

   Specifies the directory where the server is installed.

3. Enter the following command:
   • On Windows:

     setdbparm.bat property

   • On UNIX:

     setdbparm property

   property

   Specifies the database property that you want to modify. Options are as follows:

   database.maxconnections.in.pool

   Specifies the maximum number of simultaneously open database connections available in the connection pool. The server first requests an open connection from the pool. If all of the connections in the pool have been allocated, the server waits until another connection is available before allocating the connection. When the connection is no longer needed, the server returns the connection to the pool.

   Default: 50

   Note: The server no longer allows connections to be created outside the connection pool.

   database.minconnection

   Specifies the number of database connections in the connection pool when the server starts. Based on demand, the server adds new connections to the connection pool, up to the maximum specified by the database.maxconnections.in.pool property.

   Default: 3

   integratedSecurity

   (Microsoft SQL Server databases only) Indicates whether the CA Workload Automation DE server uses Windows authentication or SQL Server authentication to connect to the database. If this property is set to true, the server uses Windows authentication; otherwise, it uses SQL Server authentication.

   javax.net.ssl.trustStore

   Specifies the full path to the trust store file, including the trust store filename. The trust store stores all certificates CA Workload Automation DE requires.

   javax.net.ssl.trustStorePassword

   Specifies the password for accessing the trust store file.

   jdbc.Driver

   Specifies the name of the JDBC driver that the server uses to access the database.

   jdbc.URL

   Specifies the database URL.

   Example: jdbc:oracle:thin:@11.2.1.12:1234:APPS

   rdbms.password

   Specifies the database user's password that the server uses to access the database.

   Note: If the password for the CA Workload Automation DE database and the password for the database user do not match, the server cannot connect to the database.

   rdbms.type

   Specifies the type of relational database that the server uses.

   Limits: Oracle, Microsoft SQL Server, IBM DB2

   rdbms.userid

   Specifies the user ID that the server uses to access the database.

   relational.database.retry.attempts

   Specifies the number of times that the server tries to connect to the database.

   relational.database.retry.interval

   Specifies the frequency in seconds in which the server tries to connect to the database.

   Default: 60 seconds

   You are prompted for a property value.

4. Enter the new value for the database property that you want to modify.
5. Repeat steps 3 and 4 for each connection property that you want to modify.
6. Restart the server.

   The database connection properties are modified.

 

 

Additional Information:

If you see the warning message 'Out of DB connections' in the tracelog check with your dba about increasing the number of allowed connections. As the number of jobs and applications increase the server will require more connections to the database for timely updates.
 
We use the setdbparm command to make changes (the setdbparm is in bin directory)
 
Here is an example of running the setdbparm:
 ./setdbparm database.maxconnections.in.pool
 Changing max connections in pool (database.maxconnections.in.pool)
 Enter new max connections in pool:500  (change this higher number)
 Verify new max connections in pool:500
 Changed.
 
The Server must be restarted for the change to take effect.
 

 

Environment

Release: WKLOEB01300-11.3-Workload Automation-Agent for Oracle EBusiness Ste
Component: