[Mc4j-development] Websphere 5.1 support

[Greider, H. J. (LNG-DAY) <Her...@le...>]

I'm working with the Websphere 5 support in 1.2, beta 4. This looks like an
incredible way to manage the internal MBeans of Websphere as well as
user-defined MBeans. 

Unfortunately, I was unable to get it to work. Following the instructions, I
supplied the location of the local installation lib folder. I can see the
classpath including all the appropriate Websphere adminstrative jar files.
That appears to be correct.

I tried several ports for the connection: BOOTSTRAP_ADDRESS and
SOAP_CONNECTOR_ADDRESS for the Deployment manager and the same for the
actual appserver. I used URL http://hostname:port <http://hostname:port>
for the server URL with each attempt. Isn't the BOOTSTRAP_ADDRESS the
correct endpoint to use? Can I attach to either the DeploymentManager,
NodeAgent, or DeploymentManager?

I receive the message "Unable to connect to server at [what the URL is].
Check to make sure the server is running on the specified host and port."
Just to ensure that everything is up, I was able to connect through both the
admin console as well as through wsadmin without a problem. 

I am using the Websphere installation in WSAD (rather than the normal
installation). That works great for wsadmin and direct connection from Java
applications. Could there be a dependency there?

Thanks for any assistance!
Herm Greider
LexisNexis
Dayton, Ohio