[jimnord99]

I am trying to create a Remote Websphere connection through Blue 10.7 IDE but after I configure it I do not get an option to Connect to the Remote Websphere server.

I am running Websphere 7.0 on a MS 2008 server in a virtual machine on my laptop. I am unable to get Connect or Disconnect from installations on the VM Host or even if I install it locally on the VM server running Websphere.

I can connect through a Websphere 7.0 straight on connection but I don’t want to use that as it requires controlling the Websphere server with its own Start and Stop which doesn’t seem to play well with my full server deployment (Websphere 7, FileNet, IBM Forms server etc…) What I want is to just connect through the Remote Connector but it doesn’t allow me to connect even through host 127.0.0.1 with SOAP 8880 which is correct for the server.

10.7 does not seem to have the option to automatically get the configuration from the server so I copied it directly from my Websphre 7.0 server connection settings that are listed for the Node, cell name and server name but no luck and no option to Connect.

What am I to do to debug this and fix this?

[support-tony]

jimnord99,

Sorry you’re seeing this issue but I’m not quite sure of what the problem is. What do you mean when you say that you don’t get “an option to Connect to the Remote WebSphere Server”? Also, I’m not sure about 10.7 not having the option to automatically get the configuration from the server. This option is on the second screen of the connection configuration wizard, as shown in the following image:

This works fine for me on a local system. I haven’t tried it for a truly remote system yet, as I’d need to set up for that but it would help if you could give more details as requested. Perhaps some screenshots might help.

[jimnord99]

I am including a few attachment files showing the issue – the first is the configuration and the second shows that from the IDE there is no option to Connect or Disconnect.

My statement on there being no button to pull the server configuration is that, yes there is a checkbox to get the server configuration but it doesn’t appear to round trip to the server and get the information. I am used to a button that would actually ping the server to get the information that way you know that you can communicate with the system. The check box in the interface doesn’t appear to do this.

Attachments:

You must be logged in to view attached files.

[support-tony]

jimnord99,

Thanks for the additional information, which helped me understand your problem better. The new option for obtaining the server cell information has replaced the button. When selected, the option will go to the server for the information when needed – on connection – rather than immediately when you’re configuring the remote connector.

Regarding the disabled Connect/Disconnect menu items, these refer to the debug connection. The connect is available as the debug icon in the servers view. The debug connection is only possible if you have enabled debug, and specified the debug port, in the remote websphere connector configuration. This is in the second window of the wizard when creating or editing a server instance for the remote connector.

Please let us know if this helps.

[jimnord99]

ok – now I understand what you mean. You set up the connection, select the auto checkbox and then it will automatically connect and get the information when you use the connection (deploy etc…). There is no Connect or Disconnect if you are not using the debugger.

So I understand it and now I have it working but I don’t think it is at all intuitive. I would have thought that debugging or not I would want to connect to the remote before I attempt to use it and would want a status indicating the success or failure of that connection. It would be nice if the tutorial would point this out. I would vote for putting the button back in the interface and allowing a way to connect to the remote or at least check the connection to the remote before attempting to use it.

Thanks for your help.

[support-tony]

Jim,

Thanks for getting back to us and I’m glad it’s working now.

Although the change to an option, rather than a button, is probably more flexible (since the remote instance could be started or not and could theoretically have different settings at each connection) I agree that some kind of test facility when configuring would be nice. I’ve raised an enhancement request for that, though I can’t say when (or if) it will be added.

Sorry for the inconvenience.

[Author]

Posts