Migration guide for IBM WebSphere Message Broker on HP-UX

Transcription

1 Technical white paper Migration guide for IBM WebSphere Message Broker on HP-UX Migrating from WebSphere Message Broker on HP-UX for HP 9000 servers to WebSphere Message Broker on HP-UX for Integrity servers Table of contents Executive summary 3 Reasons to migrate 3 Migration process 3 Planning the migration 4 Performing the migration 4 Further information 5 WebSphere Message Broker on HP-UX platforms 5 WebSphere Message Broker support lifecycle 5 WebSphere Message Broker support of HP-UX for HP 9000 servers and HP-UX for Integrity servers 6 WebSphere Message Broker and WebSphere MQ 6 WebSphere MQ pre-requisite 6 WebSphere Message Broker and WebSphere MQ interoperability 7 Understanding potential migration issues with WebSphere Message Broker No Rules and Formatter extension available for WebSphere Message Broker on HP-UX for Integrity servers 8 Database version support 8 32-bit and 64-bit execution groups 8 Shared Object Library file-name extension changed from.sl to.so 8 Different Switch file settings 8 Other minor differences 9 Summary for potential migration issues 9

2 Summary 9 References 9 Appendix A. Introduction to WebSphere Message Broker 10 History of WebSphere Message Broker 10 Related products 10 Appendix B. Obtaining WebSphere Message Broker software kits 10 WebSphere Message Broker base kits 11 WebSphere Message Broker fix packs 11 Appendix C. Reasons to migrate from HP-UX for HP 9000 servers to HP-UX for Integrity servers 12 Appendix D. Comparison of WebSphere Message Broker 6.1 system requirements for HP-UX platforms 13 Introduction to WebSphere Message Broker system requirements 13 WebSphere Message Broker 6.1 system requirements comparison for HP-UX platforms 13 Appendix E. Online documentation differences between WebSphere Message Broker 6.1 for HP-UX for HP 9000 and WebSphere Message Broker 6.1 for HP-UX for Integrity 15 For more information 18

3 Executive summary This paper provides information to help migrate an IBM WebSphere Message Broker deployment from HP-UX for HP 9000 (PA-RISC based) servers to HP-UX for HP Integrity (Intel Itanium based) servers. This paper: Lists reasons why you should consider migrating your IBM WebSphere Message Broker deployment from HP-UX for HP 9000 servers to HP-UX for HP Integrity servers. Outlines the process to migrate from a WebSphere Message Broker deployment from HP-UX for HP 9000 servers to HP-UX for Integrity servers. Lists the WebSphere Message Broker versions currently available and supported on the HP-UX platforms, along with their support lifecycle. Lists WebSphere Message Broker version interoperability with WebSphere MQ versions. Lists potential issues that might be encountered in migrating from a WebSphere Message Broker deployment on HP-UX for HP 9000 servers to a WebSphere Message Broker deployment on HP-UX for Integrity servers. This paper focuses on IBM WebSphere Message Broker version 6.1, because that is the only currently supported version that supports both HP-UX for HP 9000 servers and HP-UX for Integrity servers. The focus of this paper is the broker runtime environment, because the broker toolkit is not supported on either HP-UX platform. Target audience: This paper is intended to assist system administrators and developers with the migration of an IBM WebSphere Message Broker deployment from HP-UX for HP 9000 servers to HP-UX for Integrity servers. Note This paper assumes that the reader is familiar with WebSphere Message Broker, although a brief summary is given in Appendix A. Introduction to WebSphere Message Broker, and additional information is given in Appendix B. Obtaining WebSphere Message Broker software kits. Reasons to migrate There are many reasons to migrate from using WebSphere Message Broker on HP-UX for HP 9000 servers to using WebSphere Message Broker on HP-UX for Integrity servers. These include: Longer support lifecycles for application, operating system and server hardware Take advantage of latest technologies such as HP Converged Infrastructure and HP Converged Cloud Performance Functionality Cost of ownership Ease of transition Appendix C. Reasons to migrate from HP-UX for HP 9000 servers to HP-UX for Integrity servers provides further detail on the above reasons to migrate. In summary there is a compelling value proposition to migrate from using WebSphere Message Broker on HP-UX for HP 9000 servers to using WebSphere Message Broker on HP-UX for Integrity servers. Migration process The focus of this paper is migrating from using WebSphere Message Broker on HP-UX for HP 9000 servers to using WebSphere Message Broker on HP-UX for Integrity servers. 3

