IBM WebSphere MQ for HP NonStop Update

Transcription

1 IBM WebSphere MQ for HP NonStop Update Gerry Reilly Development Director and CTO, IBM Messaging 5 th December IBM Corporation

2 Trademark Statement IBM, WebSphere and the IBM logo are trademarks of International Business Machines Corporation, registered in many jurisdictions. Other marks may be trademarks or registered trademarks of their respective owners. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. 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, registered marks or service marks of their respective owners. References in this publication to IBM products and services do not imply that IBM intends to make them available in all countries in which IBM operates. 2

3 Available today IBM WebSphere MQ V5.3 MQ Server only Base MQ code level V5.3 Latest release level V (September 2012) Supports key range of HP platforms HP NonStop Server (S-series) HP NonStop Server G06.25, or later HP Integrity NonStop Server HP NonStop Server H06.04 or later HP Integrity NonStop Server BladeSystem J or later HP Integrity NonStop BladeSystem NB54000c (needs minimum of MQ V level) that is capable of running the J

4 Architecture IBM Software Group WebSphere software Has evolved over time and offers best of both A blend of UNIX common services integrated with key architectural value propositions of the HP NonStop architecture OSS (Unix) environment Standardization of interfaces Multi-threading for better resource utilization and overall scalability Guardian for key server processes and databases giving fault-tolerance and data integrity NonStop Process pairs (queue servers, channel server and execution controller) Queue and message storage audited by TMF Secure channels provided using SSL from OpenSSL Full interoperation with GSKit implementations on other platforms PATHWAY for process management & monitoring Disaster recovery using RDF 4

5 We have added Extended Transactional client support at an MQ V7.1 release level Gives access to full MQ V7.1 function to NonStop applications linking to MQ on other systems Client is free and fully supported C / C++ extended transactional client Cobol ptal support JMS client Supports both Guardian and OSS application programs and OSS multithreaded applications GA product made available in July 2013 Available from Support Pac page: Will be updated following each major MQ release 5

6 MQ on HP NonStop Server MQ V5.3 will remain in marketing and with full service for guaranteed prolonged minimum period Will continue to support new NonStop releases to be qualified on new Itanium processor releases Full service and support included maintenance and security fixes Normal service period extended to at least 2Q2016 Extended service to at least 2Q2020. Will remain interoperable with all current and future releases of MQ on other platforms This version will remain as the server release and will not be updated with a new server version Minor functional enhancements may be provided via the service streams 6

7 MQ in Client Topologies XA TM App NODE 1 Extended MQ Client Database client Queue Manager NODE 3 Database Server NODE 2 However you will continue to have the choice. Existing fully supported server or new client. Client Benefits Lower cost to deploy, only pay for central server Smaller install and runtime footprint Can configure to connect to multiple servers so failure resilient with automatic reconnect Can workload balance across Queue Managers Very low administration, zero local admin except for initial set-up Transactional client allow participation as a RM TMF transaction All WAS/MQ customers use this topology, so common use in production Server Benefits Messaging even when network not available Local control over administration and monitoring 7

8 Functional Comparison Key / Distinguishing Features OS Levels Client Applications MQ 5.3 Server G06.25, H06.04, J06.03 or later MQ 7.1 Client to a Remote Queue Manager H06.24, J06.13 or later Describes the key features and functional differences for application developers writing applications API - C API - C++ API - Java API - JMS [no App Server support] API - TAL API - ptal API - COBOL Transactions - local transactions Transactions - TMF Coordinated two-phase commit [not supported for JMS] Feature - Message Properties API / Selectors Feature - Workload consolidation multi-qm Feature - Native Publish/Subscribe Messaging Feature - Async Message Delivery Feature - Auto-Reconnect Feature - Cooperative Browse Feature - JMS access to MD and msg contents Behaviour - Default syncpoint behaviour OS Threading Model Access to functional updates [32bit non-native, native,srl and PIC] via Fuji Broker via SetSignal on MQGET Commit SPT [32bit native, PIC] - [client lib can be linked from C++] [Natively] Async Consumer [Callback] Rollback PUT 8

9 Functional Comparison - Infrastructure/Administration Features Key / Distinguishing Features MQ 5.3 Server MQ 7.1 Client to a Remote Queue Manager Describes the key features and functional differences for system administrators when connecting applications directly to a v7.5 queue manager, as opposed to using a v5.3 queue manager on HPNS as a gateway to a v7.5 infrastructure. Transport - IPv6 Transport - LU6.2 Transport - Channel Compression Transport - Pre-connect Exit SSL - SHA-2 SSL - Auto Reset of secret key SSL - Refresh credentials without QM restart SSL - OCSP Certificate revocation Management - Detailed connection information (visibility of app name, in-flight unit of works etc) Management - Detailed Channel and Queue Status (client product version and client type etc) Management - MQSC WHERE clause (select client details) Management - Stats and accounting (client stats such as number of puts, msg sizes, msg types etc) Clustering - Advanced workload balancing (weighting) Clustering - Advanced cluster authority (granularity beyond cluster transmit queue) Clustering - Bind on Group (affinity to a QM per group) Clustering - Split cluster transmit queue Runtime - Resource Usage (on HPNS) Runtime - Performance (on HPNS) Runtime Fault Tolerance (on HPNS) (under consideration) (under consideration) Reduced No significant impact Dependent on network and server availability 9

10 Possible Roadmap Enhancements to the WebSphere MQ V5.3 on HP NonStop Limited enhancements to server will be delivered via service stream. Key features under consideration include; Upgrade of Open SSL to provide SHA 2 Java7 support IPv6 support Open to other requests that can be delivered via the service stream Client release It is our intent to update the transactional client to the VNext level during

11 Summary HP and IBM remain committed to providing MQ capability on the HP NonStop Platform Close collaboration will continue New approach will provide more timely access to new MQ capabilities on HP NonStop Existing workload No need to change. MQ 5.3 will continued to be support and available for new licence deployment Can migrate to client to simplify operational management if and when appropriate New workload Can be deployed on MQ 5.3 if this meets the functional requirement Or, can be deployed using to the client if additional functional capability is required or to centralise operational management 11

12 IBM and BrightStrand Partnership Close working relationship between IBM and BrightStrand BrightStrand MQ Services include; Education MQ on NonStop Performance and tuning Migration to client topologies Installation & Configuration 12

13 THANK YOU 13