Universal Messaging Backbone for SOAguide.webspheremq.fr/docs/Universal Messaging...WebSphere...

Ben MannProduct Line Manager WebSphere MQ family

UniversalMessaging Backbone for SOA

2

Business Drivers and IT Challenges

Demonstrate integrity of business data as it moves around organization

Demonstrate integrity of financial reporting to avoid incurring penalties

Comply with government and industry regulations

ITBusiness

Exploit new techniques and technologies

Create value from new innovations to drive bottom line

Move business ahead…

…whilst plugging these into today’s systems

Keep the business running, minimizing disruption and downtime…

…but keep IT going!

Spend less time on just maintaining today’s systems

Introduce process improvements with lower incremental cost and time

Do more with less

Reduce the time, effort and risk involved in making IT changes and enhancements

React to new opportunities and threats without impacting ability to continue executing

Absorb changes

Draw IT skills from a broader poolLess dependency on specialists

Make the right choice for today without regrets tomorrow

Reduce risk

3

Information bottled is uselessInformation exists in both time and space

The Key to Addressing these Challenges

� The most valuable asset in your business is information

� How you move information around your organization determines the how much value you can get from it

� How information flows around your organization determines how competitiveyour business is

� How Reliable? Timely? Secure? Relevant? Integral? Available? Auditable?

� Can you get the right information to the right place at the right time?

� How fit is your enterprise?

4

Murky, foggy communication between department silos that prevents information being used across organization

Holdups in getting the right information to the right place… And no way of knowing what information went where

How Do You Transport Your Information Today?

Changes that are riskier, cost more and take longer each time and cause even more disruption each time

Tools and technologies you can’t leverage because they won’t mesh with what you already have

Choices you aren’t really free to make because of things you can’t connect or that have different transport needs

� Your success is linked to how good your information “transportation system” is

� Are you in the driving seat of how your information moves and flows?

� In an audit could you prove that your information is being handled aright?

5

Leverage Your Organization’s Diversity

� Difference between chaos and order is not homogenisation it is purpose

� Rather than fruitlessly battling these differences why not embrace them!

� Leverage your IT and organizational diversity by unifying it

� Don’t rip and replace to impose order – integrate things just the way they are

Your

Stra

tegy

New Te

chnolo

gy

Standards

& M

andates

Acquisitions & Mergers

Your

Custo

mers

Your People

Your Suppliers

You

6

Get the right information to the right place regardless of

•When•Where•Why•How•Who

Get the right information to the right place regardless of

•When•Where•Why•How•Who

No limits connectivity

Ability to connect virtually anything

Freedom to make the right choices

Flexibility to absorb changes

No limits connectivity

Ability to connect virtually anything

Freedom to make the right choices

Flexibility to absorb changes

3 Key Characteristics Needed

Distributed yet unified

Flexible and Adaptable

Robust and Available

Scalable and Modular

Distributed yet unified

Flexible and Adaptable

Robust and Available

Scalable and Modular

� To respond to threats, opportunities and changes

� To make the right business decisions and technology choices

7

Qualities-of-Service Delivery Styles

Transactional

Persistent

At-least-once

Best-Effort

Fire-and-Forget

Request-Reply

Replay

Guaranteed

At-Most-Once

Client-Server

Backbone

Point-to-Point

Peer-to-Peer

Publish/Subscribe

Grid

Bus

Fastest speed

Multicast

Lowest Latency

Unicast

Skills

Languages

Mindsets

Orientations

COBOL, C/C++, RPCJava, JEE, JMS.NET, C#, VB, WCFAJAX, Perl, Python…

ServiceBatchFileMessageResource…

WSDL, XML, WS-*REST, MEST, KISS

End-Points

Vendor Platforms

Applications

Operating Systems

Devices

Web services

Web 2.0

JEE, .NET, etc

Exploitation & Support

SAP, Siebel, etc…

Mobile, Wireless, PoS,Sensor, Actuator, RFID…

AppliancesHTTP, AJAX, REST,…

SOAP, WSDL, WS-RM, WS-N…

IBM’s Vision – Universal Messaging Backbone� Addressing the full spectrum of transport requirements

8

Benefits of Universal Messaging Backbone

Provide transport foundation for ESB and enable non-Services to participate in SOA

Increase re-use of existing assets and enable governance

Accelerate SOA

CapabilityBenefit

Support the broadest set of skills and approaches

Use the systems, people, skills, languages and tools you have

Enable Choice

Enable dynamic delivery of information and unified configuration across backbone

Make changes faster with lower risk and cost

Flexibility

Enable new technologies and bridge these to the systems that power the business today

Bring the benefits of new technologies and approaches to the systems you already have

Combine New & Now

Backbone that support growth incrementally. Exploit multi-core, multi-Processor environments

Start simple and scale with growing business demands and IT capacity

Grow at your pace

Backbone that can connect virtually anything

Support the IT systems you have today and may have tomorrow

Breadth

9

IBM delivers the Universal Messaging Backbone

� Via messaging portfolio of standalone and embedded services

� Seamless bridging and native links within messaging portfolio– Preserving reliability, transactionality and publish-and-subscribe domains

– Core is WebSphere MQ family

– Continually evolving and expanding

– Extensive IT environment coverage

WebSphere MQ–for z/OS–for ESE/VSA–for NSS/OVMS–Extended Security–Everyplace/Mobile–Telemetry Transport–Low Latency Messaging

WebSphere MQ family

– Provides “MQ inside” SOA portfolio

– Offers an integrated JEE experience

– Shared within stack of SOA products

WebSphere Business Services Fabric

WebSphere Process Server

WebSphere ESB

WebSphere Application Server

Embedded Messaging

10

WebSphere DataPowerIntegration Appliance

Purpose-built hardware ESB with simplified deployment

and hardened security

WebSphereMessage Broker

ESB for universal connectivity and transformation in heterogeneous

IT environments

WebSphere ESBBuilt on WebSphere

Application Server for an integrated SOA platform

Messaging Backbone underpins SOA� ESB layer builds upon Messaging Backbone

– Adds “awareness” of what messages contain backbone– Adds message mediation, message transformation and content-based routing

� Messaging Backbone provides underlying transport layer for Enterprise Service Bus and BPM

– Provides transport services for ESB family and extends its reach

WebSphere MQ family Embedded Messaging

11

Cut IT integration cost and maintenance 2-4 times

Cost

Source: “Enterprise Integration Challenge,” Software Strategies, 2006

All

Cu

sto

m D

evel

op

men

tB

asic

/Fre

e F

TP

Tec

hn

olo

gy

+ C

ust

om

Dev

elo

pm

ent

Building & Maintaining

“ Val

ue A

dded

FTP

”So

lutio

ns +

Cus

tom

Dev

elop

men

t

Number of Applications Integrated

Size of Project

Custom-built, in-house, hard-coded integration solutions…

…often take 2 to 4 times the time and effort to build

…require a similar multiple of ongoing maintenance and support effort...

… IBM application integration costs 2-4 times less

Software Strategies ”

the more applications you integrate the more you save

Handwritten Code

Integration Software “

Enter

prise

Appli

catio

n Midd

leware

Handwritten extensions

to FTP

“ ”

12

Your Application

Messaging Backbone – A First Step To SOA

Messaging

Integration

Service-Orientation

Hand-coded, Hard-wired

Your Application

Duplicated logic buried inside for:•Connectivity•Transformation•Mediation

Increased flexibility and reuse

Your Application

Still has to do:•Transformation•Mediation

Still has to do:•Mediation

0

1

2

3

More code to write and maintain

Your ServiceElimi

nate dupli

cated conn

ectivity log

ic

Reduce th

e cost and

time of ch

anges

Increase I

T flexibility

13

?Web 2.0

HTTP GET

HTTP POST

HTTP DELETE

AJAX

Simple access from Web 2.0 to existing apps and data

–URL identifies queues and topics–Simple RESTful interface

Delivered in WebSphere MQ V7–Bridge for HTTP (Dist and z/OS)–Leverages JEE Application Server

As-is download of bridge for MQ V6As-is download offers native HTTP

The Solution: Universal Messaging Backbone that connects Web 2.0 to existing IT systems

Universal Messaging Backbone for Web 2.0

Business Objective: Increase revenues by driving more Web-based product sales!

IT Tactic: Use Web 2.0!–Make the Web site more interactive and “stickier” to increase customers purchases–Recommend items including those that others bought and personalized promotions–Provide compelling order details including stock levels, availability and delivery

The Challenge: Frictionless access to the data–Your Web 2.0 team can build the new exciting interface

–But can’t access the data needed for the Web 2.0 app (order history, logistics, inventory…)–Your IT Systems team hold the data

–But can’t build the interactive Web 2.0 sites

Applications and Data

Applications and Data

Web 2.0

HTTP GET

HTTP POST

HTTP DELETE

AJAXUniversal Messaging BackboneHTTPBridge

14

Universal Messaging Backbone

Existing Applications

Universal Messaging Backbone for SOA

Business Objective: Increase the flexibility of existing business processes!

IT Tactic: Bring the existing applications that deliver those processes into an SOA–Turn the existing applications into Services–Increase ability to re-use and govern existing applications

The Challenge: Turning a batch-oriented application into a Service–Time, effort, skills and application-specific expertise needed to wrapper the application as a Service–How to avoid overloading the application with Service requests–How to avoid disruption to the “service” the application provides the business today

The Solution: Universal Messaging Backbone that can manifest applications as ServicesProvide SOA approach to accessing applications connected by a Universal Messaging Backbone–Without application modification or disruptionProvided by public Service Definition –IRI to access data via Queues or Topics–WSDL to describe the applications as ServicesWebSphere Service Registry & Repository V6.1–Can catalog and govern connected applications–Aids change management and auditingPresents opportunity to automate service-enablement

SOAReuse

Catalog

GovernPublish

15

Universal Messaging Backbone for Web services

Business Objective: Increase the reliability of business services!

IT Tactic: Leverage SOA to loosely couple applications as Services–Building upon the richness of WSDL and WS-* to implement complex Service interactions patterns–Building upon the simplicity of REST to implement a pragmatic solution

The Challenge: How to provide a robust, time-independent, transport for SOAP–How to exchange information when all the Services involved aren’t always simultaneously available–How to code checks to detect transfer failures, re-try and handle duplicate transmissions–How to preserve the integrity of business transactions than span a number of service interactions

The Solution: Universal Messaging Backbone that provides reliable transport for SOAPProvide reliable transport for exchanging SOAP between Web services–Enhancing HTTP-based solutions –Enabling time-independent exchanges (asynchronous delivery of SOAP) –Providing transport services – rather than re-building for each service!–Enabling multiple exchanges to be coordinated into transactions

SOAP


SOAP

Web service Web service

16

Universal Messaging Backbone supporting range of skills sets

WindowsCommunications

FrameworkSAM / PHP

Web 2.0

HTTP bridging for AJAX applications with simple

RESTful interface

Multi-LanguageMessage Service

IBM interface offering JMS behaviours in more

languages than Java

Open source extension for PHP Web Scripting

Seamless experience for .NET (Indigo) Developer

–Leverage the skills you already have

–Draw IT skills from a larger pool

–Choose the right interface for the application

–Combine new technologies with the applications you already have

MQ Interface

IBM interface providing full function MQ access

for Java, C, C++, COBOL, .NET, PL/1…

� Support the broadest range of interfaces, languages and skills

Java Message Service (JMS)

Industry standard Java interface for point-to-

point and pub-sub msg

17

Support for virtually every commercial IT System

80+ platform configurations–AIX–Linux x86, x86-64–Linux POWER–Linux for System z–Windows x86, x64–Solaris x86 / SPARC–iSeries i5/OS–HP-UX Itanium/PA-RISC–HP NonStopServer–HP OpenVMS

Exploit System z for messaging powerhouse–Unique code-base designed natively for tight z/OS integration

–Runs as formal MVS sub-system

–Leverage Parallel Sysplex to provide Shared Queues for continuous availability, scalability and capacity

–Support for event-driven publish-subscribe delivery

Enable popular applications and environments–Built-in bridge for CICS, IMS, Batch/TSO

–JCA support to provide JMS services for JEE App Servers

–Support for Databases DB2, Oracle etc

–Support for External Transaction Coordinators

–Over 950 ISVs with enabled Packaged Applications

Applications

Universal Messaging Backbone supporting range of IT systems

80+ platforms

� Freedom to make platform choices and overcome life’s surprises

z/OS

18

Unified Configuration & Management

� Visual display at a glance� Eclipse-based environment� Extensible and customizable� Remote connection from

Linux x86 and Windows

� Logically centralized configuration of remote, distributed backbone� View and configure entire messaging backbone – including on z/OS

Delete

Create

Display

Modify

Test

Deploy

� Granular permissions � SSL secured connections� Diagnostic tools for testing

configuration including publish-and-subscribe

19


Transactional

Persistent

At-least-once

Best-Effort

Fire-and-Forget

Request-Reply

Replay

Guaranteed

At-Most-Once

Client-Server

Backbone

Point-to-Point

Peer-to-Peer

Publish/Subscribe

Grid

Bus

Fastest speed

Multicast

Lowest Latency

Unicast

Skills

Languages

Mindsets

Orientations




End-Points

Vendor Platforms

Applications

Operating Systems

Devices

Web services

Web 2.0

JEE, .NET, etc


SAP, Siebel, etc…




Transactionality preserves the integrity of applications and data

Messaging Backbone

TravelBooking A

B

C

D

Universal Messaging Backbone supporting range of Qualities-of-Service

Qualities-of-Service

Low-latency delivery enables faster response to business opportunities and threats

WebSphere MQ Low Latency Messaging V2.0–Newest addition to WebSphere MQ family–Adds low latency Quality of Service to the Universal Messaging Backbone–Capable of over 8 million messages/second–Capable of less than 200µs latency(lower latency = less lag time)

–Offers Multicast and Unicast delivery

WebSphere MQLow Latency Messaging

Delivery Styles

Guaranteed delivery helps overcome availability losses and helps free up busy resources

ZA

Messaging Backbone

The receiver – Application Z – is busy or not available or the host machine is down

Sending a message from A to Z. Could be SOAP, Web 2.0, images, text, etc…The network goes down…!The sender – A – is busy or goes down just after dispatching

Both applications become busy or go down during transmission

Time-Independent (Asynchronous) Delivery helps overcome all these situations

20


Transactional

Persistent

At-least-once

Best-Effort

Fire-and-Forget

Request-Reply

Replay

Guaranteed

At-Most-Once

Client-Server

Backbone

Point-to-Point

Peer-to-Peer

Publish/Subscribe

Grid

Bus

Fastest speed

Multicast

Lowest Latency

Unicast

Skills

Languages

Mindsets

Orientations




End-Points

Vendor Platforms

Applications

Operating Systems

Devices

Web services

Web 2.0

JEE, .NET, etc


SAP, Siebel, etc…




Transactionality preserves the integrity of applications and data

Messaging Backbone

TravelBooking A

B

C

D



Guaranteed delivery helps overcome availability losses and helps free up busy resources

ZA

Messaging Backbone

The receiver – Application Z – is busy or not available or the host machine is down

Sending a message from A to Z. Could be SOAP, Web 2.0, images, text, etc…The network goes down…!The sender – A – is busy or goes down just after dispatching

Both applications become busy or go down during transmission

Time-Independent (Asynchronous) Delivery helps overcome all these situations

21


Transactional

Persistent

At-least-once

Best-Effort

Fire-and-Forget

Request-Reply

Replay

Guaranteed

At-Most-Once

Client-Server

Backbone

Point-to-Point

Peer-to-Peer

Publish/Subscribe

Grid

Bus

Fastest speed

Multicast

Lowest Latency

Unicast

Skills

Languages

Mindsets

Orientations




End-Points

Vendor Platforms

Applications

Operating Systems

Devices

Web services

Web 2.0

JEE, .NET, etc


SAP, Siebel, etc…





Qualities-of-Service

Low-latency delivery enables faster response to business opportunities and threats

WebSphere MQ Low Latency Messaging V2.0–Newest addition to WebSphere MQ family–Adds low latency Quality of Service to the Universal Messaging Backbone–Capable of over 8 million messages/second–Capable of less than 200µs latency(lower latency = less lag time)

–Offers Multicast and Unicast delivery

WebSphere MQLow Latency Messaging

Delivery Styles

22

Positioning of IBM Messaging Transports

Low Latency MessagingEnterprise MessagingTarget Market

Semi-Reliable“Know-when-you-lose data”

Ultra-Reliable“Bet-The-Business”

Reliability – Quality of Service

Ultra-Fast“Microseconds”

Time Independent“As-Soon-As-Possible”

Speed – Quality of Service

Financial Markets, Telco and others with similar QoS needs

AllTarget Industries

NoYesUses Queuing

Unique – C-basedJMS, XMS and MQIAPIs

Linux and Windows on x86, and Solaris on x86 and SPARC

80+ platform configurationsPlatform coverage

Included in WebSphere Front OfficeWAS, WMB, WESB, DataPowerXI50, DB2, CICS, IMS, etc, etc…

Interoperates with

WebSphere MQ Low Latency Messaging

WebSphere MQ

23

� Introducing WebSphere MQ V7

– Delivering the core of IBM’s Universal Messaging Backbone

– Enhancing the market-leading messaging offering

1. Premier ease-of-use for improved developer productivity2. Turbo-charged performance and enhanced resilience3. WebSphere MQ goes Web 2.0!4. Publish-and-Subscribe support for z/OS

Announcing the Latest Evolution of IBM’s Universal Messaging Backbone

Enhanced JMSSupport

EnhancedTooling

EnhancedPerformance

EnhancedResilience

New MQI Commands

HTTP Bridge for Web 2.0

Enhanced Pub/Sub

New Pub/Sub for z/OS

WebSphere MQ V7

24

1. Premier ease-of-use for improved developer productivity

– Graphical configuration of JMS and Publish-and-Subscribe

– New MQI verbs providing greater flexibility for

– Selecting messages for processing– Adding custom properties to messages– Automatically notifying applications when messages arrive

Enhancing Usability of IBM’s Universal Messaging Backbone

25

1. Premier ease-of-use for improved developer productivity

– Heart-beat monitoring of client connections

– To help increase messaging availability

– Pre-emptive delivery of messages for increased throughput

– A.k.a Message Read-Ahead

– New Quality-of-Service that avoids waiting for confirmation of delivery – enables “receipts” to be received later

– Can help increase application throughput– A.k.a Asynchronous consume

Enhancing Usability of IBM’s Universal Messaging Backbone

26

2. Turbo-charged performance and enhanced resilience– Enhanced publish-and-subscribe performance

– Increased throughput by up to 20%* (Distributed)

– New publish-and-Subscribe support added in this release (z/OS)

– Enhanced JMS performance

– Increasing JMS selectors by up to 250%* (Distributed)

– Increasing JMS listener throughput by up to 45%* (Distributed)– Increasing JMS listener throughput by up to 220%* (z/OS)

– Enhanced Clients performance

– Increased throughout of non-persistent messaging by up to 300%* (Distributed)

Enhancing Performance of IBM’s Universal Messaging Backbone

Preliminary results observed on pre-release level code. For the latest performance information please click on Performance Reports at www.ibm.com/webspheremq/support

*

27

3. WebSphere MQ goes Web 2.0!

– Helps enrich Web 2.0 applications with real business data

– Distributed and z/OS platforms

– Developer needs no MQ skills

– Uses Ajax and simple RESTfulinterface to access data by URIs

– Helps simplify deployment and maintenance of large scale distributed applications

– Enables simple access to MQ without need to install MQ clients

Enhancing Web 2.0 Connectivity for IBM’s Universal Messaging Backbone

Browser

Ajax Library

JEE Application Server

Message Delivery

HTTP GET

HTTP POST

HTTP DELETE

Business Applications & Data

WebSphere MQ V7 Messaging Backbone

WebSphere MQBridge for HTTP

28

A B

X Y

C

Enabling Flexible Delivery on z/OS for IBM’s Universal Messaging Backbone

4. Publish-and-Subscribe for z/OS– Dynamic and flexible way of determining where messages are sent

– Helps reduce the cost, time and skills involved when changes are required

– Helps define new paths of information flow in an ad hoc manner


The address of each message is “hard-wired”

MessageTo: X, YTo: X, Y

29

A B

X Y

C


To: A, B, C, YTo: A, B, C, YTo: A, B, C, YTo: A, B, X, Y





Each application has to “know” where its messages need to be sent…

30

A B

X Y

C

Z






When changes occur – like new applications being added – all the messages need to be re-addressed

To: X, Y, ZTo: A, B, X, Y , Z

31

A B

X Y

C

Z






Replacing the address of messages with “topics” or “keywords” makes the information flow more dynamic

Topics

32

A B

X Y

C

Z





New applications can receive messages as needed with no modifications required to the other applications


Topics

33

Challenge� Manage change in tax and regulatory environments by

taking advantage of new technology that provides flexibility to application developers

Solution� Service oriented architecture enabling application

developers to reuse existing code, speeding up time to market

� Messaging Backbone based on WebSphere MQ to transfer messages between CICS and batch applications and between applications on different platforms

Benefits� Better cost efficiency due to lower requirements on CPUs� Faster application development time

DATEV – Consumer Products, Germany

Software� WebSphere MQ� CICS Transaction Server� CICS Transaction Gateway� DB2 Universal Database for

z/OS� WebSphere Application

Server

“From DATEV point of view [WebSphere] MQ V7 offers two very important features. First at all the simplifie d usage of PubSub and secondly the asynchronous message consume r.”

“From DATEV point of view [WebSphere] MQ V7 offers two very important features. First at all the simplifie d usage of PubSub and secondly the asynchronous message consume r.”

34

WebSphere MQ V7.0

�Announcements (April 1st)– WebSphere MQ– http://www.ibm.com/common/ssi/fcgi-

bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-068

– WebSphere MQ for z/OS V7– http://www.ibm.com/common/ssi/fcgi-

bin/ssialias?infotype=an&subtype=ca&appname=GPA&htmlfid=897/ENUS208-067

�Electronic GA– Distributed (June 16th)

– z/OS (June 27th)

�Physical (Media) GA– Distributed (June 27th)

– z/OS (June 27th)

35

Migration

ＭＱＭＱＭＱＭＱV1.2V1.2V1.2V1.2



WWWWＭＱＭＱＭＱＭＱ/z/z/z/z

V5.3V5.3V5.3V5.3

WWWWＭＱＭＱＭＱＭＱ////ｚｚｚｚ

V5.3.1V5.3.1V5.3.1V5.3.1WWWWＭＱＭＱＭＱＭＱ////ｚｚｚｚ

V6.0V6.0V6.0V6.0

Recommendation: migrate from these older versions direct ly to MQ V6

Supported backwardmigration path till 30 April 2008

36

Migration to WebSphere MQ V7

V5.3.1 V7V6

Forward migration path

Supported backwardmigration path

No route back to v5.3.1after 30 April 2008

Customers still on MQ V5.3.1 should not wait for MQ V7

Notes:1. The following v6 APARs are required if you are usi ng Queue Sharing Groups (QSGs)

and/or need rollback capability. Target date for d elivery: • To enable coexistence of v6 and v7 Qmgrs in a QSG: P K64466 • To enable backward migration from v7 to v6: PK64463

37

Alternative Path to WebSphere MQ V7

V5.3.1 V7

Forward migration path

Backup v5.3.1 logs,Pagesets, etc.

Backup

Restore v5.3.1 logs,Pagesets, etc.

Notes:1. If any v5.3.1 queue managers to be migrated are m embers of a Queue Sharing Group (QSG), then all que ue

managers in the QSG will have to be upgraded to v7 at the same time.2. If you do choose to go back to v5.3.1, any work d one under v7 will effectively be lost.3. Only consider this option if:

• You do not need experience for your production migr ation.• You don't use queue sharing groups or you have suff icient knowledge and experience for migrating QSG

definitions.• You know you will never have to fallback.• You understand the risks of using unsupported v5.3. 1 code from its end of service until you choose to install

V7.

38

Migration Q&A

� Question: WMQ V7 slides state that it's possible "... to migrate up to v7from v531 but there will be no support for fall back to v531". What does this mean in detail, particularly to QSG users?

– Answer: This means that you will be able to stop your qmgr(s) at v531. Perform migration actions, then restart them at v7. However, if things go wrong, there is no path back to v531. You are reliant on having taken backups of your qmgr logs (containing CF structure backups for shared queues), pagesets and DB2 tables prior to performing the migration actions and restoring them should you need to revert to the v531 configuration. Specifically, a v531 qmgr will not startup in a QSG that has been migrated to v7, a v531 qmgr will not startup if its pagesets have been used in a v7 qmgr.

� Question: There definitely is *no* utility that updates QSG DB2 tables for compatibility between V5 and V7. From this, I conclude that - all members of a QSG have to be switched to V7 at one time (if the "switch" is from V531 Y V7) -- TRUE?

– Answer: Correct. We provide job CSQ45ATB which adds additional tables and columns to existing tables as required by a V7 qmgr. Running this job is one of the migration actions. As you are avoiding V6 you will have a disruptive migration path to V7 - it is not possible to maintain availability of the QSG during migration.

39

Migration Q&A (Continued)

� Question: Shared queue object definitions can only be "migrated" by means of saving them at v531 and restoring them at v7 -TRUE ??

– Answer: CSQ45ATB job will alter the DB2 tables ready for use with v7 qmgrs. Saving definitions prior to migration is a sensible precaution. You'd only have to restore them if you needed to fallback to the v531 configuration.

� Question: What about shared queue messages (CF structure contents)? Will a queue manager started at v7 be able to access CF structures and their contents, as they have been left over by the v531 queue manager?

– Answer: Yes

� Question: I understand that the "migration" surely can be done by means of a WMQ cold start at v7, after definitions and (if necessary) queue contents have been saved at the old V5 level- with both logs, BSDSs and PSIDs created new. The question is: will/ should it be possible to keep the PSID contents, thus preserving (non-shared) object definitions and messages and just newly create the logs and the BSDSs, apply the CSQUTIL/RESETPAGE function to the PSIDs, and then restart at v7 (of course, the DB2 stuff would have to be re-created new completely). So, will v7 be able to work with a consistent set of PSIDsproduced and closed at v5?

– Answer: It will be possible to cleanly stop a qmgr at v5.3.1. Perform the migration actions, then restart that qmgr at v7 without loss of persistent messages and other data. This would be our advised approach (rather than the cold starting you mention above - if you cannot afford to go via v6)

40

WebSphere MQ V7.0 – Pricing

�Distributed: 5%– IBM Software cross-product pricing adjustments to distributed

products in Jan & May 2007

�z/OS: 15%– No price changes since April 2005

– 5% 2005, 5% 2006, 5% 2007 = 15%

41

Single-core Chip

Socket

Chip

Processor Core 1

Dual-core Chip

Socket

Chip

Processor Core 1 2

� Processor Definition is Important in Middleware Licensing� The processor core is the functional unit on which software executes

– Multi-core chips have more than one processor core on the chip

Processor Value Units (PVUs)

IBM Software continues to define a processor = coreAs do most Middleware Vendors…eg. Oracle and BEA

However, some Hardware Vendors . . . Intel, AMD, an d Sun define processor = chip

42

Processor Value Unit Licensing

� IBM distributed middleware is licensed in Processor Value Units(PVUs)– Each processor core assigned a specific number of Processor Value Units

– Acquire the appropriate number of PVUs for each processor core– Each middleware program has a unique price per PVU– PVUs are transferable among systems by product within the enterprise

* Power PC 970 dual-core and Power5 quad-core chips require 50 PVUs per processor core and POWER6TM requires 120 PVUs

120Power6 TM

30RISC Sun T1 Octi-core

50x86 Dual- and Quad-core, Power5 Quad-core

100RISC Dual-core*

100Single-core (All Platforms)

PVU Entitlements per Processor Core

Chip Type

43

Processor Value Unit Licensing Basics

Per Processor Entitlements x 100

= Processor Value Unit Entitlements

� PVUs have a simple comparison to the previous per processor licenses

Per Processor Price/100

= Processor Value Unit Price

� Customer price = # entitlements X price per entitlement . . . UNCHANGED!**

WAS ND on Power5 Dual-core Chip

Per Processor

PricingConversion

Factor

Processor Value Unit

Pricing

Licenses for 2 Processor Cores 2.00 x 100 200

Price per License* $15,500 / 100 $155

Price for 2 Processor Cores $31,000 No Change $31,000

* Suggested Retail Price

Example

� Customer price remains unchanged!

44

Sub-capacity Licensing Leverages PVUs In Virtualized Environments

� Applicable only to SW that uses Processor Value Unit metrics

� Full capacity requires PVU entitlements for all activated processor cores in a server

� Sub-capacity licensing limits the PVU entitlements to the number of processor cores in the partition(s) that are available to the software

Sub-capacity

Partition with three processor

cores


cores

1 2 3 4 5 6

License PVUs for 3 processor cores

IBM eServer Six processor cores activated

Full Capacity


cores


cores

License PVUs for 6 processor cores

1 2 3 4 5 6

IBM eServer Six processor cores activated

What is sub-capacity licensing?

45

Additional Questions

� Additional parameters on cluster to allow usable fail over (cf PMR from "Banque de France") like CLWLPRTY INTERVAL (CLWLPRTYINT)

– We responded to a similar requirement (4070) from the Banque de France (July 2007) Suggested solution given to the the Requirement:

– The CLWLPRTY INTERVAL (CLWLPRTYINT) needs to be present as a new Channel Attribute, so that we can control the time after which, if a channel is in a state other than INACTIVE or RUNNING, messages are sent to the next priority channel. This will allow controlling the backup site switching. The counter has to be reset once the higher priority channel status returns to INACTIVE or RUNNING.

� Upgrade / Cohexist / Migrate (evolution request). Ability to install two version of MQ on the same box. For WMQ 5.3 + 6.0 and WMQ 6.0 + 7.0.

– This is a Candidate for next major MQ release

