asadmin-ping-connection-pool, ping-connection-pool - tests that a connection pool is usable
ping-connection-pool --user admin_user [--password admin_password] [--host localhost] [--port 4848]
[--secure|-s] [--passwordfile filename] [--terse=false] [--echo=false] [--interactive=true] pool_name
Tests that 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 use with an application that is expected to be deployed,
before deploying the application, the previously created pool is tested with this command.
This command is supported in remote mode only.
--user authorized domain application server administrative username.
--password password to administer the domain application server.
--host machine name where the domain application server is running.
--port port number of the domain application server listening for administration requests.
--secure if true, uses SSL/TLS to communicate with the domain application server.
--passwordfile file containing the domain application server password.
--terse indicates that any output data must be very concise, typically avoiding human-friendly
sentences and favoring well-formatted data for consumption by a script. Default is
--echo setting to true will echo the command line statement on the standard output. Default
--interactive if set to true (default), only the required password options are prompted.
poolname name of the connection pool to be tested.
Example 1: Using ping-connection-pool
Before you can ping a connection pool, you must:
o Create a connection pool with authentication.
o Make sure the Enterprise Information Server (can be the database) is started.
asadmin> ping-connection-pool --user admin1 --password adminadmin1
--host pigeon --port 5001 sampleConnectionPool
Command ping-connection-pool executed successfully