Default Messaging Provider Problem Determination - IBM Redbooks

The solution to this problem is to verify the component managed authentication
alias. This alias can be specified for the data source definition, or for the
messaging engine definition.
Note: The recommended (and more secure) method of specifying the
authentication alias is to do it in the messaging engine data store definition. Be
aware, that if you specify the authentication alias in this way, testing the data
source connection in the administrative console will fail.
If the authentication alias is specified in both places (data source and
messaging engine), the alias specified on the messaging engine will be used.
If specified at the messaging engine, you can find the authentication alias
specification by performing the following steps in the administrative console:
1. Select Service integration → Buses.
2. Click the bus name.
3. Under Additional Properties, click Messaging engines.
4. Click the messaging engine name.
5. Under Additional Properties, click Data store.
If specified at the data source, you can find it by performing the following steps:
1. Select Resources → JDBC providers.
2. Select the proper scope.
3. Select the JDBC provider from the list.
4. Under Additional Properties, click Data sources.
5. Select the data source name.
The authentication alias must contain a valid user name and password
combination that has appropriate access privileges for the database. Refer to
Section 11.8.4 of WebSphere Application Server V6 System Management and
Configuration Handbook, SG24-6451.
16 WebSphere Application Server V6: Default Messaging Provider Problem Determination