hp software omu what’s new & tips & techniquesfcsseldorf_omu_schmol... · nnmi...

HP Software OMU

What’s new &Tips & Techniques

© 2008 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice

Hans-Peter Schmollinger

OMU Architect,Hewlett Packard

VivitVivitVivitVivit DDDDüsseldorfüsseldorfüsseldorfüsseldorf

Agenda: Integrations

Product Integration

BAC 7.5/8.0 state synchronizing + context launch

SiteScope 9.5 Runtime + SiteScope Sam Admin

27 November 2008

SiteScope 9.5 Runtime + SiteScope Sam Admin

NNMi 8 integration

New WebService-Stack officially released

DMA is covered via other sessions

Agenda: What’s new within OMU

Patch update E.G. 8.31 including

Configuration Value Pack -> BES Midas

OMU 9 next version

37 November 20083

Patch update E.G. 8.31 including

Performance Manager 8.10

Operator GUI enhancements

Agenda: Tips & Tricks

Auto granting

Assign services to user profiles

47 November 20084

Assign services to user profiles

Multiple Logfile (LE) Interceptors

Multiple Action Agents

When was OM called OpC released the first version time?

HP Operations Center

1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008

OMUOpC

ITO

3.0

ITO

4.0

ITO

ITO

5.3

VPO

6.0

OVOU

7.0OVOU

8.0

OMU

OMU

8.31

OMU

8.20

Historical summary

67 November 2008

OMW

OpC

1.0

OpC

2.0ITO

5.05.3

OVOU

8.10

OMU

8.27

VPW

6.0

VPW

6.10

OMW

8.0

OMW

8.10

OMW

7.50OVOW

7.20

OVOW

7.10

OVOW

7.0

OVOW

7.21OVOW00189

OVOW00210

OVOW00228

OVOW00229

NOTE: Product name changes for marketing reasons only!

HP Software Evolutionscope and revenue

Data center transformation

IT Services

The cloud

Service Service Service Service ––––driven driven driven driven OperationsOperationsOperationsOperations

Business Business Business Business Service MgmtService MgmtService MgmtService Mgmt

Business Service Business Service Business Service Business Service AutomationAutomationAutomationAutomation

Service Lifecycle Service Lifecycle Service Lifecycle Service Lifecycle MgmtMgmtMgmtMgmt

Manage across Manage across Manage across Manage across the IT value chainthe IT value chainthe IT value chainthe IT value chain

2008/10 IDC2008/10 IDC2008/10 IDC2008/10 IDCHP Performance and HP Performance and HP Performance and HP Performance and

Availability Management Availability Management Availability Management Availability Management Number 1 in distributed Number 1 in distributed Number 1 in distributed Number 1 in distributed

2008200820082008

1980198019801980

200720072007200720062006200620062005200520052005

2000200020002000

1997199719971997

19901990199019901993199319931993

The big iron ageThe client/server age

The webNetwork Network Network Network MgmtMgmtMgmtMgmt

Integrated Network Integrated Network Integrated Network Integrated Network & System Mgmt& System Mgmt& System Mgmt& System Mgmt

Application Application Application Application MgmtMgmtMgmtMgmt

IT Service IT Service IT Service IT Service MgmtMgmtMgmtMgmt

Service Service Service Service ––––driven driven driven driven OperationsOperationsOperationsOperations

Service MgmtService MgmtService MgmtService Mgmt

OpswareOpswareOpswareOpsware

TowerTowerTowerTower

MercuryMercuryMercuryMercury

SPI DynamicsSPI DynamicsSPI DynamicsSPI Dynamics

Bristol Bristol Bristol Bristol TechnologiesTechnologiesTechnologiesTechnologies

PeregrinePeregrinePeregrinePeregrine

NovadigmNovadigmNovadigmNovadigm

TeMIPTeMIPTeMIPTeMIP

ProlinProlinProlinProlin

TrinagyTrinagyTrinagyTrinagy

HP Operations Manager HP Operations Manager HP Operations Manager HP Operations Manager Number 1 in OperationsNumber 1 in OperationsNumber 1 in OperationsNumber 1 in Operations

In Gartner’s Magic QuadrantIn Gartner’s Magic QuadrantIn Gartner’s Magic QuadrantIn Gartner’s Magic Quadrant

Number 1 in distributed Number 1 in distributed Number 1 in distributed Number 1 in distributed environmentenvironmentenvironmentenvironment

OMU Integration Demo

BAC 7.xOM/U Web based

Configuration Value Packand Midas

Operations Manager UnixIntegration Demo

Operations Manager Unix

Best in class event management

9 7 November 2008

Operations Manager Unix

New WebServices

OMSAM Admin

for SiteScope

NNMi integration

Demo

http://yogibear.deu.hp.com/LasVegas2008/OMU_Integration_demoV2.0.exe

10 7 November 2008

OM UnixIntegration Package

Ready to be

downloaded

OM/UNIX Integration Package

• Download page:ftp://ovweb.external.hp.com/pub/cpe/ito/OM-Installation/

• Including Manuals

12 7 November 2008

• Including Manuals

OM/UNIX Integration Package

• New Integration Package OM/UNIX is ready for download

• Includes−SiteScope Administration (Sam Admin reused from BAC)

−OM Incident Web-Services

13 7 November 2008

−OM Incident Web-Services

−NNMi enablement technology

• Prerequisite:− OMU 8.30 patch

− Java API patch

Component Dependency Graph

OM IncidentWeb-Service

OM SAM Admin+SiteScope Runtime

interationNNM i 8

OM Incident client Reuse of BasicAuthentication

for URLs againstOMU

14 7 November 2008147 November 2008

OM-NNMiintegration

For 8.2, included inOMU 8.30 patch

ovtomcatB

