White Papers
Abstract
This publication describes the integration of WebSphere Application Server, WebSphere Process Server, WebSphere Message Broker, and WebSphere MQ. It uses a fictive order process to verify secured and reliable communication among these products in a bi-directional way.
Content
The scenario consists of WebSphere Process Server, WebSphere Application Server and WebSphere Message Broker-applications; MQ queues; two user registries (Tivoli Directory Server, file-based); and DB2 databases.
The integration considers:
- SSL configuration between WebSphere Application Server, WebSphere Process Server, and WebSphere Message Broker/WebSphere MQ
- Identity propagation and assertion between WebSphere Application Server, WebSphere Process Server, and WebSphere Message Broker
- JAX-WS and JAX-B clients on WebSphere Application Server for the WebSphere Process Server BPC- and HTM API
- Web Service Addressing (WS-A) between WebSphere Application Server and WebSphere Message Broker
- Integration patterns
- The documentation of the detailed implementation steps and provides an overview of the interactions from a security point of view.
Original Publication Date
08 March 2010
[{"Product":{"code":"SSQH9M","label":"WebSphere Process Server"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Security","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.0.0.5;7.0.0.4;7.0.0.3;7.0.0.2;7.0.0.1;7.0;6.2.0.3;6.2.0.2;6.2.0.1;6.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg27018200