Q1: Is there a mechanism to test the J2C/JCA
connection from the websphere administrative console? Why?
A1: The answer is no. There is no mechanism to test the J2C/JCA
connection from websphere administrative console. The reason is that there
isn't a standard operation that can be done on all J2C Connection
Factories. For example, with CICS ConnectionFactories, you get a
connection, and create an interaction which specifies a procedure to run.
That procedure resides on the CICS server, and there is no standard one
that is built in to every CICS server. It gets worse when you consider
that whatever mechanism that implemented would have to know how to handle
CICS, IMS, mySAP, and dozens of other JCA compliant resource adapters.
Since there's no standard testConnection mechanism included in the JCA
specification, it's nearly impossible for WebSphere to make a test
connection button for the J2C/JCA connection in websphere administrative
console.
Q2: How to test the J2C/JCA connection?
A2: The easiest way is to create a simple SessionBean that does
the lookup, and calls getConnection().
|