Configuring a Database Connection 

Use

To connect the J2EE Engine to a particular database, you need to set the properties of the Configuration Manager. Use this procedure to configure the connection that the Configuration Manager establishes to the RDBMS you choose.

Prerequisites

To connect to the RDBMS, you need to have:

·        An installed JDBC driver for the database

·        A running database, which is initialized with the proper tables that Configuration Manager uses.

Procedure

Using the Config Tool offline, you can edit the properties of the Configuration Manager before you start the J2EE Engine.

You can also change the properties of a running J2EE Engine, using the Properties tab of the Configuration Manager in the Visual Administrator. The changes take effect after you restart the cluster element.

To configure the connections to the RDBMS, set the following properties:

·        secstorefs.keyfile

·        secstorefs.lib

·        secstorefs.secfile

·        system.name

·        rdbms.initial_connections

·        rdbms.maximum_connections

The rdbms.maximum_connections property defines how many connections can be established to the database at a time. These connections are used by the Configuration Manager to access the underlying database. If you set a small number of connections such as one, some of the services will have to wait for an idle database connection while accessing the Configuration Manager. This will negatively affect the performance.

For more information about these properties, see Configuration Manager properties in the Reference Manual. You have to change them on both the server and dispatcher elements to connect the cluster elements to the same database. Server and dispatcher nodes do not need the same number of initial and maximum connections, but they must access the same database.

Result

The next time you start the J2EE Engine, the Configuration Manager connects to the specified database and stores the persistent information there.