4 Planning the migration There are many factors to consider in planning the migration, including: Choose your target WebSphere Message Broker version Need to consider support lifecycle and which versions of HP-UX for Integrity servers are supported. This is covered in the WebSphere Message Broker on HP-UX platforms section of this paper. Choose your target WebSphere MQ version WebSphere MQ is a pre-requisite of all versions of WebSphere Message Broker. There are interoperability restrictions. This is covered in the WebSphere Message Broker and WebSphere MQ section of this paper. Choose your target HP-UX for Integrity servers operating system version This is most likely to be HP-UX 11i v3, which is the latest version. Choose your target HP Integrity server hardware This will depend upon the deployment requirements. Consider whether application processes in the target environment will operate in 32-bit or 64-bit mode WebSphere Message Broker for HP-UX for Integrity servers only supports 64-bit execution groups. Ensure any additional software applications used in the HP-UX for HP 9000 servers source environment are available for the HP-UX for Integrity servers target environment If not, then source alternative applications. Check that the target environment offers all of the functionality used in the source environment The Understanding potential migration issues with WebSphere Message Broker 6.1 section of this paper addresses this for WebSphere Message Broker 6.1. If required functionality is missing from the target environment, then investigate further whether/how the missing functionality can be worked-around. Phased migration It may be that a phased migration approach is chosen for example, to migrate from WebSphere Message Broker 6.1 on HP-UX for HP 9000 servers to WebSphere Message Broker 6.1 on HP-UX for Integrity servers, and then subsequently upgrade WebSphere Message Broker to 8.0 on the target platform. This document will help with the first phase of such a migration, and the IBM online documentation for WebSphere Message Broker 8.0 (see References) will help with the second phase of the migration (for example, see the Migrating section of the online documentation). Performing the migration This section assumes that: The target environment has been decided upon that is, the version of WebSphere Message Broker, the version of WebSphere MQ, and the version of HP-UX for Integrity, etc., have all been chosen. You have read the subsequent section titled Understanding potential migration issues with WebSphere Message Broker 6.1 and no major problems have been identified. Once you have set up the target HP-UX for Integrity environment complete with WebSphere MQ and WebSphere Message Broker installed, and any other additional software applications required you can consider creating a new Message Broker environment (including queue manager) on the target HP-UX for Integrity system. Note IBM does not support the migration of the Message Broker environment via backup and restore because the migration is cross-platform. 4

5 The following steps outline how to create the Message Broker environment on the HP-UX for Integrity servers system. Create the WebSphere MQ queue manager and message queue definitions. Create the Message Broker. Build any user-defined nodes. Deploy the Message Broker artifacts (message flows, message sets, bar/jar files, nodes, etc.). Start the queue manager(s). Start the broker instance(s). Further information As referenced in the Planning the migration section of this document, the remainder of this document contains the following sections to help you to plan your WebSphere Message Broker migration. WebSphere Message Broker on HP-UX platforms WebSphere Message Broker and WebSphere MQ Understanding potential migration issues with WebSphere Message Broker 6.1 WebSphere Message Broker on HP-UX platforms WebSphere Message Broker has been ported to various platforms, including several UNIX variants, Linux, Microsoft Windows and z/os. WebSphere Message Broker first supported HP-UX for HP 9000 servers at the MQSeries Integrator v2.0 release circa The last WebSphere Message Broker version to support HP-UX for HP 9000 was 6.1, which was released in 2008 (the same year that HP stopped selling HP 9000 servers). WebSphere Message Broker v6.0 was the first version ported to and supported on HP-UX for Integrity servers, and the latest WebSphere Message Broker v8.0 release still supports HP-UX for Integrity. Note that IBM makes separate software kits for WebSphere Message Broker for HP-UX for HP 9000 servers and for WebSphere Message Broker for HP-UX for Integrity servers see Appendix B. Obtaining WebSphere Message Broker software kits for further information. WebSphere Message Broker support lifecycle IBM s Software Support Lifecycle Policy at describes their Enhanced 5+3 Support policy, whereby a software application is supported for a minimum of 5 years from release, with the option of extended support at increased cost for a further 3 years. This policy applies to most versions of WebSphere Message Broker for both HP-UX platforms, although customers should check this with their IBM representative before starting a migration. Information on the support lifecycle of the various WebSphere Message Broker versions can be found at 01.ibm.com/software/support/lifecycle/index_w.html. Table 1 summarizes when recent WebSphere Message Broker versions were made available, and when standard support ends. Table 1. WebSphere Message Broker standard support lifecycles WebSphere Message Broker version General Availability End of Standard Support WebSphere Business Integration Message Broker v5.0 June 2003 September 2008 WebSphere Message Broker v6.0 April 2006 April 2011 WebSphere Message Broker v6.1 June 2008 Estimated June 2013 WebSphere Message Broker v7.0 December 2009 Estimated December 2014 WebSphere Message Broker v8.0 December 2011 Estimated December

6 At the time of writing this document: WebSphere Business Integration Message Broker v5.0 and WebSphere Message Broker v6.0 are out of standard support, and thus are not considered by this document. WebSphere Message Broker v6.1, v7.0 and v8.0 are in standard support. WebSphere Message Broker support of HP-UX for HP 9000 servers and HP-UX for Integrity servers The IBM web page has links to further web pages that describe the system requirements for a specific WebSphere Message Broker version for all supported platforms. Table 2 summarizes the WebSphere Message Broker support for different HP-UX versions on the HP 9000 and HP Integrity server platforms. Table 2. WebSphere Message Broker support of HP-UX for HP 9000 servers and HP-UX for Integrity servers HP-UX 11i v1 on HP 9000 HP-UX 11i v2 on HP 9000 HP-UX 11i v2 on HP Integrity HP-UX 11i v3 on HP 9000 HP-UX 11i v3 on HP Integrity WebSphere Message Broker v6.1 Not Supported Supported Supported Supported Supported WebSphere Message Broker v7.0 Not Supported Not Supported Supported Not Supported Supported WebSphere Message Broker v8.0 Not Supported Not Supported Supported Not Supported Supported From Table 2 it can be seen that WebSphere Message Broker v6.1 is the only release that is currently supported on both HP-UX for HP 9000 servers and HP-UX for Integrity servers. For information on the end-of-support dates for HP-UX versions, please refer to the web page titled HP-UX Operating System Release History, and sub-titled End of Sales & End of Factory Support at hp.com/softwarereleases/releasesmedia2/history/slide2.html. WebSphere Message Broker and WebSphere MQ WebSphere MQ pre-requisite WebSphere Message Broker requires WebSphere MQ. A separate paper entitled Migration guide for IBM WebSphere MQ on HP-UX (see References) addresses migrating from WebSphere MQ on HP-UX for HP 9000 servers to WebSphere MQ on HP-UX for Integrity servers, and is recommended reading. The WebSphere MQ migration paper has a section titled Comparing HP-UX for HP 9000 and HP Integrity servers that contains useful information not duplicated here. 6

