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 Managed Servers

In WebLogic we have three choices for Configuring the Managed servers.

1.  Admin console . 
2. config.sh / config.cmd ( configuration wizard) 
3. WLST 

1. Using Administration console

1. Log in to admin console with your credentials
2. In the Left pane, expand the Environment in the Domain Structure > select the Server  
3. In the work-area that right side, click on the New button to Creating the Managed Servers 

Adding New managed server -  Click on New button

Update the New Managed server attribute values

Summary of Servers - Newly created managed server visible

 when does the managed server named directory will be created?
Lets check the servers directory in the domain directory... Here no new server name it will not created when it is configured.It will be

WebLogic Domain directory

Starting of Managed Servers  Syntax

Here I have a Linux environment where I can use startManagedServer.sh for those who are using Windows platform can use startManagedServer.cmd.

 vagrant@precise64:~/wlsdomain/Demo2_Domain/bin$ ./startManagedWebLogic.sh Demo2_MS1 http://192.168.33.10:8001
 

Managed servers directory will be created after First Time it Started.

2. Using the configuration Wizard to create Managed servers

To invoke the configuration Wizard we have to navigate to $WL_HOME/common/bin directory.
To run the wizard in Windows platform you have to use config.cmd script and in the Unix platform config.sh provided that platform must support X-Windows (X11 forwarding).

Here, I have Windows sample:

Invoking WebLogic domain Configuration Wizard

Configuration Wizard Choose existing Domain 

Select the Managed Servers for configuration

Add the Managed Servers - provide Name, Listen Address, Port

Skip Cluster, Machine Configurations

Configuration Summary - Added two managed servers to Domain Demo1

Configuration Progress

Finally Successful configuration changes to the Demo1 Domain 

3. Create Managed Server using WLST

Ref: Create Online managed server