Cluster Server Agent for WebLogic Server Installation and Configuration Guide

Transcription

1 Cluster Server Agent for WebLogic Server Installation and Configuration Guide AIX, Linux, Solaris 7.0

2 Veritas InfoScale Availability Agents Last updated: Legal Notice Copyright 2017 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo are trademarks or registered trademarks of Veritas Technologies LLC or its affiliates in the U.S. and other countries. Other names may be trademarks of their respective owners. This product may contain third party software for which Veritas is required to provide attribution to the third party ( Third Party Programs ). Some of the Third Party Programs are available under open source or free software licenses. The License Agreement accompanying the Software does not alter any rights or obligations you may have under those open source or free software licenses. Refer to the third party legal notices document accompanying this Veritas product or available at: The product described in this document is distributed under licenses restricting its use, copying, distribution, and decompilation/reverse engineering. No part of this document may be reproduced in any form by any means without prior written authorization of Veritas Technologies LLC and its licensors, if any. THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. VERITAS TECHNOLOGIES LLC SHALL NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE. The Licensed Software and Documentation are deemed to be commercial computer software as defined in FAR and subject to restricted rights as defined in FAR Section "Commercial Computer Software Restricted Rights" and DFARS , et seq. "Commercial Computer Software and Commercial Computer Software Documentation," as applicable, and any successor regulations, whether delivered by Veritas as on premises or hosted services. Any use, modification, reproduction release, performance, display or disclosure of the Licensed Software and Documentation by the U.S. Government shall be solely in accordance with the terms of this Agreement. Veritas Technologies LLC 500 E Middlefield Road Mountain View, CA

3 Technical Support Technical Support maintains support centers globally. All support services will be delivered in accordance with your support agreement and the thencurrent enterprise technical support policies. For information about our support offerings and how to contact Technical Support, visit our website: You can manage your Veritas account information at the following URL: If you have questions regarding an existing support agreement, please the support agreement administration team for your region as follows: Worldwide (except Japan) Japan Documentation Make sure that you have the current version of the documentation. Each document displays the date of the last update on page 2. The latest documentation is available on the Veritas website: Documentation feedback Your feedback is important to us. Suggest improvements or report errors or omissions to the documentation. Include the document title, document version, chapter title, and section title of the text on which you are reporting. Send feedback to: You can also see documentation information or ask a question on the Veritas community site: Veritas Services and Operations Readiness Tools (SORT) Veritas Services and Operations Readiness Tools (SORT) is a website that provides information and tools to automate and simplify certain timeconsuming administrative tasks. Depending on the product, SORT helps you prepare for installations and upgrades, identify risks in your datacenters, and improve operational efficiency. To see what services and tools SORT provides for your product, see the data sheet:

4 Contents Chapter 1 Introducing the agent for WebLogic Server... 7 About the Cluster Server agent for WebLogic Server... 7 Supported software... 8 How the agent supports intelligent resource monitoring... 8 About WebLogic Server... 8 WebLogic Server agent functions... 9 Online... 9 Offline Monitor Clean Chapter 2 Installing, upgrading, and removing the agent for WebLogic Server Before you install the Cluster Server agent for WebLogic Server Prerequisites for enabling i18n support About the ACC library Installing the ACC library Installing the ACC library IPS package on Oracle Solaris 11 systems Installing the ACC library package on Solaris brand nonglobal zones Installing the agent in a VCS environment Installing the agent IPS package on Oracle Solaris 11 systems Installing agent packages on Solaris brand nonglobal zones Installing the agent in a Solaris 10 brand zone Uninstalling the agent in a VCS environment Removing the ACC library Upgrading the agent in a VCS environment Updating the agent using the update script... 23

5 Contents 5 Chapter 3 Configuring the agent for WebLogic Server About configuring the Cluster Server agent for WebLogic Server Importing the agent types files in a VCS environment WebLogic Server agent attributes Executing secondlevel monitoring Executing a customized monitoring program Uniquely identifying WebLogic Server instances Attributes used in different resource configurations Using WebLogic provided scripts Editing the WebLogic stop script Avoiding storing unencrypted credentials in startup/shutdown scripts Delaying managed server startup process Configuring multiple Administrative Servers that have the same name for different domains Chapter 4 Chapter 5 Enabling the agent for WebLogic Server to support IMF About Intelligent Monitoring Framework Benefits of IMF Agent functions for the IMF functionality imf_init imf_getnotification imf_register Attributes that enable IMF IMF IMFRegList Before you enable the agent to support IMF Enabling the agent to support IMF If VCS is in a running state If VCS is not in a running state Disabling intelligent resource monitoring Sample IMF configurations Configuring the service groups for WebLogic Server using the CLI Before configuring the service groups for WebLogic Server Configuring service groups for WebLogic Server Creating service groups for WebLogic Server under Solaris nonglobal zones... 63

