Configuring Managed Servers in Weblogic Administration Console

Start weblogic Administration console by using startWebLogic.cmd in command prompt.Directory: Oracle\Middleware\user_projects\domains\Test_Domain\startWebLogic.cmdOpen the weblogic Administration console with http://localhost:7001/console by using login credentials.
Adminserver is in running mode.

Creation of new Managed server in Admin console:

In the administration console under Domain Structure (Eg : base_doamin) as per in below screen, expand Environment (by clicking the + next to it). Then click Servers à New

Enter new server details such as Name, Server Listen Address, Server Listen Port (Unique) and click “Next”

Here overview of new server details appears and click “Finish”

How to start Managed server:

Open cmd prompt navigate to E:\Oracle_Madhavi\Middleware\user_projects\domains\base_domain\bin> startMangedWeblogic.cmd ms1 t3://192.168.1.2:7001

Creating machines:

Machine is logical representation of physical machine.

We will assign managed servers with Machines. Once we assign the managed servers with the machine we can start and stop the servers through administration console.

Each machine is having one node manager.

Node manager is a java service .it will start and stop and monitoring the servers under that machine.

Nodemanger default port is 5556

Below screen shows machine not assigned to managed server (ms1).

New machine creation :

Click “Machine” in Domain structure. Then click “New”

Enter new machine details such as Name, click “Next”

Providing the Node Manager Properties:

Default Node manager Listen Port: 5556. Click “Finish”

New machine successfully created.

Click on machine1

Setting of machine1 appears.

Navigate to servers.

Click “Add” and select managed server (ms1). Click on finish

Navigate to servers try to start server.

Giving error as Node manager is not reachable, so needs to start node manager service.

Navigate to Machineà m1à Monitoring.

Node manager status showing “Inactive”.

When nodemanger is inactive need to start the nodmenager.

To start nodemanger
Navigate to weblogic_home\server\bin>startNodeManger.cmd <nodemanger hostname> <nodemanger portnumber>

Eg : Startnodemagner.cmd  192.168.1.2 5556

It saying already in use JVM_BIND means port is using already

Navigate to “Services.msc” in command prompt and already one Nodemanger service is running.

 Stop the service and run Nodemanger through cmd prompt again.

Now it’s in “Reachable” mode.

Creating Nodmemanger service:

Navigate to weblogic_home/server/bin> run installNodeMgrSvc.cmd

Navigate to serversà control à start the ms

Managed server is in Starting mode

After few minutes its changed to “Running” mode.