What is Node Manager ?

Hi
I have been reading documents on Oracle Fusion Middleware 11g. At lot of places 'Node Manager' is mentioned across these documents.
Please can someone explain here what is Node Manager and what it is its role in OFMW 11g ?
Cheers
Mayur

Hi Mayur,
For more details please refer to: http://weblogic-wonders.com/weblogic/2010/06/18/weblogic-initials/
 What is NodeManager?
A Node Manager process is not associated with a specific WebLogic domain but with a machine. Node Manager process to control server instances in any WebLogic Server domain until the server instances reside on the same machine as the Node Manager process.
Node Manager is a WebLogic Server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location. Although Node Manager is optional, it is recommended if your WebLogic Server environment hosts applications with high availability requirements.
A Node Manager process is not associated with a specific WebLogic domain but with a machine. You can use the same Node Manager process to control server instances in any WebLogic Server domain, as long as the server instances reside on the same machine as the Node Manager process.
Why We Need Nodemanagers?
1). It can Start, Shut Down, and Restart an Administration Server which has assigned a Machine.
2). It can Start, Shut Down, and Restart an Managed Server which has assigned a Machine.
3). It can Restart Administration and Managed Servers. (Crash Recovery of Servers is an Interesting feature)
4). It can be used to Monitor Servers and View Log Data
Types of NodeManagers?
*1). Java Based Nodemanager:* This can be used in Windiows as well as UNIX based Operating systems. Java Based Node Manager is not supported on Open VMS, OS/390, AS400, UnixWare, or Tru64 UNIX.
*2). Script Based Nodemanager:* This nodemanager can be used in UNIX based operating systems. The advantage of the script-based Node Manager is that it can remotely manage servers over a network that has been configured to use SSH.
For More Information on NodeManager please refer to:
http://download.oracle.com/docs/cd/E13222_01/wls/docs90/server_start/nodemgr.html
And
http://blogs.oracle.com/jamesbayer/2010/01/weblogic_nodemanager_quick_sta.html
Thanks
Jay SenSharma

Similar Messages

What is the use of Node Manager?

OBIEE Oracle Business Intelligence 11.1.1.5
I have started up the WebLogic server which delivers the WL Server Admin Console as well as the Fusion Middleware Control.
I have ignored NodeManager. It hasnt been started.
What is the use of NodeManager?
Oracle tells us:
Note: In order to start the Managed Server using the WebLogic Server Administration Console, the Node Manager must be running.
http://download.oracle.com/docs/cd/E21043_01/bi.1111/e10541/components.htm
But my Manged Server is running ok - I can check http://<host>:7001/console and its ok.
So why do I need to bother with NodeManager?
I only have WLS and OHS installed - no BI instance.
DA

Answers inline:
As I have installed weblogic server 10.3.5 on windows. while am starting it using cmd am getting two ips as
1**.*.... for weblogic server one is (channel default 4... .. and one is default 1) kindly explain.
- It doesn't generate any IP. If you have installed successfully, weblogic will run on your system and it's ip will remain same. You can access it using your systems'IP:portnumber
Also tell as I have to use cmd for starting servers how can i use unix commands for the same??
- You have installed on windows so unix command won't work for you. You can either start by going into services window in windows or start using command by going to path weblogichome\domains\domainname\bin. Execute startWebLogic.cmd
Also explain what is the use of node manager and weblogic scripting tool which are also installed in the system.
- Node manager is used for communication bentween two or more servers in a domain.
As am looking to install OIM 11g so kindly tell what are all the things I need to know about weblogic so that i can learn OIM easily.
- To install OIM, install weblogic, install oracle database. Use RCU utilities to create database and then install SOA, OIM and configure them. You can get all kinds of guides and steps for OIM 11g r2 here:
http://docs.oracle.com/cd/E27559_01/index.htm
regards,
GP

What is the function of Node Manager in WLS 8.1 SP4

Hi,
I was trying to understand the real function of Node Manager. During my install I had install Node Manager to run as Windows Service (w2k server). I was wondering as to how i can setup Node Manager to monitor my manage servers (from what i know it can do) and can it restart any manage servers that stop and/or are not started.
Thanks
J

