HP Software OM Tips & Techniques

HP Software OM Tips & Techniques 

Hans-Peter Schmollinger 

OMU Architect, Hewlett Packard 

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

Technology for better business outcomes

Agenda: Integrations 

•Product Integration 

−BAC 7.5 state synchronizing + context launch 

−SiteScope 9.5 Sam Admin 

−NNMi 8 integration 

•New WebService-Stack officially released 

2 4 June 2008

Agenda: What’s new within OMW 8.10 

• User Interface enhancements 

− Web UI refresh 

− MMC Console enhancements 

• Incident Web Service API 

• Platform support extensions – including 

management server platforms 

3 4 June 2008

Agenda: What’s new within OMU 

4 

• Automatic and independently restart of 

aborted OMU processes 

• Operator GUI enhancements 

• Configuration Value Pack 3.12 

• Others 

4 June 2008

Agenda: Tips & Tricks 

5 

4 June 2008 

•Auto granting 

•Assign services to user profiles 

•Multiple Logfile (LE) Interceptors 

•Multiple Action Agents

HP Software Centers 

6 

4 June 2008 

STRATEGY 

Project & Portfolio 

Management Center 

CIO Office 

SOA 

Center 

CTO Office 

Business Outcomes 

APPLICATIONS 

Quality 

Center 

OM + OMPerf. + SPI’s 

& 

SiteScope 

Performance 

Center 

SAP, Oracle, SOA, J2EE, .Net 

Business 

Availability 

Center 

Operations 

Center 

Network 

Management 

Center 

OPERATIONS 

Universal CMDB 

Service 

Management 

Center 

Change & 

Configuration 

Center

When was OM 

called OpC 

released the first 

version time? 

© 2008 Hewlett-Packard Development Company, L.P. 

The information contained herein is subject to change without notice

HP Operations Center 

Historical summary. 

OMU 

OMW 

8 

19 

93 

OpC 

1.0 

4 June 2008 

19 

94 

19 

95 

OpC 

2.0 

19 

96 

ITO 

3.0 

19 

97 

ITO 

4.0 

19 

98 

ITO 

5.0 

19 

99 

ITO 

5.3 

20 

00 

VPW 

6.0 

VPO 

6.0 

20 

01 

VPW 

6.10 

20 

02 

OVOU 

7.0 

OVOW 

7.0 

OVOW 

7.10 

20 

03 

OVOW 

7.20 

OVOW 

7.21 

20 

04 

NOTE: Product name changes for marketing reasons only! 

OVOU 

8.0 

OVOU 

8.10 

20 

05 


7.50 

OVOW 

00189 

20 

06 


8.20 

OVOW 

00210 

OVOW 

00228 

20 

07 


8.27 

OVOW 

00229 


8.0 

20 

08 


8.30+ 


8.10

OMU Integration Demo

Operations Manager Unix 

Best in class event management 

BAC 7.5 

Integration 

Integration 

Demo 

Demo 

Operations Manager Unix 

OM 

SAM Admin 

for SiteScope 

OM/U Web based 

Configuration Value Pack 

3.12 

New WebServices 

NNMi 

integration

Demo 

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

/OMU_Integration_demoV2.0.exe

OM OM OM Unix 

Unix 

Integration Integration Integration Package Package 

Package 



OM/UNIX Integration Package 

• New Integration Package OM/UNIX is ready for 

download 

• Includes 

− SiteScope Administration (Sam Admin reused from BAC) 

+ SiteScope Service and Message integration 

− OM Incident Web-Services 

− NNMi enablement technology 

• Prerequisite: 

− OMU 8.30 path 

− Java API patch 

13 4 June 2008

Component Dependency Graph 

OM-NNMi 

integration 

For 8.2, included in 

OMU 8.30 patch 

OMW 8.10 

14 4 June 2008 HP Confidential 

OM Incident 

Web-Service 

ovtomcatB 

OvXpl 06.00.060 

OM SAM Admin 

* NNM i 8 

OM Incident client 

+SiteScope Runtime 

interation 

Reuse of Basic 

Authentication 

* 

* = released with patches 

DMA CI WebService 

Basic Authentication 

JRE 1.5 

for URLs against 

OMU

OM – SiteScope Sam Admin 




16 4 June 2008


• Main purpose 

SAM Admin application enables you to configure and manage 

multiple SiteScope instances using SAM Admin within HPOM. 

− 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 4 June 2008

OM 8 - NNM i 8 Integration 

Architecture and Implementation Details 



Integration Architecture 