6 Contents 6 Chapter 6 Troubleshooting the agent for WebLogic Server Using the correct software and operating system versions Meeting prerequisites Configuring WebLogic Server resources Starting the WebLogic Server instance outside a cluster Defining additional environment variables before starting or stopping WebLogic resources Reviewing error log files Using WebLogic Server log files Reviewing cluster log files Using trace level logging Using agent for WebLogic Server log files Problems starting a Managed Server through the administrative console Unable to bring two or more VCS resources offline simultaneously Serial version UID mismatch on the AIX platform Troubleshooting the configuration for IMF Known issues Appendix A Sample Configurations About sample configurations for the agents for WebLogic Server Configuring "weblogic.admin GETSTATE" based monitoring Sample agent type definition for WebLogic Server Sample service group configuration for WebLogic Server Sample resource configurations for WebLogic Server Node Manager without SLM enabled Node Manager with SLM enabled Administrative Server (NM) without SLM enabled Administrative Server (NM) with SLM enabled Managed Server (NM) without SLM enabled Managed Server (NM) with SLM enabled Managed Server (NNM) without SLM enabled Managed Server (NNM) with SLM enabled Administrative Server (NNM) without SLM enabled Administrative Server (NNM) with SLM enabled Service group dependencies for WebLogic Server Sample configuration in a VCS environment... 94

7 Chapter 1 Introducing the agent for WebLogic Server This chapter includes the following topics: About the Cluster Server agent for WebLogic Server Supported software How the agent supports intelligent resource monitoring About WebLogic Server WebLogic Server agent functions About the Cluster Server agent for WebLogic Server Cluster Server (VCS) agents monitor specific resources within an enterprise application. They determine the status of resources and start or stop them according to external events. The Cluster Server agent for WebLogic Server provides high availability for WebLogic Servers in a cluster. For the latest updates or software issues for this agent, see the Cluster Server Agent Pack Release Notes.

8 Introducing the agent for WebLogic Server Supported software 8 Supported software For information on the software versions that the Cluster Server agent for WebLogic Server supports, see the Veritas Services and Operations Readiness Tools (SORT) site: How the agent supports intelligent resource monitoring With Intelligent Monitoring Framework (IMF), VCS supports intelligent resource monitoring in addition to the pollbased monitoring. Pollbased monitoring polls the resources periodically whereas intelligent monitoring performs asynchronous monitoring. When an IMFenabled agent starts up, the agent initializes the Asynchronous Monitoring Framework (AMF) kernel driver. After the resource is in a steady state, the agent registers with the AMF kernel driver, the details of the resource that are required to monitor the resource. For example, the agent for WebLogic Server registers the PIDs of the WebLogic Server processes with the AMF kernel driver. The agent s imf_getnotification function waits for any resource state changes. When the AMF kernel driver module notifies the imf_getnotification function about a resource state change, the agent framework runs the monitor agent function to ascertain the state of that resource. The agent notifies the state change to VCS, which then takes appropriate action. For more information, see the Cluster Server Administrator s Guide. About WebLogic Server WebLogic Servers fall into two categories: Administrative and Managed. The Administrative Server provides a central point from which you can manage the domain, and it provides access to WebLogic server administration tools [WLS05: Introduction to BEA WebLogic server and BEA WebLogic Express, July 2005]. All other servers are considered as Managed Servers. A Node Manager is a WebLogic server utility that enables you to start, shut down, and restart Administration Server and Managed Server instances from a remote location.

9 Introducing the agent for WebLogic Server WebLogic Server agent functions 9 The Cluster Server agent for WebLogic Server supports both Administrative and Managed Servers, and Node Manager based configurations. The agent recognizes the startup server dependency that exists between Managed and Administrative Servers and provides the cluster administrator with the choice of enforcing or not enforcing this startup restriction. Similarly, the agent is WebLogic Cluster agnostic. In other words, this agent can provide clustering services for standalone WebLogic Servers and can support Managed Servers that participate in a WebLogic Cluster. WebLogic Server agent functions The agent consists of resource type declarations and agent executables. The agent executables are organized into online, offline, monitor, and clean functions. Online The online function performs the following tasks: Performs a preliminary check to ensure that the WebLogic Server component is not already running. Checks the value of the ServerRole attribute set for the resource. If the value of the attribute is Managed, the online function may delay the Managed server startup process until the Administrative server is initialized. For details, refer to description of attributes AdminServerMaxWait and RequireAdminServer. Starts the WebLogic Server component using the following mechanism. Node Manager Administrative server (NM) Uses the wlst command startnodemanager. Uses the wlst commands nmconnect and nmstart.

10 Introducing the agent for WebLogic Server WebLogic Server agent functions 10 Managed server (NM) Administrative server (NNM) Managed server (NNM) Uses the wlst commands nmconnect and nmstart. Uses the script configured in ServerStartProgram attribute. Uses the script configured in ServerStartProgram attribute. Ensures that the component is up and running successfully. The agent function uses the wait period that the OnlineTimeout attribute specifies, to enable the WebLogic Server component to initialize fully before allowing the monitor function to probe the newly running server instance. Offline The offline function performs the following tasks: Performs a preliminary check to ensure that the WebLogic Server component is not already offline. For different resource configurations, stops the WebLogic Server component gracefully using the mechanism shown as follows. Node Manager Administrative server (NM) Managed server (NM) Administrative server (NNM) Managed server (NNM) Terminates the Node Manager process. Uses the wlst commands connect and shutdown. Uses the wlst commands connect and shutdown. Uses the script configured in ServerStopProgram attribute. Uses the script configured in ServerStopProgram attribute. Ensures that the resource is given enough time to go offline successfully. The agent function uses a wait period that the OfflineTimeout attribute specifies, to allow the WebLogic Server component to complete the offline sequence before allowing further probing of the resource. Monitor The monitor function performs the following tasks: Conducts a firstlevel check on the WebLogic Server component to ensure that the WebLogic Server component s process is running. The agent identifies the process for the WebLogic Server component by applying the pattern matching on command lines of processes running in the system.