OvXpl 06.00.060 JRE 1.5

DMA CI WebService

Basic Authentication

OM – SiteScope Sam Admin

OM—SiteScope Sam Admin

16 7 November 2008

OM—SiteScope Sam Admin

• Main purpose−Show overview of all SiteScope instances

−Sync SiteScope config between SiteScope instances

−Ease of use out of OM Console

• The web app is reused from BAC

17 7 November 2008

• The web app is reused from BAC

• HP OM/Windows 8.10+ will release a server patch + add-on package by end of 2008.

OM 8—NNM i 8 IntegrationArchitecture and Implementation DetailsImplementation Details

Integration Architecture

OMIncidentService

IncidentServiceClient

Messagemanager

NNM i 8 OM 8

19 7 November 2008

ConfigurationXML

UI launch

OMOperator

UIWebBrowser

DB

WebUI endpoint

Implementation of the NNMi part

• Incident service client for NNMi−Message Driven Bean, listening on JBoss message bus

−Configuration via XML file

−Enablement controlled via commandline tool

• Uses the OM Incident WS for Incident (message)

20 7 November 2008

• Uses the OM Incident WS for Incident (message) creation and Incident updates

• Several of Applications for General NNM use

• General (<host>)

− NNMi Console

− NNMi Status

− myIncidentTableView

− openRCIncidentTableView

OM provides a default set of NNMi applications

General set of NNMi applications in OM

21 7 November 2008

− openRCIncidentTableView

− signinaudit tool

• NNM Int-Admin

− Create Server Apps

NNMi applications in OM used in node context• Several of Applications for the

use in a node context• By Node (<host>)

− Configurationpoll tool

− Commconf tool

− Statuspoll tool

− Ping tool

− Traceroute tool

22 7 November 2008

− Traceroute tool

− Node information

− Showlayer2neighbors

− Showlayer3neighbors

• By Incident

− Incident Node Form

− Incident

− Showlayer2neighbors

− Showlayer3neighbors

NNMi applications in OM used in incident context• Several of Applications

for the use in an Incident (Message) context

23 7 November 2008

Application Integration Script

• The central integration part of the NNMi integration in OM is the Application Integration Script

• In OM 8.2 is the script responsible for the initial set-up of the NNMi Message Group and the basic set of NNMi Applications

• In OM 8.30 is the script also used to add those sets of

24 7 November 2008

• In OM 8.30 is the script also used to add those sets of NNMi applications that require the definition of the NNMi server in the call. These are the ‘General’ and ‘By Node’ applications

Demo call of the script

• The result is a new set of the applications− General (Server 1)

− By Node (Server 1)

> create_nnm_appls.sh

Full qualified name of the NNMi system:

nnmsv1.company.com

Short name of the NNMi system [nnmsv1]:

Server 1

Port to access the NNMi system [8004]:

80

==========================================

25 7 November 2008

==========================================

System Name: nnmsv1.company.com

Short Name: Server 1

Port: 80

==========================================

Are these parameter correct?

Press [ENTER] to proceed or [^C] to cancel.

Done

Workflow in OM

26 7 November 2008

OM WebServices–Overview

Agenda

OM Incident WS – What it provides

Supported WS Clients

OMW and OMU WS compatibility

28 7 November 2008

OM Unix WS Server Architecture

Incident WSDL

Demo WS client implementation

Backup – WS Management Protocol Composition

Backup – CI WebServices (DMA)

OM Incident WS—what it provides • Integration Model (IM) compliant Incident attributes (ITIL aligned)

+ OM specific extensions (e.g. custom attributes, …)

• Create, Read and some Update Operations (severity, title, annotations, custom attributes)

• Incident Operations incl. mass operations (close, own, …)

• Notification support based on public subscribe and pull mechanism

