Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Operations Manager i10.62

Develop > Integrate external event processes > Integrate an external event processing service defined by a WSDL

Integrate an external event processing service defined by a WSDL

You can integrate an external event processing system that exposes its interfaces using a standard web service and a WSDL (Web Services Description Language) description using the steps described in this section.

HPE recommends that you implement the integration in stages that correspond to the four defined forwarding types. Each stage builds upon the previous to create a more fully functional integration:

All forwarding types. You must implement the Groovy script init() method for all forwarding types. The method is called whenever the Groovy script is initialized.
Notify. This is the minimum and requires implementing the forwardEvent() method in the Groovy script to forward events to the target server.
Notify and Update. This requires implementing the forwardChange() method in the Groovy script to forward changes to the target server.
Synchronize. This requires implementing the receiveChange() method in the Groovy script to receive changes from the target server.

The target server must be able to call the OPR Event Synchronization Web Service to post the changes to OMi when a change occurs on the target server. The payload of the web service request is passed to the Groovy script receiveChange() method for interpretation. The web service call may be of any type, for example SOAP or REST based.
Synchronize and Transfer Control. No additional Groovy script methods are required for this implementation.
Optional. Ping support. This requires implementing the Groovy script ping() method.

For more information about Groovy script methods, see Groovy script methods.

To support the other forwarding types, the appropriate methods in the Groovy script must be implemented in a similar fashion as the forwardEvent() method.

The following configuration steps are required to implement an integration for the notify forwarding type:

Generate Java code from WSDL

The following example uses Apache Axis to generate Java code from a WSDL file.

Download and install the following prerequisites:

Java JDK 1.7 or later

Apache Axis2

Apache Ant 1.7
Create a working directory, for example integration.
Copy the WSDL file to that directory, for example integration/service.wsdl.
Create a directory for the generated code, for example integration/gen.
Change to the gen directory.
Run Apache Axis2 and generate the code from the WSDL file:

wsdl2java -uri file:../service.wsdl

Edit the generated build.xml file to correctly set the classpath in the manifest of the JAR file:

Open the build.xml file in a text editor.
Locate the Ant target jar.client.

Add the following Ant path declaration just after the path declaration axis2.class.path at the beginning of the file:

<path id="axis2.client.class.path">
   <fileset dir="${axis2.home}">
      <include name="lib/*.jar"/>
   </fileset>
</path>
<pathconvert property="axis2.client.class.path.string" 
             pathsep=" ">
   <path refid="axis2.client.class.path” />
   <flattenmapper />
</pathconvert>

In the jar task, add the following manifest directive to specify the classpath in the JAR file manifest.

As there are many Axis2 JAR files needed at execution time, it is simpler if the manifest of the generated JAR file is able to resolve the dependencies at runtime.

<jar destfile="${lib}/${name}-test-client.jar">
   <fileset dir="${classes}">
      <exclude name="**/META-INF/*.*"/>
      <exclude name="**/lib/*.*"/>
      <exclude name="**/*MessageReceiver.class"/>
      <exclude name="**/*Skeleton.class"/>
   </fileset>
   <manifest>
      <attribute name="Created-By" 
                 value="Developer name goes here" />
      <attribute name="Class-Path" 
                 value="${axis2.client.class.path.string}" />
   </manifest>
</jar>

Save the changed build.xml file.
Run ant at the command line. This builds the JAR file needed to access the service. The output is available the build/lib directory.

Configure the external event processing application as a connected server

Synchronizing events and event changes between OMi and the external event processing application depends on OMi forwarding events to the external event processing application. To achieve this, you must configure the external event processing application as a target connected server in the Connected Servers manager.

When you configure the connected server, you also create the Groovy script to access the service.

Navigate to the Connected Servers manager:

Administration > Setup and Maintenance > Connected Servers

Alternatively, click Connected Servers.
In the central Connected Servers pane, click New and select External Event Processing. Alternatively, you can click New in the External Event Processing area in the right pane.

The Create External Event Processing Server panel opens.
In the General section, enter a display label, an identifier (a unique internal name if you want to replace the automatically generated one), and, optionally, a description of the connection being specified.
In the Server Properties section, complete the following information:
1. Enter the fully qualified domain name of the host system of the external event processing server.
2. From the drop-down list, select the CI type of the CI that will represent the external event processing server in the RTSM.
3. Optional. Customize the way events and change notifications are delivered to this server by using Advanced Delivery Options:
In the Integration Type section, complete the following information:
1. Select Call script adapter to establish the connection with the external server type.
2. Click Manage Scripts to open the Event Forwarding Script Configuration dialog box. Provide the following information:
  1. Select the sample:LogfileAdapter Groovy script and click Duplicate Item to create a copy of the script.
  2. In the General tab of the script editor, rename the copy to TestAdapter.
  3. In the Script tab, add calls to the classes in the Axis2 generated JAR file:
    - You must first call the forwardEvent() script method. You need to create a target object for a given event.
    - The Axis2 code generator generated a stub class. You need to construct this class, and then, by using the event passed in the args to forwardEvent(), create an external event.
    - Each service will be different, so there are no specifics to supply here. When the external event is successfully created, the externalID is set in the args before the method is exited.
  4. In the Advanced tab, add all JAR files required by the TestAdapter script.
  5. Click OK to save the TestAdapter script, and then close the Event Forwarding Scripts Configuration dialog box.
3. Specify a maximum transaction time value (the time limit for the execution of the script). The default value is 60 seconds.
In the Outgoing Connection section, complete the following information:
1. For event forwarding and change notification, enter the user credentials (user name and password) and the port number required to access the external server. The default port value is automatically inserted and can be restored by clicking Set default port.
2. Optional. If you are using secure communication (default), make sure that the Use secure HTTP check box is selected, and then apply a certificate by clicking import the certificate and using one of the following methods:
  - Connect and Import from Server: Retrieves a certificate from the host system specified in this server connection.
  - Import from File: Opens the file browser and enables you to navigate to and specify a Base64 Encoded X.509 certificate file for the server connection.
3. Select the Enable synchronize and transfer control check box to be able to transfer responsibility to the external event processing server.
  
  When the Synchronize and Transfer Control flag is set, an OMi operator is able to transfer ownership of the event to the target connected server. If the flag is not set, the Synchronize and Transfer Control option does not appear in the list of forwarding types when configuring forwarding rules.
  
  Note If the Enable synchronize and transfer control check box is not selected for any target connected server, the Transfer Control option does not appear at all in the Event Browser context menu. If a specific server is configured without the Enable synchronize and transfer control option being selected, that server is not available in the Event Browser context menu as a server to which you can transfer ownership.
In the Incoming Connection section, select the Accept event changes from external event processing server check box to enable the external event processing server to update events on the OMi server from which the event was forwarded.

Note If Enable synchronize and transfer control was previously selected, the Accept event changes from external event processing server option is assumed and cannot be disabled.

Specify the credentials for the OMi integration user to enable the external event processing server to authenticate with OMi and synchronize back external event changes.
In the Event Drilldown section, complete the following information:
1. Enter the fully qualified domain name of the host system of the external event processing server and the port number used for drilldown. The default port value is automatically inserted and can be restored by clicking Set default port.
2. Optional. Select the Use secure HTTP check box for secure communication.
In the Test Connection section, click Run Test to check that the specified connection attributes are correct. If an error message is displayed, correct the connection information, and retest the connection.
Make sure that the Activate after save check box is selected if you want to enable the server connection immediately.
Click Create. The target external event processing server appears in the list of connected servers.

Send Help Center feedback