WFM 5.2 System Preparation

Version B.05.05.251
050598

This set of instructions covers the transition of WFM operation from WFM 5.1.8 to WFM 5.2.

In order to upgrade the various WFM applications at different times from versions 5.1.8 to 5.2, this installation guide (IG) is designed to be executed on an individual basis for each WFM application. The exceptions to this are the WAM and WASYNC (formerly WESASYNC) applications, which must always be deactivated/activated together.

WFM 5.2 Application Corresponding Apache IG
GCM Apache Update for WFM5.2 GCM Instance
MWFL Apache Update for WFM5.2 MWFL Instance
WES Apache Update for WFM5.2 WFMMAIN Instance
WASYNC
WAM

IG execution should be followed by the corresponding sections (3, 4 and 5) in the WFM 5.2/Apache IG set so that the Apache layer is also transitioned from 5.1.8 to 5.2.

Prerequisites:

Notes:

  1. For WFM version 5.1.8, one application was named WESASYNC. For WFM 5.2 this name has been shortened to WASYNC.

  2. Use the following table as a guide when performing the individual WFM 5.2 application installation.
Application Node
Manager		 Managed Server(s) User Applicable Regions
GCM n/a GCM gcm AM (hpat615, hpat616 only)
MWFL n/a MWFL mwfl all
WES weshipri WES weshipri all
WAM/WASYNC weslopri WAM/WASYNC weslopri all

Stop the Version 5.1.8 Managed Server
Stop the 5.1.8 weslopri and weshipri Node Managers
Modify $PATH in .PROFILE Files
Stop the Version 5.2 Managed Server
Stop the 5.2 weslopri and weshipri Node Managers
Application Server Preparation                                           (BLT required)
Restart the weshipri and weslopri Node Managers

IG Notes:

 1–Stop the Version 5.1.8 Managed Server

Managed Servers
WES GCM
WAM & WESASYNC MWFL

  1.  Start the admin console in a Web browser.

      http://wlsgprd1.atl.hp.com:22900/console

  2.  Enter your username and password.

  3.  Expand the Servers branch in the left pane.

  4.  Right-click the WFM 5.1.8 <managed_server> entry (-ies) corresponding to the WFM application you are presently upgrading.

    Examples:

  WES_5_1_8_AM_hpat616_weshipri_3 

  WESASYNC_5_1_8_EU_eelink05_weslopri 

  MWFL_5_1_8_AP_sgpux281_mwfl
  5.  Select Start/stop this server from the context-sensitive menu.
      Start/stop this server

  6.  Click the Shutdown this server link in the right pane.

  7.  Click Yes when prompted, "Are you sure you want to shutdown <managed_server>".

    Note: The managed server has been shut down when the Status field changes to TASK COMPLETED.

  8.  Referring to the table above, repeat the previous steps for each remaining <managed_server> entries.

  9. <hostname>
    Values

    <domain>
    Values
    hpat615 hpat616 hpat705 atl
    eelink05 eelink06 eelink04 sdc
    sgpux138 sgpux139 sgpux281 sgp

    For the WES managed server only—Repeat the following steps a through c for each application server per region.

    1.  Log in to the <hostname>.<domain>.hp.com application server as user weshipri.

      Example:

  hpat615.atl.hp.com

    2.  Grep for the WES windu process ID (PID).

        ps –ef | grep weshipri | grep windu

    3.  Kill the WES windu process. 

        kill -9 <windu_PID>

  10. For the WASYNC managed server only—

    11. Repeat the following steps a through c for each application server per region.

    1.  Log in to the <hostname>.<domain>.hp.com application server as user weslopri.

      Example:

  hpat615.atl.hp.com

    2.  Grep for the WASYNC windu process ID (PID).

        ps –ef | grep weslopri | grep windu

    3.  Kill the WASYNC windu process. 

        kill -9 <windu_PID>

 2–Stop the 5.1.8 weslopri and weshipri Node Managers

Note: This section pertains only to the following three WFM applications: WES, WAM, WESASYNC. Skip to section 3 if you are presently using this installation guide to upgrade GCM or MWFL.

Perform the following steps for both the weshipri and weslopri Node Managers on all application servers in all regions.

Applicable Application NodeManager <nodemanager directory> <listen_port> <nodemanager user>
WES weshipri nodemanager-weshipri 5558 weshipri
WAM/WESASYNC weslopri nodemanager-weslopri 5559 weslopri

  1.  Log in to the <hostname>.<domain>.hp.com application server as user <nodemanager user>.

    Example:
      hpat615.atl.hp.com as weshipri

  2.  Run hostname to verify you are logged on to the application server before continuing.

      hostname

Expected output:

  <hostname>

Example (AM region):

   hpat615, hpat616 or hpat705

  3.  Change to the /opt/bea/weblogic700/common/<nodemanager-directory> directory.

      cd /opt/bea/weblogic700/common/<nodemanager-directory>

Example:

  cd /opt/bea/weblogic700/common/nodemanager-weshipri

  4.  Execute the stopNodeManager script.

      ./stopNodeManager.sh

  5.  Verify NodeManager is not running.

      lsof -i :<listen_port>

Example:

  lsof -i :5558

(The sample output should be null.)

  6.  Repeat all of the steps in this section for the remaining regional application servers.
     

 3–Modify $PATH in .PROFILE Files

Note: This section pertains only to the following three WFM applications: WES, WAM, WESASYNC (WASYNC). Skip to section 3 if you are presently using this installation guide to upgrade GCM or MWFL.

Perform the following steps for both the weshipri and weslopri users on all application servers in all regions.

  1.  Log in to the <hostname>.<domain>.hp.com application server as user <user>.

    Example:
      hpat615.atl.hp.com as weshipri

  2.  Run hostname to verify you are logged on to the application server before continuing.

      hostname

Expected output:

  <hostname>

Example (AM region):

   hpat615, hpat616 or hpat705

  3.  Change to the /home/<user_directory> directory.

      cd /home/<user_directory>

Example:

  cd /home/weshipri

  4.  Create a backup the of the .profile file.

    Note: Append today's date in yy.mm.dd format at the end of the backup file as shown.

      cp .profile .profile.<yy.mm.dd>

  5.  Open the .profile file for editing.

      vi .profile

  6.  Locate the $PATH entry.

      # Set up the search paths:
  PATH=$PATH:.:/opt/bea/install/scripts:/opt/bea/jdk131_09/bin

  7.  Modify the $PATH entry to read as follows (note modifications delineated in boldface).

      # Set up the search paths:
  PATH=$PATH:.:/opt/weblogic/install/scripts:/opt/weblogic/jdk142_03/bin

  8.  Save the changes and exit the editor.

  9.  Source in the updated .profile file in order to affect the changes.

      . ~/.profile

 4–Stop the Version 5.2 Managed Server

  1. Region <domain>
    AM atl
    EU sdc
    AP sgp

     Start the admin console in a Web browser.

      http://wlsgprd1.<domain>.hp.com:31600/console

Example:

  http://wlsgprd1.atl.hp.com:31600/console

  2.  Enter your username and password.

  3.  Expand the Servers branch in the left pane.

  4. Managed Servers
    WES GCM
    WAM & WASYNC MWFL

     Right-click the WFM 5.2 <managed_server> entry (-ies) corresponding to the WFM application you are presently upgrading.

    Examples:

  WES_pri_hpat615_03 

  WASYNC_sec_eelink06_01
  5.  Select Start/stop this server from the context-sensitive menu.
      Start/stop this server

  6.  Click the Shutdown this server link in the right pane.

  7.  Click Yes when prompted, "Are you sure you want to shutdown <managed_server>".

    Note: The managed server has been shut down when the Status field changes to TASK COMPLETED.

  8.  Referring to the table above, repeat the previous steps for each remaining <managed_server> entries.

  9.  Leave the admin console running.

  10. <hostname>
    Values

    <domain>
    Values
    hpat615 hpat616 hpat705 atl
    eelink05 eelink06 eelink04 sdc
    sgpux138 sgpux139 sgpux281 sgp

    For the WES managed server only—

    11. Repeat the following steps a through c for each application server per region.

    1.  Log in to the <hostname>.<domain>.hp.com application server as user weshipri.

      Example:

  hpat615.atl.hp.com

    2.  Grep for the WES windu process ID (PID).

        ps –ef | grep weshipri | grep windu

    3.  Kill the WES windu process. 

        kill -9 <windu_PID>

  11. For the WASYNC managed server only—

    12. Repeat the following steps a through c for each application server per region.

    1.  Log in to the <hostname>.<domain>.hp.com application server as user weslopri.

      Example:

  hpat615.atl.hp.com

    2.  Grep for the WASYNC windu process ID (PID).

        ps –ef | grep weslopri | grep windu

    3.  Kill the WASYNC windu process. 

        kill -9 <windu_PID>

 5–Stop the 5.2 weslopri and weshipri Node Managers

Note: This section pertains only to the following three WFM applications: WES, WAM and WASYNC. Skip to section 4 if you are presently using this installation guide to upgrade GCM or MWFL.

Perform the following steps for both the weshipri and weslopri Node Managers on all application servers in all regions.
Applicable Application NodeManager <nodemanager directory> <listen_port> <nodemanager user>
WES weshipri nodemanager-weshipri 5551 weshipri
WAM/WASYNC weslopri nodemanager-weslopri 5552 weslopri

  1.  Log in to the <hostname>.<domain>.hp.com application server as user <nodemanager user>.

    Example:
      hpat615.atl.hp.com as weshipri

  2.  Run hostname to verify you are logged on to the application server before continuing.

      hostname

