Jitterbit connectors
Use connectors to integrate BMC applications with other BMC or third-party applications. Learn more about Connector availability and types.
Connector availability and types
Connectors integrate BMC applications with third-party applications to share data between the two applications and perform tasks.
BMC Helix iPaaS provide connectors on multiple platforms for a vast number of applications. For more details, see list of all available connectors.
Connectors are available based on your subscriptions:
- BMC exclusive— Exclusive connectors developed by BMC on Jitterbit Harmony that are available to BMC Helix iPaaS customers only.
- BMC and other third-party connectors, powered by Jitterbit — Connectors developed for BMC and other third-party applications on the Jitterbit Harmony platform that are available to all Jitterbit customers.
Connector types
Connectors are also available to read and write data to and from long-term and short-term storage, and databases.
Connectors are documented individually, but can be classified by their use. Connectors are classified into the following types:
Applications—Connectors for different types of applications. These connectors are further classified into:
API — Connector used in conjunction with a Jitterbit Custom API and are preconfigured endpoints whose associated activities include Request and Response activities. Schemas are defined by files provided by the user.
The API connector used in conjunction with a Jitterbit Custom API, is preconfigured to expose an operation or set of operations as a consumable REST endpoint. Connectors are available for service based requests like HTTP/REST or SOAP services to send or receive data using standard methods such as GET, POST, PUT, or DELETE.Service based — These connectors are used with a service that provides the metadata needed for the connection and activities. In the case of HTTP/REST services, you research and test the service, and then you provide the schemas within each activity. In the case of SOAP services, this metadata is provided in a Web Service Definition Language (WSDL) file and schemas are queried from the service.
Short-term storage — These connectors are typically used when you want to store files temporarily for use in a downstream operation. Associated activities include Read and Write activities. However, written files cannot be relied on to be present after operation execution, except Local Storage with some additional configuration. Schemas are defined by files provided by the user.
Long-term storage — These connectors are typically used for long-term or permanent storage of files. Associated activities include Read and Write activities. Schemas are defined by files provided by the user.
Database — These connectors can also be considered a long-term storage connector but offers more functionality than the other long-term storage connectors. The Database connector is used to access relational database management systems (RDMS) using third-party drivers. Activities include Query, Insert, and Update (Jitterbit Harmony also supports an Upsert activity through a combination of these). Schemas are queried from the database using the chosen driver.
Related topic