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)
Install the Software &Template Files |
IG Notes:
If printing, print in landscape mode only.
1–Upload the SDI Model Template (AM Region Only) |
Open a BLT to the OVO team in the AM region to perform the following tasks.
Log on to the OVO management server as root (administrator).
Log on to the OVO console (opc) as opc_adm (administrator).
Change to the /tmp directory.
cd /tmp
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
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
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
Install the software and load the AM region template files.
/opt/OV/bin/OpC/opccfgupld -replace -subentity -verbose /tmp/ovo93_atl_wfm53_081805
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 |
||
Application Server Assignments |
||
hpat615.atl.hp.com |
hpat616.atl.hp.com | hpat706.atl.hp.com |
Distribute the actions, commands, templates and monitors to the EIA nodes.
opcragt <sys1> <sys2> -distrib -force
Remove the ovo93_atl_wfm53_081805.tar file.
rm ovo93_atl_wfm53_081805.tar
Repeat all steps in this section for each remaining AM regional application server.
Backup the current /opt/OV/wasspi/wls/conf/SiteConfig file for the AM region on the OVO management server.
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
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
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
Open the ITO Application Bank window from the Window menu.
Double-click the WLSSPI icon to display the Application Group: WLSSPI window.
Double-click the WLSSPI Admin icon to display the Application Group: WLSSPI Admin window.
Note: This window contains programs to check your WLSSPI installation.
Select the Node Group Bank item from the Window menu.
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.
Select the icon representing the WLS server to be configured.
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.
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 |
||||||
|
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.
Press [Enter] to complete the
server configuration.
4–Verify the WLSSPI Configuration (AM Region Only) |
Open the Application Bank window from the Window menu.
Double-click the WLSSPI icon to display the Application Group: WLSSPI window.
Double-click the WLSSPI Admin icon to open the Application Group: WLSSPI Admin window.
Select the Node Group Bank item from the Window menu.
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.
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.
Click Close.
Click the up arrow icon (é) on the toolbar.
Double-click the WebLogic icon.
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