20
www.royalcyber.com WebSphere MQ Services
www.royalcyber.com
WebSphere MQ Services
Agenda
Royal Cyber Introduction
Connectivity Challenges
What is WebSphere MQ?
WebSphere MQ Queuing
MQ Clustering
WebSphere MQ Troubleshooting
Performance Tuning
Royal Cyber MQ Services
Established: Based in Illinois (USA), serving multiple industries including many Fortune 1000+ companies since 1997 by experienced IT professionals. To offer cutting edge IT services globally help organizations both in Public and Private sector to improve and modernize their services supplementing organization’s skill set with team augmentation On-site resource deployment Improved Return-on-Investment (ROI) by taking projects offshore
Achievements:
To date, Royal Cyber Inc. has grown into a reputable IT firm not only in USA but also in European, Middle Eastern and South Asian Markets.
4
Why?
Reduce Complexity
Manage Exponential Change
Ensure Compliance
Reduce Cost
Improve Control
Customers want to improve this….
… to run their business like this.
The Connectivity Challenge
What is WebSphere MQ?
A middleware product that implements a messaging and queuing framework.
Middleware - an intermediate software component that bridges dissimilar computing environments. Unix, MVS, OS/400 Tandem,
VMS, NT, etc.
SNA, NetBios, TCP/IP
Cobol, C, JAVA
Application A
Application B
WebSphere MQ
MQPUT
MQGET
Any platform Any programming language
Any platform Any programming language
How Messaging & Queuing Works
Communication can be one-way or two-way. Here, A sends to B on Queue1, and B responds to A on Queue2
Asynchronous vs. Synchronous
Communications
Synchronous: App sends request, then blocks until request is processed.
Requires service available at EXACTLY same time as client needs service.
Asynchronous: App sends request and checks at some future time if complete.
Service need not be available when client sends request
No Constraints on Application Structure
There can be a one to many relationship between applications
Or a many to one relationship between
applications
Applications Shielded from Environmental
Differences Applications
Programmatic API
Communications using Message Channels
Queue Manager
Queue Manager
Message Queue
Enhancements in WebSphere MQ v7.1
WebSphere MQ Clients: Enables an application to connect remotely or locally to a WebSphere MQ queue manager.
Publish/Subscribe: Increases messaging capability from point-to-point
messaging to a less coupled style of messaging.
MQ Clusters: Allow multiple instances of the same service to be hosted
through multiple queue managers, to enable load-balancing and fail-over and
simplify administration.
Additional Features: Multi-version and re-locatable installation for easier install, testing, and migration
Support for virtualized environments
Scalability and message throughput enhancements
Reduced complexity for enabling and checking system security
Telemetry function for lightweight connectivity to mobile and other devices now included in the package
Distribute across multiple end-points with integrated Multicast function
Upgrade from trial-to-production deployment
MQ Clustering • Queue Manager required for every broker instance
• Queue Manager to be created and configured prior to broker
• Active and Standby Queue Manager
• System with Queue Manager instances to share Data and Logs Directory
• Active and Standby Queue Manager sharing resources from the shared storage
• Locking and release mechanism for resources
WebSphere MQ Troubleshooting
An MDB listener fails to start: If an MDB listener deployed against a listener port fails to start, you should see the following message:
Server memory consumption and java.lang.OutOfMemoryError exception when processing JMS messages: Intensive processing of JMS messages using the default JMS provider can cause a java.lang.OutOfMemoryError exception and cause the application server to terminate
Troubleshooting Tools: a simple command line tool (xmqdspev) to display WebSphere MQ events that are generated on the SYSTEM.ADMIN.*.EVENT event queues.
• To troubleshoot WebSphere MQ configuration issues. • To troubleshoot WebSphere MQ application issues. • To monitor and record the activity on a queue manager. • To provide event information easily consumable by other tools.
WebSphere MQ Performance Tuning
The following checklist details the major WebSphere® MQ tuning considerations:
Make judicious use of tracing
Employ message management
Set the CCSID
Configure appropriate logging
Enable MQ connection pooling in WebSphere Application Server
Case Study
ECN
MQ Prairie Receiver MQ Prairie Sender
WebSphere MQ Services WebSphere MQ Installation and Configuration
System Architecture Design & Implementation
Application Design using WebSphere MQ
Application Programming using native MQ interfaces & JMS (Java Messaging System)
Testing, Troubleshooting & Performance Tuning WebSphere MQ Environment
Deployment Strategies including Distributed Queue Management and Clustering Techniques
MQ Clustering for High Availability
Migration from older versions to V7.0/7.1
Apply fix patches for resolve issues and improve performance
Complete monitoring solution for web administrators using command line and GUI based custom tools
L2 Support for MQ environment
Support for advancements and growth of environment using SOA based solutions: WebSphere Message Broker and Data Power Appliances
