Working with Managed Servers

Transcription

1 Module 4 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 BEA Systems, Inc. 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. 1

2 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 BEA Systems, Inc. 2 2

3 A Review of WLS Domains 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 Server1 MachineA Server2 Server3 MachineB Server4 MyCluster BEA Systems, Inc. 3 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. 3

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 Critical Domain Notifications (Logs) LOG LOG MyDomain Administration Server Configuration repository (config.xml) XML BEA Systems, Inc. 4 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. 4

5 What Is a Managed Server? 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 BEA Systems, Inc. 5 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. 5

6 Domain Overview Domain Domain Log LOG Get Configuration at Startup Managed Server 1 Cluster Console Critical Domain Notifications GET / SET Administration Server Domain Log Messages LOG LOG Local Logging Managed Server 2 Local Logging XML Configuration Repository config.xml Monitor/ Update LOG Managed Server 3 Local Logging BEA Systems, Inc. 6 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. 6

7 Configuration Wizard Overview 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 BEA Systems, Inc. 7 7

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 BEA Systems, Inc. 8 8

9 Configuration Template Builder 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 BEA Systems, Inc. 9 9

10 Starting Configuration wizard f Scripts in /common/bin directory f Graphical mode Windows Start menu [Windows] config.cmd or [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] BEA Systems, Inc

11 Creating a script for creating a domain in silent mode 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 BEA Systems, Inc

