Transcript Selling WebSphere made Simple

®
IBM Software Group
IBM Support for FIA (FIXML) Messaging
Enterprise Service Bus View of Standards
The Evolution of Messaging for Financial Services
March 2005
Jim Glenister
IBM Consultant, WebSphere Software
© 2005 IBM Corporation
IBM Software Group | WebSphere software
WMQ and FIXML Standards for Financial Services
Future Systems
T+1 (T+0) , STP
STP SERVICE PROVIDER
CUSTODY + CLEARING
(OCC, DTCC, Other)
PRIMARY FINANCIAL MARKETS SYSTEMS
(EXCHANGES, NASD)
COLLATERAL
POSITION
LAST SALE
BID - ASK
NET SETTLEMENT
POSITION
TRADES
RETRANSMITTED DATA
VALUE ADDING
MKT INFORMATION
PROVIDERS
RETRANSMIT REQUEST
POST TRADE VMU
TRADING & REPORTING
MKT DATA
REPORTING
MARKET DATA
- TRADE DATA (NOE)
- CLEAR & SETTLEMENT
ORDER
EXECUTION
ORDERS
EXECUTIONS
TRADES
COMPARISON
POSITION
MKT
INFO
FINANCE INDUSTRY SHARED ENTERPRISE SERVICE BUS
MDS INQUIRIES
SECURITIES FIRM
OFFICES
EXECUTIONS
ORDERS
ORDERS +
INQUIRIES
SECURITIES FIRM
REPORTS +
CONFIRMS
ORDER + TRADE
PROCESSING
ENTERPRISE
MESSAGING
ORDERS +
INQUIRIES
TRADES
P+S
REPORTS +
CONFIRMS
SECURITIES FIRM
ACCOUNTING
CLEARANCE
SETTLEMENT
CONFIRMS
MARGIN CALLS
CLIENT DIRECT
MESSAGING
SCOPE OF FIXML
MESSAGING
STANDARDS
PRIVATE CLIENT
ACCESS GW
INVESTMENT
MANAGER
ACCESS GW
2
IBM Software Group | WebSphere software
FIA to spearhead related efforts:
Establishing standards for message transmission

Message Descriptors
 Standardize on the usage of Message Descriptors

Put and Get
 Guidelines for setting fields and Options in an MQ-Put
 Guidelines for setting fields and Options in an MQ-Get

Queue Definition
 Queue Depth based on volume
 Maximum Message Length

Message Data Formats
 Standardize on the use of ASCII for FIXML messages

Dead Letter Queues
 Processing messages from Dead Letter Queues

Channels Exit Routines

Hardware requirements / Software requirements
Exchanges and Firms to work with FPL to define a FIXML
messaging API for re-transmission of messages
Origin
Destination
Date/Time
Sequence Nbr
Type
3
IBM Software Group | WebSphere software
How WMQ (MQSeries) Works – FIA Standards
Requesting Application
Serving Application
Serving Application
PUT MSG
GET MSG
GET MSG
MSG
MQSeries
Interface
Message
Queuing
Service
XMIT
Q
MQSeries
Interface
MQSeries
Interface
Q1
Q1
Message
Queuing
Service
Message
Channel
Agent
Message Queue
Manager
Q2
MSG
DLQ
Message
Channel
Agent
Network
Message Queue
Manager
4
IBM Software Group | WebSphere software
WMQ Queue Manager Structure – FIA Standards
Command Queue
Data Conversion Interface
Security Enabling Interface
Queue
Manager
Kernel
Name Service Interface
Event Queues
DLQ
Pluggable
Trigger
Monitors
Pluggable
Message
Channel
Agents
Exits
Channels
Queues
Performance
5
IBM Software Group | WebSphere software
Messaging Service Environment Characteristics

















Multiple Platforms (zOS/OS390, UNIX , Windows NT/2000, AS/400, Tandem)
"Store and Forward" of Messages
Assured Delivery (Once, and only once) of Message Objects
Persistent or Non-Persistent Messages (Designated by message)
Priority Levels on Messages
Purge of "Killer" Messages that Repeatedly Cause Failures
Message Expiry (Time-to-live for a given message)
24 x 7 Continuous Operation
Transactional Integrity as a Resource Manager and Recovery Coordinator
Failover and Automated Recovery of Messaging Access to Business Services
High Volume Performance with Peak Load Handling Mechanisms
Flexible Message Resource Naming (Alias names that reflect business service )
Security (Protected message resources, data privacy via encryption, intrusion protection)
Automated Management Controls (Programmed commands, monitoring, event alerts)
Feedback: Confirmation and Notification Reports
Message Logging (Optional redundant logging)
Large Objects ( --> 100MB)
6
IBM Software Group | WebSphere software
Messaging Application Characteristics















Multiple Platforms (zOS/OS390, UNIX , Windows XP/2000, AS/400, Tandem)
Consistent APIs in Multiple Programming Languages (Java, C, Cobol, Others)
"Business Service Name" Transparently Mapped to Message Destinations
Transparent Placement of Messages on Local or Remote Queues
Support for Synchronous and Asynchronous Style
Shared or Exclusive Queue Usage
Message Arrival Triggers Initiation of Server Processes
Multiple Servers Concurrent Access to Queues with Preservation of Message Integrity
Correlation of Requests and Corresponding Replies
Selective "Get" of a Specific Message from the Message Queue
Non-destructive Browsing of Message Queues
Selective Commit/Rollback (Syncpoint) Controls for Unit of Work Integrity
Support for XML Messages
Applications Have No Communications Network Responsibility or Awareness
Multiple Programming Models Supported by Messaging





