OVERVIEW OF WEBLOGIC ADMINISTRATION

OBJECTIVES

 WLS INSTALLATION
 WLS DOMAINS
 NODEMANAGER
 SERVER LIFE CYCLE
 ADMIN CONSOLE

WLS INSTALLATION

THREE MODES OF INSTALLATION
 GRAPHICAL
 CONSOLE
 SILENT

GRAPHICAL
 Installation wizard takes you through the series of steps obtaining the configuration information required for installation.
Steps for installation:
 Download the software
//Windows:
 Go to the directory where you downloaded the installation program and double-click the installation file
//Unix:
 Launch the installation by entering the following command:
 chmod a+x filename.bin
./filename.bin


CONSOLE MODE

 Download the software as described
 Go to the directory in which you downloaded the installation program.
//Windows
 net_platformXXX_win32.exe -mode=console (net installer)
 platformXXX_win32.exe -mode=console (WebLogic Platform package installer)
 serverXXX_win32.exe -mode=console (WebLogic Server package installer)
(In these filenames, XXX represents the version number of the software you are installing)
//Unix
 chmod a+x filename.bin
./filename.bin -mode=console
Configuration Information
 BEA License Agreement
 Choose BEA Home Directory
 Choose Install Type
 Choose Components
 Specify Download Options
 Choose Product Directory
 Install as Services

SILENT MODE
 The installation program reads the settings for configuration from an XML file
Steps:
 Create a template file that defines the configuration settings
 Start Installation using the following command
Windows:
filename.exe -mode=silent –silent_ xml=/path_to_silent.xml
Unix:
chmod a+x filename
./filename.bin -mode=silent -silent_xml=/path_to_silent.xml

WLS DOMAINS
What?
How?

WLS DOMAINS – What?
 basic administrative unit for a WebLogic Server installation
 logically related group of WebLogic Server resources that you manage as a unit.
 Administration Server serves as a central point of contact
 include additional WebLogic Server instances called Managed Servers
 domain's configuration is stored in a separate configuration file called config.xml
 can include multiple WebLogic Server clusters and non-clustered WebLogic Server instances

Components of Weblogic Server Domain
 Servers
 Clusters
 Machine
 Deployments
 Applications
 EJB Modules
 Web Application Modules
 Connector Modules
 Services
 JDBC
 JMS
 Virtual Hosts
 Mail

Creating a new Domain

 Using the Configuration Wizard
 weblogic.Server Command
 Using Ant Tasks

Note: A domain can be created either in development or production mode.
Development mode uses a relaxed security configuration and enables you to auto-deploy applications.
A production domain uses full security and may use clusters or other advanced features

NODE MANAGER
 Java utility that runs as separate process from WebLogic Server
 can start and stop the Managed Servers remotely using the Administration Console or from the command line
 automatically restart a Managed Server after an unexpected failure.
 Monitor the self-reported health of Managed Servers and automatically kill server instances whose health state is "failed“
 Default Configuration for Nodemanager exists and it can be directly started by executing the startNodeManager script.

Configure Nodemanager in production Environment
Production Environment:
 nodemanager.hosts - IP address or DNS name entries are made
 Configure a Machine - for Node Manager to accept commands from remote Administration Servers
 Configure SSL – for secure communication b/w nodemanager -admin server and nodemanager - managed servers
 nodemanager.properties –
 SSL properties
 Non-SSL properties

SERVER LIFECYCLE

Server States
 SHUTDOWN
- a server instance is configured but inactive

 STARTING
- a server instance prepares itself to accept requests and perform application processing
- it retrieves its configuration data
- starts its kernel-level services
- initializes subsystem-level services
- deploys applications
- loads and runs startup classes

 STANDBY
- a server has initialized all of its services and internal applications (such as the Administration Console)
- can accept administration commands
- can participate in cluster communication
- does not accept requests from external clients.

 RESUMING
- to bring back the server to running state from stand by state

 RUNNING
- it offers its services to clients
- can operate as a full member of a cluster

 SUSPENDING
- server handles a predefined portion of the work that is currently in process—referred to as "in-flight" work
- Upon completion of in-flight work, the server progresses from the SUSPENDING state to the SHUTTING_DOWN state.

 SHUTDOWN
- a result of a graceful shutdown or forced shutdown process

 FAILED
- one or more critical subsystems have failed, the server instance sets its state to FAILED

 UNKNOWN
- If a server instance cannot be contacted, it is in the UNKNOWN state.

ADMIN CONSOLE
 graphical user interface you use to manage a WebLogic Server domain
Uses of Administration Console:

 Configure, start, and stop WebLogic Server Instances

 Configure WebLogic Server Clusters

 Configure WebLogic Server Services, such as database connectivity (JDBC), and messaging (JMS).

 Configure security parameters, including managing users, groups, and roles.

 Configure and Deploy your applications.

 Monitor server and application performance.

 View server and domain log files.

 View application deployment descriptors.

 Edit selected runtime application deployment descriptor elements.

ADMIN CONSOLE VIEW
ADMIN CONSOLE VIEW depends on the security role granted to the user
The four global roles are as follows:

1.Admin
 View the server configuration, including the encrypted value of encrypted attributes.
 Modify the entire server configuration.
 Deploy enterprise applications, startup and shutdown classes, and Web application, EJB, J2EE Connector, Web Service, and WebLogic Tuxedo Connector components. If applicable, edit deployment descriptors.
 Start, resume, and stop servers by default.

2. Deployer
 View the server configuration, except for encrypted attributes.
 Change startup and shutdown classes, Web applications, JDBC data pool connections, EJB, J2EE Connector, Web Service, and WebLogic Tuxedo Connector components. If applicable, edit deployment descriptors.

3. Monitor
 View the server configuration, except for encrypted attributes.
 This security role effectively provides read-only access to the WebLogic Server Administration Console, weblogic.Admin utility and MBean APIs.

4. Operator

 View the server configuration, except for encrypted attributes.
 Start, resume, and stop servers by default.