7 WebSphere Message Broker and WebSphere MQ interoperability Table 3 shows the version interoperability between WebSphere Message Broker and WebSphere MQ, taken from IBM s web pages for the System Requirements for the different WebSphere Message Broker versions. Table 3. WebSphere Message Broker interoperability with WebSphere MQ on HP-UX platforms WebSphere Message Broker version HP-UX Platform WebSphere MQ versions supported 6.1 HP-UX for HP 9000 servers (11i v2 & 11i v3) WebSphere MQ v6.0 WebSphere MQ v7.0 WebSphere MQ v HP-UX for Integrity servers (11i v2 & 11i v3) WebSphere MQ v6.0 WebSphere MQ v7.0 WebSphere MQ v HP-UX for Integrity servers (11i v2 & 11i v3) WebSphere MQ v HP-UX for Integrity servers (11i v2 & 11i v3) WebSphere MQ v Understanding potential migration issues with WebSphere Message Broker 6.1 Two sources of online information about WebSphere Message Broker 6.1 were searched to identify differences that could cause potential migration issues from HP-UX for HP 9000 servers to HP-UX for Integrity servers. The online information sources are listed below, along with reference to the Appendix section of this document that itemizes the differences: System requirements for WebSphere Message Broker 6.1 see Appendix D WebSphere Message Broker v6.1 online documentation see Appendix E Appendices D and E list all of the documented differences in WebSphere Message Broker 6.1 support of, or functionality on, HP-UX for HP 9000 servers and HP-UX for Integrity servers. The reader should not be put off by the number of differences because probably only a subset of the differences will affect your migration. The rest of this section examines the main potential migration issues arising from the searches of the system requirements and documentation. It includes references such as WMB6.1SR#07 and WMB6.1DOC#05, where: WMB6.1SR#07 Refers to the WebSphere Message Broker 6.1 system requirements comparison table, row 7. (See Table D.1 in Appendix D). WMB6.1DOC#05 Refers to the WebSphere Message Broker 6.1 documentation differences table, row 5. (See Table E.1 in Appendix E). 7

8 No Rules and Formatter extension available for WebSphere Message Broker on HP-UX for Integrity servers References: WMB6.1SR#01, WMB6.1SR#07 The Rules and Formatter extension to WebSphere Message Broker is available for HP-UX for HP 9000 servers, but not available for HP-UX for Integrity servers. The Supported Migration Paths section of the online WebSphere Message Broker documentation provides some guidance on this. Database version support References: WMB6.1SR#04, WMB6.1DOC#14, WMB6.1DOC#17 WebSphere Message Broker supports older database versions on HP-UX for HP 9000 than on HP-UX for Integrity. This could necessitate a database upgrade as part of the migration progress. 32-bit and 64-bit execution groups References: WMB6.1DOC#01, WMB6.1DOC#05, WMB6.1DOC#06, WMB6.1DOC#13, WMB6.1DOC#16, WMB6.1DOC#18 WebSphere Message Broker v6.1 on HP-UX for HP 9000 supports both 32-bit and 64-bit execution groups, whereas WebSphere Message Broker v6.1 on HP-UX for Integrity only supports 64-bit execution groups. The implication here is that if WebSphere Message Broker user defined nodes have been written in C or Java and built 32-bit on HP-UX for HP 9000, then they will have to be built 64-bit on HP-UX for Integrity. This could require some additional migration effort if the code makes assumptions about the sizes of data types. Note If you are moving from 32-bit execution groups on HP-UX for HP 9000 servers to 64-bit execution groups on HP-UX for Integrity servers, then expect an increase in the memory footprint of the processes involved. Note also that HP-UX for Integrity servers has greater memory requirements than HP-UX for HP 9000 servers, due to architectural differences. This difference is due to the increased size of the instruction-code of application binaries for Integrity over HP 9000 (the data-space requirements are the same). Therefore, when planning a migration, ensure that the target Integrity server has at least 25% more memory than the original HP 9000 server (assuming the same workload). Shared Object Library file-name extension changed from.sl to.so References: WMB6.1DOC#02, WMB6.1DOC#03, WMB6.1DOC#04, WMB6.1DOC#05 On HP-UX for HP 9000 servers the shared object library filename extension is.sl, whereas on HP-UX for Integrity servers the extension is.so. Build scripts may need updating to use the new extension. Different Switch file settings References: WMB6.1DOC#08, WMB6.1DOC#09 In the Changing the XA resource manager definitions section of the IBM documentation for WebSphere Message Broker 6.1, there are different switch file settings for the two HP-UX platforms both in the main part of the filename, and in the filename extension. 8

9 Other minor differences WMB6.1DOC#07: The command to install WebSphere Message Broker maintenance updates and program fixes is setuphp on HP-UX for HP 9000 servers and setuphpia64 on HP-UX for Integrity servers. WMB6.1DOC#11: More disk space is required to install and run WebSphere Message Broker 6.1 on HP-UX for Integrity than on HP-UX for HP 9000 WMB6.1DOC#12: There are different compiler versions for HP-UX for HP 9000 and HP-UX for Integrity. WMB6.1DOC#15: There are minor differences in directory structure for WebSphere Message Broker 6.1 once installed. Summary for potential migration issues Of the potential migration issues listed above, the two major ones are likely to be: WebSphere Message Broker on HP-UX for Integrity only supports a 64-bit execution group, whereas on HP-UX for HP 9000 servers WebSphere Message Broker supported both 32-bit and 64-bit execution groups No Rules and Formatter extension to WebSphere Message Broker on the HP-UX for Integrity servers platform The impact of these two migration issues on a WebSphere Message Broker deployment is hard to quantify because it depends upon: How 32-bit/64-bit clean the code is for user defined nodes How extensive the use of the Rules and Formatter extensions are It is suggested that a trial port of a sample component is tried for example, trying to build a user-defined node for 64-bit addressing to better understand the likely effort involved for your deployment. Summary This paper listed reasons to migrate your WebSphere Message Broker deployment from HP-UX for HP 9000 servers to HP-UX for Integrity servers. This paper outlined the process to migrate from a WebSphere Message Broker deployment on HP-UX for HP 9000 servers to a WebSphere Message Broker deployment on HP-UX for Integrity servers. This paper listed the WebSphere Message Broker versions currently available and supported on HP-UX platforms. This paper listed WebSphere Message Broker version interoperability with WebSphere MQ versions. This paper listed potential issues that might be encountered in migrating from a WebSphere Message Broker deployment on HP-UX for HP 9000 servers to a WebSphere Message Broker deployment on HP-UX for Integrity servers. References Migration guide for IBM WebSphere MQ on HP-UX WebSphere Message Broker v6.1 online documentation WebSphere Message Broker v7.0 online documentation WebSphere Message Broker v8.0 online documentation 9

10 Appendix A. Introduction to WebSphere Message Broker WebSphere Message Broker is an integration broker product that allows business information to flow as messages between distributed disparate applications. WebSphere Message Broker has WebSphere MQ message queuing middleware previously known as MQSeries as a pre-requisite. The WebSphere Message Broker v6.1 version also has the IBM DB2 database as a pre-requisite. (The DB2 requirement is dropped from future versions of WebSphere Message Broker, starting with v7.0.) A key difference between WebSphere Message Broker and WebSphere MQ relates to the message data. WebSphere MQ has no knowledge of the structure of the message data, whereas WebSphere Message Broker does. WebSphere Message Broker can be used to set up a message flow that applies rules to transform message data. For example, if application A transmits and receives message data in extensible Markup Language (XML) format, and application B transmits and receives message data in Comma Separated Values (CSV) format, then message flows can be set up in WebSphere Message Broker to transform messages between the two formats so that the two applications can communicate without being modified. Thus WebSphere Message Broker can be deployed in a Service Orientated Architecture (SOA) as an Enterprise Service Bus (ESB), providing connectivity between applications and services. History of WebSphere Message Broker WebSphere Message Broker was originally called MQSeries Integrator, and the MQSI acronym is still used in the product s commands (such as mqsicreate, mqsiservice, etc.) and directory names (such as /opt/ibm/mqsi and /var/mqsi on HP-UX). MQSeries Integrator was incorporated into the WebSphere brand and went through a couple of name changes first WebSphere MQ Integrator at version 2.1, then WebSphere Business Integration Message Broker at version 5.0 before finally being known as WebSphere Message Broker starting with the version 6.0 release. Related products The focus of this document is the core WebSphere Message Broker product. Products closely associated with the core WebSphere Message Broker product, are: WebSphere Event Broker This is essentially a subset of WebSphere Message Broker. WebSphere Event Broker was discontinued in 2007, at the v6.0 release. WebSphere Message Broker with Rules and Formatter This is a superset of WebSphere Message Broker, with additional functionality Note that while WebSphere Event Broker and WebSphere Message Broker with Rules and Formatter were available for HP-UX for HP 9000 servers, neither product is supported on HP-UX for Integrity. The WebSphere Message Broker documentation for versions 6.1, 7.0 and 8.0 all include sections entitled Supported Migration Paths. Migration from WebSphere Event Broker or WebSphere Message Broker with Rules and Formatter to a later version of WebSphere Message Broker (without Rules and Formatter) is described in those sections. Appendix B. Obtaining WebSphere Message Broker software kits IBM makes separate software kits available for: WebSphere Message Broker on HP-UX for HP 9000 servers WebSphere Message Broker on HP-UX for Integrity servers When installing WebSphere Message Broker on HP-UX, ensure that you have the appropriate kit for the target HP-UX server platform. 10

11 A WebSphere Message Broker installation typically requires the installation of two software kits: First, a WebSphere Message Broker base kit is required. Second, a WebSphere Message Broker fix pack is typically required, to patch the base kit up to the latest maintenance level. Fix packs can also provide new functionality. WebSphere Message Broker base kits Customers or partners who subscribe to IBM PartnerWorld s Software Access Option or a super-set package that includes the Software Access Option can obtain WebSphere Message Broker base kits from IBM s PartnerWorld website ibm.com/partnerworld/. Note that access to the IBM software kits via the PartnerWorld portal requires an annual subscription for the Software Access Option, and user sign-in. Table B.1 lists the identification-string (ID) used on IBM s PartnerWorld website for the WebSphere Message Broker base kits for HP-UX platforms. Note how IBM generally refers to HP-UX for HP 9000 servers as HP-UX, and refers to HP-UX for Integrity servers as HP Itanium. Thus the right column of Table 3 shows the correct HP-UX platform name. Table B.1. IBM WebSphere Message Broker base kits for HP-UX on the IBM PartnerWorld website ID Description HP-UX Platform C19YPML WebSphere Message Broker v6.1 for HP-UX HP-UX for HP 9000 servers C19YXML WebSphere Message Broker v6.1 for HP Itanium HP-UX for Integrity servers CZED7ML WebSphere Message Broker v for HP Itanium HP-UX for Integrity servers CI424ML WebSphere Message Broker v8.0 for HP Itanium HP-UX for Integrity servers WebSphere Message Broker fix packs IBM makes consolidated maintenance updates available periodically for WebSphere Message Broker. The web page entitled Recommended fixes for WebSphere Message Broker at ibm.com/support/docview.wss?uid=swg lists the latest fix pack information for various platforms, including HP-UX for HP 9000 servers, and HP-UX for Integrity servers. Note that there are separate WebSphere Message Broker fix packs for HP-UX for HP 9000 servers and for HP-UX for Integrity servers. Table B.2 shows the latest fix pack versions current at the time of creating this document for currently supported WebSphere Message Broker versions for HP-UX for HP 9000 servers and for HP-UX for Integrity servers. Table B.2. IBM WebSphere Message Broker fix packs for HP-UX WebSphere Message Broker version IBM terminology for HP-UX Platform HP-UX platform name Latest fix pack version (at time document created) 6.1 HP-UX PA-RISC HP-UX for HP 9000 servers HP Itanium HP-UX for Integrity servers HP Itanium HP-UX for Integrity servers HP Itanium HP-UX for Integrity servers n/a 11

12 Appendix C. Reasons to migrate from HP-UX for HP 9000 servers to HP-UX for Integrity servers There are many reasons to migrate from using WebSphere Message Broker on HP-UX for HP 9000 servers to using WebSphere Message Broker on HP-UX for Integrity servers. These include: Longer support lifecycles for application, operating system and server hardware The latest version of WebSphere Message Broker v8.0 circa 2011 at the time this document was created is supported on HP-UX for Integrity servers, whereas the last WebSphere Message Broker version to support HP-UX for HP 9000 servers was v6.1 circa The end-of-standard-support dates for IBM software products are typically about 5 years after the product version was released. Thus WebSphere Message Broker for HP-UX for Integrity servers has a longer supported future than WebSphere Message Broker for HP-UX for HP 9000 servers. The HP-UX operating system has a longer support life planned for Integrity servers than for HP 9000 servers. From hp.com/softwarereleases/releases-media2/history/slide2.html, the end-of-support date for HP-UX 11i v3 for Integrity servers is currently 31-December-2022, whereas the end-of-support date for HP-UX 11i v3 for HP 9000 servers is currently 31-December HP Integrity servers are supported further into the future than HP 9000 servers. Typically HP servers are supported for a minimum of 5 years from the end-of-sales date for that specific server model. The end-of-sales date for HP 9000 servers was 31-December-2008, whereas HP Integrity servers are still currently on sale. See hp.com/go/hpuxservermatrix for support lifecycles for specific server models. Take advantages of latest technologies such as HP Converged Infrastructure and HP Converged Cloud The latest HP Integrity servers most of which are available as server blades fully integrate with HP Converged Infrastructure. HP Converged Infrastructure is about integrating servers, storage, networking, security, power, cooling, and facilities into shared pools of interoperable resources; all managed through a common management platform. This leads to a shared-services model for the information technology (IT) resources, enabling them to be rapidly deployed, to better meet business requirements. For further information see hp.com/go/ci. HP 9000 servers are not part of HP Converged Infrastructure. HP Converged Cloud embraces both traditional IT and three types of cloud computing: private cloud, managed cloud and public cloud. HP Converged Cloud uses HP Converged Infrastructure components such as HP Integrity servers as the foundation. The HP Converged Cloud solution enables you to build on-premise cloud services and to consume off-premise cloud services, thus resulting in a hybrid environment that can adapt to meet changing business needs. For further information on HP Converged Cloud see HP Converged Cloud does not support HP 9000 servers. Performance HP Integrity servers are based on Itanium processors whereas HP 9000 servers are based on PA-RISC processors. Itanium processors are available with more cores-per-processor than PA-RISC (currently 4 and 2 respectively), and an Itanium core is generally faster than a comparable PA-RISC core. Thus an HP Integrity server of the same formfactor as an HP 9000 server will be capable of much greater performance. Functionality The latest releases of WebSphere Message Broker such as v7.0 and v8.0 (which are both available for HP-UX for Integrity servers and not for HP-UX for HP 9000 servers) provide new functionality compared to WebSphere Message Broker v6.1 (which is available for both HP-UX platforms). For example, WebSphere Message Broker v7.0 introduced the WebSphere Message Broker Explorer graphical user interface tool. Cost of ownership There are many aspects to total cost of ownership including power and cooling, and system management. The latest Integrity servers are more power-efficient than the HP 9000 servers, resulting in reduced power and cooling costs. HP-UX is managed in the same way on HP Integrity servers and HP 9000 servers, preserving any investment made in HP-UX system management training. Ease of transition HP-UX was ported from HP 9000 servers to Integrity servers, and has mostly common source-code providing highly compatible interfaces on both platforms for users, programmers and system administrators. This means it is easy for users, programmers and system administrators to transition from HP-UX for HP 9000 servers to HP-UX for Integrity servers. Current users of WebSphere Message Broker on HP-UX for HP 9000 servers may consider moving to WebSphere Message Broker on Linux for Intel x86 rather than going to WebSphere Message Broker on HP-UX for Integrity 12

13 servers. However, going to Linux for Intel x86 is more of a port than a migration, because the Linux operating system is different from HP-UX. While UNIX shell commands and utilities are very similar on HP-UX and Linux, system management tasks are quite different, and the layered product environment is likely to be different too (depending which layered products have been deployed). For example, customers currently using the HP C compiler for HP-UX for HP 9000 servers will find the HP C compiler for HP-UX for Integrity servers more compatible in terms of compiler options, etc. than using the GNU C compiler for Linux for Intel x86. Also there are architectural differences to consider, such as Linux on Intel x86 being little-endian whereas both HP-UX for HP 9000 servers and HP-UX for Integrity servers are big-endian, which might be an issue if migrating binary data. In summary there is a compelling value proposition to migrate from using WebSphere Message Broker on HP-UX for HP 9000 servers to using WebSphere Message Broker on HP-UX for Integrity servers. Appendix D. Comparison of WebSphere Message Broker 6.1 system requirements for HP-UX platforms Introduction to WebSphere Message Broker system requirements IBM has a web page at that has links to the system requirements web pages for currently supported versions of WebSphere Message Broker (WMB) on all the supported platforms. Recall from Tables 1 and 2 that WMB 6.1 is the only currently supported version of WebSphere Message Broker that is available for both HP-UX for HP 9000 servers and HP-UX for Integrity servers. The links below are for the system requirements for WebSphere Message Broker 6.1 for the two HP-UX platforms: IBM System Requirements for WebSphere Message Broker v6.1 on HP-UX for HP 9000 (PA-RISC) servers IBM System Requirements for WebSphere Message Broker v6.1 on HP-UX for Integrity (Itanium) servers WebSphere Message Broker 6.1 system requirements comparison for HP-UX platforms This section compares the system requirements of WebSphere Message Broker 6.1 for the two HP-UX platforms. The comparison is from the perspective of migrating from WebSphere Message Broker 6.1 on HP-UX for HP 9000 servers to the same WMB 6.1 version on HP-UX for Integrity servers. The system requirements web pages for WebSphere Message Broker 6.1 for both HP-UX platforms are in a table format. Each row in the table has a name (for example, Please read first, Hardware Requirements, etc.). Text in the comparison table is color-coded per the key below. Think of the text-colors as being similar to traffic lights, with red text meaning a potential migration issue, orange text being a warning, green text being equality (so no migration issue), and blue text being unique functionality for WebSphere Message Broker on HP-UX for Integrity (also no migration issue; and provides a potential opportunity for improvement). Key: Text in red indicates an area where WebSphere Message Broker support of HP-UX for Integrity servers is deficient when compared to WebSphere Message Broker support of HP-UX for HP 9000 servers. Text in orange indicates an area where WebSphere Message Broker support of HP-UX for Integrity servers is different when compared to WebSphere Message Broker support of HP-UX for HP 9000 servers. Text in green indicates an area where WebSphere Message Broker support of HP-UX for Integrity servers is equivalent when compared to WebSphere Message Broker support of HP-UX for HP 9000 servers. Text in blue indicates an area where WebSphere Message Broker support of HP-UX for Integrity servers has additional support when compared to WebSphere Message Broker support of HP-UX for HP 9000 servers. 13

14 Table D.1 summarizes how the WebSphere Message Broker 6.1 system requirements compare. Entries within Table D.1 are indexed by the row name within the table that they appear in on the IBM System Requirements web page (for example, Please read first ), and by a Table Index String that is used elsewhere in this paper to reference individual rows of Table D.1. An example Table Index String iswmb6.1sr#01, where WMB6.1 represents the version of WebSphere Message Broker, SR represents System Requirements, and #01 represents the first row entry in Table D.1. Table D.1. System requirements comparison for WebSphere Message Broker 6.1 on HP-UX for HP 9000 servers and HP-UX for Integrity servers Row Name in IBM System Requirements table, and Table Index String Comment Please Read First WMB6.1SR#01 Hardware requirements WMB6.1SR#02 Operating Systems WMB6.1SR#03 Databases WMB6.1SR#04 WebSphere MQ WMB6.1SR#05 Supported Adapters WMB6.1SR#06 Rules and Formatter Extension WMB6.1SR#07 WebSphere Service Registry and Repository WMB6.1SR#08 Same minimum JRE version of 1.5 for both HP-UX platforms. Same JMS v1.1 provider supported. The Rules and Formatter extension to WMB is supported on HP-UX for HP 9000 servers, but not on HP-UX for Integrity servers. HP 9000 (PA-RISC) and Integrity (Itanium) are different servers. The requirement for both platforms is 64-bit hardware. Both WebSphere Message Broker v6.1 variants support HP-UX 11i v2 and HP-UX 11i v3 on their respective platforms. These HP-UX versions are all 64-bit. Java patches are required for both HP-UX platforms. WMB 6.1 supports IBM DB2 v8.2 & v9.1 on both HP-UX platforms. WMB 6.1 for HP-UX for Integrity additionally supports DB2 9.5 & 9.7. WMB 6.1 supports Oracle 10gR1, 10gR2, 11gR1 and 11gR2 on both HP-UX platforms. WMB 6.1 on HP-UX for HP 9000 servers also supports Oracle 9iR2. WMB 6.1 supports Sybase ASE 12.5 & 15.0 on both HP-UX platforms. WMB 6.1 supports Informix Dynamic Server v10 on both HP-UX platforms. WMB 6.1 on HP-UX for HP 9000 servers also supports Informix Dynamic Server v9.40. WMB 6.1 on HP-UX for Integrity servers also supports Microsoft SQL Server 2005 & WMQ 6.0, WMQ 7.0 and WMQ are supported by WMB 6.1 on both HP-UX platforms. WMB 6.1 supports adapters for SAP, Siebel and PeopleSoft on both HP-UX platforms. As noted in Please Read First category section (WMB6.1SR#01), the Rules and Formatter extension to WMB that is supported on HP-UX for HP 9000 servers is not supported by WMB on HP-UX for Integrity servers. WMB 6.1 supports WebSphere Service Registry and Repository and 7.0 on both HP-UX platforms. The potential migration issues listed in Table D.1 in red text can be summarized as: The Rules and Formatter extension to WebSphere Message Broker is supported on HP-UX for HP 9000, but not on HP-UX for Integrity. (WMB6.1SR#01, WMB6.1SR#07) WebSphere Message Broker supports older database versions on HP-UX for HP 9000 than on HP-UX for Integrity. (WMB6.1SR#04) 14

15 Appendix E. Online documentation differences between WebSphere Message Broker 6.1 for HP-UX for HP 9000 and WebSphere Message Broker 6.1 for HP-UX for Integrity IBM online documentation for WebSphere Message Broker (see References for version-specific URLs) highlights differences between WebSphere Message Broker (WMB) for HP-UX for HP 9000 servers and WebSphere Message Broker for HP-UX for Integrity servers by referring to the two HP-UX platforms as: PA-RISC for HP-UX for HP 9000 servers Itanium, IA64, or IPF for HP-UX for Integrity servers Table E.1 shows the results of searching the WebSphere Message Broker 6.1 documentation for references to PA-RISC, Itanium, IA64, and IPF, where the documentation shows a difference in functionality between the HP-UX platforms. The same text color-coding used in Appendix D applies here. The left column of each row of Table E.1 contains the navigation path to the appropriate section in the WebSphere Message Broker documentation, along with a Table Index String that is used elsewhere in this paper to reference individual rows of Table E.1. An example Table Index String is WMB6.1DOC#01, where WMB6.1 represents the version of WebSphere Message Broker, DOC represents Documentation, and #01 represents the first row entry in Table. E.1. Table E.1. Documentation differences between WebSphere Message Broker 6.1 for HP-UX for HP 9000 servers and WebSphere Message Broker 6.1 for HP-UX for Integrity servers WebSphere Message Broker 6.1 documentation section, and Table Index String WebSphere Message Broker Version > Configuring > Configuring databases > Enabling ODBC connections to the databases WMB6.1DOC#01 WebSphere Message Broker Version > Configuring > Configuring databases > Enabling JDBC connections to the databases > Configuring a JDBC type 4 connection for globally coordinated transactions WMB6.1DOC#02 Comment WMB on HP-UX for HP 9000 servers supports 32-bit and 64-bit execution groups, whereas WMB on HP-UX for Integrity servers only supports 64-bit execution groups. WMB 32-bit execution groups for HP-UX for HP 9000 servers support various combinations of 32-bit and 64-bit broker and user databases, whereas WMB 64-bit execution groups only support 64-bit broker and user databases. The JDBC switch files for HP-UX for HP 9000 servers are libjdbcswitch.sl (32-bit) and libjdbcswitch64.sl (64-bit). The JDBC switch file for HP-UX for Integrity servers is libjdbcswitch.so, and is 64-bit only. WebSphere Message Broker Version > Configuring > Configuring global coordination of transactions > Configuring global coordination with Oracle by using a 64-bit queue manager WMB6.1DOC#03 WebSphere Message Broker Version > Configuring > Configuring global coordination of transactions > Configuring global coordination with Sybase WMB6.1DOC#04 The switch file for Oracle is UKor8dtc23.sl for HP-UX for HP 9000 servers and UKor8dtc23.so for other UNIX platforms including HP-UX for Integrity servers. The switch file for Sybase is UKasedtc23.sl for HP-UX for HP 9000, and UKasedtc23.so for other UNIX platforms including HP-UX for Integrity servers. WebSphere Message Broker Version > Developing applications > Developing message flow applications > Designing a message flow > Configuring JMS nodes to support global transactions WMB6.1DOC#05 The JMS provider switch files for HP-UX for HP 9000 servers are libjmsswitch.sl (32-bit) and libjmsswitch64.sl (64-bit). The JMS provider switch file for HP-UX for Integrity servers is libjmsswitch.so, and is 64-bit only. 15

16 WebSphere Message Broker 6.1 documentation section, and Table Index String Comment WebSphere Message Broker Version > Developing applications > Developing user-defined extensions >Implementing user-defined extensions > Implementing a user-defined parser > Compiling a C user-defined extension WMB6.1DOC#06 WebSphere Message Broker Version > Installing > Applying service to runtime components > Installing service on Linux and UNIX WMB6.1DOC#07 WebSphere Message Broker Version > Installing > Applying service to runtime components > Linux and UNIX > Linux and UNIX: changing the ODBC connection and XA resource manager definitions for V or later WMB6.1DOC#08 WebSphere Message Broker Version > Migrating > Migrating from Version 6.0 products > Migrating from WebSphere Message Broker Version 6.0 > Migrating a broker > Distributed operating systems > Changing the ODBC connection and XA resource manager definitions for a broker migrated from Version 6.0 to Version (or later) WMB6.1DOC#09 WebSphere Message Broker Version > Reference > Databases > odbc64.ini sample file WMB6.1DOC#10 WebSphere Message Broker Version > Reference > Installation > Hardware requirements > Memory and disk space requirements WMB6.1DOC#11 WebSphere Message Broker Version > Reference > Installation > Software requirements > Optional software support WMB6.1DOC#12 WebSphere Message Broker Version > Reference > Installation > Software requirements > Support for 32-bit and 64-bit platforms WMB6.1DOC#13 WebSphere Message Broker Version > Reference > Installation > Software requirements > Supported databases WMB6.1DOC#14 WMB for HP-UX for HP 9000 servers supports both 32-bit and 64-bit builds of user-defined extensions in C. WMB for HP-UX for Integrity servers only supports 64-bit builds of user-defined extensions in C. Compile-commands for 64-bit builds are the same for both HP-UX platforms. There is a small difference when linking, to pull in platform-specific Java run-time environment libraries. The command to install WMB maintenance updates and program fixes is setuphp for HP-UX for HP 9000 servers and setuphpia64 for HP-UX for Integrity servers. In the Changing the XA resource manager definitions section there are different switch file settings for the two HP-UX platforms. In the Changing the XA resource manager definitions section there are different switch-file libraries settings for the two HP-UX platforms for databases such as Oracle & Sybase. The odbc64.ini sample file for HP-UX for Integrity servers has an entry for Microsoft SQL Server, which the sample file for HP-UX for HP 9000 servers does not have. The disk space requirements for WMB on HP-UX for Integrity servers are greater than on HP-UX for HP 9000 servers. There are different C & C++ compiler versions for HP-UX for HP 9000 servers and for HP-UX for Integrity servers. WMB on HP-UX for HP 9000 servers supports both 32-bit and 64-bit execution groups, whereas WMB on HP-UX for Integrity servers only supports 64-bit execution groups. There are differences in ODBC support (e.g. version of database products) for DB2, Informix, Oracle and Sybase. WMB on HP-UX for Integrity servers supports Microsoft SQL Server for ODBC, whereas WMB on HP-UX for HP 9000 servers does not. 16

17 WebSphere Message Broker 6.1 documentation section, and Table Index String Comment WebSphere Message Broker Version > Reference > Installation > System changes > Directory structures after installation WMB6.1DOC#15 WebSphere Message Broker Version > Reference > Operations > Commands > Runtime commands > mqsi_setupdatabase command WMB6.1DOC#16 WebSphere Message Broker Version > Reference > Operations > Commands > Runtime commands > mqsimanagexalinks command WMB6.1DOC#17 WebSphere Message Broker Version > Troubleshooting and support > Dealing with problems > Resolving problems when creating resources WMB6.1DOC#18 There are minor differences in the directory structure for WMB 6.1 installed on HP-UX for HP 9000 servers and HP-UX for Integrity servers. On HP 9000 there are sub-directories of merant, ODBC32 & SecurityProvider32 under /opt/ibm/mqsi/6.1: those subdirectories are not present on Integrity. Integrity has a sub-directory of config under /var/mqsi, which is not present on PA-RISC. The mqsi_setupdatabase command is only valid for 32-bit execution groups, thus applies to WMB for HP-UX for HP 9000 servers, but not to WMB for HP-UX for Integrity servers. Different versions of DataDirect Connect for ODBC are supported (v5.0 on HP-UX for HP 9000, and v5.2 for HP-UX for Integrity). Under the Checklist for configuring databases heading of the WMB documentation at the path listed in the cell to the left, there is reference to 32-bit ODBC which applies to WMB for HP-UX for HP 9000 servers and does not apply to WMB for HP-UX for Integrity servers. Both HP-UX platforms support 64-bit ODBC. 17

18 For more information HP-UX 11i operating system, hp.com/go/hpux HP-UX technical documentation, hp.com/go/hpux-core-docs HP Integrity servers, hp.com/go/integrity IBM WebSphere Message Broker product, IBM WebSphere Message Broker System Requirements, IBM WebSphere Message Broker Fix Pack download, To help us improve our documents, please provide feedback at hp.com/solutions/feedback. Get connected hp.com/go/getconnected Current HP driver, support, and security alerts delivered directly to your desktop Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omiss ions contained herein. Microsoft and Windows are U.S. registered trademarks of Microsoft Corporation. Intel and Itanium are trademarks of Intel Corporation in the U.S. and other countries. Oracle and Java are registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group. 18 4AA4-4918ENW, Created January 2013