Software AG Products 10.7 | Integrating On-Premises and Cloud Applications | Accessing databases | Configuring Access to Database Systems | Identifying Database Aliases
 
Identifying Database Aliases
Identify a database alias to specify the connection information that the server must supply to connect to a database. Set up aliases if:
*You want developers to be able to define database flow services using the webMethods Integration Server Administrator.
*You want to maintain all database connection parameters in one place to allow for easier maintenance. For example, you can easily update the information if a password changes or a database moves.
To better manage requests for database connections, you can specify that the server use database connection pools. With database connection pools in effect, the Integration Server controls the number of database connections it makes to a database, preventing the database from exceeding its connection limit and rejecting requests. If a request exceeds a database connection pool’s limit, the server blocks it and tries the connection request again later.
See Enabling Database Connection Pooling for more information about how database connection pools work and how to set them up.
Note:
Before you configure a database alias, make sure the WmDB package is enabled. For information about enabling packages, see webMethods Integration Server Administrator’s Guide.
*To identify a database alias
1. Open the Integration Server Administrator if it is not already open.
2. Go to Adapters > WmDB > Alias Management.
3. Click Add. The server displays the New DB Alias page.
4. Set the new alias parameters as follows:
For this parameter...
Specify...
Alias
The alias name that you want to use for the database. You can specify any combination of letters, numbers, and the underscore character for an alias name; there is no restriction on the number or of characters you can specify.
DB URL
The URL for the database. For example: jdbc:odbc:Support.
DB Username
The user name that the server must supply to log on to the specified database. If a user name and password are not required, leave this field blank.
DB Password
The password that the server must supply to log on to the selected database. If a user name and password are not required, leave this field blank.
DB Driver
The name of the Java class for the JDBC driver.
If the server has any drivers currently loaded, the server displays a Loaded Drivers field that has a drop down list containing the drivers that are loaded. If you select a driver from the list, the server places the driver name in the DB Driver field.
If you do not specify a driver, the server uses the default driver specified in the watt.server.jdbc.defaultDriver parameter in the server.cnf file.
To see the value of the default driver, use the Settings > Extended page from the Integration Server Administrator as described in webMethods Integration Server Administrator’s Guide.
Important:
Be sure the server has access to the Java classes for the driver. For more information about making the Java classes available, see Making the Java Classes for JDBC Drivers Accessible.
If you are using the Oracle JRE on a Windows platform, the server has access to the Java classes for the JDBC-ODBC bridge driver named sun.jdbc.odbc.JdbcOdbcDriver.
Minimum Connections
The minimum number of connections to maintain in the database connection pool. The server creates these connections when it first receives a request to connect to the database. If more connections are needed, the server creates additional connections until the value for Maximum Connections, described below, is reached.
The default is 0.
Note:
This field displays only if the server is configured for database connection pooling (that is, if the watt.server.db.connectionCache property in the server.cnf file is set to server).
See Enabling Database Connection Pooling for more information.
Maximum Connections
The maximum number of connections to maintain in the database connection pool. When the number of connection requests reaches this value, the server blocks the requests.
The default is 1.
Note:
This field displays only if the server is configured for database connection pooling (that is, if the watt.server.db.connectionCache property in the server.cnf file is set to server).
See Enabling Database Connection Pooling for more information.
Expiration Time (ms)
The amount of time the server waits before discarding an inactive connection from the database connection pool. The server only discards connections if the pool contains more than the minimum number of connections. Afterwards, if more connections are needed than exist in the pool, the server creates new ones.
The default expiration time is 60000 milliseconds.
Note:
This field displays only if the server is configured for database connection pooling (that is, if the watt.server.db.connectionCache property in the server.cnf file is set to server).
See Enabling Database Connection Pooling for more information.
5. Click Submit.