Install OVO Monitoring – WFM 5.3 (AM Region Only)

Version B.05.08.191
051917a


These installation instructions cover the deployment and configuration of OVO support for the following in AM region ONLY.

AM Region Only                (BLT required)

Upload the SDI Model Template

   Get the Requisite Files

   Install the Software &Template Files
Configure Server Connections and Graphs
Modify WLSSPI Configuration
Verify the WLSSPI Configuration

IG Notes:

 

 1–Upload the SDI Model Template (AM Region Only)

1a–Get the Requisite Files

Open a BLT to the OVO team in the AM region to perform the following tasks.

  1.  Log on to the OVO management server as root (administrator).

  2.  Log on to the OVO console (opc) as opc_adm (administrator).

  3.  Change to the /tmp directory.

      cd /tmp
  4.  SFTP the SDI template files from the EIA FTP server.

      sftp eia@tsb.rose.hp.com
      Password: <correct_password>
      
      sftp> cd eia/EIA0508/WFM53/OVO 
      sftp> get ovo93_atl_wfm53_081805.tar 
      sftp> get SiteConfig_AM_WFM53
      sftp> quit
  5.  Unpack the ovo93_atl_wfm53_081805.tar file.
      tar xvf ovo93_atl_wfm53_081805.tar
    
    Sample output:
    
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/actions/restart_GSO_EM_JTEM.Z
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/actions/restart_SonicMQ_GSO_EM_Inbound_MONITOR.Z
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/cmds/
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/cmds/ovo81_ito_mwflu2.doc
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/monitor/
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/monitor/JTEM_SonicMQ_SWAT_MONITOR.Z
      x ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/monitor/SonicMQ_GSO_EM_Inbound_MONITOR.Z
  6.  Review the Word document listing all the executables included in this release before you upload the current build.

      /tmp/ovo93_atl_wfm53_081805/C/EXECUTABLES/hp/pa-risc/hp-ux11/cmds/ovo93_atl_wfm53_081805_bld.doc
    

1b–Install the Software & Template Files

  1.  Install the software and load the AM region template files.

      /opt/OV/bin/OpC/opccfgupld -replace -subentity -verbose /tmp/ovo93_atl_wfm53_081805
  2.  Add, if necessary, and validate that these template groups are assigned to the following systems:

    Template Group

    EIA_3_0

    WebLogic SPI Template Group

    EIS206-WLS-7.0-Metrics
    EIS206-WLSSPI-Logfiles

    Application Server Assignments

    hpat615.atl.hp.com

    hpat616.atl.hp.com hpat706.atl.hp.com
  3.  Distribute the actions, commands, templates and monitors to the EIA nodes.

      opcragt <sys1> <sys2> -distrib -force
  4.  Remove the ovo93_atl_wfm53_081805.tar file.

      rm ovo93_atl_wfm53_081805.tar
  5.  Repeat all steps in this section for each remaining AM regional application server.

  6.  Backup the current /opt/OV/wasspi/wls/conf/SiteConfig file for the AM region on the OVO management server.

  7. Note: Append today's date in yy_mm_dd format at the end of the backup file as shown.

      mv /opt/OV/wasspi/wls/conf/SiteConfig /opt/EIA_Apps/ITO/SiteConfig_<hostname>.<yy_mm_dd>
    
    Example:
    
      mv /opt/OV/wasspi/wls/conf/SiteConfig /opt/EIA_Apps/ITO/SiteConfig_i3107ei3.05_05_18
    
    
  2–Configure Server Connections and Graphs

Overview—Along with each set of templates, the EIA Monitoring team now provides an updated project SiteConfig file for streamlined SPI deployment. The new process involves first backing up all existing SPI configuration data, then removing this data from within the Edit WebLogic SPI Configuration dialog box. The contents of the new SiteConfig file (provided by the EIA Monitoring team) are now read into into memory and pasted into the Edit WebLogic SPI Configuration dialog box.

2a–Process the SiteConfig File

  1.  Verify that the backup SiteConfig_<hostname>.<yy.mm.dd> file exists in the /opt/EIA_Apps/ITO/ directory.

      ls -al /opt/EIA_Apps/ITO/SiteConfig_<hostname>.<yy.mm.dd>
    
    Example:
    
      ls -al /opt/EIA_Apps/ITO/SiteConfig_i3107ei3.05_05_18
  2.  Copy the new AM-region SiteConfig file to the /opt/OV/wasspi/wls/conf/ directory.

      cp /tmp/SiteConfig_AM_WFM53 /opt/OV/wasspi/wls/conf/SiteConfig
    
  3–Modify Server Configuration

