Working with Managed Servers

(1)

1

.

Working with Managed Servers

At the end of this module you will be able to:

9 Administer servers and managed servers

9 Configure domains, machines, and managed

servers

9 Start managed servers at boot time

9 Describe simple logging

Working with Managed Servers-1 Working with Managed Servers-1

This module provides additional details about configuring and running BEA WebLogic Server (WLS) so that you will be able to administer WLS in a 24/7 environment. This module augments the Basic

WebLogic Server Administration (BWLA) module and provides advanced information for system administrators.

(2)

2 BEA Certified Administrator 8.1: Exam Preparation Course

-System Administrator Working with Managed Servers

.

Road Map

1. Configuring Domains

–

How Weblogic Server Domains Work

–

The Domain Directory Structure and Files

–

Creating a Domain

2. Configuring Servers

3. Logs and Monitoring

(3)

3

.

f

A

WebLogic Server Domain

is:

–

a self-contained administrative unit

–

an interrelated set of resources such as machines, servers

and clusters

–

managed by a single administration server

MyDomain

MyCluster MachineB

Server2 Server3

Server4

MachineA Server1

An interrelated set of WebLogic Server resources managed as a unit is called a domain. A domain includes one or more WebLogic Servers, and may include WebLogic Server clusters. Within WebLogic Server 8.1 all resources are managed, created, configured, destroyed and otherwise configured via domains.

(4)

.

What Is an Administration Server?

f

An

administration server

is:

–

the central point of control for a domain

–

the keeper of the XML configuration repository

–

a central source for logging information

MyDomain Administration Server Critical Domain Notifications (Logs) Configuration repository (config.xml) LOG LOG

XML

A WebLogic Server running the administration service is called an administration server. The administration server provides the central point of control for configuring and monitoring an entire domain. An administration server must be running in order to perform any management operation on a domain. In a configuration with multiple WebLogic Servers, only one server is the administration server; the other servers are called managed servers. Each managed server obtains its configuration at startup from the administration server.

The administration server maintains the complete configuration of the domain (for example, servers in the domain, clusters, connection pools, deployed applications) in a persistent repository called the

Configuration Repository. Currently, WebLogic Server only supports a persistent file repository called config.xml, but future releases of WebLogic Server will support property storage in an LDAP server, database or custom repository created by you.

(5)

5

.

f

A

managed server

:

–

is an instance of WebLogic Server

–

loads its configuration remotely from an administration

server

–

may or may not be part of a cluster

A managed server is simply a single server that boots on a remote, or perhaps the same, physical machine and loads its configuration from a specified administration server. Managed servers get all of their configuration information from the remote administration server and need only know the domain and server they represent in a domain.

Managed servers can be part of one or more clusters or they can be standalone. When you start a

WebLogic Server without specifying an administration server on the command line, the server will start as an administration server. When you specify an administration server on the command line, the new server will start as a managed server.

(6)

.

Domain Overview

Managed Server 2 Cluster Managed Server 1 Managed Server 3 Administration Server Domain Log Configuration Repository config.xml GET / SET

Get Configuration at Startup Critical Domain Notifications Domain Log Messages Monitor/ Update Domain Console

LOG

XML

Local Logging LOG Local Logging LOG Local Logging LOG

The diagram above shows the critical components of a domain. A domain is an arbitrary logical

administration unit managed by one administration server. A domain can encompass clusters in different geographies.

The administration server is responsible for providing the configurations for ALL servers of a specific domain and to log critical (configurable) notifications of the domain’s servers. The administration server is also responsible for monitoring a managed server. A managed server is responsible for performing the business logic.

A managed server gets its configuration from the administration server at boot time and the managed server is then able to execute independently of the administration server. The administration server registers itself with each managed server so that it can receive critical notifications and run-time server state changes. Note that the only configuration folders and files that play a role are those of the

administration servers. Managed servers’ configuration folders and files are ignored, because they download all configuration information from the administration server.

The configuration management is implemented through Java Management Extension (JMX). The communication between the managed servers and the administration server is via RMI also using JMX. Configuration is done through the Administration Console so knowledge of JMX is not required.

Note: The diagram in the slide is a simplification, all the servers would be monitored and updated from the

administration server. Also, all the managed servers retrieve their configuration information at start-up time and log critical data to the administration server.

(7)

7

.

f

Configuration wizard is a stand-alone Java app that can be run

independently of WLS to simplify the creation of domains.

f

8.1 configuration wizard is template-based.

f

