SOAP

Core meaning

SOAP (Simple Object Access Protocol) is a protocol specification for exchanging structured information between software systems using XML-based messages, typically over HTTP, HTTPS, or other transport protocols. It defines a formal message structure, standard encoding rules, and a processing model so that different applications and platforms can interoperate in a predictable way.

SOAP messages usually consist of:

– An XML envelope that identifies the message and its content
– An optional header for metadata (such as security, routing, or transaction data)
– A body that carries the operation request or response payload

Use in manufacturing and enterprise integrations

In industrial and regulated environments, SOAP is commonly used as one of the web service mechanisms for system-to-system integration, including:

– MES–ERP integration for exchanging production orders, confirmations, material movements, and inventory data
– Communication between manufacturing systems (MES, LIMS, QMS, WMS) and corporate or cloud applications
– Service-oriented architectures where enterprise service buses (ESB) mediate SOAP-based messages

Because SOAP has a well-defined contract approach (typically via WSDL), it is often used where stable, strongly typed interfaces and explicit change control are required.

Characteristics and boundaries

SOAP commonly includes:

– **XML-only message format**: Payloads and control data are represented in XML.
– **Explicit service contracts**: Interfaces are often described using WSDL (Web Services Description Language).
– **Extensibility via headers**: Security, transactions, and reliability features are typically implemented in SOAP headers (e.g., WS-* specifications).
– **Transport independence**: While often used over HTTP/HTTPS, SOAP can run over other transports (such as JMS or SMTP).

SOAP does **not** refer to:

– The REST architectural style or RESTful APIs, which do not rely on a specific envelope protocol.
– General XML data exchange without the SOAP envelope or processing rules.

Common confusion and related terms

– **SOAP vs REST**: SOAP is a protocol with a formal envelope and processing rules. REST is an architectural style for building APIs, frequently using JSON or XML over HTTP without the SOAP envelope.
– **SOAP vs generic web services**: “Web service” is a broad term. SOAP is one specific, standards-based web service protocol; others use REST/JSON, gRPC, or custom approaches.
– **SOAP vs XML over HTTP**: Simply posting XML to an HTTP endpoint does not make it SOAP; SOAP requires a compliant envelope and processing model.

MES–ERP integration context

In the context of MES–ERP integration, SOAP-based web services commonly refer to:

– Exposed ERP or MES endpoints described via WSDL that accept SOAP requests for operations such as order creation, posting confirmations, or retrieving master data
– Middleware or ESB/iPaaS platforms that consume and produce SOAP messages to bridge legacy systems and newer REST or message-queue interfaces

In regulated manufacturing, SOAP interfaces are often subject to formal change control, documentation, and testing because their contracts and payload structures are tightly defined and versioned.