Plugins

Overview

The Kinetic Platform can use plugins to connect to just about any system. Several Bridges, Handlers and Source are prebuilt and available from Kinetic Data. We use plugins to do common CRUD (create, read, update and delete) operations and much more.

Bridges

Kinetic Platform developers use bridge plugins to get data from source systems. A source system can be a SQL database or a Saas system with a rest api. If it connects to the net a bridge adapter can be written to connect Kinetic to it. Bridges are executed by a Kinetic Agent.

Handlers and Agent Handlers

Handlers are snippets of Ruby code that are executed by Workflow or an Agent. Handlers can be written to execute all of the CRUD operation. Using Handlers, Kinetic Platform developers are able to do all the fun things only Kinetic allows them to do. If you're looking to accomplish a task in a system and the system has an API that allows you to accomplish the task then Kinetic Platform can be used to automate the process.

Plugin configuration

Bridge, Agent Handlers and Sources are selected from the adapters and handlers that are deployed to the Agent. Handlers are imported and exposed to Workflow for use with Trees and Routines.

Bridge configuration

A Bridge is an instance of a bridge adapter class. A bridge adapter is a Java project that is deployed to an Agent. Each bridge adapter will have its own configuration fields. Normally, the configuration field are the details required to connect to the source system.

📘

New Bridge

• The Agent selected will save the instance of the bridge adapter. Choose an Agent from the dropdown. Additional Agents are added through Space > Settings > Platform Components.
• Each Agent will have its own Adapter Classes. New bridge adapters are added to the agent by placing a jar file into the deployed Agent's lib directory and restarting the server.

Handlers

Workflow uses handlers to preform all sorts of useful task. One of the main uses of Handlers are for CRUD operations to source systems. Handlers can also be used to manipulate data, send out emails and start processes. Once a Handler is imported into the platform they will required their own configuration called info values. The configuration normally takes the details required to connect to a source system. Handler may also have additional info values that are used in the processing of the handler.

📘

Import Handler

From the Kinetic Platform consoles Handlers are added to the space.

• Import the Handler by dragging or selecting the handler zipped file from you local machine.
• Import a handler by providing a URL to a zipped handler.

Agent Handlers

Agent Handlers are similar to standard Handlers in that they are snippets of Ruby code. The large difference between standard Handlers and Agent Handlers are the Handler executions. Standard Handlers are executed via Workflow where Agent Handlers are executed via an Agent.

📘

New Agent Handlers

• The Agent selected will save the instance of the agent handler. Choose an Agent from the dropdown. Additional Agents are added through Space > Settings > Platform Components.
• Each Agent will have its own Agent Handlers. New agent handlers are added to the agent by placing a jar file into the deployed Agent's lib directory and restarting the server.