Port conflict: Installing WAS Base and ND on sam machine.

[Vikrama Sanjeeva]

Hi,
I have sucessfully installed WAS V 5.0 [i.e. BASE] on WIN 2000 Server (SP4), 2 GB RAM, 3 GHz processor machine.
Now I am about to install WAS ND on the same machine. In fact it will be an upgrade from WAS Base to WAS ND. But as mentioned in "IBM WebSphere Application Server V5.1 System Management and Configuration" on page 154 that, "If you are installing Network Deployment on the same system as IBM WebSphere Application Server V5, you will get port conflicts for the administration ports."
So, kinldy guide me what precautions I have to take before installing ND? Any port configuration I have to do before ND installation or after?

Bye,
Viki.

[Vikrama Sanjeeva]

Hi guyz,

Here is a quote for port 9090 from "IBM WebSphere Application Server V5.1 System Management and Configuration" page 131:

"This port is the same as used by a base WebSphere Application Server installation. If you are installing Network Deployment on a system that has an existing base installation, you will need to select a different port unlessyou are going to immediately add that base installation to the Deployment Manager cell. In that case, the base admin console application is deleted and there is no port conflict."

Since, I am deploying WAS ND for testing and learning purpose, therefore I think, following to the above quote, I should add the existing BASE installation to Deployment Manager cell resulting in a permenant REMOVAL (deleting) of Administration Console of BASE installation. Here I have two questions,

After adding existing BASE to Deployment Manager:

1: Will I'll be able to administer the BASE via "wsadmin"?
2: This BASE will be considered as a NODE of ND?

Kindly clear these concepts.

Bye,
Viki.

[Roland Barcia]

Once you federate the node, the port conflict will fix itself. Once you add a node to the DMgr, you must configure the server through the the DMgr. But you can run wsadmin, as long as point to the DMmgr. The federate node will uninstall the admin console from the base server. It will allow you to run wsadmin on the server, but any config changes will be lost after replication. This is all explained in my book. Link is below. View JavaRanch review of our book as well.

[Vikrama Sanjeeva]

Hi,

I isntalled ND and also added node using the following command:

addNode <DM_hostname> 8879 -includeapps and

http://localhost:9090/admin is opening successfully. But using wsadmin I can configure BASE but once it is synchronize witrh DMGR, all changes will be updated (overwritten) as per DMGR configuration? Plz. clear this point.

Bye,
Viki.

[Roland Barcia]

This is by design. DMgr provides centralized administration for many nodes and servers. You can use the DMgr's admin console to administer the server.