+

Search Tips   |   Advanced Search

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.

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

Guidelines for using this administrative console page:


Pause

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.


Resume

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

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.


Running object scope

Server running the connection factory or data source MBean.


Status

State of the connection factory or data source Bean.

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 Bean in this state.

  • Manage resources through JCA lifecycle management operations
  • Administrative console scope settings
  • Administrative console buttons
  • Administrative console page features