• Secured access of Web Service (SSL secured, requires OM user/passwd

29 7 November 2008297 November 2008

• Secured access of Web Service (SSL secured, requires OM user/passwd authentication)

• Documentation for integrators

• Supported for

− OMU 8.30 (April 2008)• HP-UX Itanium: 11.23, 11.31

• HP-UX PA-RISC: 11.11, 11.23, 11.31

• Solaris: 9,10

− OMW 8.1• Windows (x86): 2003 Server

Supported WS clients

AXIS2 based

WS Cclient

Any WSclient

WS-Man based

WS client

Any WSclient

.net based

WS client

Any WSclient

30 7 November 2008307 November 2008

OM UNIX 8.30

Web Services

Incident WS

OM Ext.

Incident WS

OM Ext.

Integration Model Service

Product Service Extension

WS clients (AXIS, .net, Wiseman, …)

Wiseman based implementation

+ Axis2 WSDL extension

OMW and OMU WS compatibility

OVO forWindows

ISM supporting App

Web Services

Incident WS

OM Ext.

Incident WS

App Ext.

…

HP OutsourcingServices

Any WSclient

Partners / Customers

Any WSclient

NNM

Web Services

NNM WSclient

Wiseman based

31 7 November 2008317 November 2008

OM UNIX 8.30

Web Services

Incident WS

OM Ext.

Incident WS

OM Ext.

OM Windows 8.1

Web Services

Incident WS

OM Ext.

Incident WS

OM Ext.

Integration Model Service

Product Service Extension

WS clients (AXIS, .net, Wiseman, …)

Both OMs expose

identical WSs

WCF based implementation

Wiseman based implementation

OM Unix WS server architecture

J2EE Server

WS ManagementServlet

Dispatcher

ResourceHandler

Web ServiceConsumers

1 1

1

0..*

Serv

ices

32 7 November 2008

Legend:Blue: Wiseman CodeGrey: Application Code

HandlerDelegate

Resource IteratorFactory

Resource

ResourceEnumeration

Iterator

EnumerationSupport

1

1

1

0..*

1 0..*

InstantiateCRUD

&custom

operations

Enumerate

Enumerate

Enumerate

OM Unix WS server architecture

OMU Server

MSIMessage Manager

(opcmsgm)

Create New

Message

Read Change

J2EE Server

WS Management

ServletDispatcher

Resource

Handler

Web ServiceConsumers

1 1

1

0..*

Serv

ices

33 7 November 2008

Legend:Blue: Wiseman CodeGrey: Application Code

(opcmsgm)

Data Base(dblib)

Read Filtered

Messages

Read Change

Events (new,own, ..)

Handler

Delegate

ResourceIteratorFactory

Resource

Resource

Enumeration

Iterator

Enumeration

Support

1

1

1

0..*

1 0..*

InstantiateCRUD

&custom

operations

Enumerate

Enumerate

Enumerate

WSDL https://<OMU server>:8444/opr-webservice/Incident.svc?wsdl

34 7 November 2008

ExampleBelow /opt/OV/contrib/OprWsInc/clients/ you get three example implementations for:

axis wcf wiseman

Example: Generate incidents (OM msgs) using the Wiseman client

public class WsmanClientTester_hpeter

{

private static WsmanClient client;

private static EndpointReferenceType epr;

public static void main(String[] args) throws Exception

{

client =

new WsmanClient("opc_adm", // username

"opc_adm", // passwd

"", // keystore (optional)

35 7 November 2008

"", // keystore (optional)

"com.hp.schemas.ism.serviceoperation.incidentmanagement._1.incident",

"com.hp.schemas.ism.serviceoperation.incidentmanagement._1.incidentextensions",

"com.hp.schemas.opr.ws.serviceoperation.incidentmanagement._1.incident",

"com.hp.schemas.opr.ws.serviceoperation.incidentmanagement._1.incident.change",

"com.hp.schemas.opr.ws.serviceoperation.incidentmanagement._1.incidentfilter");

// Base incident EndpointReference to which server it should go

epr =

WsmanClient.createEndpointReference("https://elisa.deu.hp.com:8444/opr-webservice/Incident.svc",

"http://schemas.hp.com/ism/ServiceOperation/IncidentManagement/1/Incident",

null);

Incident incident = new Incident();

IncidentHelper.setEmittingNode(incident, "elisa.deu.hp.com"); //msg node

IncidentHelper.setAssignedOperator(incident, "opc_op"); //own message immediately

incident.setTitle("Hello World, I am ws-man client"); //msg_text

incident.setSeverity("Minor"); //severityJAXBElement<Incident> incidentElement = new JAXBElement<Incident>(QNames.INCIDENT, Incident.class, null, incident);

EndpointReferenceType incidentEpr = client.create(incidentElement, epr);

// read message from server and print out all attributes

Object incidentObject = client.read(incidentEpr);

if (incidentObject instanceof Incident)

Example (2)Below /opt/OV/contrib/OprWsInc/clients/ you get three example implementations for:

axis wcf wiseman

Example: Read incidents (OM msgs) using the Wiseman client

// read message from server and print out all attributes

Object incidentObject = client.read(incidentEpr);

if (incidentObject instanceof Incident)

{

Incident inc = (Incident) incidentObject;

System.out.println(IncidentHelper.getIncidentString(inc));

36 7 November 2008

System.out.println(IncidentHelper.getIncidentString(inc));

}

}

Demo WS client • Demo stubs for AXIS2 and Wiseman are part of the installation.

# /opt/OV/support/oprweb/client/java/runclient.sh \

-host <host> -port <port> -user <user> -password <password> [-ssl] \-action <action>

action: enumerate [-expires <default|ExpirationDateInXmlFormat>] [-filter <EnumerationFilter attributes>]

release -context <context returned from enumerate request>

get -id <id>

create -title <title> -emittingNode <emittingNode> [-attr <optional attribute>]*

put -id <id> -title <new title> -severity <new severity>

37 7 November 2008

put -id <id> -title <new title> -severity <new severity>

subscribe [-expires <default|ExpirationDurationInXmlFormat>] [-filter <EventingFilter attributes>]

renew -context <context returned from subscribe request> -duration <duration in ms>

unsubscribe -context <context returned from subscribe request>

pull -context <enumeration context returned by subscribe action> [-maxelements <max number of incidents>]

close -id <id> [-id <another id>]*

reopen -id <id> [-id <another id>]*

own -id <id> [-id <another id>]*

disown -id <id> [-id <another id>]*

addAnnotation -id <id> -text <annotation text>

updateAnnotation -id <id> -annotationid <annotation id> -text <annotation text>

deleteAnnotation -id <id> -annotationid <annotation id>

getAnnotations -id <id>

setCustomAttribute -id <id> -key <key> -text <text>

deleteCustomAttribute -id <id> -key <key>

OM WebServices Demo

http://yogibear.deu.hp.com/LasVegas2008/OMU_WebServiceDemo0002.exe

Demo WS client (2)optional attributes:

[-description <description>]

[-severity <severity>]

[-solution <solution>]

[-category <category>]

[-subcategory <subcategory>]

[-producttype <product type>]

[-problemtype <problem type>]

[-collaborationmode <collaboration mode>]

[-emittingci <emitting ci>]

[-application <application>]

EnumerationFilter attributes:

[-severity <severity>]*

[-emittingnode <emittingnode>]

[-category <category>]

[-application <application>]

[-object <object>]

[-emittingci <emitting ci>]

[-correlationkey <correlation key>]

[-escalationstatus <escalation status>]

[-conditionmatched <condition matched>]

[-receivedtime <recieved time> <at|from|to>]

39 7 November 2008

[-object <object>]

[-type <type>]

[-creationtime <yyyy-MM-dd HH:mm:ss[+HHmm]>]

[-correlationkey <correlation key>]

[-customattribute <key> <text>]*

[-title <title> <exactly|contains>]

[-customattribute <key> <text>]*

EventingFilter attributes:

[-severity <severity>]*

[-emittingnode <emittingnode>]

[-category <category>]

[-application <application>]

[-object <object>]

[-emittingci <emitting ci>]

[-correlationkey <correlation key>]

[-escalationstatus <escalation status>]

[-conditionmatched <condition matched>]

[-forwardtotroubleticket <forward>]

[-forwardtonotification <forward>]

[-changetype <new|modified|closed|reopened>]*

[-title <title> <exactly|contains>]

[-customattribute <key> <text>]*

WS Management Protocol Composition

WS-Management

WS-Management WSDL Binding for CIM

WS-CIM Schema Translation IntegrationIntegration

DescriptionDescription

ApplicationApplication

40 7 November 2008

HTTPS, TCP

XML, SOAP, WS-Addressing

Security Profiles

WS-EventingResource Addressing Model WS-Transfer WS-Enum Data TransferData Transfer

SecuritySecurity

MessagingMessaging

TransportsTransports

What’s new in OMU

CVP Update

Web-Based Administration for HPOM for UNIX version 8.x• HP no longer sells the Configuration Value Pack product. Current CVP

customers under support should contact blue elephant systems (BES) directly for their entitlement to the MIDAS Configurator product. The URL for this migration is http://www.besint.com/content/view/149/182/

• For customers interested in acquiring a web-based administrative tool for Operations Manager, there are a number of solutions provided by several HP Partners. Please refer to the HP Partner portal at:

43 7 November 2008

HP Partners. Please refer to the HP Partner portal at:

• http://h20229.www2.hp.com/partner/directory/partners.html?c=22-2-4

• We strongly encourage existing CVP customers to migrate to the MIDAS Configurator. The two products are functionally identical (CVP was an OEM of the BES MIDAS Configurator). Migrating now will allow you to receive updates and support directly from BES.

OMU 9 overview

OMU9 - Key New FeaturesWeb-based Administrative UI• Multiple administrators with granular use roles• Jump from OM Message in Java UI directly into policy configuration• Admin UI is “light-weight” version of Configuration Value Pack / Midas

Configurator (bes)• Automatic config sync of Operator/Java GUI E.G add node without

reload config

Policy Enhancements• Policy versioning• Policy versioning• Support of WMI, Service Discovery, Windows Eventlog, …

policy types• Support of advanced scripting/thresholding• Store threshold (opcmon) value into EPC (Coda)• Custom Message Attributes also for

– SNMP policies– Scheduled actions

45

OMU9 - Key New Features

Product installation•De-coupled OMU server software installation &

configuration (with granular re-entry & customization points)

•Native installation on Solaris (pkg_add)Oracle DB improvements•AL32UTF8 support (Unicode standard 4.0) - enables •AL32UTF8 support (Unicode standard 4.0) - enables

to store differently localized OM messages in the same DB

•On-line config upload (opccfgupld) without OMU server restart. Re-read of important OMU configuration files and XPL variables, which required a restart so far.

46

HP Operations Manager 9.0 for UNIX

OMU Server

HP-UX 11iv3 on HP Integrity(= HP-UX Itanium11.31)

Sun SPARC Solaris: 10

OM HTTPS Agents

All platforms supported with 8.51 and higher:

Definition of the Beta requirements

[Oct 2008] – HP Restricted47474747

with 8.51 and higher:HP-UX PA/IA, Solaris SPARC/x86,

MS Windows x86/x64/IA, Linux x86/x64/IA/zSeries,

AIX, Tru64, OpenVMS Alpha/IA

JRE / Browsers

JRE 5 or 6,Internet Explorer 7, Mozilla Firefox 1.5+

OMU 8.xxPatches

Server Enhancements in 8.31

Automatic Message Key Creation

To avoid the duplicate suppression of the messages that do not have a message key and improve performance, an automatic message key creation is introduced. A Message Manager configuration setting OPC_CREATE_AUTO_KEYS automatically creates a message key for messages that do not have it. This behavior is enabled by default and it

49 7 November 2008

messages that do not have it. This behavior is enabled by default and it also requires that Suppress and Count Duplicate Messages server option is enabled. If a message has no message key, it is created in the following format:

AUTOKEY:HASH

where HASH is calculated as an SHA-1 hash of the following message attributes: node name, message group, application, object, service name, severity and message text Note that message key is not automatically generated if a message has zero length message key defined.

Server Enhancements in 8.31Improved Heartbit Polling

Several changes are introduced in the HPOM heartbeat polling area to avoid false alerts:

• For server initiated HBP to HTTPS agents:

In case a new OPC_HBP_DOUBLE_CHECK config setting is set to TRUE, the current ovoareqsdr worker

thread immediately re-checks the agent, if the error is not node down or network

50 7 November 2008

thread immediately re-checks the agent, if the error is not node down or network down.

• For agent sends alive package:

If ovoareqsdr gets an agent alive package that indicates that ovcd is down, and the new behavior is enabled by setting the OPC_RECHECK_AGENT_ALIVE_OVCD_DOWN config setting to TRUE, ovoareqsdr handles this as if it did not get any alive package. That means it will initiate active heartbeat polling when the polling interval is reached.

If it was a temporary situation, the active HBP shows that there are no problems and no HBP error is sent. If an error is still present at that time you will get a specific HBP error.

Performance Manager 8.10 integration updateContrib. Tool

http://yogibear.deu.hp.com/LasVegas2008/OMU_OVPM0005.avi

Updated integration contrib tool with OMU 8.31 patch:

#/opt/OV/contrib/OpC/OVPM/install_OVPM.sh

Performance Manger 8.1x integration

52

Updated integration contrib tool with OMU

8.31 patch:

1.Install Performance Manager 8.10 on a remote PC

2.Use script to upload application definition and

Performance Manger 8.1x integration

53

2.Use script to upload application definition and

define PM remote node #/opt/OV/contrib/OpC/OVPM/install_OVPM.sh

3.Assign application group “OVPM” to

users/operator

OMU 8.27 patch numbers

All of the patches listed below as well as the Release Notes are planned for mid of 10/2007.

Platform OMU 8.27 server A.08.27 Java GUI

A.08.27Java GUI repackaged

for OMU 7.x

Itanium PHSS_36831 PHSS_37182 N/A

54 7 November 2008

Reminder: List of latest OMU patches can be found on

http://openview.hp.com/ecare/getsupportdoc?docid=OVO-PATCHES

Reference info for OMU 8.26 (intermediate patch) in notes.

Itanium PHSS_36831 PHSS_37182 N/A

PA-RISC PHSS_36832 PHSS_37183 PHSS_37197

SPARC ITOSOL_00601 ITOSOL_00618 ITOSOL_00619

Overview of enhancements introduced with 8.27 server patch• Performance improvement for count/suppress duplicates

• Reduced server processes startup time

• Automatic and independently restart of aborted OMU processes

• opcragt – multi-threaded

• opcragt – cleanstart

• User responsibility matrix modification via CLI

55 7 November 2008

• User responsibility matrix modification via CLI

• Improved error message for unknown nodes

• Enhanced profile report – users <-> profile assignment

• itochecker error for node with multiple IP addresses

• opccfgupld – option to delete templates not existing in upload file

• opccfgout - modified error message for nodes with unresolvable

• Notification messages directly to history log

• Java GUI client version control

Overview of enhancements introduced with 8.27 server patch

• New APIs/CLIs:−API to delete container element w/o deleting object itself

−API and CLI to get and modify trouble ticket interface

−API and CLI to get/add/modify/remove Instr Text IF

−opccfgttest enhanced to test opcinstruction_*() APIs

56 7 November 2008

−opccfgttest enhanced to test opcinstruction_*() APIs

−API and CLI to get modify and delete notification service (including schedule)

−API to get and modify dbconfig and mgmtserverconfig

−API to access pattern matching code

Server Enhancements

Automatic and independently restart

57 7 November 2008

Automatic and independently restartof aborted OMU server processes

Automatic and independently restartof aborted OMU processes

OPC_RESTART_PROCESS (If TRUE opcctrlm tries to restart aborted sub processes.

The restart is done according

OPC_RESTART_COUNT and OPC_RESTART_TIMEFRAME.

If defined # is exceeded no more restart.)

• Configuration via ‚ovconfchg -ovrg server -ns opc –set

58 7 November 2008

If defined # is exceeded no more restart.)

Default: FALSE

OPC_RESTART_COUNT (# abortions within OPC_RESTART_TIMEFRAME before restart stops )

Default: 5

OPC_RESTART_DELAY (# seconds before restart)

Default: 10 (seconds)

OPC_RESTART_TIMEFRAME (# minutes without beeing restarted more than specified by OPC_RESTART_COUNT)

Default: 60 (minutes)

After configuration modification, OMU server processes have to be restarted.

Some enhancements introduced for the Operational GUI with patcheswith patches

Overview of enhancements introduced with 8.27 JGUI patch

• Sorts services by Label attribute in message browser

• Ability to disable history browser based on operator

• Java GUI client version control

60 7 November 2008

Sorts services by Label attribute

61 7 November 2008

Sorts services by Label attribute

Needs to be enabled,because it has a minor performance impact.

62 7 November 2008

performance impact.

Ability to disable history browser basedon operator

Motivation:

• Opening a history browser consumes quite some CPU on the mgmt server. With this feature you can disable the history message browser for specific user.

• OPC_JGUI_HISTBRW_DISABLED variable was introduced.

63 7 November 2008

• Example: ovconfchg -ovrg server -ns opc -set /OPC_JGUI_HISTBRW_DISABLED opc_op1,opc_op2

Logging capability for cgi script ito_op_applet_cgi.ovpl

• Motivation−CGI script has no logging mechanism.

− It is difficult to find out what is wrong in case an error happens.

• Solution

64 7 November 2008

• Solution−A logging mechanism was added.

−Logging is enabled when the file /var/opt/OV/log/ito_op_applet_cgi.log exists.

− Logging information is then written to this file.

Java GUI client version control

• Determine version of connected JGUIs on management server− listgui extended to show version of JGUIs

connected to opcuiwww

65 7 November 2008

Java GUI client version control

• Limit version which is allowed to connect −# ovconfchg -ovrg server -ns opc -set

OPC_JGUI_MINIMAL_VER A.08.28

66 7 November 2008

Operational UI Enhancements

• HP One Voice look & feel

• IE 7 support

• Message View Filtering

Delivered via Operational UI Patch 8.25

67 7 November 2008

• New startup options

• Detachable windows

• Custom filename for configuration file

• HTML application output enhancement

Operational UI – HP One Voice look & feel

JGUI 8.25 uses new HP SW appearance (set as default)

68 7 November 2008

Appearance selectable via Edit -> Preferences -> General tab -> Look and Feel

Options: Aqua, Metal, Motif, HP One Voice, Windows

Java GUI – Message View Filtering Different GUI based types of filters

69 7 November 2008

Demo

Java GUI – Message View Filtering Different GUI based types of filters

• All filters must conform to the described syntax.

• Quick− Quick access via popup menu.

− Only criteria operator ‘equal’– simple OR/AND rules only

• Simple

70 7 November 2008

• Simple− All criteria operators – simple OR/AND plus NOT rules only

• Advanced− All criteria operators – all possible rule and criteria configurations

• The definition of the filters above can also be written in plain text format opposed to GUI-based.

Java GUI – Message View FilteringQuick Message View Filters

• Show messages matching the selected values of one or more columns.

• Selecting more than one value for a single column, messages must match only one of these values (OR relation).

• Selecting more than one column, messages must match all criteria (AND relation).

• Restriction: ‘equals’ is the only operator available.

71 7 November 2008

• Restriction: ‘equals’ is the only operator available.

• Access:

− Select column header

− Right click for context menu

− Select filter values

• Rules− One difference compared to the quick message view filter: Rule

operator NOT is possible as well.

• Criteria Operators− All operators available for criteria are selectable.

Access

Java GUI – Message View FilteringSimple Message View Filters

72 7 November 2008

• Access− Actions -> Filtering -> Message

View Filter -> Simple View tab

Java GUI – Message View FilteringAdvanced Message View Filters

• No limitation: Any criterion and rule can be configured if it conforms to filter syntax.

73 7 November 2008

• Access: Actions -> Filtering -> Message View Filter-> Advanced View tab

Java GUI – Message View FilteringText format Message View Filters

• The definition of the filters above can also be written in plain text format opposed to GUI-based.

74 7 November 2008

• Access:Actions -> Filtering -> Message View Filter-> Text View tab

Java GUI – Message View FilteringHINT: Backup server sync

• All files below of this directory should be copied frequently to the backup server. This will help to have all defined View Filters available on all servers.

75 7 November 2008

# scp –r /etc/opt/OV/share/conf/OpC/mgmt_sv/jgui/* \

<backupserver>:/etc/opt/OV/share/conf/OpC/mgmt_sv/jgui/

JGUI Applet launch using CGI with parameters

• The CGI Perl script has two goals:− Extract the JGUI startup options from the URL address

− Encrypts the username and password values (if passed)

Java GUI – New startup optionsCGI Perl Script

77 7 November 2008

Java GUI – New startup options Integration Scenario

• A benefit of the new feature is e.g. its usage in environments with integrated products.

• Example: OVOU – BAC (Business Availability Center)

• One typical customer request:

• ‘As part of the OVOU - BAC integration we want to be able

78 7 November 2008

• ‘As part of the OVOU - BAC integration we want to be able to launch the OVOU message browser in context of a BAC KPI (key performance indicator) calculated based on OVOU messages.’ This is mainly a nodename or service ID!

Java GUI – New startup options Decomposed JGUI

• Applet open active message browser with node filter: http://elisa.deu.hp.com:3443/OvCgi/ito_op_applet_cgi.ovpl?user=opc_adm&passwd=opc_adm&gui.dftlayout=false&gui.msgbrw.brwpane=true&gui.msgbrw.filter.nodes=elisa.deu.hp.com&https=true

Even

79 7 November 2008

&webstart=true

is possible

Java GUI – New startup options Decomposed JGUI (8.26 feature)

• Using encoded user and passwd in the URL: http://elisa.deu.hp.com:3443/OvCgi/ito_op_applet_cgi.ovpl?init1=6f70635f61646d&init2=6f70635f61646d&gui.dftlayout=true&gui.msgbrw.brwpane=true&gui.msgbrw.filter.nodes=elisa.deu.hp.com&https=true

• init1 = user

Init2 = passwd

80 7 November 2008

• Init2 = passwd

• How to encode:# /opt/java1.5/bin/java -cp /opt/OV/www/htdocs/ito_op/ito_op.jar \ com.hp.ov.it.ui.OvEmbCrypto opc_adm6f70635f61646d

Launch OVO UI in context out of BAC

Add Context Menu Item

Pre-processor Class: Dashboard generic URL

URL: http://<ovosrv>:3443/OvCgi/ito_op_filter.ovpl

81 7 November 2008

URL: http://<ovosrv>:3443/OvCgi/ito_op_filter.ovpl

Key: OvoNodeValue: NODE.PROPS.host_dnsnameConvert to: gui.msgbrw.filter.node

Post-processor Class: Open window

Key: SLAVE_WINValue: 0

New default startup page

82 7 November 2008

Java GUI – HTML application output enhancement

OVOU 8.25 JGUI patch covers the following ERs:

1. Enable feature centrally via XPL configuration variable.-> Precedence over itooprc parameter.

2. "<html>" with parameters should be recognized as a html output.

3. Functionality also available for instruction texts.

Enable:

83 7 November 2008

Enable:# ovconfchg -ovrg server -ns opc –set PC_JGUI_WEBBRW_APPL_RESULT TRUE

Disable:# ovconfchg -ovrg server -ns opc -set OPC_JGUI_WEBBRW_APPL_RESULT FALSE

# ovconfchg -ovrg server -ns opc -clear OPC_JGUI_WEBBRW_APPL_RESULT

Tips and Tricks

OVO Agent Install Automationusing NEW OVO/UNIX 8 feature (autogrant)feature (autogrant)

OVO Agent Install Automationusing NEW OVO/UNIX 8 feature (autogrant)

• The OVO Unix 8 functionality was enhanced to1. Improved support of HTTPS agents behind NAT sending

certificate-requests. The problem is that the node is often not part of DNS.

2. Allow automatic processing of certificate-requests for HTTPS agents, called autogrant.

867 November 2008

3. Allow automatic adding of systems to the OVO nodebank after granting a certificate-request.

4. Allow programmatically adding Node to nodegroup + immediate deployment of policies which might be assigned tothe nodegroup.

OVO Agent Install Automationusing NEW OVO/UNIX 8 feature (autogrant)

• Prerequisite only on OVO/U server needed:1.Install OVO/U 8.31 server patch

for PA-Risc (8.29 for IA64 HPUX 11.23 and Solaris)

2.Install OVO 8.17 Agent patch (8.17.2 for IA64 HPUX 11.23 and Solaris) and deploy to mgmt server.

877 November 2008

and Solaris) and deploy to mgmt server.L-core components which are part of 8.17 OVO Agent are needed on the mgmt server.

3.Download and Install below patches from HP web-page for

HPOvSext.HPOVSECCS HP OpenView Certificate Management Server

OVO Agent Install Automationusing NEW OVO/UNIX 8 feature (autogrant)

• Use # ovconfchg -ovrg server -edit

[opc]

OPC_CSA_AUTOMATION=TRUE

[opc.opccsad]

887 November 2008

OPC_CSA_RULES=rule1+(*.deu.hp.com)-(16.57.64.*)

rule1=PRE_ACTION:/tmp/pre_act.sh,ADD_NODE,GRANT,POST_ACTION:/tmp/post_act.sh

OPC_CSA_NAT_RULES=rule2+(16.57.64.*)

rule2=PRE_ACTION:/tmp/pre_act.sh,ADD_NODE,GRANT,POST_ACTION:/tmp/post_act.sh

OVO Agent Install Automationusing NEW OVO/UNIX 8 feature (autogrant)

• /tmp/pre_act.sh− To auto grant the request the node must be resolveable on the OVO/U server. This script does

get all the info passed to do the task E.G. add an entry in to /etc/hostsArgs passed to the script:Nodename=moses.deu.hp.com IPAddress=16.57.35.134 PeerAddress=16.57.35.134 RequestID=a34985e8-01dd-7524-0c93-cc52e1e9d8f8 Platform=HP-UX 11.0, CPU: PARisc MachineType=MACH_BBC_HPUX_PARISC CN=ac1fe636-e9dc-7504-0cd6-ce34067e2b55

• /tmp/post_act.sh (Siemens example)− Determine clinical device type based on the hostname by querying the SIEMENS asset

897 November 2008

− Determine clinical device type based on the hostname by querying the SIEMENS asset inventory.

− Assign this OVO managed node to appropriate OVO node group by calling

/opt/OV/bin/OpC/utils/opcnode -assign_node group_name=Auto_Grant_Nodes node_name=<nodename> net_type=NETWORK_IP

FYI, the OVO node groups have already assigned the clinical device specific policies

− Deploy the OVO policies by calling # opcragt –distrib <Nodename>

The above rules and actions are executed as part of the OVO HTTPS agent certificate request processing.

Demo

Assign services to user profiles

Assign services to user profiles

• How to enable service profile assignments

# ovconfchg -ovrg server -ns opc -set \OPCSVC_CONSIDER_PROFILES TRUE

927 November 2008

• Then you need to restart the server processes:

# opcsv -start

OVO agent scalability improvements: log file monitoring and automatic and automatic actions

Multiple parallel opcle feature

• Prerequisite: OVO HTTPS Agent 8.13 or later

• Purpose of the feature:− The feature of “multiple parallel opcle” was implemented to

improve the performance of the OVO log file encapsulation module. So far the OVO opcle process doesn't use the capabilities of multi-processor machines. Instead it's a single-

947 November 2008

capabilities of multi-processor machines. Instead it's a single-threaded program regarding it's main task, which is processing of log files. To benefit from multiple CPUs, you can start multiple opcle programs in parallel now.

− This does NOT cover the use case where you want multiple CPUs processing a single log file.

Multiple parallel opcle feature

• Basic concept: − There's one opcle that works as usual. There can be further

opcle instances, which handle only log files which names begin with a specific prefix. Let's call them special opcle. If you run multiple standard opcle in parallel, then they all process the same log files and you would get duplicate messages. Also, the standard opcle must not process such log files from the special

957 November 2008

standard opcle must not process such log files from the special opcle - again to avoid duplicate messages.

Multiple parallel opcle feature• How to configure:

You need to register the special opcle's at OV control. Some example control files are located at ./ctrl/le*.xml. The special opcle's have to be called with the command line option "-pol_prefix <comma-separated_list_of_policy_prefixes>".

• E.G. copy /var/opt/OV/conf/ctrl/opcle.xml to opcle1.xml and change the lines below<ovc:Component>

<ovc:Name>opcle1</ovc:Name>

<ovc:Label>

…

967 November 2008

…

<ovc:ProcessDescription>opcle</ovc:ProcessDescription>

<ovc:CommandLine>/opt/OV/lbin/eaagt/opcle -pol_prefix abc,bcd,cde</ovc:CommandLine>

<ovc:OnHook>

<ovc:Name>START</ovc:Name>

<ovc:Actions>

<ovc:Start>

<ovc:CommandLine>/opt/OV/lbin/eaagt/opcle -pol_prefix abc,bcd,cde</ovc:CommandLine>

</ovc:Start>

</ovc:Actions>

</ovc:OnHook>

Multiple parallel opcle feature• Tell original opcle which logiles (prefix) to ignore

# /opt/OV/bin/ovconfchg -ns eaagt -set \OPC_OPCLE_POLICY_EXCLUDE_INFO abc,bcd,cde,ghi

• You have to register the control file via the command# ovc -kill # ovcreg -add opcle1.xml# ovc –start

977 November 2008

# ovc –start

• Create policy starting with abc, assign to node and deploy

• Check if additional LE is running# ovc –status AGENT

coda OV Performance Core AGENT,CODA (5376) Running

opcmsga OVO Message Agent AGENT,EA (5377) Running

opcacta OVO Action Agent AGENT,EA (5379) Running

opcmsgi OVO Message Interceptor AGENT,EA (5380) Running

opcmona OVO Monitor Agent AGENT,EA (5381) Running

opcle OVO Logfile Encapsulator AGENT,EA (6192) Running

opcle1 OVO Logfile Encapsulator AGENT,EA (6241) Running

Multiple parallel opcacta feature

• Basic concept:

Customize startup of the existing opcacta and establish multiple additional opcacta instances. All opcacta’s process action requests from the actagtq, allowing more actions to be executed

987 November 2008

actagtq, allowing more actions to be executed in parallel.

Note: eaagt:MAX_NBR_PARALLEL_ACTIONS applies to each opcacta.

Multiple parallel opcacta feature (1/3)• How to configure:

You need to register the special opcacta's at OV control. Some example control files are located at ./ctrl/le*.xml.

Every opcacta must be called with the command line option "-<parm>“ , so modify the existing opcacta.xml first.

• Edit /var/opt/OV/conf/ctrl/opcacta.xml and change/add the lines below<ovc:Component>

<ovc:Name>opcacta1</ovc:Name>

997 November 2008

<ovc:Label>

…

<ovc:ProcessDescription>opcacta</ovc:ProcessDescription>

<ovc:CommandLine>-1</ovc:CommandLine>

<ovc:OnHook>

<ovc:Name>START</ovc:Name>

<ovc:Actions>

<ovc:Start>

<ovc:CommandLine>/opt/OV/lbin/eaagt/opcacta -1</ovc:CommandLine>

</ovc:Start>

</ovc:Actions>

</ovc:OnHook>

Multiple parallel opcacta feature (2/3)• How to configure:

Now create additional opcacta’s.

• E.G. copy /var/opt/OV/conf/ctrl/opcacta.xml to opcacta2.xml and change the lines below

<ovc:Component>

<ovc:Name>opcacta2</ovc:Name>

<ovc:Label>

…

100

7 November 2008

…

<ovc:ProcessDescription>opcacta</ovc:ProcessDescription>

<ovc:CommandLine>/opt/OV/lbin/eaagt/opcacta -2</ovc:CommandLine>

<ovc:OnHook>

<ovc:Name>START</ovc:Name>

<ovc:Actions>

<ovc:Start>

<ovc:CommandLine>/opt/OV/lbin/eaagt/opcacta -2</ovc:CommandLine>

</ovc:Start>

</ovc:Actions>

</ovc:OnHook>

Multiple parallel opcacta feature (3/3)• You have to register the control file via the command

# ovc –kill # ovcreg –add opcacta.xml# ovcreg –add opcacta2.xml# ovc –start

• Check all the opcacta’s are running

101

7 November 2008

• Check all the opcacta’s are running# ovc –status AGENT

opcacta1 OVO Action Agent AGENT,EA (3050) Running

opcmsga OVO Message Agent AGENT,EA (3056) Running

opcle OVO Logfile Encapsulator AGENT,EA (3112) Running

opcmsgi OVO Message Interceptor AGENT,EA (3117) Running

opcacta2 OVO Action Agent AGENT,EA (3119) Running

Caution: These registered opcacta’s are not preserved during agent patching. If you patch the agent the parallel opcacta needs to be reapplied manually.

Save service graph layout

HP OpenView Operations for UNIX

New button to switch of the

auto layout to do manual

positioning of the service icons

Service Graph Layout is saved

within the session settings

103

7 November 2008

Q&AQ&A

Backup

Backup Slides -Overview of enhancements introduced via patches following patches following OMU 8.10 before 8.27

Introduced features listed per patch number (1/2)JGUI – Operational service view vs. service status view 8.11JGUI – Large-scale services views in MoM environments 8.13

HTTPS-based Java UI – OVOU Mgmt Svr communication 8.14 and others

XPL tracing improvements 8.16 Core

Oracle DB and OMU mgmt independent cluster packages 8.20

opcdelmsg 8.21

opcpkgdwn 8.21

opcinstrumdwn 8.21

IP node and non-IP node with same node name 8.21

HTTPS-based forwarding 8.21

107 7 November 2008

HTTPS-based forwarding 8.21

Cloned HTTPS Agent Images 8.21

opccfguser 8.22

Deployment with Radia 8.22/8.16

Improved communication opcmsgm – opcdispm – opcuiwww 8.22/JGUI 8.22

Improved server to server communication via bulk transfer 8.23

opcragt usage for troubleshooting communication problems 8.23

opchbp – new: interval and better error handling 8.23/8.25

Outbound-only communication 8.23/8.16

opccmachg 8.24

Improved cluster error handling 8.24

OMU Server Pooling 8.24

opcownmsg 8.25

SSH based virtual terminal 8.25

Introduced features listed per patch number (2/2)Configuring backup management servers for the Java GUI JGUI 8.21

Java GUI Connection Port Setting (non-secure) JGUI 8.24

JGUI – HP One Voice look & feel JGUI 8.25

JGUI – Detached windows JGUI 8.25

JGUI – Message View Filtering JGUI 8.25

JGUI – Message Group Icons Customization JGUI 8.24

JGUI – R flag for Read-Only messages in message browser JGUI 8.24

JGUI – Full support for INFORM own mode JGUI 8.24

108 7 November 2008

JGUI – Full support for INFORM own mode JGUI 8.24

JGUI – Web Page Links JGUI 8.14

JGUI – Application HTML Output as an Internal Webpage JGUI 8.24

JGUI – HTML application output enhancement JGUI 8.25

JGUI – New startup options JGUI 8.25

JGUI – opcwall utility JGUI 8.25

JGUI – Polling Global Configuration Changes JGUI 8.21 JGUI – Allowed Users Local Configuration Files JGUI 8.21 JGUI – Custom filename for configuration file JGUI 8.25

JGUI – Performance improvements for acknow.history messages JGUI 8.23 JGUI – Verify Java Client console version via CLI JGUI 8.25

Q&AQ&A

Thank you for coming!

Technology for better business outcomesTechnology for better business outcomes