19 4 June 2008 

NNM i 8 OM 8 

WebUI endpoint 

Incident 

Service 

Client 

Configuration 

XML 

Web 

Browser 

UI launch 


Incident 

Service 


Operator 

UI 

Message 

manager 

DB

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) 

creation and Incident updates 

20 4 June 2008

General set of NNMi Applications in 


• OM provides a default set of NNMi Applications 

• Several of Applications for 

General NNM use 

21 4 June 2008 

• General () 

− NNMi Console 

− NNMi Status 

− myIncidentTableView 

− 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 

22 4 June 2008 

• By Node () 

− configurationpoll tool 

− commconf tool 

− statuspoll tool 

− ping tool 

− traceroute tool 

− node information 

− showLayer2Neighbors 

− showLayer3Neighbors

NNMi Applications in OM used in 

incident context 

• Several of Applications for the 

use in an Incident (Message) 

context 

23 4 June 2008 

• By Incident 

− Incident Node Form 

− Incident 

− showLayer2Neighbors 

− showLayer3Neighbors

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.2 and 8.5 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. 

24 4 June 2008

Demo call of the script 

> 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 

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

System Name: nnmsv1.company.com 

Short Name: Server 1 

Port: 80 

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

Are these parameter correct? 

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

Done 

25 4 June 2008 

The result is a new set of the 

applications 

− General (Server 1) 

− By Node (Server 1)

Workflow in OM 

26 4 June 2008

OM WebServices 

Overview 



Agenda 

• OM Incident WS – What it provides 

• Supported WS Clients 

• OMW and OMU WS compatibility 

• OM Unix WS Server Architecture 

• Incident WSDL 

• Demo WS client implementation 

• Backup 

− WS Management Protocol Composition 

− CI WebServices (DMA) 

28 4 June 2008

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 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 

29 4 June 2008 HP Confidential

Supported WS Clients 

AXIS2 based 

WS Client 

Any WS 

client 


WS-Man based 

Web Services 

Incident 

Incident 

WS 

WS 

WS Client 

Any WS 

client 



Ext. 

Ext. 

OM UNIX 8.30 

Integration Model Service 

Product Service Extension 

WS clients 

(AXIS, .net, Wiseman, …) 

.net based 

WS Client 

Any WS 

client 

Wiseman based 

implementation 

+ Axis2 WSDL 

extension

OMW and OMU WS 

compatibility 

ISM supporting App 

Web Services 

Incident 

Incident 

WS 

WS 

Wiseman based 

implementation 


App 

Ext. 

Ext. 

Web Services 

Incident 

Incident 

WS 

WS 

OM UNIX 8.30 




Ext. 

Ext. 

HP Outsourcing 

Services 

Any WS 

client 

… 

Both OMs 

expose 

identical WSs 

NNM 

Web Services 

NNM WS 

client 

Web Services 

Incident 

Incident 

WS 

WS 

Integration Model Service 

Product Service Extension 

WS clients 

(AXIS, .net, Wiseman, …) 

OVO for 

Windows 



Ext. 

Ext. 

OM Windows 8.1 

Partners / 

Customers 

Any WS 

client 

WCF based 

implementation

OM Unix WS Server Architecture 

Web Service 

Consumers 

Legend: 

Blue: Wiseman Code 

Green: Application Code 

32 4 June 2008 

Services 

WS Management 

Servlet 

1 1 

CRUD 

& 

custom 

operations 

Resource 

Dispatcher 

1 

0..* 

Resource 

Handler 

1 

1 

Handler 

Delegate 

J2EE Server 

enumerate 

enumerate 

Enumeration 

Support 

1 

1 0..* 

enumerate 

0..* 

Resource Iterator 

Factory 

Resource 

Enumeration 

Iterator 

instantiate

OM Unix WS Server Architecture 

Web Service 

Consumers 

Services 

Legend: 

Blue: Wiseman Code 

Green: Application Code 

33 4 June 2008 

WS Management 

Servlet 

1 1 

CRUD 

& 

custom 

operations 

Resource 

Dispatcher 

1 

Resource 

Handler 

Handler 

Delegate 

J2EE Server 

0..* 

1 

1 

enumerate 

enumerate 

Enumeration 

Support 

1 

1 0..* 

0..* 

Resource Iterator 

enumerate 

Factory 

Resource 

Enumeration 

Iterator 

instantiate 

Create New 

Message 

Read Change 

Events (new,own, ..) 

Read Filtered 

Messages 

OMU Server 

MSI 

Message Manager 

