Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
6 views3 pages

Admin Server

The document provides an overview of the Admin Server, a Java Virtual Machine (JVM) process essential for managing domains. It details the server's configuration, starting and stopping procedures, and methods for checking its status and browsing the Admin Console. Key tasks include configuration changes and control changes, all performed through the Admin Console or Weblogic Scripting Tool (WLST).

Uploaded by

Devaraja K N
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
6 views3 pages

Admin Server

The document provides an overview of the Admin Server, a Java Virtual Machine (JVM) process essential for managing domains. It details the server's configuration, starting and stopping procedures, and methods for checking its status and browsing the Admin Console. Key tasks include configuration changes and control changes, all performed through the Admin Console or Weblogic Scripting Tool (WLST).

Uploaded by

Devaraja K N
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

Admin Server

Tuesday, September 16, 2014 7:24 PM

Agenda:

a. Admin Server Arch


b. Introduction Admin Server
c. Configuration of Admin Server
d. Port Numbers of Admin Server
e. Starting Admin Server
f. Checking the status of AS
g. Browsing the Admin Server

DEV_IVR_Domain

AS NM

Introduction to Admin Server:

Admin Servers is a JVM Process.

JVM Process:

It’s a Java Virtual Machine, where the java codes would be processed using the same. So Admin server is the first JVM
Process which we will discuss about.

Admin Server gets created with every domain.

Admin Server takes care of the entire domain/domains.

Admin Server uses two methods to take care of the domain.

Admin Server

Admin Console Weblogic Scripting Tool (WLST)

When you start the Admin Server the admin server establish with unique port numbers. HTTP & HTTPS. Using those port
numbers you can access the Admin Console or WLST.

Using Admin console or WLST you can perform two major task:

Configuration Changes:

Creating Managed Server:


Configuring Port number:
Conf, SSL:
Creating Clusters:
So n so..

Control Changes:

WLS L2 - Temp Page 1


Control Changes:

Stopping / Starting / Restarting / Admin mode.

Note: All the above can be done to that particular domain which your Admin Console points to.

Checking the configuration of Admin Server:

Admin Server & Managed Server: all the configuration regarding to that domain would be under Domain_home/config/

Checking the configuration of Admin Server:


[root@localhost domains]# less /opt/Oracle/Middleware/Oracle_Home/user_projects/domains/Dev_Phonebanking/config /config.xml

This file, starts with Security configuration, and then it goes to the username and password and it goes to port number of
each JVM process which we have configured with the domain.
<server>
<name>AdminServer</name>
<ssl>
<name>AdminServer</name>
<enabled>true</enabled>
<listen-port>8002</listen-port>
</ssl>
<listen-port>8001</listen-port>
<listen-address/>
</server>

Note: Sometimes the server will be admin server and there won't be a listen-port defined. It means it's using the default port
number.

Start the Admin Server:


[wlsuser@wls-node40 bin]$ cd /opt/Oracle/Middleware/Oracle_Home/user_projects/domains/Dev_Phonebanking/bin
[root@localhost bin]# nohup ./startWebLogic.sh &

Where,

Nohup will push the output of this command to a nohup.out file and "&" will push this command as a bg process.

To check the status of startup of weblogic Admin Server, tail -f nohup.out


Alternatively you can check the logs of the weblogic Admin server for that domain under.

tail -f Domain_Home/servers/AdminServer/logs/AdminServer.log

Note: You can run the same command in all the domains which you have created. But remember if it’s a dev mode on the
domain it would start without any error because there is no security for starting or stopping JVM process.

Stop The Weblogic Admin Server:


[root@wls-node40 bin]# ./stopWebLogic.sh

Browse the running Admin Server:

Making a URL:
<Protocol>://<SN/HN/DN>:<Port>/<Context Root>
http://wls-node40:8001/console

WLS L2 - Temp Page 2


Making a URL:
<Protocol>://<SN/HN/DN>:<Port>/<Context Root>
http://wls-node40:8001/console
http://wls-node40:7001/console

WLS L2 - Temp Page 3

You might also like