Advanced messaging security delivered in IBM WebSphere MQ Advanced Message Security V7.0.1

IBM United States Software Announcement 210-334
October 5, 2010

ENUS210-334.PDF ENUS210-334.PDF

Table of contents
Overview Overview Publications Publications
Key prerequisites Key prerequisites Technical information Technical information
Planned availability date Planned availability date Ordering information Ordering information
Description Description Terms and conditions Terms and conditions
Product positioning Product positioning Prices Prices
Statement of direction Statement of direction Order
now Order now
Program number Program number

(Corrected on October 18, 2010)

The At a glance, Description, and Product positioning sections are revised.

Top rule
At a glance
Bottom rule

WebSphere® MQ Advanced Message Security V7.0.1 extends the security features of WebSphere MQ with:

  • Application-level, end-to-end data protection
  • Comprehensive security without writing complex security code or modifying or recompiling existing applications
  • Administration of security policies across mainframe and distributed servers through MQ explorer or Command Line
  • WebSphere MQ server and WebSphere MQ client support
  • Integration with a WebSphere File Transfer Edition to provide end-to-end secure messaging solution

To order, contact your IBM® representative, an IBM Business Partner, or the Americas Call Centers at: 800-IBM-CALL Reference: YE001



Back to topBack to top
 
Top rule
Overview
Bottom rule

Information security is one of the top concerns both for business leaders and for those responsible for IT. Ensuring that information moving around the enterprise retains its integrity and is protected from unauthorized access is an ongoing challenge and responsibility for all organizations.

Based on WebSphere MQ Extended Security Edition V6.0, WebSphere MQ Advanced Message Security V7.0.1 is designed to remove many technical pre-requisites to simplify installation and configuration. WebSphere MQ Advanced Message Security V7.0.1 will help address these challenges when moving information around the enterprise between virtually every type of commercial IT system.

These advanced security services are compatible with:

  • WebSphere Message Broker
  • WebSphere MQ File Transfer Edition V7.0.3

WebSphere MQ is a prerequisite for WebSphere MQ Advanced Message Security V7.0.1. A separate license of WebSphere MQ is required for WebSphere MQ Advanced Message Security V7.0.1 on the distributed platform. WebSphere MQ Advanced Message Security is offered with the charge metric of per-processor-value-unit (PVU).

For instance, customer with 100 PVUs of WebSphere MQ Extended Security Edition V6.0 would get 100 PVUs of WebSphere MQ V7.0.1 and 100 PVUs of WebSphere MQ Advanced Message Security V7.0.1 when they are ready to migrate to WebSphere MQ Advanced Message Security V7.0.1.

For any customers who are currently paying for WebSphere MQ Extended Security Edition V6.0, contact an IBM sales representative for help with new license purchase for WebSphere MQ Advanced Message Security 7.0.1, when you are ready to migrate to WebSphere MQ Advanced Message Security V7.0.1. Customers are advised to stop paying MLC for WebSphere MQ Extended Security Edition V6.0, and start paying MLC for WebSphere MQ after migrating to WebSphere MQ Advanced Message Security V7.0.1.



Back to topBack to top
 
Top rule
Key prerequisites
Bottom rule

For a comprehensive list of prerequisites, refer to the Hardware requirements and Software requirements sections.



Back to topBack to top
 
Top rule
Planned availability date
Bottom rule

  • October 8, 2010: Electronic availability
  • October 22, 2010: Media availability


Back to topBack to top
 
Top rule
Description
Bottom rule

WebSphere MQ Advanced Message Security V7.0.1 delivers a special edition of WebSphere MQ with increased security features.

In addition to delivering increased security features of WebSphere MQ, WebSphere MQ Advanced Message Security V7.0.1, also offers a multiplatform security management solution that provides data protection for WebSphere MQ-based applications, without the need to modify or even recompile them.

This enhanced data protection acts at the application layer, above the link or channel level, so that the integrity and confidentiality of messages can be preserved and demonstrated not just while messages are in transit between systems, but also while they are under the control of WebSphere MQ (that is, while residing in a message queue). This is critical when using WebSphere MQ to process personally identifiable information or other types of sensitive data, such as high-value transactions. WebSphere MQ Advanced Message Security can help clients as part of their regulatory compliance efforts to meet their security goals and obligations.

With WebSphere MQ Advanced Message Security V7.0.1, you gain the flexibility to add application-level data protection and security policy administration to the broad set of security services previously available in WebSphere MQ. The application-level data protection services in WebSphere MQ Advanced Message Security V7.0.1 adds another dimension to the link-level data protection services available in WebSphere MQ. For example, application-level data protection captures message data and secures it before the message is placed onto a queue.

For even greater flexibility, messages can be individually digitally signed or signed and encrypted based on the policy you set. If you want, you can define your security policy so that only a subset of the messages passing over a single channel is secured. Further, when using the application-level data protection, each message is signed with a unique private key associated with the sending application. Message origin can be traced to the originating application instead of only to the originating channel.

Individual messages are encrypted under unique keys, helping to remove the threat of compromising the encryption key through repetitive use.

WebSphere MQ Advanced Message Security V7.0.1 can save development expense and time. It can remove the need to reengineer and modify your applications to secure message data from within each application. Reengineering existing production applications is a expensive process, the costs of which only begin with the application recoding expenses.

Licensing cryptography routines, training your staff, designing, and implementing a real-time key exchange process and budgeting for ongoing maintenance cost of custom security code make this approach to solving security problems impractical. With WebSphere MQ Advanced Message Security V7.0.1 you may see an immediate return on investment upon deploying it.

For processing sensitive data like financial transactions, Human Resources records, medical records, or any other type of personally identifiable information (PII), application-level data protection yields a true end-to-end security model.

WebSphere MQ Advanced Message Security V7.0.1 also enables administration of security policies on queue managers and on individual queues. These include:

  • Put and get access control permissions, including time-of-day and day-of-week restriction.
  • Data protection options (none, integrity, and privacy).
  • Audit options that allow generation of a specific security audit record for each open, put, get, and close operation showing the security policy in place and whether it was successfully enforced. This can be critical in demonstrating compliance with legislation like the United States Health Insurance Portability and Accountability Act (HIPAA) or similar mandates in other countries.

Administration is performed via MQ explorer or Command Line for setting, viewing, and updating policies. A delegation capability allows IT organizations to maintain control over the enterprise security infrastructure for WebSphere MQ Advanced Message Security V7.0.1 and still grant a specific department or line-of-business the ability to manage its subset of resources. Administration can also be done via scripting using a command line interface.

An enterprise-wide view of these security policies, with the ability for authorized administrators to update them, can greatly improve efficiencies and reduce administrative costs.

In this release of WebSphere MQ Advanced Message Security V7.0.1, the advanced security services are provided on a subset of the operating systems on which WebSphere MQ is available. This subset includes:

  • AIX V5.3, v6.0
  • Sun Solaris 9, and 10
  • HP-UX 11i
  • Microsoft(TM) Windows(TM) Windows® 2003
  • Linux(TM) (Intel®) - Red Hat Enterprise Linux® 4.0
  • Linux(TM) (Intel) - SUSE Linux Enterprise Server 9.0, and 10.0
  • zSeries® Linux - Red Hat Enterprise Linux 4.0 (64-bit only)
  • zSeries Linux - SUSE Linux Enterprise Server 9.0, and 10.0 (64-bit only)