Client-Server
One-way Event Push (Asynchronous "Fire-and-Forget" Datagram)
Publisher-Subscriber
Object Oriented Design (e.g., JMS Message Driven Beans)
Multi-step Workflow Processing
7
IBM Software Group | WebSphere software
Messaging Architecture – Point-to-Point Patterns
8
IBM Software Group | WebSphere software
Messaging Architecture - Publish and Subscribe Patterns
9
IBM Software Group | WebSphere software
WMQ: Design for Performance
Exploitation of WMQ Capabilities
 Priority scheduling of messages and processes
 Thresholds on queues
 Load-responsive multiple server instantiation (e.g., Triggers)
 Alias queue name = service name (can inhibit G/P, change priorities)
 Message channel and queue activity (persistent, non-persistent)
 Logical unit of work (syncpoint) controls (MQCMIT, MQBACK)
 Batch transmissions across channels
Efficiencies for Throughput and Fast Response
 Long running tasks (eliminates startup/shutdown transients)
 Persistent-connection channels between queue managers
 Parallel processes (e.g., Logging can be asynchronous via MQ)
 'Fast Path' techniques
Resources Allocated to Meet Critical Peaks (Chaos Control)
 Deferred processing of non-critical requests
 Deferred processing of secondary activities
 MQSeries Log on separate, high speed devices
 Page sets and buffer pools
10
IBM Software Group | WebSphere software
WMQ High Availability - Cluster Groups
MESSAGE HUB CLUSTER GROUP
1
REQUESTER 1
REQUESTER
APPLICATION
REQUEST
QMR1
REPLY
REPORT
4
MESSAGE HUB SITE 1
QMH1
ROUTING
LOGGING
FORMATTING
ASSURED DELIVERY
RECOVERY
REPORTING
SERVER CLUSTER GROUP
2
SERVER 1
REQUEST
QMS1
REPLY
REPORT
3
SERVER 2
REQUEST
MESSAGE HUB SITE 2
REQUESTER n
REQUESTER
APPLICATION





REQUEST
QMH2
QMRn
REPLY
REPORT
ROUTING
LOGGING
FORMATTING
ASSURED DELIVERY
RECOVERY
REPORTING
SERVER
APPLICATION
QMS2
REPLY
REPORT
SERVER n
REQUEST
QMSn
REPLY
REPORT
SERVER
APPLICATION
SERVER
APPLICATION
Transparent Access to QMs and Queues in a Cluster
Workload Balancing via WLM Exit
Failover to Surviving Members of Cluster Group
Application Affinity (Requester-Server) if Required
Administrative and Operational Support (e.g., Q Definitions, Suspend/Resume)
11
IBM Software Group | WebSphere software
WMQ High Availability - z/OS V5.3 Shared Queue Groups
12
IBM Software Group | WebSphere software
Message Flow Standards via WMQ (MQSeries) and ESB
13
IBM Software Group | WebSphere software
WMQ and WBI Family Product Detail and Directions
Graham Oakes, IBM
14
IBM Software Group | WebSphere software
Summary
 IBM appreciates the opportunity to work with FIA to evolve the FIXML
over WMQ standards needed for high performance and reliable
communication.
 The objective of an ESB approach is to transcend the WMQ transport
layer with value add services that reduce the cost of developing and
managing disparate interfaces. An FIA sponsored ESB can enable
sharing of standards and components that implement them:
 A communications “architecture” that enables software applications that run
 on different platforms and devices
 or which are written in different programming languages
 or which use different programming models
 or which use different data representations
 to reliably communicate with no disruption to existing applications or interfaces.
 IBM has the most comprehensive WMQ and ESB skills, experience
and offerings that we can share with the FIA membership. The
formation of a working group and named interfaces to pursue the
standards is recommended as the next step.
15
IBM Software Group | WebSphere software
FIA Standards Working Group Focus and Structure
16
IBM Software Group | WebSphere software
IBM WMQ and WBI Components of FIA (FIXML) ESB
FIXML Client
Access Adapter
Requester
Interface
WBI Business Integration Services
FIXML Service
Provider Connector
Business
Process
Manager
Server
Interface
Service
Registry
Message
Transformation
Service
Message
Locator
Transformation
Transaction
Standards
Process State
Management
Business
Event
Rules
Process
+
Flow
Routing
Logic
Rules
Client
Profiles
Message
Transformation
Logical
Recovery
Session
State
Services
Data Base
Standards
Standard
Messages
FIXML Data
Business Process Interfaces
(APIs, Objects, Adapters)
Transaction State
Management
(State, UDDI, Metadata)
WBI Message Broker - FIXML Gateway and Broker Services
Rules Based
Routing
Message
Formatting
Resend
Retransmit
Alert
Notification
Data Enrichment
Services
Publish
Subscribe
Message Flow
Management
Bridges and
Adapters
Message
Repositories
WMQ Basic Infrastructure Services
System
Administration
+
Resource
Management
Security
Exception
Handling
Logging
Services
Trigger
Monitor
Configuration
Management
Event
Monitor
API
Services
Queue
Management
Data
Transform
Channel
Session State
Service
Monitoring
+
Recovery
Management
17