Network Deployment (Distributed operating systems), v8.0 > Reference > Sets

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, you can control the runtime status of the corresponding data source and connection factory resources.

We can view this admin console page in different locations, depending on whether to manage data sources or J2C connection factories. For example:

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

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

Guidelines for using this admin console page:

• The table displays a list of MBeans that correspond to the data sources or connection factories in your selection from the previous console page. These MBeans are compatible with v6.0.2 and later of the application server.
• We can only perform JCA life cycle management actions on MBeans that are in the active state. In this context, an MBean is considered active when an application performs a JNDI name space lookup on the corresponding data source or connection factory resource.
• Pause 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.

Pause

Specifies to pause the MBean that is selected. Pausing an MBean halts outbound communication to the back-end resource, and this action affects all applications that use the resource on the selected server.

For transitioning users: When an application attempts a connection to a paused data source, the connection manager raises an SQLException with an error code of com.ibm.websphere.rsadapter.WSDataSource.ERROR_CONNECTION_POOL_IS_PAUSED.trns

Resume

Specifies to resume the MBean that is selected. Resuming an MBean enables outbound communication to the back-end resource. This action affects all applications that use the resource on the selected server.

Purge

Specifies to purge the contents of the connection pool for the data source or connection factory specified. Purging the pool does not affect ongoing transactions.

Name (JNDI name)

Name of the connection factory or data source configuration, followed by the JNDI name in parenthesis.

Run object scope

Server that is running the connection factory or data source MBean.

Status

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. We can apply the JCA life cycle 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 life cycle management operation that was applied previously to the MBean. An application performed a JNDI namespace lookup on the resource. We can apply the JCA life cycle 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. We cannot apply JCA life cycle management operations to an MBean in this state.

Manage resources through JCA lifecycle management operations

Related

Administrative console scope settings
Administrative console buttons
Administrative console page features

+

Search Tips   |   Advanced Search