1. Overview of Enterprise Server Administration
Default Settings and Locations
Instructions for Administering Enterprise Server
4. Administering the Virtual Machine for the Java Platform
6. Administering Web Applications
7. Administering the Logging Service
8. Administering the Monitoring Service
9. Administering Life Cycle Modules
10. Extending Enterprise Server
Part II Security Administration
11. Administering System Security
12. Administering User Security
13. Administering Message Security
Part III Resources and Services Administration
14. Administering Database Connectivity
15. Administering EIS Connectivity
Administering Connector Connection Pools
To Create a Connector Connection Pool
To List Connector Connection Pools
To Connect to (Ping) or Reset (Flush) a Connector Connection Pool
Administering Connector Resources
To Create a Connector Resource
To Update a Connector Resource
To Delete a Connector Resource
Administering the Resource Adapter Configuration
To Create Configuration Information for a Resource Adapter
To List Resource Adapter Configurations
To Update a Resource Adapter Configuration
To Delete a Resource Adapter Configuration
Administering Connector Security Maps
To Create a Connector Security Map
To List Connector Security Maps
To Update a Connector Security Map
To Delete a Connector Security Map
Administering Connector Work Security Maps
To Create a Connector Work Security Map
To List Connector Work Security Maps
To Update a Connector Work Security Map
To Delete a Connector Work Security Map
Administering Administered Objects
To Create an Administered Object
To Update an Administered Object
To Delete an Administered Object
16. Administering Internet Connectivity
17. Administering the Object Request Broker (ORB)
18. Administering the JavaMail Service
19. Administering the Java Message Service (JMS)
20. Administering the Java Naming and Directory Interface (JNDI) Service
21. Administering Transactions
After a connector module has been deployed, you are ready to create a connector connection pool for it.
The following topics are addressed here:
Use the create-connector-connection-pool subcommand in remote mode to create a connector connection pool for a deployed connector module. When you are building the connector connection pool, certain data specific to the EIS will be required. The value in the mandatory --connectiondefintion option provides the EIS info.
Multiple connector resources can specify a single connection pool.
Creating a connector connection pool is a dynamic event and does not require
server restart. However, there are some parameters that do require server restart. See
Configuration Changes That Require Server Restart.
Before creating the connector connection pool, the connector must be installed.
Ensure that the server is running.
Remote subcommands require a running server.
Create the connector connection pool by using the create-connector-connection-pool(1) subcommand.
Information about properties for the subcommand is included in this help page.
If needed, restart the server.
Some properties require server restart. See Configuration Changes That Require Server Restart. If your server needs to be
restarted, see
To Restart a Domain.
You can verify that a connection pool is usable by using the ping-connection-pool subcommand.
For instructions, see To Contact (Ping) a Connection Pool.
This example creates the new jms/qConnPool pool for the javax.jms.QueueConnectionFactory connector module.
asadmin> create-connector-connection-pool --steadypoolsize 20 --maxpoolsize 100 --poolresize 2 --maxwait 60000 --raname jmsra --connectiondefinition javax.jms.QueueConnectionFactory jms/qConnPool Command create-connector-connection-pool executed successfully
You can also view the full syntax and options of the subcommand by typing asadmin help create-connector-connection-pool at the command line.
Use the list-connector-connection-pools subcommand in remote mode to list the pools that have been created.
Ensure that the server is running.
Remote subcommands require a running server.
List the connector connection pools by using the list-connector-connection-pools(1) subcommand.
This example lists the existing connector connection pools.
asadmin> list-connector-connection-pools jms/qConnPool Command list-connector-connection-pools executed successfully
You can also view the full syntax and options of the subcommand by typing asadmin help list-connector-connection-pools at the command line.
Use the ping-connection-pool or flush-connection-pool subcommands in remote mode to perform these
tasks on a connection pools. See To Contact (Ping) a Connection Pool or
To Reset (Flush) a Connection Pool for instructions.
Ensure that the server is running.
Remote subcommands require a running server.
Connect to or reset a connector connection pool by using theflush-connection-pool(1) subcommand
or the
ping-connection-pool(1) subcommand.
Use the get and set subcommands to view and change the values of the connector connection pool properties.
List the connector connection pools by using the list-connector-connection-pools(1) subcommand.
View the properties of the connector connection pool by using the get(1) subcommand.
For example:
asadmin> get domain.resources.connector-connection-pool.conectionpoolname.*
Set the property of the connector connection pool by using the
set(1) subcommand.
For example:
asadmin> set domain.resources.connector-connection-pool .conectionpoolname.validate-atmost-once-period-in-seconds=3
If needed, restart the server.
Some properties require server restart. See Configuration Changes That Require Server Restart. If your server needs to be
restarted, see
To Restart a Domain.
Use the delete-connector-connection-pool subcommand in remote mode to remove a connector connection pool.
Ensure that the server is running.
Remote subcommands require a running server.
List the connector connection pools by using the list-connector-connection-pools(1) subcommand.
If necessary, notify users that the connector connection pool is being deleted.
Delete the connector connection pool by using the delete-connector-connection-pool(1) subcommand.
This example deletes the connection pool named jms/qConnPool.
asadmin> delete-connector-connection-pool --cascade=false jms/qConnPool Command delete-connector-connection-pool executed successfully
You can also view the full syntax and options of the subcommand by typing asadmin help delete-connector-connection-pool at the command line.