Software Group

WebSphere Message Broker v6

Jonathan Woodford [email protected] Message Broker Development

GSE Nordic WebSphere User Group 2006

2006 IBM Corporation

Software Group | WebSphere Business Integration

Agenda
Broker Directions and Key Themes Getting Started with Version 6 Platform coverage Migration and Coexistence Administration Improvements Graphical Mapping Java Compute Node ESQL enhancements Other New and Improved Nodes Web Services Message Modelling Performance Improvements
Whats New in WebSphere Message Brokers Version 6 2005 IBM Corporation

WebSphere Message Broker Key dates

June 2003 : Message Broker Version 5 released Eclipse-based toolkit and repository Incremental delivery of function via CSD and supportpacs e.g. CICS, VSAM support September 2005 : Message Broker Version 6 released Focus on performance, usability and new feature function Web Services requester/provider improvements, JMS interactions, Java transformations March 2006 : Message Broker Runtime Fixpack 01 released August 2006 : Message Broker Runtime Fixpack 02 released September 2006 : End of Service for WMQI V2.1
WebSphere Message Broker

WebSphere Message Broker - Directions and key themes

Improved user experience
Install, migration and co-existence Mapping, Java support, ESQL, debugging Flat-files, JMS interoperability Parsers, ESQL, 64-bit support Command scripting, platform and database coverage

Development skills and experience Enhanced connectivity options Enhanced performance

Improved manageability

WebSphere Message Broker

Getting Started
Simplified Launchpad and install Available as download via Passport Advantage, CDs or on a single DVD per platform Install alongside previous versions (2.1 and 5) Single prerequisite product for development, unit test and PoC environments on Windows Websphere MQ (v5.03.0.1 or later) Broker database is required for production and non-Windows Bound, hardcopy install guide included in product package Improved Default Configuration Wizard Fewer configuration options Create (or remove) default configuration Deploys and runs install verification samples Launches into samples gallery Comprehensive Samples Gallery Get successful experience with MB technologies quickly Technology (e.g. Java Compute Node, JMS nodes) Application oriented samples (e.g. Data Warehouse)

WebSphere Message Broker

Simplified Launchpad

WebSphere Message Broker

Comprehensive Samples Gallery

WebSphere Message Broker

Getting Started with Version 6 Samples

WebSphere Message Broker

Platform coverage
Broker
Windows 2000/XP/2003 z/OS HP-UX Solaris AIX Linux (Intel+)

Configuration Manager
Windows 2000/XP/2003 z/OS HP-UX Solaris AIX Linux (Intel+)

Toolkit
Windows 2000/XP Linux (Intel)

Complete Linux story for all components Support for 64-bit Execution Groups (AIX, HP, Solaris) Support for Oracle databases on Linux platform

WebSphere Message Broker

Flexible Migration and Coexistence

Simplified migration from v2.1 and v5 Single new command to migrate components between versions mqsimigratecomponents V6 can be installed on the same machine and run alongside all previous versions of the product Domain coexistence Complete interoperability between v5 and v6 V5/V5.1 Tooling components V5/V5.1 Config V6 tools can manage v2.1 and v5 brokers V5/V5.1 Broker The v6 broker can be migrated back to the previous version (v2.1 or v5) Must not be using new v6 function
WebSphere Message Broker

Domain compatible?

V6 Tooling Yes Yes Yes No No Yes

V6 Config Yes n/a Yes No n/a Yes

V6 Broker Yes Yes Yes No No Yes

V2.1 Tooling V2.1 Config V2.1 Broker

Flexible Migration and Coexistence

V6 product is installed to a new location Profiles are used (Command Console on Windows) to select which MB v6 instance you are working with Component names must still be unique on the machine It is now possible to name Configuration Managers, and have more than one running in each instance The v6 mqsilist command can list all components on the machine, or just those in the current instance

WebSphere Message Broker

Installing V6 alongside previous versions (approach 1)

V2.1 or V5 Product Install

V6 Command Console

V6 Product Install

mqsimigratecomponents BrokerA ConfigMgr

BrokerA

ConfigMgr

Machine As File System

WebSphere Message Broker

Installing V6 alongside previous versions (approach 2)

V2.1 or V5 Product Install

V6 Product Install

BrokerA

ConfigMgr

BrokerB

ConfigB

Machine As File System

WebSphere Message Broker

