Control Admin Server Using Node Manager and WLST

Control AdminServer with Node manager in WLST

Hey all, here we are going to know about the start and stop of admin server with node manager nm commands using WLST.

Controlling WebLogic Servers with Node Manager using WLST

 Here are the brief steps we are going to follow.

1.    Start Node manager        -  startNodeManager()
2.  Connect to node manger   - nmConnect()
3.Connect and Enroll to admin server    - connect() ,nmEnroll()
4.Start and Stop admin server            - nmStart(),nmKill()
        -

Step 1: Start Node Manager

Start Node Manager using below command. Provide the argument values from “nodemanager.properties” file under node manger home

wls:/offline> startNodeManager(verbose='true', NodeManagerHome='/u01/app/oracle/fmw/demodomain/nodemanager',
ListenPort='5557',ListenAddress='192.168.33.100')

StartNodeManager

Step 2: Connect to node manager using WLST

Connect WLST offline and type help('nmConnect') to get syntax. Syntax:    nmConnect([username, password], [host], [port], [domainName], [domainDir], [nmType], [verbose])

wls:/offline> nmConnect('weblogic','Welcome1','192.168.33.100','5557','demodomain', nmType='plain')
 Connecting to Node Manager ...

Successfully Connected to Node Manager.

nmConnect

Note :- If your node manager not already started nmConenct result following error.

STEP3: Connect to admin server and Enroll(One time activity)

NM connect result will be successful when admin server is running.

3.a. Connect

wls:/nm/demodomain> connect()
Please enter your username :weblogic
Please enter your password :Welcome1
Please enter your server URL [t3://localhost:7001] :t3://192.168.33.100:7001
t3://192.168.33.100:7001
Connecting to t3://192.168.33.100:7001 with userid weblogic ...
Successfully connected to Admin Server "demoadmin" that belongs to domain "demodomain".
Warning: An insecure protocol was used to connect to the server.
To ensure on-the-wire security, the SSL port or Admin port should be used instead.

3.b. Node Manager Enroll
Syntax : nmEnroll('c:/nmdomain')

wls:/demodomain/serverConfig/> nmEnroll('/u01/app/oracle/fmw/demodomain')
Enrolling this machine with the domain directory at /u01/app/oracle/fmw/demodomain ...Successfully
enrolled this machine with the domain directory at /u01/app/oracle/fmw/demodomain.

Step 4: Start and Stop admin server

Start Syntax: - nmStart('<ADMIN SERVER')

Stop Syntax:- nmKill('<ADMIN SERVER')

wls:/nm/demodomain> nmStart('demoadmin')
Starting server demoadmin ...
Successfully started server demoadmin ...

Terminating the admin server using nmKill() command in WLST

wls:/nm/demodomain> nmKill('demoadmin')
Killing server demoadmin...
Successfully killed server demoadmin..

nmStart and nmStop

Configuring Node Manger and Machine

To configure Node manager we need to configure the Machine on the WebLogic domain. This machine can be defined with Name, type of the OS. Usually this OS type could be

1. Unix 
2. Virtual and
3. Others(non-Unix that is Windows).

Configuring Node Manager

You could configure a Node Manager in the WebLogic Domain can be of two types:

• Per Domain
• Per Machine

Here each one has its significance. Per domain is easy to maintain, when same machine is used for multiple WebLogic domains with different business environment then better to have per domain.

If all WebLogic domains related to same business unit then we can use per machine nodemanager. Example, Customer supporting domain, its OHS domain, integration domains we can use single nodemanager for all of them together. You need to ensure that nmErolled for all these domains.



Step2 :

Create Machine for Windows(Other ) and Unix

Creating Node Manager  on  Unix :

Creating Node Manager on  Windows

Node Manager Monitoring






Configuration of Node Manager properties :

Here I've Windows hosted Administration server and also I have VirtualBox having Guest OS as Precise64 which is Ubuntu Linux. So I configured two managed servers assigned in the Windows and two more in the Linux box. The final summary of machines in the domain are as follows:



Machines summary details

Select the Machine and assign the servers



Add Managed Servers .



From Admin console click on Machines  Select Servers Tab > add button in the Work area.



Select above created Machine and click Add . Select the Managed server from DropDown.

Similar  add Managed Servers to Unix Machine .

After Adding the Machines Go to the Summary

Managed Serves Summary

Start Run the Managed serves .. If the

Status of the Node Manager is Inactive  verify  Node Manager properties and update the values :

Make sure

ListenAddress  = <Host Name >  replace LocalHost to <HostName>

SecurListener = False      < Replace from True > 

Starting NodeManager from Domain bin directory

Configuring Node manager properties on a machine

Manager Server can Start even it is in Failed NOT Restartable  status using the Node Manager

Server status FAILED_NOT_RESTARTABLE

Node Manger creates Boot Identity for every WebLogic server that is controlled by Node Manager .

Node manager  monitor and creates process Id contain file .