3a–Process the WLSSPI SiteConfig file

  1.  Open the ITO Application Bank window from the Window menu.

  2.  Double-click the WLSSPI icon to display the Application Group: WLSSPI window.

  3.  Double-click the WLSSPI Admin icon to display the Application Group: WLSSPI Admin window.

    Note: This window contains programs to check your WLSSPI installation.

  4.  Select the Node Group Bank item from the Window menu.

  5.  Double-click the EIA node group icon to display its Node Group: EIA window, positioning this window adjacent to the Application Group: WLSSPI Admin window.

  6.  Select the icon representing the WLS server to be configured.

  7.  Drag and drop the WLS server icon onto the Config WLSSPI icon in the Application Group: WLSSPI Admin window.

    Note: The Edit WebLogic SPI Configuration dialog box should now appear. Leave this dialog box open throughout the remaining steps of this installation, as you'll be working in it during several sections.

3b–Current SiteConfig data

  1. WLSSPI Information—AM Region

    Primary admin server:       i3107ei3.atl.hp.com
    Secondary admin server:   i3107ei4.atl.hp.com
    Admin server log directory:  /opt/sasuapps/wfmsvc/domain/atconnct_RIBS_40/atconnct_RIBS_40.log

    Regional AdminServer managed server names:                                                                                        Port:

    AdminServer                                                                                                                                                     31600

    New WFM managed server names:

       WASYNC_pri_hpat615_01
       WES_pri_hpat615_01

       WES_pri_hpat615_02

       WES_pri_hpat615_03

       WES_pri_hpat615_04
       WAM_pri_hpat615_01
       MWFL_pri_hpat615_01

       GCM_pri_hpat615_01
     

       WASYNC_sec_hpat616_01
       WES_sec_hpat616_01

       WES_sec_hpat616_02

       WES_sec_hpat616_03

       WES_sec_hpat616_04
       WAM_sec_hpat616_01
       MWFL_sec_hpat616_01

       GCM_sec_hpat616_01

     

       WASYNC_ter_hpat705_01
       WES_ter_hpat705_01

       WES_ter_hpat705_02

       WES_ter_hpat705_03

       WES_ter_hpat705_04
       WAM_ter_hpat705_01
       MWFL_ter_hpat705_01

       GCM_ter_hpat705_01

     

    Port #

     

    32100 
    32300

    32302

    32304

    32306
    32000
    31900

    31800


    32100 
    32300

    32302

    32304

    32306
    32000
    31900

    31800
     

    32100 
    32300

    32302

    32304

    32306
    32000
    31900

    31800

    New managed server log directories on hpat615:

    /opt/sasuapps/wfmsvc/instances/links/WASYNC/atconnct_RIBS_40/WASYNC_pri_hpat615_01/WASYNC_pri_hpat615_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_pri_hpat615_01/WES_pri_hpat615_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_pri_hpat615_02/WES_pri_hpat615_02.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_pri_hpat615_03/WES_pri_hpat615_03.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_pri_hpat615_04/WES_pri_hpat615_04.log

    /opt/sasuapps/wfmsvc/instances/links/WAM/atconnct_RIBS_40/WAM_pri_hpat615_01/WAM_pri_hpat615_01.log
    /opt/sasuapps/wfmsvc/instances/links/MWFL/atconnct_RIBS_40/MWFL_pri_hpat615_01/MWFL_pri_hpat615_01.log

    /opt/sasuapps/wfmsvc/instances/links/GCM/atconnct_RIBS_40/GCM_pri_hpat615_01/GCM_pri_hpat615_01.log
     

    New managed server log directories on hpat616:

    /opt/sasuapps/wfmsvc/instances/links/WASYNC/atconnct_RIBS_40/WASYNC_sec_hpat616_01/WASYNC_sec_hpat616_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_sec_hpat616_01/WES_sec_hpat616_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_sec_hpat616_02/WES_sec_hpat616_02.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_sec_hpat616_03/WES_sec_hpat616_03.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_sec_hpat616_04/WES_sec_hpat616_04.log

    /opt/sasuapps/wfmsvc/instances/links/WAM/atconnct_RIBS_40/WAM_sec_hpat616_01/WAM_sec_hpat616_01.log
    /opt/sasuapps/wfmsvc/instances/links/MWFL/atconnct_RIBS_40/MWFL_sec_hpat616_01/MWFL_sec_hpat616_01.log

    /opt/sasuapps/wfmsvc/instances/links/GCM/atconnct_RIBS_40/GCM_sec_hpat616_01/GCM_sec_hpat616_01.log

    New managed server log directories on hpat705:

    /opt/sasuapps/wfmsvc/instances/links/WASYNC/atconnct_RIBS_40/WASYNC_ter_hpat705_01/WASYNC_ter_hpat705_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_ter_hpat705_01/WES_ter_hpat705_01.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_ter_hpat705_02/WES_ter_hpat705_02.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_ter_hpat705_03/WES_ter_hpat705_03.log

    /opt/sasuapps/wfmsvc/instances/links/WES/atconnct_RIBS_40/WES_ter_hpat705_04/WES_ter_hpat705_04.log

    /opt/sasuapps/wfmsvc/instances/links/WAM/atconnct_RIBS_40/WAM_ter_hpat705_01/WAM_ter_hpat705_01.log
    /opt/sasuapps/wfmsvc/instances/links/MWFL/atconnct_RIBS_40/MWFL_ter_hpat705_01/MWFL_ter_hpat705_01.log

    /opt/sasuapps/wfmsvc/instances/links/GCM/atconnct_RIBS_40/GCM_ter_hpat705_01/GCM_ter_hpat705_01.log

    Save your changes and exit the editor.

    Expected output (appearing in the Edit WebLogic SPI Configuration window):
    
      Set configuration for <node>? yes
      Transferring configuration to <node>
      Importing configuration on <node>

    Verify that the new SPI configuration contains all of the data included in the table above.

  2. Press [Enter] to complete the server configuration.
     

  4–Verify the WLSSPI Configuration (AM Region Only)
  1.  Open the Application Bank window from the Window menu.

  2.  Double-click the WLSSPI icon to display the Application Group: WLSSPI window.

  3.  Double-click the WLSSPI Admin icon to open the Application Group: WLSSPI Admin window.

  4.  Select the Node Group Bank item from the Window menu. 

  5.  Double-click the EIA node group icon to display its Node Group: EIA window, positioning this window adjacent to the Application Group: WLSSPI Admin window.

  6.  Drag and drop the recently-configured managed node from the Node Group: EIA window onto the Verify icon in the Application Group: WLSSPI Admin window. 

       Expected output (appearing in the Output of Application No. x window):
    
          /var/opt/OV/bin/OpC/monitor/wasspi_wls_le (U.02.04.01) should be A.02.04.00
          		..
          		..
          		..
          		..
          ----------------End /var/opt/OV/wasspi/wls/conf/SiteConfig ----------------
    
          1 problem was detected

    Note: This message is benign and may be ignored.

  7.  Click Close.

  8.  Click the up arrow icon (é) on the toolbar.

  9.  Double-click the WebLogic icon.

  10.  Drag and drop the recently-configured managed node from the Node Group: EIA window onto the Check WebLogic icon in the Application Group: WebLogic window.

       Sample output (appearing in the Output of Application No. x window):
    
                                  .
                                  .
                                  .
       GCM_pri_hpat615_01
    
       WebLogic Status report
    
       Status of WebLogic for server GCM_pri_hpat615_01
       ========================================================
       Server Name               : GCM_pri_hpat615_01
       Server State              : RUNNING
       Start date                : Thu Jan 30 16:49:51 2003
       Port                      : 31800.0
       Admin Server Host         : 15.21.126.15
       Admin Server Port         : 31600.0
       Current Open Socket Count : 2.0
       WebLogic Version          : WebLogic Server 8.1 SPI Mon Sep 9 22 
       GCM_sec_hpat616_01
    
       WebLogic Status report
    
       Status of WebLogic for server GCM_sec_hpat616_01
       ========================================================
       Server Name               : GCM_sec_hpat616_01
       Server State              : RUNNING
       Start date                : Thu Jan 30 16:49:51 2003
       Port                      : 31800.0
       Admin Server Host         : 15.21.126.15
       Admin Server Port         : 31600.0
       Current Open Socket Count : 2.0
       WebLogic Version          : WebLogic Server 8.1 SPI Mon Sep 9 22 
       GCM_ter_hpat705_01
    
       WebLogic Status report
    
       Status of WebLogic for server GCM_ter_hpat705_01
       ========================================================
       Server Name               : GCM_ter_hpat705_01
       Server State              : RUNNING
       Start date                : Thu Jan 30 16:49:51 2003
       Port                      : 31800.0
       Admin Server Host         : 15.21.126.15
       Admin Server Port         : 31600.0
       Current Open Socket Count : 2.0
       WebLogic Version          : WebLogic Server 8.1 SPI Mon Sep 9 22