For more details on the base-level security functions available in WebSphere MQ, refer to Software Announcement 209-245, dated August 25, 2009.

Accessibility by people with disabilities

A US Section 508 Voluntary Product Accessibility Template (VPAT) can be requested via the IBM website

http://www.ibm.com/able/product_accessibility/index.html

Section 508 of the U.S. Rehabilitation Act

WebSphere MQ Advanced Message Security is capable as of October 22, 2010 , when used in accordance with IBM's associated documentation, of satisfying the applicable requirements of Section 508 of the Rehabilitation Act, provided that any assistive technology used with the product properly interoperates with it. A U.S. Section 508 Voluntary Product Accessibility Template (VPAT), containing details on the products accessibility compliance, can be requested on the following website

http://www.ibm.com/able/product_accessibility/index.html


Back to topBack to top
 
Top rule
Product positioning
Bottom rule

The WebSphere MQ family offers a messaging backbone for service-oriented architecture (SOA) connectivity. It connects new and existing applications, as well as web services, with reliable messaging. WebSphere MQ is a first step to SOA as a transport layer to underpin an Enterprise Service Bus. It delivers assured, reliable messaging - as well other qualities of service - offering choice in the class of delivery.

WebSphere MQ supports industry-standard, Java™ Messaging Service (JMS) messaging. It enables simple, RESTful access from Web 2.0 to core back-end applications. WebSphere MQ integrates virtually any commercial IT system with support for more than 80 platform configurations. It integrates Java Enterprise Edition (JEE) applications, Microsoft® .NET applications, IBM CICS®, IBM IMS™, DB2®, and packaged applications.

WebSphere MQ can help organizations get more from their IT investments by offering a reliable and flexible integration backbone for exchanging messages between applications and Web services.

  • WebSphere MQ, the core of application integration, delivers the reliable, proven messaging backbone for SOA connectivity, as the universal, multipurpose data transport. It connects many commercial IT systems, with support for more than 80 platform configurations. WebSphere MQ supports industry-standard JMS messaging and offers a choice of APIs. WebSphere MQ interoperates with the JMS embedded in WebSphere Application Server, extending its reach to non-JEE environments. WebSphere MQ is a flexible connectivity solution that can grow incrementally with changing business needs.
  • WebSphere MQ for z/OS® exploits the capabilities of the IBM System z® platform to deliver a messaging powerhouse.
  • WebSphere MQ for HP OpenVMS, WebSphere MQ for HP NonStop Server, and MQSeries® for z/VSE™ all extend the reach of WebSphere MQ to these specific computing platforms.
  • WebSphere MQ Telemetry extends messaging beyond enterprise boundaries to remote sensors and devices making data and events from the real-world readily available to existing applications, services and decision makers enabling organizations to sense-and-respond faster.
  • WebSphere MQ File Transfer Edition adds file-specific features to the proven WebSphere MQ transport. It delivers a managed file transfer solution that enables the movement of files between IT systems with reliability and without the need for programming.
  • WebSphere MQ Advanced Message Security expands the industry-standard security supplied by WebSphere MQ with end-to-end data protection for applications. It enables enterprise-wide, management of security polices on an MQ network and can be deployed to existing production environments without changes to existing WebSphere MQ applications.
  • WebSphere MQ Low Latency Messaging (on Linux, Microsoft Windows, and Solaris platforms) extends the WebSphere MQ product family with low-latency, high-throughput delivery. It is optimized for the high-volume, low-latency requirements typical of financial markets firms and other industries where speed of data delivery is paramount.

The WebSphere portfolio provides additional connectivity capabilities that can build on, and take advantage of, the SOA Messaging provided by WebSphere MQ:

  • WebSphere Service Registry and Repository provides an SOA Repository that can help publish, find, enrich, manage, and govern services and policies in your SOA. Using the MQ Service Definition, WebSphere Service Registry and Repository can now be used visualize the relationships between MQ services and to govern the lifecycle of MQ applications and messaging services in the same way as for other SOA services.
  • WebSphere Message Broker is an enterprise service bus (ESB) built for universal connectivity and transformation in heterogeneous IT environments. It builds on the WebSphere MQ messaging layers with ESB capabilities that add transformation, intelligent routing, and information flow modelling.
    • WebSphere Message Broker Starter Edition is an entry-level starting point to deploy an ESB with the ability to grow as your clients' business needs increase.
    • WebSphere Message Broker for Remote Adapter Deployment enables deployment of adapters with a compact and efficient runtime at an affordable price.
  • WebSphere ESB leverages Web services standards and builds on the embedded messaging in WebSphere Application Server. WebSphere MQ extends the reach of this ESB to non-JEE environments and a broader range of platforms.
  • WebSphere DataPower® Integration Appliance XI50 offers an ESB in an appliance form factor. It is a 1U (1.75-in thin) rack-mountable network device capable of transforming between disparate message formats, including binary, legacy, and XML, and providing message routing and security. XI50 delivers client connectivity into the WebSphere MQ backbone.
  • WebSphere Partner Gateway enables trading partner business-to-business (B2B) integration. It provides centralized and consolidated B2B trading partner and transaction management to enable and manage process and data integration with trading partners. It supports standards-based transport protocols such as EDIINT AS1, AS2 or AS3, RosettaNet RNIF 1.1 and 2.0, cXML, CIDX Chem eStandards 4.0, ebXML Messaging Service (ebMS) 2.0 to support the connectivity needs of various trading partners, and FIPS 140-2 enablement to be compliant with the FIPS standard.
  • WebSphere DataPower B2B Appliance XB60 provides purpose-built business-to-business (B2B) hardware that supports AS2 and AS3 protocols and trading partner profile management in a high-performance demilitarized zone (DMZ)-ready appliance.
  • WebSphere DataPower Low Latency Appliance XM70 is a purpose-built Low Latency Messaging hub for simplified deployment, content-based routing and extreme performance.
  • WebSphere Transformation Extender is a universal data transformation and validation engine. It helps tackles the challenges of integrating enterprise systems and information with a codeless, graphical approach to development.
  • WebSphere Adapters deliver generic technology and business application adapters with wizards that quickly and easily service enable legacy applications, enterprise resource planning (ERP), human resources (HR), customer relationship management (CRM), and supply chain systems.

In addition, the IBM Tivoli® portfolio offers systems management for large-scale WebSphere MQ Solutions. Tivoli OMEGAMON® XE for Messaging can help improve the availability and performance of WebSphere MQ solutions. It can identify common problems and automate corrective actions using predefined industry best-practice situations, while monitoring key WebSphere MQ metrics.

Tivoli OMEGAMON XE for Messaging can help improve management of Service Level Agreements (SLAs) by monitoring availability and capacity using real-time and historical data analysis. Out-of-the-box capabilities, such as auto-discovery and monitoring of complex WebSphere MQ environments, can improve IT staff productivity and reduce administration costs.

In addition, SupportPac™ product extensions, which enable additional function are available. Visit

http://www-01.ibm.com/software/integration/wmq/


Back to topBack to top
 
Top rule
Statement of direction
Bottom rule

All statements regarding IBM plans, directions, and intent are subject to change or withdrawal without notice.



Back to topBack to top
 
Top rule
Program number
Bottom rule

Program    
number     VRM              Program name
 
5724-Z94   7.0.0            WebSphere MQ Advanced Message Security


Back to topBack to top
 
Top rule
Offering Information
Bottom rule

Product information is available via the Offering Information website

http://www.ibm.com/common/ssi

Also, visit the Passport Advantage® website

http://www.ibm.com/software/passportadvantage


Back to topBack to top
 
Top rule
Publications
Bottom rule

No publications are shipped with this product.

The IBM Publications Center

http://www.ibm.com/shop/publications/order

The Publications Center is a worldwide central repository for IBM product publications and marketing material with a catalog of 70,000 items. Extensive search facilities are provided. Payment options for orders are via credit card (in the U.S.) or customer number for 20 countries. A large number of publications are available online in various file formats, and they can all be downloaded by all countries.



Back to topBack to top
 
Top rule
Technical information
Bottom rule

Specified operating environment

Hardware requirements

For full and latest details, visit

http://www.ibm.com/software/integration/wmq/requirements/index.html

AIX®

64-bit IBM pSeries® systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods and the application programs.

Any hardware capable of running other trademarked AIX systems from IBM or other vendors that have passed a set of certification tests for compliance with the AIX application binary and programming interfaces.

HP-UX Itanium®

Any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software, and any associated applications unmodified.

HP-UX PA-RISC

64-bit systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods, and the application programs.

Linux on IBM System x® (32-bit)

x86 PC hardware, including x86-64 processors, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods and the application programs.

Linux on IBM System x (64-bit)

AMD64, EM64T, and compatible processors: any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software, and any associated applications unmodified.

Linux on IBM System p®

64-bit System i® and System p IBM POWER processor-based systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods, and the application programs.

Linux on IBM System z

IBM System z9® or IBM eServer™ (or equivalent) 64-bit: any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software, and any associated applications unmodified.

Sun Solaris on x86-64

AMD64, EM64T, and compatible processors: any hardware that is explicitly compatible and fully capable of running the specified operating system, all the corresponding supporting software, and any associated applications unmodified. Sun Solaris operating environment: 64-bit Sun SPARC systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods, and the application programs.

Sun Solaris SPARC

64-bit Sun SPARC systems only, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods, and the application programs.

Microsoft Windows

X86 and x86-64 (also known as x64) technology-compatible PC hardware, capable of running the required level of a compatible operating system with enough storage to meet the combined requirements of the programming prerequisites, WebSphere MQ, the access methods, and the application programs. Note that Itanium 64-bit is not supported.

Software requirements

For full and latest details, visit

http://www.ibm.com/software/integration/wmq/requirements/index.html

AIX

Operating systems

  • AIX 5.3 Technology Level 04 or Technology Level 05 plus SP2 or later, and the appropriate firmware
  • AIX 6.1

For C/C++ applications

  • IBM C for AIX V6.0
  • IBM XL C Enterprise Edition for AIX V7.0
  • XL C Enterprise Edition for AIX V8.0
  • XL C Enterprise Edition for AIX V9.01
  • XL C Enterprise Edition for AIX V10.1
  • IBM VisualAge® C++ Professional for AIX V6.0
  • XL C/C++ Enterprise Edition for AIX V7.0
  • XL C/C++ Enterprise Edition for AIX V8.0
  • XL C/C++ Enterprise Edition for AIX V9.01
  • XL C/C++ Enterprise Edition for AIX V10.1
1
The minimum level of XL C/C++ Enterprise Edition for AIX V9.0 is 9.0.0.3.

For COBOL applications

  • IBM COBOL Set for AIX V2.0 (32-bit applications only)
  • Micro Focus Server Express® V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • IBM 32-bit SDK for AIX, V1.42
  • IBM 32-bit SDK for AIX, V52
  • IBM 32-bit SDK for AIX, V6 2

64-bit

  • IBM 64-bit SDK for AIX, V1.4.2
  • IBM 64-bit SDK for AIX, V52
  • IBM 64-bit SDK for AIX, V62
2
Java 5 and above require at least AIX 5.3.0.30.

SOAP support

  • IBM 32-bit Java SDK for AIX, V1.4.2
  • IBM 32-bit Java SDK for AIX, V5
  • IBM 32-bit Java SDK for AIX, V6
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • TXSeries® V6.1 and V6.23, 4
  • TXSeries V7.1 3, 4
  • BEA Tuxedo V9.1
3
This requires either AIX 5.3 TL6 SP4 plus APAR IZ10231 or AIX 6.1. APAR IZ10231 is available in AIX 5.3 Technology Level 6 Service Pack5 (AIX 5.3 TL6-SP5, TL7, 610).
4
The resiliency feature of TXSeries V6.1, V6.2, or V7.1 is not supported. XA Resiliency feature of TXSeries V6.1, V6.2, V7.1 does not work with WebSphere MQ as a Resource Manager.

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported5
5
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4) or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9) or later

Resource Managers (when WebSphere MQ is the transaction manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX®, and Microsoft Windows6
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows 6
  • IBM Informix® Dynamic Server (IDS) V10 with Client SDK V2.907
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.07
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V157
6
Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
7
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • IBM Communications Server for IBM AIX V6.3 (SNA)
  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for AIX, V5
  • IBM 64-bit SDK for AIX, V5

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1 or later
  • WebSphere Application Server V7 or later
  • WebSphere Application Server Community Edition V1.1 or later
  • WebSphere Application Server Community Edition V2.1 or later

Multi-instance queue managers

When using NFS on AIX v5.3, APAR IY92300 is required.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System™ (GPFS™) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

HP-UX Itanium

Operating systems

  • HP-UX 11i V2 (11.23) for IPF
  • HP-UX 11i V3 (11.31) for IPF8

For C/C++ applications

  • For applications using the WebSphere MQ C++ classes, the standard runtime is supported.
  • HP C/ANSI Developer Bundle for HP-UX 11i2
  • HP aCC A.06.12
  • HP aCC A.06.13
  • HP aCC A.06.14
  • HP aCC A.06.15
  • HP aCC A.06.16

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

pthread cumulative patch PHCO_34718 is required to resolve an intermittent core dump when running Java applications. The ID of the problem record is JAGaf78055.

32-bit

  • HP-UX IPF Software Development Kit for the Java 2 platform, V1.4.2
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2 for 32-bit Itanium9, 10
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 32-bit Itanium (SR1 or above) 10

64 bit:

  • HP-UX IPF Software Development Kit for the Java 2 platform, V1.4.2
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2 for 64-bit Itanium 9, 10
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 64-bit Itanium (SR1 or above) 10
8
Before installing on HP-UX 11i V3 (11.31) see technote 1270591.
9
Only if the JDK is supplied with another IBM product.
10
FIPS compliance is only supported on IBM adapted SDKs.

SOAP support

  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2 for 32-bit Itanium
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 32-bit Itanium (SR1 or above) (32-bit only)
  • HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software, V6 for 32-bit Itanium
  • Apache Axis V1.4 (supplied with WebSphere MQ)

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4) or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9) or later

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • TXSeries V6.1 and V6.211
  • TXSeries V7.111
  • BEA Tuxedo V9.1
  • BEA Tuxedo V10.3
11
The resiliency feature of TXSeries V6.1, V6.2, and V7.1 is not supported. The XA Resiliency feature of TXSeries V6.1, V6.2, and V7.1 does not work with WebSphere MQ as a Resource Manager.

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported12
12
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the Transaction manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows13
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows13
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9014
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.014
  • Oracle 10g Release 2
  • Oracle 11g
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1514
13
Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
14
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • HP SNAplus2 Version 7 (SNA)
  • TCP/IP (provided by the operation system); IPv6 feature support is available with HP's Transport Optional Upgrade Release (TOUR)

Versions of products or components shipped with the product

JDK

  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 32-bit Itanium
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 64-bit Itanium

GSKiit

  • Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Multi-instance queue managers

ONC B.11.31.08 required for multi-instance queue manager support.

For HP-UX 11.31, libc cumulative patch PHCO_36900 or superseding patch is required.

For multi-instance queue managers you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

HP-UX PA-RISC

Operating systems

  • HP-UX 11i V2 (11.23)
  • HP-UX 11i V3 (11.31)15
15
Before installing on HP-UX 11i V3 (11.31), see technote 1270591.

For C/C++ applications

  • For applications using the WebSphere MQ C++ classes, the standard runtime is supported.
  • HP C/ANSI Developer Bundle for HP-UX 11i2
  • HP aCC A.03.6516
  • HP aCC A.03.67 16
  • HP aCC A.03.7016
  • HP aCC A.03.7316
  • HP aCC A.03.7417
  • HP aCC A.03.77
  • HP aCC A.03.80
16
Supported on HP-UX 11i V2 only.
17
Supported on HP-UX 11i V3 only.

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • HP-UX Software Development Kit for the Java platform and JDK, V1.4.2 (32- and 64-bit)
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.218, 19
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 (SR1 or above)19

64 bit

  • HP-UX Software Development Kit for the Java platform and JDK, V1.4.2 (32- and 64-bit)
  • HP 64-bit SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2 for 64-bit PA-RISC18, 19
  • HP 64-bit SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 64-bit PA-RISC (SR1 or above)19
18
Only if the JDK is supplied with another IBM product.
19
FIPS compliance is only supported on IBM adapted SDKs.

SOAP support

  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V1.4.2 (32-bit only)
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 32-bit (SR1 or above) (32-bit only)
  • HP JDK for JSE HP-UX 11i platform, adapted by IBM for IBM Software, V6 for 32-bit PA-RISC
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • TXSeries V6.1 and V6.220
  • TXSeries V7.1 20
  • BEA Tuxedo V9.1

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported21

Resource Managers (when WebSphere MQ is the transaction manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows22
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.023
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1523
20
The resiliency feature of TXSeries V6.1, V6.2, and V7.1 is not supported. The XA Resiliency feature of TXSeries V6.1, V6.2, and V7.1 does not work with WebSphere MQ as a Resource Manager.
21
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.
22
Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
23
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • HP SNAplus2 Version 7 (SNA)
  • TCP/IP (provided by the operation system); IPv6 feature support is available with HP's Transport Optional Upgrade Release (TOUR)

Versions of products or components shipped with the product

JDK

  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0
  • HP SDK for J2SE HP-UX 11i platform, adapted by IBM for IBM Software, V5.0 for 64-bit PA-RISC

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later
  • WebSphere Application Server V7, or later

Multi-instance queue managers

ONC B.11.31.08 required for multi-instance queue manager support.

For HP-UX 11.31, libc cumulative patch PHCO_36900 or superseding patch is required.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Linux on System x (32-bit)

Operating systems

  • Red Hat Enterprise Linux (RHEL) V4.0, or later update
  • Red Hat Enterprise Linux (RHEL) V5.0 to V5.3
  • SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V11
  • NLPOS9 FP1
  • IRES V2
  • Red Flag Data Centre V5.0

For C/C++ applications

  • GNU C Compiler (gcc) and g++ V3.3 (SLES 9)
  • GNU C Compiler (gcc) and g++ V4.1 (SLES 10)24
  • GNU C Compiler (gcc) and g++ V3.4 (Red Hat 4)24
  • GNU C Compiler (gcc) and g++ V4.1 (Red Hat 5)24
24
On Linux platforms, if you need to use SSL in a C++ WebSphere MQ application, you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with WebSphere MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. WebSphere MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • Java 2 Platform, Standard Edition (J2SE) V1.4.2 from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition (J2SE) V5.0 from Sun Microsystems, Inc.
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.225
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.025

64-bit

Not applicable

25
Only if the JDK is supplied with another IBM product.

SOAP support

  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.2
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • BEA Tuxedo V9.1
  • BEA Tuxedo V1026, 27

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported28
26
This only applies to Red Hat Linux: A fix with identifier CR235194 is required to ensure that WebSphere MQ can successfully access the C library function catopen() in a Tuxedo server program.
27
Use rolling patch R017 so as to obtain a fix with identifier CR382618.
28
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction manager)

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9029
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.029
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1529
29
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • IBM Communications Server for Linux V6.2 (SNA)
  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later
  • WebSphere Application Server V7, or later
  • WebSphere Application Server Community Edition V1.1, or later
  • WebSphere Application Server Community Edition V2.1, or later

Multi-instance queue managers

Multi-instance queue managers are not supported on RHEL V4.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Linux on System x (64-bit)

Operating systems

  • Red Hat Enterprise Linux (RHEL) V4.0, or later update
  • Red Hat Enterprise Linux (RHEL) V5.0 to V5.3
  • SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V11

For C/C++ applications

  • GNU C Compiler (gcc) and g++ V3.3 (SLES 9)
  • GNU C Compiler (gcc) and g++ V4.1 (SLES 10)30
  • GNU C Compiler (gcc) and g++ V3.4 (Red Hat 4)30
  • GNU C Compiler (gcc) and g++ V4.1 (Red Hat 5)30
30
On Linux platforms, if you need to use SSL in a C++ WebSphere MQ application, you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with WebSphere MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. WebSphere MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • Java 2 Platform, Standard Edition (J2SE) V1.4.2, from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition (J2SE) V5.0, from Sun Microsystems, Inc.
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.231
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.031

64-bit

  • Java 2 Platform, Standard Edition (J2SE) V1.5, from Sun Microsystems, Inc.
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java 2 Technology Edition, V1.4.231
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java Technology Edition, V6.031
31
Only if the JDK is supplied with another IBM product.

SOAP support

  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V1.4.2
  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on Intel architecture, Java Technology Edition V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • BEA Tuxedo V9.1

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported32
32
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction manager)

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9033
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.033
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1533
33
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Linux on Intel architecture, Java 2 Technology Edition V5.0
  • IBM 64-bit SDK for Linux on AMD64/EM64T architecture, Java 2 Technology Edition, V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later
  • WebSphere Application Server V7 or later
  • WebSphere Application Server Community Edition V1.1, or later
  • WebSphere Application Server Community Edition V2.1, or later

Multi-instance queue managers

Multi-instance queue managers are not supported on RHEL V4.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Linux on System p

Operating systems

  • Red Hat Enterprise Linux (RHEL) V4.0, or later update
  • Red Hat Enterprise Linux (RHEL) V5.0 to V5.3
  • SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V11

For C/C++ applications

  • GNU C Compiler (gcc) and g++ V3.3 (SLES 9)
  • GNU C Compiler (gcc) and g++ V4.1 (SLES 10)34
  • GNU C Compiler (gcc) and g++ V3.4 (Red Hat 4)34
  • GNU C Compiler (gcc) and g++ V4.1 (Red Hat 5)34
34
On Linux platforms, if you need to use SSL in a C++ WebSphere MQ application, you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with WebSphere MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. WebSphere MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • IBM 32-bit SDK for Linux on iSeries® and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only)35
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on System i and System p

64-bit

  • IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only)35
  • IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 64-bit SDK for Linux on System i and System p architecture, Java Technology Edition, V6.035
35
Only if the JDK is supplied with another IBM product.

SOAP support

  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V1.4.2 (supported on System p only)
  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Linux on System i and System p architecture, Java Technology Edition, V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported36
36
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction manager)

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9037
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.037
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1537
37
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • IBM Communications Server for Linux V6.2 (SNA)
  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition V5.0
  • IBM 64-bit SDK for Linux on iSeries and pSeries, Java 2 Technology Edition, V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later
  • WebSphere Application Server Community Edition V1.1, or later

Multi-instance queue managers

Multi-instance queue managers are not supported on RHEL V4.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Linux on System z

Operating systems

  • Red Hat Enterprise Linux (RHEL) V4.0, or later update
  • Red Hat Enterprise Linux (RHEL) V5.0 to V5.3
  • SUSE Linux Enterprise Server (SLES) V9 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V10 with Service Pack 1, or later
  • SUSE Linux Enterprise Server (SLES) V11

For C/C++ applications

  • GNU C Compiler (gcc) and g++ V3.3 (SLES 9)
  • GNU C Compiler (gcc) and g++ V4.1 (SLES 10)38
  • GNU C Compiler (gcc) and g++ V3.4 (Red Hat 4)38
  • GNU C Compiler (gcc) and g++ V4.1 (Red Hat 5)38
38
On Linux platforms, if you need to use SSL in a C++ WebSphere MQ application, you must link the application against the libstdc++.so.5 runtime library. This is because the version of the GSkit SSL libraries supplied with WebSphere MQ depends on libstdc++.so.5 and this GSkit version is not compatible with other C++ runtime library versions. WebSphere MQ C++ applications built against the GCC 3.2 or 3.3 C++ runtime libraries comply with this restriction and will be able to use SSL.

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition, V1.4.239
  • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 31-bit SDK for Linux on System z architecture, Java Technology Edition, V6.039

64-bit

  • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition, V1.4.239
  • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 64-bit SDK for Linux on System z architecture, Java Technology Edition, V6.039
39
Only if the JDK is supplied with another IBM product.

SOAP support

  • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition V1.4.2
  • IBM 31-bit SDK for Linux on zSeries architecture, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 31-bit SDK for Linux on zSeries, Java Technology Edition V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported40
40
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction manager)

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9041
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.041
  • Oracle 10g Release 2
41
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 31-bit SDK for Linux on zSeries, Java 2 Technology Edition V5.0
  • IBM 64-bit SDK for Linux on zSeries, Java 2 Technology Edition, V5.0

GSKiit

  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Multi-instance queue managers

Multi-instance queue managers are not supported on RHEL V4.

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Sun Solaris on x86-64

Operating systems

  • Sun Solaris V10 (with SunSolve-recommended Patch Cluster level)

For C/C++ applications

  • Sun ONE Studio 10 Enterprise Edition for Sun Solaris (C and C++)
  • Sun ONE Studio 11 Enterprise Edition for Sun Solaris (C and C++)

For COBOL applications

  • Micro Focus Server Express V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • Sun Java 2 Platform Standard Edition, Version 1.4.2
  • Sun Java 2 Platform Standard Edition, Version 5.0
  • Sun Java 2 Platform Standard Edition, Version 6.0
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition, V1.4.242, 43
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0 (SR1 or above)43
  • IBM 32-bit SDK for Sun Solaris on Intel architecture, Java Technology Edition V6.042, 43

64-bit

  • Sun Java 2 Platform Standard Edition, Version 5.0
  • Sun Java 2 Platform Standard Edition, Version 6.0
  • IBM 64-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0 (SR1 or above)43
  • IBM 64-bit SDK for Sun Solaris on AMD64/EM64T architecture, Java Technology Edition V6.042, 43

SOAP Support

  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition, V1.4.2
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Sun Solaris on Intel architecture, Java Technology Edition V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers: Not applicable

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported44
42
Only if the JDK is supplied with another IBM product.
43
FIPS compliance is only supported on IBM SDKs.
44
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9045
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.045
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1545
45
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0
  • IBM 64-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Firefox 2.0
  • Konqueror (UI base mode only)

Multi-instance queue managers

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Sun Solaris SPARC

Operating systems

  • Sun Solaris V9
  • Sun Solaris V10

For C/C++ applications

  • Sun ONE Studio 9 Compiler Collection (C and C++)
  • Sun Studio 10 Software for Sun Solaris Platforms
  • Sun ONE Studio 11 Enterprise Edition for Sun Solaris (C and C++)

For COBOL applications

  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • Sun Solaris Java SDK V1.4 with JDK V1.4.2
  • Sun Solaris Java SDK V5 with JDK V5
  • Sun Solaris Java SDK V6 with JDK V6
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition, V1.4.246, 47
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition, V5.0 (SR1 or above)47
  • IBM 32-bit SDK for Sun Solaris, Java Technology Edition, V6.046, 47

64-bit

  • Sun Java 2 SDK, Standard Edition V1.4.2
  • Sun Java 2 SDK, Standard Edition V5
  • Sun Java 2 SDK, Standard Edition V6
  • IBM 64-bit SDK for Sun Solaris, Java 2 Technology Edition, V1.4.2 46, 47
  • IBM 64-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0 (SR1 or above)47
  • IBM 64-bit SDK for Sun Solaris, Java Technology Edition V6.0 46, 47

SOAP support

  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition, V1.4.2
  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0 (SR1 or above)
  • IBM 32-bit SDK for Sun Solaris, Java Technology Edition V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • TXSeries V6.1 and V6.248
  • TXSeries V7.148
  • BEA Tuxedo V9.1
46
Only if the JDK is supplied with another IBM product
47
FIPS compliance is only supported on IBM SDK
48
The resiliency feature of TXSeries V6.1, V6.2, and V7.1 is not supported. The XA Resiliency feature of TXSeries V6.1, V6.2, and V7.1 does not work with WebSphere MQ as a Resource Manager.

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • BEA WebLogic Server 10.3 (JMS only)50
  • Other application server environments may be supported49
49
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.
50
BEA WebLogic Server 10.3 must be run with Sun Java 6.0.

Resource Managers (when WebSphere MQ is the transaction manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9051
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.051
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1551
51
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • SNAP-IX V7.0 (SNA)
  • TCP/IP (IPv4 and IPv6 provided by the operating system)

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0
  • IBM 64-bit SDK for Sun Solaris, Java 2 Technology Edition V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later
  • WebSphere Application Server V7, or later
  • WebSphere Application Server Community Edition V1.1, or later
  • WebSphere Application Server Community Edition V2.1, or later

Multi-instance queue managers

For multi-instance queue managers, you will need a networked storage device (such as a NAS). The storage must be accessed by a network file system protocol which is Posix-compliant and supports lease-based locking. Network File System version 4 (NFS v4) and IBM General Parallel File System (GPFS) both satisfy this requirement. Earlier versions of NFS do not satisfy this requirement and must not be used with multi-instance queue managers.

Microsoft Windows

Operating systems

  • Microsoft Windows XP Professional (SP2 or later)
  • Microsoft Windows XP Professional x64 Edition
  • Microsoft Windows Server 2003 (SP1 or later) (Standard Edition or Enterprise Edition)
  • Microsoft Windows Server 2003 (SP1 or later) (Standard x64 Edition or Enterprise x64 Edition)
  • Microsoft Windows Server 2003 R2 (SP1 or later) (Standard Edition or Enterprise Edition)
  • Microsoft Windows Server 2003 R2 (SP1 or later) (Standard x64 Edition or Enterprise x64 Edition)
  • Microsoft Windows Server 2008 (Standard or Enterprise (32- and 64-bit Edition)52
  • Microsoft Windows Vista (Business, Enterprise or Ultimate Edition)
  • Microsoft Windows Vista (64-bit versions of Business, Enterprise or Ultimate Edition)
  • Microsoft Windows Embedded Point of Service 1.0
52
There is an open issue with the use of WebSphere MQ and MSCS in a Microsoft Windows 2008 environment. Reference: APAR IC59261.

For C/C++ applications

  • Microsoft Visual Studio C++ 2005

For COBOL applications

  • IBM COBOL supplied with Rational® Developer for System z
  • Micro Focus Server Express V4.0 and V5.0

For Java applications using the WebSphere MQ classes for Java or JMS

32-bit

  • Java 2 Platform, Standard Edition (J2SE) V1.4.2, from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition V5.0 (SR1 or above), from Sun Microsystems, Inc.
  • Java 2 Platform, Standard Edition V6.0, from Sun Microsystems, Inc.
  • IBM 32-bit SDK for Microsoft Windows, Java 2 Technology Edition, V1.4.253, 54
  • IBM 32-bit SDK for Microsoft Windows, Java 2 Technology Edition, V5.0 (SR1 or above)53
  • IBM 32-bit SDK for Microsoft Windows, Java Technology Edition, V6.053, 54

64-bit

  • Sun Java 2 Platform Standard Edition, Version 5.0
  • Sun Java 2 Platform Standard Edition, Version 6.0
  • IBM 64-bit SDK for Microsoft Windows AMD64/EM64T architecture, Java 2 Technology Edition, V1.4.253
  • IBM 64-bit SDK for Microsoft Windows AMD64/EM64T architecture, Java 2 Technology Edition, V5.0
  • IBM 64-bit SDK for Microsoft Windows AMD64/EM64T architecture, Java Technology Edition, V6.053
53
Only if the JDK is supplied with another IBM product.
54
FIPS compliance is only supported on IBM SDKs.

For .NET applications

  • Microsoft .NET Framework V2.0
  • Microsoft .NET Framework V3.0
  • Microsoft .NET Framework V3.5
  • Microsoft .NET Framework SDK V3.5 or Microsoft Visual Studio 2008 for Windows Communications Foundation (WCF) support

SOAP support

  • Microsoft Internet Information Services (for running .NET services) on Microsoft Windows XP and 2003
  • Microsoft .NET Framework V2.0
  • Microsoft .NET Framework SDK V2.0 or Microsoft Visual Studio 2005 (for deploying Microsoft .NET services)
  • IBM 32-bit SDK for Microsoft Windows, Java 2 Technology Edition, V1.4.2
  • IBM 32-bit SDK for Microsoft Windows, Java 2 Technology Edition, V5.0 (SR1 or above)
  • IBM 32-bit SDK for Microsoft Windows, Java Technology Edition, V6.0
  • Apache Axis V1.4 (supplied with WebSphere MQ)

Transactions Managers

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • TXSeries V6.1 and V6.255
  • TXSeries V7.155
  • BEA Tuxedo V9.1
  • MTS/COM (at the same level as the operating system)

WebSphere Message Broker

  • WebSphere Message Broker V6.1 with Fix Pack 4 (6.1.0.4), or later
  • WebSphere Message Broker V6.0 with Fix Pack 9 (6.0.0.9), or later

Application servers

Where a WebSphere MQ client application is running in one of the listed transaction manager environments, it is recommended that you contact the transaction manager vendor in the first instance for support:

  • WebSphere Application Server, including the WebSphere Application Server client container, V6.0.2
  • WebSphere Application Server, including the WebSphere Application Server client container, V6.1
  • WebSphere Application Server, including the WebSphere Application Server client container, V7.0
  • BEA WebLogic Server 9.2 (JMS only)
  • Other application server environments may be supported56
55
The resiliency feature of TXSeries V6.1, V6.2, and V7.1 is not supported. The XA Resiliency feature of TXSeries V6.1, V6.2, and V7.1 does not work with WebSphere MQ as a Resource Manager.
56
For more detailed information about using WebSphere MQ with application servers, see the WebSphere MQ resource adapter statement of support document.

Resource Managers (when WebSphere MQ is the transaction Manager)

Using the WebSphere MQ classes for JMS, WebSphere MQ can only act in the role of a Resource Manager. A third-party Transaction Coordinator must be used (for example, WebSphere Application Server).

Using the WebSphere MQ classes for Java, WebSphere MQ can act as a Transaction Coordinator. However, it is not possible to participate in a JTA-style transaction.

  • DB2 V9.1 for Linux, UNIX, and Microsoft Windows57
  • DB2 V9.5 for Linux, UNIX, and Microsoft Windows57
  • Informix Dynamic Server (IDS) V10 with Client SDK V2.9058
  • Informix Dynamic Server (IDS) V11.10 with Client SDK V3.058
  • Oracle 10g Release 2
  • Sybase Adaptive Server Enterprise (ASE) V15 Sybase SDK V1558
57
Only 64-bit DB2 instances can be used with 64-bit WebSphere MQ.
58
Informix Dynamic Server (IDS) and Sybase Adaptive Server Enterprise (ASE) are not supported by the WebSphere MQ Java Classes.

Connectivity

  • IBM Communications Server for Microsoft Windows V6.1.2
  • IBM Personal Communications for Microsoft Windows V5.9 (part of IBM Host Access Client Package for Multi-platforms (HACP), V6)
  • Microsoft Host Integration Server 2006 (provides 64-bit support)
  • Attachmate myEXTRA| Presentation Services, V7.11
  • Attachmate EXTRA| X-treme V9
  • TCP/IP (provided by the operating system; IP V6 feature provided on Microsoft Windows XP with Service Pack 1 or later, Microsoft Windows Server 2003 and Microsoft Windows Vista)
  • NetBIOS (provided by the operating system)
  • Sequenced Package Exchange (SPX) (provided on Microsoft Windows XP and 2003 only)
  • WebSphere MQ client applications are supported on the Citrix Presentation Server V4.5

Versions of products or components shipped with the product

JDK

  • IBM 32-bit SDK for Microsoft Windows, Java 2 Technology Edition, V5.0
  • IBM 64-bit SDK for Microsoft Windows AMD64/EM64T architecture, Java 2 Technology Edition, V5.0

GSKiit

  • IBM Global Security Kit V7D (32-bit)
  • IBM Global Security Kit V7D (64-bit)

Supported browsers for the WebSphere MQ Information Center

  • Internet Explorer (IE) 6.0, Internet Explorer 7.0
  • Mozilla 1.7
  • Firefox 1.5, Firefox 2.0
  • Konqueror (UI base mode only)

Supported application servers for the WebSphere MQ Bridge for HTTP

  • WebSphere Application Server V6.0.2.1, or later59
  • WebSphere Application Server V7, or later
  • WebSphere Application Server Community Edition V1.1, or later59
  • WebSphere Application Server Community Edition V2.1, or later
59
Only the following versions of Microsoft Windows are supported: XP Professional SP2, 2003 Server SP1, and 2003 Server x64 SP1 or SP2

Multi-instance queue managers

A networked storage device accessed by the Common Internet File System (CIFS) protocol used by Microsoft Windows networks is required.

The program's specifications and specified operating environment information may be found in documentation accompanying the program, if available, such as a README file, or other information published by IBM, such as an announcement letter. Documentation and other program content may be supplied only in the English language.

Compatibility

WebSphere MQ Advanced Message Security for z/OS V7.0.1 is upwardly compatible with WebSphere MQ applications using the message level protection function from WebSphere MQ Extended Security Edition for z/OS V6.0.

Limitations

For additional information, refer to Usage restriction topic in the Terms and conditions section of this announcement, or to the license information document that is available on the IBM Software License Agreement website

http://www.ibm.com/software/sla/sladb.nsf

Planning information

Packaging

The WebSphere MQ Advanced Message Security V7.0.1 Media Pack comprises of:

  • WebSphere MQ Advanced Message Security V7.0.1 DVD
  • Quick Start Guide

Security, auditability, and control

WebSphere MQ Advanced Message Security uses the security and auditability features of the host software.

The customer is responsible for evaluation, selection, and implementation of security features, administrative procedures, and appropriate controls in application systems and communication facilities.



Back to topBack to top
 
Top rule
Ordering information
Bottom rule

This product is only available via Passport Advantage. It is not available as shrinkwrap.

Product information

Licensed function title             Product group   Product
                                                    category
 
IBM WebSphere MQ Advanced Message   IBM             WebSphere
Security                            Application
                                    Integration
                                    Middleware
                                    Other
Program name                          PID        Charge unit
                                      number     description
 
IBM WebSphere MQ Advanced Message     5724-Z94   Per Processor
 Security                                         Value Unit for
                                                  Linux on System z
IBM WebSphere MQ Advanced Message     5724-Z94   Per Processor
 Security                                         Value Unit (PVU)

Charge metrics definitions

Pprocessor Value Unit (PVU)

PVU is a unit of measure by which the program can be licensed. The number of PVU entitlements required is based on the processor technology (defined within the PVU Table by Processor Value, Brand, Type and Model Number athttp://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html) and the number of processors made available to the program. IBM continues to define a processor, for the purpose of PVU-based licensing, to be each processor core on a chip. A dual-core processor chip, for example, has two processor cores

Licensee can deploy the program using either Full Capacity licensing or Virtualization Capacity (Sub-Capacity) licensing according to the Passport Advantage Sub-Capacity Licensing Terms (see webpage below). If using Full Capacity licensing, Licensee must obtain PVU entitlements sufficient to cover all activated processor cores60 in the physical hardware environment made available to or managed by the program, except for those servers from which the program has been permanently removed. If using Virtualization Capacity licensing, Licensee must obtain entitlements sufficient to cover all activated processor cores made available to or managed by the program, as defined according to the Virtualization Capacity License Counting Rules at

http://www.ibm.com/software/lotus/passportadvantage/Counting_Software_licenses_using_specific_virtualization_technologies.html

60
An Activated processor core is a processor core that is available for use in a physical or virtual server, regardless of whether the capacity of the processor core can be or is limited through virtualization technologies, operating system commands, BIOS settings, or similar restrictions.

Notes

Some programs may require licenses for the program AND what is being managed. In that case, the following applies: In addition to the entitlements required for the program directly, Licensee must obtain PVU entitlements for this program sufficient to cover the processor cores managed by the program.

Some programs may be licensed on a managed basis ONLY. In that case, the following applies: Instead of the entitlements required for the program directly, Licensee must obtain PVU entitlements for this program sufficient to cover the processor cores managed by the program.

A few programs on an exception basis may be licensed on a referenced basis. In that case, the following applies: Rather than obtaining entitlements for the activated processor cores available to the program, Licensee must obtain PVU entitlements for this program sufficient to cover the environment made available to the Referenced program as if the program itself were executing everywhere the Referenced program was executing, independent of the basis on which the Referenced program is licensed.

Express and Workgroup programs may be licensed with maximum use terms. In that case, the following applies: The maximum authorized use terms and conditions for PVU licensed IBM Express and Middleware programs can be found in the IBM Express and Middleware Licensing Guide.

PVU

PVU is a unit of measure by which this software product can be licensed. PVU entitlements are based on processor technology (defined within the PVU table61 by processor vendor, brand, type and model number). IBM continues to define a processor, for purposes of PVU-based licensing, to be each processor core on a chip. Each software product has a unique price per PVU. To determine the total cost of deploying an individual software product in a specific hardware environment, you must take the following steps:

  1. For each processor core in the hardware environment on which the software product is to be licensed, determine the PVU requirement based on its processor technology per the PVU table61.
  2. Add the PVU requirements for all processor cores in the hardware environment.
  3. Multiply the software product's price per PVU by the total number of PVUs required as determined in step 2 above.

PVU entitlements are specific to a software product and may not be exchanged, interchanged, or aggregated with PVU entitlements of another software product.

Unless you have deployed eligible sub-capacity products according to the sub-capacity terms, you must obtain PVU Proof of Entitlements (PoEs) for the maximum number of activated62 physical processor cores in the hardware environment made available to or managed61 by the software product. This is also referred to as full capacity licensing.

61
For information regarding PVU and sub-capacity licensing, including the latest PVU table, visit
http://www.ibm.com/software/lotus/passportadvantage/pvu_licensing_for_customers.html
62
Activated processor cores are physical processor cores that are available for use in a server. They include processor cores:
  • That are activated (available for use) when the server is shipped by the manufacturer
  • That are activated subsequently through activation codes purchased from the server manufacturer by the customer
  • Whose capacity can be limited by the customer through Virtualization technologies, Operating System commands and BIOS settings.

Passport Advantage program licenses

WebSphere MQ Advanced Message Security

Part description                                         Part
                                                         number
 
IBM WebSphere MQ Advanced Message Security
MQ Advanced Message Security Per Processor Value Unit    E090TLL
 Annual SW S&S Renwal
MQ Advanced Message Security Per Processor Value Unit    D0DGULL
 Lic + SW S&S 12 Mo
MQ Advanced Message Security Per Processor Value Unit    D0DGVLL
 SW S&S Reinstate 1Yr

Passport Advantage supply

MQ Advanced Message Security V7.0.0

WebSphere MQ Advanced Message Security V7.0 for          BA0ZRML
 Multiplatform Media Pack

Passport Advantage customer: Media pack entitlement details

Customers with active maintenance or subscription for the products listed are entitled to receive the corresponding media pack.

MQ Advanced Message Security V7.0.0

Entitled maintenance        Media packs description     Part
offerings description                                   number
 
IBM WebSphere MQ Advanced   WebSphere MQ Advanced       BA0ZRML
 Message Security per        Message Security V7.0 for
 Processor Value Unit        Multiplatform Media Pack
IBM WebSphere MQ Advanced   WebSphere MQ Advanced       BA0ZRML
 Message Security per        Message Security V7.0 for
 Processor Value Unit for    Multiplatform Media Pack
 Linux on System z

Cross-platform products

Cross-platform product for use on System z

Order the part numbers that follow when the product is used for either the development of code that will be deployed on System z servers or when the product will be communicating or transferring data between a distributed server and a System z server. Otherwise order from the other set of part numbers in this announcement. This set of part numbers provides the identical supply and authorization as the other set in this announcement

Cross-platform product for use on System z IFL engines

Order the part numbers that follow when the product is intended to run on the Linux operating system on System z IFL engines. If the product is not intended to run on the Linux operating system on System z IFL engines, order from the other set of part numbers in this announcement. This set of part numbers provides the identical supply and authorization as the other set in this announcement.

WebSphere MQ Advanced Message Security

Part description                                         Part
                                                         number
 
IBM WebSphere MQ Advanced Message Security
MQ Advanced Message Security Per Proc VU for Lin Sys z   E090VLL
 Annual SW S&S Rnwl
MQ Advanced Message Security Per Proc VU for Lin Sys z   D0DGYLL
 Lic + SW S&S 12 Mo
MQ Advanced Message Security Per Proc VU for Lin Sys z   D0DGZLL
 SW S&S Reinstate 1Yr


Back to topBack to top
 
Top rule
Terms and conditions
Bottom rule

The information provided in this announcement letter is for reference and convenience purposes only. The terms and conditions that govern any transaction with IBM are contained in the applicable contract documents such as the IBM International Program License Agreement, IBM International Passport Advantage Agreement, and the IBM Agreement for Acquisition of Software Maintenance.

Licensing

IBM International Program License Agreement including the License Information document and Proof of Entitlement (PoE) govern your use of the program. PoEs are required for all authorized use.

Part number products only, offered outside of Passport Advantage, where applicable, are license only and do not include Software Maintenance.

License Information form number
Program name                              Program    Form number
                                          number
 
WebSphere MQ Advanced Message Security    5724-Z94   L-APIG-856RCH

The program's License Information will be available for review on the IBM Software License Agreement website

http://www.ibm.com/software/sla/sladb.nsf
Limited warranty applies

Yes

Limited warranty

IBM warrants that when the program is used in the specified operating environment, it will conform to its specifications. The warranty applies only to the unmodified portion of the program. IBM does not warrant uninterrupted or error-free operation of the program or that IBM will correct all program defects. You are responsible for the results obtained from the use of the program.

IBM provides you with access to IBM databases containing information on known program defects, defect corrections, restrictions, and bypasses at no additional charge. For further information, consult the IBM Software Support Handbook found at

http://www.ibm.com/support/handbook

IBM will maintain this information for at least one year after the original licensee acquires the program (warranty period).

Program technical support

Technical support of a program product version or release will be available for a minimum of five years from the general availability date, as long as your Software Maintenance is in effect. This technical support allows you to obtain assistance (via telephone or electronic means) from IBM for product-specific, task-oriented questions regarding the installation and operation of the program product. Software Maintenance also provides you with access to updates (modifications or fixes), releases, and versions of the program. You will be notified, via announcement letter, of discontinuance of support with 12 months' notice. If you require additional technical support from IBM, including an extension of support beyond the discontinuance date, contact your IBM representative or IBM Business Partner. This extension may be available for a fee.

Money-back guarantee

For clarification, note that if for any reason you are dissatisfied with the program and you are the original licensee, you may obtain a refund of the amount you paid for it, if within 30 days of your invoice date you return the program and its PoE to the party from whom you obtained it. If you downloaded the program, you may contact the party from whom you acquired it for instructions on how to obtain the refund.

For clarification, note that for programs acquired under the IBM International Passport Advantage Agreement, this term applies only to your first acquisition of the program.

Volume orders (IVO)

No

Passport Advantage applies

Yes, and through the Passport Advantage website at

http://www.ibm.com/software/passportadvantage

This product is only available via Passport Advantage. It is not available as shrinkwrap.

Usage restriction

Yes

For additional information, refer to the License Information Document that is available on the IBM Software License Agreement website

http://www.ibm.com/software/sla/sladb.nsf
IBM Operational Support Services - SoftwareXcel

No

System i Software Maintenance applies

No

Educational allowance available

Not applicable.



Back to topBack to top
 
Top rule
Prices
Bottom rule

For additional information and current prices, contact your local IBM representative.

Passport Advantage

For Passport Advantage information and charges, contact your IBM representative or authorized IBM Business Partner, or authorized IBM Business Partner for Software ValueNet®, if applicable. Additional information is also available at

http://www.ibm.com/software/passportadvantage

Business Partner information

If you are an IBM Business Partner -- Distributor for Workstation Software acquiring products from IBM, you may link to Passport Advantage Online for resellers where you can obtain Business Partner pricing information. An IBM ID and password are required.

https://www.ibm.com/software/howtobuy/passportadvantage/paoreseller


Back to topBack to top
 
Top rule
Order now
Bottom rule

To order, contact the Americas Call Centers or your local IBM representative, or your IBM Business Partner.

To identify your local IBM representative or IBM Business Partner, call 800-IBM-4YOU (426-4968).

Phone:      800-IBM-CALL (426-2255)
Fax:        800-2IBM-FAX (242-6329)
Internet:   callserv@ca.ibm.com
Mail:       IBM Teleweb Customer Support
            ibm.com® Sales Execution Center, Americas North
            3500 Steeles Ave. East, Tower 3/4
            Markham, Ontario
            Canada
            L3R 2Z1

Reference: YE001

The Americas Call Centers, our national direct marketing organization, can add your name to the mailing list for catalogs of IBM products.


Note: Shipments will begin after the planned availability date.
Trademarks

IMS, z/VSE, SupportPac, eServer, General Parallel File System and GPFS are trademarks of IBM Corporation in the United States, other countries, or both.

WebSphere, IBM, zSeries, CICS, DB2, z/OS, System z, MQSeries, DataPower, Tivoli, OMEGAMON, Passport Advantage, AIX, pSeries, System x, System p, System i, System z9, VisualAge, Express, TXSeries, Informix, iSeries, Rational, ValueNet and ibm.com are registered trademarks of IBM Corporation in the United States, other countries, or both.

Windows and Microsoft are registered trademarks of Microsoft Corporation in the United States, other countries, or both.

Intel and Itanium are registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.

Terms of use

IBM products and services which are announced and available in your country can be ordered under the applicable standard agreements, terms, conditions, and prices in effect at the time. IBM reserves the right to modify or withdraw this announcement at any time without notice. This announcement is provided for your information only. Additional terms of use are located at:

http://www.ibm.com/legal/us/en/

For the most current information regarding IBM products, consult your IBM representative or reseller, or visit the IBM worldwide contacts page

http://www.ibm.com/planetwide/us/

Terms of use

Share this page

Digg Linked In

Contact IBM

Feedback

-->