Quote "A group of application servers “managed” by a deployment manager is referred to as a WebSphere CELL. In order to facilitate this, on every application server that is “managed” (the IBM term for this is federated) within a CELL, there is a running process called a nodeagent."

My question is how many node agent do I need to run on one physical machine when 2 application server are on the same physcial machine but they are running different web apps?

You need only one node agent to manage both the App servers.Both the Application servers can have their own web applications independent of the node agent

Many thanks for the reply. That's what I thought.

Are you aware whethere there is any instructions on how to do this please? I have tried a few things, but couldn't make it work.

Many thanks

 

 

 

I assume that you've successfully installed WebSphere Application Server network deployment product.

Then

• Using the profile creation wizard, create a CELL profile . [this will give a deployment manager using which you can administrate servers and one application server.


• Then go to servers -->application servers and create a new server.


• When you deploy application1, map it to Server1.


• When you deploy application2, map it to Server2.

Many Thanks.

Yes, I do have DM installed and two servers have been created.

How do I tell one node agent to control both servers? When I created the server, they do have two different node name. For example

sever1 WC_A_node

sever1 WC_B_node

Thanks again.

 

When you go to profiles directory in the file system, how many you are seeing.

Since you started everything is on one physical server, there will generally be one profile with DMGR01 and another with AppSrv01. In this situation, there will be only one nodeagent. 

By looking at two nodes you mentioned, it seems to me that you had multiple appsrv profiles. please confirm.

Yes, my DM is on another server, while I do have two appsrv profiles on WAS server.

 

 

Hi

Have you installed DM on both physical machines ????

[quote author=121337431 post=505647179]

Yes, my DM is on another server, while I do have two appsrv profiles on WAS server.

 

[/quote]

Since you have two AppSrv profiles .. you'll have two nodeagents.In WebSphere every managed profile will have a corresponding nodeagent. If you have only one AppSrv profile and then created two servers/instances on it.. then you'll have one nodeagent.

[quote]

your question:

how many node agent do I need to run on one physical machine when 2 application server are on the same physcial machine but they are running different web apps?

[/quote]

Answer:

When the two application servers are on the same profile, one nodeagent. When the two application servers sits on different profile, each profile will have its own nodeagent.

NodeAgent is an mediator between DM and application server. One nodeagent can handle all the servers of one profile.

Hi Joseph,

Many thanks for your answer. That makes sense now.

So I should only create one profile with one node manager. And deploy  two different applications with two different URLs?

What is the downside of this? I guess if server1 is down, then both apps will be down.  

QY   

  

Hi

machine A : DM

machine B : two application servers


I Assume you already installed DM on machine A

1. on machine B install the product with custom profile and federate it to DM which is on machine A

2. from DM manager console
    2.a Servers->ApplicationServers->New
    select the custom profile Node and create the server ( ex: server1 or name it as per the application you want to deploy

     2.b repeat the 2.a with defferent server name

3. start the servers

4. deploy the applications

     Ex: application1 can be deployedon server1
           application2 can be deployed on server2
5. start the application and make sure they are working fine

Thanks for the notes. That is really useful. 


Is there any benefit if I set up two profiles (which means two node agent) instead of add a new server to the existing node?

Thanks