(opcmsgm) 

Data Base 

(dblib)

WSDL 

https://:8444/opr-webservice/Incident.svc?wsdl 

34 4 June 2008

Example 

Below /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) 

"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"); //severity 

JAXBElement incidentElement = new JAXBElement(QNames.INCIDENT, Incident.class, null, incident); 

35EndpointReferenceType 4 June 2008 incidentEpr = client.create(incidentElement, epr); 

// read message from server and print out all attributes

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 4 June 2008

Demo WS client 

• Demo stubs for AXIS2 and Wiseman are part of the 

installation. 

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

OmWsCli -host -port -user -password [-ssl] \ 

-action 

action: enumerate [-expires ] [-filter ] 

release -context 

get -id 

create -title -emittingNode [-attr ]* 

put -id -title -severity 

subscribe [-expires ] [-filter ] 

renew -context -duration 

unsubscribe -context 

pull -context [-maxelements ] 

close -id [-id ]* 

reopen -id [-id ]* 

own -id [-id ]* 

disown -id [-id ]* 

addAnnotation -id -text 

updateAnnotation -id -annotationid -text 

deleteAnnotation -id -annotationid 

getAnnotations -id 

setCustomAttribute -id -key -text 

deleteCustomAttribute -id -key 

37 4 June 2008

OMU WebServices 

Demo

Demo WS client (2) 

optional attributes: 

[-description ] 

[-severity ] 

[-solution ] 

[-category ] 

[-subcategory ] 

[-producttype ] 

[-problemtype ] 

[-collaborationmode ] 

[-emittingci ] 

[-application ] 

[-object ] 

[-type ] 

[-creationtime ] 

[-correlationkey ] 

[-customattribute ]* 

39 4 June 2008 

EnumerationFilter attributes: 

[-severity ]* 

[-emittingnode ] 

[-category ] 


[-object ] 



[-escalationstatus ] 

[-conditionmatched ] 

[-receivedtime ] 

[-title ] 

[-customattribute ]* 

EventingFilter attributes: 

[-severity ]* 

[-emittingnode ] 

[-category ] 


[-object ] 



[-escalationstatus ] 

[-conditionmatched ] 

[-forwardtotroubleticket ] 

[-forwardtonotification ] 

[-changetype ]* 

[-title ] 

[-customattribute ]*

WS Management Protocol Composition 

Resource 

Addressing Model 

40 4 June 2008 

WS-CIM Schema Translation Integration 

WS-Management WSDL Binding for CIM 

WS-Management 

WS-Transfer WS-Enum 

Security Profiles 

XML, SOAP, WS-Addressing 

HTTPS, TCP 

WS-Eventing 

Description 

Application 

Data Transfer 

Security 

Messaging 

Transports

HP Operations 

Manager for 

Windows 

What’s new with version 8.10 

© 2007 2006 Hewlett-Packard Development Company, L.P. 


Forward-looking statements 

This document contains forward looking statements regarding 

future operations, product development, product capabilities 

and availability dates. This information is subject to substantial 

uncertainties and is subject to change at any time without 

prior notification. Statements contained in this document 

concerning these matters only reflect Hewlett Packard's 

predictions and / or expectations as of the date of this 

document and actual results and future plans of Hewlett- 

Packard may differ significantly as a result of, among other 

things, changes in product strategy resulting from 

technological, internal corporate, market and other changes. 

This is not a commitment to deliver any material, code or 

functionality and should not be relied upon in making 

purchasing decisions. 

42 HP Confidential & Subject to Change without Notice

Version 8.10 Highlights 

• User Interface enhancements 

− Web UI refresh 

− MMC Console enhancements 

• Incident Web Service API 

• Platform support extensions – including 

management server platforms 

43 4 June 2008

Web UI Refresh 

Toolbar on top 

(optionally) 

Context menus for 

services, nodes, 

policies, messages, … 

Additional skins: 

Dark and light blue 

44 4 June 2008 

Message related tools

Launch tools from Web UI 

Tools 

Tool 

Status 

45 4 June 2008 

Context Menus 

Tool Properties 

Select 

Target 

Tool Cmd

Other User Interface Enhancements 

Web UI and MMC Console: 

• Find capability 

− Nodes, Services, Policies, Tools 

− MMC console only: Graphs, Reports, Messages 

• List policies deployed on node 

Web UI 

• Severity status in node list/service map 

• Optional SVG based map 

• Graphs 

� Now all operational tasks can be performed from the Web UI 

MMC Console 

• Drag & Drop tools onto nodes 

