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 Server Restart.
Before creating a connector resource, you must first create a connector connection pool. For instructions, see To Create a Connector Connection Pool.
Ensure that the server is running.
Remote subcommands require a running server.
Create the connector resource by using the create-connector-resource(1) subcommand.
Information about properties for the subcommand is included in this help page.
(Optional) 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.
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 |
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.
Ensure that the server is running.
Remote subcommands require a running server.
List the connector connection pools by using the list-connector-resources(1) subcommand.
This example lists the existing connector resources.
asadmin> list-connector-resources jms/qConnFactory Command list-connector-resources executed successfully |
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.
List the connector connection pools by using the list-connector-resources(1) subcommand.
View the properties of the connector resource by using the get(1) subcommand.
For example
asadmin> get domain.resources.connector-resource.jms/qConnFactory |
Set the property of the connector resource by using the set(1) subcommand.
For example:
asadmin> set domain.resources.connector-resource.jms/qConnFactory.enabled=true |
(Optional) 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-resource subcommand in remote mode to remove a connector resource by specifying the JNDI name.
Before deleting a resource, all associations with the resource must be removed.
Ensure that the server is running.
Remote subcommands require a running server.
List the connector connection pools by using the list-connector-resources(1) subcommand.
If necessary, notify users that the connector resource is being deleted.
Delete the connector resource by using the delete-connector-resource(1) subcommand.
This example deletes the jms/qConnFactory connector resource.
asadmin> delete-connector-resource jms/qConnFactory Command delete-connector-resources executed successfully |
You can also view the full syntax and options of the subcommand by typing asadmin help delete-connector-resource at the command line.