WebSphere Message Broker, Version 8.0.0.7 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Optional software support

The products listed here are not required, but might be useful. Except where stated, these products are not supplied with WebSphere® Message Broker.

EIS client libraries

If you plan to use WebSphere Adapters on any supported operating system, you must obtain the appropriate Enterprise Information System (EIS) client libraries from the relevant EIS vendor (for example, PeopleSoft, Siebel, or SAP). The client libraries are required to complete connections between Adapters nodes and the EIS; install them on each computer on which you run a broker that hosts message flows that include Adapters nodes.

WebSphere Adapters

For details of the versions of WebSphere Adapters supported by WebSphere Message Broker, visit the WebSphere Message Broker Requirements website. For more information about the hardware and software requirements of WebSphere Adapters, see Supported software for WebSphere Adapters.

Tivoli License Manager

To monitor the use of software products including WebSphere Message Broker, install IBM® Tivoli® License Manager (ITLM). For the details of the version of ITLM that is required, visit the WebSphere Message Broker Requirements website.

Security providers

The message flow security manager interacts with external security providers:
  • Lightweight Directory Access Protocol (LDAP) provides authentication and authorization services. For details of the LDAP version that your LDAP server must support, visit the WebSphere Message Broker Requirements website.
  • WS-Trust V1.3 STS providers (including TFIM V6.2) provide authentication, mapping, and authorization services.
  • Tivoli Federated Identity Manager (TFIM) V6.1 provides authentication, mapping, and authorization services.

JMS providers

For details of the version of the Java™ Message Service Specification that the JMSInput and JMSOutput nodes are compatible with, and work with, visit the WebSphere Message Broker Requirements website.

Compilers

C/C++ user-defined extensions that were built with older levels of compilers can be used when migrating an existing broker or setting up a new broker.

However, C/C++ user-defined extensions on Linux might cause problems if linked against libstdc++.so.5 as WebSphere Message Broker is now linked against libstdc++.so.6. Recompile your user-defined extensions using a supported compiler.

For details of the versions of the compilers that are supported, visit the WebSphere Message Broker Requirements website.

Adobe Flash Player

If you want to start the Quick Tour from the information center in the WebSphere Message Broker Toolkit, you must install the Adobe Flash Player. For details of the versions of the Adobe Flash Player that are supported, visit the WebSphere Message Broker Requirements website. You can freely download from the Adobe website an Adobe Flash Player plug-in for the web browsers that are supported by the WebSphere Message Broker Toolkit.

WebSphere Process Server and WebSphere Integration Developer

Note: From Version 7.5 onwards, WebSphere Process Server has been renamed IBM Business Process Manager Advanced. Information in this topic that refers to WebSphere Process Server Version 7.0 is also applicable to IBM Business Process Manager Advanced Version 7.5. Similarly, from Version 7.5 onwards, WebSphere Integration Developer has been renamed IBM Integration Designer. Information in this topic that refers to WebSphere Integration Developer Version 7 is also applicable to IBM Integration Designer Version 7.5.
The SCA nodes allow interoperability with WebSphere Process Server, a business integration server that supports solutions that are based on service-oriented architecture (SOA). Service Component Architecture (SCA) is a specification that describes a model for building applications and systems using SOA and the SCA nodes support scenarios in which service components that run on WebSphere Process Server either are invoked from WebSphere Message Broker or invoke a WebSphere Message Broker message flow. For details of the versions of WebSphere Process Server that are supported by WebSphere Message Broker, visit the WebSphere Message Broker Requirements website.

WebSphere Integration Developer is the development environment for WebSphere Process Server. It is the tool for building and deploying SOA-based integration solutions on WebSphere Process Server. To enable WebSphere Message Broker to interoperate with WebSphere Process Server, SCA import and export components need to be imported into WebSphere Message Broker from WebSphere Integration Developer, and Broker SCA definitions need to be exported from WebSphere Message Broker to WebSphere Integration Developer. For details of the versions of WebSphere Integration Developer that are supported by WebSphere Message Broker, visit the WebSphere Message Broker Requirements website.

WebSphere Service Registry and Repository

WebSphere Service Registry and Repository provides a central repository of documents that describe services, service interfaces, and associated policies. For details of the versions of WebSphere Service Registry and Repository that are supported by WebSphere Message Broker, see the WebSphere Message Broker Requirements website.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:05


Reference topicReference topic | Version 8.0.0.7 | ah09089_