This should help http://e-docs.bea.com/wls/docs81/adminguide/confignodemgr.html
cheers !
Dips

Multiple Node Manager Instances and servers sharing the same domain home.

Hi,
We have a 8 man server weblogic cluster spread over 4 machines. Each machine runs 2 man servers each.
Each of the machine is configured to run node manager.
We use shared storage accessible to all 8 servers and all 8 man servers have the same domain_home.
Lets call it W:/domain
Now the problem we are facing is that node manager running on 1 machine is trying to access/control a managed server on a different machine after a machine restart.
eg.
ManServer1 Home : W:/domain/servers/server1 ====> runs on Machine 1
ManServer2Home : W:/domain/servers/server2 ====> runs on Machine 2
Problem is node manager on machine 1 is trying to restart man server 2. The path W:/domain/servers/server2 is accessible to Machine 1.
After a restart, what I assume is happening is that the nodemanager is checking all servers folder under Domain_Home/Servers and trying to restart servers instead of restarting only those which it should start. The config file has the server and machine assignment done correctly. Is there a way to make this configuration towork. Or do we need to create different domain_home's for different man servers like
Domain_Home for MS1: W:/domain/MS1 ( Server Home would be : W:/domain/MS1/servers/MS1)
Domain_Home for MS2: W:/domain/MS2 ( Server Home would be : W:/domain/MS2/servers/MS2)
Regards,
Atheek
Edited by: atheek1 on 03-May-2010 00:27

Thanks - We have tried putting 2 dad entries in file, but not sure how you connect. You only specify a port number, so how does it connect that to a db???

After I do Node Manager nmConnect(...) I can no longer start a managed svr

