Add node to a cell

[PetSis]

Hi, i'm trying to execute the addnode command and i'm having problems.
I installed was 5.0 base in one machine, then installed the was ND 5.0
in the same machine (coexist option checked to modify port numbers).
The two admin consoles runs fine separately one on port 9090 (base)
and the other on port 9091 (ND).
In the base install i have three application servers (unique ports for
each one) plus the default (server1), with its applications installed
and running.
When i run de addnode command to add the base node to the cell in the
ND installation i got this error in the log:

[6/9/04 17:58:26:586 GMT-05:00] 64ce32fd SOAPConnector d soap url:
https://mylocalhost:8881/
[6/9/04 17:58:30:695 GMT-05:00] 64ce32fd SOAPConnector < reconnect
[SOAPException:
faultCode=SOAP-ENV:Client; msg=Error opening socket:
java.net.ConnectException: Connection refused: connect;
targetException=java.lang.IllegalArgumentException: Error opening
socket: java.net.ConnectException: Connection refused: connect]
at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown
Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:159)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:120)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:245)
at com.ibm.ws.management.tools.LaunchUtils.getAdminClient(LaunchUtils.java:327)
at com.ibm.ws.management.tools.LaunchUtils.getAdminClient(LaunchUtils.java:236)
at com.ibm.ws.management.tools.AdminTool.stopAllServers(AdminTool.java:357)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:284)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:159)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:127)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

[6/9/04 17:58:30:695 GMT-05:00] 64ce32fd AdminClientFa <
createAdminClient - failed

java.lang.reflect.InvocationTargetException:
com.ibm.websphere.management.exception.ConnectorNotAvailableException
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.reconnect(SOAPConnectorClient.java:168)
at com.ibm.ws.management.connector.soap.SOAPConnectorClient.<init>(SOAPConnectorClient.java:120)
at java.lang.reflect.Constructor.newInstance(Native Method)
at com.ibm.websphere.management.AdminClientFactory.createAdminClient(AdminClientFactory.java:245)
at com.ibm.ws.management.tools.LaunchUtils.getAdminClient(LaunchUtils.java:327)
at com.ibm.ws.management.tools.LaunchUtils.getAdminClient(LaunchUtils.java:236)
at com.ibm.ws.management.tools.AdminTool.stopAllServers(AdminTool.java:357)
at com.ibm.ws.management.tools.NodeFederationUtility.runTool(NodeFederationUtility.java:284)
at com.ibm.ws.management.tools.AdminTool.executeUtility(AdminTool.java:159)
at com.ibm.ws.management.tools.NodeFederationUtility.main(NodeFederationUtility.java:127)
at java.lang.reflect.Method.invoke(Native Method)
at com.ibm.ws.bootstrap.WSLauncher.main(WSLauncher.java:94)

The soap ports for my application servers are 8880 (server1),
8881(myappserv1), 8882(myappserv2), 8883(myappserv3). I got the same
error for all the servers:

[6/9/04 17:58:26:586 GMT-05:00] 64ce32fd SOAPConnector d soap url:
https://mylocalhost:8881/
[6/9/04 17:58:26:586 GMT-05:00] 64ce32fd SOAPConnector d soap url:
https://mylocalhost:8882/
[6/9/04 17:58:26:586 GMT-05:00] 64ce32fd SOAPConnector d soap url:
https://mylocalhost:8883/
[6/9/04 17:58:26:586 GMT-05:00] 64ce32fd SOAPConnector d soap url:
https://mylocalhost:8880/

After the execution ends i can see the node, the servers and
applications in the ND console, but all of them are unavailable. Also
it didn't create the node agent in the was base.

Any ideas?
Thanks in advance.

[Ken Hygh]

PetSis wrote:

This error means addnode couldn't connect to the ND soap port. You need
to fix that on the addnode commandline.

Ken

[Phill]

What is the SOAP port on your ND installation?
Your addnode command should look something like this:
>addNode localhost <$dmgr_soap_port>

Do you have globalSecurity enabled? If so, you need to add the -user,
and -password parameters to the command line as well.

[PetSis]

First, thanks for the answers:
My command line is this:
addnode myHostName 8889 -includeapps -trace

I don't have security enabled and the soap port 8889 is ok, it can
connect to de ND. The problem is when it tries to connect to the
application servers declared inside the was base.

I also noticed that i have some application legacies (was 4 AE)
installed in the was base. When i installed those applications in base
5 with the option precompile jsp checked the applications cause errors
and didn't deploy, but when i dind't use the option precompile jsp the
applications were installed succesfully. Then i run the addNode
command and it failed.
Then i uninstalled those applications with errors in compile jsp
option checked, and try again with the addNode command, now the
commands run fine.
Now the problem that i have is how to install those legacy
applications now from the ND admin console. I think that i have to
migrate the code first.

phill0...@netscape.net (Phill) wrote in message news:<a5b80260.04061...@posting.google.com>...