Skip to Content

SOAP Connector

Summary

The SOAP connector for Jitterbit Harmony Cloud Studio provides an interface for entering user-provided input such as a Web Services Description Language (WSDL) file to create a SOAP connection. That connection provides the foundation to configure associated SOAP connector activities that interact with the connection. Together, a specific SOAP connection and its activities are referred to as a SOAP endpoint.

Connector Overview

This connector is used to first configure a SOAP connection, establishing access to a SOAP web service, and then used to configure one or more SOAP activities associated with that connection as a source or target within an operation. The specific activities that are available depend on the SOAP methods selected during configuration of the SOAP connection.

Whether the activity can be used as a source or a target in an operation depends on the specific web service and the request and response structures, if present. For more information about what determines if an activity can be used as a source or target, see Parts of an Operation in Operation Creation and Configuration.

Accessing the Connector

The SOAP connector is accessed from the design component palette's Connections tab (see Design Component Palette).

soap activities

Web Service Jitterbit Variables

Certain Jitterbit variables are provided specifically for use with SOAP endpoints, including these:

  • jitterbit.web_service_call.max_redirs
  • jitterbit.web_service_call.number_of_retries
  • jitterbit.web_service_call.retry_wait_seconds
  • jitterbit.web_service_call.ssl_cert_id
  • jitterbit.web_service_call.sync_response
  • jitterbit.web_service_call.time_out

For details on using these variables, see Web Service Jitterbit Variables.

Troubleshooting

If you experience issues with the SOAP connector, these troubleshooting steps are recommended:

  1. Ensure the SOAP 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.

  2. Check the operation logs for any information written during execution of the operation.

  3. Enable operation debug logging (for Cloud Agents or for Private Agents) to generate additional log files and data.

  4. If using Private Agents, you can check the agent logs for more information.