Web Services Server connector
Use the Web Services Server connector to listen for and accept REST, SOAP, and simple HTTP requests in real time and initiate Dell Boomi Integration processes.
When a process containing this connector is deployed to an Atom, the Atom’s internal web server listens for documents based on configurations made in the Web Services Server operation or, if applicable, the API component. You can view the status of deployed web service listener processes and API components in the Listeners panel in. In that panel you can also pause, resume, and restart listeners.
When possible, the technical details of this connector, such as SOAP headers, error handling, HTTPS authentication and XML syntax, are abstracted to simplify your implementation. The XML or JSON profile houses all raw data elements and stands as the main document type for the start and end of an API process.
For more information about the different options and use cases that apply when using this connector, see the Services Enablement topic.
Web Services SOAP Client connector
HTTP Client connector
Configuring a connector to listen for client applications requires the setup of two components:
Web Services Server operation
The listen connection is managed at the Atom level. The connection is not configurable within an individual process. You can review configuration requirements for the Atom's shared web server.
This connector design provides reusable components across Atoms and the ability to launch unique operations and URLs for different process actions. When an API is published for request handling, you can develop a process to interact with virtually any system using other connectors in our library.
The Allow Simultaneous Executions process option is respected for real-time processes using the Web Services Server connector. If a process is deployed with Allow Simultaneous Executions turned off, the client receives an HTTP 500 error when attempting to invoke the process while it is running.
Generally, APIs that you publish can accept:
Multipart SOAP attachments
Arbitrary XML definitions
Other structured formats such as flat file, CSV and JSON
The accepted structure is dependent upon the input and output types defined in the Configuration of web service listen connectors topic.
This connector has no pre-defined tracked properties. See the topic Adding tracked fields to a connector operation to learn how to add a custom tracked field.
- Related Concepts
- Related References