Node Agent

What is the effect on end-user in case the dmgr goes down or node agent stops?

Questions by vamsi.mca.01   answers by vamsi.mca.01

Showing Answers 1 - 37 of 37 Answers

sahilsardana

  • Jul 19th, 2010
 

There is no effect on the end user if the DMGR goes down or the Nodeagent goes down, because nodeagent is mediator between dmgr and app server.

The app server will continue running if everything was running before and we have stopped the dmgr and nodeagent. I beleive the app server wil continue running(need to test things in my dev environment).

To confirm above, I will test it tonight after business hours and will get back to you.

In case if we say that everything is stopped and we try to start only the application server, keeping the dmgr and nodeagent down, then its not gonna work. Because the nodeagent should be running before starting the application server.

  Was this answer useful?  Yes

sahilsardana

  • Jul 19th, 2010
 

I have tested things, the application run without any problem if we keep running the application server but stop the running nodeagent and dmgr.

  Was this answer useful?  Yes

sree.boa

  • Aug 30th, 2010
 

I don't think so this will work
If NodeAgent goes down then the AppServer by default Goes down
If Appserver goes down by default App goes down then How you will get Page?

  Was this answer useful?  Yes

ram1ch

  • Oct 15th, 2010
 

If the NodeAgents are down, you would not be able to sync the changes you made on the application server to the Deployment Manager. Nodeagent is just the connection between DMGR and the AppServer.
DMGR is the Master Repository.
Hope this helps, Let me know if you have any questions

Adiseshan

  • Aug 8th, 2011
 

In case of fail over the node agent should be running to re-gain the http session attributes to the new server.
node agent should be running always..!

  Was this answer useful?  Yes

mukund

  • Aug 12th, 2011
 

no effect on user because if dmgr is down it doesn't mean that servers are down.

  Was this answer useful?  Yes

sahilsardana

  • Aug 12th, 2011
 

Node Agent Plays important role between Cell members, Its possible that 2 diff applications are communicating and its possible that an application has some dependency on another application running on another application server. So nodeagent helps 2 diff applications servers communicate with each other. Also whenever an application server starts, the node agent should be running as application server registers himself with nodeagent, if the nodeagent is down, the application server will fail to start. So, Its always recommended that the nodeagent should be running.

In the end I would say, our all services should be running without any problems, if any problems, fix it.

  Was this answer useful?  Yes

lakshmi narayana reddy

  • Aug 14th, 2011
 

we can access the app even though dmgr goes down, but node agent should be running,

Madhu

  • Jul 24th, 2012
 

Its not mandatory that node agent and dmgr should be up for application to work.

  Was this answer useful?  Yes

anil4was

  • Jul 26th, 2012
 

When DMGR goes Down then there is no impact to the end-users. If NA is goes Down then there is no problem in Distributed Environment/Clustered the servers will server the application when we maintaining fail over mechanism. (NA is nothing but communication between Dmgr and federated nodes).

Before starting the app server the applications NA must be up and running then only it serves the applications which are running on that app server.

I hope this will helps u. If any corrections let me know.....

  Was this answer useful?  Yes

subrat

  • Nov 22nd, 2012
 

If Dmgr is down there is not any impact for the end-user.If the Dmgr. and Node is down there is the application impact on the end user but in cluster environment if one node is down the other node will take care the application ,So there is not any impact on end user to access the application.

sahilsardana

  • Nov 23rd, 2012
 

It depends on different scenarios:

1. If the DMGR goes down, there is no effect to the end user.
2. If the node agent goes down, then it depends on the architecture of the applications.
A) if the application is running on a single application server, then there will be no effect(keeping in mind, server was already running).
B) If the application is running in a clustered environment and we have session persistence configured on it, then if the app server hosting the application fails, session persistence will not happen.

  Was this answer useful?  Yes

santha

  • Dec 4th, 2012
 

1) If the DMGR is Down, the available servers in that corresponding DMGR works and serving the response for the client requests. But, the main thing is if the DMGR is down at that time we cant see all available server in the Admin Console at a time..

2) If the Node agent is Down, that correspondent server are responding well for the client requests. But if there is any changes done in Application server, that are not saved from local repository to Master repository.

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.

 

Related Answered Questions

 

Related Open Questions