12 Creating a script for creating a domain in silent mode /*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 BEA Systems, Inc

13 Example: Creation of a domain BEA Systems, Inc

14 Example: Creation of a domain BEA Systems, Inc

15 Example: Creation of a domain BEA Systems, Inc

16 Example: Creation of a domain Validation in action BEA Systems, Inc

17 Example: Creation of a domain BEA Systems, Inc

18 Example: Creation of a domain BEA Systems, Inc

19 Example: Creation of a domain BEA Systems, Inc

20 Example: Creation of a domain BEA Systems, Inc

21 Example: Creation of a domain BEA Systems, Inc

22 Example: Creation of a domain Default for development mode is JDK141_02 Default for production mode is JRocket BEA Systems, Inc

23 Example: Creation of a domain BEA Systems, Inc

24 Example: Creation of a domain BEA Systems, Inc

25 Example: Creation of a domain 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: Admin server can be started by the script or the startup menu BEA Systems, Inc

26 Example: Creation of a domain Proxying mechanism already setup BEA Systems, Inc

27 Example: Creation of a domain Say you have created cluster1 and deployed some apps to the cluster. Now suppose your want to extend this domain BEA Systems, Inc

28 Extending a domain using the Config Wizard f Make sure domain is not active BEA Systems, Inc

29 Extending a domain using the Config Wizard BEA Systems, Inc

30 Extending a domain using the Config Wizard BEA Systems, Inc

31 Extending a domain using the Config Wizard Update and you are done! BEA Systems, Inc

32 Extending a domain using the Config Wizard Bring up the domain and you ll see BEA Systems, Inc

33 Starting Configuration Template Builder f f f Can only be invoked in GUI mode Go to the \common\bin subdirectory of the product installation directory. For example: cd c:\bea\weblogic81\common\bin Use config_builder.cmd or sh config_builder.sh to start the configuration template builder BEA Systems, Inc

34 Example: Creating a Configuration Template BEA Systems, Inc

35 Example: Creating a Configuration Template Wizard-generated files are always in./apps already Your files are imported to./apps BEA Systems, Inc

36 Example: Creating a Configuration Template BEA Systems, Inc

37 Example: Creating a Configuration Template BEA Systems, Inc

38 Example: Creating a Configuration Template BEA Systems, Inc

39 Example: Creating a Configuration Template BEA Systems, Inc

40 Example: Creating a Configuration Template To use the newly created template: BEA Systems, Inc

41 Section Review In this section we discussed: 9 How a WebLogic Server domain works 9 The domain directory structure 9 Domain files 9 How to create a domain BEA Systems, Inc. 41 Each section has a Section review slide that echoes the points stated in the section road map. 41

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 BEA Systems, Inc. 42 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. 42

43 Defining Additional Servers f Additional servers can be defined: BEA Systems, Inc. 43 To create a server: 1. Left-click on Servers in 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\servers element in the left panel. Once selected, all known servers are displayed in the right pane. In the right panel choose Create a new Server to display the new server page. The next slide shows the new server pane in detail. Alternately, you can right click over the domain\servers element in the left pane and choose Create a new Server to 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.name property 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 Address field specifies the IP address that this server will listen on when started. When defining administration servers, the Administration Port field 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 instance may be active at any given moment. 43

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 All entered on one line BEA Systems, Inc. 44 An administration server is started when the weblogic.server command 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.server command by hand, at the command line, your default directory should be the weblogic81 directory. The script startweblogic, provided in each domain in user_projects\domains\somedomain directory executes the script startwls in the %WL_HOME%\server\bin directory. 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.server command 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 default startweblogic script in the mydomain directory. 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.xml file and names it config.xml.booted. WebLogic Server actually uses the copy of the config.xml file for retrieving configuration information. 44

45 Starting Managed Servers Domain Critical Domain Notifications Admin Server : :7002 GET / SET Domain Log LOG Get configuration at startup (http/https) Get configuration at startup (http/https) Cluster ServerA :7001 LOG ServerB :7001 LOG Local Logging Local Logging config.xml XML Configuration Repository Get configuration at startup (http/https) Proxy :7001 LOG Local Logging BEA Systems, Inc. 45 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.server command 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 = in the weblogic.server command to start the managed servers. You can also connect using HTTPS: -Dweblogic.management.server = 45

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%" 1 -Dweblogic.Name=%SERVER_NAME% -Dbea.home="C:\bea" -Dweblogic.management.username=%WLS_USER% -Dweblogic.management.password=%WLS_PW% 2 -Dweblogic.management.server=%ADMIN_URL% -Dweblogic.ProductionModeEnabled=%STARTMODE% -Djava.security.policy=%WL_HOME%\server\lib\weblogic.policy weblogic.server <startmanagerweblogic.cmd> BEA Systems, Inc 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 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.server command by hand at the command line, your default directory should be the weblogic81 directory. The provided startmanagedweblogic script starts a managed server based on the server name and administration server address, which are required parameters. An example startmanagedweblogic command might be: C:\bea\user_domains\WLSA11>startManagedWebLogic servera admin:7001 As shown in the example above, the parameters required for the weblogic.server command 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. weblogic.management.password The password used to access the Admin Server. 46

47 Required Files for a Managed Server f A new domain Directory creates / File a number of files: MyNewDomain applications logs setenv.cmd setenv.sh startweblogic.cmd startmanagedweblogic.cmd demokey.pem democert.pem Description BEA Home directory Stores default Web Apps for servers in the domain Stores log files for servers in the domain Set environment variables for domain servers Start Administration Server for a custom domain Start a Managed Server in a custom domain Sample SSL support for servers in the domain Sample SSL support for servers in the domain BEA Systems, Inc. 47 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. Configuration Repository is stored only in Administration Server by default. 47

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 BEA Systems, Inc. 48 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_OPTIONS directive: -Dweblogic.system.BootIdentityFile=filename For example: set JAVA_OPTIONS=- Dweblogic.system.BootIdentityFile=c:\securedirectory\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. 48

49 Managed Server Independence f By default, managed servers can function independently of the administration server. f Configure Managed Server Independence Mode from the Console: BEA Systems, Inc. 49 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.xml by 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.) 49

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 BEA Systems, Inc. 50 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=path startup 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. 50

51 Replicating Domain Configuration Files f Administration servers can automatically copy configuration files onto managed servers every 5 minutes BEA Systems, Inc. 51 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. 3. Click the MSI File Replication Enabled check box.(advanced Option) 51

52 Starting WebLogic Server at Boot f WebLogic Server can be configured to start at boot time as: a Windows service a UNIX daemon BEA Systems, Inc. 52 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: WebLogic Server starts when the machine starts and shuts down when the machine shuts down. 52

53 WLS as a Windows Service fthe Configuration Wizard can setup a default WLS as a Windows service. fif you want a WebLogic Server as a Windows service with custom settings you will need to edit and run the script: <domain>\installservice.cmd fthis script will setup the Administration server as Windows service BEA Systems, Inc. 53 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 named beasvc%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_name directory (where domain_name is the directory with your domain's configuration). For example, navigate to C:\bea\user_projects\domains\humanresources. 2. Open domain_name\installservice.cmd in a text editor. 3. Create and enter values for any of the optional variables 4. Save and run installservice.cmd. If the script runs successfully, its output in the command window includes a line similar to the following: beasvc myserver installed. 53

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 jdk1.4.1home wlsinstallroot wlsbindirectory cmdtorun The name to associate with the service. Path to where the JDK is installed. Root of the WLS install tree (i.e., c:\bea\weblogic81). Path to the WLS \bin directory. Java class to run as a service (e.g., weblogic.server) including any parameters BEA Systems, Inc. 54 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 java command 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" - extrapath:"c:\bea\weblogic81\server\bin" -cmdline:%cmdline% 54

55 WLS as a UNIX Daemon 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 BEA Systems, Inc. 55 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/inittab file. Under Linux, init examines /etc/inittab and enters the run level specified by the id: line (normally the first line in the file). In addition, init starts 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 x is the run level to enter). Again, this line is normally the first line in the /etc/inittab file but it is not a requirement, it is more of a convention. Note: Other flavors of UNIX platforms have equivalent techniques. 55

56 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 WLS Started! BEA Systems, Inc

57 Example rc Scripts 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 ;; BEA Systems, Inc. 57 Here are environment variables that the above rc script 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 57

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 BEA Systems, Inc. 58 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.d AND /etc/rc0.d. These are like the start scripts but they begin with K as in K5weblogic. You can have a single script, say weblogicd as 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/k5weblogic to /etc/init.d/weblogicd. You could then use a script such as /etc/rc3 that calls all the start scripts in the /etc/rc3.d directory (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. 58

59 What If an Admin. Server Is Down? 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 BEA Systems, Inc. 59 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. 59

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 BEA Systems, Inc. 60 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. See 60

61 Discovery Mode 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) BEA Systems, Inc. 61 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, runningmanaged-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>" -method discovermanagedservers 61

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 BEA Systems, Inc. 62 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. 62

63 Multihoming 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 Machine BEA Systems, Inc. 63 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 MHOM for more details. 63

64 Section Review In this section we discussed: 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 BEA Systems, Inc. 64 Each section has a Section review slide that echoes the points stated in the section road map. 64

65 Exercise WWMS 05 Configuring a Domain 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. Lab Exercise BEA Systems, Inc. 65 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. 65

66 Road Map 1. Configuring Domains 2. Configuring Servers 3. Logs and Monitoring Using the Domain Logs Monitoring Managed Server Logs Monitoring Active Servers BEA Systems, Inc. 66 In this section we discuss configuration of domain logs and managed server logs and see how to carry out basic monitoring. 66

67 Using Logs to Monitor 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 BEA Systems, Inc. 67 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. 67

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 BEA Systems, Inc. 68 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. 68

69 Configuring Server Logging f Configure logging via the Logging tab: You must restart the server! BEA Systems, Inc Select a server in the tree pane. 2. Select the Logging tab for the server and go to the General tab. 3. Enter the name and location of the server log to use. Choose the level of information that is output to standard output. This is relative to the root directory of the domain that is started, i.e., if the domain is in c:\bea\user_projects\domains\humanresources, then the log is stored in c:\bea\user_projects\domains\humanresources\adminserver\adminserver.log 4. Click the Apply button to save your changes. 5. If you changed the log file s name, you must restart WLS. 6. Server log can be viewed on the console by clicking the View server log option. By default WebLogic Server writes to both standard out and a logging file for various events. Error levels from informational to emergency can be selected for display (emergency being the highest level). The default logging level is error, which only displays those events which should not happen. Other informational or warning events, are not displayed. Production systems will typically log messages of level error and above. You can also choose whether or not to log to standard out (the display window WebLogic Server is running in) by checking or unchecking the Log to Stdout check box. You can also choose to send debugging information to the standard output. This can be done by checking the Debug to Stdout checkbox. Note: If you use the same server log name and location as your domain log name and location, the server log will overwrite the domain log! Choose sensible log names and locations to avoid this. 69

70 Configuring the Domain Log f The domain log logs events occurring on any server and sub-system: You must restart the server! BEA Systems, Inc Select the domain 2. Click the Configuration tab for your the domain and go to the Logging tab. 3. Enter the domain log file name to use. 4. Click the Apply button to save the changes. 5. Restart WLS. The log messages forwarded by WebLogic Servers to the domain log are, by default, a subset of messages logged locally. You can configure a log filter that selects log messages for forwarding based on message severity, subsystem, or user ID. Debug messages are a special case and are not forwarded to the domain log. As with the managed server log, you can specify the maximum number of rotated files that can accumulate by selecting Limit number of Files and setting an appropriate number of files. Once the number of log files reaches this number, the oldest log file is deleted each time a log file rotation occurs. The rotated log files are numbered in order of creation filename.ext99999, where filename is the name configured for the log file. For example: humanresources.log00001 would be the first log created if the chosen filename were humanresources.log. You can specify the log paths to be absolute or relative. If relative, the paths are relative the domain root directory. 70

71 Logging Services BEA Systems, Inc. 71 Log messages are a useful tool for managing systems. Log messages allow detection of problems, help track down the source of a fault, and helps track system performance. WebLogic Server stores log messages in two locations: WebLogic Server component subsystems generate messages that are logged to a local file, that is, a file that resides on the machine where the server is running. If there are multiple servers on a machine, each server has its own log file. Applications deployed on your WebLogic Servers may also log messages to the server's local log file. In addition, a subset of messages logged locally are stored in a central domain-wide log file maintained by the Administration Server. Java Management Extension (JMX) facilities, embedded in the WebLogic Server, are used to transmit log messages from WebLogic Servers to the Administration Server. A message forwarded to other entities on the initiative of a local WebLogic Server is called a notification in JMX terminology. When a WebLogic server starts, the Administration Server's message handler registers with that server to receive log messages. At the time of registration, a user-modifiable filter is provided that is used by the local server to select the messages to be forwarded to the Administration Server. These messages are collected in the domain log. Developers can also build custom message handlers that can register with a WebLogic Server to receive log messages via JMX notifications. By default, only the most important log messages as determined by Message Severity are forwarded from the local servers to the domain log. The domain log gives you an overall view of the entire domain while focusing on just the most critical messages. To receive a different subset of logged messages from a local server, filters can be set dynamically using the Administration Console. 71

72 Messages Forwarded to Domain Log Severity Informational Warning Error Notice Critical Alert Emergency Forwarded to Domain Log by Default No No Yes Yes Yes Yes Yes Meaning Used for reporting normal operations. A suspicious operation or configuration has occurred but it may not have an impact on normal operation. A user error has occurred. The system or application is able to handle the error with no interruption, and limited degradation, of service. A warning message: A suspicious operation or configuration has occurred which may not affect the normal operation of the server. A system or service error has occurred. The system is able to recover but there might be a momentary loss, or permanent degradation, of service. A particular service is in an unusable state while other parts of the system continue to function. Automatic recovery is not possible; the immediate attention of the administrator is needed to resolve the problem. The server is in an unusable state. This severity indicates a severe system failure or panic BEA Systems, Inc. 72 Messages with a severity of debug are a special case. Debug messages are not forwarded to the domain log. Debug messages may contain detailed information about an application or the server. These messages should only occur when the application is running in debug mode. 72

73 Message Attributes ####<Jun 2, :23:02 AM PDT> <Info> <SSL> <bigbox> <myserver> <SSLListenThread> <harry> <> <004500> <Using exportable strength SSL> Attribute Timestamp Severity Subsystem Server Name Machine Name Thread ID Transaction ID User ID Message ID Message Text Description The time and date when the message originated, in a format that is specific to the locale. Indicates the degree of impact or seriousness of the event reported by the message. This attribute denotes the particular subsystem of WebLogic Server that was the source of the message. For example, EJB, RMI, JMS. These four attributes identify the origins of the message. Transaction ID is present only for messages logged within the context of a transaction. Note: Server Name and Thread ID are not present in log messages generated by a Java client and logged to a client log. The user from the security context when the message was generated. A unique six-digit identifier. Message IDs through are reserved for WebLogic Server system messages. For WebLogic Server messages, this contains the Short Description as defined in the system message catalog. For other messages, this is text defined by the developer of the program BEA Systems, Inc. 73 The first line of each message in a log file begins with #### followed by the message header. The message header provides the run-time context of the message. Each attribute of the message is contained between angle brackets. Lines following the message body are only present for messages logging an exception and display the stack trace for the exception. If a message is not logged within the context of a transaction, the angle brackets (separators) for Transaction ID are present even though no Transaction ID is present. The character encoding used in writing the log files is the default character encoding of the host system. In addition to the information contained in a log message, messages generated by WebLogic Server system components (or possibly by user-written code) include additional pre-defined or canned information that is stored in a message catalog. The additional attributes stored in the message catalog are described below. Message Body:This is a short textual description of the condition being reported. This is the same as Message Text in the message. Message Detail: A more detailed description of the condition that the message is reporting. Probable Cause: An explanation as to why the message was logged. The probable cause of the condition the message is reporting. Recommended Action: A recommendation for action by the administrator to resolve or avoid the condition reported in the message. 73

74 Domain Log Filters f Filters: can be created to receive a subset of log messages allow choice of subsystem and user id. allow choice of severity, i.e., only messages of chosen severity or higher will be forwarded to the domain log f Once filters are created they can be assigned to servers in the domain BEA Systems, Inc

75 Creating Domain Log Filters BEA Systems, Inc. 75 To receive a subset of the default log messages filters can be dynamically created through the console. Steps for Creating a New Domain Log Filter 1. Click the Domain Log Filters node in the left pane. The Domain Log Filters table displays in the right pane showing all the log filters in the domain. 2. Click the Create a New Domain Log Filter text link. A dialog displays in the right pane showing the tabs associated with configuring a new domain log filter. 3. Enter a value in the Name attribute field. 4. Select a severity level from the Severity Level drop-down list. Only messages of the severity or higher will be forwarded to the domain log. 5. Enter the User IDs associated with this log filter, if any. If no User IDs are chosen, then the filter sends messages that were generated by all users. 6. Select the Subsystems for which you want messages forwarded to the domain log. If no subsystems are chosen, then the filter sends messages from all subsystems. 7. Click Create to create a domain log filter instance with the name you specified in the Name field. The new instance is added under the Domain Log Filters node in the left pane. 75

76 Assigning a Domain Log Filter BEA Systems, Inc. 76 Assigning a Domain Log Filter to One or More Servers Expand the Domain Log Filters node in the left pane. A list of domain log filters appears under the Domain Log Filters node. Select a domain log filter in the left pane. Select the Targets tab. Select the Servers on which you want to apply the filter. Click Apply. The chosen servers now use this filter. Although you can assign a filter to multiple servers, a server can use only one filter at a time. Note that clicking Apply sets the value of the Server >myserver >Logging >Domain >Use Log Filter. You can also Choose from a list. 76

77 Message Catalog f Message catalogs are available in HTML format on e-docs as part of the documentation deliverable. You can search for messages by error number using the search engine BEA Systems, Inc. 77 All message IDs that WebLogic Server system messages generate start with BEA- and fall within a numerical range of Online reference of the different messages can be found in the message catalog at 77

78 Message Catalog BEA Systems, Inc

79 Using the Console to Monitor f The Administration Console offers many monitoring capabilities: Attribute Description Many of the Console s objects have a Monitoring tab, that displays the current status of the object You can choose categories of things to monitor by clicking on Monitor all The monitoring view can be customized by clicking on Customize this view The monitoring view can be updated automatically every 10 seconds by clicking on the button BEA Systems, Inc. 79 Every time a service or application object can be monitored, a Monitoring tab will be available in the Console for that object. Clicking on it will show you the available monitored values for the selected object. Sometimes there are more values than can be displayed. To view this extra information, there are hyperlinks on the main monitoring page, marked Monitor all something. Moreover, when the monitoring page shows information in tabular format, you may change the way the information is displayed. To do this, click on the Customize this view hyperlink and choose which columns to display, and on what columns to sort the table. Lastly, you will notice a button in the top part of the screen with two circling arrows. This is the automatic refresh button. Clicking on this button will refresh the data on the page automatically every 10 seconds (by default). The delay can be modified by clicking on the console category in the administration console (first item on the left pane tree), and changing the value in Auto-refresh every: field. 79

80 Monitoring Running Servers f To get the state of all servers at a glance, go to this page: BEA Systems, Inc When you click on Servers in the left panel the status of all servers in the domain appears in the right panel. 2. You can customize how you see the server statistics in the right panel. 3. The State column indicates whether the server is running or not. General server status can be displayed by selecting Servers under a domain. The right pane then displays a completely customizable view of the current server status. The default display lists all currently configured servers, sorted by name, whether they are running or not and a number of other status item elements such as machine binding, if the server is a member of a cluster, memory use etc. You cannot monitor the activity of one domain through another domain. For example, you cannot open the Administration Console through the default domain and try to monitor servers within another domain. 80

81 Customizing views f Columns can be customized on views BEA Systems, Inc. 81 The Customize this view link allows you to change the sort order, the items displayed and even change the default view to include other status elements such as backlogged requests, invalid logins, JDK Vendor, listen address and a number of other fields. Additionally almost any displayable field can be chosen as a sort-by field, allowing for viewing in whatever order is appropriate, such as by status and then name, or memory usage or some other appropriate field. See the WebLogic Server documentation for a complete list of all available elements at: 81

82 Monitoring Individual Servers f To monitor a single server, select the Monitoring tab under that server: BEA Systems, Inc Select a certain server. 2. Click one of the monitoring sub tabs to display more detailed monitoring information. 3. Select one of the links to view core monitoring information. When you select a specific server from the domain/servers element of the left most console pane a server specific monitoring page is displayed. A large amount of detailed monitoring information can be obtained about any running instance of WebLogic Server. The performance tab shows a running graphical output of request throughput, waiting request and memory in use, and gives a fast indication of server performance. Additional, in-depth, information is available about their associated cluster, such as multicast packet loss, packet fragments etc. The security tab provides statistics specific to security such as invalid log ins and locked out users. The remaining tabs provide in depth information about their associated service. 82

83 Section Review In this section we discussed: 9 Using the domain logs 9 Using the server logs BEA Systems, Inc. 83 Each section has a Section review slide that echoes the points stated in the section road map. 83

84 Module Review In this module we discussed: 9 Domain concepts 9 How to create domains 9 How to create and start Administration and managed servers 9 How to monitor domains and servers -84 Servers BEA Systems, Inc