Expected output:

  <hostname>

Example (AM region):

   hpat615, hpat616 or hpat705

  3.  Change to the /opt/weblogic/weblogic81/common/<nodemanager_directory> directory.

      cd /opt/weblogic/weblogic81/common/<nodemanager_directory>

Example:

  cd /opt/weblogic/weblogic81/common/nodemanager-weshipri

  4.  Execute the stopNodeManager script.

      ./stopNodeManager.sh

  5.  Verify NodeManager is not running.

      lsof -i :<listen_port>

Example:

  lsof -i :5551

(The sample output should be null.)

  6.  Repeat all of the steps in this section for the remaining regional application servers.
     

 6–Application Server Preparation

Open a BLT on each regional application server to perform the following steps.

Note: The GCM application applies only to hpat615 and hpat616 in the AM region.
Region

Application Servers

AM hpat615.atl.hp.com hpat616.atl.hp.com hpat705.atl.hp.com
EU eelink05.sdc.hp.com eelink06.sdc.hp.com eelink04.sdc.hp.com
AP sgpux138.sgp.hp.com sgpux139.sgp.hp.com sgpux281.sgp.hp.com
FAT rpfat1.rose.hp.com i3107ei6.atl.hp.com i3107ei5.atl.hp.com
Region WFM Application user
AM GCM gcm
all WES weshipri
all WAM & WASYNC weslopri
all MWFL mwfl

  1.  Log in to the <hostname>.<domain>.hp.com application server as user root.

    Example:
      hpat615.atl.hp.com

  2. Based on the individual WFM application for which you are presently upgrading from versions 5.18 to 5.2, request the following group changes for the corresponding <user> on each of the regional application servers: weshipri, weslopri, mwfl or gcm (the latter being for hpat615 and hpat616 in the AM-region only).

    1.  Change the primary group of <user> from eia to eia8.

    2.  Change the secondary group of <user> from eia8 to eia.

 7–Start the weshipri and weslopri Node Managers

Note: This section pertains only to the following three WFM applications: WES, WAM, WASYNC. Skip to section 6 if you are presently using this installation guide to upgrade GCM or MWFL.

Perform the following steps for both the weshipri and weslopri NodeManagers on all application servers in all regions. 
Applicable Application NodeManager <nodemanager directory> <listen_port> <nodemanager user>
WES weshipri nodemanager-weshipri 5551 weshipri
WAM/WASYNC weslopri nodemanager-weslopri 5552 weslopri

  1.  Log in to the <hostname>.<domain>.hp.com application server as user <nodemanager user>. 

    Example:
      hpat615.atl.hp.com as weshipri

  2.  Run hostname to verify you are logged on to the application server before continuing.

      hostname

Expected output:

  <hostname>

Example (AM region):

   hpat615, hpat616 or hpat705

  3.  Change to the /opt/weblogic/weblogic81/common/<nodemanager_directory> directory.

      cd /opt/weblogic/weblogic81/common/<nodemanager_directory>

Example:

  cd /opt/weblogic/weblogic81/common/nodemanager-weshipri

  4.  Execute the startNodeManager script.

      ./startNodeManager.sh

  5.  Verify NodeManager is running.

      lsof -i :<listen_port>

Example:

  lsof -i :5551

Sample output (the PID and device numbers will vary):

  COMMAND PID    USER   FD  TYPE  DEVICE SIZE/OFF NODE NAME

    java  8786 weshipri 26u inet 0x8757e040 0t0 T  CP  hpat615.atl.hp.com:5550 (LISTEN)

  6.  Repeat all of the steps in this section for the remaining regional application servers.

 8–Start the WES, WAM/WASYNC, GCM or MWFL Managed Servers

Managed Servers
WES GCM
WAM MWFL
WASYNC

  1.  Switch to the admin console running in the browser window.

  2.  Expand the Servers branch in the left pane.

  3.  Right-click the WFM 5.2 <managed_server> entry (-ies) corresponding to the application you are presently upgrading.

    Examples:

  WES_pri_hpat615_01 

  WASYNC_sec_eelink06_01 

  MWFL_ter_sgpux281_01
  4.  Select Start/stop this server from the context-sensitive menu.
      Start/stop this server

  5.  Click the Start this server link in the right pane.

  6.  Click Yes when prompted, "Are you sure you want to start <managed_server>".

    Note: The managed server has been started when the Status field changes to RUNNING.

  7.  Referring to the table above, repeat the previous steps for each remaining <managed_server> entries.