![]() ![]() A Business Rule can check for this field if it contains a GUID value. This is important so that the incident can be identified easily as originating from OMi. The incident table can be modified to include the OMi event ID field and be transformed similarly as the description example as shown above. ![]() The target is set for the incident table to match on the target field “description”. Here is an example of a transformation map source field for “description”. A ServiceNow Business Rule can also be applied to further shape the event data before it's inserted into the incident table.Īn example of an import table containing the event data fields we want to transform is below: In ServiceNow, it's good practice to have an import table where a transformation map is executed, thereby transforming the forwarded event values to matching values in the ServiceNow incident table. With this sample filter shown here, the selection is made when an event matches the filter as a critical event with any lifecycle state that has the priority either set to highest, high, or unknown will be forwarded. As an additional option, the integration allows you to right-click on an event and manually transfer it to ServiceNow for incident creation and synchronisation. These filters are used to select and automate events for forwarding and synchronisation with the Connected Server. Once the OMi connected server to ServiceNow is enabled, Event Forwarding rules can be tailored to use simple event filtering. Additionally, you will need an account in OMi in order for ServiceNow to interact with OMi WebServices. You will need to create an account in ServiceNow and enable the "Web service access" role to be allowed to make Web service API protocol calls. There are some examples provided one in particular is the "LogFile Adapter", and with the use of the OMi extensibility guide, these examples can easily translate into useful real-world cases. ![]() The script is set under the Connected Servers option in the managed scripts. Generally speaking, someone who has an intermediate breadth in JavaScripting can sufficiently develop a connector script. It requires a little groovy script programming knowledge. The integration with ServiceNow is relatively straightforward and simple. The possibilities are endless and the GUI is customisable-and as for the designs provided out-of-the-box, they are a fully featured event and service model, driven to work well from the operations and support personnel perspectives. It is robust in design and suitable for every known event and service model situation possible. OMi has been tested over time, built on a firm foundation. In each case where JDS has provided OMi to ServiceNow integration, it has proven successful and satisfying for our customers. In most of these cases, the requirement was also to integrate ServiceNow-a request that has been growing in popularity. We have delivered Micro Focus solutions and migrated "Operations Manager for Windows" (OMW) to the innovative new OMi for a number of customers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |