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.

You can view this administrative console page in different locations, depending on whether you want to manage data sources or J2C connection factories. For example:
Guidelines for using this administrative console page:

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 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 that is specified. Purging the pool does not affect ongoing transactions.

Name (JNDI name)

Specifies 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

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

Status

Specifies 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 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.

You 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.

You cannot apply JCA life cycle management operations to an MBean in this state.




Related tasks
Managing resources through JCA lifecycle management operations
Related reference
Administrative console scope settings
Administrative console buttons
Administrative console page features
Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Jan 30, 2014 9:17:32 AM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-iseries&topic=jcalifecycle
File name: udat_jcalifecycle.html