General » Introduction to HW & SW » TracksOperating systems » MVS - z/OS » UNIX - Linux - AIX » VMwareDatabases, transaction systems and middleware » DB2 for z/OS » DB2 UDB for Linux, UNIX and Windows » Oracle » SQL Server » MySQL » IMS » CICS » WebSphere MQ » WebSphere Application Server » Business intelligence and data warehouseApplication development » Methods and techniques » TOGAF » PRINCE2 » Programming languages » Internet development » Object Oriented systems » Java » IBM development tools » SAS » XML » SOA & web servicesSystems management » ITIL
Practical informationRegistration Definition
WebSphere MQ
IBM WebSphere MQ (Message Queueing) is a network communication technology developed by IBM in March 1992. This technology allows independent and possibly non-concurrent applications on a distributed system to communicate with each other. MQ is available on a large number of platforms (IBM and non-IBM), including mainframe, Unix and Windows.
(Bron: Webster's Dictionary of Computing)
Importance
WebSphere MQ has been metamorphosed the last few years. It has been developed as an alternative, mainframe oriented application development methodology - an alternative for special applications.
The introduction of a distributed component has become important - WebSphere MQ is able to overcome the differences between systems and platforms. An important element of virtualisation!
Nowadays, WebSphere MQ has become an important element of the Service Oriented Architecture (SOA) strategy of IBM: the WebSphere Application Server (WAS) message bus is the implementation of WebSphere MQ server.
Core competencies
Since its development in 1992, WebSphere MQ has been important for ABIS. ABIS has followed its evolution. That's why not only the domain WebSphere MQ has changed a lot, but also the domains SOA and WebServices!
The set-up of a WebSphere MQ distributed environment is not easy. That's why we offer a seriies of basic and management courses. An optimal configuration and tuning is crucial: availability, security and efficiency depend on it!
How to develop message-oriented, asynchronous applications? From a traditional development environment (e.g.based on Cobol)? From Java (e.g. by means of JMS) and Visual Basic? And what's the advantage of message broking and workflow management?
Service Oriented Architectures are often based on 2 alternative infrastructures: a web service architecture as well as a message/queue-based architecture. That's why WebSphere MQ is important! We should concentrate on the role of WebSphere MQ with the integration of traditional, backend, IMS and/or CICS applications (see In focus - WebSphere backend integration). What's the task of message brokers and workflow management?
Certification
By means of the ABIS course hand-outs and based on practical experience, our participants and course leaders have already taking the following certificates (details - see Certification matrix 'WebSphere Application Server'):
Course leaders
Koen De Backer, Responsible for the WebSphere MQ domain.
Training methods
Training | Classroom instruction | Cases | Indivodual training | Coaching |
Please find an overview of the standard trainings in this borchure. | Available as individual trainings. | Available. |
| |
Consulting | Alternative architecture. | |||