A template is a jar file which contains the files and scripts

required to create or update a domain.

f

Types of templates:

– Configuration template: used to create a domain. Defines full set of services.

– Extension template: used to extend existing domain. Defines services and applications. For example, use it to add WLS platform components to your existing domain.

f

Can define your own custom /extension template using WLS

Configuration Template Builder.

(8)

.

Configuration Wizard

f

Creating Domain

–

Express Configuration: template settings cannot be modified.

–

Custom Configuration: when you need custom modification

on servers/clusters/machines, DB service or targets.

f

Extending Domain

–

Used to add a pre-defined application (e.g. WLS platform

component) or a set of services (JDBC, JMS) to an existing

domain.

–

Select the domain dir that you want to extend and identify

the extension template to include additional applications.

(9)

9

.

f

Used to create your own custom configuration or extension

templates.

f

To create a custom configuration template

– Select the original domain or configuration template and update • Basic template info

• App and domain dir contents

• Servers/clusters/machines

• JDBC/JMS/Target/Security/Environment and OS options

f

To create a custom extension template

– Select the original domain or extension template and update • Basic template info

• App dir contents

• JDBC/JMS/Security options

(10)

.

Starting Configuration wizard

f

Scripts in

/common/bin

Graphical mode

– Windows Start menu

– [Windows] config.cmdor

– [Unix] sh config.sh f

Console mode

– [Windows] config.cmd –mode=console

– [Unix] sh config.sh –mode=console f

Silent mode

– Create a silent-mode script (default: configscript.txt)

– [Windows] config.cmd –mode=silent silent_script=…] [-log=logfile]

– [Unix] sh config.sh –mode=silent silent_script=…] [-log=logfile]

(11)

11

.

f

Typically copy the contents of one of the sample

scripts to a text editor and edit it for your

configuration.

f

Steps

–

1. Select the configuration template

–

2. Edit the configuration information

–

3. Create the domain

–

4. Close the configuration template

(12)

.

/*Create a new domain from a configuration template */ read template from

"C:\bea\weblogic81\common\templates\domains\medrec.jar"; create User "user1" as u1;

set u1.Password "password";

//by default "user1" is in "Administrators" group unassign User "user1" from Group "Administrators"; assign User "user1" to Group "Deployers";

//creation of servers will trigger auto configuration create Server "myServer1" as s1;

set s1.ListenPort "8001"; set s1.SSL.Enabled "true"; set s1.SSL.ListenPort "8002";

// if you do not have applications, do not do assignments for them assign all Applications to Target "MedRecServer";

assign all Services to Target "MedRecServer, myServer1"; //JMSServer can’t be assigned by "assign all Services". assign JMSServer "*" to Target "myServer1";

set ServerStartMode "prod";

set JavaHome "C:\bea\jrockit81sp1_141_03"; set CreateStartMenu "false";

//no effect here since MedRec template does not specify app separation set AppDir "C:\bea\user_projects\applicationsmy\medrec";

write domain to "C:\bea\user_projects\domains\myMedrec"; close template;

Step 1

Step 2

Step 3

Step 4

Creating a script for creating a domain in

silent mode

(13)

13

.

(14)

.

Example: Creation of a domain

(15)

15

.

(16)

.

Validation in action

Example: Creation of a domain

(17)

17

.

(18)

.

Example: Creation of a domain

(19)

19

.

(20)

.

Example: Creation of a domain

(21)

21

.

(22)

.

Default for development mode is JDK141_02

Default for production mode is JRocket

Example: Creation of a domain

(23)

23

.

(24)

.

Example: Creation of a domain

(25)

25

.

Admin server can be started by the script or the startup menu

cd to domain dir. Run setenv.cmd then uses startmanagedweblogic.cmd script to start the managed servers.

Once the whole domain has been started up:

(26)

.

Proxying mechanism already setup

Example: Creation of a domain

(27)

27

.

Say you have created cluster1 and deployed some apps to the cluster. Now suppose your want to extend this domain…

(28)

.

Extending a domain using the

Config Wizard

f

Make sure domain is not active.

(29)

29

.

(30)

.

Extending a domain using the

Config Wizard

(31)

31

.

Update and you are done!

(32)

.

Bring up the domain and you’ll see…

Extending a domain using the

Config Wizard

(33)

33

.

f

Can only be invoked in GUI mode

f

Go to the

\common\bin

subdirectory of the product

installation directory. For example:

cd c:\bea\weblogic81\common\bin

f

Use

