IBM Software - WebSphere

WebSphere Message
Broker V8 Application
Development I
Course Errata Document
September 10, 2013

Information

WM664 (Classroom)
VM664 (Online)
ZM664 (Self-paced)

ERC1.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.

Image-related items
Description

A directory exists on the image for Exercise 3, but this exercise is paper-and-pencil.
Students can ignore this directory.

Description

Some exercise directories contains extraneous or unused files.

Students can ignore files that are not required by the exercises.

Description

The \solutions directory is spelled \soutions

The exercise solutions are contained in this directory, despite the misspelling. This applies to
several exercises where the solutions directory is referenced.

Lab Setup Guide items

None reported.

Student Exercises Guide items

Location

Exercise 1, part 4, step 7

Instruction reads:
In the Message Flow editor, hover the mouse pointer over the node terminals to display the node names.
Instruction should read:
In the Message Flow editor, hover the mouse pointer over the node terminals to display the terminal
names.
Location

Exercise 2, part 2, step 7

The summary page that is displayed after the pattern is generated might display as a blank page.
If a blank page is displayed:
1. Close the tab.
2. Under the Pattern Configuration item in the Application Development perspective, double-click
EmployeeRecordToQ_summary.html to display the summary page.
Location

Exercise 2, part 3, step 2

Instruction is correct; this text is explanatory text:

After completing this step, the message set project moves to a new application named
EmployeeRecordToQ_Flows.
Location

Exercise 2, part 3, step 8a

It might be necessary for students to click in the Type column twice in order for the drop-down Type menu to
display.
Location

Exercise 2, part 3, step 9a

The screen capture that follows step b belongs to step a. Also, there is extraneous text last name properties
that follows the screen capture.
Location

Exercise 2, part 3, step 9d

Instruction reads:
Click the Overview tab to return to the message set structure.
Instruction should read:
Click the Overview tab to return to the message structure.
Location

Exercise 2, part 3, step 10d

Instruction is correct; this text is explanatory text:

No value is specified for the Message field in this case because only types are defined in the message
definition, and only one message definition is defined in the message set.

Location

Exercise 2, part 4, step 3

Instruction is correct; this text is explanatory text:

Be sure to copy the file, not move the file.

Location

Exercise 2, part 4, step 4

Each successful run writes five records to the EMPLOYEE_OUT queue. There are five extraneous records in the
queue initially; these records can be disregarded.

Location

Exercise 2, part 5, step 2

Instruction tells students to close the project.

Disregard this instruction. In WebSphere Message Broker Version 8, this project became an application instead
of a project, and applications cannot be explicitly closed or opened.
Location

Exercise 2, part 5, step 4

Instruction tells students to delete the broker archive (.bar) file.

Disregard this instruction. It is not necessary to delete the .bar file.
Location

Exercise 3, step 1

Instruction reads:
In this flow, an MQInput node is wired to a Compute node. The Compute node Failure terminal is wired to
an MQOutput node. The message fails on the node that is labeled Out.t
Instruction should read:
In this flow, an MQInput node is wired to a Compute node. The Compute node Failure terminal is wired to
an MQOutput node. The message fails on the node that is labeled Out.

Location

Exercise 3, step 3

Instruction reads:
In this flow, an MQInput node is wired to a Compute node. The Compute node has a wired Out terminal
and an MQOutput node that is wired to its Failure terminal. The message fails on the node that is labeled
Out terminal.
Instruction should read:
In this flow, an MQInput node is wired to a Compute node. The Compute node has a wired Out terminal
and an MQOutput node that is wired to its Failure terminal. The message fails on the node that is labeled
Out.
Location

Exercise 3, step 4

Instruction reads:
In this flow, an MQInput node is wired to a Compute node. The Compute node has MQOutput nodes that
are wired to the Out terminal and Failure terminal. The message fails on the Compute node.l
Instruction should read:
In this flow, an MQInput node is wired to a Compute node. The Compute node has MQOutput nodes that
are wired to the Out terminal and Failure terminal. The message fails on the Compute node.
Location

Exercise 4, step 1

The PI file that the students import already contains a Trace node in the message flow.
In step 1c, students should delete the existing Trace node, and then follow the remaining instructions as written.
Location

Exercise 4, part 2, step 2c

In addition to verifying that the MQInput node uses the specified queue, students should also verify that the
Message drop down property under Input Message Parsing is set to {}:msg_CUSTOMERCOMPLAINT

Location

Exercise 4, part 2, step 3

The trace output file (trace.txt) already contains data.

Students can either delete the trace.txt file (it is re-created during testing), or disregard the extraneous data
that the file contains.
Location

Exercise 4, part 5, step 5e

Instruction reads:
Check the MB7BROKER Administration Log view in WebSphere Message Broker Explorer for a
message that confirms that the Trace node is disabled.
Instruction should read:
Check the MB8BROKER Administration Log view in WebSphere Message Broker Explorer for a
message that confirms that the Trace node is disabled.
4

Location

Exercise 4, part 8, step 1

The debug port is already set on the image. Students should follow the steps as indicated, but do not have to
change any settings.
Location

Exercise 4, part 8, step 4

Although no breakpoints are set, when the exception is raised, the Switch Perspective dialog is displayed.
Students should click Yes to allow the switch to occur, and then click Resume.

Location

Exercise 5, part 2, step 7a

Instruction reads:
On the Basic tab, set the ESQL module to
Instruction should read:
On the Basic tab, set the Java Class to
Location

Exercise 5, part 2, step 2b

If the Type Selection menu is blank, clean the projects by selecting Project > Clean and then try again.
Location

Exercise 6, part 2, step 4g

Instruction is correct; this text is explanatory text:

This search causes an index to be built for future searches, so this search can take several minutes.
Location

Exercise 7, part 2, steps 1a and 1b

Instructions read:
(1a) In the Broker Development view, right-click Independent Resources.
(1b) Click New > Independent Resources > Other. The New wizard is shown.
Instructions should read:
(1a) In the Broker Development view, right-click RouteComplaint.
(1b) Click New > Other. The New wizard is shown.
Location

Exercise 7, part 2, step 4

This instruction is extraneous; ignore this step.

Location

Exercise 7, part 2, step 5d

Instruction is correct, but explanatory text about the subflow not being included is incorrect. The subflow is
included in the project.
Location

Exercise 7, part 3, Option 1, steps 2 and 3

If students use the cut-and-paste option, the modules that are copied from the file are incorrectly named. The
5

CREATE COMPUTE MODULE statements include the prefix Myflow_ in the module name. Students should
delete that prefix.
Location

Exercise 8, part 4, step 1h

Instruction is correct, but must be followed by another instruction before step 1i:
Click Next.
Location

Exercise 8, part 6, step 1c

The CREATE DATABASE MODULE statement should specify Lab8_Database, rather than Store_Msg.
Location

Exercise 9, Part 3, step 2

Deployment fails due to an internal error in Message Broker V8.0.0.0. This issue was reported as a product
defect. See the course errata documentation for any additional information or updates on this problem.

Student Notebook items

Location

Student guide pg. 2-73 (figure 2-51)

The student notes for this visual are incorrect.

The correct notes for this visual are located with figure 2-52.

Location

Student guide pg. 2-74 (figure 2-52)

The student notes for this visual are incorrect.

The correct notes for this visual are located with figure 2-53.
Location

Student guide pg. 2-75 (figure 2-53)

The student notes for this visual are incorrect.

There are no student notes for this visual.

Course presentation items by unit

None reported.

End of document