Administration Console

Back Next

JDBC Identity Service

If you select a Provider Type of JDBC, the Connection tab is as follows:

In your identity service, be sure to map the Process Central security role,

abTaskClient

, to each user that will login to Process Central.

View and update identity service settings as shown in the table below.

Before enabling a JDBC datasource for the identity service ensure the prerequisites are met:

A database is configured for use with JDBC identity service

A connection pool resource is configured in your application server

The database driver exists in the c

ommon/lib

(or similar) directory

Note
: Tomcat users must manually configure the JNDI

DataSource

in the Process Server context file.

If desired you can import and export your JDBC configuration.

Enter the provider-specific connection settings used to establish connectivity to your identity store.

Provider Configuration
Enable	Add a checkmark to use the identity service. Initially the service is disabled since it is not configured and ready for use. Configure the remaining settings, and then enable the service.
Provider Type	Select JDBC from the drop-down list:
DataSource JNDI Name	The resource must be assigned a JNDI name for location at run-time. For example, java:comp/env/jdbc/IdentityTest
Database Type	Choose database type from picklist. Choose Other to use generic settings
Username	(Optional). An application server may require credentials for a JNDI context; that is, credentials for doing a lookup on the JNDI tree. Your application server may require credentials for looking up a connection pool for access to the identity service. In this case, you must provide the user name and password. For a local data source, you can leave this field blank. Note that the user name for the JNDI context is not the same as the user name for the data source itself. The data source username must be set on the connection pool resource.
Password	(Optional) Password associated with Username