Skip to Content

Turn your connections into holiday cash with our new Customer Referral Program! Learn more

✕

SOAP connector for Jitterbit Integration Studio

Summary

The SOAP connector establishes connections via the Simple Object Access Protocol, SOAP.

The SOAP connector provides an interface where users can insert input such as a Web Services Description Language (WSDL) file to create a SOAP connection, the foundation used for generating instances of SOAP activities. These activities, once configured, interact with the web service through the connection.

The SOAP connector is accessed from the design component palette's Project endpoints and connectors tab (see Design component palette).

Connector overview

This connector is used to first configure a SOAP connection. Activity types associated with that connection are then used to create instances of activities that are intended to be used as sources (to provide data in an operation) or targets (to consume data in an operation).

Together, a specific SOAP connection and its activities are referred to as a SOAP endpoint:

SOAP activity types

Note

The activities available change depending on the choices made when configuring the connector. The ones shown in the image above are an example. Your connector may show different activities.

Note

This connector is a native Integration Studio connector, which may be referred to by Jitterbit when communicating changes made to connectors. The release schedule for native Integration Studio connectors is based on the cadence of Harmony portal web applications.

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.

  5. For additional troubleshooting considerations, see Operation troubleshooting.

Additional resources

The following Jitterbit variables are provided specifically for use with SOAP endpoints:

  • jitterbit.web_service.last_fault
  • 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.