WebSphere MQ (MQSeries) Programming - Java
Book Now - 1 Delivery Method Available:
Classroom Virtual Classroom Private Group - Virtual Self-Paced OnlineOverview
This four day class will equip the student with an understanding of the object orientated approach to WebSphere MQ programming which is quite different from that used within procedural languages like COBOL.
The course has extensive practical exercises that reinforce the lecture sessions and attendees are expected to already have a good understanding of the JAVA programming language as this cannot be taught during the course.
Please note the course may require the client to set up the classroom environment to allow practical exercises to be done and attendees must be familiar with the JAVA development environment that is to be used during the course.
Although this is not a formal WebSphere MQ design course: hints, tips and problems will be discussed to help the student come to an understanding of some of the design issues created by the asynchronous environment.
On completion of the class, students will be able to:
- Write WebSphere MQ JAVA programs.
- Understand some of the design issues that have to be faced.
- Understand some of the problems faced by the queuing administrator.
- Within limits, define the objects that they, the programmer, may need to define during the development
Training Partners
We work with the following best of breed training partners using our bulk buying power to bring you a wider range of dates, locations and prices.
Prerequisites
The student is expected to be a competent Java programmer, be able to use the hardware and software platforms provided by the client and have a level of understanding gained either from the Websphere Overview course or equivalent source. Attendees failing to meet these requirements may be asked to leave the course if, in the opinion of the presenter, that failing is detracting from the presentation. Although this is not an WebSphere MQ administration course, the student will be expected to define their own WebSphere MQ objects (queues, processes etc.) and ensure that channels, listeners, trigger monitors etc. are running.