• Assign messages to other users 

46 4 June 2008

Incident Web Service API 

• Web Services enables clients to access HPOM 

messages using standard interfaces instead of 

product-specific interfaces. 

• OM Messages are exposed as ITIL Incidents 

• Clients can be implemented using tools that 

support WS-Management, for example Wiseman. 

47 4 June 2008 

Consistent Incident Web Service for 

OM for Unix and OM for Windows

New Agent Platforms 

• Windows Server 2008 / Longhorn: 

− OMW 8.0: Hotfix for x86/x64 HTTPS agent available from 

support 

− OMW 8.10: Support for x86/x64 part of standard agent (8.52) 

• Windows Vista SP1 for x86/x64 HTTPS 

• Asianux 3.0: Support for x86/x64 

• Debian 3.1: Support for x86 

• Debian 4.0r1: both OMW 8.0 and 8.10 

• SuSE Linux 9.1/9.2/9.3: HTTPS agent on x64 

• SLES 10 SP1: 64bit HTTPS support on IA-64 

48 4 June 2008

Management Server Platform additions 

• Management Server / Console: 

− Support for installation of the management server and 

the console on Windows 2008 Server (32-bit) 

• Database: 

− Microsoft SQL Server 2005 Standard and Enterprise 

Edition; clusters with more than 2 nodes require 

Enterprise Edition 

49 4 June 2008

What’s new in OMU

What’s new in OMU

OMU 8.27 patch numbers 

Platform 

Itanium 

PA-RISC 

SPARC 

52 

All of the patches listed below as well as the 

Release Notes are planned for mid of 10/2007. 

OMU 8.27 

server 

PHSS_36831 

PHSS_36832 

ITOSOL_00601 

A.08.27 

Java GUI 

PHSS_37182 

PHSS_37183 

ITOSOL_00618 

A.08.27 

Java GUI 

repackaged for 

OMU 7.x 

N/A 

PHSS_37197 

ITOSOL_00619 

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.

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 

- 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 

- 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 of 

aborted OMU server processes

Automatic and independently restart of 

aborted OMU processes 

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

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

The restart is done according to 

OPC_RESTART_COUNT and 

OPC_RESTART_TIMEFRAME. 

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. 

56 4 June 2008

Some enhancements introduced for 

the Operational GUI with patches

Overview of enhancements introduced with 

8.27 JGUI patch 

58 

• Sorts services by Label attribute in message 

browser 

• Ability to disable history browser based 

on operator 

• Java GUI client version control

Sorts services by Label attribute 

59

Sorts services by Label attribute 

60 

Needs to be enabled, 

because it has a minor 

performance impact.

Ability to disable history browser based on 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. 

• Example: 

ovconfchg -ovrg server -ns opc -set / 

OPC_JGUI_HISTBRW_DISABLED opc_op1,opc_op2 

61

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 

• 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. 

62

Java GUI client version control 

• Determine version of connected JGUIs on management server 

• listgui extended to show version of JGUIs connected to opcuiwww 

63

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 

64

Operational UI Enhancements 

Delivered via Operational UI Patch 8.25 

•HP One Voice look & feel 

•IE 7 support 

•Message View Filtering 

•New startup options 

•Detachable windows 

•Custom filename for configuration file 

•HTML application output enhancement 

65 

4 June 2008

Operational UI - HP One Voice look & feel 

66 

JGUI 8.25 uses new HP SW appearance 

(set as default) 

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 

67 

Demo


Different GUI based types of filters 

All filters must conform to the described syntax. 

Quick 

68 

– Quick access via popup menu. 

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

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.

69 


Quick 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. 

Access: 

- Select column 

header 

- Right click for 

context menu 

- Select filter values

70 


Simple Message View Filters 

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: 

Actions -> Filtering -> Message View Filter 

-> Simple View tab

No limitation: Any criterion and rule can be configured 

if it conforms to filter syntax. 

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

71 


Advanced Message View Filters


Text format Message View Filters 

The definition of the filters above can also be written in plain 

text format opposed to GUI-based. 

Access: 

Actions -> Filtering -> Message View Filter-> Text View tab 

72

73 


HINT: 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. 

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

:/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) 

75 

Java GUI - New startup options 

CGI Perl Script 

Client 

Server 

http://server:3443/OvCgi/ 

ito_op_applet_cgi.ovpl? 

URL 

Web Server 

(Apache) ito_op_applet_cgi 

HTML ..ovpl 

ito_op.jar 

HTML 

Perl script returns 

