|
Home > Archive > WebSphere Application Server > April 2006 > May I use JMX without nodeAgent?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
May I use JMX without nodeAgent?
|
|
|
| I installed stand-alone application on WebSphere and try to use JMX programming to manage the application. When getNodeAgentMBean(String nodeName) is called, the printout told me that "Node agent MBean not found". Do I have to install deploymenr manager b
efore using JMX?
From config\cells\nodes\ I know the node name is correct. But I did not see nodeagent.
Any help is appreciated.
Wayne
| |
| Paul Ilechko 2006-04-27, 8:08 am |
| wz6871@sbc.com wrote:
> I installed stand-alone application on WebSphere and try to use JMX
> programming to manage the application. When getNodeAgentMBean(String
> nodeName) is called, the printout told me that "Node agent MBean not
> found". Do I have to install deploymenr manager before using JMX?
> From config\cells\nodes\ I know the node name is correct. But I did
> not see nodeagent. Any help is appreciated. Wayne
The node agent only exists in a network deployment configuration, so if
you don't have ND you can't use that API
| |
|
| Thank you very much for the info.
It seems that the WAS JMX library is available in the \lib directory. Is it possible to use JMX library to create a node agent in Java progam to manage a node?
As a matter of fact, the ND version is not the problem. The problem is that the administrator only want to install the stand-alone application.
If JMX is not a choice, is there any other alternative can be used to write a installer? wsadmin script also needs JMX and node agent, correct?
Thanks again!
Wayne
| |
| Ken Hygh 2006-04-27, 8:08 am |
| wz6871@sbc.com wrote:
> Thank you very much for the info.
> It seems that the WAS JMX library is available in the \lib directory. Is it possible to use JMX library to create a node agent in Java progam to manage a node?
> As a matter of fact, the ND version is not the problem. The problem is that the administrator only want to install the stand-alone application.
> If JMX is not a choice, is there any other alternative can be used to write a installer? wsadmin script also needs JMX and node agent, correct?
> Thanks again!
> Wayne
What's a "standalone application"? something non-J2EE? EAR? WAR?
Application Client?
Ken
| |
| Paul Ilechko 2006-04-27, 8:08 am |
| wz6871@sbc.com wrote:
> Thank you very much for the info. It seems that the WAS JMX library
> is available in the \lib directory. Is it possible to use JMX library
> to create a node agent in Java progam to manage a node? As a matter
> of fact, the ND version is not the problem. The problem is that the
> administrator only want to install the stand-alone application. If
> JMX is not a choice, is there any other alternative can be used to
> write a installer? wsadmin script also needs JMX and node agent,
> correct? Thanks again! Wayne
I think you are a little confused. There are two different editions of
WAS - Base, that only supports a single server, and Network Deployment,
that supports clustering. Both can be managed using JMX, but only
Network Deployment contains Node Agents and a Deployment Manager. If you
are using Base WAS you can only use JMX commands that manage Servers,
there are no Nodes for you to manage. You don't need a Node Agent to run
wsadmin or to use JMX APIs.
| |
|
| We have the ND version. But only the base part is installed. The deployment manager is not installed.
I know the base installation does not create node agent. From another point of view, since everything in WAS can be controlled by JMX, the JMX should also be able to create (and delete) the node agent. I just want to know how to use JMX to create node age
nt, so I can manage the application by Java program. After I finish my work, if neccessary, I can delete node agent by JMX. All these possible?
Use wasadmin in a simple way does not need script. But, the document gives a way to use wasadmin script for management (Jacl, Jython). My question is does this wasadmin script also need to have node agent?
Thank a lot.
Wayne
| |
| Ken Hygh 2006-04-27, 8:08 am |
| wz6871@sbc.com wrote:
> We have the ND version. But only the base part is installed. The deployment manager is not installed.
>
> I know the base installation does not create node agent. From another point of view, since everything in WAS can be controlled by JMX, the JMX should also be able to create (and delete) the node agent. I just want to know how to use JMX to create node a
gent, so I can manage the application by Java program. After I finish my work, if neccessary, I can delete node agent by JMX. All these possible?
>
> Use wasadmin in a simple way does not need script. But, the document gives a way to use wasadmin script for management (Jacl, Jython). My question is does this wasadmin script also need to have node agent?
>
> Thank a lot.
>
> Wayne
>
You're misunderstanding the WebSphere model. Please read the
documentation to understand the relationships between the Deployment
Manager, Node Agent(s), and Application Server(s).
In order to manage a standalone server, you cannot go through a node
agent. With JMX, you can manage a standalone server directly.
Ken
| |
|
| "With JMX, you can manage a standalone server directly." Very good!!
Can you give an Java example to manage a standalone server directly with JMX? Without using node agent.
As I read both was600base_admin.pdf and was600nd_admin.pdf, both documents use same method
private void getNodeAgentMBean(String nodeName).
Thanks a lot.
Wayne
|
|
|
|
|