Friday, April 5, 2013

Installing node manager as a Windows service

To install node Manager as a Windows service you should perform following steps:

Step 1 - Install Node Manager as Windows Service:
Execute the following script: FMW_HOME/WL_HOME/server/bin/installNodeMgrSvc.cmd (by example C:\Oracle\Middleware\wlserver_10.3\server\bin\installNodeMgrSvc.cmd).
This should create a Windows Service called "Oracle WebLogic NodeManager (PATH_TO_DOMAIN)". Go to Windows Services and double click it. On the Log On tab, check the option "This Account" and provide the user/password you plan to use to run the WLS under windows.
Click OK and start the service, and next st op the service. This should create default node manager configuration files you could modify in next step.

Step 2 - Configure Node Manager Properties File:
Go to FMW_HOME/WL_HOME/common/nodemanager folder (by example C:\Oracle\Middleware\wlserver_10.3\common\nodemanager) and open nodemanager.properties file. Change the following properties to:

SecureListener=false
//If set to true, use the SSL listener, otherwise use the plain socket. There is better solution to set this to false, especially when you start to deal with nodemanager.

CrashRecoveryEnabled=true
//The CrashRecoveryEnabled configuration property allows Node Manager to restart servers after a system crash. The property is not enabled by default.

StartScriptEnabled=true

Finally you can start nodemanager service once again.

If you are trying to automate the environment using Node Manager and WLST and you are trying to Start the Admin Server and all the Managed Server using WLST only. And the Managed servers are to be started for the first time using WLST and Node Manager then you may encounter the below error :

<Feb 21, 2013 5:39:56 AM PST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: 

There are 1 nested errors:

weblogic.management.ManagementException: Booting as admin server, but servername, UCM_server1, does not match the admin server name, AdminServer
    at weblogic.management.provider.internal.RuntimeAccessService.start(RuntimeAccessService.java:67)
    at weblogic.t3.srvr.ServerServicesManager.startService(ServerServicesManager.java:461)
    at weblogic.t3.srvr.ServerServicesManager.startInStandbyState(ServerServicesManager.java:166)
    at weblogic.t3.srvr.T3Srvr.initializeStandby(T3Srvr.java:881)
    at weblogic.t3.srvr.T3Srvr.startup(T3Srvr.java:568)
    at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:469)
    at weblogic.Server.main(Server.java:71)

> 


Cause :

The reason for the above error is that when the Managed Server are to be started for the first time using the Node Manager and WLST,  the boot.properties file ( at %domain_home%/servers/ManagedServer/security/) and startup.properties file ( %domain_home%/servers/ManagedServer/data/NodeManager/) should be already present.
Solution :

To generate the boot.properties file , and startup.properties file use the below WLST command :

nmGenBootStartupProps('NameOfManagedServer') 



wls:/SEOD/serverConfig> nmGenBootStartupProps('UCM_server1')

Successfully generated boot.properties at C:\Users\Administrator\Desktop\servers

\UCM_server1\data\nodemanager\boot.properties.

Successfully generated startup.properties at C:\Users\Administrator\Desktop\serv

ers\UCM_server1\data\nodemanager\startup.properties.

1 comment:

  1. Hi, Great.. Tutorial is just awesome..It is really helpful for a newbie like me.. I am a regular follower of your blog. Really very informative post you shared here. Kindly keep blogging. If anyone wants to become a Java developer learn from Java Training in Chennai. or learn thru Java EE Online Training from India . Nowadays Java has tons of job opportunities on various vertical industry.

    ReplyDelete