config_builder.cmd

or

sh config_builder.sh

to start the configuration template builder

(34)

.

Example: Creating a Configuration

Template

(35)

35

.

Wizard-generated

files are always in

./apps already

Your files are

imported to ./apps

(36)

.

Example: Creating a Configuration

Template

(37)

37

.

(38)

.

Example: Creating a Configuration

Template

(39)

39

.

(40)

.

To use the newly created template:

Example: Creating a Configuration

Template

(41)

41

.

9 How a WebLogic Server domain works

9 The domain directory structure

9 Domain files

9 How to create a domain

In this section we discussed:

(42)

.

Road Map

1. Configuring Domains

2. Configuring Servers

–

Creating Additional Managed Servers

–

Starting an Administration Server

–

Discovery Mode

–

Starting and Stopping Managed Servers

3. Logs and Monitoring

In this section we will discuss practical issues related to creating and starting Administration and managed servers. Operating system specifics related to boot-time startup configuration are also covered.

(43)

43

.

f

Additional servers can be defined:

3 2 1

4

To create a server:

1. Left-click on Serversin the left panel.

2. Select Create a new Server…in the right panel. 3. Specify the server information:

a name for the server.

a machine that it resides upon. We will be covering machines shortly and will revisit this

concept.

a valid listen port.

a DNS name or IP address that this server is bound to.

If using an alternate Web server (for example, Apache, Netscape) use this field to specify

the Web server’s plug-in address to allow WebLogic Server to forward requests to it.

4. Click the Create button to finish creating the server.

To create a new server within a given domain, select the domain\Serverselement in the left panel. Once selected, all known servers are displayed in the right pane. In the right panel choose Create a new Serverto display the new server page. The next slide shows the new server pane in detail. Alternately, you can right click over the domain\Serverselement in the left pane and choose Create a new Serverto display the new server page.

To create a new server, whether administration or managed, you must provide a number of fields. The Name field specifies the name that will be associated with the server and specified by the

weblogic.Nameproperty when starting the administration server. The Machine field specifies a machine to associate with this server. Machines are used to control the UID and GID under UNIX that this server will run under. The Listen Addressfield specifies the IP address that this server will listen on when started.

When defining administration servers, the Administration Portfield specifies the port that this server will listen on for administration requests.

Note: You can have many server instances bound to the same IP Address/Listen port pair but only one

(44)

.

Review: Starting an Admin. Server

f

An administration server:

–

is the default server if no management server parameter is

specified

–

loads all its configuration and security information locally

To start an administration server:

java -hotspot -Xms32m -Xmx200m -classpath "%CLASSPATH%" -Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:\bea" -Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy weblogic.Server 10 0101 1110

All entered on one line

An administration server is started when the weblogic.Servercommand is given without specifying a management server from which to load its configuration. For obvious reasons, the configuration information required to start the administration server is loaded locally. In order to correctly start an administration server, you must supply the domain to boot into and the server name. If you are entering the weblogic.Servercommand by hand, at the command line, your default directory should be the weblogic81directory. The script startWebLogic, provided in each domain in

user_projects\domains\somedomaindirectory executes the scriptstartWLSin the %WL_HOME%\server\bindirectory. The domain name and server name elements of the script are then used to correctly load the domain and server instance.

The required parameters to the weblogic.Servercommand to start an administration server are: weblogic.Name—The name of the administration server itself.

bea.home—The root directory of the BEA software tree.

java.security.policy—Complete path to a java security policy to be used by WLS.

WebLogic Server installs a defaultstartWebLogicscript in themydomaindirectory. This script can be used as a starting point for developing your own administration scripts.

When the administration server is started WebLogic Server makes a copy of the config.xmlfile and names it config.xml.booted. WebLogic Server actually uses the copy of the config.xmlfile for retrieving configuration information.

(45)

45

.

ServerA 192.168.1.2:7001 ServerB 192.168.1.3:7001 Cluster Proxy 192.168.1.4:7001 Admin Server 192.168.1.1:7001 192.168.1.1:7002 Domain Log Configuration Repository config.xml

GET / SET

Get configuration at startup (http/https)

Critical Domain Notifications

Domain

Get configuration at startup (http/https)

LOG

XML

Local Logging LOG Local Logging LOG Local Logging LOG

When you start a managed server you need to specify the administration server that is maintaining the configuration information for the managed server. The weblogic.Servercommand that allows managed servers to point to their administration server is

-Dweblogic.management.server. If you leave this command off, then by default you are starting the server as an administration server and not a managed server. In the above example, you would specify

-Dweblogic.management.server = http://192.168.1.1:7001 in the weblogic.Servercommand to start the managed servers.

You can also connect using HTTPS:

(46)

.

Starting Managed Servers

f

To start a managed server you must:

–

specify a server name

–

specify an administration server from which to load configuration

information

–

specify the administration server username and password

To start a managed server:

java -hotspot -Xms32m -Xmx200m -classpath "%CLASSPATH%" -Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:\bea" -Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% -Dweblogic.management.server=%ADMIN_URL% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy weblogic.Server 10 0101 1110 <startManagerWeblogic.cmd> 1 2

1. Specify the server name you want to start.

2. Specify the DNS name and listen port of the administration server. The managed server will get its configuration information from the administration server. The port is usually 7001.

Starting a managed server is much like starting an administration server with the exception that rather than loading the configuration from a local repository all information is loaded from a remote repository. Also, you do not need to specify a domain name when you start a managed server, it retrieves its domain name from the administration server. You must specify a number of properties in order to correctly load a managed server. As with administration servers, if you are entering the webLogic.Servercommand by hand at the command line, your default directory should be the weblogic81directory. The provided startManagedWeblogicscript starts a managed server based on the server name and administration server address, which are required parameters.

An example startManagedWebLogiccommand might be:

C:\bea\user_domains\WLSA11>startManagedWebLogic serverA admin:7001

As shown in the example above, the parameters required for the weblogic.Servercommand to start a managed server are:

• weblogic.Name—The name of the managed server configuration to load.

• bea.home—The root directory of the BEA software tree.

• java.security.policy—Complete path to a java security policy to be used by WebLogic Server.

• weblogic.management.server—The DNS name and port of the administration server to load the configuration from.

(47)

47

.

f

A new domain creates a number of files:

democert.pem demokey.pem startManagedWebLogic.cmd startWebLogic.cmd setenv.sh setenv.cmd logs applications MyNewDomain

Set environment variables for domain servers

Directory / File

Sample SSL support for servers in the domain

Start a Managed Server in a custom domain

BEA Home directory

Stores default Web Apps for servers in the domain

Description

Stores log files for servers in the domain

Start Administration Server for a custom domain

Sample SSL support for servers in the domain

Domains can be created using a Configuration Wizard only on the physical machine chosen for Administration Server.

The other servers in the domain called as Managed Servers download all the configuration from running Administration Server.

So all you require in a managed server machine is BEA product installation, the necessary start scripts, SSL file etc.

(48)

.

Creating a Boot Identity File

f

Create a file called

boot.properties

located in the

domain’s root directory containing 2 lines:

–

username=username

–

password=password

f

First time you start the server, the server reads the

Boot Identity file and overwrites it with an encrypted

version of the username and password.

f

Thereafter, the server will remember your identity for

the subsequent startup cycles.

The username and password can be stored in a file so that you do not need to log in every time you start the server. To do this place the following lines in a text file:

username=<username> password=<password>

The username must belong to a role that has permission to start a server. Do one of the following:

• Save the text file as <domain>\boot.properties

• Save the file under some other name or location and add the following argument to the set JAVA_OPTIONSdirective: -Dweblogic.system.BootIdentityFile=filename

For example:

set

JAVA_OPTIONS=-

Dweblogic.system.BootIdentityFile=c:\secure-directory\myBootIdentity

The boot identity file can also be created automatically during first server startup if you specify the following option in the start script of the server.

-Dweblogic.system.StoreBootIdentity=true

You will be prompted for the username and password for the first time if you don’t specify the username and password on the startup script.

(49)

49

.

f

By default, managed servers can function

independently of the administration server.

f

Configure

Managed

Server

Independence

Mode from

the Console:

Usually, when a Managed Server starts, it contacts the Administration Server to retrieve its configuration information and starts as a Dependent Server. If a Managed Server is unable to connect to the specified Administration Server during startup, it can retrieve its configuration by reading a configuration file and other files directly on the local file system.

A Managed Server that starts in this way is running in Managed Server Independence mode. In this mode, a server uses its cached application files to deploy the applications that are targeted to the server. You cannot change a Managed Server’s configuration until it is able to restore communication with the Administration Server.

Starting in Managed Server Independence Mode – If Managed Server Independence Mode is enabled (which is the default setting for a server), and if the Administration Server is unavailable, the Managed Server looks in its root directory for the following files:

• A configuration file (msi-config.xmlby default) • SerializedSystemIni.dat

• boot.properties(This is an optional file that contains an encrypted version of your username and password. For more information, refer to Bypassing the Interactive Prompt.)

(50)

.

…Managed Server Independence

f

If the administration server is unavailable at boot time,

managed servers search for:

–

msi-config.xml

–

SerializedSystemIni.dat

–

boot.properties(optional)

f

If managed servers do not share the root directory with

the admin server copy config files to managed server’s

directory and rename config.xml to msi-config.xml

–

specify location of files using –Dweblogic.

RootDirectory=path

By default, a server assumes that its root directory is the directory from which you issue the server startup command.

A Managed Server that runs in the same domain and on the same machine as the Administration Server shares its root directory with the Administration Server by default. If you start such a Managed Server, it will automatically find the configuration files.

For other Managed Servers, you can do any of the following:

• Copy the configuration files from the Administration Server's root directory (or from a backup) to the Managed Server's root directory. When you start the server, it will use the copied configuration files. • Use the -Dweblogic.RootDirectory=pathstartup option to specify a root directory that

already contains these files.

• If you enable replication of configuration data, as described in Replicating the Domain's Configuration Files, all of the necessary configuration files will already be in the server's default root directory. Any boot identity file, which is an optional file, is not replicated. You must copy it to the appropriate location.

In addition to the configuration files, a server must also have access to a security realm to complete its startup process.

If you use the default WebLogic Security Service, then the Administration Server maintains an LDAP server to store the domain's security data and all Managed Servers replicate this LDAP server. If you use this default service and the Administration Server fails, Managed Servers running in Managed Server Independence mode can use the replicated LDAP server for security services.

If you use a third party security provider, then the Managed Server must be able to access the security data before it can complete its startup process.

(51)

51

.

f

Administration servers can automatically copy

configuration files onto managed servers every 5

minutes.

Managed Server Independence mode includes an option that will copy the required configuration files into the Managed Server’s root directory every 5 minutes.

By default, a Managed Server does not replicate these files. Depending on your backup schemes and the frequency with which you update your domain’s configuration, this option might not be worth the performance cost of copying potentially large files across a network.

To enable a Managed Server to replicate the domain’s configuration files, do the following from the Administration Console:

1. Click the server node in the left pane and select a specific server in the left pane. 2. From the Configuration tab, click the Tuning tab.

(52)

.

Starting WebLogic Server at Boot

f

WebLogic Server can be configured to start at boot

time as:

–

a Windows service

–

a UNIX daemon

WebLogic Server, whether running individually or as part of a cluster, is normally started at machine boot time. In the event that a machine that is serving in a 24/7 environment reboots, it is critical that the

application server restart its services at boot time. Both Windows and the various flavors of UNIX support starting processes at boot time. Windows has an entire infrastructure built expressly for the purpose of controlling boot processes called Windows Services. Both Linux and Solaris also support starting daemons at boot time using rc scripts. While the two mechanisms are different, the end result is the same:

(53)

53

.

f

The Configuration Wizard can setup a default WLS as a

Windows service.

f

If you want a WebLogic Server as a Windows service

with custom settings you will need to edit and run the

script:

<domain>\installService.cmd

f

This script will setup the Administration server as

Windows service.

When you use the Configuration Wizard to create a domain and server, you can either specify that the wizard sets up the server as a Windows service or, after you finish the wizard, customize and use a script that the wizard creates.

If you use the Configuration Wizard to set up a Windows service, the service is subject to the following constraints:

• It will be namedbeasvc%SERVER_NAME%.

• The server will be started as an Administration Server and will use all default settings.

If you want your service to use custom settings, you can decline to have the wizard create the service for you and do the following instead:

1. After you finish the Configuration Wizard, navigate to the domain_namedirectory (where

domain_nameis the directory with your domain's configuration). For example, navigate to

C:\bea\user_projects\domains\humanresources. 2. Open domain_name\installService.cmdin a text editor. 3. Create and enter values for any of the optional variables

4. Save and runinstallService.cmd.

If the script runs successfully, its output in the command window includes a line similar to the following: beasvc myserver installed.

(54)

.

Setting Up Windows Services

f

The

beasvc.exe

utility supports installing Java

programs (e.g., WLS) as Windows Services.

Syntax:

%WL_HOME%\server\bin\beasvc.exe -install

-svcname displayName -javahome jdk1.4.1Home -execdir wlsInstallRoot -extrapath wlsBinDirectory -cmdline cmdToRun

displayName The name to associate with the service. jdk1.4.1Home Path to where the JDK 1.4.1 is installed.

wlsInstallRoot Root of the WLS install tree (i.e., c:\bea\weblogic81). wlsBinDirectory Path to the WLS \bin directory.

cmdToRun Java class to run as a service (e.g., weblogic.Server) including any parameters.

10 0101 1110

The Windows program beasvc.exe creates service entries in the registry which can then be treated as normal Windows services.

Services are installed by choosing a service name, setting various Java and run-time related parameters and then providing a command to be run by the BEA Service Manager program. By pairing different service names with different commands multiple instances of WebLogic Server can be configured to run at the same time.

Note: You do not use the javacommand to run this program.

An example of the complete command is shown below for a domain named WLSA11: cd C:\bea\user_projects\domains\humanresources

set CLASSPATH=.;C:\bea\weblogic81\server\lib\weblogic_sp.jar;

Set CLASSPATH=%CLASSPATH%;C:\bea\weblogic81\server\lib\weblogic.jar set CMDLINE="Xms32m Xmx64m classpath \"%CLASSPATH%\"

-Dweblogic.Name=studentA -Djava.security.policy==\"C:\bea\

weblogic81\server\lib\weblogic.policy\" -Dbea.home=\"C:\bea\" – Dweblogic.management.password=password weblogic.Server"

"C:\bea\ weblogic81\server\bin\beasvc" install svcname:studentA javahome:"C:\bea\jdk141_03" execdir:"C:\bea\weblogic81"

(55)

55

.

f

UNIX daemons are configured using

rc

scripts.

f

rc

scripts and the

init

process describe:

–

what is run and when

–

how the init

process reads

/etc/inittab

to determine

what run level to enter

–

what rc

scripts will be run as the machine enters and exits

each run level

Both Linux and Solaris, as well as other UNIX variants, use the concept of run levels for loading daemons. As a UNIX platform boots, it goes through a predefined sequence of run levels. At each level different processes are started or stopped depending on whether the machine is booting or shutting down. The root (parent) of all the processes is the init process which controls what run level the system will enter. Under both Solaris and Linux the run level is determined by examining the /etc/inittabfile. Under Linux, initexamines /etc/inittaband enters the run level specified by the id:line (normally the first line in the file). In addition, initstarts up a number of common processes. Level 3 and level 5 are commonly thought of as the multi-user run levels. Under Solaris, the run level to enter is specified by the is:x:initdefault:line (where xis the run level to enter). Again, this line is normally the first line in the /etc/inittabfile but it is not a requirement, it is more of a convention.

(56)

.

WLS Started!

WebLogic Server at Boot

f

WebLogic Server can be configured using two files for

boot control:

–

/etc/rc.d/init.d/weblogicd

–

/etc/rc.d/rc.wls

/etc/rc.d/rc5.d/S99wls start (ln –s ../weblogicd S99wls)

/etc/rc.d/rc.wls

(57)

57

.

f

Here is an example

rc

script to start and stop WLS 8.1

servers:

#!/bin/sh # $Id$ #

...environment variables definitions...see notes pages...

case "$1" in start)

java -hotspot -Xms32m -Xmx200m -classpath $CLASSPATH \ -Dweblogic.Name=$SERVER_NAME -Dbea.home="C:\bea" \ -Dweblogic.management.username=$WLS_USER \ -Dweblogic.management.password=$WLS_PW \ -Dweblogic.ProductionModeEnabled=$STARTMODE \ -Djava.security.policy=$WL_HOME/server/lib/weblogic.policy \ weblogic.Server ;; ... 10 0101 1110

Here are environment variables that the above rcscript depends on:

WL_PWD=weblogic # system password JAVA_HOME=/usr/jdk141_03 # Java Home

BEA_HOME=/opt/bea # A possible location for WLS on Solaris WL_HOME=$BEA_HOME/weblogic81 # The /weblogic700 directory

WL_LIB=$WL_HOME/lib # The /lib directory

WL_CONFIG=/usr/bea # The location of the /config directory # Add Solaris libraries (like native/io -- performance packs)

if [ -n "$LD_LIBRARY_PATH" ]; then

LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$WL_LIB/solaris:$WL_LIB/solaris/oci816_8 else LD_LIBRARY_PATH=$WL_LIB/solaris:$WL_LIB/solaris/oci816_8 fi PATH=$WL_HOME/lib/solaris:$PATH PATH=$WL_HOME/bin:$PATH PATH=$JAVA_HOME/jre/bin:$PATH PATH=$JAVA_HOME/bin:$PATH export LD_LIBRARY_PATH PATH CLASSPATH=$WL_HOME

