Compatibility information and installation requirements

Step 1

Step 2

Install OpenSSL, if necessary

Step 4

Step 5

Step 6

Step 7

Shut down WLM if it is already running

Step 9

Step 10

Step 11

Step 12

Step 13

Verify that HP-UX is up-to-date

HP suggests that as part of your systems’ ongoing maintenance and support, the systems be kept up-to-date through the HP IT Resource Center’s Support Plus program. This program delivers quarterly patch bundles via the web and as part of the quarterly AR media. To register, go to the following location:

http://itrc.hp.com

Select the patch/firmware database link and register to create an account and log in, as instructed. After logging in, scroll down to the “find standard patch bundles” section and select “HP-UX patch bundles”. The bundles of interest are “Quality Pack” and “Support Plus”.

For HP-UX 11i v1 (B.11.11), the recommended bundles are described in the following table:

If you are using HP-UX 11i v1 (B.11.11) and are interested in using processor sets (PSETs), you can download software (to support processor sets) from the following location:

http://www.hp.com/go/wlm

Select the Patches/support link and search for “processor sets”. This software also corrects several problems (see section “System panic when PRM is enabled; install failure in absence of PRM when certain kernel patches are present”).

	NOTE: Install GOLDQPK11i before installing the processor sets software—unless you are using a depot to install them at the same time.

Processor sets are included with HP-UX 11i v2 (B.11.23) and HP-UX 11i v3 (B.11.31).

For HP-UX 11i v2 (B.11.23), install the following patches:]

1. Determine which patch bundles are already on the system

   Run the swlist command, which will list the bundle if found:

   # /usr/sbin/swlist -l bundle patch_bundle

   where patch_bundle is GOLDBASE11i, GOLDAPPS11i, or HWEnable11i

2. Download any missing patch bundles from the following location: http://www.hp.com/go/softwareinfo/SUPPORT_PLUS/ to /tmp

   	NOTE: Do not install these patch bundles at this point.

Related support sites include:

(Optional) Configure long hostnames

Ensure the NodeHostNameXpnd bundle is installed if you want to use long host names on HP-UX 11i v2 or v3. Configure long host names as described below.

Set the kernel tunable to allow long hostnames:

# kctune expanded_node_host_names=1

Set the node and hostname, with the changes being persistent across boots:

# /sbin/set_parms hostname

where hostname is the literal string hostname—not the desired hostname. You will be prompted for the hostname.

For configuration information, read the paper “Node and Host Name Sizes on HP-UX,” available in /usr/share/doc/NodeHostNameSize.pdf on systems with the NodeHostNameXpnd bundle installed.

Install OpenSSL, if necessary

If you download software from the Web and create a software depot of your own, OpenSSL A.00.09.07-d or later must be installed on the system on which you are installing WLM. You can obtain the OpenSSL software from the HP Software Depot (http://www.hp.com/go/softwaredepot). If you are installing WLM from the quarterly AR CD-ROM, the required OpenSSL software is installed with WLM.

Determine what patches are needed

1. Check the following data to determine what patches are suggested for WLM:

   If you plan to use the WLM configuration wizard, the wlmgui command, or wlminfo’s interactive mode GUI (-i), all of which depend on Java (Java Runtime Environment version 1.4.2 or later is required), refer to the following location for patch information:

   http://www.hp.com/go/java

   In addition, running these utilities with PRM-based configurations requires PRM C.03.00 or later.

   On HP-UX 11i v1, apply patch PHCO_29109 to address a pthread library issue.

   For the latest information on WLM patches, visit the “Patches / support” page available from the following location:

   http://www.hp.com/go/wlm

   For HP-UX 11i v1, the following patches are available:

   Table 1-4 HP-UX 11i v1 (B.11.11) patches for WLM

   HP-UX 11i v1 patch[1]	Description
   PHKL_33372	Memory Resource Groups (MRG) patch (supersedes PHKL_32619)
   PHKL_30034, PHKL_30035, PHKL_31993, PHKL_31995, PHKL_32061	NOTE: Install all these patches at the same time. These patches: Preserve allocations in cases where a workload group with a large allocation and just enough jobs to get that allocation could be outperformed by a smaller allocation group with more jobs Improve performance of I/O-based applications when the Fair-Share Scheduler (FSS) is enabled
   [1] These patches might have been superseded. You can use these listed patches or their superseding patches.

    

   For HP-UX 11i v2 (B.11.23), install the following patches:]

   Table 1-5 HP-UX 11i v2 (B.11.23) patches for WLM

   HP-UX 11i v2 patch[1]	Description
   BUNDLE11i patch bundle	Bundle of patches (Installing this bundle updates your system to HP-UX 11i v2 Update 2.)
   PHKL_32518	Allows you to create more than 64 workload groups—assuming you have already installed BUNDLE11i.
   PHKL_33052	Prevents performance degradation when using workload groups that are based on FSS groups in a single-processor virtual partition, nPartition, or system
   PHKL_33604, PHKL_33605	NOTE: Install these patches at the same time. These patches help ensure each job within a FSS-based workload group gets a more equal share of the group’s allocation than it would under HP-UX semantics.
   [1] These patches might have been superseded. You can use these listed patches or their superseding patches.

    

