HP Management Platform Synchronization Installation and Reference Manual Revision History Table 1 Revisions Date Edition Revision August 2008 B.05.07 First Release January 2009 A.05.20 Second Release July 2009 A.05.30 HP Insight Remote Support Advanced A.05.30 September 2009 A.05.40 HP Insight Remote Support Advanced A.05.40 November 2009 A.05.40 EAPv3 SAP Solution Manager integration June 2010 A.05.50 HP Insight Remote Support Advanced A.05.50 July 2012 A.05.
Legal notices Provided by: HEWLETT-PACKARD COMPANY 3404 E. Harmony Road Fort Collins, CO 80528 U.S.A. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents Contents Revision History ................................................................................................................................................... 1 Conventions ......................................................................................................................................................... 5 Frequently Used Acronyms ..................................................................................................................................
Contents 5 SAP SolMan integration 5-1 Prerequisites ................................................................................................................................................ 48 5-1-1 Features and Benefits ......................................................................................................................... 48 5-2 Installing the SolMan integration ..................................................................................................................
Appendix A Conventions The typeface conventions used within this document are as follows: Body Text: Arial 10 pt is used as the main body text in this document. FileName : Courier 10 pt indicates document names and file extensions. ComputerOutput: Courier New 10 pt indicates text output from a computer, text, or user interface. [Hard Button]: Arial Bold 10 pt indicates the use of a keyboard button. UserInput: Courier New 10 pt indicates text the user must enter into the system.
Introduction to MPS 1 Introduction to MPS NOTE: Throughout this document the terms HP OpenView Operations Manager and HP Operations Manager (OM) are used interchangeably. The Management Platform Synchronizer (MPS) synchronizes incidents between the Central Management Server (CMS) and OpenView Operations (OVO). This allows the OpenView management platform to integrate with the remote support technology of HP Insight Remote Support Advanced.
Introduction to MPS 1-1 Intended Audience This manual is written for different level of expertise and knowledge about Remote Support. Some parts of the manual contain very detailed information usually needed only by the HP Insight Remote Support Advanced Support Group. However following the step by step instructions should allow all users to successfully install and maintain the MPS.
Introduction to MPS 1-2 Document Structure This manual is divided into the following chapters and appendices: Chapter 1: Introduction to MPS — provides an introduction to MPS that includes a high-level description of MPS architecture, components, and data flows. Chapter 2: MPS Installation Prerequisites— describes the hardware and software requirements for the MPS environment.
Introduction to MPS 1-3 MPS Overview MPS is part of the Multivendor and Application Adapter (MVAA) component of HP Insight Remote Support Advanced. Insight Remote Support Advanced is a plug-in for the HP Systems Insight Manager (HP SIM) management platform and is hosted on the customer-managed and customerowned Central Management Server (CMS).
Introduction to MPS Seen more simply, MPS provides a bridge between the customers IT processes, supported by OVO, and the HP service process which uses Insight Remote Support Advanced.
Introduction to MPS 1-3-1 Viewing and Updating Incidents in OVO MPS is able to send every incident, which is reported to HP Insight Remote Support Advanced, to the customer’s OVO system. This includes all types of devices, which report their incidents directly to Insight Remote Support Advanced, including all HP servers and certain multi-vendor server types, many network devices, storage and Storage Area Network (SAN) devices and others.
Introduction to MPS Figure 1-4 Event Collection Flow RSP Incident Event Handler HW diag OVO Mgmt Station CMS MPS HP Service Process 1-3-1-1 Sending Incident Information to OVO NOTE: The Remote Support Client located on the CMS provides the communication service which is used to synchronize HP SIM with the HP backend. The Remote Support Client will call MPS each time an incident is created or updated in its database. This database is also automatically synchronized with the HP support center.
Introduction to MPS 1-3-1-2 Processing Incidents in OVO The OVO adapter will perform the following actions through the web interface on message updates: 1. The original message is processed and the message text, appendix, and custom message attributes (such as Case IDs) are updated to the new status. 2. When the original message text needs to be overwritten the text is kept as an annotation. The annotations contain the history of message text changes.
MPS Installation Prerequisites 2 MPS Installation Prerequisites This chapter describes the hardware and software requirements for MPS. The customer should already have a CMS with the HP Insight Remote Support Advanced A.05.40 (or higher) installed. Open Service Event Manager (OSEM) Version v1.4.7 or later or Web-Based Enterprise Services (WEBES) v5.5 or later should be installed on the CMS, as MPS uses their entitlement technology.
Installing and Configuring MPS 3 Installing and Configuring MPS This chapter describes the procedures for installing, configuring and verifying installation of the MPS software on the CMS. A summary of the installation process for MPS can be described in two steps 1. Install the Multivendor and Application Adapter (MVAA) with the Remote Support Software Manager (RSSWM) on the CMS (Refer to section 3-1 ) 2.
Installing and Configuring MPS Figure 3-2 Installing the Multivendor and Application Adapter (MVAA) package in RSSWM 6. After the installer completes installation the package should show as installed. Figure 3-3 MPS Installed 3-2 Configuring MPS In a supported web browser 1. Open the URL https://:50000/. This opens the HP SIM user interface of your CMS. 2. Select Remote Support Configuration and Services… from the Options drop-down menu. 3. Select the MVAA Configuration tab.
Installing and Configuring MPS 5. Select the Enable Management Platform Synchronization checkbox. Figure 3-5 Enable Management Platform Synchronization checkbox 6. Select HP Operations Manager from the Management Platform dropdown list.
Installing and Configuring MPS Figure 3-6 Management Platform Synchronization settings 7. Configure one or more HP Operations Manager Server(s) a. To add an HP OM server i. Click Add Server to List.
Installing and Configuring MPS Figure 3-8 User Interface to add an HP OM server ii. Enter details for the OVO server - SystemName, Port, OM User and Password. iii. Optional: Configure additional servers as described in steps 4 and 5. IMPORTANT: MPS can handle multiple HP-UX OVO servers or multiple Windows OVO servers on a single CMS (for all incidents synchronized with the OVO server where the incident originated from). A mixture of HP-UX and Windows OVO servers is not possible.
Installing and Configuring MPS 3-3 Managing CMS monitored devices in OVO NOTE: The tasks described in this section are only required when the monitored devices are not already set up in OVO. If all the monitored devices have OVO agents deployed or are set up in the node bank already it is not necessary to read this section. NOTE: The descriptions and screenshots in this section apply to the HP-UX version of OVO. The Windows version of OVO might differ. To monitor a device, an OVO node should be added.
Installing and Configuring MPS Figure 3-10 Add Node 3. After adding a node, the node is shown in the node bank. 4. Add node to a node group to which the OVO Web service user has access rights.
OVO Collection Extensions 4 OVO Collection Extensions 4-1 Introduction This introduction explains when it is necessary to use OVO collection extensions and how they are installed. IMPORTANT: This chapter describes additional features of the MPS.
OVO Collection Extensions If the monitoring of HP-UX servers is done via the OVO agents, then the Event Management System (EMS) must be installed and ready to use. For a Sun Solaris or an IBM AIX platform installation, no specific diagnostic software is needed. Although the monitoring of hardware failures does not significantly increase the load on an OVO management system, we recommend having some reserve capacity in OVO, and to avoid deploying MPS when OVO resources and performance are already critical.
OVO Collection Extensions additional information to the OVO management station. MPS will look for these messages through a webservice and copy them to HP. In the new releases of HP-UX – 11.31 and later, EMS is replaced by the System Fault Manager (SFM). Incidents from SFM are sent directly to the CMS using the WBEM message standard. In this case there would be no collection through OVO needed.
OVO Collection Extensions 4-2 Managing OVO Monitored Devices on the CMS To allow the automatic generation of incidents in HP, essential information is required for each managed system including: ○ The exact product and serial numbers ○ The contacts associated with the specific managed system(s) ○ Warranty or contract status (entitlement) of a device. The management of this information can be done in alternate ways depending on your preferences which are described below.
OVO Collection Extensions Figure 4-2 Manage MPS using HP SIM 4-2-1-1 Adding a monitored device by HP SIM 1. Click menu Options->Discovery The Discovery page is shown. 2. Choose the Manual tab. Figure 4-3 Manual Tab in HP SIM 3. Input the system name or FQDN of the monitored devices. 4. Click Add System.
OVO Collection Extensions 5. Wait a few seconds then click All Systems, the discovered system is shown: Figure 4-4 System in HP SIM 6. Click the system name. 4-2-1-2 Edit a monitored device in HP SIM 1. Click any existing device 2. Choose the Tools & Links tab. 3. Click Edit System Properties. Figure 4-5 Edit System properties in HP SIM 4.
OVO Collection Extensions Figure 4-6 Edit System Properties 5. The production, entitlement, contact and other information for this device can be added or edited on this page. 4-2-1-3 Removing a device monitored by HP SIM 1. Click menu item All Systems. 2. Choose the devices to be removed, and click Delete.
OVO Collection Extensions 4-2-2 Managing MPS devices monitored by WEBES In WEBES, device information is divided into three parts: site, contact and entity On the CMS server, run menu “All Programs”->”Hewlett-Packard Service Tools”->”System Event Analyzer”->”System Event Analyzer”, input anything as profile when an edit box displayed, “Managed Entities” page shows by default. 4-2-2-1 Manage sites in WEBES Click the button “Configure Webes Managed Sites” (the red button on the top of page below).
OVO Collection Extensions 4-2-2-2 Manage contacts in WEBES Click the button “Configure Webes Managed Contacts” (the red button on the top of page below). Contact managing page shows. Figure 4-13 WEBES – Managed Contacts page 4-2-2-2-1 Add a new contact to WEBES Click button “New” to add a new contact 4-2-2-2-2 Edit a contact in WEBES Click the link of the name of contact to be edited.
OVO Collection Extensions 4-2-2-3 Manage entities in WEBES Click the button “Configure Webes Managed Entities” (the red button on the top of page below). Entity managing page shows. Figure 4-14 WEBES – Managed Entities page 4-2-2-3-1 Add a new entity to WEBES Click button “New” to add a new entity 4-2-2-3-2 Edit an entity in WEBES Click the link of the name of entity to be edited.
OVO Collection Extensions 4-3 Installing MPS on the OVO Management Server This section describes the procedures for installing and verifying installation of MPS on the OVO Management Server. It describes how to deploy and verify deployment of OVO agent templates. 4-3-1 Installing MPS on the OVO Management Server on HP-UX 4-3-1-1 Access the Install Package MPS installation agent templates are located in \distribution . Files: MPS_for_OVO8_HPUX.
OVO Collection Extensions After installation, the following modules will be installed on the OVO server: 1. HP MPS Template group and template groups under it. (Refer to the Troubleshooting Guide for further information). 2. MPS Application group and its applications. (Refer to the Troubleshooting Guide for further information). 3. HP-RST Message group. 4.
OVO Collection Extensions 4-3-1-5 Deploying OVO Agent Templates to OVO Managed Nodes This section describes how to deploy and verify deployment of OVO Agent templates to OVO managed nodes (HP-UX, Solaris, and AIX devices). IMPORTANT: Before deploying templates to an OVO managed node the OVO agent must be deployed on the node and the node must be part of a node group. For different platforms, only different templates or template groups are selected, other steps are the same.
OVO Collection Extensions 3. After the Define Configuration window shows, click Add. Figure 4-17 Define Configuration 4. The Add Configuration window shows. If Nodes/Groups are empty, select nodes or groups in the node bank or group node bank and click Get Map Selections. Then click Open Template Window.
OVO Collection Extensions 5. The template window shows. This example is using the AIX node as the managed node, so the AIX-MPS template group is selected. NOTE: This is the only part of the deployment process which differs for different platforms. The customer can select which platform they want to affect here. Figure 4-19 Select Template 6. Click Get Template Selections in the Add Configuration window. Both the nodes/groups and templates are selected.
OVO Collection Extensions 7. Click OK to close the window. In the Define Configuration window, the templates are assigned to their associated nodes/groups. Figure 4-21 Assign Template 8. Click OK to close this window. After templates are assigned, they need to be deployed to nodes.
OVO Collection Extensions 9. Click Actions>Agents>Install/Update SW & Configuration. Figure 4-22 Install/Update Software 10. The Install/Update OVO Software and Configuration window will appear.
OVO Collection Extensions NOTE: Please check the Templates, Actions and Commands options for templates used in MPS containing scripts. NOTE: Scripts used by OVO applications are also deployed during this operation. 11. After deployment, one message will be created. Figure 4-24 Message Browser 12. On the managed node, use the command ovpolicy –list to show the template installed: Figure 4-25 Command for Managed Node 13. The AIX-MPS template group contains two templates: AIXLog and AIXEvent.
OVO Collection Extensions 4-3-1-6 Deploying the OVO Agent Templates to HP-UX Devices The template assignment and deployment process are the same for different platform nodes, only the templates selected are different. Below is the template used for HP-UX. The scripts and applications used by templates are deployed at the same time when Templates>Actions>Commands is selected.
OVO Collection Extensions Figure 4-28 AIX Template 4-3-1-9 Register Monitored Devices with MPS During installation, an application group MPS will be created, and an application Register Device will be included in this application group. Each device must be registered once. In the OVO node bank, select the node and execute the application. The registering device process will then start on each node. 1. The script used in the OVO application is downloaded during template deployment.
OVO Collection Extensions Figure 4-30 Output of Application 42
OVO Collection Extensions 4-3-2 Installing MPS on the OVO Management Server on Windows Installing MPS on a Windows-based OVO Management Server requires the following steps 1. Copying OVO collection templates and migration scripts to the OVO Management Server 2. Unzipping all zipped files 3. Executing the migration scripts on the OVO Management Server to convert the templates 4.
OVO Collection Extensions 4-3-2-3 Migrating all templates to OVO Windows On the OVO Windows server convert the MPS templates to OVO Windows policies. Execute cscript C:\temp\MPS\OVOU2OVOW\Main.vbs C:\temp\MPS\MPS_AIX_templates cscript C:\temp\MPS\OVOU2OVOW\Main.vbs C:\temp\MPS\MPS_for_OVO8_HPUX cscript C:\temp\MPS\OVOU2OVOW\Main.vbs C:\temp\MPS\MPS_HPUX_templates cscript C:\temp\MPS\OVOU2OVOW\Main.vbs C:\temp\MPS\MPS_Solaris_templates.
OVO Collection Extensions Tool: MPS/RegisterDevice Instrumentations A new instrumentation directory is created: %OvInstallDir%\data\shared\Instrumentation\Categories\MPS\UNIX, files are copied from C/EXECUTABLES to the unzipped directories.
OVO Collection Extensions Figure 4-37 Deploy OVO Windows policies on Solaris monitored systems 4-3-2-5 Configure MPS service to work together with OVO Refer to chapter 3-2 Adding one or more OVO servers of this document.
OVO Collection Extensions 4-3-2-6 Run "RegisterDevice" tool on nodes Before receiving any events from node, registration information should be collected from nodes. Double click the tool “RegisterDevice” in tool group “MPS”: Figure 4-38 Register Devices Select the nodes or node groups to run the tool on, then click Launch… . A new window will show the result. IMPORTANT: Each time the policies are imported, they are of version 1.0. Versions will never increase from one migration to another.
Appendix A 5 SAP SolMan integration 5-1 Prerequisites The installation of the integration requires that the two software packages Solution Manager Service Desk and HP Instant Remote Support Advanced are deployed and working and that the required workflow processes are understood and ready to implement.
Appendix A 5-2 Installing the SolMan integration 5-2-1 Overview The installation consists of the following steps 1. Verify if all prerequisites are met, if necessary complete the required updates and install all available patches.(Refer to section 5-1 for further information). 2. Install the Multivendor Application Adapter (if not done already). 3. Configure the connection from the CMS to the server which hosts the Solution Manager in the Insight RSA configuration User Interface (UI) in HP SIM. 4.
Appendix A 3. The http settings in the screenshot below are needed – please enter the CMS name as the target host NOTE: Please use exactly the Service number 8080 and the path prefix /axis2/services/ICT_SERVICE_DESK_APIService 5-2-3 Configuring the SolMan Connection Open the HP System Insight Manager portal on the CMS – https://localhost:50000/mxprtal/home/ 1. Click on the Options drop-down menu in the top row. 2. Select Remote Support Configuration and Services 3.
Appendix A 10. Obtain the subject/category key value configured in SolMan Service Desk for synchronized incidents. Provide the SAP Category key, NOT the name of the category. Please refer to Appendix A to find out how to configure the Solution Manager to show these keys. 11. Enter this value into the corresponding field 12.
Appendix A 5-2-5 Configuring the Solution Manager – Part Two The second part of configuring the Solution Manager involves completing the settings in the Solution Manager. In the following picture example settings are shown: Please refer to the SAP training video for SAP Solution Manager integration for more details on this step. TIP: The training video is available at the following location: https://websmp209.sap-ag.de/~sapidb/011000358700000176252009E/index.
Appendix A Appendix A How to configure the solution manager to get the category key How to display the key in SAP Fields This process is a personalization of the users SAP Graphical User Interface (GUI). 1. In the Top Bar click on the icon for Customize Local Layout as shown below. 2.
Appendix A 3. Set the flag on Show keys in All Dropdown Lists and Click OK The keys are displayed in front of the description. This setting is now valid for all fields in the SAP GUI.
