Skip to main content

IMPORTANT - Product End of Life Statement - IMPORTANT

Request RE, Survey, and Calendar 1.5 Support Ending December 31, 2020
Contact Kinetic Data Support with Questions
Kinetic Community

Unleashing the Power of Kinetic Bridging

Explores Kinetic Bridging, a strategy for utilizing distributed and disparate data systems within Kinetic Request.  Through Kinetic Bridging, Kinetic Request can populate service items with live, dynamic data from BMC Remedy, Active Directory, custom database solutions, or just about any other data storage solution.

TopicsScreenshot - Unleashing the Power of Kinetic Bridges.png

  • What is Kinetic Bridging?
  • Architecture
  • Strategy
  • Example
    • Installing a bridge
    • Defining an abstract model
    • Configuring the model mappings
    • Leveraging the model in a service item
  • Benefits
    • Access
    • Configuration Driven
    • Portability


Your data is distributed and stored in many different formats.  Kinetic Bridging is a strategy for providing federated access to this information through Kinetic Request.  At the core, Kinetic Bridging defines data structures and attributes independently from back end implementation.  Data mappings are configured and used to translate these abstract structures into their functional representations.

On the front end, Kinetic Request developers can leverage the abstract data models without the need for understanding the technical implementation.  When a service item is accessed, Kinetic Request passes the abstract structure and data mapping information to a Kinetic Bridge, which is responsible for the actual interaction with a data source.

Kinetic Bridges are developed as simple Java web applications.  These applications accept a common request format, interact with the data source, and respond with a common response format.

Similar to how Kinetic Task opened up the back end to interacting with distributed and disparate data sources, Kinetic Bridging opens up the front end.


Resources pending the formal release of Kinetic Request 5.1.