Improved Administration
New command line tools Deployment (V5) Start/Stop message flows Create/Delete execution groups Intelligent Resource Utilization Queue and database handles released during flow inactivity Restart database without restarting the broker Java administration API (Configuration Manager Proxy) Runtime versioning

WebSphere Message Broker

Command Line Administration New and Improved

New New Improved Improved

mqsimigratecomponents mqsicreateexecutiongroup mqsideleteexecutiongroup mqsistartmsgflow mqsistopmsgflow mqsibackupconfigmgr mqsirestoreconfigmgr mqsicreatedb mqsideletedb mqsicreateaclentry mqsideleteaclentry mqsilistaclentry or create your own!
WebSphere Message Broker

Password prompt option added to all relevant commands:

mqsicreatebroker, mqsicreateconfigmgr, mqsicreateusernameserver, mqsisetdbparms mqsichangebroker, mqsichangeconfigmgr, mqsichangeusernameserver

Revised database options for:

mqsicreateconfigmgr mqsichangeconfigmgr

Supply Configuration Manager names to:

mqsicreateconfigmgr mqsichangeconfigmgr mqsideleteconfigmgr Improved readability for all command help Better formatting

Configuration Manager Proxy API

A complete Java programming interface to the Configuration Manager Administer domains programmatically Brokers import com.ibm.broker.config.proxy.*; Execution groups Message flows public class CreateBroker { public static void main(String[] args) { Dictionaries ConfigManagerProxy cmp = Subscriptions ConfigManagerProxy.getInstance(); TopologyProxy topology = cmp.getTopology(); Topology topology.createBroker(MYBROKER,QMGR); Collectives } } Event Log Topics Configuration Manager Comprehensive samples and documentation provided The same interface that is used by the Message Brokers Toolkit and various commands
WebSphere Message Broker

Runtime versioning
V6 makes it easier to discover what has been deployed to your brokers New fields associated with each deployed object Deployment time, Modification time, BAR file name, Version

WebSphere Message Broker

Improved Developer Productivity

Next Generation Mapping Spreadsheet development model Ability to debug mappings Java compute node ESQL enhancements

WebSphere Message Broker

The next generation of the mapping editor

Adopt a spreadsheet model for creating transformations the user concentrates on the structural transformations not the execution logic

1. Source definition 2. Target definition 2 1

May be a message, element of a message or a database May also be a message, element of a message or a database

3. Expression editor 4. Overview and editor

Support for all ESQL features and user defined functions in ESQL or Java.

Script editor allows you to fine tune things that lines and expressions cant -- such as mutually exclusive if-conditional expressions

WebSphere Message Broker

Mapping editor: debug view

1. Set break- points 2. Step over 3. Inspect variables 4. Debug subroutines

1 4

WebSphere Message Broker

Java as a First Class Transformation Language

Offers a Compute node alternative for Java programmers Similar look and feel No ESQL skill or experience required General purpose programmable node Java programming language Standards based - J2SE 1.4.2 Offloaded processing on z/OS via zAAP Extra convenience methods have been added The message tree can be queried and traversed using XPath 1.0 syntax Extensions to allow new elements to be created in message structure Also Provides full access to the existing Java plug-in API Databases can be accessed via two supported routes JDBC type 4 drivers - standard Java, non-transactional MbSQLStatement - uses brokers ESQL syntax, fully transactional

WebSphere Message Broker

Using the Java Compute Node

Full Eclipse Java experience
Eclipse Java editor provides built-in syntax assists

Select Open Java and choose which template to use:

Filtering message template Allows you to look at the incoming message without changing it Modifying message template Allows you to change parts of the incoming message Creating message template Allows you to create and build a new message from scratch Equivalent to the ESQL module in a compute node

Java class is a property of the node

