Most integrations with Openview Operations (OVO, in short) to monitor and manage the events involves feeding event data to OVO. As explained in Mark Secrist's excellent column on integrating JMX notifications to OVO, you have a number of options to do so: use of SNMP traps, through opcmsg command or C API, or using OpenView Interconnect (OVI). Each option has its own pros and cons and you must do a careful analysis in the context of your situation before running with a particular approach. Thankfully Mark's column presents advantages and disadvantages of each approach as well and makes your job easy.

This is not to say that you will find answers to all your questions (can any how-to guide ever make that promise?). A number of additional points became apparent to us while discussing the exact same topic with a customer who wanted to feed their JMX notifications to OVO and who had strict perforamnce requirements. I list them below:

• Not all options are available to you in every situation. For example the opcmsg interface, either using the command line or C API, is available to only those programs that run on a "managed node" (ie; a machine that hosts OVO Agent), whereas OVI can be used by any network connected program.
• There exists a Java version of the opcmsg API. This is implemented as a JNI wrapper around C API. In fact OVI uses this Java API.
• Local agent reduces network traffic. Integration through opcmsg interface means that the message will be processed by the local OVO agent, possibly applying filtering rules and reducing network traffic.
• All communication between OVO agent (HTTPS agents only) and OVO server can be secured using OVO mechanisms. Using OVI or SNMP traps to transport the notifications may require additional setup for security (assuming security is improtant to you in this context).

The additional insights based on the above points wilol come handy when you design you own integration with OVO.