Troubleshooting
Problem
The authentication alias applied on ActivationSpec is not being used by the runtime instance of ActivationSpec. The user name and password values needed for inbound connection have to be set explicitly on the ActivationSpec, either in enterprise service discovery tool or through the administrative console after deployment.
Symptom
The authentication alias applied on ActivationSpec is not being used by the runtime instance of ActivationSpec. The user name and password values needed for inbound connection have to be set explicitly on the ActivationSpec, either in enterprise service discovery tool or through the administrative console after deployment.
Cause
The runtime environment does not pull values from the authentication alias.
Resolving The Problem
Specify the user name and password on the ActivationSpec property. There are two options for doing this.
Option 1
Specify the value on the instance of ActivationSpec created when the application was deployed. Use the administrative console to select the ActivationSpec instance, and specify values for the User name and Password fields.
Option 2
Specify the values for the User name and Password fields on the ActivationSpec properties section on the last panel of the enterprise service discovery wizard. When you do this, the fields are serialized to the export file and will be applied on the deployed activation specification instance.
A limitation to this approach is that once these values are specified on the ActivationSpec property in the export file, they cannot be dynamically changed using the administrative console. So, if you need to update the user name and password after deployment, you must use the first option.
Product Synonym
JCA JDBC Adapter;Websphere JDBC Adapter
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21216512