1. Overview of GlassFish Server Administration
Default Settings and Locations
Instructions for Administering GlassFish 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. Writing and Running JavaScript Clients to Monitor GlassFish Server
10. Administering Life Cycle Modules
11. Extending and Updating GlassFish Server
Part II Resources and Services Administration
12. Administering Database Connectivity
13. 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
To Update a Connector Connection Pool
To Delete a Connector Connection Pool
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
14. Administering Internet Connectivity
15. Administering the Object Request Broker (ORB)
16. Administering the JavaMail Service
17. Administering the Java Message Service (JMS)
18. Administering the Java Naming and Directory Interface (JNDI) Service
19. Administering Transactions
A connector resource provides an application or module with the means of connecting to an EIS. Typically, you create a connector resource for each EIS that is accessed by the applications deployed in the domain.
The following topics are addressed here:
Use the create-connector-resource subcommand in remote mode to register a new connector resource with its JNDI name.
Creating a connector resource 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 Restart.
Before You Begin
Before creating a connector resource, you must first create a connector connection pool. For instructions, see To Create a Connector Connection Pool.
Remote subcommands require a running server.
Information about properties for the subcommand is included in this help page.
Some properties require server restart. See Configuration Changes That Require Restart. If your server needs to be restarted, see To Restart a Domain.
Example 13-4 Creating a Connector Resource
This example creates a new resource named jms/qConnFactory for the jms/qConnPool connection pool.
asadmin> create-connector-resource --poolname jms/qConnPool --description "creating sample connector resource" jms/qConnFactory Command create-connector-resource executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help create-connector-resource at the command line.
Use the list-connector-resources subcommand in remote mode to list the connector resources that have been created.
Remote subcommands require a running server.
Example 13-5 Listing Connector Resources
This example lists the existing connector resources.
asadmin> list-connector-resources jms/qConnFactory Command list-connector-resources executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help list-connector-resources at the command line.
Use the get and set subcommands to view and change the values of the connector resource properties.
For example
asadmin> get domain.resources.connector-resource.jms/qConnFactory
For example:
asadmin> set domain.resources.connector-resource.jms/qConnFactory.enabled=true
Some properties require server restart. See Configuration Changes That Require Restart. If your server needs to be restarted, see To Restart a Domain.
Use the delete-connector-resource subcommand in remote mode to remove a connector resource by specifying the JNDI name.
Before You Begin
Before deleting a resource, all associations with the resource must be removed.
Remote subcommands require a running server.
Example 13-6 Deleting a Connector Resource
This example deletes the jms/qConnFactory connector resource.
asadmin> delete-connector-resource jms/qConnFactory Command delete-connector-resources executed successfully
See Also
You can also view the full syntax and options of the subcommand by typing asadmin help delete-connector-resource at the command line.