Forum Support

Why choose CLIP ?

AppLink's CLIP is the bridge between your enterprise-class event- and incident management solution - it provides a combined workflow of both ITIL management processes, a Closed Loop Incident Process.

What do you get ?

  • AppLink's CLIP provides a pre-configured out-of-the-box solution to tightly integrate e.g. HP BSM with ServiceNow or BMC Remedy: have your basic integration installed and configured in less than an hour !
  • it is a mature, robust, proven and fully supported solution that exists in the market since the first release of HP BSM OMi in 2011, with an installed base of dozens of Fortune 500 companies worldwide 
  • AppLink's CLIP is a Certified solution - it has been certified in 2015 by HP, as well as ServiceNow - in case you use AppLink's "Scoped App" for ServiceNow, you find this App in ServiceNow's App Store. 
  • Bi-directional "Closed Loop" integration
    • incident creation can be easily configured in the CLIP Web UI with support for all event attributes and CLIP's transformation and mapping capabilities
    • on initial incident creation, relevant incident attributes like the incident number and assignments are displayed in the event's forwarding tab, annotations, custom attributes
    • on event update, the incident is updated with a worklog entry summarizing all event changes, optionally, incident state, impact, urgency can be adapted
    • on incident update, the event is updated with additional annotations, custom attributes and also the forwarding tab is updated with the new incident values. Dependent on the new incident values, AppLink CLIP can manipulate the events lifecycle state, severity, priority or assignments accordingly, e.g. it closes the event if the incident is resolved   
  • Manual and automatic incident creation
  • the Web UI
    • displays the current status of all integrations and their targets
    • provides a "synchronization list view" of all events and incidents that have been created and updated by AppLink's CLIP with search capabilities to easily locate individual events or incidents. 
    • The "Drill-Down" into an event-incident pair shows all transactions, from the incident creation and bi-directional updates to closure with all details.
    • "Statistics View" shows graphical charts to allow trend analysis for incidents created
  • the Database
    • is self maintained and keeps track of all transactions and mappings for an adjustable period
    • can be used for reposting purposes by means of SQL
  • Self- and HP BSM OMi Monitoring
    • all connections are actively monitored periodically, all connection issues are logged and can lead to alarms
    • Performance metrics like processing times for create and update operations allow to pinpoint bottlenecks and support troubleshooting 
    • the "OMi Queue" Monitoring feature allows to monitor the OMi queue lengths over time with it's number of events and event updates waiting to be transferred with a display in a statistics chart. Thresholds can be configured to alarm in situations where events are queuing up in OMi.  
  • Support for external data: you have a need to incorporate external data into your integration, e.g. to determine incident assignment or priority of a new incident ? CLIP offers to incorporate external data from files, web services, etc. to be used in the incident creation and manipulation rules. 
  • Cross launch capabilities: open the related incident with one click from OMi's event forwarding tab - or vice versa, open the OMi event browser from a link from your incident ! 
  • Platform Support: AppLink's CLIP solution is available for Windows and Linux, with support for OMi 9, OMi 10, ServiceNow Berlin-Geneva, BMC 7,8,9 and NNMi 9 and 10. For details, please refer to the "User & Admin guide"

read more


Dollarphotoclub 64157724-new

CLIP 5.04.00, May 2016

We're pleased to present CLIP V5.04.00


New features:

High Availability (HA) and Scalability for CLIP

CLIP V5.04 extends previous HA capabilities by adding a new, clustered deployment model that allows for

  • High Availability : HA is achieved by replicating CLIP instances and run it in a HA cluster
  • Automatic failover: failover does not require any manual intervention
  • Automatic recovery: should a failed CLIP instance come up again, it is available instantly and automatically performs a recovery procedure
  • Scalability: all requests can be distributed among the CLIP instances of the cluster, the cluster can run in Active/Active or Active/Passive mode


CLIP for HP BSM for ServiceNow: New option for direct integration without "Update Set"

In former versions, CLIP for HP BSM required the upload of a ServiceNow "Update Set" or the installation of AppLink's "Scoped App" for CLIP from the ServiceNow AppStore. These contain the Web Service endpoint, transform map, business rules, scripts, menus etc. used by CLIP to create incidents and trigger incident updates to be reported back to HP BSM.

Even though the use of the "Update Set" / "Scoped App" is still the recommended option for the integration, CLIP V5.04 now offers a "direct" integration into ServiceNow without use of an "Update Set" or "Scoped App"– incidents can be created directly in the ServiceNow Incidents table. Using this mode, CLIP actively polls for changes of incidents to update the OMi events accordingly.

This option can be used if

  • company policies refuse to apply additional configurations to your ServiceNow instance for the integration into HP BSM 
  • a more simple approach is favored - no maintenance is necessary on ServiceNow release changes


CLIP for HP BSM for Salesforce: New integration to RemedyForce and the platform

CLIP V5.04 includes an integration module to integrate with the platform.  Utilizing the new CLIP module for, CLIP provides an out-of-the-box standard integrations into BMC RemedyForce.


Extended CLIP variable scopes

CLIP supports extended access to attributes of related events and incidents in the rules to update events and incidents. Example use cases for this feature include:

  • on incident creation, CLIP can auto assign the event to OMi operators and groups dependant of the submission type and only after initial submission by evaluating event and incident attributes
  • update the incident state dependant dependant of event state and other event attributes and the current incident state by lookup of the current incident state, e.g. an incident can be closed if the event is closed but only if the current incident state is "New" so it was not yet assigned 



CLIP for HP BSM OMi: CLIP can do various kind of OMi event manipulations to show data of an related incident in the "forwarding tab", custom attributes, annotations, change state, severity and priority etc. The current CLIP version also allows to auto assign an event to an OMi user and group using the attributes "assigned_user" and "assigned_group" in ClipConfig.xml.


For changed features and issues fixed, please refer to the ReleaseNotes in the "Downloads" area under "Information & Documentation" as a registered and logged in user.


Go to top

© AppLink GmbH 2016 - Legal Notice