� Expiration checking for SSL certificate (evolution request). Tool that send an alert when SSL cert. are about to expire (like on WAS 6.x)

– We will consider this for the future. However it is not necessarily as simple as it might sound. The EFFECTIVE expiry of any certificate would need to include the expiry of related CA certs in the chain. That information is not readily available to MQ from the SSL subsystems/toolkits which are used, and would require enhancements in several different products or toolkits before it could be used.

– We would hope that enterprise-level certificate management tools are in place for PKI, that might be able to give warnings outside of MQ of the need to update any certificates.

46

Why IBM?

Over 15 years of proven experience

Connect virtually anything

Most widely deployed Messaging Backbone

Relied upon as the mission-critical Backbone

Continuously Investing and Innovating

–Over 15 years leadership in Messaging technology innovation

–Broad coverage of platforms, technologies, languages–Draw skills from a larger pool – use who you have today–Over 9,300 certified developers for IBM Messaging alone

–Over 10,000 customers using IBM Messaging Backbone–Over 90% of the Fortune 50 and 9 of the Fortune 10–Over 80% of the Global 25 and 7 of the Global 10

–Financial Markets client handles $1 trillion worth of traffic per day on one MQ network*–Banking client sends $7-$35 trillion worth of traffic per day on just one MQ-based SWIFT gateway*

–Over 120 patents and filings within the messaging and ESB space–New WebSphere MQ family products–Regular enhancements, updates and new releases

Results reported from actual IBM WebSphere MQ implementations*

–Government client sends 675 million messages per day*–Banking client handles over 213 million messages per day on z/OS alone*

Entrusted with Tens of billions of messages each day

47

Next Steps

�Think about how you move your information around– What could you gain from taking the next step on your SOA journey?

– What advantages can you gain from Publish-and-Subscribe?

– What benefits can you get from extending IT systems with Web 2.0?

�Ask your IT team to put WebSphere MQ to the test– Open beta of the latest V7 release

�Learn more –MQ V7 www.ibm.com/webspheremq/v7

–MQ TV www.ibm.com/webspheremq/tv

Questions & Answers

© IBM Corporation 2007. All Rights Reserved.

The workshops, sessions and materials have been pre pared by IBM or the session speakers and reflect th eir own views. They are provided for informational purposes only, and are neither intend ed to, nor shall have the effect of being, legal or other guidance or advice to any participant. While efforts were made to verify the completeness and accuracy of the information contained in this p resentation, it is provided AS IS without

warranty of any kind, express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this presentation or any other materials. Nothing contai ned in this presentation is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licens ors, or altering the terms and conditions of the ap plicable license agreement governing the use of IBM software.

References in this presentation to IBM products, pr ograms, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities reference d in this presentation may change at any time at IB M’s sole discretion based on market opportunities or other factors, and are not intende d to be a commitment to future product or feature a vailability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales , revenue growth or other results. Performance is based on measurements and projection s using standard IBM benchmarks in a controlled env ironment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerati ons such as the amount of

multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the w orkload processed. Therefore, no assurance can be given that an individual user will achieve r esults similar to those stated here.

All customer examples described are presented as il lustrations of how those customers have used IBM pr oducts and the results they may have achieved. Actual environmental costs and performan ce characteristics may vary by customer.

The following are trademarks of the International B usiness Machines Corporation in the United States a nd/or other countries. For a complete list of IBM trademarks, see www.ibm.com/legal/copytrade.shtmlAIX, CICS, CICSPlex, DB2, DB2 Universal Database, i 5/OS, IBM, the IBM logo, IMS, iSeries, Lotus, OMEGA MON, OS/390, Parallel Sysplex, pureXML, Rational, RCAF, Redbooks, Sametime, Smart SOA, Syst em i, System i5, System z , Tivoli, WebSphere, and z/OS.

Java and all Java-based trademarks are trademarks o f Sun Microsystems, Inc. in the United States, other countries, or both.Microsoft and Windows are trademarks of Microsoft C orporation in the United States, other countries, or both.Intel and Pentium are trademarks or registered trad emarks of Intel Corporation or its subsidiaries in the United States and other countries.UNIX is a registered trademark of The Open Group in the United States and other countries.Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Other company, product, or service names may be tra demarks or service marks of others.

Date post:	01-Feb-2021
Category:	Documents
Upload:	others
View:	4 times
Download:	1 times

Universal Messaging Backbone for SOAguide.webspheremq.fr/docs/Universal Messaging...WebSphere...

Documents