Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
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 |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Event Synchronization Web Service Interface
- Forward events and event changes from OPR client
- Synchronize event changes back from external client
- Event attributes that support back synchronization
- Event update: Logfile Adapter examples
- Event change creation: Logfile Adapter examples
- Event update to event_list example
- Event Submit Examples
- Event change creation for event_change_list examples
- Event synchronization web service troubleshooting
Event update: Logfile Adapter examples
Note The examples showing event updates in this section are specific to the Logfile Adapter (the sample Groovy script adapter provided with the product), and would work only for the Logfile Adapter, or for accessing the Event Synchronization Web Service directly without having a Groovy script configured for the target connected server.
You can submit event changes with an event update. The HTTP method in this case is PUT, and the expected payload for the Logfile Adapter is an OprEvent
. Each Groovy script adapter defines its own expected payload, so the expected payload would be different for other Groovy script adapters.
The Event Synchronization Web Service supports sending multiple properties in a single payload. The following examples each show just one changed property, with the exception of the last sample, which shows two changed properties (see Change Multiple Properties in One Call).
You can send test payloads to the Event Synchronization Web Service using the REST web service command-line utility RestWsUtil
, supplied with the product. When using the utility, make sure that the event you are trying to update was first forwarded to the target connected server you are using to authenticate with the Event Synchronization Web Service.
For details about the RestWsUtil
command-line utility, see RestWsUtil Command-Line Interface.
An example call for an event update is shown below. The following sample call for an event update is for a connected server named logger
with password set to Password1
, and attempts to update an event with the ID 0695624b-93fa-40b1-8b0fc9b4ea07a4ec
. The sample call looks like this:
RestWsUtil -update update.xml-url "https://<server.example.com>/opr-gateway/rest/9.10/synchronization/event/0695624b-93fa-40b1-8b0fc9b4ea07a4ec" -username logger -password Password1 -verbose
The samples that follow show possible XML payloads for the call. The payloads are contained in the update.xml
file referenced in the call to the RestWsUtil
command-line utility.
Note An Event REST WS sample is located at:
<OMi_HOME>/opr/examples/event-ws
This can be compiled and packaged into a war file for deployment into a J2EE container. See the README.txt in this directory for instructions on how to build this webapp and deploy it for testing.
A Event REST WS template is located at:
<OMi_HOME>/opr/examples/synchronization-ws
This can be used as a starting point for developers who want to develop their own Event Synchronization web service. See the README.txt in this directory for instructions on how to build this webapp. The "TODO" sections must be completed by the developer.
The Event Synchronization Web Service supports only the set or unset operations for the description of an event. Insert, update, or delete operations are not supported.
Example: Set the Description
Here is a sample payload to set the description:
<event xmlns="http://www.hp.com/2009/software/opr/data_model"> <description>This is a new description</description> </event>
Example: Unset the Description
Here is a sample payload to unset the description:
<event xmlns="http://www.hp.com/2009/software/opr/data_model"> <description/> </event>
The Event Synchronization Web Service supports only the set or unset operations for the title of an event. Insert, update, or delete operations are not supported.
Example: Set the Title
Here is a sample payload to set the title:
<event xmlns="http://www.hp.com/2009/software/opr/data_model"> <title>This is a new title</title> </event>
Example: Unset the Title
Here is a sample payload to unset the title:
<event xmlns="http://www.hp.com/2009/software/opr/data_model"> <title/> </event>
The Event Synchronization Web Service supports sending multiple properties in a single payload. Here we show just two changed properties.
Example: Set Title and Description
The title and description can be set in a single call. The order of the attributes is unimportant and attributes not specified do not affect the current values.
Here is a sample payload to set the event title and description in a single update call:
<event xmlns="http://www.hp.com/2009/software/opr/data_model"> <title>This is a new title</title> <description>This is a new description</description> </event>
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-asm@hpe.com.
Help Topic ID:
Product:
Topic Title:
Feedback: