WEBLOGIC COMMON

Managed Weblogic Server

Weblogic Managed Servers:

In this post I will be providing some basic idea about the Weblogic Domain and its component called Managed Weblogic Server.

What is Weblogic Domain?

A domain is the basic administration unit for WebLogic Server instances. A domain consists of one or more WebLogic Server instances (and their associated resources such as JDBC resource or JMS resource) that can be managed with a single Administration Server.

A minimal domain can contain only one WebLogic Server instance, which functions both as an Administration Server, and as a Managed server. This instance is called as Weblogic Administration Server or Weblogic Admin Sever.

As it is the only instance present in domain so this Weblogic Admin Server can also be used as Managed Weblogic Server.

Below figure Fig.1 , shows a minimal Weblogic domain containing only one Admin Server.

Fig.1 Weblogic domain with Admin Server only.

Till now I hope, the concept of Weblogic Domain is clear.

As terms Weblogic Admin Server and Weblogic Managed Server has been used, let me explain each of them separately.

Weblogic Admin Server OR Weblogic Administration Server:

The minimum requirement for a Weblogic Domain to exist is that it must contain one Administration Server. This Weblogic Server Instance is basically used for the Administrative purpose of complete Weblogic domain.

This Admin Server can also be used for the purpose of deployment of applications along with Administrative purpose and in that case the Admin Server is acting as Managed Weblogic Server instance.

Managed Weblogic Server:

Any other server instance other than Administrative Server of a Weblogic domain is called as Managed Weblogic Server. Managed Servers host the components and associated resources that constitute the applications—for example, JSPs and EJBs.

Below figure Fig. 2 Shows A Weblogic Domain with 1 Admin Server and 1 Managed Server on a Single Machine.

Fig.2 Weblogic domain with Admin Server and one Managed Server.

How to change the Integrated Weblogic Port number

here came a situation where I wanted to work with two JDevelopers simultaneously and start two different applications in two JDEVs. 

(Both of them have to in separate installation location, else it will create a problem because of system directory).

Now, when we want to start WLS in JDEV, only the first one will be started and the other one fails with an exception of port conflict. Until few days back, $1million dollar question was how to change the integrated WLS port number?

So, heres the answer after some R&D. In the view menu, click on “Application Server Navigator”. Right click on Integrated Weblogic server.

1) If it is the first time that you are trying to start the server, then there is a menu “Create Default Domain”. If you click on this, a window will be displayed where it asks for the preferred port number. Change it here.

2) If the domain is already created, then click on Properties and change the preferred port number.

Again, if you want to change the port before starting JDEV from the file system, then goto 

$JDEV_USER_HOME/systemxxx/o.j2ee and open the file adrs-instances.xml and change the http-port in the startup-preferences:

<hash n=”startup-preferences”>

   <value n=”http-port” v=”7111″/>

</hash>

Note 1: adrs-instances.xml will be created ONLY after you create the default domain.

Note 2: systemxxx – refers to system.<JDEV version> like system.11.1.1.3.56.59 for PS2.

Note 3: $JDEV_USER_HOME – in windows – would be C:\Documents and Settings\

[user_name]\Application Data\JDeveloper”

Now, you can run multiple Integrated WLS simultaneously. But please be aware that running more than one WLS server will degrade system performance.