11 Introducing the agent for WebLogic Server WebLogic Server agent functions 11 The agent for WebLogic Server also supports Intelligent Monitoring Framework (IMF) in the firstlevel check. IMF enables intelligent resource monitoring. The agent for WebLogic Server is IMFaware and uses the asynchronous monitoring framework (AMF) kernel driver for resource state change notifications. See How the agent supports intelligent resource monitoring on page 8. You can use the MonitorFreq key of the IMF attribute to specify the frequency at which the agent invokes the monitor function. See MonitorFreq on page 52. Depending on the configuration, the monitor function can conduct a second level check on the WebLogic Server component. The secondlevel check uses the wlst.sh scripting utility to attempt to connect to the WebLogic Server component. For different resource configurations, the wlst commands used to connect to the WebLogic Server component are listed as follows. Node Manager Administrative server (NM) Managed server (NM) Administrative server (NNM) Managed server (NNM) Uses the wlst command nmconnect. Uses the wlst command connect. Uses the wlst command connect. Uses the wlst command connect. Uses the wlst command connect. Note: The attribute used to configure the secondlevel check and its frequency depends on the software versions of VCS and WebLogic Server agent you have installed: For VCS 5.1 SP1 or later with WebLogic Server agent version , use the LevelTwoMonitorFreq attribute. For VCS 5.1 or earlier with WebLogic Server agent or earlier, use the SecondLevelMonitor attribute. Depending upon the value of the MonitorProgram attribute, the monitor function can perform a customized check using a usersupplied monitoring utility. Clean The clean function performs the following tasks: Attempts to gracefully shut down the WebLogic Server component. For Administrative and Managed server in Node Manager based configurations, the clean function attempts the wlst nmkill command. Identifies the process for the WebLogic Server component and kills it.

12 Introducing the agent for WebLogic Server WebLogic Server agent functions 12 The default value of the CleanTimeout attribute is 60 seconds. As the clean function may execute two wlst.sh operations, 60 seconds may be insufficient. You can set this attribute to 120 seconds or more. Note: For information about the additional functions of the agent for WebLogic Server when IMF is enabled: See Agent functions for the IMF functionality on page 50.

13 Chapter 2 Installing, upgrading, and removing the agent for WebLogic Server This chapter includes the following topics: Before you install the Cluster Server agent for WebLogic Server About the ACC library Installing the ACC library Installing the agent in a VCS environment Uninstalling the agent in a VCS environment Removing the ACC library Upgrading the agent in a VCS environment Before you install the Cluster Server agent for WebLogic Server You must install the Cluster Server agent for WebLogic Server on all the systems that will host WebLogic Server service groups. Before you install the agent for WebLogic Server, ensure that the following prerequisites are met. Install and configure Cluster Server. For more information on installing and configuring Cluster Server, refer to the Cluster Server installation and configuration guides.

14 Installing, upgrading, and removing the agent for WebLogic Server About the ACC library 14 Remove any previous version of this agent. To remove the agent, See Uninstalling the agent in a VCS environment on page 21. Install the latest version of ACC Library. To install or update the ACC Library package, locate the library and related documentation in the Agent Pack tarball. See About the ACC library on page 14. Prerequisites for enabling i18n support Perform the following steps to enable i18n support to the agent: Install ACCLib version or later. See Installing the ACC library on page 15. For VCS 5.0 and earlier releases, copy the latest ag_i18n_inc.pm module from the following location on the agent pack disc. Note: Review the readme.txt for instructions to copy this module. VCS 5.0 VCS 4.1 VCS 4.0 cd1/platform/arch_dist/vcs/application/i18n_support/5.0 cd1/platform/arch_dist/vcs/application/i18n_support/4.1 cd1/platform/arch_dist/vcs/application/i18n_support/4.0 where arch_dist takes the following values: 'sol_sparc' for Solaris SPARC 'generic' for Linux Note: arch_dist is not applicable to AIX. About the ACC library The operations of a Cluster Server agent depend on a set of Perl modules known as the ACC library. The library must be installed on each system in the cluster that runs the agent. The ACC library contains common, reusable functions that perform tasks, such as process identification, logging, and system calls.

