The Jitterbit Harmony HTTP Connector establishes access to an HTTP server through a RESTful web service (REST API).
The HTTP connector provides an interface for creating an HTTP connection, the foundation used for generating instances of HTTP activities. These activities, once configured, interact with an HTTP server through the connection.
The HTTP connector is accessed from the design component palette's Connections tab (see Design Component Palette).
A beta version of Jitterbit's HTTP v2 (Beta) connector (an application connector) is also available. For more information, see REST-based Connector Considerations.
This connector is used to first configure an HTTP connection. Activity types associated with that connection are then used to create instances of activities that can be used as sources (to provide data) or targets (to consume data) in an operation or a script.
Whether an activity instance can be used as a source or a target depends on whether the web service requires a structured request or returns a structured response. Each activity instance is configured with request and response schemas using user-provided custom schemas.
Together, a specific HTTP connection and its activities (GET, PUT, POST, DELETE, or Custom) are referred to as an HTTP endpoint:
If you experience issues with the HTTP connector, these troubleshooting steps are recommended:
Ensure the HTTP connection is successful by using the Test button in the configuration screen. If the connection is not successful, the error returned may provide an indication as to the problem.
Check the operation logs for any information written during execution of the operation.
Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.
If using Private Agents, you can check the agent logs for more information.