Before you begin
Java 2 Connector authentication data entries are used by resource adapters and Java Database Connectivity (JDBC) data sources. A Java 2 Connector authentication data entry contains authentication data, which includess the following information:This task creates and deletes Java 2 Connector (J2C) authentication data entries.
Steps for this task
Note: When creating a new authentication data entry and specifying an alias, be aware that the node name is automatically appended as a prefix to the alias name you specify. For example, if you specify the alias, tek_test_Con3, and the node is MyNode, then the final alias name is: MyNode/tek_test_Con3.
Remember that this full alias name is the one used in your deployment descriptor.
Results
A new J2C authentication data entry is created or an old entry is removed. The newly created entry is visible without restarting the application server process to use in the data source definition. But the entry is only in effect after the server is restarted. Specifically, the authentication data is loaded by an application server when starting an application and is shared among applications in the same application server.If you create or update a data source that points to a newly created J2C authentication data alias, the test connection fails to connect until you restart the deployment manager. After you restart the deployment manager, the J2C authentication data is reflected in the run-time configuration. Any changes to the J2C authentication data fields require a deployment manager restart for the changes to take effect. The node agent must also be restarted.
Example
What to do next
Use the authentication data entry that is defined in the resource adapters or the JDBC data sources.