- What is Kinetic Bridging?
- Installing a bridge
- Defining an abstract model
- Configuring the model mappings
- Leveraging the model in a service item
- Configuration Driven
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.