Run Weblogic in Production mode

I always go with the default installation of Weblogic and always get the Sun JVM in Development mode. If you have installed Weblogic in Development mode but want to run it in the Production mode, its very simple. Start the weblogic as follows:

$./ -Dweblogic.ProductionModeEnabled=true

The key-value pair “weblogic.ProductionModeEnabled=true” will start the weblogic server in Production mode. The key difference between Development mode and Production mode (by default, without any JDK installations specified in the installation) is that the Development mode runs with Sun JVM and Production mode runs with JRockit JVM.

JRockit is enhanced JVM and enhanced for its performance. Its one of the best and fastest JVM until now (as claimed by WL aka Oracle). If you install JRockit Mission Control, then you can measure the performance of your Weblogic server (JRockit also supports Sun JVM and other JVMs).

If you want to start Weblogic in the background and want to get the stdoutput in a log start it as follows:

$ nohup ./ -Dweblogic.ProductionModeEnabled=true &


Difference between DEV and PROD mode in Weblogic 10.3

Development mode
The default JDK for development domain is Sun Hotspot
You can use the demo certificates for SSL
Auto deployment is enabled
Server instances rotate their log files on startup
Admin Server uses an automatically created during startup
The default maximum capacity for JDBC Datasource is 15
The debugFlag which is used to start the WebLogic Workshop Debugger is enabled

Production mode
The default JDK for production domain is JRockit
If you use the demo certificates for SSL a warning is displayed
Auto deployment is disabled
Server instances rotate their log files when it reaches 5MB
Admin Server prompts for username and password during startup
The default maximum capacity for JDBC Datasource is 25
The debugFlag which is used to start the WebLogic Workshop Debugger is disabled.

Weblogic Server Basic Components

A Weblogic server domain is an administrative grouping of servers and/or clusters. You configure, manage, monitor the domain from central location; this central location is the administration (admin) server.

Admin Server
Admin server is just a Weblogic Server instance which maintains a repository of configuration information for the domain. Admin server acts as a centralized application deployment server which provides browser based admin console for configure, manage and monitor all aspects of the domain.

Managed Server
A Managed server is a term for any other server in the domain other than the admin server. Managed Servers host the components and associated resources that constitute your applications – for example, JSPs and EJBs. When a Managed Server starts up, it connects to the domain’s Administration Server to obtain configuration and deployment settings.

Two or more Managed Servers can be configured as a WebLogic Server cluster (more about this in next blog) to increase application scalability and availability. In a WebLogic Server cluster, most resources and services are deployed to each Managed Server (as opposed to a single Managed Server,) enabling failover and load balancing.

Node Manager
Node Manager is a Java utility that runs as separate process from WebLogic Server and allows you to perform common operations tasks for a Managed Server, regardless of its location with respect to its Administration Server. While use of Node Manager is optional, it provides valuable benefits if your WebLogic Server environment hosts applications with high availability requirements.

If you run Node Manager on a machine that hosts Managed Servers, you can start and stop the Managed Servers remotely using the Administration Console or from the command line. Node Manager can also automatically restart a Managed Server after an unexpected failure.

WebLogic Server Cluster
A WebLogic Server cluster consists of multiple WebLogic Server server instances running simultaneously and working together to provide increased scalability and reliability. A cluster appears to clients to be a single WebLogic Server instance. The server instances that constitute a cluster can run on the same machine, or be located on different machines. You can increase a cluster’s capacity by adding additional server instances to the cluster on an existing machine, or you can add machines to the cluster to host the incremental server instances. Each server instance in a cluster must run the same version of WebLogic Server.

How Does a Cluster Relate to a Domain?

  • A cluster is part of a particular WebLogic Server domain.
  • A domain is an interrelated set of WebLogic Server resources that are managed as a unit.
  • A domain includes one or more WebLogic Server instances, which can be clustered, non-clustered, or a combination of clustered and non-clustered instances.
  • A domain can include multiple clusters.
  • A domain also contains the application components deployed in the domain, and the resources and services required by those application components and the server instances in the domain.