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).
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.
Web services
The web services standards are listed in Table 1:
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 |
||||||
Web Services Interoperability (WS-I) Reliable
Secure Profile (RSP)
Note: Before WS-I RSP, the specification was
named Reliable Asynchronous Messaging Profile (RAMP).
|
||||||
SOAP |
||||||
SOAP with Attachments API for Java (SAAJ) Specification |
||||||
SOAP over Java Message Service (SOAP over JMS) |
|
|||||
SOAP Message Transmission Optimization Mechanism (MTOM) |
||||||
Universal Description, Discovery and Integration (UDDI) |
||||||
Web Services Business Activity (WS-BA) |
||||||
W3C XML Schema |
||||||
Web Services Addressing (WS-Addressing) |
||||||
Web Services Atomic Transaction (WS-AT) |
||||||
Web Services Coordination (WS-COOR) |
||||||
Web Services Description Language (WSDL) |
||||||
Web Services Interoperability Organization (WS-I) Basic Profile |
||||||
Web Services-Interoperability Attachments Profile |
||||||
Web Services Policy (WS-Policy) specification |
||||||
Web Services Notification (WS-Notification) |
||||||
Web Services Reliable Messaging |
||||||
XML-binary Optimized Packaging (XOP) |
Web service security
The web service security standards are listed in Table 2:
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 |
||||||
Decryption Transform for XML Signature |
||||||
Exclusive XML Canonicalization |
||||||
OASIS Web Services Security: SOAP Message Security (WS-Security) |
||||||
OASIS Web Services Security: Kerberos Token Profile |
||||||
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.
|
||||||
OASIS Web Services Security: Username Token Profile |
||||||
OASIS Web Services Security: X.509 Token Profile |
||||||
Web Services Interoperability Organization (WS-I) Basic Security Profile |
||||||
Web Services Interoperability Organization (WS-I) Reliable Secure Profile |
||||||
Web Services Secure Conversation (WS-SecureConversation) |
||||||
Web Services Trust |
||||||
XML Signature Syntax and Processing |
||||||
XML Encryption Syntax and Processing |