Passing client information to a database

Using a WAS API or trace function, you can pass unique client information on every connection that originates from the same data source.

 

About this task

Some databases, such as DB2, support a data source custom property that triggers your database servers to extract client information from WAS connections. (Consult the database documentation to see whether your product supports this capability and which property the product requires.) Be aware, however, that these properties introduce a very limited functionality in Application Server. Consequently, an application server connection manager incurs the following risky behaviors, which can result in the transfer of wrong client information to the database.

Application Server offers two methods of passing client information that provide the necessary connection management flexibility. Using either method, we can set client information on some connections and not others, as well as set different client information on different database connections from the same data source.

 

Procedure

 

Results

 

Example

See Example: Setting client information with the setClientInformation(Properties) API .

 

See also


Example: Setting client information with the setClientInformation(Properties) API
Implicitly set client information
Setting client information traces with the administrative console