public class jcn2 extends MbJavaComputeNode { public void evaluate(MbMessageAssembly assembly) throws MbException { MbOutputTerminal out = getOutputTerminal("out"); MbOutputTerminal alt = getOutputTerminal("alternate"); MbMessage message = assembly.getMessage(); // Add user code below // End of user code out.propagate(assembly); }

WebSphere Message Broker

ESQL Enhancements
Improved support for creating DATETIME variables Simplify date/time constructions DECLARE myDate DATE = DATE(2004, 03, 01); Flexible Type Formatting Add FORMAT clause to CAST SET myString = CAST(money AS CHAR FORMAT "#,###.00"); Add support for CAST between INTERVAL and FLOAT Cardinality functions Remove restrictions on CARDINALITY and EXISTS Add new SINGULAR function User Defined Attributes Attributes of a node that can be defined and given values by the user Can be accessed by ESQL of a node (treated as constants) DECLARE COLOUR EXTERNAL CHARACTER; Dynamic database schema names Can exploit user defined attributes to allow schema/table names to be specified at deploy WebSphere Message Broker Broker Attributes Allows flow designer to determine state (e.g. MessageFlowName, ProcessId, Family, QueueManagerName, TraceActive) DECLARE myFlow CHARACTER = MessageFlowName; Matches attributes available in Java Handlers Run when error condition is detected Provides more flexible and improved support for handling of errors Stored Procedure enhancements Single scalar return value CALL myProc1( int1, int2 ) INTO intRetVal; Single/Multiple Results sets CALL myProc1( int1, int2, Environment.RetVal[], OutputRoot.XML.A[] ); Multiple Database Support Access to multiple databases from the same Compute, Database or Filter node

Messaging Processing Nodes: New and updated

Java Compute node
Provides existing Compute node capability for Java programmers Deploy Java JARs Periodically start flows at preconfigured and programmatic time intervals. Can be used anywhere within a message flow, unlike an MQInput node which can only be used as the first node in a message flow. Native JMS Interoperability
New New

TimerControl Node

Web Services HTTPS support

Updated Updated

MQGET node

Aggregation MQ based implementation Delivers improved performance XSLT Deployed style sheets Compiled style sheets Publication Support for Multicast PGM

JMS Input/Output

WebSphere Message Broker

Web Services Support

Improved support for modelling and working with SOAP messages Pre-defined message definitions for SOAP Support for SOAP with Attachments (SwA) via new MIME parser A mechanism for importing an existing WSDL definition A new WSDL importer wizard, accepting a variety of WSDL styles More flexible protocol support Support for SOAP 1.1 and SOAP 1.2, and for HTTP 1.1, HTTPS Built-in WS-I Compliance checking Automatically validates WSDL against the WS-I Basic Profile

WebSphere Message Broker

Message Modelling
Functional WSDL importer for enhanced SOAP modelling Simplifies the calling of Web services from within flows SOAP with Attachments (SwA) support Via new MIME parser XML Schema enhancements (xsi:type, list, union) Large message support Allows arbitrary parts of a message to be parsed or written Pre-built message definitions are supplied for some common industry message formats SOAP envelope, SOAP encoding, VSAM request, Timeout Request, MIME Performance Significant improvement of broker implementation, no model changes required Code optimizations TDS Parser rewrite
WebSphere Message Broker

z/OS Specific Enhancements

Full use of JES spool for consolidated message output Deployment audit trail messages MVS dumps, not USS coredumps when necessary(!)

WebSphere Message Broker

Other miscellaneous enhancements

RealTime/Multicast PGM Database Unicode support Publish Subscribe Performance Literal topic + # support Solaris Scaling Additional instances now scale effectively Internal runtime changes Overall performance improvement

WebSphere Message Broker

Significant Performance Improvements

Pe rce ntage Improv e me nt v s. V5 CSD 04
GA published reports show 50% average improvements on all platforms Lab Performance results show 47% to 67% increase in message throughput (based on September drivers) Highlights are: Parser [up to 3x increase] Aggregation Node [up to 10x increase] ESQL functions [avg. of 2x increase] Customer feedback has validated improvements Migrated, unchanged V2.1, 5 flows show expected gains Performance report for each sample Enables customers to validate tuning to match the Lab results, eg Message Routing Sample can run at 1700 messages a second using a 1k message on Windows.

HP W indows Linux Solaris AIX z/OS 0% 20% 40%

67.17% 66.69% 65.59% 63.01% 55.21% 47.83%

60% 80%

Average of all tests

WebSphere Message Broker

Key SupportPacs and Offerings

Complex Event Processing
Compliance checks, fraud detection, etc

Resend/Replay CICS Request Node

Executes a CICS External Call Interface (EXCI)

VSAM Nodes
Reads and writes records from a VSAM data set

Message Broker File Extender DataStage TX Extender

Allows you to extend the range of message formats and protocols that Message Broker can handle

MQ/MB Combined Administration

WebSphere Message Broker

Broker Summary

Message Broker v6 is a significant release: Continues to deliver significant new function Satisfies major customer requirements Improves performance Improves ease of use and flexibility

WebSphere Message Broker

Any Questions?
Please fill out an evaluation form

WebSphere Message Broker