CLASSPATH=$WL_LIB/weblogic_sp.jar:$CLASSPATH CLASSPATH=$WL_LIB/weblogic.jar:$CLASSPATH

(58)

.

…Example

rc

Scripts

case "$1" in

...

stop) java \

-classpath $CLASSPATH weblogic.Admin \ -url t3://localhost:7001 \

-username system -password $WL_PWD \

SHUTDOWN

;;

*)

echo "Usage: $0 {start|stop|restart}" exit 1 ;; esac 10 0101 1110

Under UNIX you have a variety of run levels. WebLogic generally starts at run level 3. In Solaris the initialization scripts for run level 3 all start with ’S’ and are stored in /etc/rc3.d. For instance, on a Solaris box you might have:

/etc/rc3.d/S15nfs.server /etc/rc3.d/S34dhcp

/etc/rc3.d/S50apache /etc/rc3.d/S60weblogic /etc/rc3.d/...

To shut down a daemon there are similar scripts in /etc/rc1.dAND /etc/rc0.d. These are like the start scripts but they begin with ’K’ as in K5weblogic.

You can have a single script, say weblogicdas shown in the slides above stored in the /etc/init.d directory. And then link scripts such as /etc/rc3.d/S60weblogic, /etc/rc1.d/K5weblogic and /etc/rc0.d/K5weblogicto /etc/init.d/weblogicd. You could then use a script such as /etc/rc3that calls all the start scripts in the /etc/rc3.ddirectory (the ones that begin with ’S’) in alphabetical order and passes them the ’start’ parameter. As the system shuts down the same thing happens in reverse.

Notice that the domain directories are in /usr/bea/user_projects. This takes the developer supplied stuff out of the installation hierarchy.

(59)

59

.

f

The administration server:

–

can go down without affecting the operation of managed

servers

–

can be restarted while managed servers are still running

f

When an administration server goes down:

–

domain log entries are lost while it is down

–

managed servers can start in independent mode

–

the administration console and management tools are

unavailable

One misconception about the administration server is that it represents a single point of failure. This is NOT true. Administration servers are only needed to start managed servers. After the managed servers are started, the administration server may go down without affecting them. The only thing that may be lost in such a scenario is the domain-specific log entries, only while the administration server is down. Also, if a new managed server tries to start, it will fail because it won’t be able to connect to the administration server. Lastly, the administration console and other management tools won’t be available.

You may tell an administration server to re-connect to the managed servers when it boots. This way, the log entries that follow will be stored.

When the administration server is down, the SNMP agent no longer functions. This will be addressed later in the course.

(60)

.

Administration Server Backup

f

WLS 8.1 allows the creation of a backup of the server

as follows:

–

install (if necessary) WLS on backup machine

–

copy application files to backup machine

–

copy configuration files to backup machine

–

restart Administration server on new machine with discovery

enabled

f

The new Administration server will contact managed

servers and inform them that it is running on a new IP

address.

Restarting an Administration Server on Another Machine

If a machine crash prevents you from restarting the Administration Server on the same machine, you can recover management of the running Managed Servers as follows:

1. Install the WebLogic Server software on the new administration machine (if this has not already been done).

2. Make your application files available to the new Administration Server by copying them from backups or by using a shared disk. Your application files should be available in the same relative location on the new file system as on the file system of the original Administration Server.

3. Make your configuration and security files available to the new administration machine by copying them from backups or by using a shared disk. These files are located in the root directory of the domain being managed by the Administration Server.

4. Restart the Administration Server on the new machine with the addition of the following argument on the command line:

-Dweblogic.management.discover=true

This argument will force the Administration Server to discover the presence of the Managed Servers that are running. (If you omit this property, the Administration Servers still executes the discovery. Make sure, however, that this property is either not defined or not set to false in the command line you use to start WebLogic Server.)

When the Administration Server starts, it communicates with the Managed Servers and informs them that the Administration Server is now running on a different IP address.

(61)

61

.

f

The Discovery Mode:

–

enables re-connecting to managed servers after the

administration server went down

–

is ON by default, but can be turned OFF by using a special

flag when starting the administration server

–

tells the administration server to detect all managed servers

that may be running on the network

–

-Dweblogic.discover.enabled=false