html page with 

arguments and 

encrypted use & 

passwd 

attributes are passed 

via ENV variable 

QUERY_STRING={arguments} 

ito_for_activator.html 

Encrypt user & 

passwd with 

OvEmbCrypto utility 

in ito_op.jar lib

76 


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 

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!

77 


Decomposed JGUI 

Applet open active message browser with node filter: 

http://elisa.deu.hp.com:3443/OvCgi/ito_op_applet_cgi.ovpl?user=opc_a 

dm&passwd=opc_adm&gui.dftlayout=false&gui.msgbrw.brwpane=true&gui 

.msgbrw.filter.nodes=elisa.deu.hp.com&https=true

78 


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=6f70635f 

61646d&init2=6f70635f61646d&gui.dftlayout=true&gui.msgbrw.brwpa 

ne=true&gui.msgbrw.filter.nodes=elisa.deu.hp.com&https=true 

init1 = user 

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_adm 

6f70635f61646d

Launch OVO UI in context out of BAC 

79 

Add Context Menu Item 

Pre-processor Class: Dashboard generic URL 

Pre-processor Class: Dashboard generic URL 

URL: http://:3443/OvCgi/ito_op_filter.ovpl 

URL: http://:3443/OvCgi/ito_op_filter.ovpl 

Key: OvoNode 

Key: OvoNode 

Value: NODE.PROPS.host_dnsname 

Value: NODE.PROPS.host_dnsname 

Convert to: gui.msgbrw.filter.node 

Convert to: gui.msgbrw.filter.node 

Post-processor Class: Open window 

Post-processor Class: Open window 

Key: SLAVE_WIN 

Key: SLAVE_WIN 

Value: 0 

Value: 0

New default startup page 

80

Java GUI - HTML application output 

enhancement 

OVOU 8.25 JGUI patch covers the following ERs: 

81 

1. Enable feature centrally via XPL configuration variable. 

-> Precedence over itooprc parameter. 

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

3. Functionality also available for instruction texts. 

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

CVP Update 

Additions to Configuration Value Pack 

3.1.2 

Targeted for Nov time frame

CVP 3.1.2 New Feature Summary 

83 

4 June 2008 

• OM Agent Software 

installation 

• Full-text Search 

• Version Control System 

enhancements 

• Usability enhancements 

• Changed platform Support 

• Internal improvements

CVP 3.1.2 Agent Installation 

84 

4 June 2008 

Query with 

filter on which 

nodes you 

want to install 

the agent

CVP 3.1.2 Agent Installation (2) 

85 

4 June 2008 

Add Password 

if necessary

CVP 3.1.2 Agent Installation (3) 

86 

4 June 2008 

Installation 

Output read 

from logfile

CVP 3.1.2 Fulltext Search 

• Complete full-text search on each 

OMU configuration object: 

− can be restricted to object types (eg. 

only policies and message groups), 

but can also work on all objects at 

once 

− can be restricted to one OMU server, 

but can also search over multiple 

servers at once 

• Search uses a index, that can be 

generated periodically or on each 

change, eg. with each modify or 

delete): 

− No OMU slowdown because of index 

− Index generation can be scheduled 

87 

4 June 2008

CVP 3.1.2 Fulltext Search 

• Complete full-text search on each 

OMU configuration object: 

− can be restricted to object types (eg. 

only policies and message groups), 

but can also work on all objects at 

once 

− can be restricted to one OMU server, 

but can also search over multiple 

servers at once 

• Search uses a index, that can be 

generated periodically or on each 

change, eg. with each modify or 

delete): 

− No OMU slowdown because of index 

− Index generation can be scheduled 

88 

4 June 2008

89 

CVP 3.1.2 Version Control System 

Enhancements 

• Map multiple servers to one and the 

same CVS repository 

• Browse CVS repository to allow 

retrieval of objects removed in OMU 

• Versioning of scripts 

(eg. monitor scripts or commands) 

• Removal of versions 

4 June 2008

CVP 3.1.2 Platform support changes 

• HP-UX 11.31 

• HP-UX 11.00 will no longer be supported 

90 

4 June 2008

CVP 3.1.2 Usability Enhancements 

• The selectors for Assignment/Compare 

are enhanced with filters and the 

possibility to switch backends 

• Enhanced compare for policies, policy 

groups, applications, etc. 

• ASCII editor for scripts (monitors, 

commands, actions) inside the browser 

• When showing contents of a Group 

object, the context and path is shown 

• Role editor has selectors for easier 

selection of objects 

91 

