Supported web service standards

IBM® Business Process Manager Version 8.5 supports a variety of web service industry standards that can be configured and used through the Business Process Model and Notation (BPMN) or Service Component Architecture (SCA) programming models (JAX-WS export and import web services bindings within a module, in the case of IBM Business Process Manager Advanced).

Note: The tables in this topic are specific to IBM Business Process Manager Version 8.5 and earlier versions of related products.

For some support (for example, the Web Services Notification (WS-Notification) specification), the specific capability is listed as Not supported because it is not present in the BPMN or SCA supplied programming model. However, for IBM Business Process Manager Advanced, the capability is present and available to be used in the underlying application server (WebSphere® Application Server 8.5) with its supplied programming model and tools accessible by way of Integration Designer perspectives. These entries are marked in the following tables with an asterisk (*).

For a complete list of web services supported in WebSphere Application Server 8.5, see Specifications and API documentation.

Policy set support: Beginning in Version 8.5, policy sets could be added to a web services server configuration or an outbound or inbound web service integration component. Policy sets include policy types to create a complete set of policies (or properties) that are available to be configured within that policy set. Policy types are a set of related policies (or properties) that are supported by a particular Quality of Service (QoS). Examples of policy types included in these standards are WS-Security and WS-Addressing. An example of a policy set is the Username WSSecurity default policy set which is one of the default policy sets shipped with WebSphere Application Server. Policy sets are not included in these standards.

Note: The Version 8.5 column in the tables lists the latest specification level that the product supports. However, support for specifications is compatible with earlier versions of the product; the Version 8.5 product supports all specifications that are listed for Version 6.2 through Version 8.5. The word New appears beside the version where the specification was first supported. For example, Version 8.0 was the first time JAX-WS 2.2 was supported.

Web services

The web services standards are listed in Table 1:

Table 1. Supported web service industry standards
Specification or API IBM Business Process Manager Advanced Version 8.5 IBM Business Process Manager Standard 8.5 IBM Business Process Manager Advanced Version 8.0 IBM Business Process Manager Advanced 7.5 and WebSphere Process Server 7.0 IBM Business Process Manager Standard 8.0 and 7.5 WebSphere Process Server 6.2

Java API for XML Web Services (JAX-WS) specification

  • Not supported for IBM Business Process Manager Standard V7.5.
  • For IBM Business Process Manager Standard V8.0, use JAX-WS 2.2 for outbound web services. - New
Web Services Interoperability (WS-I) Reliable Secure Profile (RSP)
Note: Before WS-I RSP, the specification was named Reliable Asynchronous Messaging Profile (RAMP).
  • Not supported
  • RAMP 1.0
  • RAMP 1.0
  • RAMP 1.0

SOAP

SOAP with Attachments API for Java (SAAJ) Specification

  • Not supported
  • Not supported

SOAP over Java Message Service (SOAP over JMS)

  • Not supported in the JAX-WS binding
  • If you want to use SOAP over JMS, use the JAX-RPC binding as your communications protocol.
  • Not supported
  • Not supported in the JAX-WS binding
  • If you want to use SOAP over JMS, use the JAX-RPC binding as your communications protocol.
  • Not supported in the JAX-WS binding
  • If you want to use SOAP over JMS, use the JAX-RPC binding as your communications protocol.
  • Not supported
  • Not supported in the JAX-WS binding
  • If you want to use SOAP over JMS, use the JAX-RPC binding as your communications protocol.

SOAP Message Transmission Optimization Mechanism (MTOM)

  • Not supported
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.

Universal Description, Discovery and Integration (UDDI)

Web Services Business Activity (WS-BA)

  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.

W3C XML Schema

Web Services Addressing (WS-Addressing)

  • WS-Addressing 1.0 family of specifications:
  • Supported with restrictions: callback endpoint references from outbound responses are not supported (wsa:ReplyTo and wsa:FaultTo)
  • WS-Addressing 1.0 family of specifications:
  • WS-Addressing 1.0 family of specifications:
  • Not supported
  • WS-Addressing 1.0 family of specifications:

Web Services Atomic Transaction (WS-AT)

  • Not supported
  • Not supported
  • WS-AT 1.0

Web Services Coordination (WS-COOR)

  • Not supported
  • Not supported
  • WS-COOR 1.0

Web Services Description Language (WSDL)

Web Services Interoperability Organization (WS-I) Basic Profile

Web Services-Interoperability Attachments Profile

  • Not supported
  • Not supported

Web Services Policy (WS-Policy) specification

  • Not supported
  • Not supported
  • Not supported

Web Services Notification (WS-Notification)

  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.

Web Services Reliable Messaging

  • Not supported
  • Not supported

XML-binary Optimized Packaging (XOP)

  • Not supported
  • XML-binary Optimized Packaging - New
  • This standard is supported for BPM Advanced Version 7.5.1 when MTOM is enabled but not for BPM Advanced Version 7.5.0 or for WebSphere Process Server 7.0.
  • Not supported
  • Not supported. The standard is supported through the supplied WebSphere Application Server programming model.

Web service security

The web service security standards are listed in Table 2:

Table 2. Supported web service security industry standards
Specification or API IBM Business Process Manager Advanced 8.5 IBM Business Process Manager Standard Version 8.5 IBM Business Process Manager Advanced 8.0 IBM Business Process Manager Advanced 7.5 and WebSphere Process Server 7.0 IBM Business Process Manager Standard Version 8.0 and 7.5 WebSphere Process Server 6.2

Canonical XML

  • Not supported
  • Not supported

Decryption Transform for XML Signature

  • Not supported
  • Not supported

Exclusive XML Canonicalization

  • Not supported
  • Not supported

OASIS Web Services Security: SOAP Message Security (WS-Security)

OASIS Web Services Security: Kerberos Token Profile

  • Not supported
  • Not supported
OASIS Web Services Security: SAML Token Profile 1.1
Note: This specification is supported only in reference to the SAML Version 1.1 and 2.0 assertions within SOAP messages. SAML tokens can be used for inbound web services and outbound web services. However, you cannot reliably propagate the same inbound token to outbound web services as there are scenarios where the token is lost due to thread boundary changes, such as when a business process definition is invoked from the inbound service. For outbound web services you will need to create or request a token from a Security Token Service (STS. For more information see SAML concepts.
  • Not supported
  • Not supported

OASIS Web Services Security: Username Token Profile

OASIS Web Services Security: X.509 Token Profile

  • Not supported

Web Services Interoperability Organization (WS-I) Basic Security Profile

  • Not supported

Web Services Interoperability Organization (WS-I) Reliable Secure Profile

  • Not supported
  • Not supported

Web Services Secure Conversation (WS-SecureConversation)

  • Not supported

Web Services Trust

  • Not supported
  • Not supported

XML Signature Syntax and Processing

XML Encryption Syntax and Processing