
Resource Management Commands
TABLE | (Continued) | |
Command | Definition |
|
|
| |
Removes a custom resource. | ||
|
| |
Lists the custom resources. | ||
|
| |
Adds a new connector connection pool with the specified connection | ||
| pool name. |
|
|
| |
Removes the connector connection pool specified using the operand | ||
| connector_connection_pool_name. | |
|
| |
Lists the connector connection pools that have been created. | ||
|
| |
Registers the connector resource with the specified JNDI name. | ||
|
| |
Removes the connector resource with the specified JNDI name. | ||
|
| |
Gets all the connector resources. | ||
|
| |
Creates the administered object that has a specified JNDI name. | ||
|
| |
Removes the administered object with the specified JNDI name. | ||
|
| |
Lists all the administered objects. | ||
|
| |
Creates configuration information for the connector module. | ||
|
| |
Deletes the configuration information created in domain.xml for the | ||
| connector module. | |
|
| |
lists the configuration information in the domain.xml for the | ||
| connector module | |
|
| |
Creates the resources named in the specified XML file. The | ||
| xml_file_pathis the path to the XML file containing the resources to | |
| be created. The DOCTYPE should be specified as | |
| ||
| resources.xml file. | |
|
| |
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.
242 | Sun GlassFish Enterprise Server 2.1 Administration Guide • December 2008 |