–

weblogic.Admin …… DISCOVERMANAGEDSERVER can be

used to attach managed servers dynamically to the running

administration server (if already started without discovery

mode)

Under normal circumstances once a domain is up and running it can continue to run indefinitely. Both managed servers and the administration server for a domain would normally start and continue to run for however long is appropriate. However, occasionally it may be required that you restart an administration server or a managed server. One of the features that WebLogic Server provides for supporting restarting an administration server is the ability to discover what managed servers are already up and running. The Discovery Mode allows an administration server to re-connect to managed servers after it went down. This feature makes the administration server look for running managed servers on the network, and re-connect to them.

The administration server keeps track of running managed servers in an XML file, running-managed-servers.xml, in the domain directory. This file must be created. First start the

administration server in discovery mode and then start all the managed servers. This will create the file. The next time you start the administration server, you may turn off the discovery mode and the file will not be deleted. Later if the administration server goes down, you will be able to start in discovery mode using this file.

But booting in Discovery Mode is slower because of the overhead incurred by the detection and connection process.

If for any reason you need to attach to managed servers while the administration server is already started

without discovery mode, you may use this command to attach dynamically:

java weblogic.Admin -url <host>:<port> -username system -password

<password> INVOKE -mbean "<domain>:Type=Domain,Name=<domain>"

(62)

.

Running Multiple WLS Instances

f

You can run multiple instances of WLS using different

configurations on the same physical machine at the

same time by:

–

assigning multiple IP address to a machine (multihoming)

and defining each server to use a unique IP address

f

or by:

–

specifying the same IP address but using different listen ports

It is possible to run multiple instances of WebLogic Server on a machine by specifying either multiple IP addresses for the machine (multihoming) or by using all the same IP addresses but specifying different listen ports.

(63)

63

.

f

A multihomed machine:

–

is a machine with multiple IP addresses

–

can run a different WLS instance bound to each IP address

–

can be used to configure a cluster on a single machine

192.168.1.1

192.168.1.2

Machine

A multihomed machine is one where multiple IP addresses are all bound to a single machine. A

multihomed machine may have more than one network card or simply multiple IP addresses bound to a single network card. In either case, a machine with more than one IP address is considered to be

multihomed. Multihomed machines can be configured to run multiple instances of WebLogic Server, each bound to a specific IP address and in this way can simulate a multiple machine cluster environment on a single machine, as is typical in WLS 6.x.

Note: If you need help configuring multiple IP addresses on your machine, consult the appendix module

(64)

.

Section Review

9 How to define and start an administration server

9 How to create and start a managed server

9 The Discovery Mode

9 Starting WebLogic Server

at boot time

9 Managed server

independence

9 Administration server

backup

In this section we discussed:

(65)

65

.

f

In this lab you are going to configure a domain and

configure servers within the domain.

f

Ask the instructor

for any clarification.

f

The instructor will

determine the stop time.

WWMS 05—Configuring a Domain

Lab Exercise

Exercises are introduced where appropriate with an exercise slide detailing the title of the exercise and its number relative to the letter ID of the module.

Exercises that are at the end of a module should be located after the last section review but before the module review.

(66)

.

Road Map

1. Configuring Domains

2. Configuring Servers

3. Logs and Monitoring

–

Using the Domain Logs

–

Monitoring Managed Server Logs

–

Monitoring Active Servers

In this section we discuss configuration of domain logs and managed server logs and see how to carry out basic monitoring.

(67)

67

.

f

Logs can aid in the discovery of:

–

frequently accessed resources

–

activity by day and time interval

–

amount of data sent and received

–

IP addresses of users accessing the site

–

number of actual “hits”

–

problems servicing requests

–

performance statistics

Administrators will use logs to monitor the servers, monitor resources for the application, and to retrieve performance statistics. Logs are helpful because they gather information 24 hours a day, 7 days a week. Therefore an administrator will be able to monitor how a system performed, without needing to be there at the particular time.

(68)

.

Main Server Logs

f

A Server log:

–

logs all server activity

–

is stored in

serverName\<serverName>.log

by default

–

is stored locally on the server

f

A Domain log:

–

logs all domain activity

–

is stored in

<domainName>.log

by default

–

is stored on the administration server

f

These logs are independently configured.

WebLogic Server maintains different levels of logs. A domain log can be kept to store all domain activity. This is the log file the administration server maintains and logs all critical logs from the managed servers. Each managed server also maintains a local log file so the administrator can monitor all local server activity.