Database form
|
03-02 R-5246 GENTJ Complete this tab to specify database connection information.
After you complete and save the form, you can click Test Connection to confirm database connectivity.
Field |
Description |
||||||||||||||
Database | |||||||||||||||
How to Connect |
Select one of three choices.
The
Process Commander may open more than one connection to a database. When using WebSphere's pooled connection facility, a general guideline for production systems is to set the maximum number of connections for the PegaRULES database to about one-third to one-fifth of the number of simultaneous requestors (and adjust the PegaRULES database settings to allow the same number of connections. SR-1415 Don't forget to count listeners and agents as requestors. SR-4475 The Use configuration in preferences caseFor example, connection to a Microsoft SQL Server database
can be defined in the <env
name="database/databases/Northwind/url" In this example, the database name is Northwind and the user name (account) is Smith with password password. The database is located on the server SHELPNT using TCP/IP port 1433. Process Commander may open more than one database connection with this user name. To provide good performance, the system creates a pool of connections over time. (This internal connection pooling is an alternative to facilities provided by WebSphere or WebLogic.).
The
Account and password securityIf you choose If you choose |
||||||||||||||
JDBC Definition | |||||||||||||||
JDBC URL |
03-02 This field appears only when you select
Enter the full URL. Examples for Microsoft, Oracle, IBM DB2 and Sybase databases are: B-20065 SR-3432
where 127.0.0.1 is the node name or IP address of the server hosting the database, and 1433 or 1521 is the TCP/IP port number for database access. Precise syntax requirements vary depending on server platform, database version, and JDBC client; additional parameters may be required. Consult your database administrator (DBA) for details. If this Data-Admin-DB-Name instance is to connect to the PegaRULES database, consult the Installation Guide for your platform. If your PegaRULES database is hosted by Oracle 9, the Type 2 (OCI or thick client) driver is required; the thin client (Type 4) works with Oracle 10g. HAASC 3/16/07 Sybase databases are accessible only through Connect SQL rules. Sybase is not supported as a host for the PegaRULES database B-3245. Don't place any spaces or other extraneous characters before or after the JDBC URL value. B-5736 |
||||||||||||||
JDBC Datasource | |||||||||||||||
JNDI Name |
C-1592 This field appears only when you select
Enter the name of the JNDI server defining a connection pool. The procedure for defining a connection pool depends on two factors:
If during installation of Process Commander, the
installer specified a JDBC Datasource for connecting to the
PegaRULES database, the username and password for that data
source may appear in the |
||||||||||||||
Admin JNDI Name |
Optional. Leave blank unless (1) this database name instance is to access the PegaRULES database using JNDI, (2) the primary database user account does not have the ALTER TABLE and CREATE TABLE capabilities, and you want developers to have any of these capabilities:
Identify a JNDI name that defines PegaRULES database connection for which the account has the ALTER TABLE and CREATE TABLE capabilities. (This ordinarily is distinct from database account used by most application users, who only insert, update, and delete rows). Consult the Installation Guide (for your platform) for additional information on this field. Alternatively, you can specify the username and password in
the |
||||||||||||||
Authentication | |||||||||||||||
Username |
Optional. Enter the user or account name for this database, if required. Use a database user that is capable of accepting unqualified table names and converting them to fully qualified table names. If this database is to be accessed through Connect SQL rules (Rule-Connect-SQL rule type), confirm that this database user has search, update, delete, and other capabilities that support the SQL statements in those rules, and that this database is the default database of the user. B-3276 |
||||||||||||||
Password |
Optional. If the database account requires a password, enter
the password. If this field is blank, the system expects to
obtain a password from a text file named
|
||||||||||||||
Admin Username |
Optional. The Admin User Name and Admin Password field provide an alternative way to specify a PegaRULES database account for specific capabilities. Optional. Leave blank unless (1) this database name instance is to access the PegaRULES database using JNDI, (2) the primary database user account does not have the ALTER TABLE and CREATE TABLE capabilities, and you want developers to have any of these capabilities:
Identify a PegaRULES database account (referenced by the
Admin JNDI Name field) that has the ALTER TABLE
and CREATE TABLE capabilities. (This account ordinarily is
distinct from database account used by most application users,
who only insert, update, and delete rows). Alternatively,
you can specify the username and password in the
|
||||||||||||||
Admin Password |
Optional. Leave blank unless you have supplied an Admin Username value. 5.4 Enter a password for the database account identified in the Admin Username field. |
||||||||||||||
Test Connection | |||||||||||||||
Test Connection |
After you complete and save the form, click to test connectivity to the database. If the test fails, diagnostic information appears in a new window. (This test does not try the alternate account to the PegaRULES database, if any, specified in the Admin Username and Admin Password fields). See Pega Developer Network article PRKB-21078 Troubleshooting JDBC problems with tools from Pegasystems and others for advice on researching JDBC issues. |