Accomplishing this abstraction is a two step process:
- Define a set of abstract structures (for example, specifying that a "Person" has a "First Name" and "Last Name") and mappings (for example, mapping "Person" to the "CTM:People" form on an BMCBMC© Remedy server, and the "fName" and "GivenName" fields to "First Name" and "Last Name").
- Register a Kinetic Bridge, which is a simple web application that accepts a common request interface, interacts with the desired data source, and respond with a common response format.
Once these two simple steps have been completed, Kinetic applications such as Kinetic Request can be configured to retrieve and leverage any abstracted data without the need for custom programming or integrations.
If you are just getting started with Kinetic Bridging and want to jump right in, see the Getting Started guide. Otherwise, you can read more about Kinetic Bridging in the Documentation section, or download existing Bridges from the Resources section.
- Bridging provide access to live, distributed data from disparate technologies (BMC© Remedy, Active Directory, cloud solutions, custom database applications, etc).
- Bridging is configuration driven.
- Environment migrations are only data
- There is a clear separation of roles (a Kinetic Request developer does not need to be familiar with Active Directory to leverage data from an Active Directory server)
- The Bridge and the structure/mapping definitions need to be set up once, and can be used 1000 times
- Bridging encourages portability.
- Applications that leverage Kinetic Bridging reference abstract bridge models, so changing to a new data source only requires the updating of relevant mappings
- Generic samples or templates can be easily distributed that refer to common bridge model abstractions and these examples don't require any additional development or customization