The resource commands allow you to manage the various resources used in your application.
Table C–7 Resource Management Commands
Command |
Definition |
---|---|
create-jdbc-connection-pool |
Registers a new JDBC connection pool with the specified JDBC connection pool name. |
delete-jdbc-connection-pool |
Deletes a JDBC connection pool. The operand identifies the JDBC connection pool to be deleted. |
list-jdbc-connection-pools |
Gets the JDBC connection pools that have been created. |
create-jdbc-resource |
Creates a new JDBC resource. |
delete-jdbc-resource |
Removes a JDBC resource with the specified JNDI name. |
list-jdbc-resources |
Displays a list of JDBC resources that have been created. |
create-jms-resource |
Creates a Java Message Service (JMS) connection factory resource or a JMS destination resource. |
delete-jms-resource |
Removes the specified JMS resource. |
list-jms-resources |
Lists the existing JMS resources (destination and connection factory resources). |
create-jndi-resource |
Registers a JNDI resource. |
delete-jndi-resource |
Removes the JNDI resource with the specified JNDI name. |
list-jndi-resources |
Identifies all the existing JNDI resources. |
list-jndi-entries |
Browses and queries the JNDI tree. |
create-javamail-resource |
Creates a JavaMail session resource. |
delete-javamail-resource |
Removes the specified JavaMail session resource. |
list-javamail-resources |
Lists the existing JavaMail session resources. |
create-persistence-resource |
Registers a persistence resource. |
delete-persistence-resource |
Removes a persistence resource. When you delete a persistence resource, the command also removes the JDBC resource if it was created using the create-persistence-resource command. |
list-persistence-resources |
Displays all the persistence resources. |
create-custom-resource |
Creates a custom resource. A custom resource specifies a custom server-wide resource object factory that implements the javax.naming.spi.ObjectFactory interface. |
delete-custom-resource |
Removes a custom resource. |
list-custom-resources |
Lists the custom resources. |
create-connector-connection-pool |
Adds a new connector connection pool with the specified connection pool name. |
delete-connector-connection-pool |
Removes the connector connection pool specified using the operand connector_connection_pool_name. |
list-connector-connection-pools |
Lists the connector connection pools that have been created. |
create-connector-resource |
Registers the connector resource with the specified JNDI name. |
delete-connector-resource |
Removes the connector resource with the specified JNDI name. |
list-connector-resources |
Gets all the connector resources. |
create-admin-object |
Creates the administered object that has a specified JNDI name. |
delete-admin-object |
Removes the administered object with the specified JNDI name. |
list-admin-objects |
Lists all the administered objects. |
create-resource-adapter-config |
Creates configuration information for the connector module. |
delete-resource-adapter-config |
Deletes the configuration information created in domain.xml for the connector module. |
list-resource-adapter-configs |
lists the configuration information in the domain.xml for the connector module |
add-resources |
Creates the resources named in the specified XML file. The xml_file_path is the path to the XML file containing the resources to be created. The DOCTYPE should be specified as install_dir/lib/dtds/sun-resources_1_2.dtd in the resources.xml file. |
ping-connection-pool |
tests if a connection pool is usable for both JDBC connection pools and connector connection pools. For example, if you create a new JDBC connection pool for an application that is expected to be deployed later, the JDBC pool is tested with this command before deploying the application. Before pinging a connection pool, you must create the connection pool with authentication and ensure that the enterprise server or database is started. |