File name: udat_jcalifecycle.html
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:
- For connection factories: Click . Select the connection factory
configurations that you want to manage, and click Manage
state.
- For data sources, click . 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 MBeans that correspond to the data
sources or connection factories in your selection from the previous
console page. These MBeans are compatible with Version 6.0.2 and later
of the application server.
- You 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 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.
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 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.
|
|