15 Installing, upgrading, and removing the agent for WebLogic Server Installing the ACC library 15 Instructions to install or remove the ACC library on a single system in the cluster are given in the following sections. The instructions assume that the ACCLib tar file has already been extracted. Note: The LogDbg attribute should be used to enable debug logs for the ACCLibbased agents when the ACCLib version is or later and VCS version is 6.2 or later. Installing the ACC library Install the ACC library on each system in the cluster that runs an agent that depends on the ACC library. To install the ACC library 1 Log in as a superuser. 2 Download ACC Library. You can download either the complete Agent Pack tar file or the individual ACCLib tar file from the Veritas Services and Operations Readiness Tools (SORT) site ( 3 If you downloaded the complete Agent Pack tar file, navigate to the directory containing the package for the platform running in your environment. AIX Linux Solaris cd1/aix/vcs/application/acc_library/version_library/pkgs cd1/linux/generic/vcs/application/acc_library/version_library/rpms cd1/solaris/dist_arch/vcs/application/acc_library/version_library/pkgs where dist_arch is sol_sparc.

16 Installing, upgrading, and removing the agent for WebLogic Server Installing the ACC library 16 4 If you downloaded the individual ACCLib tar file, navigate to the pkgs directory (for AIX and Solaris), or rpms directory (for Linux). 5 Install the package. Enter, if asked to confirm overwriting of files in the existing package. AIX Linux Solaris # installp ac d VRTSacclib.bff VRTSacclib # rpm i \ VRTSacclibVersionNumberGA_GENERIC.noarch.rpm # pkgadd d VRTSacclib.pkg Note: To install the ACCLib IPS package on a Solaris 11 system, see Installing the ACC library IPS package on Oracle Solaris 11 systems. Note: The LogDbg attribute should be used to enable debug logs for the ACCLibbased agents when the ACCLib version is or later and VCS version is 6.2 or later. Installing the ACC library IPS package on Oracle Solaris 11 systems Install the ACC library IPS package on an Oracle Solaris 11 system. To install the ACC library IPS package on Oracle Solaris 11 systems 1 Copy the VRTSacclib.p5p package from the pkgs directory to the system in the /tmp/install directory. 2 Disable the publishers that are not reachable as package install may fail, if any, of the already added repositories are unreachable. # pkg setpublisher disable <publisher name> 3 Add a filebased repository in the system. # pkg setpublisher g /tmp/install/vrtsacclib.p5p Veritas 4 Install the package. # pkg install accept VRTSacclib 5 Remove the publisher from the system. # pkg unsetpublisher Veritas 6 Enable the publishers that were disabled earlier. # pkg setpublisher enable <publisher name>

17 Installing, upgrading, and removing the agent for WebLogic Server Installing the ACC library 17 Installing the ACC library package on Solaris brand nonglobal zones With Oracle Solaris 11, you must install the ACC library package inside nonglobal zones. The native nonglobal zones are called Solaris brand zones. To install the ACC library package on Solaris brand nonglobal zones 1 Ensure that the SMF services, svc:/application/pkg/systemrepository:default and svc:/application/pkg/zonesproxyd:default, are online on the global zone. # svcs svc:/application/pkg/systemrepository:default # svcs svc:/application/pkg/zonesproxyd:default 2 Log on to the nonglobal zone as a superuser. 3 Ensure that the SMF service svc:/application/pkg/zonesproxyclient:default is online inside the nonglobal zone: # svcs svc:/application/pkg/zonesproxyclient:default 4 Copy the VRTSacclib.p5p package from the pkgs directory to the nonglobal zone (for example, at the /tmp/install directory). 5 Disable the publishers that are not reachable, as package install may fail, if any of the already added repositories are unreachable. # pkg setpublisher disable <publisher name> 6 Add a filebased repository in the nonglobal zone. # pkg setpublisher g/tmp/install/vrtsacclib.p5p Veritas 7 Install the package. # pkg install accept VRTSacclib 8 Remove the publisher on the nonglobal zone. # pkg unsetpublisher Veritas 9 Clear the state of the SMF service, as setting the filebased repository causes the SMF service svc:/application/pkg/systemrepository:default to go into the maintenance state. # svcadm clear svc:/application/pkg/systemrepository:default 10 Enable the publishers that were disabled earlier. # pkg setpublisher enable <publisher>

18 Installing, upgrading, and removing the agent for WebLogic Server Installing the agent in a VCS environment 18 Note: Perform steps 2 through 10 on each nonglobal zone. Installing the agent in a VCS environment Install the agent for WebLogic Server on each node in the cluster. To install the agent in a VCS environment 1 Download the agent from the Veritas Services and Operations Readiness Tools (SORT) site: You can download either the complete Agent Pack tar file or an individual agent tar file. 2 Uncompress the file to a temporary location, say /tmp. 3 If you downloaded the complete Agent Pack tar file, navigate to the directory containing the package for the platform running in your environment. AIX cd1/aix/vcs/application/weblogic_agent/ vcs_version/version_agent/pkgs Linux cd1/linux/generic/vcs/application/weblogic_agent/ vcs_version/version_agent/rpms Solaris cd1/solaris/dist_arch/vcs/application/weblogic_agent/ vcs_version/version_agent/pkgs where, dist_arch is sol_sparc If you downloaded the individual agent tar file, navigate to the pkgs directory (for AIX and Solaris), or rpms directory (for Linux).

19 Installing, upgrading, and removing the agent for WebLogic Server Installing the agent in a VCS environment 19 4 Log in as a superuser. 5 Install the package. AIX # installp ac d VRTSwls.rte.bff VRTSwls.rte Linux # rpm ihv \ VRTSwlsAgentVersionGA_GENERIC.noarch.rpm Solaris # pkgadd d. VRTSwls Note: See Installing the agent IPS package on Oracle Solaris 11 systems on page 19. After installing the agent package, you must import the agent type configuration file. See Importing the agent types files in a VCS environment on page 26. Installing the agent IPS package on Oracle Solaris 11 systems To install the agent IPS package on an Oracle Solaris 11 system 1 Copy the VRTSwls.p5p package from the pkgs directory to the system in the /tmp/install directory. 2 Disable the publishers that are not reachable as package install may fail, if any of the already added repositories are unreachable. # pkg setpublisher disable <publisher name> where the publisher name is obtained using the pkg publisher command. 3 Add a filebased repository in the system. # pkg setpublisher g /tmp/install/vrtswls.p5p Veritas 4 Install the package. # pkg install accept VRTSwls 5 Remove the publisher from the system. # pkg unsetpublisher Veritas 6 Enable the publishers that were disabled earlier. # pkg setpublisher enable <publisher name>

20 Installing, upgrading, and removing the agent for WebLogic Server Installing the agent in a VCS environment 20 Installing agent packages on Solaris brand nonglobal zones To install the agent package on Solaris brand nonglobal zones 1 Ensure that the SMF services, svc:/application/pkg/systemrepository:default and svc:/application/pkg/zonesproxyd:default, are online on the global zone. # svcs svc:/application/pkg/systemrepository:default # svcs svc:/application/pkg/zonesproxyd:default 2 Log on to the nonglobal zone as a superuser. 3 Ensure that the SMF service svc:/application/pkg/zonesproxyclient:default is online inside nonglobal zone: # svcs svc:/application/pkg/zonesproxyclient:default 4 Copy the VRTSwls.p5p package from the pkgs directory to the nonglobal zone (for example, at the /tmp/install directory). 5 Disable the publishers that are not reachable, as package install may fail, if any of the already added repositories are unreachable. # pkg setpublisher disable <publisher name> 6 Add a filebased repository in the nonglobal zone. # pkg setpublisher g/tmp/install/vrtswls.p5p Veritas 7 Install the package. # pkg install accept VRTSwls 8 Remove the publisher on the nonglobal zone. # pkg unsetpublisher Veritas 9 Clear the state of the SMF service, as setting the filebased repository causes the SMF service svc:/application/pkg/systemrepository:default to go into the maintenance state. # svcadm clear svc:/application/pkg/systemrepository:default 10 Enable the publishers that were disabled earlier. # pkg setpublisher enable <publisher> Note: Perform steps 2 through 10 on each nonglobal zone.

21 Installing, upgrading, and removing the agent for WebLogic Server Uninstalling the agent in a VCS environment 21 Installing the agent in a Solaris 10 brand zone To install the WebLogic Server agent in a brand zone on Solaris 10: Ensure that the ACClibrary package, VRTSacclib, is installed in the nonglobal zone. To install VRTSacclib in the nonglobal zone, run the following command from the global zone: # pkgadd R /zones/zone1/root d VRTSacclib.pkg To install the agent package in the nonglobal zone, run the following command from the global zone: # pkgadd R zoneroot/root d. VRTSwls For example: # pkgadd R /zones/zone1/root d. VRTSwls Note: You can ignore the following messages that might appear: ## Executing postinstall script. ln: cannot create /opt/vrtsagents/ha/bin/weblogic/imf_getnotification: File exists ln: cannot create /opt/vrtsagents/ha/bin/weblogic/imf_register: File exists or ## Executing postinstall script. ln: cannot create /opt/vrtsagents/ha/bin/weblogic/imf_getnotification: No such file or directory ln: cannot create /opt/vrtsagents/ha/bin/weblogic/imf_register: No such file or directory Uninstalling the agent in a VCS environment You must uninstall the agent for WebLogic Server from a cluster while the cluster is active. To uninstall the agent in a VCS environment 1 Log in as a superuser. 2 Set the cluster configuration mode to read/write by running the following command from any node in the cluster: # haconf makerw

22 Installing, upgrading, and removing the agent for WebLogic Server Removing the ACC library 22 3 Remove all WebLogic Server resources from the cluster. Run the following command to verify that all resources have been removed: # hares list Type=WebLogic 4 Remove the agent type from the cluster configuration by running the following command from any node in the cluster: # hatype delete WebLogic Removing the agent s type file from the cluster removes the include statement for the agent from the main.cf file, but the agent's type file is not removed from the cluster configuration directory. You can remove the agent s type file later from the cluster configuration directory. 5 Save these changes. Then set the cluster configuration mode to readonly by running the following command from any node in the cluster: # haconf dump makero 6 Use the platform's native software management program to remove the agent for WebLogic Server from each node in the cluster. Run the following command to uninstall the agent: AIX Linux Solaris # installp u VRTSwls.rte # rpm e VRTSwls # pkgrm VRTSwls Note: To uninstall the agent IPS package on a Solaris 11 system, run the following command: # pkg uninstall VRTSwls Removing the ACC library Perform the following steps to remove the ACC library.

23 Installing, upgrading, and removing the agent for WebLogic Server Upgrading the agent in a VCS environment 23 To remove the ACC library 1 Ensure that all agents that use ACC library are removed. 2 Run the following command to remove the ACC library package: AIX Linux Solaris # installp u VRTSacclib # rpm e VRTSacclib # pkgrm VRTSacclib Note: To uninstall the ACCLib IPS package on a Solaris 11 system, run the following command: # pkg uninstall VRTSacclib Upgrading the agent in a VCS environment Perform the following steps to upgrade the agent with minimal disruption, in a VCS environment. Updating the agent using the update script The WebLogic package (VRTSwls) contains a script named wls_update.pl. This script updates the WebLogic9 agent type to WebLogic and reconfigures all the existing resources of the WebLogic9 agent type with the WebLogic agent type. This script also removes the WebLogic9 agent type. To update the agent using the update script 1 Install the WebLogic Server agent package (VRTSwls) on all nodes. See Installing the agent in a VCS environment on page Navigate to the agent source directory: 3 Run the wls_update.pl script available in the agent directory. bash3.00#./wls_update.pl 4 Follow the prompts to update the agent type. 5 Do you want to go ahead with Update process (y/n):y Are you sure to update [WebLogic9] Type to [WebLogic] Type (y/n):y Do you want to Delete the Agent Type WebLogic9(y/n):y

24 Installing, upgrading, and removing the agent for WebLogic Server Upgrading the agent in a VCS environment 24 6 If the script runs successfully, the following messages are displayed: Old Agent type [WebLogic9] has been deleted The old agent type[ WebLogic9 ] is successfully replaced by new agent type [WebLogic] For more details check the log file [/var/vrtsvcs/log/tmp/weblogic_10881/wls_update.log] 7 Use the platform s native software management program to remove the old agent package (VRTSwls9) for WebLogic Server from each node in the cluster. Run the following command to uninstall the agent: AIX Linux Solaris # installp u VRTSwls9.rte # rpm e VRTSwls9 For Solaris 10: # pkgrm VRTSwls9 For Solaris 11: # pkg uninstall VRTSwls9 8 This completes the procedure for updating the WebLogic9 agent type to WebLogic. Note: If you upgraded the VCS version to VCS 5.1 SP1 and the WebLogic Server agent version to (or later), and if you had enabled detail monitoring in the previous version, then do the following: Set the value of the LevelTwoMonitorFreq attribute to the same value as that of the SecondLevelMonitor attribute.

25 Chapter 3 Configuring the agent for WebLogic Server This chapter includes the following topics: About configuring the Cluster Server agent for WebLogic Server Importing the agent types files in a VCS environment WebLogic Server agent attributes Executing secondlevel monitoring Executing a customized monitoring program Uniquely identifying WebLogic Server instances Attributes used in different resource configurations Using WebLogic provided scripts Avoiding storing unencrypted credentials in startup/shutdown scripts Delaying managed server startup process Configuring multiple Administrative Servers that have the same name for different domains About configuring the Cluster Server agent for WebLogic Server After installing the Cluster Server agent for WebLogic Server, you must import the agent type configuration file. After importing this file, review the attributes table that

26 Configuring the agent for WebLogic Server Importing the agent types files in a VCS environment 26 describes the resource type and its attributes, and then create and configure WebLogic Server resources. To view the sample agent type definition and service groups configuration: See About sample configurations for the agents for WebLogic Server on page 77. Importing the agent types files in a VCS environment To use the agent for WebLogic Server, you must import the agent types file into the cluster. You can import the agent types file using the VCS graphical user interface or using the command line interface. To import the agent types file using the VCS Java GUI 1 Start the Cluster Manager (Java Console) and connect to the cluster on which the agent is installed. 2 Click File > Import Types. 3 In the Import Types dialog box, select the following file: VCS 4.x VCS 5.x or later VCS 5.0 VCS 5.1 or later AIX Linux Solaris AIX Linux Solaris SPARC Solaris SPARC /etc/vrtsvcs/conf/sample_weblogic/ WebLogicTypes.cf /etc/vrtsagents/ha/conf/weblogic/ WebLogicTypes.cf /etc/vrtsagents/ha/conf/weblogic/ WebLogicTypes50.cf /etc/vrtsagents/ha/conf/weblogic/ WebLogicTypes51.cf 4 Click Import. 5 Save the VCS configuration. The WebLogic Server agent type is now imported to the VCS engine. You can now create WebLogic Server resources. For additional information about using the VCS GUI, refer to the Cluster Server Administrator's Guide.

27 Configuring the agent for WebLogic Server WebLogic Server agent attributes 27 To import the agent types file using the CLI 1 Log on to any one of the systems in the cluster as the superuser. 2 Create a temporary directory. # mkdir./temp # cd./temp 3 Copy the sample file Types.cf. 4 Create a dummy main.cf file. # echo 'include "WebLogicTypes.cf"' > main.cf 5 Create the WebLogic Server resource type as follows: # hacf verify. # haconf makerw # sh main.cmd # haconf dump WebLogic Server agent attributes Refer to the following required and optional attributes while configuring the agent for WebLogic Server. Table 31 lists the required attributes for the agent for WebLogic Server. Table 31 Required attributes Required attribute BEA_HOME Description The absolute path to BEA home directory of WebLogic Server installation. BEA_HOME is used to uniquely identify the ServerRole processes. Type and dimension: stringscalar Default: "" Example: /bea/wls90/admin

28 Configuring the agent for WebLogic Server WebLogic Server agent attributes 28 Table 31 Required attributes (continued) Required attribute DomainDir Description The domain directory of the WebLogic Server domain to which the instance belongs. The agent for WebLogic Server uses this attribute to connect to the Node Manager using the wlst.sh utility. Specify this attribute for Administrative and Managed Servers. If the SecondLevelMonitor attribute is specified, specify this attribute for the Node Manager also. Type and dimension: stringscalar Default: "" Example: /bea/wls90/admin/user_projects/domains/wls90domain ListenAddressPort The Listen Address and port of the WebLogic instance. The format is ListenAddress:port. Ensure that the ListenAddress string resolves to the proper IP Address, using the network name service that you used on the host. The WebLogic Server connects to the ListenAddress on the specified port through the wlst.sh API. Specify this attribute for Administrative and Managed Servers only. Type and dimension: stringscalar Default: "" Example: wls90adminsol.veritas.com:7001 or wls90adminsol.veritas.com:5556 nmhome The absolute path to the Node Manager home directory. Specify this attribute for Node Manager based configurations only. Type and dimension: stringscalar Default: "" Example 1: /bea/wls90/admin/weblogic90/common/nodemanager Example 2: /bea/wls90/admin/user_projects/domains/nodemanager

29 Configuring the agent for WebLogic Server WebLogic Server agent attributes 29 Table 31 Required attributes (continued) Required attribute nmlistenaddressport Description The Listen Address and port of the WebLogic Node Manager. The format is ListenAddress:port. The value of this attribute must match the values of ListenAddress and ListenPort that appear in the long listing of processes for a Node Manager instance. The ListenAddress string must resolve to a proper IP Address, using the network name service that you used on the host. The agent for WebLogic Server uses the ListenAddress on the specified port to connect through the wlst.sh API. Type and dimension: stringscalar Default: "" Example: wlsadmin:5556 nmuser The user name of the Node Manager. The agent uses this user identity, along with the nmpassword, to connect to the Node Manager. Specify this attribute for Node Manager based configurations only. Type and dimension: stringscalar Example: weblogic Default: "" nmpassword The password of the Node Manager. The agent uses this password, along with the nmuser, to connect to the Node Manager. For VCS, encrypt the value of this attribute using the $VCS_HOME/bin/vcsencrypt utility that VCS provides. Specify this attribute for Node Manager based configurations only. Type and dimension: stringscalar Default: "" Example: HTIvKTlTNnINjNKnL nmtype The WebLogic Node Manager type. This type is used while connecting to the Node Manager through the wlst.sh script. Valid values include: plain: plain socket Javabased implementation rsh: RSH implementation ssh: scriptbased SSH implementation ssl: Javabased SSL implementation Type and dimension: stringscalar Default: ssl Example: ssh

30 Configuring the agent for WebLogic Server WebLogic Server agent attributes 30 Table 31 Required attributes (continued) Required attribute ResLogLevel Description The logging detail performed by the agent for WebLogic Server for the resource. Valid values are: ERROR: Only logs error messages. WARN: Logs above plus warning messages. INFO: Logs above plus informational messages. TRACE: Logs above plus trace messages. TRACE is very verbose and should only be used during initial configuration or for troubleshooting and diagnostic operations. Type and dimension: stringscalar Default: INFO Example: TRACE Note: You must use the LogDbg attribute instead of the ResLogLevel attribute to enable debug logs for the ACCLibbased agents, when the ACCLib version is or later and the VCS version is 6.2 or later. The agent captures the first failure data of the unexpected events and automatically logs debug messages in their respective agent log files. ServerName The name of the WebLogic Server. You must specify this attribute for Administrative and Managed Servers only. See Uniquely identifying WebLogic Server instances on page 40. Type and dimension: stringscalar Default: "" Example: AdminServer ShutdownTimeout The timeout value, in milliseconds, which is passed on to the wlst.sh script. The wlst.sh script uses this value to instruct the agent to shut down a specified server forcefully, if the shutdown() command is not completed in the given timeframe. If the value of this attribute is set to 0, the agent tries to gracefully shut down the specified server till the value specified in the OfflineTimeout attribute of the Offline function. If even after exceeding the value specified in the OfflineTimeout attribute, the resource is still not offline, the agent runs the Clean function. If the value of this attribute is greater than 0, then that value is passed on to shutdown() command via the wlst.sh script. Type and dimension: integerscalar Default: "" Example: 1000

31 Configuring the agent for WebLogic Server WebLogic Server agent attributes 31 Table 31 Required attributes (continued) Required attribute WlstScript Description The absolute path to the wlst.sh utility. Type and dimension: stringscalar Default: "" Example: /bea/wls90/admin/weblogic90/common/bin/wlst.sh WLSUser The user name of the user that is connecting the wlst.sh utility to the server running the WebLogic Server instance, along with WLSPassword. Type and dimension: stringscalar Default: "" ServerRole Type of WebLogic Server. Valid values are: NodeManager: Online operation executes wlst.sh script with startnodemanager() API. Example: startnodemanager(verbose='true',nodemanagerhome='/bea/wls90/admin/ weblogic90/common/nodemanager',listenport='5556',listenaddress='wls90adminsol') Administrative: Online operation executes wlst.sh script with nmconnect() and nmstart() API. Example: nmstart ( AdminServer1 ) Managed: Online operation executes wlst.sh script with nmconnect() and nmstart() API. Example: nmstart ( ManagedServer1 ) Type and dimension: stringscalar Default: "" Example: Administrative

32 Configuring the agent for WebLogic Server WebLogic Server agent attributes 32 Table 31 Required attributes (continued) Required attribute ServerStartProgram Description The complete command line of the script used to start WebLogic Server. If command line arguments are passed to ServerStartProgram, the agent uses the command and arguments as it is. Example: For Administrative Server ServerStartProgram = "/wls/my_domain/startweblogic.sh For Managed Server ServerStartProgram = "/wls/my_domain/startmanagedweblogic.sh Managed1 t3://wlsadmin:7001" ServerStartProgram = "/wls/my_domain/startmanagedweblogic.sh Managed1 t3s://wlsadmin:9002" If no arguments are passed, the agent forms the command line as follows: For Managed Server: $ServerStartProgram $ServerName $AdminURL For Administrative Server: $ServerStartProgram Type and dimension: stringscalar Default: "" Example: /bea/user_projects/domains/wls90domain/bin/startweblogic.sh

33 Configuring the agent for WebLogic Server WebLogic Server agent attributes 33 Table 31 Required attributes (continued) Required attribute ServerStopProgram Description The complete command line of the script used to stop WebLogic Server. If command line arguments are passed to ServerStopProgram, the agent uses the command and arguments as it is. Example: For Administrative Server ServerStopProgram = "/wls/my_domain/stopweblogic.sh ServerStopProgram = "/wls/my_domain/stopweblogic.sh wlsuser wlspasswd t3s://wlsadmin:9002 For Managed Server ServerStopProgram = "/wls/my_domain/stopmanagedweblogic.sh Managed1 t3://wlsadmin:7001 wlsuser wlspasswd" ServerStopProgram = "/wls/my_domain/stopmanagedweblogic.sh Managed1 t3s://wlsadmin:9002 wlsuser wlspasswd" If no arguments are passed, the agent forms the command line as follows: For Managed Server: $ServerStopProgram $ServerName $AdminURL $WLSUser $WLSPassword For Administrative Server: $ServerStopProgram Type and dimension: stringscalar Default: "" Example: /bea/user_projects/domains/wls90domain/bin/stopweblogic.sh User The UNIX user name used to start and stop the WebLogic Server instance. If MonitorProgram is specified, the agent for WebLogic Server uses this user's credentials to run the defined program. You must synchronize the user name across the systems within the cluster. This user name must resolve to the same UID and have the same default shell on each system in the cluster. The agent operations use the getpwname(3c) function system call to obtain UNIX user attributes. Hence you can define the user name locally or in a common repository such as NIS, NIS+, or LDAP. Type and dimension: stringscalar Default: "" Example: wlsadmin

34 Configuring the agent for WebLogic Server WebLogic Server agent attributes 34 Table 31 Required attributes (continued) Required attribute WLSPassword Description The password of user connecting WLST to ServerRole Application Server, along with WLSUser. Encrypt the value of this attribute using the $VCS_HOME/bin/vcsencrypt utility that VCS provides. While encrypting the password, use the agent option. Type and dimension: stringscalar Default: "" Example: weblogic Table 32 lists the optional attributes.

35 Configuring the agent for WebLogic Server WebLogic Server agent attributes 35 Table 32 Optional attributes Optional attribute AdminUrl Description The URL of the Administrative Server. If the Administrative Server uses the http or t3 protocol, set this attribute only for those resources whose ServerRole attribute is Managed. If the Administrative server uses the https or t3s protocol, set this attribute for those resources whose ServerRole attribute is Administrative or Managed. For the Managed Server, ensure that the value of this attribute contains the Administrative Server host name and port that appear in the long listing of processes for the Managed Server. If the value of this attribute is different, the agent fails to find the process. For example, the value of this attribute could be <protocol>://wlsadmin:7001, where: <protocol> is the protocol that is used to connect to the WebLogic Server. If the WebLogic Server port is secure or if tunneling is enabled, the protocol value is https or t3s; in other cases, the protocol value is http or t3. You must ensure that the WebLogic Server can be connected with the specified protocol value using the wlst.sh script. wlsadmin is the Administrative Server host name 7001 is the Administrative Server port. If the RequireAdminServer attribute is set to 1, AdminUrl is used to connect to the Administrative Server of the specified domain to determine if the server is fully online. Managed Servers also use this URL to connect to the Administrative Server and download its web applications and services (JMS, JDBC Connection Pool, etc.) configuration. Type and dimension: stringscalar Default: "" Example 1: t3://wlsadmin:7001 Example 2: t3s://wlsadmin:7001 AdminServerMaxWait The maximum number of seconds that a Managed Server waits for an Administrative Server to respond to a test probe. See Delaying managed server startup process on page 46. Type and dimension: integerscalar Default: 60 Example: 90

36 Configuring the agent for WebLogic Server WebLogic Server agent attributes 36 Table 32 Optional attributes (continued) Optional attribute LogDbg Description For ACCLibbased agents, you must use the LogDbg resource type attribute to enable the debug logs when the ACCLib version is or later and the VCS version is 6.2 or later. Set the LogDbg attribute to DBG_5 to enable debug logs for ACCLIB based agent. By default, setting the LogDbg attribute to DBG_5 enables debug logs for all WebLogic resources in the cluster. If debug logs must be enabled for a specific WebLogic resource, override the LogDbg attribute. Type and dimension: stringkeylist Default: {} (none) For more information on how to use the LogDbg attribute, refer to the Cluster Server Administrator s Guide. MonitorProgram The full pathname and commandline arguments for an externally provided monitor program. See Executing a customized monitoring program on page 39. Type and dimension: stringscalar Default: "" Example 1: /bea/wls90/admin/mymonitor.sh Example 2: /usr/local/bin/mymonitor.sh mywls.foo.com 8080 RequireAdminServer The flag that is used to control the startup behavior of a WebLogic Server instance. When the RequireAdminServer attribute is set to 1 (true), the Managed Server resource is not allowed to complete an initiated online operation until the Administrative Server is ready to accept connections. If the RequireAdminServer attribute is set to 0 and the AdminServerMaxWait is set to a value > 5, the online operation first probes the Administrative Server instance to see if it is ready to accept connections. If the server is not ready, the operation waits for 5 seconds and then probes the server again to determine its state. This cycle of probe and wait repeats until either the Administrative Server is ready or the AdminServerMaxWait time expires. Specify this attribute for Managed Server only. Type and dimension: booleanscalar Default: 0 (false) Example: 1 (true)