JCA lifecycle management

Use this page to perform JCA lifecycle management operations on data source and connection factory MBeans. With these management operations, you can control the runtime status of the corresponding data source and connection factory resources. You can view this administrative console page in two locations, depending on the type of resource that you want to manage:

• For connection factories: Click Resources > Resource adapters > Resource_adapter > J2C connection factories. Select the connection factory configurations that you want to manage, and click Manage state .

• For data sources: Click Resources > JDBC Providers > JDBC_provider > Data sources . Select the data source configurations that you want to manage, and click Manage state .

Guidelines for using this administrative console page:

• The table displays a list of Version 6.0.2-compatible MBeans that is correspond to the data sources or connection factories in your selection from the previous console page.

• You can only perform JCA lifecycle management actions on MBeans that are in the active state. In this context, an MBean is considered active when an application performs a Java Naming and Directory Interface (JNDI) name space lookup on the corresponding data source or connection factory resource.

• Pausing an MBean halts outbound communication to the backend, such as a database. This action affects all applications that use the resource on the selected server.

Table column heading descriptions:

Name (JNDI name)

The name of the connection factory or data source configuration, followed by the Java Naming and Directory Interface (JNDI) name in parenthesis.

Running object scope

The server that is running the connection factory or data source MBean.

Status

The state of the connection factory or data source MBean.

Possible values:

State	Indications
ACTIVE	The resource that corresponds with the MBean is ready to provide an application with connections to a backend. An application performed a JNDI namespace lookup on this resource. You can apply the JCA lifecycle management operation of PAUSE to an MBean in this state.
PAUSED	All outbound communication to the backend through the corresponding resource is stopped, as a result of a JCA lifecycle management operation that was applied previously to the MBean. An application performed a JNDI namespace lookup on the resource. You can apply the JCA lifecycle management operation of RESUME to an MBean in this state.
NOT_ACCESSED	The MBean exists on the specified server, but no applications performed a JNDI name space lookup on the corresponding connection factory or data source. You cannot apply JCA lifecycle management operations to an MBean in this state.