2. Determine which patches are already on the system

   If a recent Quality Pack is installed, some of these patches may already be on your system. To determine if these patches are installed, use swlist as follows:

   # /usr/sbin/swlist [-l patch] patch

   where patch is the patch’s tag. For example, to check that patch PHKL_32061 is installed, use the following command line:

   # /usr/sbin/swlist -l patch PHKL_32061

   Similarly, if you downloaded patch bundles in Step 1, check the bundles for the patches:

   # /usr/sbin/swlist -d patch @ /tmp/bundle_name

   If a given patch is not listed, check HP’s IT Resource Center (http://itrc.hp.com) for a superseding patch, then use swlist to list the superseding patch.

3. Download any missing patches to /tmp.

   If any of the required patches are missing (not installed or not in a bundle you downloaded), download the patches from HP’s IT Resource Center:

   Americas/Asia-Pacific

   http://itrc.hp.com/

   Europe

   http://europe.itrc.hp.com/

   	NOTE: Do not install these patches at this point.

(Optional) Create a software depot to minimize system reboots

Creating a depot is beneficial when you are completing two or more of the following tasks:

Completing two or more of the above tasks will cause multiple reboots unless you create a software depot. With a depot including all the patches, the patch bundles, and WLM, you can combine the installation steps into a single operation, thereby limiting the number of installation reboots that must occur.

If you do not mind multiple reboots or your system will not be subject to multiple reboots because its software is up-to-date, proceed to Step Step 6, Step 6.

In order to install these items with a single swinstall(1M) command, all of the related filesets must be collected into a single software depot distribution directory.

The following steps outline how to create a software depot. The steps use examples showing how to include the following items in your depot:

	NOTE: To satisfy SD-UX, it may be necessary to copy dependency filesets into this common depot.

1. Ensure that adequate disk space is available. The size of each patch can be found in its README text.

2. Create a directory for the depot:

   # mkdir /tmp/wlm_depot

3. Place any patch bundles you downloaded in Step 1 (GOLDQPK11i or HWEnable11i) in /tmp/ if they are not already there.

   For more information on these patch bundles, refer to Table 1-2 “HP-UX 11i v1 (B.11.11) general support patches”.

4. Check each of the patch bundles.

   # /usr/sbin/swlist -d @ bundle_path

   For example, check GOLDQPK11i as follows:

   # swlist -d @ /tmp/GOLDQPK11i_11.11.depot

   The output should include lines similar to the following lines:

   GOLDAPPS11i B.11.11.0312.4 Gold Applications Patches for HP-UX 11i v1, December 2003

   GOLDBASE11i B.11.11.0312.4 Gold Base Patches for HP-UX 11i v1, December 2003

   If your output is not similar, please download the file again.

5. Add the patch bundles to the depot:

   # /usr/sbin/swcopy -s bundle_path bundle_name @ depot_path

   where bundle_path and depot_path are fully specified path names, and bundle_name is the patch bundle’s tag. For example:

   # swcopy -s /tmp/GOLDQPK11i_11.11.depot GOLDAPPS11i @ /tmp/wlm_depot

   # swcopy -s /tmp/GOLDQPK11i_11.11.depot GOLDBASE11i @ /tmp/wlm_depot

   This step automatically registers the wlm_depot. Therefore, there is no need to register it using the swreg command.

6. Verify the depot:

   # /usr/sbin/swverify -d \* @ depot_path

   where depot_path is a fully specified pathname. For example:

   # swverify -d \* @ /tmp/wlm_depot

7. Place any missing individual patches that you downloaded in Step 4 in /tmp/.

   For HP-UX 11i v1 (B.11.11) patches, refer to Table 1-4 “HP-UX 11i v1 (B.11.11) patches for WLM”.
   For HP-UX 11i v2 (B.11.23) patches, refer to Table 1-5 “HP-UX 11i v2 (B.11.23) patches for WLM”.
   

8. Add each patch file to the depot:

   # swcopy -s patch_file_path \* @ depot_path

   where patch_file_path and depot_path are fully specified path names. For example:

   # swcopy -s /tmp/PHKL_32619.depot \* @ /tmp/wlm_depot

9. Verify the depot:

   # swverify -d \* @ depot_path

   where depot_path is a fully specified pathname. For example:

   # swverify -d \* @ /tmp/wlm_depot

10. Ensure perl is available at /opt/perl/bin/perl

    If you intend to use the:

    • wlmaudit utility to display audit reports

    • wlmoradc or smooth utilities from the WLM Oracle Database Toolkit (ODBTK)

    • expsmooth utility from the WLM BEA WebLogic Server Toolkit (WebLogicTK)

    • wlmcert utility and secure network communications

    and perl is not available at /opt/perl/bin/perl:

    • If perl is not already installed, add it to your depot from the quarterly Application Release (AR) CD-ROM using the following swcopy line:

      # swcopy -s mount_path perl \* @ /tmp/wlm_depot

      where mount_path is the path to the quarterly AR CD-ROM.

    • If perl is installed, but in a location other than /opt/perl/bin/perl, ensure there is a symbolic link from /opt/perl/bin/perl to your perl.

11. Locate and mount the WLM installation media. For assistance, consult mount_cdfs(1M), or use SAM, SMH, or the SD-UX Interactive User Interface for swcopy, which you can use to “find” the CD-ROM.

12. Add WLM (product B8843CA) to the depot.

    	NOTE: The WLM bundle B8843CA requires a customer_id/codeword pair to unlock it from the quarterly AR CD-ROM. Purchase of WLM entitles you to this codeword, which can be found on the Software Certificate you received from HP. The WLM codeword is needed to complete the next step.

    Use a line similar to the following to add WLM to your depot:

    # /usr/sbin/swcopy -x customer_id=cust_id \ -x codeword=codeword \ -s mount_path \ B8843CA @ depot_path

    where mount_path is the path to the CD-ROM and depot_path is the same fully specified depot as in previous steps. For example:

    # swcopy -x customer_id=xyzCorp -x codeword=123456789101bcdf \ -s /cdrom B8843CA @ /tmp/wlm_depot

13. Verify the depot:

    # swverify -d \* @ depot_path

    where depot_path is a fully specified pathname. For example:

    # swverify -d \* @ /tmp/wlm_depot

Disable PRM from starting automatically

If you have previously installed WLM or PRM, ensure that PRM is disabled from starting automatically by setting the variable PRM_CONFIG to 0 in the file /etc/rc.config.d/prm:

PRM_CONFIG=0

(Optional) Disable PRM’s remote configuration daemon

The PRM remote configuration daemon is not useful with WLM. It need not be started. It is recommended that it be disabled.

If you have previously installed WLM or PRM, ensure that PRM’s remote configuration daemon is disabled from starting automatically by setting the variable PRM_RMTCONF to 0 in the file /etc/rc.config.d/prm:

PRM_RMTCONF=0

Shut down WLM if it is currently running

Run the following command on every system or partition where you will install/upgrade WLM:

# /opt/wlm/bin/wlmd -k

Also shut down any running instances of the WLM global arbiter:

# /opt/wlm/bin/wlmpard -k

Install patches and install/upgrade WLM

	NOTE: The procedure below explains installation using the command-line version of swinstall. For information on using the swinstall GUI, refer to the section “Using the swinstall Graphical User Interface (GUI)”.

WLM is bundled as B8843CA, which contains the products Workload-Mgr, WLM-Monitor, and WLM-Dev tools. If desired, you can use swlist to list the product’s filesets:

# swlist -l fileset -s depot_path B8843CA

Installing WLM ensures that the following product is also installed:

If the system already has the correct version installed, it will not be modified.

The WLM product B8843CA replaces the WLM product B8843BA from WLM Version 1.0. If you install using swinstall’s match_target option, the new B8843CA product will match your installed B8843BA product.

Workload Manager is installed in /opt/wlm/. The manpages are also installed in /opt/wlm/.

1. Plan for system downtime. This should include generation of a current system backup and notification to all users.

2. Shut down MeasureWare if it is running:

   # /usr/sbin/init.d/mwa stop

3. Install WLM

   There are two methods for installing WLM. You can:

   • Install WLM from the depot you created in Step 5

   • Install WLM directly from the CD-ROM

   These options are discussed below.

   Installing WLM from a depot

   If you are installing WLM from your local depot, use swinstall as follows:

   # /usr/sbin/swinstall -x patch_match_target=true \ -x autoreboot=true \ -s depot_path \ B8843CA [patch_bundles] [individual_patches]

   where depot_path is the fully specified path of the depot just created. For example:

   # swinstall -x patch_match_target=true \ -x autoreboot=true \ -s /tmp/wlm_depot \ B8843CA GOLDAPPS11i GOLDBASE11i PHKL_32619

   SD-UX will attempt to build a new kernel and reboot the system.

   	NOTE: Starting with WLM A.03.01, WLM no longer requires a reboot. The autoreboot option need no longer be set to true to satisfy requirements of the HP PRM kernel-building fileset PRM-Sw-Krn.PRM-KRN. Consequently, the SD-UX Interactive User Interface no longer prompts for an OK to reboot.

   Installing from the CD-ROM

   	NOTE: Installing without the benefit of a depot may cause unnecessary reboots. For information on reducing reboots, see Step 5 on creating a software depot.

   If you are installing WLM from the CD-ROM:

   1. Install the general support patch bundles and software from Step 1

      If your system is missing any general HP-UX patch bundles or software mentioned in Step 1, install them now.

      Be sure to read the patch bundle documentation for any special installation instructions.

   2. Install WLM

      	NOTE: The WLM bundle B8843CA requires a customer_id/codeword pair to unlock it from the AR CD-ROM. Purchase of WLM entitles you to this codeword, which can be found on the Software Certificate you received from HP. The WLM codeword is needed to complete the next step.

      Use a line similar to the following to install WLM:

      # /usr/sbin/swinstall -x customer_id=cust_id \ -x codeword=codeword \ -x autoreboot=true \ -s mount_path B8843CA

      where mount_path is the path to the CD-ROM. For example:

      # swinstall -x customer_id=xyzCorp \ -x codeword=123456789101bcdf \ -x autoreboot=true \ -s /cdrom B8843CA

   3. Install WLM-specific patches from Step 4

      If your system is missing patches from Step 4, install them now.

      Be sure to read the patch documentation for any special installation instructions.

4. Restart MeasureWare if it was running before the WLM upgrade/installation:

   # /usr/sbin/init.d/mwa start

Check the file /var/adm/sw/swagent.log

Check the file /var/adm/sw/swagent.log for messages relating to additional tasks that may need attention following the swinstall of WLM bundle B8843CA.

(Optional) Ensure you have the proper version of GlancePlus

If you plan to use WLM data collectors that are based on Glance Adviser (such as glance_app or glance_tt), be sure to install and use GlancePlus C.03.35.00 or later to avoid a memory leak that occurs when Glance Adviser runs continuously. If you are using HP-UX 11i v1, install GlancePlus when installing the 11i Enterprise or 11i Mission-critical Operating Environments. If you are using processor sets, install GlancePlus C.03.58.05 or later.

(Optional) Install files for integration with HP Systems Insight Manager

If you plan to use WLM with HP Systems Insight Manager (or Servicecontrol Manager), install the fileset CMSConfig.WLMB-CMS-Tools on the CMS. This fileset is available from the depot /var/opt/mx/depot11 on the host where WLM has been installed.

If you are installing this fileset on a CMS that has WLM installed, the installation will fail if the fileset is not compatible with (does not have the same revision string as) the installed WLM.

(Optional) Merge new /etc/rc.config.d/wlm file with your modified file

If you have made any modifications to your /etc/rc.config.d/wlm file by setting any of the variables ending in “_ENABLE” to 1, merge the file /opt/wlm/newconfig/etc/rc.config.d/wlm with your /etc/rc.config.d/wlm file.

As of WLM A.02.02, the /opt/wlm/newconfig/etc/rc.config.d/wlm file includes the variables WLMCOMD and WLMCOMD_ENABLE.