Manage resources through JCA lifecycle management operations

We can manage the run-time status of our data source and connection factory resources to perform some data access administrative tasks without restarting the application server. This topic outlines the process for managing those resources through the administrative console.

When we manage the run-time status of connection factories or data sources, we are applying Java EE Connector Architecture (JCA) lifecycle management operations to the Beans associated with these resources. The management operations are PAUSE and RESUME. Pausing an MBean halts outbound communication to the backend, such as a database. This action affects all applications that use the corresponding connection factory or data source on the same server.

With these management operations, we can perform some administrative tasks dynamically, without restarting the application server:

• Respond to a security threat, and prevent new connection requests from reaching the backend

• Perform maintenance on the backend
• Apply configuration changes to non-required properties of the connection factory or data source, such as turning JDBC trace on or off, or modifying preferences for collecting client information

Tasks

1. Navigate to the administrative console page that corresponds to the resource type to manage.

   • For connection factories, use either of the following paths:
     • Resources > Resource Adapters > J2C connection factories
     • Resources > Resource Adapters > Resource Adapters > resource_adapter > J2C connection factories

   • For data sources, use either of the following paths:
     • Resources > JDBC > Data sources
     • Resources > JDBC > JDBC providers > JDBC_provider > Data sources

2. Select the connection factory or data source configurations to manage, and click Manage state. The administrative console now displays the JCA lifecycle management page, which contains a table that depicts the full scope configuration of our previous selection.

   The table is comprised of three columns:

   • JNDI name: The JNDI name of the connection factory or data source configuration.
   • Run object scope: The server running the connection factory or data source MBean.
   • Status: The status of the connection factory or data source Bean.

3. Select the rows that represent each invocation of the resource, per running server, to manage. Be aware that when you click your management operation, WebSphere Application Server applies it to every resource object in your selection.

   Restriction: If the MBean status of a row has a value of NOT_ACCESSED, we cannot apply JCA lifecycle management operations to that MBean. The NOT_ACCESSED state indicates that the MBean exists on the specified server, but no applications performed a JNDI namespace lookup on the corresponding connection factory or data source.

4. Click Pause or Resume. The status column of the table changes to reflect the new state of the Bean.

Subtopics

• JCA life cycle management
  Use this page to perform JCA life cycle management operations on data source and connection factory MBeans. With these management operations, we can control the runtime status of the corresponding data source and connection factory resources.
• JCA life cycle management
  Use this page to perform JCA life cycle management operations on data source and connection factory MBeans. With these management operations, we can control the runtime status of the corresponding data source and connection factory resources.