IBM BPM, V8.0.1, All platforms > Authoring services in Integration Designer > Services and service-related functions > Access external services with adapters > Configure and using adapters > IBM WebSphere Adapters > JDBC > Plan for adapter implementation

Enabling IBM WebSphere Adapter for JDBC to connect to a new schema at run time

You can dynamically connect to a new schema when moving from one environment to another, by enabling IBM WebSphere Adapter for JDBC to pick up the database schema name for tables, views, and synonyms at run time.

You can change the database schema name based on your environment using the TableNameEnv property. To use this property, you must specify the environment variable name during the enterprise metadata discovery (EMD). The environment variable value contains the schema name. The adapter picks up the schema name at run time from the value of the environment variable.

The run time must contain the defined variable before the application is deployed. The value of the environment variable name contains the new schema name.

The TableNameEnv ASI, which is created during the metadata discovery is used by the adapter at run time. The business object ASI stores the environment variable specified in the EMD. The adapter checks for this variable in the environment variables of WebSphere Application Server or IBM Process Server during runtime. If the variable name is not found during run time, the adapter proceeds with the old schema name.

You must create an environment variable with the same name as provided in the EMD. You can use the environment variable to specify the target schema name.

The following are the important points to be taken care to connect to a new schema:

To enable the adapter to pick up the database schema name for tables, views, and synonyms at run time, see the below topics:

Plan for adapter implementation