I am running 10.3.2 on both windown and redhat
I have a domain with AdminServer and one managed server.
I can start AdminServer from the shell with startWebLogic.cmd
I can log into the web based 'console'
I can go to Environment -> Servers and start/shutdown the managed server.
If I use WLST and...
connect('user', 'pass', 't3://localhost:7001')
nmEnroll('fullPathToDomainDir')
I am still OK, I can still use the console to start and stop the managed server and I can so WLST start('managedSever')
I stop running the AdminServer from the shell - it is no longer running.
Now, I want to start the AdminServer with Node Manager, so (with WLST)...
nmConnect('user','pass','localhost','5556','domainName)
I get the error...
'Cannot connect to Node Manager: Access to domain 'domainname' for user 'user' denied
As suggested elsewhere, I go and edit nm_password.properties and change the hashed user/pass to
username=user
password=pass
I go back to WLST, now nmConnect works!!!
I can then do..
nmStart('AdminServer')
The AdminServer start, I go to the web console, and I try to start the managed server, I get...
'For server managedServer, the Node Manager associated with machine machineName is not reachable'
So it looks like the re-hashed password from nmConnect(...), while it works for WLST, it no longer works for the console.
Bottom line, I can get either get the console to start the managed server (if I do WLST connect(...) + nmEnroll(...)) or I can get WLST to start the servers (if I reset nm_password.properties and do nmConnect), but I can not get WLST to start the AdminServer and have the AdminSever console start the managed server.
I know for a fact that others have run into this, but in the threads I found, the thread stops before a soluton is posted.
Anyone know about this issue?
Regards

There are a couple of things you need to keep in mind:
-- There is one and only one valid username / passwrod for connecting to the node manager.
-- When you use nmEnroll, the username / password placed in the nm_password.properties file is taken from the admin server, hashed an placed in the nm_password file.
-- When you edit the nm_password.properties, and place the line "enter in username=user / password='pass',", in clear text, you have over ridden the U/P \thje admin server knows.
That is why you have a situation, oen of the two works but never both at the same time.
What you need to do is:
-- Log in to the WL Console.
-- in the Domain Tree, click at teh root level, which is the domain name.
-- Under the security tab, under advanced there is a node manager username / password.
-- Click on "Lock and edit", and change those to match what you are using through WLST.
-- Activate changes.
-- Just to make sure all is well, use nmEnroll to re enroll the node manager again , this way the nm_password.properties file will be set up correctly.
Now, both the WL Console should be able to talk to the node manager as well as nmConnect('user','pass','localhost','5556','domainName) would succeed.
Also, if you want to use node manager to start /servers, make sure you edit the file ( $WL_HOME/common/nodemanager/nodemanager.properties) and change the line
StartScriptEnabled=false
to
StartScriptEnabled=true
This will ensure all the proper class paths and properties etc needed are set up when using the node manager.
You would need to bounce the node manager for this change t take effect
Hope this helps.

I can not start a remote server via Node Manager

There is a workaround to this problem. The issue seems to be
that when the node manager tries to start the managed server
it can not find java.exe in the system path. So please go to
Control Panel->System->...->Environment, and modify your PATH
system environment variable to include the java bin directory
in it.
Then try using the node manager again to start the managed
servers and you should have no problems.
We are aware of the issue and working on having a fix for it.
Savvas
"Rakesh Chauhan" <[email protected]> wrote:
>
Hey Guys!
I am using WLS6.1 on WIN2000 boxes. And I am getting the same error on
the Admin
console when I try to start any of the two
managed servers.
<Sep 25,2001 1:39:12 PM EDT> <Info> <[email protected]:7002><WindowsProcessControl:
online successfully invoked on server 'server90', pid: 0> The interesting thing is that when I start managed server of its own,
it is started
successfully and you can Stop the managed
server from the Admin Console.
Really frusted, I hope I have configured everything correctly. Can somebody
help
me out ?
Thanks Rakesh
"Martin Matthews" <[email protected]> wrote:
This message is simply a message from the Admin Server saying that it
has asked
NodeManager on the remote machine to start a certain server.
To see the logs for server startup then you can find these either on
the Admin
machine at WL_HOME/config/NodeManagerClientLogs/<ManagedServerName>/*.log
or on the remote machine at
WL_HOME/config/NodeManagerLogs/<ManagedServerName>/*.log
Cheers
Martin
"Paul Nixon" <[email protected]> wrote:
I also would like to know the answer to the question below from Vincent.
I am getting
this message in the Admin console from either of my two managed servers
whenever
the console has successfully contacted the Node Manager in managed
server
host.
The Node Manager logs themselves also report "online successful". What
doesn't
seem to happen is WebLogic startup and I haven't found any error log
that explains
why.
I have set the Remote Startup parameters correctly [I think] for both
managed
servers so cannot see what further is required.
Any input appreciated.
Paul.
"Vincent Ducret" <[email protected]> wrote:
Hi everybody,
When I try to start a remote WLS 6.1 server from my computer, I receive
the message
below in my WLS administration console. The Node manager is runningon
the remote
machine and correctly configured, I hope!
What does this message mean ???
Thanks for your help
Vincent
<21 aoÃ»t 01 10:19:17 CEST> <Info> <[email protected]:5555>
<WindowsProcessControl:
online successfully invoked on server 'testserver', pid: 0>

OBIEE 11g (11.1.1.5.0) - Issue with starting Node Manager

Hi,
Have anyone faced an issue with starting Node Manager in OBIEE 11g (11.1.1.5.0)? OS is 64 bit Linux, WebLogic is 10.3.5. I used the software-install method and followed by running config.sh. Everything completed successfully. I updated the catalog and rpd location in the FMW control screen.
To get it activated I bounced services and when I try to start Node Manager it gives below error --
<Aug 30, 2011 2:02:42 PM CDT> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Aug 30, 2011 2:02:42 PM> <SEVERE> <Fatal error in node manager server>
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
Aug 30, 2011 2:02:42 PM weblogic.nodemanager.server.NMServer main
SEVERE: Fatal error in node manager server
java.io.IOException: Unsupported cypher suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5
at weblogic.nodemanager.server.SSLListener.init(SSLListener.java:82)
at weblogic.nodemanager.server.NMServer.start(NMServer.java:206)
at weblogic.nodemanager.server.NMServer.main(NMServer.java:377)
at weblogic.NodeManager.main(NodeManager.java:31)
+ set +x
I see the same issue reported in ML OBIEE 11g - Node manager fails to start upon upgrade [ID 1329442.1] and WebLogic Server: Node Manager Startup is Failing with java.io.IOException: Unsupported cypher suite [ID 1329260.1] I tried to modify commEnv.sh. But it didnt help me.
Please let me know if anyone have faced similar issue and what exactly did you do to resolve it.
Cherrish Vaidiyan
Edited by: Cherrish on Aug 30, 2011 3:14 PM

Hi,
There are Two types of Cipher suites --- Certicom Cipher Suite and SunJSSE Equivalent Cipher Suite. And with Weblogic 10.3.5, you are using Sun JSSE Cipher Suite, and by default Node Manager uses the Certicom Cipher Suite.
In the nodemanager.properties, Add CipherSuite=SSL_RSA_EXPORT_WITH_RC4_40_MD5, save and restart Node Manager.
Reference Metalink Note: WebLogic Server 10.3.x: Getting "Unsupported Cipher" Exceptions When Starting Node Manager [ID 1307325.1]
Cherrish Vaidiyan

Unable to initialize Node Manager on Weblogic 11g (10.3.5) Linux env..

Hello,
I worked earlier on Weblogic 8.1 and after a long gap I am coming back to Weblogic Server.
And I tried to install & setup Weblogic Server 11g R1 (10.3.5). I successfully installed WL 11g on a Linux machine, configured the domain, and admin server without any problem. I created a managed server on the Console and tried to initialize the node manager to be able to start the managed server. I am getting the following error message repeatedly. And I did not select SSL connection, while setting up the environment.
Can someone help me resolve this issue?
<Sep 13, 2011 12:19:31 PM> <WARNING> <Uncaught exception in server handlerjavax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.>
javax.net.ssl.SSLHandshakeException: [Security:090476]Invalid/unknown SSL header was received from peer inb01.n2nservices.com - 192.168.112.46 during SSL handshake.
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireException(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.fireAlertSent(Unknown Source)
at com.certicom.tls.record.ReadHandler.fireAlert(Unknown Source)
at com.certicom.tls.record.ReadHandler.getProtocolVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.checkVersion(Unknown Source)
at com.certicom.tls.record.ReadHandler.readRecord(Unknown Source)
at com.certicom.tls.record.ReadHandler.readUntilHandshakeComplete(Unknown Source)
at com.certicom.tls.interfaceimpl.TLSConnectionImpl.completeHandshake(Unknown Source)
at com.certicom.tls.record.ReadHandler.read(Unknown Source)
at com.certicom.io.InputSSLIOStreamWrapper.read(Unknown Source)
at sun.nio.cs.StreamDecoder.readBytes(StreamDecoder.java:264)
at sun.nio.cs.StreamDecoder.implRead(StreamDecoder.java:306)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:158)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at weblogic.nodemanager.server.Handler.run(Handler.java:71)
at java.lang.Thread.run(Thread.java:662)
Sep 13, 2011 12:19:31 PM weblogic.nodemanager.server.Handler run

Can you see what listen address you have given to Node Manager in console or in config.xml?
<machine xsi:type="unix-machineType">
<name>Servername</name>
<node-manager>
<name>Servername</name>
<listen-address>localhost</listen-address>
</node-manager>
</machine>
Another way to start Managed server is to use startManaged.sh script.

Not able to start SOA managed server first time with node manager by WLST

Hi all,
I have created a SOA11g domain. Then using WLST utility I have started the Node Manager.
Then from WLST prompt I have connected to the Node Manager & started the Admin Server successfully.
But when ever I am starting the SOA manager server using WLST it's throwing the following error in WLST page : -
Error Starting server soa_server1: weblogic.nodemanager.NMException: Exception while starting server 'soa_server1'
In server log file I am getting the following error : -
Server subsystem failed. Reason: weblogic.security.SecurityInitializationException: Authentication for user denied
weblogic.security.SecurityInitializationException: Authentication for user denied
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.
Can anyone please tell me what can be the issue?
Thanks in Advance!!!
Edited by: 008 on Dec 6, 2012 7:53 PM

Hi,
I am getting this problem only when I am trying to start the domain for the first time after domain creation using WLST/nodemanager.
If I start & stop the SOA managed server from EM console & then try to start it aging from WLST/NodeManager then it's work fine.When you a server for the first time by using console or startManagedWeblogic.cmd, a file boot.properties is created under %DOMAIN_HOME%\servers\soa_server2\data\nodemanager...
The WLST/Nodemanager approach doesn't create the file so it won't work for the first start... But it will work just fine from the second on...
I've never tried, but you can try and create the boot.properties manually in your script with the following content... Password should be encrypted after the first successful start...
username=type-the-username-here
password=type-the-password-here
Cheers,
Vlad

Error when trying to start managed server from node manager

I have a managed server which is authenticated through a WeblogicAuthenticProvider. When starting the managed server from command line I need to setup certain jars in the classpath in order to start it successfully. However when I try and start the managed server from a node manager, I receive the following error.
Any ideas as to what is going on are appreciated. Is there any way to force Weblogic Node manager to invoke the actual startManagedWeblogic.cmd when bringing up the managed server
Thanks
<Jun 5, 2006 9:21:05 AM EDT> <Info> <NodeManager@*.*:5555> <Starting Server TweCluster::TaxwareServer1 ...>
<Jun 5, 2006 9:21:07 AM EDT> <Info> <NodeManager@*.*:5555> <Server TweCluster::TaxwareServer1 started, process id = 3,012>
<Jun 5, 2006 9:21:11 AM EDT> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with BEA WebLogic JRockit(TM) 1.4.2_05 JVM R24.4.0-1 Version ari-38120-20041118-1131-win-ia32 from BEA Systems, Inc.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141140> <The managed server is going to contact the admin server at http://zeus3dev:7001 to check if there exists a running admin server at this URL.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150017> <This server is being started as a dependent managed server.>
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Management> <BEA-141107> <Version: WebLogic Server 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647
WebLogic XMLX Module 8.1 SP4 Mon Nov 29 16:21:29 PST 2004 471647 >
<Jun 5, 2006 9:21:12 AM EDT> <Info> <Configuration Management> <BEA-150015> <Connecting to the administration server http://zeus3dev:7001 to retrieve the initial configuration.>
<Jun 5, 2006 9:21:16 AM EDT> <Notice> <Log Management> <BEA-170019> <The server log file E:\bea8.1\weblogic81\common\nodemanager\TaxwareServer1\TaxwareServer1.log is opened. All server side log events will be written to this file.>
The WebLogic Server did not start up properly.
java.lang.NoClassDefFoundError: com/taxware/twe/util/crypto/CryptoUtil
at com.taxware.twe.auth.server.GenericPrincipalValidator.<init>()V(GenericPrincipalValidator.java:41)
at com.taxware.twe.auth.server.WeblogicPrincipalValidator.<init>()V(WeblogicPrincipalValidator.java:38)
at com.taxware.twe.auth.server.WeblogicAuthenticationProvider.getPrincipalValidator()Lweblogic.security.spi.PrincipalValidator;(WeblogicAuthenticationProvider.java:188)
at weblogic.security.service.PrincipalAuthenticator.initialize(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:154)
at weblogic.security.service.PrincipalAuthenticator.<init>(Ljava.lang.String;[Lweblogic.management.security.ProviderMBean;)V(PrincipalAuthenticator.java:262)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doATN(Ljava.lang.String;Lweblogic.management.security.RealmMBean;)Lweblogic.security.service.PrincipalAuthenticator;(SecurityServiceManagerDelegateImpl.java:581)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(Lweblogic.management.security.RealmMBean;Ljava.util.HashMap;)V(SecurityServiceManagerDelegateImpl.java:420)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(Ljava.lang.String;)V(SecurityServiceManagerDelegateImpl.java:700)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms()V(SecurityServiceManagerDelegateImpl.java:733)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManagerDelegateImpl.java:876)
at weblogic.security.service.SecurityServiceManager.initialize(Lweblogic.security.acl.internal.AuthenticatedSubject;)V(SecurityServiceManager.java:734)
at weblogic.t3.srvr.T3Srvr.initializeHere()V(T3Srvr.java:822)
at weblogic.t3.srvr.T3Srvr.initialize()V(T3Srvr.java:670)
at weblogic.t3.srvr.T3Srvr.run([Ljava.lang.String;)I(T3Srvr.java:344)
at weblogic.Server.main([Ljava.lang.String;)V(Server.java:32)
Reason: com/taxware/twe/util/crypto/CryptoUtil

Found a workaround:
Manually, add PATH (and probably the other environment variables also) to
${WLS_HOME}/common/bin/commEnv.sh.

Stop managed server without node manager and admin server

What are the commonly used ways to stop managed Weblogic server without node manager running and without administration server running?
(I have only one solution: on the managed server startup dump process ID to a file, and then when I want to stop it, send a signal to this process ID and kill JVM. But it seems not very clean way.)
(The managed server is started when both node manager and admin server are down, and I provide boot.properties of admin server to the managed server to start.)
UPDATED: And I don't want to start neither admin server, nor node manager even temporarily.
Edited by: user12163080 on Jun 24, 2010 4:40 AM

Hai,
I read the Oracle weblogic wlst script document without Admin server you cannot connect the managed server through the WLST script. see the below lines
"The start command starts Managed Servers or clusters in a domain using Node Manager.
To use the start command, WLST must be connected to a running Administration Server.
To start Managed Servers without requiring a running Administration Server, use the
nmStart command with WLST connected to Node Manager."
"You shut down a server to which WLST is connected by entering the shutdown command
without any arguments.
When connected to a Managed Server instance, you only use the shutdown command to shut
down the Managed Server instance to which WLST is connected; you cannot shut down another
server while connected to a Managed Server instance.
WLST uses Node Manager to shut down a Managed Server. When shutting down a Managed
Server, Node Manager must be running.
In the event of an error, the command returns"
They are two option if you are using adminserver then we can stop the any Managed server.
The option is if you are using the nodemanager without admin server we can stop the any Managed server.
The last final solution to kill the particular Managed server pid.
Regards,
S.vinoth babu

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

Steps to setup and configure Node Manager on local and remote machine

Hello,
I am using WLS 10.3 on Windows.
I have two machines, One cluster and two managed servers (one on each machine) created under a domain. I have used configuration wizard to create the domain.
I have gone through documents on Node Manager and found what to configure. But I have not found when to configure. In other words I want to know what is the sequence of steps if I have to set Node Manager on my local machine (in which domain exists) and on remote machine.
Please let me know the sequence of steps I need to follow to set and configure the Node Manager on local and remote machine. I want to use Java Node Manager (not the Script node manager).
Thanks,
Sanjay

Hello,
Ok, let me tell you what I have done till now.
1) Installed WebLogic 10.3 on machine A (local machine, on which I have created domain and my Admin Server is running. Also Managed Server 1 is created on this machine).
2) Installed WebLogic 10.3 on machine B (remote machine, on which Managed Server 2 will be created).
3) On machine A I used the configuration wizard and create a domain. While creating the domain I did the following:
i) Created two managed servers.
ii) Created a cluster
iii) Assigned Servers to cluster.
iv) Created two machines.
v) Assigned servers to machines (Admin Server and MS_1 to machine A and MS_2 to machine B).
4) Sarted Admin Server.
5) On the Admin Console I made some configurations for the Node Manager on Machines -> Machine A -> Node Manager. Assigned the values:
i) Type (SSL)
ii) Listen Address (IP_Address of machine A)
iii) Listen Port (5556)
6) Similarly did for Machine B.
So till now phsically the managed server (MS_2) directory and configuration is not there on Machine B (its only configured on machine A because I created the domain on Machine A).
Now I want install/configure/setup NM on both the machines. Start my both the managed servers using Admin Console (which will use the node managers).
What are the sequence of steps I need to follow my task?
Any help and suggestions are welcome with warm regards.
Thanks,
Sanjay

For server Eagle-PROD-Instance, the Node Manager associated with machine

I have a wlst script that creates a domain and a managed server. I associate the server with a machine that's attached to a node manager. It creates the managed server fine but when I try and start it I get this error
For server Eagle-PROD-Instance, the Node Manager associated with machine Eagle-Machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
The machine is associated with the Node Manager and the NM is running. I can start the managed server from the command line, but not from the admin console
This is the script, am I missing something?
Thanks
name: createManagedServer.py
description: This script create the weblogic domain, and executes each weblogic queue module
subfile. it reads a property file : weblogic_wlst.properties for server domain information
author     : mike reynolds - edifecs 2011
created     : April 8th 2011
import sys
from java.lang import System
from java.util import Properties
from java.io import FileInputStream
from java.io import File
from weblogic.management.security.authentication import UserEditorMBean
from weblogic.management.security.authentication import GroupEditorMBean
from weblogic.management.security.authentication import UserPasswordEditorMBean
# Loads the contents a properties file into a java.util.Properties
# configPropFile = "weblogic_wlst.properties"
def loadPropertiesFromFile(configPropFile):
     configProps = Properties()
     propInputStream = FileInputStream(configPropFile)
     configProps.load(propInputStream)
     propInputStream.close()
     return configProps
def getProperties():
     importConfigFile = sys.argv[1]
     print importConfigFile
     domainProps = loadPropertiesFromFile(importConfigFile)
     properties = Properties()
     input = FileInputStream(importConfigFile)
     properties.load(input)
     input.close()
     return properties
def create_users(username, password, description):
# create admin user
cmo.getFileRealms()
try:
userObject=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject.createUser(username,password,description)
print "Created user " + username + "successfully"
except:
print "check to see if user " + username + " exists "
def add_user_to_group(username):
print "Adding a user to group ..."
cmo.getFileRealms()
try:
userObject2 = cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject2.addMemberToGroup('Administrators',username)
print "Done adding user " + username
except:
print "check to see if user " + username + " is already in group "
def connect_server(user,pw,url):
          connect(user,pw,url)
def create_machine():
try:
print 'Creating machine' + machine
# cd('/')
# create(machine, 'Machine')
mach = cmo.createUnixMachine(machine)
mach.setPostBindUIDEnabled(true)
mach.setPostBindUID('oracle')
mach.setPostBindGIDEnabled(true)
mach.setPostBindGID('oracle')
mach.getNodeManager().setNMType('ssl')
except:
     print "machine exists"
def build_domain():
### Read Basic Template
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
readTemplate(WL_HOME+"/common/templates/domains/wls.jar")
template=WL_HOME+"/common/templates/domains/wls.jar"
cd('Servers/AdminServer')
set('ListenAddress', adminServerAddress)
set('ListenPort', int(adminServerPort))
cd('/')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('w3bl0g1c')
### Write Domain
setOption('OverwriteDomain', 'true')
print "writing domain " + domainDir + domainName
writeDomain(domainDir+'/'+domainName)
closeTemplate()
create_machine()
arg = "Arguments=\" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -da\""
prps = makePropertiesObject (arg)
domain = domainDir + domainName
try:
     #startNodeManager()
#nmConnect('weblogic', 'w3bl0g1c', host, 5556, 'AdminServer', domain, 'ssl')
# nmStart('AdminServer')
startServer('AdminServer', domainName, url, adminUser, adminPassword, domainDir, 'true')
except:
print "could not connect to Node Manager"
def create_server():
# get server instance properties
name = properties.getProperty("serverName")
domain = properties.getProperty("domainName")
port = properties.getProperty("listenPort")
address = properties.getProperty("listenAddress")
servermb=getMBean("Servers/" + name)
machine = properties.getProperty("machineName")
nodePort = properties.getProperty("nodeManagerPort")
domainDir = properties.getProperty("domainDir")
if servermb is None:
          startEdit()
          cd('/')
          cmo.createServer(name)
          cd('/Servers/'+ name)
          cmo.setListenAddress(address)
          cmo.setListenPort(int(port))
          cd('/')
          cmo.createMachine(machine)
          cd('/Machines/' + machine + '/NodeManager/' + machine )
          cmo.setNMType('Plain')
          cmo.setListenAddress(address)
          cmo.setListenPort(int(nodePort))
          cmo.setDebugEnabled(false)
          cd('/Servers/' + name)
          cmo.setListenPortEnabled(true)
          cmo.setJavaCompiler('javac')
          cmo.setClientCertProxyEnabled(false)
          cmo.setMachine(getMBean('/Machines/' + machine ))
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cd('/Servers/' + name + '/ServerDiagnosticConfig/' + name)
          cmo.setWLDFDiagnosticVolume('Low')
          cd('/Servers/' + name)
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cmo.setEnabled(false)
### Executable Script
### CreateDomain.py
### Define constants
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
print "Starting the script ..."
print "Getting properties ... "
properties = getProperties()
adminServerAddress = properties.getProperty("adminServerAddress")
adminServerPort = properties.getProperty("adminServerPort")
adminUser = properties.getProperty("adminUser")
adminPassword = properties.getProperty("adminPassword")
edifecsUser = properties.getProperty("edifecsUser")
edifecsPassword = properties.getProperty("edifecsPassword")
host = properties.getProperty("host")
domainDir = properties.getProperty("domainDir")
domainName = properties.getProperty("domainName")
user = properties.getProperty("username")
pw = properties.getProperty("passwd")
url = properties.getProperty("adminURL")
machine = properties.getProperty("machineName")
print "Building the domain..."
build_domain()
print "Connecting to server"
connect_server(adminUser, adminPassword, url)
edit()
startEdit()
# create managed server
# create_machine()
create_server()
print "Creating users"
# starting configuration tree
serverConfig()
create_users(adminUser, adminPassword, "Administrator")
add_user_to_group(adminUser)
create_users(edifecsUser, edifecsPassword,"Administrator")
add_user_to_group(edifecsUser)
# have to restart edit to save config
edit()
startEdit()
# nmKill('AdminServer')
print "saving configuration"
try:
     save()
     activate(block="true")
     print "script returns SUCCESS"
     print "admin server is running"
     print "starting server " + name
     startServer(domainName, name ,url,adminUser, adminPassword, domainDir,'true')
except:
     print "failed to save server"
     dumpStack()

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

Query regarding the Node manager configuration(WLS and OAM Managed server)

Query regarding the Node manager configuration(WLS and OAM Managed server):
1) In the nodemanager.properties I have added the ListenAddress:myMachineName and ListenPort: 5556
My setup : One physical Linux machine(myMachineName) has : WLS admin server, managed server(OAM 11G) and nodemanager.No clustered environment.
2) nodemanager.log has the following exception when I start the oam_server1 using EM(Enterprise Manager11g):
Mar 23 2012 1:39:55 AM> <SEVERE> <Fatal error in node manager server>
java.net.BindException: Address already in use
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:336)
at java.net.ServerSocket.bind(ServerSocket.java:336)
at javax.net.ssl.impl.SSLServerSocketImpl.bind(Unknown Source)
at java.net.ServerSocket.<init>(ServerSocket.java:202)
at javax.net.ssl.SSLServerSocket.<init>(SSLServerSocket.java:125)
at javax.net.ssl.impl.SSLServerSocketImpl.<init>(Unknown Source)
at javax.net.ssl.impl.SSLServerSocketFactoryImpl.createServerSocket(Unknown Source)
Default port on which node manager listen for requests is localhost:5556.I have changed it to point to my machine. The port should be of WLS admin server or it should be the managed server port?
3) I have started the NodeManager using the startNodeManager.sh script.
4) The admin server port is 7001 and the oam managed server port is 14100.
Any inputs on what might be wrong in the setup will be helpful.Thanks !

By using netstat -anp|grep 5556 you can check which process on your machine is using the 5556 port.

What is Node Manager ?

Similar Messages

Maybe you are looking for