4 June 2008

CVP 3.1.2 internal improvements 

• configurable menus/actions 

• newer jdk (1.5) 

• access.log for web server 

• script to analyze support.zip files for 

common errors 

92 

4 June 2008

Tips and Tricks

OVO Agent Install Automation 

using NEW OVO/UNIX 8 feature 

(autogrant) 

94 4 June 2008


using NEW OVO/UNIX 8 feature (autogrant) 

• The OVO Unix 8 functionality was enhanced to 

1. Improved support of HTTPS agents behind NAT sending certificaterequests. 

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

95 4 June 2008 

2. Allow automatic processing of certificate-requests for HTTPS 

agents, called autogrant. 

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 to the nodegroup.



• Prerequisite only on OVO/U server needed: 

96 4 June 2008 

1. Install OVO/U 8.27 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. 

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 

(available since July 2007) 

HPOvSext.HPOVSECCS 1.00.220 HP OpenView 

Certificate Management Server 

• ITOSOL_00598 Solaris 

• PHSS_36632 Itanium 

• PHSS_36633 PA-RISC



• Use # ovconfchg -ovrg server -edit 

[opc] 

OPC_CSA_AUTOMATION=TRUE 

[opc.opccsad] 

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 

97 4 June 2008


using NEW OVO/UNIX 8 feature 

(autogrant) 

• /tmp/pre_act.sh 

98 4 June 2008 

− 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/hosts 

Args passed to the script: 

Nodename=moses.deu.hp.com IPAddress=16.57.35.134 

PeerAddress=16.57.35.134 RequestID=a34985e8-01dd-7524-0c93cc52e1e9d8f8 

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 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= 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 

The above rules and actions are executed as part of the 

OVO HTTPS agent certificate request processing.

Demo 

Demo 

99 4 June 2008

Assign services to user profiles 

10 

0 4 June 2008

Assign services to user profiles 

• How to enable service profile assignments 

# ovconfchg -ovrg server -ns opc -set \ 

OPCSVC_CONSIDER_PROFILES TRUE 

• Then you need to restart the server processes: 

# opcsv -start 

10 

1 4 June 2008

OVO agent scalability 

improvements: 

log file monitoring and 

automatic actions 

10 

2 4 June 2008

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-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. 

10 

3 4 June 2008


• Basic concept: 

10 

4 4 June 2008 

− 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 opcle - again to avoid duplicate 

messages.


• 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 ". 

• E.G. copy /var/opt/OV/conf/ctrl/opcle.xml to opcle1.xml and change 

the lines below 

 

opcle1 

 

… 

opcle 

/opt/OV/lbin/eaagt/opcle -pol_prefix 

abc,bcd,cde 

 

START 

 

 

/opt/OV/lbin/eaagt/opcle -pol_prefix 

abc,bcd,cde 

 

 

 

10 

5 4 June 2008


• 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 

• 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 

10 

6 4 June 2008

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 

in parallel. 

Note: eaagt:MAX_NBR_PARALLEL_ACTIONS 

applies to each opcacta. 

10 

7 4 June 2008


(1/3) 


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 "-“ , so modify the 

existing opcacta.xml first. 

• Edit /var/opt/OV/conf/ctrl/opcacta.xml and change/add the lines 

below 

 

opcacta1 

 

… 

opcacta 

-1 

 

START 

 

 

/opt/OV/lbin/eaagt/opcacta -1 

 

 

 

10 

8 4 June 2008


(2/3) 


Now create additional opcacta’s. 

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

change the lines below 

 

opcacta2 

 

… 

opcacta 


 

START 

 

 


 

 

 

10 

9 4 June 2008


(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 

# 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. 

11 

0 4 June 2008

Last Minute GUI enhancement 

Save service graph layout 

Coming Soon 

(next patch) 

11 

1 4 June 2008

Service Graph 

Layout is saved 

within the session 

settings 

11 

2 4 June 2008 

New button to 

switch of the auto 

layout to do 

manual 

positioning of the 

service icons

Q & A 

11 11 

33 

4 June 

June 

2008 

2008

11 

4 

4 June 2008 

BACKUP

Backup Slides - Overview of 

enhancements introduced via 

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.11 

JGUI - 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 

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 

116

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 

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 

117

Performance Manger 8.x integration 

118 

Updated integration contrib tool with OMU 8.31 patch: 

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

Questions? 

Thank Thank you you you for for coming! 

coming!

HP Software OM Tips & Techniques

Create successful ePaper yourself

Delete template?

Save as template?