IBM Cloud

IBM MQ V10 Application

Development I

Course Corrections Document

August 22, 2017

WM666 (Classroom)
ZM666 (Self-paced)
ERC 1.0

About this document

This document contains information about issues that were
encountered during deliveries of this course. These issues will
be addressed in subsequent updates of the material.
You should review this document before the start of class, and
use this list as the first point of reference if issues arise.
Student Exercises Guide items

The step reads:

For the File name or pattern property, type: EXPLOYEE.TXT.

The step should read:

For the File name or pattern property, type: EMPLOYEE.TXT.

Part 3, Step 4a

Add the following Information note:

Setting Record Detection to Fixed Length causes the following warning message in the Problems view when the
message is saved:
Node 'EmployeeFile' is configured to propagate separate messages for each record
in the input file, but has no flow wired to its End of Data terminal.
In Integration Bus, you can wire the End of Data terminal to process an “end of data” message after all the data in a
file is processed. You can ignore this warning message in this exercise because no extra processing is required
when the end of the data is read. For example, if you were writing the data to a single output file instead of separate
messages, you would wire the End of Data terminal to the FileOutput node Finish File terminal.
In this exercise, you can eliminate this warning message by setting Record Detection to Whole File. In a real
application, Whole File might not be a valid choice because it limits the allowable file size.

Exercise 7
Part 3 Step 3
Attention!
 You are using port 2311 as the Java Debug Port. You are not using port 4415 shown in the sample Debug
Configuration screen capture example shown in Step 3c.
 You use the same port you set in Step 1.
 In Step 3e you confirm the integration server default and port 2311.

The step reads:

Reference the ComplaintDataModels shared library in the RouteApplication application

The step should read:

Reference the ComplaintDataModels shared library in the RouteComplaint application

End of document