Instructions

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>.
La impresión está destinada únicamente para

uso personal y privado. No se podrá reproducir o
retransmitir ninguna parte de este libro sin la autorización previa del editor. Todo infractor será objeto de acciones
legales.
IBM Training
Student Exercises
IBM Integration Bus V10 System Administration

Course code WM646 ERC 1.0
IBM Systems
Middleware
IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. No se
podrá reproducir o
retransmitir ninguna parte de este libro sin la autorización previa del editor. Todo infractor será objeto de acciones legales.
Student Exercises
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business
Machines Corp., registered in many jurisdictions worldwide.
The following are trademarks of International Business Machines Corporation, registered in many
jurisdictions worldwide:
AIX® CICS® Data Power®
DB2® developerWorks® Express®
Informix® MQSeries® Notes®
ObjectGrid® PartnerWorld® PowerHA®
RACF® Redbooks® Tivoli®
WebSphere® z/OS®
Linux is a registered trademark f Linus Torvalds in the United tes, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other
countries, or both.
Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle
and/or its affiliates.
UNIX is a registered trademark of The Open Group in the United States and other countries.
VMware and the VMware "boxes" logo and design, Virtual SMP and VMotion are registered
trademarks or trademarks (the "Marks") of VMware, Inc. in the United States and/or other jurisdictions.
Other product and service names might be trademarks of IBM or other companies.
December 2015 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without any
warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer responsibility and
depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been
reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will result elsewhere. Customers
attempting to adapt these techniques to their own environments do so at their own risk.
© Copyright International Business Machines Corporation 2015.

This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
podrá reproducir o
Student Exercises
Contents
Trademarks ........................................................................................................................................... v
Exercises description ........................................................................................................................ vii
Exercise 1. Integration node setup andcustomization .................................................................. 1-1

Parti: Get build and version information ................................................................................ 1-2
Part 2: Verify user authorizations ............................................................................................. 1-7
Part 3: Create an integration node and integration servers ...................................................... 1-8
Exercise 2. Connecting to IBM MQ ................................................................................................. 2-1

Part 1: Use IBM MQ Explorer to create the queue manager .................................................... 2-4
Part 2: Create the integration nodes and integration servers ................................................... 2-5
Part 3: Create the SYSTEM.BROKER queues and topics on the integration node queue
manager..................................................................................................................................... 2-8
Part 4: Create an MQEndpoint policy ..................................................................................... 2-10
Exercise 3. Using the IBM Integration Toolkit ............................................................................... 3-1

Part 1: Work with a simple message flow ................................................................................. 3-5
Part 2: Create and deploy a BAR file ........................................................................................ 3-8
Part 3: Test the message flow by using the Flow Exerciser ................................................... 3-13
Exercise 4. Administering the IBM Integration Bus runtime components .................................. 4-1
Parti: Use the IBM Integration command interface ............................................................. 4-3
Part 2: Use the IBM Integration web interface ....................................................................... 4-6
Part 3: Use the IBM Integration API Exerciser ................................................................... 4-12
Part 4: Back upand restore the integration node ............................................................... 4-16
Exercise 5. Using file-based security to control administration access ..................................... 5-1

Part 1: Activate file-based security on the integration node ..................................................... 5-4
Part 2: Define administration roles and set file-based permissions .......................................... 5-6
Part 3: Test the IBM Integration web interface with security ..................................................... 5-8
Exercise 6. Using queue-based security to control administration access .............................. 6-1

Part 1: Set IBM MQ permissions for users ............................................................................... 6-4
Part 2: Test the default unsecured environment ....................................................................... 6-6
Part 3: Activate administration security and test the secured environment ............................ 6-10
Exercise 7. Implementing web services and web services security ........................................... 7-1
Part 1: Configure the integration node HTTP listener ............................................................... 7-4
Part 2: Review the message flows ........................................................................................... 7-5
Part 4: Test the web service application ................................................................................. 7-12
Part 5: Implement SSL for the web service application ........................................................... 7-14
Exercise 8. Using problem diagnosis tools ................................................................................... 8-1

Part 1: Examine and deploy the BAR file ................................................................................. 8-3
Part 2: Test the message flow ................................................................................................... 8-5
Student Exercises
© Copyright IBM Corp. 2015 Contents iii

Course materials may not be reproduced in whole or in part
without the prior written permission of IBM.
podrá reproducir o
Part 3: Manage traces and Trace nodes ................................................................................... 8-6

Part 4: Administer the message flow debugger ...................................................................... 8-11
Exercise 9. Identifying runtime problems ............................................................................................ 9-1

Part 1 : Analyze message flow runtime failures ....................................................................... 9-2
Part 2: Isolate and identify problems ........................................................................................ 9-6
Exercise 10. Viewing runtime statistics ............................................................................................. 10-1

Part 1 : Enable message flow and resource statistics ........................................................... 10-3
Part 2: View message flow and resource statistics ................................................................ 10-5
Part 3: Set up subscriptions for resource statistics .............................................................. 10-10
Exercise 11. Administering workload management policies .......................................................... 11-1

Part 1 : Create a workload management policy ..................................................................... 11-3
Part 2: Attach a workload management policy to a message flow ......................................... 11-4
Exercise 12. Recording and replaying message flow data ............................................................ 12-1
Parti: Set up the environment for record and replay .............................................................. 12-3
Part 2: View messages in the IBM Integration web interface ................................................. 12-6
Part 3: Replay messages ...................................................................................................... 12-11
Part 4: Handle failed messages ............................................................................................. 12-13
Appendix A. Exercise solutions ........................................................................................................... A-1
iv Integration Bus V10 Administration © Copyright IBM Corp. 2015

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. No
se podrá reproducir o
Student Exercises
Trademarks
The reader should recognize that the following terms, which appear in the content of this training
document, are official trademarks of IBM or other companies:
jurisdictions
AIX® worldwide: Data Power®
DB2® CICS® Express®
Informix® developerWorks® Notes®
ObjectGrid® MQSeries® PowerHA®
RACF® PartnerWorld® Tivoli®
WebSphere® Redbooks®
z/OS®
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries,
or both.
trademarks or trademarks (the "Marks") of VMware, Inc. in the United States and/or other
jurisdictions.
© Copyright IBM Corp. 2015 Trademarks v

Student Exercises
6 Integration Bus V10 Administration © Copyright IBM Corp. 2015

Student Exercises
Exercises description
This course includes the following exercises:
• Integration node setup and customization
• Connecting to IBM MQ
• Using the IBM Integration Toolkit
• Administering the IBM Integration Bus runtime components
• Using file-based security to control administration access
• Using queue-based security to control administration access
• Implementing web services and web services security
• Using problem diagnosis tools
• Identifying runtime problems
• Viewing runtime statistics
• Administering workload management policies
• Recording and replaying message flow data
In the exercise instructions, you can check off the line before each step as you
complete it to track your progress.
Most exercises include required sections, which should always be completed.
It might be necessary to complete these sections before you can start later
exercises. Some exercises might also include optional sections that you might
want to complete if you have sufficient time and want an extra challenge.
Use the following user name and password to log in to course image:
User name: iibadmin Password: weblsphere
© Copyright IBM Corp. 2015 Exercises description 7

Student Exercises

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado.
No se podrá reproducir o
Student Exercises
Exercise 1. Integration node setup and

customization
What this exercise is about

In this exercise, you complete the configuration tasks that prepare the IBM
Integration Bus environment for use. You also start the IBM Integration web
user interface to view the integration node and integration server properties.
What you should be able to do

After completing this exercise, you should be able to:
• Get build and version information for IBM Integration Bus components
• Verify user authorizations
• Create and verify an integration node and integration server
• Start the IBM Integration web user interface
Introduction
In the first part of this exercise, you verify the maintenance (fix pack) levels of
the IBM Integration Bus software.
In this second part of the exercise, you verify that the user ID that is used in
the lab exercises has administrative privilege to create and manage IBM
Integration Bus and IBM MQ resources.
In the third part of this exercise, you use the IBM Integration command
interface to create an integration node and report integration node properties.
You then use the IBM Integration command interface and the IBM Integration
web interface to create integration servers on the new integration node.
Requirements
• IBM Integration Bus V10
• IBMMQV8
• User ID of “iibadmin” that is a member of the “mqbrkrs” group
© Copyright IBM Corp. 2015 Exercise 1. Integration node setup and customization 1-1
Student Exercises
Exercise instructions
The required licensed programs are already installed on your exercise image. These licensed
programs include:
• IBM MQ V8
• IBM DB2 Express 10.1
Your user ID (iibadmin) is a member of the Windows “Administrators” group.
For all exercises in this course, use the information that is listed in this table.
Windows user ID for lab exercises iibadmin
Windows password for lab exercises weblsphere
IBM Integration Bus installation directory c:\Program Files\lBM\lIB\10.0.0.0\

IBM MQ installation directory c:\Program Files\lEM\Websphere M2
TESTNODE iibadmin
IBM Integration Bus integration node for
development
The lab image also includes the c:\iabfiies directory that contains, test files, scripts, and other
components that you use during the course exercises.
Part 1: Get build and version information

It is important to know the current software version and build level for all your software. In this part of
the exercise, you verify the maintenance (fix pack) levels of the IBM Integration Bus software.
_ 1. Get the software version information for the IBM Integration Toolkit.
_ a. From the Windows Start menu, click All Programs > IBM Integration Bus 10.0.0.0 >
IBM Integration Toolkit 10.0.0.0. Optionally, you can double-click the IBM Integration
Toolkit shortcut icon on the Windows desktop.
After a few moments, the Integration Toolkit opens and the Welcome page is presented.
On the Welcome page, you can learn more about the features of Integration Bus, see
what is new in IBM Integration Bus V10, and install language packs for the Integration
Toolkit.
1-2 Integration Bus V10 Administration © Copyright IBM Corp. 2015

Student Exercises
b. Close the Welcome page by clicking Go to the Integration Toolkit.

c. To display configuration information about the Integration Toolkit and the Integration Bus
environment, click Help > About IBM Integration Toolkit.
The About IBM Integration Toolkit window shows the Integration Toolkit version
information.
Student Exercises
The Build ID identifies the most recent fix pack that is applied. In this example, the build
ID is 10.0.0, dated March 13 2015 (20150313).
d. The icons across the About IBM Integration Toolkit window contain information about the
features that are installed in the Integration Toolkit. Click one or more of these icons and
explore the installed elements.
e. Click Installation Details in the About IBM Integration Toolkit window to show the
installed Integration Toolkit components and their versions.
Within the Installation Details page, you can select tabs to view the installed components,
the IBM Integration Toolkit installation history, the installed features, and plug-ins.
Installed Software Installation History Features Plug-ins Configuration
Name Version Id
c> Dali Java Persistence Tools - JPA Support 3.2.2. V201301091616-... org.eclipse.jpt.jpa.feature.fea
t> ^ Data Tools Platform Connectivity 1.100.3.v20131127_00... org.eclipse.datatools.connect
i> &= Data Tools Platform Enablement 1.100.2. v20131127_00... org.eclipse.datatools.enabler
u Data Tools Platform Enablement for Apache Derby 1.100.3. v20131127_00... org.eclipse.datatools.enabler
t> ^ Data Tools Platform Enablement for IBM 1.100.10.v20131127_0... org.eclipse.datatools.enabler
i> ijì Data Tools Platform Enablement for JDBC 1.100.2.v20131127_00... org.eclipse.datatools.enabler
f. in the IBM Integration Toolkit Installation Details window, click the Configuration tab.
The Configuration tab contains the details about the installed configuration of the
Integration Toolkit environment. This page is a summary of the other tabs on the
Installation Details page.
Student Exercises

Installed Software j Installation History | Features ) Plug-ins Configuration j trtrtr Date: Thursday, October 1, 2 015 at 9:31:52 AH
Pacific Daylicfl ■fr** platform Details:

*** System properties:
CommonPath=C : \ Program F i les\ IBM\ IIB\ 10.0.0.0\ commons c lasses'-,
[Paths]=
applicat ionXHI=org.ec1ipse.ui.workbench/LegacyIDE.e4xmi
awt. too lkit=sun. awt. windows . UToolkit
com . ikim. cpu. endian= 1 itt le
com.ikim.j c1.checkClassPath=
com . ikim. ot i . configurât ion=scar
com . ikim. ot i . jcl .build=2 01412 15_2 2 73 95
com. ikim. ot i . shared. enakiled=f alse
com. ikim. ot i . vm .bootstrap . library. path=C : \ Program F i les\ IEH's I IB's 1C com . ikim. ot i .
vm. 1 ikir ar y. ver s ion=2 7 com . ikim. packed .vers ion=2
com. ikim. system. agent. path=C : \ Program Files\ IBM'S IIB\ 10.0.0.0\ comme com . ikim.
util .extralikis. proper t ies= com. ikim. vm.k»itmode= 64 com. ikim. zero . version=2
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildld=4.2.2.H20140918-1444
eclipse.commands3-os
Win32
-ws
Win32
-arch
x86_64
-showsplash m III
■ i i ________________________________________________ JLT I
(^) View Error Log Copy to Clipboard Close
Before you update any components in the Integration Toolkit, you should use the Copy to
Clipboard action, and then paste the clipboard contents into a file. Save the file for reference
in case you need to determine which components are installed at a specific point in time.
_ g. Click Close to close the configuration details.
_ h. Click OK to close the About IBM Integration Toolkit window.
_ i. Leave the IBM Integration Toolkit open (minimize it if you want); you use it later in this
exercise.
2. Get the software version information for the IBM Integration Bus.
_ a. Start an IBM Integration Bus Console session by clicking All Programs > IBM
Integration Bus 10.0.0.0 > IBM Integration Console 10.0.0.0 from the Windows Start
menu. As an option, you can double-click the IBM Integration Console shortcut icon on the
desktop.
Student Exercises
Important
When IBM Integration Bus is installed on Windows, a special command console is also
installed from which you run Integration Bus commands. It is a Windows command shell, but it sets
some environment variables when it is started.
Be sure to use an Integration Bus command console session when you are directed to do so in the
exercise instructions. If you attempt to use a Windows command prompt session, the commands you
enter might fail because the appropriate environment variables are not set.
b. Use the iib command to report the details of an IBM Integration Bus component.
In the IBM Integration Console, enter the command:
iib version
The response message contains the version, product, build levels and
build number.
Q IBM Integration Console 10.0.0.0
_AWWWWW__AWWWWW__AWWWWWW ______________ AW ___ A

WWW ___________________________________
V///AW/// V///AW///__XAW////////AW AWWW____ AW////AW__
_VW\_______VW\ ____ VW\ _____ \AW __ \/////W\_/W\ _ \//W\_
__\AW______VWN ____ VWWWWWWW __________ \AW_\AW __ \AW_
__ \/W\ ______ \/\W _ XAW////////AW _____ \AW_\AW _____ \AW_
__ VW\ _______ \/W\ ___ \/W\ ____ \/W\ ___ \/W\_\/W\ ___ \AW_
__ \AW _______ \/W\ ___ \AW _____ \AW ______ \AW_\//W\ _ AW_
_/WWW\WW„AWWWWW.VWWWWWWV _______________ \/\W \///WWW\/_
_\///////////__\///////////__\///////////// ___ V//
______________________________________ \///////__
I Enter an Integration Bus command e.g.

IIB toolkit, IIB help
C:\Progran Files\IBM\IIB\10.0.0.0>iib uersion
Installation: C:\Program
Uersion: Files\IBM\IIB\10.G.0.0' '10.0.0.0'
Product : IBM Integration Bus'
Build Number: -735’
IB Leuel: 'ibO00-L150317.735_P'
Seruer leuel: 'S0O0-L15031G.10572'
Toolkit leuel '20150313-1900'
The Version and Level fields identify the fix pack that is applied to IBM Integration Bus.
This information is useful when working with IBM Support.
in the example, the version is 10.0.0.0, which indicates that no fix pack is applied. For
example, FixPack 1 would show as version 10.0.0.1.
c. Minimize the IBM Integration Console window; you use it later in this exercise.

podrá reproducir o
Student Exercises
Part 2: Verify user authorizations

In this part of the exercise, you verify that the user ID that is used in the lab exercises has
administrative privileges.
1. To administer the integration node components and resources, the integration node service ID
must be a member of the mqbrkrs security group.
In this step, Management
I£9Computer you verify that the mqbrkrs security group exists on your system and that your
account (iibadmin)
File Action View Helpis a member. If the mqbrkrs group cannot be found, you create it and add
B i x a i i □ H
your account as a member of that group.
Computer Management (Local) B
Description
From the Windows Start menu, click All Programs > Administrative Tools > Computer
a. System Tools E0 © Task Scheduler S jk Administrators Backup Administrators have complete and u..,
Management.
^ Event Viewer Shared Folders Local Operators * Certificate Service Backup Operators can override secu..
Users and Groups □ Users Groups DCO... ¿^Cryptographic Members of this group are allowed t.
Expand
PerformanceSystem Tools
Device Manager □ ¿2* > Local Users and Groups.
Operators ¿8 Distributed COM Members are authorized to perform ..
b. Storage
Click Groups to display
Disk Management SI theUsers Event Log Readers Jfc
users and groups. Members are allowed to launch, acti...
Guests II5JU5R5 Members of this group can read eve..
c. Services and Applications
^'NetworkConfiguration Guests have the same access as me.,
Ei Performance Log Users Built-in group used by Internet Infer..
¿§jj*Performance Monitor U... Members in this group can have som..
Power Users If Print Members of this group may schedule,,
Operators djk Remote Desktop Members of this group can access p...
Users |f Replicator $£ Users Power Users are included for backw...
%DB2ADMN5 ¿fe’DB2USER5 Members can administer domain prin..
Members in this group are granted t...
Supports file replication in a domain
Users are prevented from making ac..
This group and local administrators ...
This group will have read and execut..
If you are using the VMware image for this course, the mqbrkrs group is already
created. You do not need to create it.
IBM Integration Bus Group
mqm IBM WebSphere MQ Administration ,..

d.
Double-click the mqbrkrs group to display the members of the group.
e.
Verify that iibadmin (your user ID for this course) is listed as a member of the group.
^ V Note
If you are not using the pre-built image for this course, and the mqbrkrs group does not exist, you
can create it and then add your user ID to the Members list.
1. Right-click Users and click New > Group from the menu.
2. Type mqbrkrs in the Group name field.
Course materials may not be reproduced In whole or in part
podrá reproducir o
Student Exercises
3. Click OK.
4. Open the new group and then add your account ID as a member of the mqbrkrs group.
v _______________________________________________________________________________ J
_ f. Click Cancel to close the Properties window for the mqbrkrs group.
_ 2. Some Integration Bus applications require IBM MQ. In these applications, the administrator
must also be a member of the IBM MQ administration group mqm (this group is created
automatically when IBM MQ is installed).
Verify that your user ID iibadmin is a member of mqm group.
If necessary, add iibadmin to the mqm group.
Changes to a user's group membership
Add..
IijHSComputer Management
I File Action View Help
Apply Help
I B I X S È > I H
y
1 Description
Computer Management (Local) □
System Tools EE Task Scheduler 0 |^j Administrators Administrators have complete and u...
Event Viewer 0 Shared Folders B * Backup Operators Backup Operators can override secu,,,
Local Users and Groups ilfj Users r°l
Certificate Servi
Groups 0 (0) Performance Cryptographic C
mqm Properties
Device Manager
Distributed COM General j
Storage
Event Log Readi
IgJ1 Disk Management 0
Guests IISJUSRS
Services and Applications
Network Configi
&
Performance Lot
Performance Mo
Description: IBM WebSphere MQ Administration Group
Power Users Print
Operators Remote
Desktop Replicator Members:
Users iibadmin
DB2ADMNS & MUSR_MQADMIN
DB2USERS
mqbrkrs mqm
Security _Test
are not effective until the next time the user logs on.
_ 3. Close the Computer Management window.
Part 3: Create an integration node and integration servers

In this part of the exercise, you use the IBM Integration Bus command interface to create an integration
node. This integration node does not have an IBM MQ queue manager that is specified on the
integration node.

Student Exercises
podrá reproducir o
Note
For the following steps, you use an IBM Integration Console. Remember that command
arguments are case-sensitive.
1. Start an IBM Integration Console session with Windows “Administrator” privileges.

Click Start > All Programs > IBM Integration Bus 10.0.0.0 and then right-click IBM
Integration Console 10.0.0.0, and then click Run as administrator.
Optionally, you can right-click the IBM Integration Console icon on the desktop and then click
Run as administrator.
Click Yes to run the IBM Integration Console with “Administrator” privileges.
2. Type the following command to create an integration node that is named IIBNODE_NOQM:
mqsicreatebroker IIBNODE_NOQM
3. Start the new integration node.

In the IBM Integration Console, type:
mqsistart IIBNODE_NOQM
You should receive a response similar to the following example.

BIP8071II: Successful command initiation, check the system log to ensure that the
component started without problems and that it continues to run without problems.
4. On Windows, a Windows service is created automatically when you create an integration node.
Verify that a Windows service is created for the new integration node.
___a. In
IBM Integration Bus Component Name -*■ Description 1 Status Startu
IIBNODE_NOQM
•ZJ Diagnostic System Host The Diagnostic System Host is u.., Manu;
Stop the service ‘.Disk Defragmenter Provides Disk Defragmentation ... Manu;
A \à
Pause the service §5 Distributed Link Tracking Client Maintains links between NTFS fil.., Manu;
Restart the service
'„'¡Distributed Transaction Coordinator Coordinates transactions that s,., Started Autorr
'„■ ¡DNS Client The DNS Client service (dnscach.., Started Autorr
'„■ ¡DNS Server Enables DNS clients to resolve D.., Started Autorr
Windows,
'„'¡Encrypting File System (EFS) Provides the core file encryption.,. Manu;
click Start >
'„'¡Extensible Authentication Protocol The Extensible Authentication P.., Manu;
All Programs
'„■ ¡Function Discovery Provider Host The FDPHOST service hosts the ... Manu;
>
'„'¡Function Discovery Resource Publication Publishes this computer and res,., Manu;
Administrativ
'„'¡Group Policy Client The service is responsible for ap.., Started Autorr
e Tools >
'„'¡Health Key and Certificate Management Provides X.5Û9 certificate and k.., Manu;
Services.
'„'¡Human Interface Device Access Enables generic input access to ,,. Manu;
b. Scroll down . ¡IBM Integration Bus 10.0,0.0 Server MasterService IBM Integration Bus 10,0.0,0 Se... Started Autorr
Manu
and verify that ¿*iIBM Integration Bus Component IIBMODE_NOQM IBM Integration Bus Node "IIBN,.. Started a
. f'jl.TRM Tr.l-onraHnn Rue Cnmnnnanf TF^TMi''ir'lF TRM Tnhanrahinn Ri ic MnHa ÇhaHharl Mani i;
¡iharlmin "TFÇT
you see a
service for
IBM
Integration
Bus Component l!BNODE_NOQM.
H B I ► ■ 00 B>
Services [Local)
Description:
IBM Integration Bus Mode
"IIBMODE_MOQM"
podrá reproducir o
Student Exercises
r / Note ^
You might also see a service for the IBM Integration Bus Component TESTNODEJibadmin. This is the
service for the development integration node that is created automatically the first time that the IBM
Integration Toolkit starts.
V ______________________________________________________________________________ y
_ c. Close the Services window.

_ 5. Check that the integration node environment is set up correctly.
mqsicvp IIBNODE_NOQM

BIP8873I: Starting the component verification for component 'IIBNODE_NOQM'. BIP8876I:
Starting the environment verification for component 'IIBNODE_NOQM'.
BIP8894I: Verification passed for 'Registry'.
BIP8894I: Verification passed for 'MQSI_REGISTRY'.
BIP8894I: Verification passed for 'Java Version - 1.7.0 IBM Windows AMD 64 build
pwa6470_27sr2fpl0-20141218_02(SR2 FP10)
BIP8894I: Verification passed for 'MQSI_FILEPATH'.
BIP8878I: The environment verification for component 'IIBNODE_NOQM' has finished
successfully.
BIP8882I: Starting the WebSphere MQ verification for component 'IIBNODE_NOQM'.
BIP8874I: The component verification for 'IIBNODE_NOQM' has finished successfully.
_ 6. Verify that new integration is created in “advanced” mode.
mqsimode IIBNODE_NOQM

BIP1802I: Integration node 'IIBNODE_NOQM' is in 'advanced' mode.
BIP1831I: Integration node 'IIBNODE_NOQM' has mode extensions ''.
BIP8071I: Successful command completion.

podrá reproducir o
Student Exercises
7. Display the node properties for the new integration node.

mqsireportbroker IIBNODE_NOQM

BIP8927I: Integration node name 'IIBNODE_NOQM'
Last mqsistart path = 'C:\Program Files\IBM\IIB\10.0.0.OXserver' mqsiprofile
install path = 'C:\Program Files\IBM\IIB\10.0.0.0\server' Work path =
'C:\ProgramData\IBM\MQSI'
Integration node UUID = ''
Process id = '3004'
Queue Manager = ''
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds Internal configuration timeout =
'60' seconds Statistics major interval = '60' minutes Operation mode =
'advanced'
Fixpack capability level = '' (effective level 'unrestricted') Integration
node registry format = 'vlO.O'
Administration security = 'inactive'
Multi-instance integration node = 'false'
Shared Work Path = 'none'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = 'disabled'
Cache manager port range = '2820-2039'
Integration registry hostname = ''
Default integration node CCSID = '5348'
podrá reproducir o
Student Exercises
_ 8. Report integration node service details.

mqsiservice IIENODE_NOQM

BIPmsgs en_US
Console OEM CP=437, ICU CCSID=5348
Default codepage=ibm-5348 P100-1997, in ascii=ibm-5348 P100-1997 JAVA
console codepage name=cp437
Install Path = C:\Program Files\IBM\IIB\10.0.0.OXserver

Shared Work Path = NOT_HA_ENABLED_BROKER
Local Work Path = C:\PrograraData\IBM\MQSI
process id = 888
service userid = LocalSystem
general default userid = LocalSystem
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = (effective level unrestricted)

podrá reproducir o
Student Exercises
9. Get web interface port number for the integration node.

_ a. In the IBM Integration Console, type:
mqsireportproperties IIBNODE_NOQM -b webadmin -o HTTPConnector -a
You should receive a response that is similar to the following example.

HTTPConnector
uuid='HTTPConnector'
address=''
port='4415'
maxPostSize=''
acceptCount=''
compressableMimeTypes='text/html,text/css,application/javascript, image/gi f,
image/png,application/json' compression='on' connectionLinger=''
connectionTimeout='' maxHttpHeaderSize='' maxKeepAliveRequests='' maxThreads=''
minSpareThreads=' ' noCompressionUserAgents='' restrictedUserAgents=''
socketBuffer='' tcpNoDelay='' enableLookups='false' serverName=''
_ b. Record the value for HTTPConnector port property. You use this value in the next step
to start the IBM Integration web interface for this integration node.
Information
IBM Integration Bus assigns a web user administration port number dynamically. When
the first integration node is started, it is assigned the default port of 4414. For subsequent integration
nodes, the port number increments and the node is assigned the next port number in sequence.
J
10. Create an integration server by using a command.

mqsicreateexecutiongroup IIBNODE_NOQM -e serverl

BIP1124I: Creating integration server 'serverl7 on integration node 'IIBNODE_NOQM7
BIP1117I: Integration server was created successfully.
The integration node has initialized the integration server.
Student Exercises
11. Confirm the components on the integration node by using the mqsilist command. Type:
mqsilist IIBNODE_NOQM

BIP8071I: Integration server 'serverl' on integration node 'IIBNODE NOQM' is running.
12. Start the IBM Integration web interface for the new integration node.
__ a. Open a web browser. Your course image includes both Internet Explorer and Mozilla
Fi refox.
__ b. For the URL, type:
http: //localhost: port
Replace port in this command with the FITTPConnector port value that the
mqsireportporties command returns.
For example, if the port number that the mqsireportproperties command returns in
Step 9 is 4417, type http: //localhost: 4417.
c. After a brief pause, the IBM Integration user interface for the IIBNODE_NOQM integration node starts.
IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. No se podrá reproducir o
© Copyright IBM Corp. 2015

Course materials may not be reproduced In whole or In part
Student Exercises
13. Display the current integration servers that are defined on the integration node.
Click the down arrow that is to the left of the Servers folder.
You should see one integration server that is named server!. You should also see that icon
next to the integration server name contains an up pointing green arrow, which indicates that
the integration server is running.
^ II BNODE_MOQM
serverl
2n Operational Policy
Security
Evi
Monitoring
14. Create an integration server that is named server2 on the integration node by using the IBM
Integration web interface.
_ a. In the IBM Integration web interface, click the down arrow to the right of the Servers
folder and then click Create.
J IIBNODEJNOQM
server
► ll2] Operation
► QE Data
__ b. In the New Integration Server window, type server2 and then click OK.
_ c. After a brief pause, you should see a message that the integration server was created.
You should also see that the Servers folder now contains two integration servers:
serverl and server2.
15. Start the IBM Knowledge Center for IBM Integration Bus V10 from the IBM Integration web
user interface.
_ a. Click the Help icon in the IBM Integration web interface.
|4-3‘llBNODE_NOqM - IBM Integration - Internet Explorer
http: //localhost : IIBNODE_NOQM - IBM Integ... X | Eg IBM Knowledge Center

4415/#broke
IBM Integration Welcome, Default
Filter Options.
IIBNODE_NOQM - Integration Node
Exercise 1. Integration node setup and customization

Student Exercises
_ b. The IBM Knowledge Center web page opens in a new tab in the web browser.
^ IBM Knowledge Center - Internet Explorer
IDlxl
? JH http : //www-01 ibm.com/supp P **
— IIBNODE_NOQM - IBM Integration S3 IBM Knowledge Center LJ firsts
IBM Knowledge Center Sign In English - 0
Search Save Search ▼
Search Filters: IBM Integration Bus 10.0.0 x (y Auto-select | Clear All Add Products..
ß Share ▼ Add to Collection ▼ ¿7 0
IBM Integration Bus 10.0.0 > Welcome

IsT] Table of Contents
* Back to all products
* IBM Integration Bus IBM Integration Bus Version lo.o

IBM Integration Bus 10.0.0
Welcome
► Start here Welcome to the product documentation for IBM® Integration Bus Version 10.0,
where you can find detailed instructions about how to complete the tasks to
► Product overview establish and maintain your integration environment This information also
describes concepts to help you understand the product, and the ways in which
► Scenarios you can use it to solve your business problems.
► Planning your IBM Integration Bus solution
► Migrating
► Installing and uninstalling
Some of the links in this documentation work only if you are accessing this documentation from the IBM
► Configuring integration nodes for development < Integration Toolkit. The links that work only in the IBM Integration Toolkit are displayed with toolkit icon
► Configuring integration nodes for test and produ v* a.
When the documentation is used in a user interface or local Knowledge Center, some links work only if
you have a connection to the internet, and these links are displayed with this icon ^.
ji My Collections
Search Results
(^) Getting started a Common tasks
What's new?
Contact Privacy Terms of use Accessibility Feedback
_ c. Take some time to investigate the sections in the IBM Knowledge Center for IBM
Integration Bus.
For example, you can type mqsicreatebroker in the Search area to find information
about the mqsicreatebroker command.
Exercise clean-up
_ 1. Close the web browser window.
_ 2. Close the IBM Integration Console window.
End of exercise

Student Exercises
Exercise review and wrap-up

In the first part of this exercise, you verified the maintenance (fix pack) levels of the IBM Integration
Bus software.
In this second part of the exercise, you verified that the user ID that is used in the lab exercises has
administrative privileges to create and administer IBM Integration Bus and IBM MQ resources.
In the third part of this exercise, you used the IBM Integration command interface to create an
integration node and report integration node properties. You then used the IBM Integration command
interface and the IBM Integration web interface to create integration servers on the new integration
node. You also used the IBM Integration web interface to access the IBM Knowledge Center for IBM
Integration Bus V10.
Having completed this exercise, you should be able to:
Student Exercises

Student Exercises
Exercise 2. Connecting to IBM MQ

In this exercise, you create an IBM MQ queue manager and an IBM Integration
Bus integration node that uses the queue manager as a default queue
manager. You create a second integration node with the same default queue
manager as the first integration node. Finally, you create the IBM Integration
Bus system queues on the queue manager and an MQEndpoint policy.

• Create an integration node that uses a default IBM MQ queue manager
• Share a default IBM MQ queue manager with multiple integration nodes
• Create the IBM Integration Bus system queues on a queue manager
• Create an MQEndpoint policy
Introduction
With the release of IBM Integration Bus V10, an IBM MQ queue manager is no
longer a prerequisite for integration nodes.
You can develop and deploy many message flow applications with Integration
Bus independently of IBM MQ; however, some Integration Bus capabilities still
require access to an IBM MQ queue manager. For example, the MQInput and
MQOutput nodes in a message flow require access to an IBM MQ queue
manager. Other Integration Bus capabilities require that a queue manager that
has special SYSTEM.BROKER queues is specified on the integration node.
For example, event driven message processing nodes such as the Collector
node and the Aggregation node require that a queue manager is specified on
the integration node.
Information
The IBM MQ message processing nodes do not require a queue manager to be specified on the
integration node unless you want to use a default queue manager for the local IBM MQ connection.
In IBM Integration Bus V10, multiple integration nodes can share a queue
manager. Flows that are deployed to integration servers in different
© Copyright IBM Corp. 2015 Exercise 2. Connecting to IBM MQ 2-1

Student Exercises
integration nodes that share a queue manager can put and get from different
queues or the same queues.
Using a shared queue manager can provide high availability for an
application. If one of the flows, integration server, or integration node fails, the
other flow on the other integration node can assume the workload. In the
example in the figure, the integration nodes IIBNODE_WITHQM and
IIBNODE_WITHQM2 share the IBM MQ queue manager IIBQM.
In the first part of this exercise, you create a queue manager that is named
IIBQM.
In the second part of this exercise, you create two integration nodes
(IIBNODE_WITHQM and IIBNODE_WITHQM2). Each integration node
specifies the same queue manager (IIBQM) as the default queue manager.
You also create an integration server on each integration node.
In the third part of this exercise, you add the BROKER.SYSTEM queues to
the queue manager.
Integration Bus administrators can use an MQEndpoint policy to control the
values of IBM MQ node connection properties at run time. The MQEndpoint
policy overrides any equivalent properties that are specified for the MQ
Connection properties in the message flow definition.
In the fourth part of the exercise, you create an MQEndpoint policy on the
development integration node TESTNODEJibadmin by using the IBM
Integration web interface. The TESTNODEJibadmin integration node is the
development integration node that is created automatically for developers the
first time that the IBM Integration Toolkit starts.
In this part of the exercise, you also export an MQEndpoint policy and then
import it into another integration node (IIBNODE_NOQM).

Student Exercises
Requirements
• A lab environment with the IBM Integration Bus V10 Bus and IBM MQ V8
• A user iibadmin who is a member of the mqbrkrs and mqm groups
• The IIBNODE_NOQM Integration node and integration servers that are
created in Exercise 1, Part 3. It also requires that the integration node
IIBNODE_NOQM is running.

Student Exercises
Part 1: Use IBM MQ Explorer to create the queue manager
In this part of the exercise, you use IBM MQ Explorer to create a queue manager that is named IIBQM
and a dead-letter queue that is named DLQ.
_ 1. Start IBM MQ Explorer.
From the Windows Start menu, click All Programs > IBM WebSphere MQ > WebSphere MQ
(Installation 1) or double-click the WebSphere MQ Explorer (Installationl) icon on the
desktop.
_ 2. Create a queue manager that is named IIBQM with a dead-letter queue that is named DLQ.
_ a. In the MQ Explorer Navigator view, right-click Queue Managers and then click New >
Queue Manager.
WebSphere MQ Explorer (Installationl)
File Edit Window Help
fe. MQ Explorer - Navigator £3 4^ - □ Hi MQ Explorer - Co

E-@ IBM WebSphere MQ
Queue Ma
Queue Mana
&
Show/Hide Queue Managers,.. Add
& Queue Mar &
Remote Queue Manager,,. Filter: Standard h
JM5 Adminl &
Managed F È? Queue Manager.
Service Del Transfer Queue Managers.,.
Tests ►
Sets ►
b. For the Queue Manager name, type: IIBQM

c. For the Dead-letter queue, type: DLQ
d. Click Finish.

Student Exercises
After a brief pause, the queue manager is created and started. A listener is also started
on the default TCP port of 1414.
The queue manager is shown under the Queue Managers folder in the MQ Explorer -
Navigator view.
3. Create a queue that is named DLQ for the dead-letter queue.
_ a. In the MQ Explorer - Navigator view, expand the IIBQM queue manager folder.
_ b. Right-click Queues and then click New > Local Queue.
BM WebSphere MQ Explorer (Installation!)

'tSL MQ Explorer - Navigator £3 ^ :-] □ ft MQ Exp I orer - '

B"@ IBM WebSphere MQ
B" tzh Queue Managers Ë Queues
5¡ IIBQM
Filter: Standarc
& TopU & Local Queue.,,
Subs. Alias Queue...
Status,,,
Model Queue,,,
0 & Char Tests Remote Queue Definition.
►
& Liste Object Authorities ►
& ServTces
c. For the queue Name, type: DLQ

d. Click Finish.
e. Click OK in the Confirmation window.
f. Verify that the queue DLQ is listed in the Queues content view.
^>IBM WebSphere MQ Explorer (Installation!)
File Edit Window Help ¡§7. MQ Explorer - Navigator S3
“□
H) MQ Explorer - Content « I! ™ I & ~
iQueues
<£> B ~
□ Q} IBM WebSphere MQ Queue Managers B 53
IIBQM Filter: Standard for Queues
•£> Queues Topics
Subscriptions 0 Channels ' Queue name Queue type | Open input count | Open output count | Current queue depth | Put messages Get messages
Listeners Services y DLQ Local 0 0 0 Allowed Allowed
_ 4. Minimize IBM MQ
Explorer.
Part 2: Create the integration nodes and integration servers

In this part of the exercise, you use the IBM Integration Bus command interface to create two
integration nodes that use the same queue manager as the default queue manager. You also create an
integration server on each integration node.
_ 1. Create an integration node that is named IIBNODE_WITHQM.
_ a. Start an IBM Integration Console session with Windows “Administrator” privileges.

Student Exercises
Optionally, you can right-click the IBM Integration Console icon on the desktop and
then click Run as administrator.
_ b. Enter the following command to create an integration node that is named
IIBNODE_WITHQM that specifies the queue manager IIBQM:
mqsicreatebroker IIBNODE_WITHQM -q IIBQM
_ c. Start the new integration node.

mqsistart IIBNODE_WITHQM

_ 2. Check that the integration node environment is set up correctly for l!BNODE_WITHQM.
Verify that the integration node properties for the integration node indicate that queue manager
IIBQM is specified on the integration node.
mqsicvp IIBNODE_WITHQM

BIP8873I: Starting the component verification for component 'IIBNODE_WITHQM'.
BIP8876I: Starting the environment verification for component 'IIBNODE_WITHQM'.
pwa6470_27sr2fpl0-20141218_02(SR2 FP10)
BIP8878I: The environment verification for component 'IIBNODE_WITHQM' has finished
successfully.
BIP8841I: The WebSphere MQ verification for component 'IIBNODE_WITHQM' had finished
successfully.
BIP8874I: The component verification for 'IIBNODE_WITHQM' has finished successfully.
_ 3. Create an integration server on IIBNODE_WITHQM that is named serverl.

Student Exercises

mqsicreateexecutiongroup IIBNODE_WITHQM -e server!

BIP1124I: Creating integration server 'serverl' on integration node '
IIBNODE_WITHQM'
4. Get the IBM Integration web interface port number for the IINODE_WITHQM integration node.
__ a. In the IBM Integration Console, type the following command to get the HTTP Connection
port number:
mqsireportproperties IIENODE_WITHQM -b webadmin -o HTTPConnector -a
__ b. Record the value for HTTPConnector port. You use this value in the next step to start
the IBM Integration web interface for this integration node.
Information
IBM Integration Bus assigns a web user administration port number dynamically. When the first
integration node is started, it is assigned the default port of 4414. For subsequent integration nodes,
the port number increments and the node is assigned the next port number in sequence.
J
__ a. Open a web browser.
http://localhost: port
Replace port in this command with the HTTPConnector port value that the
For example, if the port number that the mqsireportproperties command returns in Step 4
is 4416, type http: //localhost: 4416.
__ c. After a brief pause, the IBM Integration user interface for the IIBNODE_NOQM
integration node starts.
6. Following the same procedure that you used for creating the integration node
IIBNODE_WITHQM and the integration server serverl, create another integration node that is
named IIBNODE_WITHQM2 and an integration server that is named server2.
Be sure to specify the same queue manager, IIBQM, as the queue manager on the integration
node.

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunatgob.pe>. La impresión está destinada únicamente para uso personal y privado. No se
podrá reproducir o
Student Exercises
Part 3: Create the SYSTEM.BROKER queues and topics on the integration

node queue manager
Some Integration Bus capabilities and message processing nodes require access to an IBM MQ queue
manager and SYSTEM.BROKER queues and topics on the integration node queue manager.
In this part of the exercise, you use an Integration Bus sample command file to add the
SYSTEM.BROKER queues and topics to the IIBQM queue manager that the IINODE_WITHQM and
IIBNODE_WITHQM2 integration nodes use.
_ 1. In IBM MQ Explorer, check the SYSTEM queues on the queue manager IIBQM.
__ a. In the IBM MQ Explorer Queues content view, click the Show System Objects icon to
:
display the SYSTEM queues and topics.
IBM WebSphere MQ Explorer (Installation!)
__ b. Locate the current set of SYSTEM.BROKER queues.

IBM MQ created these queues. They are generic queues that are automatically set up for
all brokers and queue managers on a network. These queues are not specific to Integration
Bus.
MQ Explorer - Content ZÌ | ±j|| | t-jsf | Q
□
¡Queues
Filter: Standard for Queues
Queue name Queue type Open input count Open output count Current queue depth Put mes |
Local 1 1 99 Allowed
y SYSTEM.BROKER.ADMIN,STREAM Local 1 1 0 Allowed
|0j SYSTEM.BROKER.CONTROL,QUEUE Local 30 0 Allowed

y SYSTEM.BROKER.DEFAULT,STREAM Local 10 o Allowed
y SYSTEM. BROKER. INTER .BROKER. COMMUNICATIONS Local 10 0 Allowed
y SYSTEM.CFIANNEL,INITQ Local 10 0 Allowed
y SYSTEM.CFIANNEL,5YNCQ Local 00 0 Allowed
y SYSTEM.CHLAUTH.DATA.QUEUE Local 00 3 Allowed
2. In the IBM Integration Console, type the following command to go to the Integration Bus sample
directory for IBM MQ. This directory contains the batch file that creates the SYSTEM.BROKER
queues.
cd server\sarnple\wmq

Student Exercises
3. In the IBM Integration Console, type the following command to run the command file on the IIBQM
queue manager.
iib_createqueues.ctnd IIBQM
You should see messages that indicate that the SYSTEM.BROKER queues and topics are
created. You should also see messages that indicate that security is set on the queues by using
the IBM MQ setmqaut command.
4. In IBM MQ Explorer, check the SYSTEM queues on the queue manager IIBQM and verify that the
queue manager
now contains the
Integration Bus
SYSTEM.BROKER
queues.
£[j MQ Explorer - Content £3
iQueues
Queue name Queue type Open input count Open output count | Current queue depth |
U SYSTEM,BROKER. ADAPTER,PROCESSED Local 0 00
lai SYSTEM,BROKER.ADMIN,STREAM Local 1 1 0
lai SYSTEM.BROKER. AGGR.CONTROL Local 0 0 0
U SYSTEM,BROKER.AGGR.REPLY Local 0 0 0
lai SYSTEM,BROKER.AGGR.REQUEST Local 0 0 0
lai SYSTEM,BROKER.AGGR.TIMEOUT Local 0 00
lai SYSTEM,BROKER.AGGR.UNKNOWN Local 0 00
lai SYSTEM.BROKER.AUTH Local 0 00
SYSTEM,BROKER.CD,MODEL Model
lai SYSTEM,BROKER.CONTROL,QUEUE Local 3 00
lai SYSTEM,BROKER.DC,AUTH Local 0 0 0
lai SYSTEM,BROKER.DC,BACKOUT Local 0 0 0
lai SYSTEM.BROKER.DC.RECORD Local 0 0 0
lai SYSTEM,BROKER.DEF AULT,STREAM Local 1 0 0
lai SYSTEM,BROKER.EDA,COLLECTIONS Local 0 ID 0
lai SYSTEM,BROKER.EDA,EVENTS Local 0 00
SYSTEM,BROKER.FTE,MODEL Model
lai SYSTEM. BROKER. INTER .BROKER. COMMUNICATIONS Local 1 00
ÌI SYSTEM,BROKER.MODEL.QUEUE Model
lai SYSTEM,BROKER.SEQ,EXPIRY Local 0 00
lai SYSTEM,BROKER.SEQ,GROUP Local 0 0 0
|al SYSTEM,BROKER.SEQ,NUMBER Local 0 0 0
lai SYSTEM.BROKER.TIMEOUT.QUEUE Local 0 0 0
lai SYSTEM,BROKER.WS,ACK Local 0 0 0
lai SYSTEM,BROKER.WS,INPUT Local 0 ID 0
lai SYSTEM.BROKER.WS.REPLY Local 0 00
5. The command script also creates the topic SYSTEM.BROKER.MB.TOPIC, which maps to the topic
string $SYS/Broker. This topic is required for the Integration Bus record and replay, and statistics
components.

Student Exercises
Click Topics under the IIBQM queue manager in the MQ Explorer - Navigator. Verify that
the SYSTEM.BROKER.MB.TOPIC is created on the queue manager.
% IBM WebSphere MQ Explorer (Installation!)
File Edit Window Help jfe! MQ Explorer - Navigator £3 1=1 B

£0E!^
g MQ Explorer - Content £3
B© IBM WebSphere MQ
□-& Queue Managers - 0
Topic
IIBQM
s
;. & Queues
Filter: Standard for Topics
i i ..... & [tigjitj
!. Subscriptions I Topic type | Topic string
Topic name
i S Channels ©SYSTEM.BASE,TOPIC Local
j . & Listeners ©SYSTEM.BROKER.ADMIN,STREA Local SYSTEM,BROKER, ADMIN
i ..Services .STREAM
M Local
I & Process Definitions ©SYSTEM.BROKER.DEFAULT.STR
©SYSTEM.BROKER.MB,TOPIC
EAM Local $5Y5/Broker
_ 6. Minimize IBM MQ Explorer.
Jbïb I tm.UtrAULI . IUP1L
Part 4: Create an MQEndpoint policy

Integration Bus administrators can use an MQEndpoint policy to control the values of IBM MQ node
connection properties at run time. The MQEndpoint policy overrides any equivalent properties that are
specified for the MQ Connection properties in the message flow definition.
In this part of the exercise, you create an MQEndpoint policy on the development integration node
TESTNODEJibadmin by using the IBM integration web interface. The TESTNODEJibadmin
integration node is the development integration node that is created automatically for developers the
In this part of the exercise, you also export an MQEndpoint policy and then import it into another
integration node (IIBNODE_NOQM).
_ 1. Open a web browser and start the IBM Integration web interface for the
TESTNODEJibadmin integration node.
_ a. Ensure that the integration node TESTNODEJibadmin is running. Type:
mqsilist
If the results of this command show that TESTNODEJibadmin is not running, start it by
using the mqsistart command.
_ b. Get the HTTP Connector port value for the web interface by typing the following
command in the IBM Integration Console.
mqsireportprqperties TESTNODE_iibadmin -b webadmin -o HTTPConnector -a
_ c. Record the value for port property.

_ d. In the web browser, type the following URL to start the IBM Integration web interface for
TESTNODEJibadmin
http://localhost :port

Student Exercises
Filter Options...
TESTNODEJibadmin - Integration Node

- $ TESTNODEJibadmin ▼ i S' Qi Overview Statistics
Servers
► Ug] Operational Policy
► g Data
► ^ Security ▼ Quick View
Node Name
► 0 Monitoring TESTNOD
EJibadmin
Version 10DDO
Admin Security ©Off
Run Mode running

Short Description
Long Description
2. In the IBM Integration web interface, expand Operational Policy.

3. Click the down arrow on the right side of MQEndpoint to display the menu and then click
Create.
I
I
n
:
i
- $ TESTNODEJibadmin ▼
► Servers ▼
- ill Operational Policy

► Configurable Services ▼
MQEndpoint i
► MQTTPublish MQEndpoint
► MQTTSubscrit Create
► (jfcip Workload Management ▼
4. Define the MQEndpoint policy for a local connection to the queue manager IIBQM.
_ a. For the Policy name, type: LocaiConnectToiiBgM
_ b. For the Connection, select Local queue manager.
__ c. For the Queue manager name, type: IIBQM
__ d. For the Queue manager host name, type: locaihost
_ e. For the Listener port number, type: 1414

_ f. For the Channel name, type: SYSTEM.DEF.SVRCQNN

Student Exercises
Operational Policy - MQEndpoint

Q Overview
]. Save As Revert
g. Click Save.
|j Use a policy to control the operational behavior of a message flow node at run time.... Oct 3,2015, 6:55:29 AM x
Policy name*
Loe alConnectTo
11BQM
Connection Queue manager
Local queue manager
name Queue manager host

IIBGM
name Listener port number

localhost
Channel name Security 1414
identity
SYSTEM.DEF.SVRCONN
Use SSL SSL peer name
SS-L cipher specification
h. After a brief pause, you should see the new MQ Endpoint policy under the MQEndpoint
policy folder in the IBM Integration web interface.
- £ TESTNODEJibadmin T
► Servers ▼
- §2 Operational Policy
- (£3 MQEndpoint
j7l Local Connection BQM

MQTTPublish ^
|ti> MQTTSubscribe ▼
5. Verify that the new policy is available to the developer in the Integration Toolkit.
__ a. Start the IBM Integration Toolkit if it is not already running.
__ b. In the Integration Toolkit, click the Integration Registries tab (in the same view as the
Integration Nodes tab).

Student
IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. Exercises
Integration Modes Integration Registries S3 >■

□ Întegration Registries
Integration Registry on IIBNODE_NOQM & Policies
17^7 Services
Integration Registry on IIBNODE_WITHQM
□£ Policies Jj Services
Integration Registry on IIBNODE_WITHQM2
Policies ¿j' Services
É& Integration Registry on TESTNODEJibadmin
Policies Services
àS
The Integration Registries tab contains an entry for each integration node to which the
Integration Toolkit can connect. By default, the Integration Toolkit can connect to any local
integration node.
C.
You created the MQEndpoint policy on TESTNODEJibadmin.
Right-click Integration Registry on TESTNODEJibadmin and then click Refresh to
update the Integration Registry view in the IBM Integration Toolkit.
Verify that the MQEndpoint policy that is named LocalConnectTollBQM is listed under the
d. Integration Registry on TESTNODEJibadmin folder.
Integration Nodes ¡ Integration Registries £3 t- Dat
E ¿eg Integration Registries

É Integration Registry on IIBNODE_NOQM Policies jj
Services
É <5 Integration Registry on IIBNODE_WITHQM
Policies Jj Services
- £ Integration Registry on IIBNODE_WITHQM2 (£7
Policies
□ <3 Integration Registry on TESTNODEJibadmin

..................................................................................... ............................. .......................
É -|Jÿ Policies
j i .... gj] MQEndpoint/LocalConnectToIIBQM
¿7 Services
r I# I Information
I
J
_L
The application developer can now reference the MQEndpoint policy in the message flow by specifying
the policy URL in the Policy URL field in the Policy properties on the IBM MQ message processing
nodes.
The format Of a policy URL is /apivl/policy/poi icy Type/policyName.

Student Exercises
For example, the policy URL for the MQEndpoint policy that you created in this exercise is:
/apivl/policy/MQEndpo int/LocalConnectTollBQM.
V ______________________________________________________________________________ V
_ 6. Export the MQEndpoint policy to the c: \iabfiies\Lab02-MQ directory.
__ a. In the IBM Integration Console, go to the C:\iabfiies\Lab02-MQ directory. Type:
cd C:\labfiles\Lab02-M2
__ b. Type the following command to create a policy file from the LocalConnectTollBQM
MQEndpoint policy that was created on TESTNODEJibadmin:
mqsireportpolicy TESTNODE_iibadmin -t MQEndpoint -1 LocalConnectToIIBQM
-f LocalConnectToIIBQM. xml
The command should create the file and display the current values of the MQEndpoint
policy.
__ c. Using Windows Explorer, verify that the LocalConnectToIIBQM.xml file was created in
the C:\iabfiies\Lab02-MQ directory.
_ 7. View the contents Of the LocalConnectToIIBQM.xml file.
You can double-click the file to view it in a web browser (shown in the screen capture) or open
Windows Notepad to view it as a text file.
<?xml version="1.0" encodtng="UTF-8" standalone="true"?>

- <policy type='MQEndpoint'>
- <policyProperties>
- <mqConnectionDetailsPolicy>
<connection>SERVER</connection>
<destinationQueueManagerName>IIBQM</destinationQueueManagerName>
<queueManagerHostname>localhost</queiieManagerHostnanne>
<listenerPortNLmber>14i4</listenerPort!\lumber>
<channelName>SYSTEM.DEF.SVRCONN</channeiName>
<useSSL>false</useSSL>
</mqConrectionDetailsPolicy>
</policyProperties>
</policy>
_ 8. Import the exported MQEndpoint policy definition to create an MQEndpoint Policy on

IIBNODE_NOQM.
mqsicreatepolicy IIBNODE_NOQM -t MQEndpoint -1 LocalConnectTollBQM -f
LocalConnectToIIBQM.xml
After a brief pause, you should receive a response that the command completed successfully.
_ 9. Verify that the MQEndpoint policy was imported successfully by using the
mqsireportpolicy command.

Student Exercises
In the IBM Integration Console, type: mqsireportpolicy IIBNODE_NOQM -t

MQEndpoint -r You should receive the following response.
BIP1895I: Policy type 'MQEndpoint' Policy name 'LocalConnectToIIBQM' Policy URI
'/apivl/policy/MQEndpoint/LocalConnectToIIBQM' Policy content '<?xml version="l. 0"
encodings"UTF-8" standalone="yes"?Xpolicy type= "MQEndpoint"> <policyProperties>
<mqConnectionDetailsPolicy>
<queueManagerHostname>localhost</queueManagerHostname>
<listenerPortNumber>1414</listenerPortNumber>
<channelName>SYSTEM.DEF.SVRCONN</channelName>
<useSSL>false</useSSL> </mqConnectionDetailsPolicy>
</policyProperties></policy>'
rp/
r Note
You can also verify that the MQEndpoint policy was imported into the IIBNODE_NOQM integration
E iÜg Integration Registries
node by using the IBM Integration Integration Registry on IIBNODE_NOQM web interface for
IIBNODE_NOQM or by viewing the Integration Registry in the IBM
Integration Toolkit.
! S"l2 Policies
! I 1 ............. in MQEndpoint/LocalConnectToIIBQM
(ö Services
+ Integration Registry on IIBNODE_WITHQM +
Integration Registry on IIBNODE_WITHQM2 - 4
Integration Registry on TE5TNODE_iibadmin É-
|£=! Policies
i 1 .........In MQEndpoint/LocalConnectToIIBQM
Services
V ________________________________________________________________J
Exercise clean up
_ 1. Stop the IIBNODE_WITHQM2 integration node. In the Integration Console, type:
mqsistop IIBNODE_WITHQM2
End of exercise

Student Exercises

In the first part of this exercise, you created a queue manager that is named IIBQMGR.
In the second part of this exercise, you created two integration nodes (IIBNODE_WITHQM and
IIBNODE_WITHQM2). Each integration node specifies the same queue manager (IIBQMGR) as the
default queue manager. You also created an integration server on each integration node.
In the third part of this exercise, you added the BROKER.SYSTEM queues to the queue manager.
In the fourth part of the exercise, you created an MQEndpoint policy on the development integration
node TESTNODEJibadmin by using the IBM Integration web interface. You also exported an
MQEndpoint policy and then imported it into another integration node.

Student Exercises
Exercise 3. Using the IBM Integration Toolkit

In this exercise, you use the IBM Integration Toolkit to complete basic
configuration tasks. You also import, deploy, and test a message flow to learn
the administrative tasks available in the development environment.

• Import, deploy, and test a message flow
• Use the BAR file editor to examine the BAR file contents
Introduction
You typically administer IBM Integration Bus by using the IBM Integration web
user interface, and the IBM Integration Console command interface. Some
basic administration functions are also available in the IBM Integration Toolkit.
In this exercise, you use import, deploy, and test a message flow so that you
can gain an understanding of the administrative tasks that a developer often
does in a development environment.
In the first part of this exercise, you import an Integration Bus project
interchange file into the Integration Toolkit. The project interchange file
includes a message flow application. The message flow is shown in the
following figure.
© Copyright IBM Corp. 2015 Exercise 3. Using the IBM Integration Toolkit 3-1
Student Exercises
This message flow accepts a simple XML message from an IBM MQ queue of
the form:
<InMsgXVersion>2</Version></InMsg>
The message flow validates the value of <version> in a Filter node as follows:
• If <version> equals 2, send the message through the True terminal and
put the message on the REPLYQ node, which puts the message on the
REPLY queue.
• If <version> equals 1 or 3, send the message through the False terminal
to the FALSEQ node, which puts the message on the FALSE queue.
• If <version> does not equal l, 2, or 3, send the message through the
Unknown terminal to the UNKNOWNQ node, which puts the message on
the UNKNOWN queue.
• If an error occurs during message processing on the Filter node, the
message is sent through the terminal to the FAILUREQ node, which puts
the message on the FAILURE queue. If the put to the FAILURE queue
fails, the message is routed back to the IN node and sent to the
TraceExtList node.
- / Note ---------------------------------------------------------------------------------
f\
You learn more about the handling of message flow processing errors later in this course.
y
Student Exercises
In the second part of this exercise, you create a BAR file and examine the
configurable properties by using the Integration Toolkit BAR file editor. You
then deploy the BAR file to the development integration server.

In the third part of this exercise, you test the message flow by using the
Integration Toolkit Flow exerciser.
Required materials
• IBM MQ and IBM Integration Bus software components
• IIBQM queue manager that you created in Exercise 2
• Lab exercise files in the c:\iabfiies\Lab03-Tikt folder.
• RFHUtil in the C:\Software folder
Student Exercises
Exercise setup
_ 1. This exercise assumes that you successfully completed Part 1 of Exercise 2 in which you
created the queue manager IIBQM.
If you did not do Part 1 of Exercise 2, complete that part of the exercise before proceeding with
this exercise.
_ 2. Use the IBM MQ runmqsc command to define the queues that are required for this
exercise. You use a command script for this purpose. The command file is in the
C:\labfiles\Lab03-Tlkt\resources directory.
_ a. Start an IBM Integration Console session if one is not already running.
_ b. Change to the C:\iabfiies\Lab03-Tikt\resources directory.
Enter the command:
cd C:\labfiles\Lab03-Tlkt\resources
_ c. Enter the command:

runmqsc IIBQM < C:\labfiles\Lab03-Tlkt\resources\Q Defs.mqsc
You should receive a response that indicates that the queues are created, similar to the
following example.
def ql(IN) replace WebSphere MQ
AMQ8006 queue created.
~k
def ql(REPLY) replace WebSphere
MQ queue created.
AMQ8006 ~k
def ql(FAILURE) replace
WebSphere MQ queue created.
AMQ8006 ~k
def ql(UNKNOWN) replace
~k
AMQ8006
def ql(FALSE) replace WebSphere
MQ queue created.
~k
AMQ8006 def ql(CATCH) replace WebSphere

MQ queue created.
AMQ8006

7 : end
6 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
podrá reproducir o
Student Exercises
_ d. Use the IBM MQ Explorer to verify that the local queues IN, REPLY, FAILURE,
UNKNOWN, FALSE, and CATCH are created on IIBQM queue manager.
feM Explorer - Navigator E3 =

□ 3 MQ Explorer - Content Ü
Q 0B^
IBM WebSphere MQ Queues
S- Queue Managers
- 0 IIBQM ______ Filter: Standard for Queues
S Topics S Queue name Queue type Open Input count | Open output count Current queue depth |
Subscriptions +>S y CATCH Local 00 0
Channels S y DLQ Local 00 0
Listeners y FAILURE Local 00 0
■ S Services y FALSE Local 00 0
■ S Process y IN Local 00 0
Definitions -S y REPLY Local 00 0
Namelists y UNKNOWN Local 00 0
_ e. Minimize the IBM Integration Console and IBM MQ Explorer.
Part 1: Work with a simple message flow

In this part of the exercise, you import an Integration Bus application into the Integration Toolkit
workspace and examine the message flow.
_ 1. Start the IBM Integration Toolkit if it is not already running.
_ a. Double-click the IBM Integration Toolkit 10.0.0.0 icon on the desktop.
You can also start the toolkit by clicking All Programs > IBM Integration Bus 10.0.0.0 >
IBM Integration Toolkit 10.0.0.0.
_ b. Close the Welcome window to go to the Integration Development perspective.
_ 2. Import an application from a project interchange file into the Integration Toolkit workspace.
_ a. From the Integration Toolkit menu bar, click File > Import.
The Import window is displayed.
® Import
Select
Import a project and its dependent projects Prom a Zip Pile.
IÔ
Select an import source:
!
S-(¡5? General à CVS
Ê CB5 Decision Services EHfc EJB
l^-lS’ IBM Integration

Project Interchange
_ b. Verify that IBM Integration > Project Interchange is selected, and then click Next.
erchange
EI-& Install
¿■ ■ ■ fe Java
EE
c. To the right of From zip file, click Browse.

d. Browse to the C:\labfiles\Lab03-Tlkt\resources directory.
3-5
© Copyright IBM Corp. 2015 Exercise 3. Using the IBM Integration Toolkit
podrá reproducir o
Student Exercises
__ e. Click VersionTest_ProjectInterchange.zip and then click Open.

__ f. Select the TestVersionNumber check box (if it is not already selected) and then click
Finish.
I® Import Project Int erchange Co ntents >
Import Projects
Import Projects From a zip File.
From zip file: | C:li,labPiles\Lab03-Tlkt\resources\VersionTest_Froject ^ | Browse... |
Project location root: | .1 :\Users',¡ badmin\ICM i.IIDTl 0'i wort space Browse... I
0 U_ TestVersionNumber
The Integration Toolkit imports the application and constructs the workspace.
3. The TestVersionNumber application is now displayed in the Application Development
view.
Fully expand the TestVersionNumber application by clicking the plus (+) signs and examine its
contents.
i Application Development £3 °i£_ Patterns Explorer
Application Development
□"EJ iTestVersionNumberi É-"i|§ Flows

t." TestVersionNumberFlow.msgflow É-S1
ESQLs
É-jíyl Check_for_V2.esql
■■¿es’ll Check_for_V2
You see that the project contains folders for Flows and ESQLs.
4. Double-clicking an object in the Application Development view causes the corresponding
editor to open the object in the editor pane, on the right side of the Integration Toolkit.
Open the message flow in the Message Flow editor by double-clicking the file
TestVersionNumberFlow.msgflow in the Application Development view.
5. Examine the message flow. Verify that it agrees with the figure that is displayed at the
beginning of the exercise.
6. The properties of each node in the message flow are preset to transform and route the
message as described at the beginning of the exercise.
Verify that the node properties match the following table.
You can view (or change) a property by right-clicking a node and then clicking Properties.
Student Exercises
Node properties are grouped into pages. The Basic page is initially visible for most nodes.

podrá reproducir o
Node name Node type Properties

IN MQInput
Basic: Queue name = IN MQ Connection:

Connection = Local queue manager Destination queue
manager name = IIBQM
Input Message Parsing: Message Domain = XMLNSC
Advanced: Transaction mode = Yes
TraceExList Trace
Basic:
Destination = File
File path = C:\TraceExList.txt
Pattern = In TraceExList! Root ===> ${Root}
ExceptionList ===> ${ExceptionList}
REPLYQ MQOutput
Basic: Queue name = REPLYQ MQ Connection:

FAILUREQ MQOutput
Basic: Queue name = FAILURE MQ Connection:

Test_Version=2 Filter Basic: Filter expression = {default}check for V2

CATCHQ MQOutput
Basic: Queue name = CATCH MQ Connection:

UNKNOWNQ MQOutput
Basic: Queue name = UNKNOWN MQ Connection:

FALSEQ MQOutput
Basic: Queue name = FALSE MQ Connection:

podrá reproducir o
Student Exercises
Part 2: Create and deploy a BAR file

In this part of the exercise, you create and deploy a BAR file in the Integration Toolkit. You also
examine the configurable properties in the BAR file editor.
_ 1. In the Integration Toolkit, click File > New > BAR file.
_ 2. For the BAR file Name, type
Testversion and then click Finish.
New BAR file
Create a new BAR file

Create a new BAR file resource
Container: BARfiles
Browse...
Folder: f<default> ____________

Name: ] TestVersion|
The BAR File editor opens with the Prepare tab.

3. On the Prepare tab, you identify the resources to include in the BAR file.
Click the TestVersionNumber application from the list of Deployable Resources to select it
as a component of the BAR file.
4. Click Build and Save to build the BAR file and save the workspace. Click OK in the
confirmation window.

podrá reproducir o
Student Exercises
5. The BAR file now appears in the Application Development view under the BARs folder and under
the Independent Resources > BARfiles > BARs folder.
Application Development New...
-]-[S] TestVersionNunriber
Flows
I I ; .............. pi TestVersionNumberFlow.msgflow
¿1 ESQLs
f---|epl Check_for_V2.esql ;
.... Ipslql Check_for_V2
BARs
^ iTestVersiori.bar -> BARfiles/Test Version, bar I □■4
Independent Resources B \z3 BARfiles [—■¿3 BARs
12 Test Version, bar
6. In the BAR file editor, click the Manage tab.

On the Manage tab, you can review and manage the resources that are contained within the BAR
file. You can add, remove, or modify resources, and override configurable properties. You can then
rebuild the BAR file, in preparation for deployment.
7. Fully expand the contents of the BAR file on the Manage tab.
Student Exercises
When you expand the contents of the message flow, you see an entry for each node in the
message flow. The nodes are listed in alphabetical order.
Manage
Rebuild, remove, edit, add resources to BAR and configure their properties
LiHlj TestVersionNumberFlow.msgflow J L0 TestVersion.bar £3 | 1=5

13
j Deployment Log
H Properties £3 Problems ( a— Outline Tasks
TestVersionNurnberF
Name r law'..rnsgflow
Type 1 Modified Size 1 Path
B [A] TestVersionNumber IT (T) Application Oct
9, 2015 8:00:13 AM 4285
Configure properties of selected built resource.
ConfigureHT| iE)
Workload Management
Filter by: | <Type
[=1 application.descriptor filter text> Oct 9. 2015 8:0... Oct
9, 2015 8:00:12 AM “3 134
¡jeljqi Check._for_V2.esql
Consumer Policy Set Consumer Policy Set Bindings 9, 2015 8:00:12 AM
E5QL file Oct
181
Coordinated Transaction Monitoring Profile Name Provider HSEI

B ËHU TestVersionNumberFlow 1
#0 CATCHQ
Policy 5et Provider Policy 5et Bindings Security Profile Name
[Sfl FAILUREQ
#0 FALSEQ
ME IN fcJ
idEfl REPLYQ
Test_Version=2 fcJ
"IP TraceExList
__________________________________________________________________________ ! 3
8. Examine the contents of the Properties view below the BAR File editor view as you click the
►Command For packaging the BAR contents
Prepara Manage I Jser Log Service Log
message flow and each node that is contained within the BAR file.
These properties are known as configurable properties. These properties can be overridden in
the BAR file. In most cases, these properties are a subset of the node properties that you see
in the Message Flow editor.
As an administrator, you might want to use the BAR file editor in the Integration Toolkit to
modify the configurable properties and update the BAR file. Take some time to examine the
configurable properties for the message flow and for each node.
9. Deploy the BAR file to the integration server that is named default on the
_ a. Verify that the integration node and the integration server are running.
In the Integration Toolkit Integration Nodes view, verify that TESTNODEJibadmin has a
green arrow and that the default integration server also has a green up arrow.

Student Exercises
podrá reproducir o
L- integration Nodes! £3 Integration Registries
E otg Integration Nodes + 3

IIBNODE_NOQM 3- IIBNODE_WITHQM 3
IIBNODE_WITHQM2 - 3
TE5TN0DE_iibadmin QT, default
b. In the Application Development view, right-click the TestVersion.bar and then click
Deploy from the menu. The Deploy dialog box is displayed.
c. Select the integration server that is named default under the TESTNODEJibadmin
integration node as the target for the deployment.
Deploy
Select Integration server to deploy selected resources.
E-JIj Integration Nodes 1+ IIBNODE_NOQM <3

IIBNODE_WITHQM $ IIBN0DE_WITHQM2 É- J
TESTNODEJibadmin
CD
<x Wm
_ d. Click Finish. A Deploying dialog box is displayed while the BAR file is deployed to the
integration server.
- HA Note
r
As you learn later in the course, there are several ways to deploy a message flow to an integration
server. Another commonly used method in the Integration Toolkit is to click the BAR file in the
Application Development navigator and drag it to the integration server in the Integration Nodes
view.
_ 10. Verify that the operation was successful by using the Integration Toolkit Integration Nodes
view and the Deployment log.
_ a. Select the Integration Nodes view in the lower-left view of the Integration Toolkit (if it is
not already selected).
Student Exercises
b. Expand the Integration Nodes > TESTNODEJibadmin > default hierarchy until you see
IIBNODE_NOQM
the message flow, TestVersionNumberFlow.
- Integration Nodes
IIBNODE_WITHQM ¿=i
IIBNODE_WITHQM2 I- ¿=l
TESTNODEJibadmin default
-]-^j TestVersionNumber
43} = TestVersionNumberFlow :
....[e^qi Check_for_V2
If the icon next to a message flow is a green upward arrow, the flow is successfully
deployed and is running.
If the icon is a yellow triangle, examine the Problems view (in the lower-right pane of the
IBM Integration Toolkit) for more status information. It might be that the message flow is
deployed but not yet running.
If the message flow start is in progress, the icon changes to the green upward arrow
when the message flow is started. It is also possible that the flow might require a manual
start, in which case you right-click the message flow, and then click Start.
You also see another item in the hierarchy (Chec_for_V2). This component is the ESQL
code that the message flow uses in the Filter node. It is included in the BAR file
automatically.
c. Click the Deployment Log tab in the lower-right pane of the Integration Toolkit.
The Deployment Log shows whether the BAR file was deployed successfully,
d. Expand the message in the Deployment Log by clicking the plus sign (+).
Properties Problems > Outline A Tasks . Deployment Log §3

Details Timestamp
B t [TestVersion.bar] has been deployed to integration server default on integration node TESTNODEJibadmin Fri Oct 09 08:29,,,
i BIP2871I; The request made by user 'W52008R2i'i64\iibadmin' to 'deploy' the resource 'C ; /User s/iibadmin/IEM/IIBT i 0/^ Fri Oct 09 08:29,,,
You should see a message that indicates that the BAR file was successfully deployed to
the integration server. BiPnnnns messages that are preceded with a blue “i” icon (for
“information”) indicate success; a yellow triangle icon indicates a warning message, and a
red exclamation point icon indicates a deployment failure.

podrá reproducir o
Student Exercises
Part 3: Test the message flow by using the Flow Exerciser

In this part of the exercise, you test the message flow by using the Integration Toolkit Flow
exerciser.
ry
r Note
The Flow exerciser automatically builds and deploys a BAR file to the selected integration server. When
you use the Flow exerciser, you can skip the step to manually build and deploy the BAR file. In this
exercise, you manually built and deployed a BAR file in Part 2 so that, as an administrator, you are
familiar with the options for building, modifying, and deploying BAR files in the Integration Toolkit.
_ 1. In the Message Flow editor, click the Start Flow exerciser icon to deploy the message flow
and start the Flow exerciser.
I TestVersionNumberFlow.msgflow U ! TestVersion.bar
<] Ç"! Palette
Flow Exerciser 3] I:; ©,
k \>
Favorites -w Í ;■ -+ h
\ i
_ 2. Select the default integration server on the TESTNODEJibadmin integration node and then
click Finish.
i Select Integration Server
Select Integration Server

Select the integration server where you want to deploy the message flow and dick Finish,
If the integration server is not currently in recording mode, then recording mode is enabled as a result of this action,
- itg Integration Nodes + $ IIBNODE_NOQM IIBNODE_WITHQM I ¿Î TTRNODF WTTHDM?
3. The application is deployed to the default integration server on TESTNODE_iibadmin. You
É TESTNODEJibadmin
1=!Ií- B, .Sv,I
ft EHH
4. should see a window that indicates that the message flow is being deployed.
Click Close in the Record Message window.
The deployed message flow is running. It is waiting for a message to enqueue on the IN
queue. When the Flow Exerciser puts a message to the IN queue, the message flow reads
(dequeues) the message and sends it through the message flow.
Test the message flow with the Test_v2_Msg.xmi file by importing the file from the file system
and sending the message with the Flow exerciser.
a. Click the Send a message to the flow icon in the Flow Exerciser toolbar.
Student Exercises
■ T est Ver sionNumberFlo w. rnsgflow £3 TestVerslon.bar

<] Palette Flow Exerciser: a si a
1 \Ö±
L - Favorites ■Cafe . J -n. R — «lit
_ b. In the Send Message window, click the New Message icon.
Send Message
Send Message
Create or select a message to send to the fit
-I' tS* Input Messages

new message 1
_ c. For the Name, type: versionis2

_ d. Click Import from file and then click File system.
_ e. Browse to C : \labf iles\Lab03-Tlkt\data, select the file Test_V2_msg.xml, and
then click Open.
The file is imported into the Flow exerciser.
I Send Message
Send Message
Create or select a message to send to the flow. Click the message category header (e.g, Input Messages) for more information.
Input Location: |IN ►Header Message Details —
Import from file

Name | VersionIs2
File name: I C:\labflles\Lab03-Tlkt\data\Test_V2_Msg,xml Workspace... File system...
□ {£' Input Messages
Main
■ ■ ■ 1^3 new
I <InMsg > cVersion >2 </Verslon ></InMsg>
message 1 iJP new
message 2
_ f. Examine the data that was read from the file. In this test file, version is set to 2.
5. You are ready to send the test message to the queue for processing by the message flow. Before
you do, reexamine the message flow diagram.

podrá reproducir o
Student Exercises
Given the test data that you are about to send to the queue, where should the incoming
message go? The possible destination queues are REPLY, UNKNOWN, FALSE, CATCH, and
FAILURE.
6. Click Send.
The Progress Information window shows that the message is sent to the input queue IN. It also
shows the destination.
1 i^TñTrn
Progress Information
□-[bj Invoke Message Flow(VersionIs2)

v'' Message flows deployment successfully completed S'
Starting
mCL Sending Message to MQ Queue "IN"
S& MQ Queue Monitor "REPLY"
H Stopped listening for response Li Stopped
When the Progress Information window displays Stopped, the test is complete. Click
7. Close.
The message path is highlighted on the message flow. Where did the message go?
8. The message path should indicate that message is routed to the REPLYQ node (which
references the REPLY queue) because the Version = 2.
If you view the queues by using IBM MQ Explorer, you see that the Current queue depth for the
r Im I
_
i
Information
I
output queue is empty. The Integration Toolkit Flow exerciser does not put the message to the output
queue; it shows the message path only. If you want to view the messages on the queues, you can use
the IBM MQ amqsput sample program or the RFHutil SupportPac to test the flow by putting a message
to the IN queue.
For example, to use the amqsput sample program to verify that the Test_v2_msg.xmi message is put on
the REPLY queue on the IIBQM queue manager, type the following command in an IBM Integration
Console window:
amqsput IN IIBQM < C:\labfiles\Lab03-Tlkt\data\Test V2 msg.xml
J
Student Exercises
9. Following the same procedure that you followed in Steps 4-8, test the flow by using the other
test messages in the c:\iabfiies\Lab03-Tikt\data\ directory.
You should be able to predict the message destination based on the message content and
Troubleshooting
the filter rules that are described in the exercise Introduction.
r
If the message did not go the expected queue, check the following conditions on the IBM MQ queue
manager or the Windows Event Log.
The message flow might be in a stopped state.
Is the message flow getting messages
Check the Integration Nodes view in the IBM
from the IN queue (is the IBM MQ
Integration Toolkit. If necessary, start the
Open Input Count on the IN queue =
message flow.
i)?
If Open Input Count for IN = 0, but the

deployment was successful, you might have a
Is the number of messages on the IBM
typographical error in the queue name on the
MQ Backout Requeue Queue = 0?
MQInput node. Check the Windows Error Log
for one or more error messages.
If Open Input Count for IN > 1, there are
multiple message flows getting messages
Is the number of messages on the IBM
from IN. This situation is more likely to happen
MQ Backout Requeue Queue > 0 and
in later exercises, should you duplicate one
increasing?
flow to serve as a starting point for another.
Was the message sent to the CATCH Check the Windows Event Log to determine
queue? the cause of the runtime error.
Was the message sent to the FALSE Check your test message. Is the <version>
or UNKNOWN queue? field present? Does <version> = 2?
Exercise Clean up
_ 1. In the Integration Toolkit, complete the following steps:
_ a. Close the message flow in the Message Flow editor.
_ b. Close the BAR file in the BAR file editor.
_ c. In the Integration Nodes view, right-click the default integration server on
TESTNODEJibadmin and then click Stop recording.
_ d. In the Integration Nodes view, delete all flows and resources from default integration
server on TESTNODEJibadmin.
Right-click the default integration server in the Integration Nodes view, and then click
Delete > All Flows and Resources. Click OK in the confirmation window.
_ 2. Close the IBM Integration Toolkit.

podrá reproducir o
Student Exercises
End of Exercise
Student Exercises

In the first part of this exercise, you imported an Integration Bus project interchange file into the
In the second part of this exercise, you created a BAR file and examine the configurable properties by
using the Integration Toolkit BAR file editor. You then deployed the BAR file to the development
integration server.
In the third part of this exercise, you tested the message flow by using the Integration Toolkit Flow
exerciser.

Student Exercises
Exercise 4. Administering the IBM Integration Bus

runtime components
In this exercise, you use the IBM Integration Bus commands and IBM
Integration web user interface to manage IBM Integration Bus runtime
components and deploy message flow applications. You also back up and
restore the integration node configuration data.

• Administer IBM Integration Bus components by using the IBM Integration
Bus commands, IBM Integration web user interface, and IBM Integration
API Exerciser
• Deploy IBM Integration Bus message flow applications by using the IBM
Integration Bus commands, IBM Integration web user interface, and IBM
Integration API Exerciser
• Back up and restore an integration node and its configuration
Introduction
IBM Integration Bus administrators can manage and manipulate the IBM
Integration Bus components by the IBM Integration command interfaces and
the IBM Integration web user interface. While the IBM Integration web user
interface is easier to use and more intuitive, commands give the ability to fully
automate the management tasks by using scripts.
In this part of the exercise, you use the IBM Integration command interface to
check the status and configuration of the integration node, integration servers,
and message flows. You also use the IBM Integration command interface to
deploy a message flow.
In the second part of the exercise, you use the IBM Integration web interface to
check the status and configuration of the integration node, integration servers,
and message flows. You also use the IBM Integration command interface to
deploy a message flow.
In the third part of the exercise, you use the IBM Integration API Exerciser
sample program to manage the integration node, integration server, and
integration node. You also used the Integration API Exerciser sample program
to create a script the creates an integration server.
Student Exercises
In the fourth part of the exercise, you back up the integration node
© Copyright IBM Corp. 2015 Exercise 4. Administering the IBM Integration Bus runtime 4-1
configuration information.
Requirements
• IIBNODE_NOQM integration node and integration servers that were
created in Exercise 1
• Lab exercise files in the c:\iabfiies\Lab04-Admin directory

Student Exercises
This exercise uses the IIBNODE_NOQM integration node and integration servers from Exercise 1,
Note
Part 3.
Part 1: Use the IBM Integration command interface

In this part of the exercise, you use the IBM Integration command interface to check the status and
configuration of the integration node, integration servers, and message flows. You also use the
command interface to deploy a BAR file that contains an application.
Important
When you enter commands, do not press Enter where you see a line break in the command. You
must enter commands on a single line, although it is permissible for the command to wrap to
subsequent lines as you type it. Press Enter only after you type the entire command.
1. IBM Integration Bus supplies a special command console from which you run Integration Bus
commands. To view what happens if you try to work outside of the Integration Console, open
a Windows command prompt window.
__ a. From Windows, click Start
_ b. Enter cmd in the Open field and then click OK.
__ c. Enter the command: mqsilist iIBNODE_NOQM

You know that the integration node is deployed and running, so what might cause this
problem?
In the lecture material, you learned that you must run mqsiprofiie.cmdto set up the
environment for various components. Do not run the mqsiprofile command now.
__ d. Close the Windows command prompt window.
2. Review the mqsiprofile. cmd file in the C: \<Integration Bus Install Path>\server\bin
directory.
In the lab exercise image for this course, the Integration Bus Install Path is c:\Program
Files\IBM\IIB\10.0.0.0\server.
__ a. Use Windows Explorer to locate the mqsiprofile. cmd file.
__ b. Right-click the file and then click Edit to open the file in Notepad.
You can see that the command file sets some environment variables. When you use the
IBM Integration Console in the Windows environment, mqsiprofiie.cmd is automatically
called to set the command environment.
Student Exercises
__ c. Close the file when you are done looking at it. Do not save any changes if you are
prompted to do so.
3. If it is not already running, start the IBM Integration Console as an administrator.
Right-click the shortcut icon on the desktop, or click Start > All Programs > IBM Integration
Bus 10.0.0.0, right-click IBM Integration Console, and then click Run as administrator.
4. Get a list of running integration servers and message flows on IIBNODE_NOQM by entering
the command:
mqsilist IIBNODE_NOQM -d2
For most commands, you can enter the command followed by a question mark character (?) to get a
summary of the command syntax.
You should see that two integration servers are running on IIBNODE_NOQM: server! and
server2.
You should also see that no message flows are currently running on the integration servers.
5. Deploy the AdminApp.bar BAR file to the server2 integration server.
The AdminApp.bar file contains an application that is named Transfomation_Map. The
application contains a message flow that is also named Transformation_Map.
When deploying a BAR file, the mqsideploy command looks for the file in the current
directory (the one from which the command is run) by default. If the BAR file is not in that
directory, you must specify the full path.
__ a. In the IBM Integration Console, change directories to the directory that contains the BAR
file (C:\iabfiies\Lab04-Admin\resources) before you deploy the file. Type:
cd C:\labfiles\Lab04-Admin\resources
__ b. Type the following command to verify that the file AdminApp.bar is in the
C: \labfiles\Lab04-Admin\resources directory.
dir
__ c. Type the following command to view the contents of the BAR file:
mqsireadbar -b AdminApp.bar
The command should return the following response.

BIP1052I: Reading Bar file using runtime mqsireadbar...
AdminApp.bar: Transformation_Map.appzip (10/12/15 2:51 PM):
__ d. Type the command to deploy the AdminApp.bar file:

mqsideploy IIBNODE_NOQM -e server2 -a AdminApp.bar
Student Exercises

BIP1039I: Deploying BAR file

'C:\labfiles\Lab04-Admin\resources\AdminApp.bar' to integration node

'IIBNODE_NOQM' <integration server 'server2'>
BIP1092I: The integration node successfully processed the deployment request.
_ 6. Verify that the flow was successfully deployed. Type:
mqsilist IIBNODE_NOQM -e server2
You should see a response that is similar to the following example:

BIP1275I: Application 'Transformation_Map' on integration server 'server2' is
running.
_ 7. Remove the deployed message flow application from the server2 integration server:
mqsideploy IIBNODE_NOQM -e server2 -d Transformation_Map
r rf Him ---------------------------------------------------------------------------------------------------------------------------------------------
To reduce the amount of typing you do, you can press the up arrow key on your keyboard in the IBM
Integration Console window to retrieve a previous command. You can then edit the portion of
command that changed (if necessary), by using the left arrow, right arrow, Delete, and Backspace
keys. Press Enter to run the command after you finish editing it.
For example, the command you enter in the next step is identical to the command you entered in
step 7. Press the up arrow key until the mqsideploy command is displayed, edit the command, and
then press Enter to reissue the command.
V ______________________________________________________________________________ y
_ 8. Redeploy the AdminApp.bar BAR file to the server2 integration server on IIBNODE_QM:
mqsideploy IIBNODE_NOQM -e server2 -a AdminApp.bar 9. Enter a command that
stops the message flow application that you deployed in Step 8:
mqsistopmsgflow IIBNODE_NOQM -e server2 -k Transformation_Map
_ 10. Restart the message flow:

mqsistartmsgflow IIBNODE_NOQM -e server2 -k Transformation_Map
You should see a confirmation message that the application started.

_ 11. Minimize or close the IBM Integration Console window. You use it later in the exercise.
Student Exercises
Part 2: Use the IBM Integration web interface

In this part of the exercise, you use the IBM Integration web interface to complete basic
administration on the integration node, integration server, and message flow applications.
_ 1. Start the IBM Integration web interface for IIBNODE_NOQM.
If you do not already know the HTTPConnector port for this integration node, type the
following the command to find the port.
_ 2. Display the IIBNODE_NOQM QuickView and Advanced Properties.

_ a. Select IIBNODE_NOQM in the IBM Integration web interface navigator in the left pane.
_ b. Show the integration node Advanced Properties by clicking the down arrow on the
Advanced Properties heading in the right pane.

r Advanced Properties
Platform Name
niter Options...
1IBNODEJJOQM - Integration Node
Fixpack Capability Operation
¿I IIBNODE_NOQM OverviewMode Platform Architecture

Statistics
Platform Version Queue
Servers -r
&
► ®3 Operational Policy
Manager Build Level
/“Edit
Admin Agent Process ID
► 0 Data
► Security r QuickView
► ^ Monitoring
IIBNODE_NQQM
10DQQ
Admin Security ©off

Run Mode Short running
Description Long
Description
Windows Server 2008 R2 Standard
unrestricted
advanced
AMD64
6.1 build 7601 Service Pack 1
SD0Q-L150316.10572 3004
►Component Properties
3. Display the properties for the server2 integration server.

__ a. Expand Servers by clicking the down pointing arrow on the left side of Servers.
b. Click server2.

Student Exercises
c. Show the integration server Advanced Properties by clicking the down arrow on the
Welcome, Default
IBM Integration
Filter Options...
$ I1BNODE_NOQM Q Overview [^v Resource Statistics [*v Statistics

Servers
server2 - Integration Server # Edit
►serverl ~
& server2 ▼ Quick View

► 11=1 Operational Integration Server Name server2
Policy Run Mode running
► ¡g Data UUID 7f6a21 da-2ba1 -4d52-920D-b2d74b857816
► Security Running true

► Monitoring Short Description
Long Description
Record Mode Disabled
| ▼ Advanced Properties
Injection Mode Disabled
Process ID 2948
Trace Level none
Soap Nodes use Embedded Listener true

Thread Local Proxy Name Managers false
Console Mode off

HTTP Nodes use Embedded Listener false
Inactive User Exit List

Active User Exit List
Trace Node Level on

User Trace Level none
►Resource Manager Properties
4. Display the properties of a message flow that is deployed to the server2 integration server.
_ a. Click the arrowon the left side of server2 to show its contents.
_ b. Click the arrowon the left side of Applications to show its contents.You should see that
the application Transformation_Map is deployed to server2.
_ c. Click the arrowon the left side of Transformation_Map to show itscontents.
_ d. Click the arrowon the left side of Message Flows to show its contents.
_ e. Click the Transformation_Map message to display its properties and then expand the
Advanced Properties and Deployed Properties sections.
Student Exercises
5. Stop the message flow that is running on server2.
__ a. Click the down arrow next to the Transformation_Map message flow and then click
Stop.
Version
Filler
Options... EHI Transformation_Map - Message Flow
UUID
▼ @ Applications
Q Overview |*v Statistics (j^ Operational Policy
J liBNODEJJOQM » g
Service T
Serrera r►il serrer! f
V ^ Transfornnalion_Map v (5
Commit C
r
Libraries T EG Message Flows Edit
Additions
& serreß ▼ g Services g p Transformation_Map
▼ Quick View ▼¡
REST APIs gl Applications
* 51 TransfQíma!icn_Map ^ Subflows Message Flowff Name
Transformation_Map 3(i
T ransformation_Map
¡§ Libraries
Flows
■y ¡P Massanp ► £L, Resources Version
j|| References UUID Stop —r
r
3a88e189-9b67-480f-iyD954eOQe«6ea5bb
^ Libraries Service Trace Force stop 3

Level none
Commit Count 1
gm Additional Instances 0
Transformation_Map
Subflows t Start Mode Maintained
g Resources ¡¡p Coordinated Transaction no
References Commit Interval 0
Ubraries Running true
jK, Shared Ubraries 0 Run Mode running
Message Flows gl
SuWows gj,
Resources
►¡?j| Operational Policy
1 - Advanced Properties 1
► g Data
►^ Security
►0 Monitoring
▼ Deployed Properties
Modified time 2015-10-12 15:18:28.000 -0700
Deployed time 2015-10-1212:26:51.702 -0700
Bar file name C:\labfiles\Lab04-
Admin\resources\AdmiriApp.bar
b. Verify that the runMode property for the message flow is now set to stopped.

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunatgob.pe>. La impresión está destinada únicamente para uso personal y privado.
Student Exercises
6. Delete all deployed applications and resources on server2.

__ a. Click the down arrow on the right side of server2 to display the menu, and then click
Delete All.
IIBNODE_NOQM v ¡g Servers ▼
► serverl ▼
- server2 ▼i
CD
¿5 Servie <£: server^
g REST Start
’ ©Applic Start All Application Types
- ^ Tr; Start All Message Flows
s Stop
-& Stop All Application Types
Stop All Message Flows
Eta Rename
Delete All
s Delete
3 Librari Deploy
__ b. A confirmation window asks if you are sure that you want to delete all deployed
contents. Click Yes on the confirmation window.
__ c. Verify that no applications are deployed to server2.
7. Deploy the AdminApp.bar file to serverl.
__ a. Click down-arrow on right of serverl and then click Deploy.
» ¿I IIBNODEJNQQM y r= Servers v
►serverl 3
r ^ server2 {£. server!
¡g Servie Start
(3 REST Start All Application Types
- gj Applio Start All Message Flows
- SI Tr; Stop
3 Stop All Application Types
-m Stop All Message Flows
Rename
& Delete All

►
m Deploy
3 Librari Start recording
fé Share Stop recording
b. Click Browse and browse to C:\labfiles\Lab04-Admin\resources, click AdminApp.bar, and

then click Open.
Student Exercises
c. Expand the contents of the BAR file to view the configurable properties of the message
flow and the
message flow
node.
BAR file: AdminApp.bar Browse

Deploy
Content Value
T
Transformado nJYIap.appzip A
startMode <unset>
javal solation <unset>
T
Transformatton_Map ...
additionaJ Instances <unset>
ntotificationTtireshold M sg sPerSec <unset>
maximum RateMsgsPerS ec <unset>

V
processing! ¡meo utSec <unset>
Overrides
Deploy BAR File

Select a BAR file to deploy. Optionally, provide an overrides file.
Cancel
_ d. Click Deploy.
_ e. Verify that the Transformation_Map message flow application is deployed to server!.
8. The IIBNODE_NOQM integration node that you are using in this exercise does not have a
queue manager that is associated with it. In this step, you see what happens when you try to
r teg ration
a. In the IBM Integration web interface for IIBNODE_NOQM, click down-arrow on right of
server! and then click
Filter Deploy.
Options...
£) The deployment of the BAR file 'Adminl .bar* to 'serverl' has failed. BIP2087 06:03 X
3NODE NOQM ▼b. Click Browse and browse toQ C:\labfiles\Lab04-Admin\resources,

Overview ['V Resource Statistics ['V Statistics
click Adminl .bar, and
I Servers -w then click Open.
^ Edit
¿1, serverl ; *r] Click Deploy. After a brief pause, an error message displays in the web interface that
c.
çŒ. Services
M REST APIs
indicates that the deployment |failed.
▼ Quick View
A
deploy a message flow that requires a default queue manager.

Welcome, Default '
- 0 Applications
Intearation Server Name

podrá reproducir o
Student Exercises
9. The error detail is provided in the Admin Log in the IBM Integration web interface.
__ a. Click the arrow on the left side of the Monitoring folder to show its contents.
__ b. Click Admin Log.
__ c. Review the messages in the Admin Log.
One of the error messages in the Admin Log describes the reason why the deployment
failed. In this case, deployment failed because the message flow in the BAR file requires a
default queue manager on the integration node.
Welcome, Default -
IBM Integration
Filter Options...
Admin Log
▼ $ IIBNODE_NOQM ▼
^ Overview
▼ {jj= Servers v
► £ serverl ▼ <£* Refresh
► ^ server2 ▼ Message Source Timestamp ▼ Message Detail

► llg Operational Policy
► ¡gj Data Runtime Response A
0 BIP4041E 2015-10-13 06:03:45.237
Integration server 'serverl' received an administration request
Pacific Daylight Time
that encountered an exception. While attempting to process a n
▼ Monitoring administration request, an exception was encountered. No u
Y Admin Log pdates have been made to the configuration of the integration
server. Review related error messages to determine why the
administration request failed.
0 BIP2683E Runtime Response 2015-10-13 06:03:45.237 A component was configured to use the queue manager that i s
Pacific Daylight Time specified on the integration node, but no queue manager wa s
found for the integration node. By default, components in IB M
Integration Bus use the queue manager that is specified on the
integration node to connect to WebSphere MQ. No queue
manager is specified on the integration node, so the compone
nt cannot resolve the connection to a queue manager. For M
Qlnput, MQOutput, and MQGet nodes, it is possible to specify a
queue manager on the message flow node, but for Aggrega
tion, Collector, Sequence, and Resequence nodes, the queue
manager must be specified on the integration node. Specify a
queue manager on the integration node, or use a queue man
ager that is specified on a MQInput, MQOutput, or MQGet no de.
t) BIP28711 Administration Result 2015-10-13 06:03:45.237

The request made by user 'SYSTEM[Default]' to 'deploy' the r
Pacific Daylight Time esource Adminl.bar' of hype ’BAR' on parent 'serverl' of type
'ExecutionGroup' has the status of FAILED'.
0 BIP2087E Runtime Response 2015-10-13 06:03:45.236
Pacific Daylight Time Integration node 'IIBNODE_NOQM' was unable to process th e
internal configuration message. The entire internal configura V
tion message failed to be processed successfully. Use the me
ssages following this message to determine the reasons for th
10. Minimize the IBM Integration web interface browser window.
Student Exercises
Part 3: Use the IBM Integration API Exerciser

In this part of the exercise, you use the IBM Integration API Exerciser to manage an integration
node and its resources. You also use the Integration API Exerciser to create an administration
script.
_ 1. Start the IBM Integration API (CMP) Exerciser.
__a. In Windows Explorer, browse to the C:\Program
Files\lEM\lIB\10.0.0.0\server\sample\lntegrationAPI\ directory.
__b. Double-click the startintegrationAPiExerciser.bat file to start the IBM Integration
API Exerciser.
_ 2. To connect to the local integration node, right-click Right-click to connect and then click
Connect to Local Integration node.
[& IBM Integration API (CMP) Ewerciser
I File View Scripting

I [Right-dick to correct! I -----------------—
Connect to Local Integration node,,,

Connect to Remote Integration node,,,
F=
3. Select the IIBNODE_NOQM integration node, and then click Submit.

podrá reproducir o
Student Exercises
4. After a connection is established, the status information is displayed in the lower part of the
Integration API Exerciser window. The upper part of the window displays information about
Student Exercises
5. Select the message flow Transformation_Map.msgflow that you deployed to the integration
server server! to display the message flow properties.
6. By right-clicking the message flow, you can turn on tracing, start and stop the message flow,
delete the message flow, and complete other operations.
J&V IBM Integration API (CMP) Exerciser
File View Scripting
fi> MessageFk
IIBNODE_ getDeployedPolicySet
NOQM getDeployedPolicybet
serverl
Refresh
B-ia Transformation_Map,appzip ■MM
Show raw property table for this object
Transformation_M?n mcnF|n> Li
Transformation_Mi Ci 5
Start
Transformation_Mc Ci
Stop
A
InputXMLSchema.>
JË
■Ci OutputXMLSchema
Delete
=L, server2 Y Administration E
Log |_J Administration Queue !oc
Get Activity Log
Configurable Services y
User Trace
Service Trace
Flow statistics
Set additional instances,..
Set runtime property... Success Set user
defined property,, Success Properties...
Stop the flow by clicking Stop on the menu.

7. Verify that the flow stopped by verifying that the runMode property is now stopped for the
Transformation_Map.msgflow.
I&IBM Integration API (CMP) Enerciser
MessageFlowProxy Method Result

i> IIBNODEJÖQM Fl- = . serverl coordinatedTransactlon no
B"E Transformation_Map,app!lp commitlnterval

0
version
j i ........... ü[rransformat¡on_Map,msgflow
TKancFnKmahinn Man
! .. fJl Transformation_MapJnputMessage, xml
runMode stopped
j .. TransformatlonJIap.map
; .. i m InputXMLSchema.xsd
!
.. 5 OutputXMLSchema.xsd getCommitCountO
!*■■=, serverE: g e tC o m mit In te r val()
0
V Administration Log :—U Administration Queue É- getConfigurationObjectT ype() <Message Flow>
& Configurable Services getConfigurationObjectTypeOfParent() <Application>
getCoordinatedTransactionO else
You can also use the IBM Integration web interface for IIBNODE_NOQM to verify the status of
the message flow.
8. Delete the server2 integration server.
Right-click the server2 integration server on IIBNODE_NOQM and then click Delete. The
delete is completed without confirmation.

podrá reproducir o
Student Exercises
9. With the IBM Integration API Exerciser, you can record a script of an operation, which captures it
for reuse. You can then run this script against other integration node environments.
Create a script that records the steps for creating an integration server and save it in the
C:\iabfiies directory.
a. From the IBM Integration API Exerciser menu bar, click Scripting > Record New Script.
b. Browse to the C:\iabfiies directory and specify a descriptive name, such as CreateNewIS.
xml.
c. Click Save. Scripting is now active.
d. Right-click the IIBNODE_NOQM integration node and then click Create integration server.
Á IBM Integration API (CMP) Exerciser
File View Scripting
1=
=í> IIBMOÜE NO™
Refresh
+]-5 server 1 ■’p’
Adrninist ■ Adrninist
Í1 Configur
Create integration server,,,
_ el
Start all message flows el el
el
Stop all message flows
__ e. Name the new integration server server2, and then click Submit.
__ f. After you see the new integration server show in the list of integration servers, stop the
script recording by clicking Scripting > Stop Recording.
10. From the IBM Integration API Exerciser, delete the server2 integration server.
11. Re-create the server2 integration server from the script.
__ a. Click Scripting > Play Back Recorded Script.
__ b. Browse to the C:\iabfiies directory.
__ c. Click the XML file that you created in Step 9 and then click Open.
The script runs and creates the server2 integration server again. The integration server is
displayed in the list after it is created.
Student Exercises
_ 12. Verify the server2 integration server by deploying an Integration Bus application.
_ a. Right-click the server2 integration server and click Deploy BAR.
I ft. IBM Integration API (CMP) Exerciser
Scripting
I File View
I =i> IIBNODEJOQM
1 + server 1
: ■“
! D -' rpKiJ Refresh
i .. f Adm
i .. _ Adm Show raw property table for this object
Deploy BAR.,.
EE& Coni 1
Start
Stop
_ a. Browse to the c:\iabfiies\Lab04-Admin\resources directory and then select the

AdminApp.bar file. Click Open and wait for the deployment to complete.
_ b. Verify that the message flow was deployed and running.

_ 13. Close the IBM Integration API Exerciser.
Part 4: Back up and restore the integration node

In this part of the exercise, you back up the integration node configuration information.
Normally, you want to back up the integration node configuration information to a separate drive. For
this exercise, you create a local folder and back up to that location.
_ 1. Use Windows Explorer to create a directory that is named iiBNODE_Backup in the
_ 2. Open an IBM Integration Console and back up the integration node configuration to the new
folder. You can use the -a option to name the archive. You do not use it here so that you can
see the default file name for the archive.
Type the following command to back up IIBNODE_NOQM:
mqsibackupbroker IIBNODE_NOQM -d C:\labfiles\lIENODE_Backup
The command should return a message similar to the following example:

BIP125I: Creating backup file
'C:\labfiles\IIBNODE_Backup\IIBNODE_NOQM_ccmmdd_him7mss.zip' for integration node '
IIBNODE_NOQM'.
In the response message, ccmmdd is the year, month, and day, and hhmmss is the hour, minute,
and second of the backup file creation time.
_ 3. With Windows Explorer, browse to the c: \iabfiies\iiBNODE_Backup directory and verify
that the backup file is in the directory.

podrá reproducir o
Student Exercises
You now have all the necessary information to restore your integration node. This file can be
c
o Important
p
i
ed and stored elsewhere (on some type of external media) or, at a minimum, on a separate
drive from where the domain exists.
r
The integration node backup command does not back up all the resources that message flows require
to function correctly. These resources include:
- IBM MQ queues
- Data that is stored in user databases
- Transient information for inflight aggregations or collections
- Runtime code, including resources that are associated with user-defined extensions such as
nodes, parsers, and exits
4. Simulate a system failure by deleting the integration node and integration node
components. After you complete the system failure simulation, you restore the integration
node and components by using the backup file that you created in Step 2.
__ a. From the IBM Integration web interface for IIBNODE_NOQM, stop any message flows
that are running on server! and server2.
__ b. From the IBM Integration web interface, delete the integration servers.
__ c. From the IBM Integration Console, stop and then delete the integration node
IIBNODE_NOQM and all files in its workpath.
Type:
mqsistop IIBNODE_NOQM
mqsideletebroker IIBNODE_NOQM -w
You can also stop the integration node services by using the Windows Services control panel. Click
All Program > Administrative Tools > Services.
Scroll to the IBM Integration Bus component for the integration node and then click Stop.
5. Attempt to start the integration node from a command console:

You should receive a message that indicates that the integration node does not exist.
6. Re-create the integration node IIBNODE_NOQM. Type:
Student Exercises
Do not start the IIBNODE_NOQM integration node after you create it. The integration node must be
Important
stopped before you can restore it.
7. Using the IBM Integration Console, restore the integration node. Type:
mqsirestorebroker IIBNODE_NOQM -d C:\labfiles\lIBNODE_Backup -a arch±ve_flle
In the command, replace arch±ve_f±ie with the name of the archive file that the
mqsibackupbroker command creates in Step 2.
After the restore completes, you receive a message that indicates that the integration node
was restored.
8. Start the integration node by using the IBM Integration Console.
9. Get the port number for the IBM Integration web interface for IIBNODE_NOQM. Type:
10. Using the IBM Integration web interface, verify that the integration node is restored correctly. It
might be necessary to enter the URL for the IIBNODE_NOQM integration node again.
You should have two integration servers that are named server! and server2.
The integration server server2, should be running the Transformation_Map application.
Exercise clean up
_ 1. Stop any message flow applications that are running on server! and server2 on
IIBNODE_NOQM.
_ 2. Delete any message flow applications from server! and server2 on IIBNODE_NOQM.
End of exercise

podrá reproducir o
Student Exercises

In this part of the exercise, you used the IBM Integration command interface to check the status and
configuration of the integration node, integration servers, and message flows. You also used the IBM
Integration command interface to deploy a message flow.
In the second part of the exercise, you used the IBM Integration web interface to check the status and
configuration of the integration node, integration servers, and message flows. You also used the IBM
In the third part of the exercise, you used the IBM Integration API Exerciser sample program to
manage the integration node, integration server, and integration node.
In the fourth part of the exercise, you backed up the integration node configuration information. Having
complete this exercise, you should be able to:
• Administer IBM Integration Bus components by using the IBM Integration Bus commands, IBM
Integration web user interface, and the IBM Integration API Exerciser
• Deploy IBM Integration Bus message flow application by using the IBM Integration Bus
commands, IBM Integration web user interface, and the IBM Integration API Exerciser
Student Exercises

Student Exercises
Exercise 5. Using file-based security to control

administration access

In this exercise, you use roles and file-based security to control administration
access to the IBM Integration web user interface, integration nodes, integration
servers, and message flows.

• Activate administration authority
• Use IBM Integration Bus file-based security to assign permissions for
integration nodes, integration servers, and message flows
Introduction
Administration security controls the rights of users to complete administrative
tasks for an integration node and its resources.
IBM Integration Bus V10 can control access to Integration node resources
through the IBM Integration web user interface. Different web users can have
different access rights across these functions, and access can be granted,
denied, or revoked.
The access authorities are defined against a set of user definitions that
represent the available security roles. A role is a set of security permissions
that control access to an integration node and its resources, and each web
user account is associated with a particular role. The permissions are checked
to determine a web user's authorization to complete tasks in the web user
interface or the REST application programming interface (API). Each web user
is then defined to use one or more of these security roles.
In this lab, you use an integration node that does not have a queue manager
that is associated with it (IIBNODE_NOQM) and create three user roles.
iibRoiei For integration node administration access, read-only
iibRoie2 For integration node administration access, read, write
iibRoie3 For integration administration access, all functions

In the second part of the exercise, you create web users and assign them to
one of the defined roles.
Finally, you explore the IBM Integration web user interface as each user.
Student Exercises
© Copyright IBM Corp. 2015 Exercise 5. Using file-based security to control administration 5-1
Requirements
• Lab files in the c: \iabfiies\Lab05-Sec directory

podrá reproducir o
Student Exercises
Exercise set up
_ 1. Check the status of file-based administration on the integration node IIBNODE_NOQM.
In an IBM Integration Console window, type:
Ensure that you see the line: Administration security = 'inactive'

If security is active on the integration node, deactivate it by typing the following commands:
mqsichangebroker IIBNODE_NOQM -s inactive mqsistart IIBNODE_NOQM
2. If not already open, open a web browser and start the IBM Integration web interface for
IIBNODEJMOQM.
You should see that you are currently logged in as a user this is named Default.
|45'IIBNODE_NOQM - IBM Integration - Internet Explorer
» |@http:/flocahostl441S/#bcoter/0 p_^j |*t 'ÿ IIBNODE_NOQM - IBM Integ.,.
x[_l
IBM Integration Welcome, Default ”■ 1
Filter Options... *=3

' IIBNODE.NOQM ~ 0 overview ^Statistics
▼ £= Servers ▼
▼ ^{servai] ▼
I llBNODE_NOQM - Integration Node
The Default user has full update access to all deployed integration node resources.
3. Click IIBNODE_NOQM to display its properties. In the Quick View properties, you should see
that Admin Security is off.
Filter Options... IIBNODE_NOQM - Integration Node
- ill illBNODEJJQQM: v Overview | •. Statistics

T • servers ▼
▼ Q.. serverl ▼
T Quick View
g Services g REST APIs g

Applications g Libraries
Node Name IIBNODE_NOQM Version 10000
Spared Libraries g Message
Admin Security Off
Flows ifj Subflows Q, Resources ▼ £
^Run Mode running Short Description Long Description
server2 ▼
4. Using the Integration web interface, deploy the file

C:\iabfiies\Lab05-sec\resources\AdminApp.barto the serverl integration server.
Student Exercises
After a brief pause, you should see that the Transformation_Map application deployed
successfully.
- J IIBNODE_NQQM ▼ T ¡S
servers -r - ^ serverl T (g
Services jg REST APIs ¡g
Applications
T Transformation_Map T ^5
Libraries ■r EG Message Flows
Transformation_Map T ^
Subflows T & iResou'ces
lnputX.MLSctiema.xsd ^
OurtputXMLSchema.xsd rg.
Transfornnation_Map.n(iap jj
Transfbrmation_MapJnputMessage„xiril gjl
References
If the integration node web administration HTTP listener is enabled, and security is not active
for the integration node, then any user can access the Integration web user interface and
control the integration node resources.
Part 1; Activate file-based security on the integration node

In this part of the exercise, you activate security for the IIBNODE_NOQM integration node.
_ 1. If an IBM Integration Console is not already open, start an Integration Console session with
Windows “Administrator” privileges.
_ a. Click Start > All Programs > IBM Integration Bus 10.0.0.0, right-click IBM Integration
Console 10.0.0.0, and then click Run as administrator.
Optionally, you can right-click the IBM Integration Console icon on the desktop and then
click Run as administrator.
_ b. Click Yes to run the IBM Integration Console with “Administrator” privileges.
_ 2. Security can be activated only when the integration node is shut down. Type the following
command to stop the integration node:
When you enter the mqsistop command, you should see that the IBM Integration web
interface page is unavailable with the message Real-time updates disabled.
_ 3. In the Integration Console, view the status of administration security and the current
authorization mode. Type:
mqsireportauthmode IIHNODE_NOQM

Student Exercises
You should see the following response:

Authorization mode = 'file'
As expected the administration security is returned as inactive. Also, this integration node was
created without a default queue manager, so default authorization mode is file.
4. Activate administration security on IIBNODE_NOQM. In the IBM Integration Console, type:
mqsicdiangeauthmode IIBNODE_NOQM -s active -m file

5. Restart the integration node. In the IBM Integration Console, type:

6. After a short pause, reload the IBM Integration web user interface by clicking the indicator in the
address page.
You are now presented with a sign-on screen because administrative security is now active.
IBM Integration
User ID:
Licensed Materials - Property of IBM Corp. Copyright by IBM Corp. and others) 2001, 2015.
IBM, and the IBM logo are trademarks of International Business Machines Corporation, registered in many jurisdictions
worldwide. Java and all Java-based marks and legos are trademarks or registered trademarks ctf Oracle and/or its affil
iates. Other prodluct or service names may be trademarks of IBM or ether companies. Microsoft: is a trademark of
Microsoft Corporation in the United States, other countries, or both.
Student Exercises
Part 2: Define administration roles and set file-based permissions.

In this part of the exercise, you create administration roles and grant administration authorities to
these roles. You reference these roles in the Integration Bus web user definitions that you create
later in this exercise.
Three levels of authorization are supported for IBM Integration Bus administration security: read, write,
and execute. You can assign permissions to a role (user) by specifying the type of permission followed
by a plus (+) to grant permissions, or a minus (-) to revoke permissions.
The following table shows the file-based authorities that are required for different types of users in this
exercise:
Role Authority
iibRolel Read (view resources)
iibRole2 Read, write (view resources,create integration servers, and modify settings)
iibRole3 Read, write, execute (start, stop, deploy, and modifying resources)
_ 1. Check whether there are any roles that are defined on the integration node. In the
Integration Console, type:
mqsireportfileauth IIBNODE_NOQM -1
You should see the response:

No defined roles are returned.

_ 2. Create the iibRolel role. In the Integration Console, type:
mqsichangefileauth IIBNODE_NOQM -r iibRolel -p read+
_ 3. Create the iibRole2 role. In the Integration Console, type:

mqsichangefileauth IIBNODE_NOQM -r iibRole2 -p read+,write+

mqsichangefileauth IIHNODE_NOQM -r iibRole3 -p all+
_ 5. Enter the command for displaying any defined roles again. In the Integration Console, type:
mqsireportfileauth IIHNODE_NOQM -1
The returned response should be as follows:

BIP8931I: Role = 'iibRolel', Resource = '', Permissions =
'read+,write-,execute-
BIP8931I: Role = 'iibRole2', Resource = '', Permissions =
'read!,write!,execute-
'read!,write!,execute!
_ 6. Define an Integration Bus web user that has read-only access.
This user can see deployed applications, but cannot control the status of these applications.

Student Exercises
In an Integration Console, type:

mqsiwebuseradmin IIBNODE_NOQM -c -u adminl -a passwOrd -r iibRolel
This command defines a new web user, adminl. The user has the security profile that the
iibRolel role defines. In this case, the user can view the integration node and any deployed
applications.
7. Define an Integration Bus web user that has read and write access.
This user can see deployed applications, and can change properties on the integration node and
integration server.
In the Integration Console, type:
mqsiwebuseradmin IIBNODE_NOQM -c -u admin2 -a passwOrd -r iibRole2
This command defines a new web user, admin2. This user has the security profile that the
iibRole2 role defines. In this case, the user can view the integration node and integration
servers, and edit their properties. This user can also view the deployed resources.
8. Define an Integration Bus web user for all access.
This user can see deployed applications, and can control all the integration node resources. In
the Integration Console, type:
iibRole3 role defines. In this case, the user can view the integration node, integration servers,
and any deployed applications. This user can also control all resources.
9. Display the defined web users. In the Integration Console, type:
The response should be similar to the following example:

BIP2837I: Web user 'adminl' is defined as having a role of
BIP2837I: Web user 'admin2' is defined as having a role of
mqsiwebuseradmin IIBNODE_NOQM -1
'iibRolel'.
'iibRole2'.
'iibRole3'.
Student Exercises
Part 3: Test the IBM Integration web interface with security

In this part of the exercise, you log in the IBM Integration web interface and test each user role.
_ 1. Log in to the IBM Integration web user interface as the admini user. The role for this user is
“read-only”.
In the IBM Integration browser window for the IIBNODE_NOQM integration node, login with
the user ID admini (password is password).
_ 2. Verify that Quick View properties for IIBNODE_NOQM show that Admin Security is On.
IIBMODE_NOQM ■ Integration Node

Q Overview |*v Statistics
▼ Quick View
Node Name IIBNQDE_NQQM
Version 1DD00
Admin Security On
Run Mods running
Short Description Long Description
_ 3. In the Integration web interface, expand the Servers folder.

You should see the available integration servers but you cannot view any of the resources.
_ 4. You gave the role iibRolel 'read' authorities at an integration node level. Setting integration
server authority provides more granular approach to authorization. You can authorize each
integration server with a separate command.
Also, with Integration Bus file-based authorization, you can change the roles' permissions
without a restart of the integration node; changes are recognized dynamically.
Change the integration server authorization so that the admini user with role iibRolel can
view the integration server resources. In the Integration Console, type:
mqsichangefileauth IIHNODE NOQM -e serverl -r iibRolel -p read+
The -e serverl parameter specifies the integration server, which means that now you are
applying the permissions at the integration server level.
_ 5. In the IBM Integration web interface, refresh the page.
_ 6. Expand the serverl integration server.
You can now view the resources on the integration server.
Although you can expand the serverl resources folders, you do not have permission to start,
stop, or other actions to the deployed artifacts.
_ 7. Try to create an integration server.
_ a. Click the arrow to the right of Servers and then click Create.

Filter Options...
IBMIIBNODE
b.
c. In Hoverthe NOQM
Integration
dialog
with your box,mouse type(5adminiserver
The integration server could not be created BIP2852
Overview
over the notification and then click OK.You should see that this
message. Welcome, adminl
Student Exercises
message is
IMPRESO POR: Jafert Frank Rabines Escorzaa hyperlink. Click
You<jrabinese@sunat.gob.pe>.
should see a messagethe link. that está
La impresión thedestinada
integration únicamente server paracoulduso personal not be created.
y privado. No se
podrá reproducir o
retransmitir ninguna parte de iftie intiera
Ôeste You
libro sinton
see
la æ'rvër
autorización cöufdnöt
a detailed be created
editor.5ÌP2352
message,
previa del ..............................................................................................................
Todo explaining
infractor será objetowhydethe attempt
acciones legales. to create the integration 1 11:34 x server
failed.
BIP2852E: The user '¡¡bRolef is not authorized to perform the requested operation 'create' against the object 'adminiserver of
type 'ExecutionGroup'. The user 'iibRolef'' needs to have Write' permission on the object 'adminiserver' of type 'ExecutorGroup'. The
user initiated a request to the integration node to complete an action on an object. The request was rejected by the integration node
because the user does not have the required authorization. Set up authorizations for Iris object to grant the required authority to this
user ID.
8. After exploring the options for the user adminl, log out of the IBM Integration web user interface.
Click the arrow next to the Welcome, adminl banner and then click Log Out.
Welcome, adminl ”
Edit Profile Log
Out
9. Log in to the IBM Integration web user interface as the admin2 user, which is the user with read
and write permissions. The password is password.
This user can view resources, edit integration node properties, and create Integration servers.
10. Expand Servers.
You should see that although you can view the available servers, the role to which admin2 is
associated is not authorized to access the integration server. The role for admin2 has read and
write access for the integration node, but not for any integration servers.
11. Set read and write access to the server! integration server for role iibRole2. In the Integration
Console, type:
mqsichangefileauth IIBNODE NOQM -e serverl -r iibRole2 -p read+,write+
This command allows this role to view the resources on the serverl integration server.
podrá reproducir o
Student Exercises
_ 12. In the IBM Integration web user interface, refresh the login for admin2 (press F5 or click
Refresh).
_ 13. Click the server! integration server in the Integration web interface. You now see an Edit
icon on the properties view (which was not available for user admini).
Welcome, adminZ
Filter Options...
Q Overview [ry Resource Statistics [*y Statistics
server2
► Operational Policy
► g Data
▼ Quick View
► Security Integration Server Name server!
► ^ Monitoring
Run Mode running
UUID 13fca595-530f-418b-be00-a1 b85170eeb8
Running true
Short Description
Long Description
IBM Integration
serverl - Integration Server

_ 14. Click Edit.
The table with the properties for the serverl integration server should open. The user admin2
should now have the authority to change the integration server properties.
_ 15. You do not change the integration server properties in this exercise. When you are done
reviewing the properties, click Cancel.
_ 16. The user admin2 has 'write' authorities, which allows the user to create an integration server
on the integration node.
Try to create an integration server that is named admin2server.
This action should succeed because admin2 has the required authorization.
_ 17. Even though admin2 can create the integration server, the administrator must authorize the
role to which admin2 is associated to allow the user to control the new integration server.
In the Integration Console, type;
mqsichangefileauth IIBNODE_NOQM -e admin2server -r iibRole2 -p reach-,write+
This command sets the permissions for this role on the admin2server integration server as
read and write.
_ 18. Refresh the IBM Integration web user interface. If necessary, log in as admin2 again.
Now, the web user can view the new integration server and its resources (although no
resources are currently deployed). The user can also edit the integration server properties.
_ 19. Log out of the IBM Integration web user interface.
_ 20. Log in to the IBM Integration web user interface as admin3.

podrá reproducir o
Student Exercises
This user has full control for the integration node resources, which includes stopping, starting,
and deploying applications and starting and stopping statistics.
21. Although admin3 has full authorities for the resources on the integration node, the
administrator must provide extra permissions to iibRole3 so that the user can manage the
integration server.
mqsichangefileauth IIBNODE_NOQM -e serverl -r iibRole3 -p all+
22. Refresh the Integration web interface and then expand the Servers > serverl.
You should see that now there is an arrow on the right side of serverl, which was not there for
admini and admin2 web users.
Click the arrow to display the menu.
You should see a menu that contains all the administration tasks that web user admin3 can
complete.
Overview
- ^ IIBNODE_NOQM -
► serverl ^ server2
admin2se fla <g=. serverl
Operational F Data Start
►Security m
Start All Application Types Start
►Monitoring Al I Message Flows
► Stop
► Stop All Application Types Stop
All Message Flows
Rename
L
Delete All n
Delete
Deploy
Start recording
Stop recording
Statistics on
Statistics off
Resource statistics on
Resource statistics off
¡g! Servers <*■

23. Click Stop to stop the integration server.
After a few seconds you should see that the integration server stopped, as indicated by the down
pointing red arrow.
▼ Servers ▼
herverl jVj ^
servetZ
^ admin2server
podrá reproducir o
Student Exercises
24. Expand the server! menu again and then click Start to start the integration server.
25. When the integration server starts, expand the Applications group and then click
Transformation_Map.
26. Click Stop on the Transformation_Map menu.
- <3 I1BN0DE_N0QM -r Overview
■» (= Servers ▼
"■ served ▼
¿5 Services
- Quick View
0 REST APIs
- çjSJ Applications Integrati
► ^1 Transfer mation_Map
Libraries 55 Tran sforma tior_Map
Shared Libraries Start
The application and all its flows are stopped,
g Message Flows Stop
as the down pointing red SubHows Delete arrows indicated.
27. Delete the Resources Statistics on
server2 Statistics off

Transformation_Map application.
28. Log out user as user admin3.
Exercise clean up
_ 1. Deactivate administration security on the IIBNODE_NOQM integration node.
_ 2. Delete the integration server admin2server.
mqsideleteexecutiongroup IIBNODE_NOQM -e admin2server
End of exercise

Student Exercises

In the first part of this exercise, you activated file-based security and then created three user roles.
In the second part of this exercise, created web users and assigned them to one of the defined roles.
In the third part of this exercise, you explored the IBM Integration web user interface as each user and
configured security authorizations for integration servers.
• Use IBM Integration Bus file-based security to assign permissions for integration nodes,
integration servers, and message flows
Student Exercises

Student Exercises
Exercise 6. Using queue-based security to control


In this exercise, you use the IBM Integration Bus security queues on IBM MQ
to set and test IBM Integration Bus access control for the integration nodes,
integration servers, and message flows.

• Activate queue-based administration authority
• Use the IBM Integration Bus security queues on IBM MQ to assign
permissions for integration nodes, integration servers, and message
flows
Introduction
IBM Integration Bus can use a special set of IBM MQ SYSTEM.BROKER
queues to control access to each entity that must be secured in terms of
administrative access. Each administrative action, such as creating an
integration server, and deploying or stopping a message flow, is mapped to
one of three categories; read, write, or run. These categories are mapped to
IBM MQ security properties as follows:
• Inquire maps to Read
• Put maps to Write
• Set maps to Run
One or more of the IBM MQ security permissions are set on a particular queue
to control access to the object that queue represents; an integration node or an
integration server. This design uses a familiar, already present mechanism
(queue security) and provides excellent granularity and flexibility.
In the first part of this exercise, you set up user and group authorities for a non-
privileged Windows user (No_Auth_iD). That same user ID is used in testing
the next parts of this lab.
In the second part of the exercise, you activate IBM Integration Bus security.
You then use the same non-privileged user ID (No Auth iD) to show that the
user cannot use any functions in the IBM Integration Bus environment.
In the third part of the exercise, IBM Integration Bus security is activated. The
same non-privileged user ID is used to demonstrate that the user cannot use
Student Exercises
any functions in the Integration Bus environment until authorization is
© Copyright IBM Corp. 2015 Exercise 6. Using queue-based security to control administration 6-1
configured on the IBM MQ authorization queues.
r / Note ---------------------------------------------------------------------------------------------- ^
This exercise uses the IBM Integration API Exerciser to test queue-based security. It is important that
you understand that all Integration Bus applications are subject to security authentication when
administrative security is active. Those applications include the IBM Integration Toolkit and the IBM
V ______________________________________________________________________________ J
Requirements
• IBM Integration Bus V10 and IBM MQ V8
• The IIBNODE_WITHQM integration node and the IIBMQ IBM MQ manager
that were created in Exercise 2
• Lab files in the c : \iabfiies\Lab06-QSec directory
• Microsoft Windows user that is named No_Auth_iD and group that is
named Securityjrest with IBM Integration Bus permissions as shown in
Part 1 of the exercise

Student Exercises
Exercise set up
_ 1. To effectively test administrative security, you must run under a different user ID than the
administrator ID iibadmin because it has full authority over the integration node environment.
Logging out of that account and logging in as another user is not a good solution on Windows
because that starts a different or unique configuration of installed software. The solution is to
use the Windows option to Run as different user. With this option, you can run a program
with different permissions than the currently logged-on user ID provides.
In this exercise, you use the Run as different user option in this lab to run the IBM
Integration API Exerciser under the No_Auth_iD user ID. The No_Auth_iD is a member of the
group security_Test. The No_Auth_ID user ID is not a member of the mqbrkrs or mqm
groups.
Verify that you have a user ID that is named No Auth iD user ID and that this user is member
of the group security_Test.
_ a. Start the Windows Computer Management application by clicking Start >
Administrative Tools > Computer Management.
_ b. In the Computer Management window, expand Local Users and Groups.
_ c. Click Users. A list of all users and groups is displayed in the right pane.
_ d. In the right pane, double-click the user ID No_Auth_iD.
_ e. Click the Member of tab and review the groups to which the user ID belongs. Notice that
the user ID is not a member of the mqbrkrs, mqm, or Administrators groups.
_ f. Click Cancel to exit without saving any changes to the user ID.
P Computer Management
File Action View Help
_ g. Close the Computer Management window.
'■1- Computer Management Name Full Description

(Local) B ' System Tools E 0 Administrat
Name
h o A u t h i D Properties irmi
Task Scheduler E I Event Viewer or ^4 Guest
E ;■/ Shared Folders B iP Local iibadmin Remote Desktop Services Profile Personal Virtual Desktop Dlal-ln
Users and Groups 3 Users MUSP._MQAD General Member Of j Profile | Environment | Sessions | Remote control
Groups No_Auth_ID
E 'V Performance Member of:
A Device Manager E ^
Securlty_Tes
Storage
:: t jfc Users
- Disk Management E
Student Exercises
_ 2. In this exercise, you use the IIBNODE_WITHQM integration node with the default queue
manager IIBQM that were created in Exercise 2.
Verify that the IIBNODE_WITHQM integration node and IIBQM are created and running.
_ a. Start IBM MQ Explorer if it is not already running. Verify that the queue manager IIBQM
is defined and running.
_ b. In an IBM Integration Console, type the following command to verify that the integration
node IIBNODE_WITHQM is running.
mqsilist IIBNODE_WITHQM
_ 3. Start the IBM Integration web interface for IIBNODE_WITHQM.

If you do not know the HTTP Connector port for the web interface, type the following
command in the Integration Console.
mqsireportproperties IIBNODE_WITHQM -b webadmin -o HTTPConnector -a
Part 1: Set IBM MQ permissions for users

If you are using any Integration Bus functions that require access to IBM MQ, permissions are
required to enable users to connect to the integration node.
In this part of this exercise, you set up IBM MQ permissions for a non-administrator users
(No_Auth_iD) that is a member of the security_Test group. That same user ID is used in testing the
next parts of this exercise.
_ 1. In IBM MQ Explorer, grant the group Security Test Connect and Inquire privileges for
the integration node queue manager IIBQM.
_ a. Under the Queue Managers folder, right-click IIBQM and then click Object Authorities
> Manage Queue Manager Authority Records. The Manage Authority Records window
is displayed.
jl IIBQM - Manage Authority Records
Groups user;
Name Alternate user authority Change Connect Delete Display Inquire Set
|j|mqbfcs§WS200TCS ■V V1 V
(¡E) * ✓ V V ✓ ✓ *•
mqrn(ô)W520Q8R2!i64
b. Review the existing groups and users by clicking the Groups tab and then the Users tab.
The only two groups that you see are mqm and mqbrkrs.
The only user that you see is iibadmin.
c. On the Groups tab, click New (at the bottom of the window). The New Authorities dialog
box is displayed.
d. For Entity name, type: Security_Test
Student Exercises
e. Under the MQI authorities options, click Connect and Inquire.

f. Click OK, and then click OK again on the result dialog box.
The Security_Test group is displayed in the Groups list with Connect and Inquire
authority.
g. Close the Manage Authority Records window.
Student Exercises
Part 2: Test the default unsecured environment

In this part of the exercise, you verify that permissions you configured in Part 1 of this exercise are
correct and that the No_Auth_iD user can successfully connect to the IIBNODE_WITHQM integration
node.
_ 1. So that you can run as another user without having to log off and back on, use the Run as
different user option in Windows and start the Integration API Exerciser.
__ a. In Windows Explorer, browse to the C:\Program
Files\IBM\IIB\10.0.0.0\server\sample\IntegrationAPI directory.
b. While holding down the Shift key, right-click the StartlntegrationAPIExercise.bat file and
then click Run as different user.
Name
5/18/2015 7:07 AM
IntegrationAPISamples.jar U
3/16/2015 9:44 PM
5tartBrokerInfo.bat
3/16/2015 9:44 PM
5tartDeployBAR.bat
3/16/2015 9:44 PM
Date modified
lapi
__ c. A login window opens and you are prompted to enter the user ID and password.
For the user ID, type: No_Auth_iD
For the password, type: webisphere
After a few moments, the Integration API Exerciser starts.
2. Adjust the timeout values for the Integration API Exerciser.
__ a. Click File > Set Timeout Characteristics.
__ b. Modify the timeout values as follows:
- Set Maximum wait time for BAR deployment to 60
- Set Maximum wait time for integration server creation to 60
- Set Maximum wait time for other requests to 2 0
Set Timeout Characteristics... IZ
Wait for the integration node to fully complete requests before returning W Maximum wait 3
time for BAR deployment (seconds) ||60
Maximum wait time for integration server creation (seconds) [&u Maximum
wait time for other requests (seconds) l20f

Maximum wait time for policy requests (seconds) |30
Submit ] Cancel

Student Exercises
__c. Click Submit.

3. The next steps assume that the IIBNODE_WITHQM integration node is running.
If the integration node IIBNODE_WITHQM is not running, start it now.
4. The Integration API Exerciser is running under No_Auth_iD and gets all permissions from the
settings for that user and its group, which is security_Test.
Connect the Integration API Exerciser to the integration node.
__a. Right-click Right-click to connection and then click Connect to Remote Integration
node
__b. Specify the connection values.
• For the Host Name, type: 127.0.0.1
• For the Port, type: 4416
• For the User Name, type: No_Auth_iD
• For the Password, type: webisphere
__c. Click Submit.

After a few seconds, the Integration API Exerciser connects to the integration node and
displays the integration node properties.
5. Using the Integration API Exerciser, verify that Administrative Security is turned off in
IIBNODE_WITHQM.
__a. With the IIBNODE_WITHQM integration node selected in the Integration API Exerciser
navigator (left pane), scroll to the bottom of the data window (right pane).
Student Exercises
b. Verify that isAdminSecurityEnabled() shows false, indicating that administrative security

is not enabled.
I® IBM Integration API (CMP) Enerciser
File View Scripting
■ fk> jHB[\IODE_WITHQM BrokerProxy Method Result

1 . =, server 1 getResourceTypeStatisticsPropertyNames("SOAPInput") [InboundMessagesTotal, RepliesSentTotal^ Inbc
I . 'p Administration Log getResourceTypeStatisticsPropertyNames("5ecurity") [TotalOperations, TotalSuccessfulOperations, Ti
; . Administration Queue getResourceTypeStatisticsPropertyNames("5ockets") [TotalSockets, TotalMessages, TotalData5ent_K
+ -{¿p Configurable Services getResourceTypeStatisticsPropertyNames("TCPIPClientNo... [OpenConnections, ClosedConnections, Messag
getResourceType5tatisticsPropertyNames("T CPIPServerN,.. [OpenConnectionSj ClosedConnectionSj Messag
getSecurityCachePropertyNamesO
SecurityCache/cacheSweepInterval 300
SecurityCache/cacheTimeout
60
SecurityCache/uuid SecurityCache
getShortDescriptionO
getTimeOfLastCompletionCodeO Oct 14, 2015 8:46:22 AM

getTimeOfLastUpdate() Oct 14, 2015 8:46:22 AM
getTypeO Broker
getUUIDO 395c52f4-9fbd-47f9-90f4-b58ad91c4072
hasBeenPopulatedByBrokerQ true
1. _ _
1 -------------------------- !---------- --------------------------------------------
1 : AdminSecurityEnabledQ false
||j|''u ........ . i'-1
When the Integration API Exerciser is connected to the integration node, information about the
integration node is displayed under the integration node in the navigation pane.
The display of the integration server server! in the Integration API Exerciser implies that
some level of access is granted to the user. In this case, the No_Auth_iD user has “read”
access to the integration node.
_ 6. Attempt to deploy a BAR as the No_Auth_iD user.
_ a. Click the server! integration server in the Integration API Exerciser navigator.
_ b. Right-click serveii and then click Deploy BAR from the menu.
r / Note -------------------------------------------------------------------------------------------- ^
Be sure to select an entity before right-clicking it in the IBM Integration API Exerciser.
V ______________________________________________________________________________ V
_ c. Browse to the C: \iabfiies\Lab06-QSec\resources directory, select

Admin_Security_Testl .bar, and then click Open.

Student Exercises
The request succeeds, as indicated in the status log in the bottom pane of the IBM
Integration API Exerciser.
------------------------------- 3
D e p I o y R e s u 11. g e tD e p I o y Sta rtTi rn e ( ) = Oct 14, 2015 10:06:32 AM
DeployResultgetDeployStopTimeQ = Oct 14, 2015 10:06:45 AM (12s)
DeployResult.getDeployResponsesO : BIP2871I: The request made by user 'SYSTEM[Default]' to 'deploy'
'C:\labfiles\Lab06-QSec\resources\Admin_Secunty_Testl.bar' of type 'BAR' on parent'serverl' of type 'ExecutlonGroup'
'COMPLETE',
' SUCCESS: The integration node completed the request.
<—- iapi.exerciser. ClassTesterForExecutionGroupProxy. testDeployBAR
H ______________________________________________________________________________________________ 1 -
►l~
7. Determine whether this user can stop a message flow.

__ a. Fully expand the server! integration server in the navigator.
b. Right-click Admin_securityi_MsgFiow. cmf and click Stop from the menu.
c. Verify that the message flow stopped by selecting the message flow and checking the
runMode status, which should now be set to stopped.
1 & IBM Integration API (CMP) EHercisi -r n
File View Scripting
ft IIBNODE_WITHQM E serverl MessageFlowProxy Method Result

traceLevel none
j A- HI Admin_5ecurity 1 J'lsgFlow, additionallnstances 0
cmf startMode Maintained
; .F Administration Log
! .IJ Administration Queue coordinated! ransaction no
É-& Configurable Services commitlnterval 0
version
i-L-i r- --- :L... «—
1 runMode [stopped
k ......... y IQI3G
getCommitCountO 1
getCommitlntervalQ 0
getConf IguratlonObjectT ype() <Message Flow>
getConfigurationObjectTypeOfParentO Execution Group >
getCoordinatedT ransactlonQ false
getDeployPropertiesO
modifyTime 2009-06-18 16:36:40,000 -0700
deployTime 2015-10-14 10:06:32.925 -0700
barFileName C:\labfiles\Lab06-
Q5ec\resources\Admin_5ecurity_Testl,bar
_ 8. Restart the flow by right-clicking Admin_Securityi_MsgFiow.cmf and clicking Start from

the menu.
_ 9. Verify that the flow is started by reviewing the status log. The runMode status should now
be set to running.
_ 10. Disconnect the Integration API Exerciser from the integration node by right-clicking
IIBNODE_WITHQM in the navigation pane and clicking Disconnect.
This step completes the testing in the unsecured environment. You saw that, given a minimum set of
authorizations, the No Auth iD has access to the integration node.
Do not exit from the IBM Integration API Exerciser. You use it again in the next part of the exercise.
Student Exercises
Part 3: Activate administration security and test the secured

environment
In this part of the lab, IBM Integration Bus security is activated, and the same non-privileged user ID is
used to demonstrate that the user cannot use any functions in the IBM Integration Bus environment.
_ 1. Activate integration node administration security.
_ a. Start an IBM Integration Console session as the administrator.
_ b. Stop the integration node so that you can make the necessary configuration change.
Type:
mqsistop IIBNODE_WITHQM
_ c. View the status of administration security and the current authorization mode. Type:
mqsireportauthmode IIBNODE_WITHQM

BIP8930I: Integration node name 'IIBNODE_WITHQM'
Authorization mode = 'mq'
As expected the administration security is returned as inactive. Also, this integration
node was created with a default queue manager, so default authorization mode is mq.
_ d. Activate administration security on IIBNODE_WITHQM. Type:
mqsichangeauthmode IIBNODE_WITHQM -s active -m mq
_ e. Restart the integration node. Type:

_ 2. When you activate administration security, the Integration web interface requires a user
name and password to log in.
_ a. Enable the Integration web interface for the administration user iibadmin. In the
mqsiwebuseradmin IIBNODE_WITHQM -c -u iibadmin -a weblsphere -r iibadmin
_ b. Log in to the Integration web interface with the administrator credentials.
For the user ID, type: iibadmin For the password, type: weblsphere
_ 3. You must also enable the Integration web interface for the No_Auth_ID so that this user can
connect to the integration nodes port.
mqsiwebuseradmin IIBNODE_WITHQM -c -u No_Auth_ID -a weblsphere -r No_Auth_ID

Student Exercises
4. Verify that the authorization queues exist on the queue manager.

_ a. In IBM MQ Explorer, click Queues under the IIBQM queue manager to display the
Queues content view.
_ b. In the Queues content view, click the Show System Object icon to display the SYSTEM
queues.
_ c. Confirm that the following authorization queues exist:
• SYSTEM.BROKER.AUTH (the authorization queue for the integration node)
• SYSTEM.BROKER.AUTH.serverl (the authorization queue for integration server)
0| MQ Explorer - Content £3
Queues
i Queue name Queue type Open Input count I Open output count
H SYSTEM, BROKER, AGGR. REQUEST Local 0 0
IM) SYSTEM.BROKER.AGGR.TIMEOUT Local 0 0
l_l cwrTrM on/M/cn A.--vn i 1__ 1 n n
HI SYSTEM. BROKER.AUTH
U SYSTEM. BROKER, AUTH, server 1
Local
Allas
0 o
r
i
4J i Ï 5 1 tn, BKUK.EK, LU, mUULL Humei
l
5. The SYSTEM.BROKER.AUTH queue controls authorization for the integration. Give the
group Securityjrest “Inquire” authority on the queue so that member of that group can
view the integration node properties.
_ a. In the IBM MQ Explorer, right-click the SYSTEM.BROKER.AUTH queue and then click
Object Authorities > Manage Authority Records from the menu.
_ b. Expand Specific Profiles and select SYSTEM.BROKER.AUTH.
Securityjrest is not displayed in the profiles. It does not have permissions on the
SYSTEM.BROKER.AUTH queue. The group must be defined to the queue and it must have
Read (“inquire”) authority.
_ c. Click the Groups tab, and then click New.
_ d. For the Entity name, type: Securityjrest
_ e. Under the MQI authorities options, click Inquire.
_ f. Click OK, and then click OK again on the result window.
The Securityjrest group is displayed in the Groups list with Inquire authority.
Student Exercises
_ g. Click Close to close the Manage Authority Records window.

6. In the IBM Integration API Exerciser, connect to IIBNODE_WITHQM.
With the security changes, the queue and integration server shows in the navigation pane.
You can see the integration server server! but it has a lock icon next to it. You cannot see the
integration server properties or the message flow that is running on the server. Granting
authority to the integration node did not grant authority to the integration servers contained
within it.
7. Click the server! integration server. You should see the BIP2852 error message in the Result
field that indicates the user is not authorized.
To list the contents of an integration server, the user ID must have Read (“inquire”) access to
the integration server.
<6^ IBM Integration API (CMP) Exerciser
File View Scripting
ExecutionGroupProxy Method Result

serverl getConf igurationObjectT ype() <Execution Group>
39 getConfigurationObjectTypeOfParentQ <Broker>
Configurable Services [1] ¡3IP2852E: The user 'No_Auth_ID' is not authorized to perforin the requested operation
View' |
get Nam ef)
getTimeOfLastCompletionCode() Oct 14, 2015 11:19:46 AM
getTimeOfLastUpdateQ Oct 14, 2015 11:19:46 AM
getType ExecutionGroup
O 4930952e-6d74-4604-8165-d 1 da806cf
getUUIDQ cd5
ha s 3 e e n
P o p u la t ed B y B r o he r ( ) hasBeenRestrictedByBroker()
_ a. In IBM MQ Explorer, Queues content view, right-click

SYSTEM.BROKER.AUTH.serverl queue and then click Object Authorities > Manage
Authority Records from the menu.
_ b. Expand Specific Profiles and then click SYSTEM.BROKER.AUTH.serverl.
_ d. Enter Securityjrest as the Entity name.
_ e. Under the MQI authorities options, select Inquire.
_ f. Click OK, and then click OK again on the result dialog box.
_ g. Click Close to close the Manage Authority Records dialog box.
8. In the Integration API Exerciser, right-click the server! integration server and then click
Refresh from the menu.
You now see the properties of the server! integration server. You can also see the message
flow that is running on the integration server.
9. Try to deploy a BAR file to serverl from the Integration API Exerciser.
_ a. Right-click the serverl integration server and click Deploy BAR from the menu.
_ b. Go to the c: \iabfiies\Lab04-QSec\resources directory and then select
Admin_Security_Test2.bar.

Student Exercises
_ c. The deployment fails. The message in the Integration API Exerciser indicates that the
user does not have authorization and must have “write” permissions on the integration
server.
The ability to deploy requires Write (Put) permission on the integration server.
10. Add Write (Put) permissions for the Securityjrest group on the integration server
SYSTEM.BROKER.AUTH.serverl queue.
_ a. Expand Specific Profiles and then select SYSTEM.BROKER.AUTH.serverl.
_ b. Click the Groups tab, and then select the Security_Test row in the table.
_ c. Click Edit.
_ d. Under the MQI authorities options, select Put.
The Security Test group now has both Inquire (Read) and Put (Write) permissions.
_ e. Click OK, and then click OK again on the result dialog box.
_ f. Close the Manage Authority Records dialog box.
11. Try to deploy the Admin_security_Test2 .bar in the Integration API Exerciser.
Verify that the flow was successfully deployed by reviewing the messages in the Integration
API Exerciser status log. You should also see the message flow in the Integration API
Exerciser navigator pane.
Student Exercises
ft IBM Integration API (CMP) Exerciser

File View Scripting
=¡> PBNODE_WITHQM 1 ExecutionGroupProxy Method

serverl getAdvancedPropertiesO
; f -mn Admin_5ecurityl_MsgFlôw.cmf ; i-— processld 5464
HHU Adrnin_5ecurity2_MsgFlow.cmf injectionMode Disabled
;r Homimstration Log soapNodesUseEmbeddedListener true

;U Administration Queue traceLevel none
El- Configurable Services threadLocalProxyNameManagers false
consoleMode off
httpNodesUseEmbeddedListener false
activellserExitList
inactivellserExitList
traceNodeLevel on
userTraceLevel none
getApplications(null)
getBasicPropertiesO
label serverl
runMode running
uuid 493B952e-6d74-4684-8165-dl da806cfcd5
shortDesc
DeployResult.getCompletionCode() = success DeployResult.getDeployStartTimeQ = Oct 14, 2015 11:49:53 AM

DeployResult.getDeployStopTime() = Oct 14, 2015 11:50:10 AM (17s) DeployResult.getDeployResponses() :
BIP2871I: The request made by user 'No_Auth_IC C:\labfiles\Lab06-QSec\resources\Admin_Security_Test2.bar'
of type 'BAR' on parent 'serverl' of type 'E
SUCCESS: The integration node completed the request.
12. Stop the Admin_Security2_MsgFiow. cmf message flow from the Integration API Exerciser.
Right-click Adminj3ecurity2_MsgFiow.cmf in the Integration API Exerciser and then click Stop.
The stop command fails because the security_Test group does not have Set (Run) authority
on the integration server, which is required for a “stop” or “start” command.
13. In IBM MQ Explorer, modify the permissions for the Security_Test group to include Set (Run)
permissions on the SYSTEM.BROKER.AUTH.serverl queue.
Review the substeps in step 10 if you need help. This time, select Set authority in addition to
the authorities that are already set.
14. In the Integration API Exerciser, try to stop the message flow now that the permissions are
modified.

Student Exercises
15. To verify that the Admin_Security2_MsgFiow.cmf message flow stopped, scroll to the last entry in
the MessageFlowProxy Method list. The last entry in the Result column is the isRunning
method with a result of false, which indicates that the flow is stopped.
If, IBM Integration API (CMP) Exerciser
File View Scripting

#i> IIBNOOE_WITHQM - ser veri traceLevel none
! hü Admin_Securityl_MsgFlow,cmf i additionallnstances 0
nÌl|Admin_5ecurity2_MsgFlow,cmf startMode Maintained
j-ït1' Administration Log j-U coordinatedTransaction no
Administration Queue 0-Q, commitlnterval 0
Configurable Services version
I.L.I
runMode stopped
isRunnina false
getCommitCount() 1
getCommitInterval()
0
getConfigurationObjectT ype() <Message Flows
getConfigurationObjectTypeOfParent() «Execution Groups
getCoordinatedT ransaction() false
modifyTime 2009-06-18 15:58:08,000 -0700
deployTime 2015-10-14 11:49:53,819-0700
QSec\resources\Admin_Security_Test2.bar
16. Attempt to create an integration server in the Integration API Exerciser.

__ a. Right-click IIBNODE_WITHQM and then click Create integration server from the
menu.
__ b. Enter Admin Security for the New integration server name and then click Submit.
The requested action fails because the Security_Test group does not have Write (Put)
permission on the integration node authorization queue.
17. In IBM MQ Explorer, add Write (Put) permissions to the SYSTEM.BROKER.AUTH queue
for Security_Test.
When you complete this step, the security_Test group should have both Read (Inquire) and
Write (Put) permissions.
18. Attempt to add the Admin_Security integration server to IIBNODE_WITHQM again. Refer to
step 16 if necessary.
This time, the command is successful.
19. Attempt to deploy the Admin_Security_Test2 .bar file that is in the C:\iabfiies\Lab06-
QSec\resources directory to the Admin_Security integration server.
The deployment fails because the group securityjrest does not have sufficient authority to
deploy to the new integration server.
The process of creating the integration server automatically creates the queue
SYSTEM.BROKER.AUTH.Admin_Security, but it does not automatically create the required
authorities.
Student Exercises
§ MQ Explorer - Content £3
Queues
Queue name Queue type | Open Input count | Open output count
y SYSTEM.BROKER, AGGR,REQUEST Bl Local
SYSTEM.BROKER,AGGR,TIMEOUT Local
y SYSTEM.BROKER,AGGR,UNKNOWN Local
y SYSTEM.BROKER,AUTH Local
Ì I SYSTEM. BROKER, AUTH, Admin_Secunty I
H SYSTEM. BROKER, AUTH, server 1 HIM
[%J SYSTEM.BROKER,CD.MODEL Model
Allas
The deployment operation requires that you add Put (Write) authority on the
SYSTEM.BROKER.AUTH.Admin_Security queue for the Security Test group.
Exercise clean up
_ 1. In the IBM Integration API Exerciser, disconnect from the integration node by right-clicking
IIBNODE_WITHQM and then clicking Disconnect.
_ 3. From the IBM Integration web interface:
_ a. Delete the integration server Admin_Security.
_ b. Stop all message flow on the serverl integration server.
_ c. Delete all flows from the serverl integration server.
_ 4. Disable administrative security on IIBNODE_WITHQM from a command in the IBM
Integration Console.
_ a. Stop the integration node and verify that it is stopped. Type:
_ b. Disable administration security. Type:

mqsichangeauthmode IIBNODE_WITHQM -s inactive -m mq
_ c. Restart the integration node. Type:

End of exercise

Student Exercises

In the first part of this exercise, you set up user and group authorities for a non-privileged Windows
user (No Auth ID).
In the second part of the exercise, you added basic authorizations for a non-administrative user.
In the third part of the exercise, you activated Integration Bus administration security. The same non-
privileged user ID was used to demonstrate that the user cannot use any functions in the Integration
Bus environment until authorization was configured on the IBM MQ authorization queues.
• Use the IBM Integration Bus security queues on IBM MQ to assign permissions for integration
nodes, integration servers, and message flows
Student Exercises

podrá reproducir o
Student Exercises
Exercise 7. Implementing web services and web

services security

In this exercise, you configure the integration node runtime environment to
support web services. You use the supplied tools to set up a web service that
can accept information from, or deliver it to, a transport with secure HTTP
(HTTPS).

• Configure the integration node HTTP listener
• Implement message flows that provide and use web services
• Implement a web service message flow application that uses HTTPS for
secure transport
Introduction
A web service is a callable program that is at a web location, and can create
unlimited extensions to the classic remote procedure call (RPC) paradigm. As
standards stabilize, web services of all types are becoming common.
In the first part of this exercise, you configure an integration node HTTP
listener.
In the second part of this exercise, you review the web services messages flow
and build and deploy a BAR file.
In the third part of this exercise, you build the BAR file and then use the
Integration Toolkit BAR file editor to modify the configurable properties.
In the fourth part of this exercise, you test the web service.
In the fifth part of this exercise, you implement SSL for the web service
application.
Required materials
• The IIBNODE_WITHQM integration node and the IIBQM queue manager
© Copyright IBM Corp. 2015 Exercise 7. Implementing web services and web services security 7-1
Student Exercises
• Lab files in the C:\iabfiies\Lab07-webSvc directory

podrá reproducir o
Student Exercises
Exercise set up
_ 1. If it is not already open, open IBM Integration Toolkit.
_ 2. To prevent any conflicts with any existing message flow applications, switch to a new
workspace that is named C:\workspace\webSvc.
_ a. In the Integration Toolkit, click File > Switch Workspace > Other.
_ b. For the Workspace, type: C:\workspace\webSvc
_ c. Click OK. After a brief pause, the IBM Integration Toolkit restarts in the new workspace.
_ d. Close the Welcome window to go to the Integration Development perspective.
_ 3. Import an existing project that contains the message flows for this exercise.
_ a. From the menu bar, click File > Import. The Import selection dialog box is displayed.
_ b. Expand General.
_ c. Select Existing Projects into Workspace, and then click Next.
_ d. To the right of Select root directory, click Browse, browse to the
C:\labfiles\Lab07-WebSvc\resources\WebSvc folder, and then click OK.
_ e. Ensure that websvc is selected in the Projects window.

_ f. Select the Copy projects into workspace option.
g. Click Finish. The WebSvc project is imported into the Independent Resources folder in the
Application Development view.
Student Exercises
_ 4. In the IBM Integration Toolkit Integration Nodes view, verify that the integration node
IIBNODE_WITHQM is running.
_ 5. Create the local queues (PINGJN, PING_OUT, and FAILURE) that are required for this
exercise on the IIBQM queue manager.
_ a. In an IBM Integration Console, type the following command:
runmqsc IIBQM < C:\labfiles\Lab07-WebSvc\Q_Defs.mqsc
_ b. Open IBM MQ Explorer and verify that the local queues were created on the IIBQM
queue manager.
Part 1: Configure the integration node HTTP listener

In this part of the exercise, you configure the integration node HTTP listener.
The integration node HTTP listener requires that you use an integration node that is configured with a
default queue manager. In this exercise, you use the integration node IIBNODE_WITHQM that you
created in Exercise 2. It is defined to use the IIBQM queue manager as its default queue manager.
_ 1. In this exercise, you use port 7085 for the integration node HTTP listener. Verify that port
7085 is not already in use by another application.
_ a. From a Windows command prompt, type the following command to get the network
information and save it to a text file. Type:
netstat -an > C:\labfiles\network.txt
_ b. Open the text file in Notepad and examine the list of assigned and active port numbers.
Verify that port number 7085 is not already in use.
_ 2. Configure the integration node HTTP listener to use port 7085.
_ a. Check the current port for the HTTP listener on the integration node. In the IBM
mqsireportprqperties IIBNODE_WITHQM -b httplistener -o HTTPConnector -a
The results should show that the current port is 7800.

_ b. Change the port for the integration node listener to 7085. In the IBM Integration
Console, type:
mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPConnector -n port -v
7085
_ c. Verify that the HTTPConnector port is now 7085. In the IBM Integration Console, type:
The results should show that the current port is now 7085.
_ 3. For the changes to take effect, the integration node must be stopped and restarted after
entering the mqsichangeproperties command.
_ a. Stop the integration node. In the Integration Console, type:

Student Exercises
After a few moments, a confirmation message is displayed, b.
podrá reproducir o Restart the integration node. In the Integration Console, type:
After
Note a few moments, a confirmation message is displayed.
'A
The mqsistop command waits for a signal that the integration node was shut down successfully before
it displays the confirmation message.
The mqsistart command returns a confirmation message when you enter start commands, but it does
not wait for the integration node and its components to signal that they are ready. As a result, if an error
occurs during start, it is possible for the mqsistart confirmation message to show even though the
components did not start.
Always check the status of the integration node and its components to ensure that they started
correctly.
Part 2: Review the message flows

_ 1. In the IBM Integration Toolkit, review the CallWebSvc message flow.
_ a. In the Application Development view, expand Independent Resources > WebSvc >
Flows.
_ b. Double-click CailWebSvc.msgflow to open it in the Message Flow editor.
2. Notice the names of the MQInput node (PINGJN) and MQOutput nodes (FAILURE and
PING_OUT). The node names are the same as the queue names that are specified as
properties and should match the queues that you created in the Exercise set up.
If you want to confirm these queue names, right-click those nodes and click Properties.
3. Click the HTTP Request node to view its properties in the Properties view.
In the Basic properties view, view the entry for Web service URL. The format of the URL is:
http://server:inode_listener_port/service
Student Exercises
The value of service must agree with a similar value that is specified in the properties of the
HTTPInput node in the target web service message flow.
_ Properties £3 . Problems Outline ^ Tasks 0 Deployment Log
** HTTP Request Node Properties - HTTP Request

Settings for working with the HTTPRequest node,
Description
Basic Web service URL* http ://localh ost : 7085/httpprotocol
HTTP Settings e,g, http'.jlserv&lpahhjtojservke

S5L
Request timeout (sec)* 1120
Response Message Parsing
Do not change any of the properties, but do remember them.

4. Open the HTTPProtocol message flow in the Message Flow editor by double-clicking
HTTPProtocol.msgflow in the Application Development view. It should contain three nodes
as shown in the following figure.
Click the HTTPInput (7085) node to see its properties.
The Path suffix for URL value on the Basic tab exactly matches the URL on the previous flow
HTTP Reply
■■ —# >-
HTTPInput (7085) Add_Time_5tamp
(the HTTPRequest node in that flow is starting this flow by using that URL).
(T Problems Outline •£* Tasks Deployment Log
HTTP Input Node Properties - HTTPInput (7085)

Settings for working with the HTTPInput node.
Description
Basic Path suffix for URL* | http://localhost:7085/httpprotocol
Advanced e,g: ¡path/to/'service, where the full uri is

Input Message Parsing http://se.fver:78DD/path/to/service Use HTTPS I“
Parser Options
_ 6. Close both of the message flows.

podrá reproducir o
Student Exercises

In this part of the exercise, you create and deploy a BAR file that contains the web services message
flows.
_ 1. In the IBM Integration Toolkit, create a BAR file that is called Webservice .bar.
_ a. From the menu bar, click File > New > BAR file.
_ b. For Container, select: WebSvc.
_ c. For Folder, use the <defauit> value.
_ d. For the Name, type: Webservice.bar
New BAR file

_ e. Click Finish. The new BAR file opens in the BAR File editor.
_ f. Select the Flows check box to add both message flows.
_ g. Under the Build Options, select Compile and in-line resources.
Cl *WebService.bar H
Prepare
Select deployable resources to include in the BAR
B O & Independent resources 3 □&,!
Deployable Resources Build Options

Build and Save..
0 Compile and in-line resources ;
Select a library to package all of its contained resources, or select independent resources to package for deployment. These resources will
be visible to other deployed resources in the same integration server. CJ r\CIMUVC LUI ILC.| 115 Ul U 1C Cl
u live uefore b
0 Override configurable property values O
O Applications, shared libraries, services, and REST APIs © Message flows, static libraries and other message flow dependencies Text filter: (type Add workspace project source files
filter text Working set filter: j <all resources>
E5QL*
□ ¡jeî CallWebSvc.esql - /WebSvc/CallWebSvc.esql
■""^¿^^P-otocoI.esql - /Web5vc/HTTPProtocol.esql
3 0 Hi7 Flows
M ■ bSvc.msgflow - /WebSvc/CallWebSvc.msgflow
0 ÜIl HTTPProtocol.msgflow - /WebSvc/HTTPProtocol.msgflow - □ ÿ
XSLT*
1 .... 0 [Ï] WebSvcTestMsg.xml-/Web5vc/Web5vcTestMsg.xml
_ h. Click Build and Save.

_ i. Click OK on the success message. The message flows are added to the BAR file.
Student Exercises
2. You can view and modify the message flow configurable properties, such as the queue
names, by editing the BAR on the BAR File editor Manage tab.
_ a. In the BAR File editor, click the Manage tab (at the bottom of the BAR File editor
window).
_ b. Fully expand the two compiled message flows (.cmf files).
■ 0 WebServIce.bar £3
Manage
gf s£] -^1 Q Filter by: | <Type filter text>
Name Type I Modified Size
El HHU Call WebSvc. cmf Compiled messa... Oct 15, 2015 7:27:26 AM 23577
El UHI CallWebSvc
^ Add_MQMD
l [g I] FAILURE
HTTP Request
Jjä PING_IN
ILÿli PING_OUT
Ö UHI HTTPProtocol.cmF Compiled messa... Oct 15j 2015 7:27:25 AM 5294

B HHB HTTPProtocol
Add Time Stamp
B-Sf. HTTPInput (7085)
HTTP Reply
jd __________________________________________________________________________________________________________________
► Command for packaging the BAR contents
\
Jl
Prepar Manage ser Log Service Log
c. Click the HTTPRequest and the HTTPInput (7085) nodes in the tree to view their
configurable properties.

podrá reproducir o
Student Exercises
The properties for the HTTPRequest node are shown here.

Properties tl Problems Outline Tasks ¡3 Deployment Log
HTTP Request
I(T) Configure properties of selected resource.

Configure
built
Workload Management Accept compressed responses by default r
Allowed SSL ciphers 1---------------------
Enable HTTP/1.1 keep-alive Y
Enable SSL certificate hostname checking
Enable certificate revocation list checking
r
r
HTTP version U
HTTP(S) proxy location
1---------------------
Protocol SSL
Request timeout (sec) 120

SSL client authentication key alias 1---------------------
Security profile
Use compression none

Validate ¡None
Web service URL 1 http : //localhost : 7085/httpprotocol

e.g. http:f/serverfeathftofeervice
Before you deploy the BAR file, you can change the URL for the target web service, which
overrides the value that was used for development testing. Similarly, a developer can test
locally by simulating a remote web service.
To start the actual target web service, no changes need to be made to the calling
message flow. You need only to specify a different URL by using the BAR File editor
Manage tab and then redeploy the BAR file.
In this exercise, you use the provided values for the connections. Do not change the
configurable properties for message flow nodes.
3. For this exercise, you allow for more than one instance of the flow to run.
__ a. While still on the BAR File editor Manage tab, click HTTPProtocoi. cmf to display the
message flow configurable properties.
__ b. In the Properties view, click Workload Management to display the Workload
Management configurable properties.
Student Exercises
c. Change the Additional Instances property value to 2.

Í _] Properties S3 til Problems a- Outline | Tasks H Deployment Log
HT1 PI’rotor nl.rmf

Configure (T) Workload management properties of selected built resource.
Workload Management Policy

Details
Notification Threshold (Messages per second) [| 0 Maximum Rate (Messages per second) |
0 Processing Timeout (Second) | 0 Processing Action None
Additional Instances | 2|
Start additional instances when flow starts I- Start Mode | Maintained
_ d. Similarly, change the Additional Instances property for the Caiiwebsvc.cmf message
flow to 2.
_ e. Save the BAR file updates by typing Ctrl+S, or by clicking File > Save from the menu
bar.
_ f. Close the BAR file editor.
4. Deploy the BAR to the server! integration server on IIBNODE_WITHQM.
_ a. In the Application Development view, right-click the Webservice.bar file and then
click Deploy from the menu.
I Application Development £3 Patterns Explorer
& -
B BARS
; tr ----------- -- ---------- - -------- ---
I-1 !& Ind.
Ö-fif Web5vc
b. In the Deploy window, click server! (under IIBNODE_WITHQM), and then click Finish.

podrá reproducir o
Student Exercises
The message flows should show under the serverl integration server in the Integration
Nodes view.
c. Verify that the deployment was successful by reviewing the Deployment Log and the
Integration Nodes view.
□■•filg Integration Nodes
[+1 TTRMnnF MnnM
□■■■ <3............... IIBNODE_WITHQ

M
serverl
; CallWebSvc P
HTTPProtocol
IIBN0DE_WITHQM2 É $
TESTNODEJibadmin
5. Deploying the message flows should activate the HTTP port 7085. Verify the port 7085 is in a
LISTENING state.
_ a. From a Windows command prompt, type:
_ b. Examine this list in Notepad, the listener that uses port 7085 should now be displayed as
LISTENING.
jf] network.tut - Notepad
File Edit Format View Help
Active connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING
TCP 0.0.0.0:523 0.0.0.0:0 LISTENING
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2414 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4414 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4416 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5722 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING
TfD n n n n-sann n n n n ■ n 1 TRTITMTMC
LISTENING
i Lr U . ' J . U. U . 5U0Ï
0.0.0.0:0 LI u i tim nu
TCP 0.0.0.0:47001 LISTENING
u. u. u. u . u
0.0. 0.0:0
The listener for port 7085 is now active because you deployed a web service message flow that
contains an HTTPInput node. The integration node compared the HTTP port number (7085) with
the port that is assigned to the integration node. Because they matched, the integration node
listener became active.
Student Exercises
r / Note ------------------------------------------------------------------------------------------- ^
The mqsicreatebroker and mqsichangebroker commands can also be used to assign or change the
integration node listener port number by using the -P HTTPPort parameter. Be sure to use an
uppercase “P” when entering this command as lowercase “p” is also a valid parameter.
Later in this exercise, you learn howto configure SSL, which uses a different port.
v ______________________________________________________________________________ _y
Part 4: Test the web service application

In this part of the exercise, you use the Integration Toolkit Unit Test Client and a pre-defined test to
test the web service.
_ 1. Enable the Integration Toolkit Unit Test Client.
_ a. In the Integration Toolkit, click Window > Preferences.
_ b. Expand Integration Development.
_ c. Click Unit Test Client.
d. Select Enable menus for test client and then click OK.

Student Exercises
2. In the Application Development view of the IBM Integration Toolkit, expand Independent
Resources > WebSvc > Flow Tests.
3. Double-click the file TestEnq.mbtest to open it in the Test Client.
4. Under Detailed Properties, change the properties in the Test Client as follows:
_ a. Change the Queue manager to match your integration node queue manager name
(IIBQM).
_ b. Change the Port to 0 (this port is not the HTTP port that you set earlier in the exercise by
Using the mqsichangeproperties command).
H *TestEnq S3 □
Events
Message Flow Test Events ► General Properties

Detailed Properties
....... I . __________ II _ L
■lljp ¿9 SIB iö
□ Enqueue Port: 0|
mq. Message sent to MQ Queue "PINGJN" Server channel: SYSTEM.BKR,CONFIG
Queue manager: | IIBQM
eue ; irii ni
“ Message — ►Header
Body : I Edit
as text
U
l~l Show in hexadecimal viewer (Read Only)
<InMsg> ~7\
<text>Hello Again</text>
</InMsg>
b
J
Import Source... Send Message
_ c. Type Ctrl+S to save the file.

_ 5. In the Unit Test Client, click Send Message to put a message on the PINGJN queue.
The message flow starts, calls the webservice flow, obtains the response, adds a message
descriptor, and delivers it to the output queue called PING_OUT.
/ Note -------------------------------------------------------------------------------------------- v
The only result that you see is Message sent to Queue. You do not see the response message until
you complete the next step.
V ______________________________________________________________________________ J
_ 6. Use the IBM MQ Explorer to see whether the message is on the output queue PING_OUT.
You can right-click the queue and click Browse Messages to view the message on the
queue.
Student Exercises
The message data should contain the following text:

<OutMsg>
<NewText>The date/time is:</NewText>
<DateTime>date_and._timestarrp when the flow was run</DateTime>
</OutMsg>
_ 7. Close the Unit Test Client in the IBM Integration Toolkit. Do not save the changes when
prompted.
Part 5: Implement SSL for the web service application

It is possible that a developer tested in an unsecured environment so that when the application is
moved to the production environment you must take steps to secure it. HTTP can be run over SSL to
ensure that the data is not altered while it is in transit.
Imagine, a scenario where a flow that calls a web service is being allowed to flow across non-SSL
HTTP connections. However, other users might start that same web service by using an HTML form
in a browser. In that case, you want to allow only trusted access. There is no requirement to change
the message flows. You set up a new archive file to make necessary changes to one message flow to
allow this scenario to work.
First, you must set up SSL for use. In a real-world environment, it is likely that you would obtain
certificates from an external certificate authority. However, for the purposes of testing or internal only
use, the keytool utility is included with the IBM Integration Bus. With the keytool utility, you can
generate certificate keys to use with SSL for testing. You use it for this exercise.
_ 1. Open an Integration Console as an Administrator user, if one is not already open.
_ 2. Change directories to the keytool utility directory:
cd C:\Program F±les\lBM\WebSphere MQ\j ava\jre\bin
_ 3. Run the keytool utility without any options to display a list of all the possible parameters:
keytool
Briefly review the parameters and options.

_ 4. Create a keystore.
_ a. Type the following command in the Integration Console:
keytool -genkey -keypass devkey -keyalg RSA -alias tomcat -keystore dev.keystore
-storepass devkey -validity 360 -keysize 2048

Student Exercises
__ b. You are asked a series of questions for the key generation process; respond to them as
shown here. You can use any name when prompted for first and last names.
What is your first and last name?
[Unknown]: Mary Smith
What is the name of your organizational unit?
[Unknown]: WM646
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Mary Smith, OU=WM645, 0=Unknown, L=Unknown, ST=Unknown, C=US correct? (type
"yes" or "no")
[no] : yes
The keystore is created with the values that you specified. The keystore file is written to the
C:\Program Files\IBM\WebSphere MQ\java\jre\bin directory.
5. Use Windows Explorer to create a directory that is named C:\iabfiies\keystores.
6. Copy the dev.keystore file from the C:\Program Fi le s \ I BM\Web Sphere M2\java\jre\bin
directory to the C:\labfiles\keystores directory.
7. Make the integration node IIBNODE_WITHQM aware of the keystore file, and configure the
HTTPListener to use the SSL port. This port is not the default HTTP port that you used earlier.
Type the following commands in the order shown.
These commands are case-sensitive.
r
To reduce the amount of typing you must do, you can press the up arrow key on your keyboard in the
Integration Console to retrieve a previous command. You can then edit the portion of command that
changed, by using the left arrow, right arrow, Delete, and Backspace keys.
Press Enter to run the command after you finish editing it.
__ a. Enable SSL for the integration node:

mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPListener -n
enableSSLConnector -v true
__ b. Configure the integration node with the keystore information:
mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -n
keystoreFile -v C:\labfiles\keystores\dev.keystore
Student Exercises
__ c. Set the keystore password in the integration node:

mqsichangeprqperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -n
keystorePass -v devkey
__ d. Set the port for HTTP SSL connections:
mqsichangeprqperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -n port -v
7083
__ e. Configure the integration node with the truststore information:
truststoreFile -v C:\labfiles\keystores\dev.keystore
__ f. Configure the truststore password in the integration node:
truststorePass -v devkey
__ g. Disable client authentication in the integration node:
clientAuth -v false
8. Use the mqsireportproperties command to verify the configuration changes that you made:
mqsireportproperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -a
Verify the values that are reported for uuid, keystoreFile, keystorePass, truststoreFile,
truststorePass, clientAuth, and port.
uuid='HTTPSConnector'
clientAuth='false'
keystoreFile='C:\labfiles\keystores\dev.keystore'
keystorePass='********1
truststoreFile='C:\labfiles\keystores\dev.keystore'
truststorePass='********1 port='7083'
9. Restart the integration node from the Integration Console so that the configuration changes
take effect.
Type:
mqsistop IIBNODE_WITHQM mqsistart IIBNODEJWITHQM
10. You are now ready to deploy message flows that use SSL. The message flows must request
the correct SSL port to function correctly. For testing purposes in this exercise, you use only
one of the two message flows.
In the IBM Integration Toolkit, create a BAR file that is called ssiArchive.bar.
Add only the HTTPProtocol message flow to the BAR file; do not add the CallWebSvc
message flow.
__ a. Right-click the BARs folder in the Application Development view.

Student Exercises
_ b. Click New > BAR file.

_ c. For Container, select WebSvc.
_ d. Use the <default> value for Folder.
_ e. For Name, enter ssLArchive.bar
_ f. Click Finish. The new BAR file is opened in the BAR File editor.
_ g. Select the check box for HTTPProtocoi .msgf low (do not include the caiiwebsvc
message flow).
_ h. Click Build and Save. The message flow is added to the BAR file.
_ i. Click OK to the confirmation dialogbox whenthe buildcompletes.
11. Modify the message flow properties to use SSL.
_ a. In the Manage tab of the BAR File editor, expand HTTPProtocoi.msgflow.
_ b. Expand HTTPProtocoi.
_ c. Click the HTTPInput (7085) node. The node properties are displayed in the Properties
view.
_ d. Modify the Path suffix for URL to use port 7083 (SSL) instead of 7085.
_ e. Select the Use HTTPS check box.
[r *55LArchive,bar £3
Manage
EÉ1 *3 Hi @l Filter by: | <Type filter text>
Name Type Modified Size Path
fe^ql HTTPProtocoi.esql ESQL file Oct 15, 2015 9:41:05 AM 599
□ m HTTPProtocoi.msgflow Message flow Oct 15, 2015 9:41:05 AM 2527
E BHll HTTPProtocoi
^ Add_Time_Stamp
m HTTPInput (7G85)
ß HTTP Reply
JLl ________________________________________________________________________________________ I
il
Prepare Manage User Log Service Log
& —
Ö Properties £3 . Problems a— Outline ffl Deployment Log

5T
cu
VI
t
HTTPInput
Configure(7085)
(T) Configure properties of selected built resource.
Path suffix for URL http : //localhost :7083/htt pprotocol
s-. g.- fpetn/tofservice, mere me run uri ts nttp;f¡serven TSQQfpethftofservice
Decompress input message Fault r
|sOAP 1.1
r
format Security profile
Maximum client wait time (sec)
I 180
'
Use HTTPS F
Student Exercises
12. Change the number of instances to 5 to allow multiple copies of the flow to run to
increase message throughput.
_ a. In the Manage tab of the BAR File editor, select HTTPProtocoi .msgf low.
_ b. Select the Workload Management section on the Properties tab.
_ c. Change Additional Instances to 5.
Properties £3 _ Problems □!: Outline Deployment Log
HTTPProtocoi .msgflow
Workload Management p0|¡

Details
Notification Threshold (Messages per second) fo Maximum Rate
(Messages per second) 0 Processing Timeout (Second) 0 Processing
Action None
Additional Instances 15l
Start additional instances when flow starts
13. Save the changes by typing Ctrl+S or clicking File > Save.
14. Create an integration server that is named ssLWebServices on IIBNODE_WITHQM.
_ a. In the Integration Nodes view of the Integration Toolkit, right-click
IIBNODE_WITHQM.
_ b. Click New Integration Server.
_ c. For the integration server name, type: ssLWebServices
_ d. Click OK.
15. Deploy the BAR file ssLArchive.bar to the SSLWebServices integration server.
Important
Do not deploy the ssLArchive.bar file to the same integration server where the non-SSL
flow is running (the default integration server).
16. Verify that deployment was successful by reviewing the Deployment Log.
17. Verify that a listener for port 7083 is now active by entering the netstat -an
command from the IBM Integration Console session.
18. Test the web service message flow.
__a. In Windows Explorer, browse to the C:\labfiles\Lab07-webSvc\resources\WebSvc
folder.
__b. Right-click the webSvcform.html file and then click Open with > Firefox.

Student Exercises
c. In the browser window, click Obtain Date/Time.

file:///C:/labfiles/Lab 10/resources/WebSvc/WebSvcform. html
^ - --
To obtain current date and time, click below
Obtain Date/Time
If you set up the keystore correctly, you get a security message about the certificate
that is being used. It might take a few moments before the browser
responds.
This Connection is Untrusted

You have asked FireFox to connect securely to localhost:7083, but we can't confirm that your
connection is secure.
Normallyj when you try to connect secured sites will present trusted identification to prove that you
are going to the right place. However, this site's identity can't be verified.
What Should I Do?

If you usually connect to this site without problems,, this error could mean that someone is trying to
impersonate the site., and you shouldn't continue.
G et rn e o ut of h e re! |
Tethnical Details
I Understand the Risks
If you understand what's going on, you can tell Firefox to start trusting this site's identification, Even
if you trust the site, this error could mean that someone is tampering with your connection.
Don't add an exception unless you know there's a good reason why this site doesn't use trusted
identification.
| Add Exception... |
If you use Internet Explorer to open the websvcform.html file, your output
results are different because of the differences in the browsers.

J
d. Expand I Understand the Risks and then click Add Exception. The Add Security
Exception window opens.
Student Exercises
_ e. Click Confirm Security Exception. A confirmation window opens.

_ f. Click Resend on the confirmation window. You should receive the response from the
web service in the form of an XML file with the date and time that is similar to the
example.
<OutMsg>
<NewText>The date/time is: </NewText>
<DateTime>2015-10-19 05:51:04.28613l</DateTime>
</OutMsg>
While it might not be obvious, the combination of the two flows used in this exercise
approximates to a “What time is it?’’ application. The “calling” flow can be altered to call
different web services by changing the URL value in the BAR file before deployment.
Exercise clean up
_ 1. In the IBM Integration Toolkit Integration Nodes view:
_ a. Right-click the SSLWebServices integration server and then click Delete > All flows
and resources.
_ b. Delete the SSLWebServices integration server.
_ c. Right-click the serverl integration server and then click Delete > All flows and
resources.
_ 2. Close any open windows and programs.
End of exercise

Student Exercises

As you saw, it is possible to change how a message flow that behaves as a web service
can be called in different ways. You also configured an integration node to use SSL and
non-SSL HTTP transports.
• Implement a web service message flow application that uses HTTPS for secure transport
Student Exercises

Student Exercises
Exercise 8. Using problem diagnosis tools

In this exercise, you enable and disable message flow Trace nodes, and
use a user trace and service trace to capture runtime information. You
also configure and activate an integration server JVM Debug Port.

• Activate a user trace and service trace to capture information
• Administer Trace nodes in a message flow
• Activate the integration server JVM Debug Port
Introduction
In this exercise, you use various problem determination tools to
administer message flows with trace nodes and administration tools to
generate and control tracing.
This exercise uses a flow that is similar to the message flow that is
used in a previous exercise but with the addition of a trace node.
In the first part of the exercise, you import a BAR file that contains a
Trace node into IBM Integration web interface. You examine the Trace
node properties and then deploy the BAR file to the IIBNODE_WITHQM
integration node.
In the second part of this exercise, you use the IBM MQ SupportPac
RfhUtil to put messages on the message flow input queue and test the
message flow.
Student Exercises
© Copyright IBM Corp. 2015 Exercise 8. Using problem diagnosis tools 8-1
In the third part of this exercise, you control Trace nodes and enable a
user trace and a service trace. A service trace provides more detailed
tracing, and generates a large amount of output.
In the fourth part of this exercise, you activate an integration server
flow debug port.
Requirements
• IBM Integration Bus V10 and IBM MQ Explorer V8
• The integration node IIBNODE_WITHQM and queue manager IIBQM
• The lab exercise files in the c: \iabf iies\Lab08-Trc folder
• The IBM MQ SupportPac IH03 (RfhUtil) in the C:\Software\ih03
folder

Student Exercises
Exercise set up
Use the IBM MQ runmqsc command to define the queues that are required for this exercise.
_ 1. Start an IBM Integration Console session if one is not already running.
_ 2. Type following command:
runmqsc IIBQM < C:\labfiles\Lab08-Trc\resources\Q_Defs.txt
_ 3. Using IBM MQ Explorer, verify that the following local queues are defined on queue
manager IIBQM: CATCH, FAILURE, FALSE, IN, REPLY, and UNKNOWN.
Part 1: Examine and deploy the BAR file

In this part of the exercise, you deploy an existing BAR file by using the IBM Integration web
interface for the IIBNODE_WITHQM integration node. The BAR file contains a message flow
that contains a Trace node.
_ 1. Open the IBM Integration web interface for the IIBNODE_WITHQM integration node if
it is
not already open.
_ 2. Expand Servers.
_ 3. Click the down arrow to the left of the server! integration server and then click Deploy.
_ 4. Click Browse and go to the c:\iabfiies\Lab08-Trc\resources directory.
_ 5. Click P D . bar and then click Open.
_ 6. Examine the Trace node properties in the PD.bar file.
_ a. The BAR file contains an application that is named SIMPLEFLOW_WITH_TRACE. In
the Deploy BAR File window, expand the application until you see the message
flow nodes.
_ b. Expand the Trace node to display the Trace node configurable properties.
Student Exercises
Deploy BAR File

Select a BAR file to deploy, Optionally, provide an overrides file.
Deploy preview:
Content Value
BAR file: PD. bar Browse
► FALSEO
► CATCHQ
► Test_Versii>n=2
► TraceExList
► FAILUREQ
T
Trace
fflePafii C:\lafofilestLabD8-TnASi mple Flowtrace .txt

► REPLY
Overrides
The developer specified that the Trace node should create a trace file. Based on
this setting at design time, the only property that the administrator can change is
the location of the trace file. In this BAR file, the trace file destination (filePath) is
set to:
C: \labf iles\Lab08-Trc\SirnpleFlowtrace. txt.
7. Click Deploy.
You should see a message flow that the deployment was successful. You should also
see that the message flow SimpleFlowWithTrace is running under the server!
integration server.
T £ IIBNODE_WIThQM w -
j S Servers
¿1. serveM Tg
Services g REST
APIs » g
Applications
-r ¿g SIM P LEFIOW_WI T H_TRAC E T
g Libraries
T £ Message Fiawsj
SimpleFlowWithTrace T
Subflows ► & Resources gp
References

Student Exercises
Part 2: Test the message flow

In this part of the exercise, you test the message flow by using the IBM MQ SupportPac
RfhUtil.
_ 1. Start RfhUtil.
_ a. In Windows Explorer, browse to the C:\Software\ih03 directory.
_ b. Double-click the rfhutil.exe file.
_ 2. Put a test message on the IN queue on the IIBQM queue manager.
_ a. On the Main tab in RfuUtil, select IIBQM for the Queue Manager Name.
_ b. Select IN for the Queue Name.
_ c. Click Open File. A file selection window is displayed.
_ d. Go to C : \labf iles\LabO8-Trc\data and then select the file Test_V2_msg. xml.
Click Open.
Student Exercises
_ e. Click Write Q to send the test message to the IN queue.

_ 3. Open another RfhUtil instance and check the REPLY queue.
_ a. On the Main tab in Rfulltil, select IIBQM for the Queue Manager Name.
_ b. Select REPLY for the Queue Name.
_ c. Click Read Q.
_ d. Switch to the Data tab and click XML as the Data Format. The message should show
as follows:
<OutMsg>
<Version>2</Version>
</OutMsg>
_ 4. Do not close the RfhUtil session, as you use it later in this lab.
Part 3: Manage traces and Trace nodes

In this part of the exercise, you use the IBM Integration Console to activate a user trace and
manage the Trace node.
_ 1. In the IBM Integration web interface, verify the current state of the Trace nodes on the
integration server.
_ a. Click server! to display the integration server properties in the Overview tab.
_ b. In the Overview tab, expand the Advanced Properties section.
_ c. The Trace Node Level property identifies the current state of the Trace nodes. Verify
that the Trace Node Level is on.

Student Exercises
serveM - Integration Server

Q Overview Resource
Statistics Statistics
T Quick View
served
Integration Server Name running
Run Mode 4S3Q952e-6d74-46jß4-S165-d1 daSOScfcdS
UUID true
Running
Short Description Long

Disabled
Description Record Mode
▼ Advanced Properties
Disabled
Injection Mode Process ID Trace Level
6904
Soap Nodes use Embedded Listener Thread
none
Local Proxy Name Managers Console Mode
true
HTTP Nodes use Embedded Listener Inactive
false
User Exit List
off
false
Trace Node Level on
UserTrace Level none
2. In the IBM Integration web interface, verify the current state of the User Trace Level
for the SimpleFlowWithTrace message flow that is running in the IIBNODE_WITHQM
server! integration server.
_ a. Expand the application under the serverl integration server to show the message
flow.
_ b. Click the SimpleFlowWithTrace application flow to show its properties in the
Overview
tab.
The message flow Advanced Properties indicate that user trace is not active (User
Trace Level is set to none).
Student Exercises
SîmpleFlowWithTrace - Message Flow

Overview Statistics Operational Policy
Edit
T Quick View
Message Flow Name SimpleFlowWittiT race
Version
UUID Mcc 19a7-eSfQ-42e0-83d3-2074d5c50e99
Service Trace Level none

Commit Cou nt 1
Additional Instances 0
Start Mode Maintained
Coordinated Transaction no
Commit Interval 0
Running true
Run Mode running
T .Advanced Properties
User Trace Level
MtUVC USCI LKIl LI3SL
3. In an IBM Integration Console, activate a debug level user trace for the
SimpleFlowWithTrace message flow.
Type:
mqs i change trace IIBNODE_WITHQM -e severl -u -f SimpleFlowWithTrace -k
SIMPLEFLOW_WITH_TRACE -1 debug
4. In the Integration web interface, verify that the User Trace Level for the message
flow is
now set to debugTrace.
5. Send another test message to the IN queue by clicking Write Q in the first RfhUtil
session that you started.
6. Verify that the reply message was put on the REPLY queue on queue manager
IIBQM.
7. Retrieve the user trace data and deactivate tracing by running the GETTRACE script.
This command file runs several IBM Integration Bus commands:
- mqsireadiog reads the binary trace data that the trace node generated
- mqsif ormatiog translates the binary trace data into human-readable format
- mqsichangetrace disables tracing (and can also be used to start tracing or
change trace parameters)
Student Exercises
The command file then starts Windows Notepad to display the trace output.

In the Integration Console, run the GETTRACE script. Enter the commands:
cd C:\labfiles\Tools gettrace
IIBNODE_WITHQM serverl
8. Review the user trace output. You should find all the runtime events (or errors) in the
trace file.
The trace shows the path that each message took through the message flow, and
how each node responded to the message. The trace listing also shows a detailed
listing of all ESQL statements that were run in the flow.
When you are done reviewing the trace listing, close the Notepad window.
A copy of user trace file serverl. txt is provided for your reference in the
C:\labfiles\Lab08-Trc\solution directory.
9. Review the output from the Trace node in the file you configured in the Trace node
properties (in this case, C:\labfiles\Lab08-Trc\SimpleFlowTrace.txt).
__ a. Use Windows Explorer to locate the Trace node output file.
__ b. Open the file and examine the contents. The entire message that the Trace node
received is displayed in the output because the developer specified ${Root} for
the trace pattern.
A copy of the trace file that the Trace node generates is provided for your reference in the
10. In the Integration Console, disable the user trace on the SimpleFlowWithTrace
message flow. Type:
mqs i change trace IIBNODE_WITHQM -e severl -u -f SimpleFloWWithTrace -k
SIMPLEFLOW_WITH_TRACE -1 none
11. Trace nodes generate trace records that you can use to monitor the behavior of a
message flow. After a developer finishes testing a message flow, the developer or the
administrator must disable the Trace nodes to avoid the performance impact that
tracing causes. In Integration Bus, you can turn off the Trace nodes without
removing them from the message flow.
Disable the Trace nodes on the serverl Integration server.
mqs i change trace IIBNODE_WITHQM -n off -e serverl
12. Using the Integration web interface, verify that the User Trace Level on the message
flow is now none and the Trace Node Level on the integration server is off.
Student Exercises
13. A service trace provides more detailed tracing, and generates a large amount of
output. In this part of the exercise, you can enable and disable a service trace by
using the
mqsichangetrace command.
Important
You typically generate a service trace under the direction of IBM

Support.
y
V _____________________________________________________
__ a. In the Integration Console, type the following command to start a service trace for
the
server! integration server. The -r flag resets trace to delete any previous trace
data that was collected.
mqs i change trace IIENODE_WITHQM -t -e server! -1 debug -r
The character before debug in the command is a lowercase “L”, not a “l”.
__ b. Type the following command to verify the trace settings on the integration server.
mqsireporttrace IIBNODE_WITHQM -t -e serverl
You should see a response that indicates that the trace level is “debug”.
14. Go to the first RFHUtil session and send another message to the IN queue.
15. Turn off the service trace. In the Integration Console, type:
mqs i change trace IIBNODE_WITHQM -t -e serverl -1 none
16. After you generate a service trace, you must retrieve the service trace data into a file.
For this exercise, the command file getsvctrace. cmd in the c: \iabf iies\Toois
directory retrieves the service trace data. The command file is similar to the
gettrace.cmd that you used when retrieving the user trace data.
__ a. Retrieve the service trace data from an IBM Integration Console session.
In the Integration Console, type the commands:
cd C:\labfiles\Tools getsvctrace 11BNODE_WITHQM serverl
__ b. Review the service trace output in the Notepad session that the getsvctrace. cmd
opens.
The information that is captured in the service trace is more detailed. It includes
trace information about the interactions of the various components (such as the
toolkit and the integration nodes).
Close the Notepad window when you are done reviewing the service trace
information.
A copy of the service trace file is provided for your reference in the
V ________________________________________________

Student Exercises
Part 4: Administer the message flow debugger

Developers can use the message flow debugger in the IBM Integration Toolkit to help
diagnose unexpected behavior within message flows. Breakpoints can be set to pause the
flow and examine and change the contents of the message, Extended Structured Query
Language (ESQL), and Java variables and mappings. While developers normally do these
tasks, an administrator might be called upon to help with setting up the debugging
environment.
Since the Java runtime debug environment is used for all message flow debugging, you must
configure the JVM debug port for the integration server in which the message flow is
running.
The debug port can be configured in the development environment by using the IBM
Integration Toolkit, or in the administration environment by using IBM Integration web
interface or a command. As an administrator, you must also be aware of the status of the
debugger because of the potential impact on overall performance. In this exercise, you
configure and manage the message flow debugger from IBM Integration web interface.
You must configure the JVM debug port once for each integration server. The integration
server QuickView in the IBM Integration web user interface identifies whether a debug port
is configured for an integration server.
1. Determine whether a debug port is defined in the server! integration server on the
IIBNODE_WITHQM queue manager.
_ a. In the Integration web interface for IIBNODE_WITHQM, click server! to display its
properties on the Overview tab.
_ b. Expand the Resource Manager Properties section.
_ c. Verify that the current value for the JVM Manager - JVM Debug Port property is 0.
Student Exercises
cg_j serverl - Integration Server

<Q> Overview Resource Statistics ■ ■ Statistics
► Quick View
► Advanced Properties
T Resource Manager Properties
JVM Manager - JVM Debug Port 0

JVM Manager - JVM Min Heap Size -1
JVM Manager - JVM Max Heap Size -1
JVM Manager - JVM Native Stack Size -1

JVM Manager - JVM Verbose Option none
JVM Manager - JVM System Property
2. Using the IBM Integration web interface, set the JVM debug port to 9997 .
_ a. Click Edit on the Overview tab for the server! integration server.
_ b. Scroll down until you see the JVM Manager - JVM Debug Port property.

Student Exercises

Overview Resource Statistics |^v Statistics
S Cancel
Cache Manager - Domain Name L-J

Cache Manager - Clients Default to SSL L-J
Cache Manager - SSL Protocol
Cache Manager - SSL Alias L-J

Content Based Filtering - Enabled false L-J
Content Based Filtering - s/alidation
Threads
1
L-J
Content Based Filtering - Evaluation
1 ...
Threads
JVM Manager - JVM Debug Port

Ü ...
_ c. Click the edit icon (the icon in the same row as the property).
_ d. In the Edit Value window, type 9997 and then click OK.
_ e. Click Save.
r Note ------------------------------------------------------------------------------ v
You can also use the mqsichangeproperties command to configure the JVM debug port:
mqsichangeproperties <intNodeName> -e <intServerName> -o ComlbmJVMManager
-n jvmDebugPort -v <portNumber>
If you use mqsichangeproperties to set the debug port, you must also manually stop and
restart the integration server by using the mqsistop and mqsistart commands.
V _______________________________________________________________________ V
_ 3. The integration server Resource Manager Properties update to show that a debug port
is
enabled.
The developer can now start the debugger from the Integration Toolkit. When the
developer is done debugging the message flow, you should disable the JVM debug
port.
_ 4. Disable the integration server JVM debug port by changing the JVM Resource Manager -
JVM Debug Port property to 0.
Student Exercises
Exercise Clean up
_ 1. Delete the deployed message flow application from the serverl integration server on
IIBNODE_WITHQM integration node.
_ 2. Clear the messages from the REPLY queue on IIBQM.
_ 3. Close the RfhUtil windows.
End of Exercise

Student Exercises

In this exercise, you used some of the troubleshooting tools available to developers and
administrators, which include the Trace node, user trace, and service trace. This exercise
also showed you how to use the IBM Integration web interface and command to monitor
and manage the troubleshooting tools. Managing the state of the troubleshooting tools in a
production environment is especially important as many of these tools negatively affect
performance.
In this exercise, you worked with a local integration node. The same tools are also available
for managing remote integration nodes after a connection is established to the remote
integration node from the IBM Integration web interface.
Student Exercises

Student Exercises
Exercise 9. Identifying runtime problems

In the first part of this exercise, you analyze a series of message flows
that produce runtime errors and determine where the incoming
message is found after the errors occur. In the second part of the
exercise, you analyze and correct error situations that involve an IBM
Integration Bus integration node that connects to an IBM MQ queue
manager.

• Describe the symptoms of runtime and environmental problems
• Isolate a problem to a particular component
• Determine the cause of a problem and correct it
Introduction
In the first part of the exercise, you examine message flows that cause
a runtime exception. You evaluate the runtime exceptions and identify
what happens to the message when the designated processing node
generates an exception.
In the second part of this exercise, you are given a preconfigured BAR
file and some information about its content and what to expect in terms
of what constitutes successful completion of the flow. You deploy and
run the message flow. The message flow fails with one or more errors.
You identify the errors and propose a correction to the problem.
Requirements
• A lab environment with IBM Integration Bus V10 and IBM MQ V8
• Successful completion of Exercises 2
• The exercise files in the C:\iabfiies\Lab09-PD and C:\iabfiies\Toois
directories
directory
© Copyright IBM Corp. 2015 Exercise 9. identifying runtime problems 9-1

podrá reproducir o
Student Exercises
Part 1: Analyze message flow runtime failures
This part of the exercise presents some message flows that connect to IBM MQ. Each
message flow shows a runtime exception. In each of the following scenarios, determine what
happens to the message that is being processed when the designated processing node
In each of the flows, TxMode is the state of the Transaction mode property for the input
message processing node.
_ 1. In this example, the error occurs on the Out node. The queue manager has a defined
dead-letter queue (DLQ) and a backout queue for the input queue (IN_BOQ).
IFailure
E>=
IN TxMode=Yes Compute
Record your answer 8

here: Out
2. Queue manager dead-letter queue = DLQ; IN queue backout queue =

IN_BOQ B
Out
>
B
a
Failures:
l
Failure
IN TxMode=No Compute
Record your answer here:
_ 3. Queue manager dead-letter queue = DLQ; IN queue has no backout queue.

Student Exercises
Failure
- E
+ }=
D
HJ TxMode=Yes Compute
Out
_ 4. Queue manager dead-letter queue = DLQ; IN queue backout queue =

IN_BOQ
B
Failure
B
E> =
TxMode=Yes Compute
..
Out

podrá reproducir o
Student Exercises

IN_BOQ

IN_BOQ

Student Exercises
7. Queue manager dead-letter queue = DLQ; IN queue backout queue = IN_BOQ

Hint: The Out node generated the original exception, but more exceptions occurred
during explicit exception handling.

podrá reproducir o
Student Exercises
Part 2: Isolate and identify problems

In this part of the exercise, you apply your accumulated knowledge to deploy and test a
message flow and then identify the problems. The instructions in this exercise are
intentionally brief.
In this part of the exercise, you are given a preconfigured BAR file. You are also given some
information about its content and what to expect, in terms of what constitutes successful
completion of the flow.
Some general hints and tips are provided.
• What is (or are) the expected result (or results) of the BAR file content? This result is
likely to be the initial criterion to determine whether all is well (or not).
• Recall that several components can participate in the IBM Integration Bus environment:
the integration node, integration server, and in some case, IBM MQ queue managers,
and queues. When, and if, something goes wrong, error messages are likely to be
generated. The question to ask is, from which component?
• What do you know, or what can you determine, about the message flow and its use of
CATCH or FAILURE logic? What do you know about the integration node queue manager
in terms of a dead-letter queue? Consider these factors when you answer the question
“Where is the message?” in the context of the default behaviors that were described in
the lecture.
• Even though this course is about IBM Integration Bus, there are cases where the
interaction, and dependence between the integration node and the queue manager are
significant. When it comes to problem recognition and problem resolution, there is can
be overlap between the two products.
• Although you have access to the IBM Integration Toolkit in this class, the focus of the
exercise is to use the IBM Integration web user interface, IBM MQ Explorer, and system
tools.
You can find solutions to this error scenario in Appendix A.
The message flow in this error scenario triggers when a message is put on the IBM MQ IN
queue. The Filter node in the message flow routes the message to an output queue based
on the message content.

podrá reproducir o
Student Exercises
1. In the IBM MQ Explorer, verify that the following local queues exist on the IIBQM
queue manager:
• CATCH
• IN
• REPLY
• FAILURE
• FALSE
• UNKNOWN
If any of the queues are missing, create them as local queues on IIBQMGR.
2. Delete any deployed message flows from the server! integration server on
3. Deploy FindTheError.bar (in the C:\labfiles\Lab09-PD\resources directory) to the
serverl integration server.
4. Verify that the message flow SimpleFlowWithTrace message flow is deployed
and running.
- J IIBNODE_WJTHQM ▼
- ¡S Servers ^
¿g, serverl ▼
¿5 Services
gl REST APIs
m (J5 Applications
■r SIMPLEFLOW WITH TRACE
Libraries
- ™ (Message Fiows;
SimpleFlowWithTrace •*
^ Subflows
5. Use RfhUtil to test the message flow.

Use test message Test_v2_Msg.xmi that is in the C:\iabfiies\Lab09-PD\data directory.
Write the message to queue IN in queue manager IIBQM.
See Exercise 8 if you need detailed instructions for the steps to test the message flow.
V ______________________________________________________________________ J
6. Evaluate the results. Where was the message sent?
Use whatever problem determination tools you think are required to understand
exactly what is taking place. Apply corrective action as you see fit. If there is a
problem, can you correct it more than one way?
Consider this exercise complete when you identify why the message is not being put
on the REPLY queue.
Student Exercises
Exercise clean up
_ 1. In IBM MQ Explorer, clear any remaining messages from the queues.
© Copyright IBM Corp. 2015 Exercise 9. Identifying runtime problems 9-7

_ 2. Close any open windows and programs (such as RFHUtil). You can leave the IBM MQ
Explorer open.
_ 3. Delete the message flow that is running on in the server! integration server on
IIBNODE_WITHQM.
_ 4. If you enabled any traces in this exercise, turn them off.
End of Exercise

Student Exercises

The first part of the exercise helped you to understand integration node default behavior if
an error (that is, an exception) occurs in a message flow. Message flow design and IBM MQ
queue definitions and specifications also affect where the messages are ultimately found.
Part two simulated, to a degree, the nature of runtime and environmental errors that are
likely to be encountered in a typical installation. Probably the most important thing to
remember is the close relationship between the IBM Integration Bus and the queue manager
for some message flows. Although a problem might manifest itself in one product, the
contributing cause might be the other.

Student Exercises

podrá reproducir o
Student Exercises
Exercise lO.Viewing runtime statistics

In this exercise, you enable integration node statistics collection and
view the collected statistics with the IBM Integration web user
interface. You also create a subscription for the integration node
statistics and write them to a queue.

• Enable integration node resource and message flow statistics
• View integration node statistics in the IBM Integration web user
interface
• Subscribe to integration node statistics from IBM MQ
Introduction
In this first part of this exercise, you use the IBM Integration web
interface to enable resource statistics collection on an integration server
and message flow statistics collection on a message flow.
In the second part of this exercise, you use the IBM Integration web
interface to examine the statistics data.
In the third part of this exercise, you use IBM MQ Explorer to subscribe
to an IBM Integration Bus statistics publication. You then use the IBM
MQ SupportPac RfhUtil to retrieve and view the statistics data.
Requirements
• The integration node IIBNODE_WITHQM and the queue manager
IIBQM that were created in Exercise 2
• The lab exercise files in the C:\labfiles\LablO-Stats\resources
directory
• The IBM MQ IH03 SupportPac in the C:\software\ih03 directory
© Copyright IBM Corp. 2015 Exercise 10. Viewing runtime statistics 10-1
Student Exercises
Exercise set up
Import and run a message flow application by using the Flow Exerciser in the IBM
Integration Toolkit if it is not already running.
_ 1. Start the IBM Integration Toolkit, if it is not already running.
_ 2. In the IBM Integration Toolkit, switch to a new workspace.
_ a. To prevent any conflicts with any existing message flow applications, switch to a
new
workspace that is named c:\workspace\stats.
_ b. For the Workspace, type: c:\workspace\stats
_ c. Click OK. After a brief pause, the IBM Integration Toolkit restarts in the new
workspace.
__ 3. Import the simpieFiowWithMap_Pi. zip project interchange file from the
C:\labfiles\LablO-Stats\resources directory.
_ c. To the right of From zip file, click Browse.
_ d. Browse to the C:\labfiles\LablO-Stats\resources directory.
_ e. Click sinpieFiowWit±Map_Pi. zip and then click Open.
_ f. Click Transformation_Map (if it is not already selected) and then click Finish.
The Transformation_Map application is now displayed in the Application
Development view.
_ 4. Open the Transformation_Map.msgfiow message flow in the message flow editor.
_ a. Fully expand the Transformation_map application by clicking the plus (+) signs and
examine its contents.
_ b. Double-click the Transformation_Map.msgfiow message flow to open it in the
message
flow editor.

podrá reproducir o
Student Exercises
_ 5. Start the Flow Exerciser and deploy the message flow to the serverl integration server on
IIBNODE_WITHQM. ~
_ a. In the Message Flow editor, click the Start Flow exerciser icon to deploy the message
flow and start the Flow exerciser.
_ b. Select the serverl integration server on the IIBNODE_WITHQM integration node and
then click Finish.
_ c. The application is deployed to the serverl integration server on IIBNODE_WITHQM.
You should see a window that indicates that the message flow is being deployed.
_ d. Click Close on the Record Message window.
Part 1: Enable message flow and resource statistics

In this part of the exercise, you enable message flow statistics and resource statistics from IBM
web user interface for the integration node IIBNODE_WITHQM.
_ 1. If it is not already open, open the IBM Integration web user interface for the
_ 2. Verify that the Transformation_Map message flow is running on serverl.
- $ IBNODEJMTHQM T
e Servers <r ^
serverl ¡gj
Services g. REST
APIs T g
Applications
- £0 Transformation_Map ▼ £
Libraries T Ep Message Flows
jTransformation_Mapi T
Up Subflows
_ 3. Enable message flow statistics collection on the Transformation_Map message flow.

_ a. Click the down pointing arrow on the right side of the Transformation_Map message
flow and then click Statistics on.
podrá reproducir o
Student Exercises
/ Note
. ^ llBNODE_WITHQM T T (=
Overview
Servers ^
^ serverl T g
Services g REST
APis -r g ■ Quick
Appiicatiens View
Message
•m .53 Transfomnation_Map
Version
Libraries
v g Message Fiows UUID
@0 Trarsformation_Map j v
g Subtlows ► Resources gp
References ^ Libraries @0 Trarsformatlori_Map
Shared Start
Libraries g Stop
Message Flows g Force stop
Subflows Statistics on
Resources Statistics off
► in Operational Policy Attach policy ..........................
b. A confirmation message that indicates that message

Defach policy
flow statistics are enabled
is displayed.
r
You can view the message flow statistics collection status by running the mqsireportfiowstats
command from an IBM Integration Console.
For example, to view the message flow statistics collection status for the message flows that
are running on the serverl integration server, type:
mqsireportfiowstats IIBNODE WITHQM -a -e serverl -j
v_ J
_ 4. Enable resource statistics collection on the serverl integration server that is running on
IIBNODE_WITHQM.
_ a. Click the down pointing arrow on the right side of the serverl integration server and
then click Resource statistics on.
_ b. A confirmation message that indicates that resource statistics are enabled is
displayed.

Student Exercises
^fj IIBNODE_WITHQM *w,QS¡ Servers -*■

' <5* serverl l
rjSj Servic serverl
(S REST Start
■wr |g3. AppliC- Start All Application Types

- m TR Start All Message Flows
e Stop
-m
Stop All Application Types Stop
All Message Flows
1
S Rename
►& Delete All
£fp Delete
, Librari Deploy
g* Share Start recording
¡gKp Messa Stop recording
Subflo Statistics on
C~t, Resoi Statistics off
¡Jg Operational F Resource statistics on
QB Data Resource statistics oft
► See urity
r / Note -------------------------------------------------------------------------------------------- ^
You can also view the resource statistics collection status by running the
mqsireportresourcestats command from an IBM Integration Console.
For example, to view the resource statistics collection status for the server! integration server
that is running on the IIBNODE_WITHQM enter:
mqsireportresourcestats IIBNODE WITHQM -e serverl
Part 2: View message flow and resource statistics

In this part of the exercise, you use the IBM Integration web interface to view the
integration server resource statistics and then message flow statistics.
_ 1. Send a test message to the flow by using the Integration Toolkit Flow Exerciser.
_ a. Click the Send a message to the flow icon in the Flow Exerciser toolbar.
Student Exercises
b. In the Send Message window, click Messagel in the Input Messages folder.
c. Click Send.
_ d. Click Close on the Progress Information window.

2. View the integration server resource statistics for server! in the IBM Integration web
interface.
a. Click the serverl integration server to display its properties and tabs.
b. Click the Resource Statistics tab to display the Resource analysis view.

Student Exercises
server! - Integration Server
se podrá reproducir o Q\ Overview Resource Statistics ['v Statistics
Resource analysis in, Download data
Used Memory (MB)
Used Memory (MB) Latest

87.0 Highest Average Lowest
87.0
Latest 87.0
Highest 87.0
Average
Lowest
354.0
10:39:45
354.0
10:39:45 10:40:00 10:40:15 10:40:30 354.0
10
354.0
I ▼ server! resource statistics Resource type: Java Virtual Machine (JVM)
:40:00
Initial Used Committed Maximum Cumulative Cumulative
Number Of
NameCommitted
▼ Memory Memory Memory Memory Memory GC Time
(MB) (MB) (MB) (MB) (Seconds) Garbage
Collections
| summary
(MB)
32 87 354 -1 89 84
Non-Heap Memory 0
32
51
36
304
50
-1
256
Heap Memory Garbage
Collection -
MarkSweepCompact 88 10
Garbage Collection -
Copy 1 74
Committed Memory (MB)
__ c. In the table at the bottom

of the Resource analysis view, click Heap Memory to add it
to the graph view. You should see a new line in the graph view that matches the
color that is shown for Heap Memory in the resource table.
_ d. In the table at the bottom of the Resource analysis view, click Non-Heap Memory to
add it to the graph view. You should see a new line in the graph view that matches
the color that is shown for Non-Heap Memory in the resource table.
_ e. In the Used Memory graph, hover you cursor over any of the graph lines to display the
data points.
If you are doing these exercises on a course image, it might take a few seconds for
the interface to recognize that your cursor is stopped over a line in the graph.
3. View the message flow statistics for Transformation_Map message flow.
_ a. Click IIBNODE_WITHQM to display its properties and tabs.
_ b. Click the Statistics tab to display the Flow comparison view.
Student Exercises
)1BN0DE_W1THQM - Integration Node
Qi Overview Statistics
Flow comparison
• Throughput per message flow for last 19 seconds. Last updated at 11:03:18 Pacific Daylight Time.
Average Elapsed
Flow name Timet Invocation Average CPI Time/
Message Rate - (messages/s) (ms) Invocatici (ms
T ransformation_Mal%| 189 7.
0.06
T Nodes for all flows In IIBNODE_WITHQM

Average -
Node Elapsed Time Average CPU Time Total Elapsed
(ms) (ms) Time (ms)
Map 11.0 0.1 11.0
HTTP Input 7.1 7.0 7.1
HTTP Reply 0.9 0.1 0.9
The Flow comparison view displays statistical information for all message flows in
the selected resource. You can use this information to see where you might
enhance performance in terms of resource usage, message flow throughput, and
response times.
c. When you identify a message flow that requires attention, you can use the Flow
analysis view to see more detailed statistical information about the nodes in the
flow.
Click the magnifying glass icon to the right of the message flow name
(Transformation_Map) to go to the Flow analysis view for the message flow.
d. The Flow analysis view contains statistical information about the selected
message flow. The view includes data such as the message rate, CPU time, and
elapsed time for messages that are processed by each node in the message flow.

Student Exercises
The charts in this view show data for three statistics at a time. By default the
charts show the message rate, average elapsed time, and average CPU time for the
selected message flow.
Ek J Transformation_Map - Message Flow
•j Overview Statistics |g=i Operational Policy
Flow analysis
▼ Updates from 09:26:51 Pacific Daylight Time (60 minutes ago). Last updated at 10:27:03 Pacific Session
e. Change the statistics to display in the charts by clicking the arrow in the table next
Message Rate (messages/s)
0.05
0.04 Latest 0.00
0.03 Average 0.01
Highest 0.05
0.02
Lowest 0.00
0.01
0
9:36 AM 9:48 AM * # # # # # # # #
40 Average Elapsed Time/ Invocation (ms)

Average Elapsed Time/ Invoci
30
Latest 0.0
20 Average 0.3
Highest 37.5
10 Lowest 0.0
0
9:36 AM 9:48 AM ### ### ### Average CPU Time/
40 Invocation (ms)
Average CPU Time/ Invocatioi ~
30
Latest 0.0
20 Average 0.2
Highest 30.6
10 Lowest 00
to each graph and then selecting the required statistic from the list.
Student Exercises
Transformation_Map - Message Flow
Q Overview Statistics (f^ Operational Policy
Flow analysis
[ ▼ Updates from 09:28:51 Pacific Daylight Time (60 minutes ago) Last updated at 10:29:03 Pacific (fgpfgianHftj Session ^ | [
f. Scroll down in this view to also see the average elapsed time and average CPU
0.05 Message Rate (messages/s) ^
A
0.04 Message Rate (messages/s)
0.03 Average Elapsed Time/ Invocation (ms)
0.02 Average CPU Time/ Invocation (ms)
0 01 Total CPU Time Waiting for Input Message (ms) Total
0 9:36 AM 9:48 AM 10:00 AM 10:12 AM 10:24 AM Average

Elapsed Time Waiting for Input Message (ms)
Maximum CPU Time (ms)
Elapsed Time/ Invocation (ms) Maximum Elapsed Time (ms)
40
Maximum Size of Input Messages (Kb)
30 Minimum CPU Time (ms)
20 Minimum Elapsed Time (ms)

Minimum Size of Input Messages (Kb)
10
Number of Threads in Pool
0 Times Maximum Number of Threads Reached
9:36 AM 9:48 AM 10:00 AM 10:12 AM 10:24 AM Average
Total CPU Time (ms)
CPU Time/ Invocation (ms) Total Elapsed Time (ms)
40
Total Input Messages
30 Total Number of Backouts
20 Total Number of Commits

Total Number of Errors Processing Messages
10
Total Number of Messages with Errors
0 Total Number of MQ Errors
Total Aggregation Timeouts
time for each message processing node and the map profile.
r --------------------------------------------------------------------------------------------------------------
To see real-time updates in the Statistics view, go back to the Integration Toolkit and send
another test message by using the Flow Exerciser.
V _______________________________________________________________________ J
4. Review the statistics.
Part 3: Set up subscriptions for resource statistics

If you enable resource statistics collection for one or more integration servers on an
integration node, you can subscribe to the messages that the integration node publishes.
In this part of the exercise, you subscribe to the resource statistics topic from IBM MQ
Explorer.
1. In IBM MQ Explorer, create the local queue that is named EVENTS.

Student Exercises
2. In IBM MQ Explorer, create a subscription for the resource statistics.

_ a. Right-click Subscriptions under IIBQM and then click New > Subscription.
_ b. For the subscription name, type HBResourceStatistics and then click Next.
_ c. Configure the subscription properties on the Change properties window:
• For Topic name, click Select, select SYSTEM.BROKER.MB.TOPIC, and then click
OK.
• For Topic String, type: +/ResourceStatistics/#
• For Destination queue manager, type: IIBQM
• For Destination name, type: EVENTS
_ d. Click Finish, and then click OK on the confirmation window.

_ e. The new subscription IIBResourceEvents with a topic string of
$SYS/Broker/+/ResourceStatistics/# should now appear in the Subscriptions content
view.
3. Use RfhUtil to view the resource statistics from the subscription destination message
queue and create an XML file that contains the resource statistics.
_ a. Start RfhUtil.
_ b. Select IIBQM for the Queue Manager Name.
c. Select EVENTS for the Queue Name.
Student Exercises
_ d. Click Browse Q.
_ e. Click the Data tab. You should see the resource statistics.
_ f. Under
Data ead Write View Ids MQ Help
Format,
select XML so the data can be viewed as XML data.
File Edit^^gj
Main [Data J MQMD ] PS | UsrProp | RFH ] PubSub pscr ] jms ] usr ] other | CICS | IMS ] DLQ
Message uata |o310) from EVENTS
<ResourceStatistics brokerLabel="IIBWODE_WITHQM" brokerUUID= "395c52 f 4-_t.

<ResourceType name="JYM">
■iresource Identifier -naitie= " s ummar y " I nit ia iMemo r y I nMB="32"
iresource Identifier -Use dMemo r ^ name="Heap Memory"
iresource IdentifierInitialMemoryInMB="32" UsedMe name="Non-Heap Memory"
i <resourceIdentifier InitialMemoryInMB="0" Use name=" Garb age Collection
i ■iresource Identifier- Copy" CumulativeGCTirt name=" Garb age Collection -
i </ResourceType> MarkSweep Compact” Cult
i <Re so urce Type name="
i ■iresource Identifier ODBC">
i </ResourceType>
name="summary" ExecuteSuccess="0" ExecuteFailure
i <Re so urce Type name=" Sockets"> —

( -iresource Identifier name="summary" Total5ockets="0" TotalMessages="C
</ResourceType>
Parsers">
<Re so urce Type name=" -Char Format
name="summary" Threads="0" ApproxMemKB="0.00" Ms
iresourceIdentifier (Alt)— (* Ascii C
name="[Deleted]" Threads="2" ApproxMemKB="0.DD"
iresourceIdentifier Ebcdic C Simp
name="[Administration]" Threads="2" ApproxMemKB=
iresourceIdentifier Chinese r Korean
</ResourceType> 5ecurity"> Trad Chinese C
<ResourceType name=" name="summary" TotalCacheEntries="0" TotalOperat Japanese C Thai f-
iresourceIdentifier " Russian
</ResourceType>
<ResourceType name=" - Dotïïet GC">
iresource Identifier
</ResourceType> name="summary" ExplicitGCCount="0" GenGCollectic
V CR/LF IT Indent I EDI
<ResourceType name=" -
T" Validate
iresource Identifier - DotWet App Domains">
BrowseNewt |
iresource Identifier name="summary" CurrentlyInUseInMB="0" TotalAlloc
</ResourceType> name="DefaultDomain" CurrentlylnUseInMB="G" Tote BrowsePrev I
il “
Copybook I
To make it easier to read the statistics data, copy the data into Windows Notepad, save it as
an XML file, and open it in a web browser.
a. Select the message data in RFHUtil, right-click the selected data, and then click Copy.
b. Open Windows Notepad.
c. Right-click in the Notepad session and then click Paste.
d. Save the file in c:\iabfiies\Labio-stats directory as statistics.xml and then close
Windows Notepad.
e. In Windows Explorer, locate the statistics.xml file and then double-click it to start a web
browser window.
Review the statistics. When you are finished, close the web browser window.

Student Exercises
Exercise clean up
1. In the IBM Integration web interface, stop the collection of resource statistics.
Click the down pointing arrow on the right side of the server! integration server and
then click Resource statistics off.
2. In the IBM Integration web interface, stop message flow accounting and statistics.
Click the down pointing arrow on the right side of the Transformation_Map message
flow and then click Statistics off.
3. Close the RFUtil session.
_ 4. Delete the Transformation_map message flow components from the server! integration
server on IIBNODE_WITHQM.
5. In the IBM Integration Toolkit, stop the Flow Exerciser.
6. In the IBM Integration Toolkit Integration Nodes view, right-click the server! integration
server and then click Stop recording.
End of exercise
Student Exercises

In this exercise, you used the IBM Integration web interface to enable integration node and
message flow statistics collection. You then used the IBM Integration web interface to view
the resource and message flow statistics.
Finally, you used IBM MQ Explorer to create a subscription for resource statistics.
• View integration node statistics in the IBM Integration web user interface

Student Exercises
Exercise 11.Administering workload management

policies
In this exercise, you use the IBM Integration web interface and IBM
Integration commands to create workload management policies. You
also attach workload management policies to a message flow.

• Create workload management policies
• Attach a workload management policy to a message flow
Introduction
Administrators can use a workload management policy to control the
workload management attributes without the need to redeploy the
message flow or integration services resources.
Workload management policies are set at the message flow level. Using
a workload management policy, the system administrators can
complete the following tasks:
• Restrict the maximum rate at which a message flow can run
• Cause a notification message to be sent if the number of messages
that arrive in the flow exceeds a specified threshold
A workload management policy can be set up and administered within
the Integration Registry by using the IBM Integration web interface,
IBM Integration commands, and the IBM Integration API.
In the first part of this exercise, you create a workload management
policy by using the IBM Integration web interface.
In the second part of the exercise, you attach a workload management
policy to a message flow. You also use message flow statistics to
observe the effects of the attached workload policy on the message
flow.
Requirements
• The IIBNODE_NOQM integration node that was created in Exercise
1
©Copyright IBM Corp. 2015 Exercise 11. Administering workload management policies 11-1
Student Exercises
• Lab files in the c : \iabfiies\Labii-WLM directory

podrá reproducir o
Student Exercises
Part 1: Create a workload management policy
In this part of the exercise, you use the IBM Integration web interface to create a workload
management policy that is defined within a configurable service.
_ 1. Open the IBM Integration web interface for the IIBNODE_NOQM integration node.
_ 2. In the navigator, expand Operational Policy.
_ 3. Click the down arrow on the right
side of Workload Management and then Overview
click Create.
» ¿1 IIBNODE_NOQM ▼
► = Servers -w -*•
Operational Policy
► Configurable
» Quick View
Services ▼
► (ffj MQEndpoint ▼
► ¡£p MQTTPublish ▼
► MQTTSubSCribe v Version
Node Name
1
l®ÿ Workload Management V Admin Se CL
► £0 Data fo Workload Management e

► ^ Security Create SCI
► gg Monitoring Long Descr
_ 4. For the policy name, type: DefauitwimPolicy

_ 5. The Additional Instances property specifies the additional threads that the integration
node can use to service the message flow.
For this exercise, set the Additional Instance property to 3.
Also, set the Start additional instances when flow starts property to Yes.
_ 6. The Processing Timeout property is the maximum time a message flow can process a
message before taking a specified action. The time is measured in seconds. The time
For this exercise, set the Processing Timeout to
r _#j
I# I 60. Information -------------------------------------------
is taken from the point that the message is received on an input node.
Automatically stopping a flow by using the workload management policy, stops the flow after
the specified amount of processing time.
There is no way to know whether the message flow was in a loop, only that it used too many
cycles, and should be stopped. When restarted, it might automatically restart again or
© Copyright IBM Corp. 2015 Exercise 11. Administering workload management policies 11-3
podrá reproducir o
continue processing until finished. If problems continue with the message flow, you can
manually force it to stop by using
the mqsistopmsgflow -f command.
J

podrá reproducir o
Student Exercises
7. The Processing timeout action property specifies the action to take when the
Processing timeout is exceeded.
For this exercise, set Processing timeout action to restartExecutionGroup, which
restarts the integration server. Set the Processing timeout to 60.
Operational Policy - WorkloadManagement : DefaultWImPolicy

0 Overview
Policy URL f^j'l Save Hä. Save As ^ Revert

/apivl /policy/Workload Management/Defau ItWlm Policy
Use a policy io control the operational behavior of a message flow at run time. [ Afore... ] Oct 21, 2015, 7:27:29 AM x
►Targets and Limits r Additional Instances
Additional instances
▼ Start Mode
Maintained
►Transactional ity
▼ Unresponsive Message Flows

_ 8. Click Save.
_ 9. Create another workload management policy that is named TenAdditionaiinstances
Use the same values that you used for the DefaultWImPolicy policy but set the
Additional instances property to io.
Part 2: Attach a workload management policy to a message flow

In this part of the exercise, you deploy a message flow and then attach a workload
management policy. You also use message flow statistics to observe the effects of the
Processing timeout action

Restart execution group
Processing timeout
seconds
attached workload policy on the message flow.

_ 1. Using the IBM Integration web interface, deploy the BAR file simpieFiow.bar (in the
C:\iabfiies\Labii-WLM\resources directory) to the serverl integration server.
podrá reproducir o
Student Exercises
2. The simpieFiow.bar file contains the Transformation_Map application, which contains the
Transformation_Map message flow.
Expand the Transformation_Map application until you see the Transformation_Map
message flow.
You should see that the Transformation_Map message flow is running.
- $ IIBNODE_NOQM T := Servers v T ^
server! w g Services g REST AP Is g
Applications
53 Transfornnation_Map ▼
^ Libraries T as Message
Flows
0)H Transfornnation_Map -*■
Sutjflows ► Q3, Resources S

References
3. Click the down arrow on right side of Transformation_Map message flow and then click
Attach Policy. The Operational Policy view opens.
4. The Operational Policy view shows the list of available workload management policies for
Click Attach policy for the DefaultWImPolicy workload management policy and then click
Apply.
TransformationJVlap - Message Flow

y Overview [yy Statistics Operational Policy
Available policies
Att
ach policy
No attached policy 0
DefaultWIm Policy <s>
Ten Additional! nstaces 0
You should see a message that the policy was successfully attached.
5. Enable message flow statistics for the message flow.
6. Click the Statistics tab to view the message flow statistics for the Transformation_Map
T Flow £ Apply Cancel

Policies
message flow.

podrá reproducir o
Student Exercises
7. Change the information that the first graph displays to Number of threads in pool.
Flow analysis
Updates from 07:34:02 Pacific Daylight Time (<1 minute ago). Last updated at 07:34:22 Pacific Daylight Time Time range: Session
Average Elapsed Time/ Invocation (ms)
Average CPU Time/ Invocation (ms)
Total CPU Time Waiting for Input Message (ms) Total
Elapsed Time Waiting for Input Message (ms) Maximum
7:34:04 AM 7:34:08 AM 7:34:12 AM 7:34:16 AM 7:34: 7:34:06 AM
CPU Time (ms)
7:34:10 AM 7:34:14 AM 7:34:18 AM
Average Elapsed Time/ Invocation (ms) Maximum Elapsed Time (ms)
Maximum Size of Input Messages (Kb) Minimum CPU

Time (ms)
Minimum Elapsed Time (ms)
7:34:04 AM 7:34:08 AM 7:34.12 AM 7:34.16 AM 7:34: 7:34:06 AM Times Maximum Number of Threads Reached Total
7:34:10 AM 7:34:14 AM 7:34:18 AM
CPU Time (ms)
You should see that one thread is running.

8. Stop and then start the message flow.
9. In the Statistics view, you should now see that four instances are available in the
thread pool (the original instance plus three more instances).
=Ha TransformationJVlap - Message Flow

j1 Overview |rv Statistics ^ Operational Policy
Flow analysis
T Updates from 07:11:08 Pacific Daylight Time (2 minutes ago). Last updated at 07:13:11 Pacific Daylig ht Time Time range: Session
10. Detach the DefaultWImPolicy policy.

Click down arrow to the right of message flow and then click Detach policy.
11. Attach the TenAdditionallnstances workload management policy to the message flow.
13. View the Number of threads in pool in the Statistics view. You should now see that 11
instances are available in the thread pool.
podrá reproducir o
▼ Updates from 07:38:05 Pacific DaylightTime (1 minute ago). Last updated at 07:39:05 Pacific Daylight Time Timerange: Session
Student Exercises
- Transformation_Map - Message Flow
0 Overview Statistics 9 v Operational Policy
Flow analysis
Exercise clean up
_ 1. Stop the Transformation_Map message flow application from serverl on the
IIBNODE_NOQM integration node.
_ 2. Delete all flows and resources from serverl on the IIBNODE_NOQM integration node
_ 3. Close the IBM Integration web interface browser window for IIBNODE_NOQM.
End of exercise
podrá reproducir o
Student Exercises

In the first part of this exercise, you created a workload management policy by using the IBM
In the second part of the exercise, you attached a workload management policy to a message
flow. You also used message flow statistics to observe the effects of the attached workload
policy on the message flow.

Student Exercises
Exercise 12.Recording and replaying message flow

data

In this exercise, you define message flow events and then record them
in a database. You also replay messages and capture and report failed
events.

• Activate message flow monitoring and store events in a database
• Enable an integration node to connect to a database with ODBC
• View event messages in the IBM Integration web user interface
• Replay a message to an IBM MQ queue by using the IBM
Integration web interface
Introduction
This exercise uses an application that contains several message flows
(summarized in the following figure).
Student Exercises
The application processes stock trade requests, and each trade runs
© Copyright IBM Corp. 2015 Exercise 12. Recording and replaying message flow data 12-1
five message flows: TRD1, TRD2, TRD3*, TRD4, and TRD5. The TRD3
message flow is selected based on the customer type:
• If the customer type is “Gold”, the TRD3a message flow runs.
• If the customer type is “Regular”, the TRD3b message flow runs.
• If the customer type is “Guest”, the TRD3c message flow runs.
The TRD6 flow runs if a validation failure occurs in the first messaqe
flow, TRD1.
Several of the message flow nodes have monitoring points that are
defined on them by using the Monitoring node properties. These
monitoring points publish certain items of the message payload data.
The Data viewer in the IBM Integration web user interface uses this
data to access processed messages, and to resubmit (replay) the
message for reprocessing.
r / Note ---------------------------------------------------------------------------------------------- ^
Flow monitoring can also be achieved noninvasively by using monitoring templates, which
are not covered in this lab.
V________________________________________________________________________ y
In this second part of this exercise, you set up a DB2 database for
record and replay database. You also configure the JDBC connection to
the database, and the IBM MQ queues that are required for the Trades
application. Command and batch files are provided in the
C:\iabfiies\Labi2-RandR\instaii directory to automate this process.
Requirements
• IBM MQ V8 and a queue manager that is named IIBQM
• IBM DB2
• An IBM Integration Bus integration node with an IBM MQ queue manager
specified on the integration node. The exercise instructions refer to
IIBNODE_WITHQM that is created in Exercise 2
• Lab files in the C:\iabfiies\Labi2-RandRdirectory
• The IBM MQ queues (created in the exercise): TRADE.VALIDATE.IN,
TRADE.CUST.TYPE.IN, TRADE.GOLD.IN, TRADE.REGULAR.IN,
TRADE.VALIDATION.FAILURE.IN, TRADE.GUEST.IN,
TRADE.RECONCILIATION.IN, TRADE.COMPLETE.IN,
TRADE.COMPLETE.OUT, TRADE.FIX.IN, TRADE.FIX.OUT,
TRADE. REPLAY. INPUT

Student Exercises
Part 1: Set up the environment for record and replay
In this part of the exercise, you set up the record and replay database, JDBC connections,
and the queues that are required for the Trades application.
Command and batch files are provided in the C:\iabfiies\Labi2-RandR\instaii directory to
automate the setup process. You can examine any of the files by using Notepad.
_ 1. Create the queues and subscriptions for the TRADES message flows on the queue
manager that is specified on the integration node.
_ a. Start an IBM Integration Console as the administrator (right-click the IBM Integration
Console shortcut on the desktop and then click Run as administrator).
_ b. In the IBM Integration Console, change directories to
C:\labfiles\Labl2-RandR\install\MQsetup. Type:
cd C:\labfiles\Labl2-RandR\install\M2setup
_ c. Enter the command to create the queues on the integration node queue manager
IIBQM:
runmqsc IIBQM < TradeQueues.mqsc d. In IBM MQ Explorer,
verify that the following objects were created:
• The local queues TRADE.VALIDATE.IN, TRADE.CUST.TYPE.IN,
TRADE.GOLD.IN, TRADE.REGULAR.IN, TRADE.VALIDATION.FAILURE.IN,
TRADE.GUEST.IN, TRADE.RECONCILIATION.IN, TRADE.COMPLETE.IN,
TRADE.REPLAY.INPUT, and RECORD.REPLAY.SUB
• The subscription RECORD.REPLAY.SUB with the topic string of
IIBNODE_WITHQM/Monitoring/#
_ 2. Create the record and replay database.
_ a. In the IBM Integration Console, type the following commands to create the DB2
database and tables:
cd ..\DBSetup CreateTRADES_Tables.bat
This command opens a DB2 command window and creates the record and replay
tables in the TRADES database. The tables are re-created so that this lab exercise
starts with a clean display of monitor events, and so that new events are easily
viewable in the IBM Integration web user interface.
It might take a few minutes for this batch file to complete.
Verify that the command ran successfully and then press Enter in the DB2
command window to close the window.
_ 3. Define the JDBC connections from the IIBNODE_WITHQM integration node to the
TRADES
database tables.
podrá reproducir o
Student Exercises
In the IBM Integration Console, type the following command:

Conf igureJDBC
_ 4. Import the data store configurable service.

The record and replay function uses a data store, which represents the database that
holds the captured monitoring events. The data store is defined to the integration
node by using configurable services.
You can define the configurable services manually. For this lab, the configurable
services are already created but they must be imported into the IIBNODE_WITHQM
integration node.
_ a. In the IBM Integration web interface for IIBNODE_WITHQM, expand the
Operational
Policy folder.
_ b. Click the down arrow to the right of the Configurable Services folder and then click
Import *.configurableservice.
^ $ IIBNODE_WlTHQM ▼ Overvi
- ¡jS Servers T
► ^ serverl ▼
- fia Operational Policy ▼
► Configurable Services
iâa Configurable Services
Qu
(Rj MQEndpoirt T(SJ Create
MQTTPublish T (R§! Import '.configurableservice
MQTTSubscribe -w(Ry
Workload Management
__ C. Browse to the C: \labfiles\Labl2-RandR\configurable_services directory and then

select the Trades_data_capture_store. configurableservice file. Click OK.
_ d. The Trades configurable service should now be listed under the Configurable
Services
> DataCaptureStore folder.

podrá reproducir o
Student Exercises
5. Following the same process as in the step 4, import Trades_source.configurableservice and
Trades_BPM_Data_Destination.configurableservice from the C:\labfiles\Labl2-
Filter Options... ^§a Trades - DataCaptureStore Configurable Service

▼ $ IIBNODEJMTHQM ▼
Q Overview
▼ Servers ^
► 45 ? serverl ▼
▼ |i] Operational Policy
-r Configurable Services ▼
► 5 ActfvityLog
► 5 Aggregation
► 5 CDServer ▼
► 5 CICSConnection Properties
► 5 CORBA commitCount
10
► 5 Collector useCoordinatedT ransaction false
► 5 ConnectoriProviders
thread Pool Size 10
► 5
queueName SYSTEM. BROKERJDC RECORD
DataCaptureSource ▼ 5 data Source Name TRADES
DataCaptureStore schema IIBAOMIN
5 DefaultCaptureStore ▼
egForView serverl
5 Trades ▼
► 5 DataiDesti nation backoutQueue SYSTEM. BROKE RJ DC
.BACKOUT
egForRecord serverl
► 5 DecisionServiceRepository
commitlntervalSecs 5
RandR\configurable_services directory.
You should now have three new configurable services for the Trades application:
• DataCaptureSource > Trades_Source
• DataCaptureStore > Trades
• DataDestination > Trades Redirect to BPM
^ gi IIBNODE_WITHQM -w•r Servers ■m►
^ serverl -rr - Bn Operational Policy
— Config urable Services
► y ActivityLog
► V Aggregation
► |Vj CDServer
► ¡Vj CICSConnection
► |V| CORBA
► ¡Vj Collector
► y ConnectorPnoviders -*■ V
DataCaptureSource
V DataCaptureSourceTemplate -r iV,
Trades_Source -r
- gj DataCaptureStore
j\j DefaultCaptureStore -r |\j Trades »■
- ^ DataDestination
jVj Trades_RedBrect_to_BPM -w
[*\ Wft4Ano(iHnaKnnTQmnliita _____________________________
podrá reproducir o
Student Exercises
The Trades_Source service subscribes to the topic
$SYS/Broker/iiBNODE_wiTHQM/Monitoring/serveri/#. So this data source collects all monitoring

events that the applications in the serveri integration server generate. This data source does
not collect events that are emitted in other nodes or integration servers.
Part 2: View messages in the IBM Integration web interface

_ 1. In the IBM Integration web interface, expand Data > Data Capture Stores in the navigator
and then select the Trades data capture store.
The events list for the Trades database is empty.
IBM Integration
No data to display
Welcome, Default ’
Filler Options...
0 Data Capture
Store
T £ IIBNODE_WITHQM T
0 Data viewer ^Replay list
> ¡o Servers »
> tj Operational Trades ^ Mark for replay
Policy T 0Data
Ÿ Customize ▼ ^ Filter ▼ Display Time ▼ ^Refresh
T g Data Capture |p No filler applied
Stores Q Trades
> Security □ Event time Local
Transaction ID
Parent
Transaction ID
Global
Transaction ID
Data Errors
> 0 Monitoring
2. In the IBM Integration web interface, deploy the BAR File that is named Trades .bar
from the c:\iabfiies\Labi2-RandR\appiication directory to the serveri integration
server.
3. Validate that the Trades application is deployed.
Expand the Trades application in the IBM Integration web user interface. Verify that
the application contains eight message flows. The message flows are run in sequence,
with just one of the TRD3* messages flows used, depending on the type of customer.

podrá reproducir o
Student Exercises
^ $ IIBNODE_WlTHQM ▼ T
Servers -v» serverl

g Services g REST APIs -
¡jEJ, Applications T ^ Trades Tg
Libraries gi iMessage Fiowsj
§1 TRD1_Validate ▼ gl
TRD2_Custoiner_Type T gffl T RD
3a_Gold_Trade ▼ g®
TRD3b_Regular_Trade ▼ gffl
TRD3c_Guest_Trade ▼ gSI
TRD4_Final_Reconciliation gBI
TRD5_Trade_Complete ■*- ga
TRD6_Failed_Trade_Woriiflow w¿5^
Subflows
4. Enable flow monitoring on the message flows in the Trades application.

Type the following command to enable monitoring on each of the message flows:
cd ..\•\monitoring
enableMbnitoringTrades
10 I
r l]
Information
A
This command runs the integration node commands:
mqsichangeflowmonitoring IIENODE_WITHQM -e serverl -k Trades -
f TRDl_Validate -c active
It also runs equivalent commands for the other message flows in the Trades application.
If you redeploy the Trades application, the flow monitoring status is reset. You must
enter the enabieMonitoringTrades command again to reactivate flow monitoring.
V _____________________________________________________________________ J
_ 5. Use RfhUtil to send some new events to the Trades application queue
TRADE.VALIDATE.IN on the IIBQM queue manager.
_ a. In RFHUtil, open the file for a “Gold” customer:
C:\labfiles\Labl2_RandR\data\TradeMessageGold_BNY347290.xml
_ b. Send one instance of the data to the queue TRADE.VALIDATE.IN on IIBQM.
podrá reproducir o
Student Exercises
_ c. Send a message to TRADE.VALIDATE.IN for a “Regular” customer:

C:\labfiles\Labl2-RandR\data\TradeMessageRegular_BNY809092.xml.
_ d. Send a message to TRADE.VALIDATE.IN for a “Guest” customer:
C:\labfiles\Labl2-RandR\data\TradeMessageGuest_BNY348475.xml.
6. Click Refresh on the Data viewer in the IBM Integration web interface to show the new
events.
r rr Note _________________________________________________________________ A
If you receive an error when trying to access the Data Capture Store, restart the server!
integration server and try to access the Data viewer again.
v ________________________________________________________________________ y

Student Exercises
Data Capture Store
Q Data viewer Replay list
Trades ▼ Mark for replay & Customize ▼ Filter ▼ Display Time v ^Refresh
No filter applied
Q Event time Local Parent Global Data Errors Event name

Transaction ID Transaction ID Transaction ID
□ CR100200-A BNY809092 APPL $500 * Trade

2015-10-20 18:21:58.268 UTC reconciliation
A
□ 2015-10-20 18:22:19.781 UTC GU123456 BNY348475 MSFT $5000 % - Trade
reconciliation
□ CR100200-A BNY809092 APPL $500 % -

Trade
□ CR100200-A BNY809092 -
Trade instruction
2015-10-20 18:21:58.125 UTC %
received
-
Trade instruction
□ 2015-10-20 18:22:19.684 UTC GU 123456 BNY348475 %
received
-
Trade instruction
□ 2015-10-20 18:22:31.490 UTC CR100200-A BNY809092 %
received
□ 2015-10-20 18:21:58.234 UTC CR100200-A BNY809092 APPL $500 % - Regular Trade:
Processing
□ CR100200-A BNY809092 APPL $500 -
Regular Trade:
2015-10-20 18:22:31.496 UTC %
Processing
□ GU123456 BNY348475 MSFT $5000 % Guest: Start
2015-10-20 18:22:19.733 UTC
□ CR100200-A BNY809092 APPL $500 -
Deciding customer
2015-10-20 18:21:58.162 UTC %
type
□ GU 123456 BNY348475 MSFT $5000 %
Deciding customer
2015-10-20 18:22:19.684 UTC
type
□ 2015-10-20 18:22:19.687 GU 123456 BNY348475 MSFT $5000 % Decision: Guest
7. The Data viewer uses the standard column heading names. You can customize the
headings so that they are more descriptive.
There are several options for customizing the column headings:
• You can change the display name of each column by double-clicking the required
display name, and entering another name. These changes are stored in the
Integration Registry, and are retained uniquely for each data capture store. All users
who display data from the same data capture store see the changes that this user
makes. If you want to record and view data with different headings, record the
events in a separate data capture store.
• You can select or clear any of the recorded fields for display.
• You can override the width of the displayed column. The widths can also be
overridden by using the divider bars.
Click Customize and change the column heading name as follows:
__a. Change Local Transaction ID to Customer number.
__b. Change Parent Transaction ID to Trade number.
__c. Change Global Transaction ID to Stock/Trade amount.
__d. Change Event name to Trade processing stage and change the field width to 160.
__e. Change hasBitstream (Data) so that it is not selected for display.
Student Exercises
w Markfor replay ; Customize

r
Customize Columns
Select the columns to display in the Data viewer. Double-click a name or width that you want to edit. You can sort the
order by clicking the header. You can also reorder tine columns and change their widths by using the header In the
main Data viewer and saving your changes here. The saved changes apply only to the current data capture store:
other data capture stores retain their current settings.
Field ID Display Maine Width (px)
eve ntTi me stamp F Event time 160 j
localTransactlonld F Customer number 100
parentTransactionld F Trade number 100
globali ransactionld F Stock/Trade amount 100
hasBitstream □ Data 70
d
__ f. Click Apply. The column names are updated with the new values.
8. You can click the column headers to change the order of the events in the Data
Build Filter
Rules
viewer. For example, click the Event time column to display the oldest events first.
'll
u t^_= , v-K,“jr
Trades - Mark for replay Customize — ■ 3jt* Filter ▼
Customer Mumbeij x - starts with ■* CR

-J L±J
Filter Clear Cancel
9. _ You can limit the data that is displayed in the Data viewer by using the Filter
function. a. Click Filter.
__ b. Specify the filter criteria of: Customer number starts with CR
c. Click Filter to activate the defined filters.
i i ?ni5-1 ridn cRinn^nn-A R M Y f u i A P P I -
_ 10. You can add more filters to the display.

__ a. Click Filter again, and click the green plus sign to add a second filter.
__ b. Specify the filter criteria Of: Trade processing stage contains Complete.

Student Exercises
__c. Click Filter to activate the new filter.
r '"7' Note ______________________________

J
The values for each filter are case-sensitive.
V _____________________________________
11. Clear the filters by selecting Filter from the Data viewer tab and then clicking Clear.
Part 3: Replay messages

In this part of the exercise, you configure the IIBNODE_WITHQM integration node to replay
messages. Replay allows messages that are listed on the IBM Integration web interface to be
selected and sent to the same, or a different, message flow for further processing.
In this lab, you replay the message by sending it to a separate IBM MQ queue; another application
does not process it.
Depending on the message flow and the types of events that you want to replay, the replay queue
might be the same input queue that the original message flow uses or a different queue. The replay
might also be a separate (and different) message flow.
_ 1. Review the configurable service that was defined to enable the replay.
__a. In the IBM Integration web interface, expand the Configurable Services folder.
__b. Select the DataDestination > Trades_Redirect_to_BPM configurable service.
This configurable service enables messages to be routed to the TRADE.FIX.IN queue on
the IIBQM.
In this lab, a simple message flow in the Trades application processes this queue. In
another scenario, a business process management application might process it and
amend the message before sending it to the Trades application again.
_ 2. In the IBM Integration web interface Data viewer, enable the Data column.
__a. Click Customize,
__b. Enable the hasBitstream (Data) column.
__c. Click Apply.
_ 3. Select some of the messages for replay.
__a. Select the check box for the message to enable it.
__b. Make sure that at least one of the selected messages shows the colored bitstream icon
in the Data column.
__c. Click Mark for replay, which is now active.
Student Exercises
Data Capture Store

Q Data viewer ££> Replay list
Trades - Mark for replay $!* Customize ▼ Filter ▼ Display Time - ^ Refresh
Nofitter applied
Trade
Customer Stoek/Trade
Ü Event time Trade Number Data Errors processing
Number amount
stage
□ 2015-10-20 CR1Q0200-A BNY809092 APPLS500 - Trade

18:22:81.499 reconciliation
UTC
2015-10-20 CG123456 BNY347290 %' Trade instruction
0 18:36:13.032 received
UTC
2015-10-20 - Trade instruction

0 CR100200-A BNY809092 %
18:21:58.125 received
UTC
n 9M*i-HV?n minrfR RWVîaa?*; IS. - Trade insfnirlinn
4. Clicking Mark for replay displays the Replay list. However, you still cannot start the Replay
function. You must first select the Data Destination.
On the Data Destination menu, select the destination Trades_Redirect_to_BPM.
Data Capture Store

y Data viewer [> Replay list
Data Destination ¡Select destination x ▼ S* Replay All

T rades_Redirect_to_B PM
e Customer Trade S
5. On the Replay list view, click Replay All (or you can replay each item individually by clicking
the green arrow next to each message).
You should see that the item that contained the data bitstream was successfully sent to the
replay destination. It does not mean that the application successfully processed data; it was
successfully sent to the receiving destination.
You cannot reply items that do not contain a data bitstream.

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. No Student Exercises
Data Capture Store
Data
Destination
Q Data viewer [> Replay list
Trades_RedirectJo_8PM [> Replay All
Trade
Customer Trade Stock/Trad e
Replay Status Event time Data Errors processing
Number Number amount stage
*!/ P ^ Success 2015-10-20

CG123456 BNY347290 % "
Trade
18:36:13.03 Instruction
2 GMT received
p ¡Q¡ Success 2015-10-20
CR100200-A BNY809Q92 %
Trade
5 GMÍT received
6. Confirm that the messages were sent to the replay queue.

__ a. Open IBM MQ Explorer.
__ b. Select Queues under IIBQM.
__ c. The Current queue depth of TRADE.FIX.OUT should increase by 2 (or the number of
messages that you sent for replay).
Part 4: Handle failed messages

If a message flow encounters an error during processing, it can be captured and reported by using
the IBM Integration web interface.
To enable this feature, the monitoring point on the message flow node must include the
$ExceptionList string in the monitoring event message.
_ 1. Using RFHUtil, send a bad message to the Trades application.
__ a. Open the file C: \labfiles\Labl2-RandR\data\TradeMessage_BadMessage.xml
__ b. Send the message to TRADE.VALIDATE.IN queue on IIBQM.
Although this message is a valid XML message, it is missing a required XML element. It
fails validation on the ReceiveTrade node because validation is set to Content and
Value
_ 2. In the IBM Integration web interface, you should see three new entries.
The Trade processing stage for the first event is Gold customer Processing trade.
The Trade processing stage for the second event Trade instruction received.
The Trade processing stage for the third event is Data validation failure.
Student Exercises
I j Data viewer [> Replay list
Trades Mark for replay F[< Customize tjjr- Filter ~ Display Time rr Refresh
3ji>No flier applied
Event time Trade Number Data Errors
Trade
□ Customer
Number
Stocki'Trade
amount processing
stage
CG123456 BNY347290 IBM $1000 % "

n 2015-10-20 Gold customer
18:36:13 135 UTC Processing trade
2015-10-20 CG123456 BNY590012 % Trade instruction

n 19:19:36.538 received
UTC
□ CG123456 BNY590012 Data validation
2015-10-20
19:19:36.537 failure
UTC
3. Failed events can be highlighted in the IBM Integration web interface Data viewer by
customizing the displayed columns. Click Customize.
_ a. If it is not already selected, enable the hasException (Errors) column.
_ b. Click Apply.
The Errors (hasException) column shows a red cross for all monitoring events that
contain the $ExceptionList data.
Exercise clean up
_ 1. In the IBM Integration web interface, stop the running application and then delete it from the
_ 2. Close RFHUtil.
_ 3. Close the IBM Integration web interface.
End of exercise

Student Exercises

In Part 1 of this exercise, set up the environment for recording and replaying messages. Set up
included building the database tables and importing the configurable services.
In Part 2 of this exercise, you viewed event messages in the IBM Integration web interface,
customized the Data viewer, and defined filters to limit the data that is displayed.
In Part 3 of this exercise, you replayed messages by sending them to an alternative queue.
In Part 4 of this exercise, you configured the message flow to generate the $ExceptionList string and
identified failed messages in the IBM Integration web interface.
• Replay a message to an IBM MQ queue by using the IBM Integration web interface
Student Exercises

podrá reproducir o Student Exercises
Appendix A. Exercise solutions
Exercise 9, Identifying runtime problems
Part 1
1. Queue manager dead-letter
queue = DLQ; IN queue backout
II Dc- #
queue = IN_BOQ J zl.
Out
Answer:
The message is rolled back to the input queue. After rollbacks reach the backout threshold, the
message is put to IN_BOQ
U -+o
D
-+ Compute
E> 4»
Failure
Failure2
IN TxMode=No
Out
Answer:
The message is discarded because the flow is not transactional (TxMode=No) and cannot be rolled
back. The MQInput node Catch terminal is not wired so, you cannot consider that option.
© Copyright IBM Corp. 2015 Appendix A. Exercise solutions A-1

podrá reproducir o
Student Exercises
3. Queue manager dead-letter queue = DLQ; IN queue has no backout queue.
Out
Answer:
The message is rolled back to the input queue. After the backout threshold is reached, the
message is put to the DLQ. The MQInput node Catch terminal is not wired.
Out
Answer:
The message is propagated through the Compute node Failure terminal. The message that is
written to the Failure queue.
Catch
Answer:
The message is propagated through the Compute nodes Failure terminal; this action fails, so it is
propagated to the Catch terminal and thus to the Catch queue, regardless of the transactional
nature of the flow.
A-2 Integration Bus V10 Administration © Copyright IBM Corp. 2015

podrá reproducir o
Student Exercises
Failure
Failure2 at
10 gr E
>=
IN TxMode=Ye: Compute
■
Catch
Out
Answer:
The message is written to the Failure2 queue (regardless of transaction mode). 7.
Queue manager dead-letter queue = DLQ; IN queue backout queue = IN_BOQ
*
Faillirez
Failure
E
Catch
Out
Answer:
The message is put onto the IN_BOQ after 2*BackoutThreshold retries that failed in FAILURE2. If
the IN_BOQ was full or PUT is disabled, the integration node tries to put the message onto the
DLQ. If that fails as well, the message loops between the MQInput node and the Failure2
MQOutput node.
Part 2
After submitting the test message, you should see that message did not go to the REPLY queue as
expected. Instead, it went to the CATCH queue.
To determine why the message flow failed, enable Trace nodes on the integration server and then
run the message flow again. The command to enable Trace nodes on server! is:
mqs i change trace IIBNODE WITHQM -n on -e serverl

Student Exercises
In the Windows Event Viewer Application log you see a Warning message:
( IIBNODE_WITHQM.serverl ) Operating system error ''The system cannot find the path
specified.
'' opening trace file ''C:\labfiles\TraceFiles\SimpleFlowtrace.txt'' for trace node
'SimpleFlowWithTrace.Trace'.
The trace node 'SimpleFlowWithTrace.Trace' attempted to open the trace file

''C:\labfiles\TraceFiles\SimpleFlowtrace.txt'' but the operating system reported the
error ''The system cannot find the path specified.
''. Message flow processing will continue, but trace output will not be written. The
node will continually attempt to open the file until it succeeds.
If the name or location of the file was not specified correctly, then correct the
message flow configuration and redeploy the integration node. If the file could not
be opened due to an environment or system error, take appropriate action to correct
this situation. This message indicates that the message flow contains a Trace node
that is attempting to write its output to a directory that does not exist. Recall
that if a Trace node is sending its output to a file, the directory path that is
specified in the trace node properties must exist, or the file is not created. To
correct this problem, you must either create the specified directory or modify the
.bar file to change the path. If you correct this problem before correcting the next
error in the log, the trace output that is written to the file provides further
details on the error.
Create the folder c : \iabfiies\TraceFiies and then rerun the message flow.
When you examine the properties for the Trace node that is connected to the CATCH terminal,
you should see that it is writing to a User Trace, not a file.
Activate a User Trace on the message flow and then rerun the flow. The command is:
mqs i change trace IIBNODE_WITHQM -e severl -u -f
SimpleFlowWithTrace -k SIMPLEFLOW_WITH_TRACE -1 debug
Run the gettrace.cmd in the C:\iabfiies\Toois directory to convert the trace file and open it in
Notepad.
The error message in the log shows that the message flow fails with a reason code 2085 when it
attempts to write to queue REPLYx, which does not exist. To correct this problem, you must
define this queue to the queue manager or modify the queueName property for the REPLY node
to a queue name that exists.
MessageException BIP2666E: An error occurred when opening queue ''REPLYx'' on
destination queue manager ''IIBQM''. State = '-1' ''MQW101'' '2085' '''' An error
occurred when opening a queue. The reason code from the MQOPEN is displayed as the
3rd (native error) state.
Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application
Programming Reference manual to establish the cause of the error,
Student Exercises
taking any appropriate action. It may be necessary to restart the integration node
after you have performed this recovery action.

A complete copy of a sample user trace is provided in the C:\iabfiies\Lab09-PD\soiution

directory.

Student Exercises

IMPRESO POR:
Jafert Frank
Rabines
Escorza
<jrabinese@su
nat.gob.pe>. La
impresión está
destinada
únicamente
para uso
personal y
privado. No se
podrá
reproducir o
retransmitir
ninguna parte
de este libro
sin la
autorización
previa del
editor. Todo
infractor será
objeto de
acciones
legales.
IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para
uso personal y privado. No se podrá reproducir o
retransmitir ninguna parte de este libro sin la autorización previa del editor. Todo infractor será objeto de acciones
legales.
IBM Training
Student Exercises
IBM Integration Bus V10 System Administration

Course code WM646 ERC 1.0
IBM Systems
Middleware
podrá reproducir o
Student Exercises
Trademarks
jurisdictions worldwide:
AIX® CICS® Data Power®
DB2® developerWorks® Express®
Informix® MQSeries® Notes®
ObjectGrid® PartnerWorld® PowerHA®
RACF® Redbooks® Tivoli®
WebSphere® z/OS®
Linux is a registered trademark f Linus Torvalds in the United tes, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other
countries, or both.
trademarks or trademarks (the "Marks") of VMware, Inc. in the United States and/or other jurisdictions.
December 2015 edition

The information contained in this document has not been submitted to any formal IBM test and is distributed on an “as is” basis without any
warranty either express or implied. The use of this information or the implementation of any of these techniques is a customer responsibility and
depends on the customer’s ability to evaluate and integrate them into the customer’s operational environment. While each item may have been
reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will result elsewhere. Customers
attempting to adapt these techniques to their own environments do so at their own risk.
© Copyright International Business Machines Corporation 2015.

This document may not be reproduced in whole or in part without the prior written permission of IBM.
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
podrá reproducir o
Student Exercises
Contents
Trademarks ........................................................................................................................................... v
Exercises description ........................................................................................................................ vii
Exercise 1. Integration node setup andcustomization .................................................................. 1-1

Parti: Get build and version information ................................................................................ 1-2
Part 2: Verify user authorizations ............................................................................................. 1-7
Part 3: Create an integration node and integration servers ...................................................... 1-8
Exercise 2. Connecting to IBM MQ ................................................................................................. 2-1

Part 1: Use IBM MQ Explorer to create the queue manager .................................................... 2-4
Part 2: Create the integration nodes and integration servers ................................................... 2-5
Part 3: Create the SYSTEM.BROKER queues and topics on the integration node queue
manager..................................................................................................................................... 2-8
Part 4: Create an MQEndpoint policy ..................................................................................... 2-10
Exercise 3. Using the IBM Integration Toolkit ............................................................................... 3-1

Part 1: Work with a simple message flow ................................................................................. 3-5
Part 3: Test the message flow by using the Flow Exerciser ................................................... 3-13
Exercise 4. Administering the IBM Integration Bus runtime components .................................. 4-1
Parti: Use the IBM Integration command interface ............................................................. 4-3
Part 2: Use the IBM Integration web interface ....................................................................... 4-6
Part 3: Use the IBM Integration API Exerciser ................................................................... 4-12
Part 4: Back upand restore the integration node ............................................................... 4-16
Exercise 5. Using file-based security to control administration access ..................................... 5-1

Part 1: Activate file-based security on the integration node ..................................................... 5-4
Part 2: Define administration roles and set file-based permissions .......................................... 5-6
Part 3: Test the IBM Integration web interface with security ..................................................... 5-8
Exercise 6. Using queue-based security to control administration access .............................. 6-1

Part 1: Set IBM MQ permissions for users ............................................................................... 6-4
Part 2: Test the default unsecured environment ....................................................................... 6-6
Part 3: Activate administration security and test the secured environment ............................ 6-10
Exercise 7. Implementing web services and web services security ........................................... 7-1
Part 1: Configure the integration node HTTP listener ............................................................... 7-4
Part 2: Review the message flows ........................................................................................... 7-5
Part 4: Test the web service application ................................................................................. 7-12
Part 5: Implement SSL for the web service application ........................................................... 7-14
Exercise 8. Using problem diagnosis tools ................................................................................... 8-1

Part 1: Examine and deploy the BAR file ................................................................................. 8-3
Part 2: Test the message flow ................................................................................................... 8-5
Student Exercises
© Copyright IBM Corp. 2015 Contents iii

podrá reproducir o
Part 3: Manage traces and Trace nodes ................................................................................... 8-6

Part 4: Administer the message flow debugger ...................................................................... 8-11
Exercise 9. Identifying runtime problems ............................................................................................ 9-1

Part 1 : Analyze message flow runtime failures ....................................................................... 9-2
Part 2: Isolate and identify problems ........................................................................................ 9-6
Exercise 10. Viewing runtime statistics ............................................................................................. 10-1

Part 1 : Enable message flow and resource statistics ........................................................... 10-3
Part 2: View message flow and resource statistics ................................................................ 10-5
Part 3: Set up subscriptions for resource statistics .............................................................. 10-10
Exercise 11. Administering workload management policies .......................................................... 11-1

Part 1 : Create a workload management policy ..................................................................... 11-3
Part 2: Attach a workload management policy to a message flow ......................................... 11-4
Exercise 12. Recording and replaying message flow data ............................................................ 12-1
Parti: Set up the environment for record and replay .............................................................. 12-3
Part 2: View messages in the IBM Integration web interface ................................................. 12-6
Part 3: Replay messages ...................................................................................................... 12-11
Part 4: Handle failed messages ............................................................................................. 12-13
Appendix A. Exercise solutions ........................................................................................................... A-1
iv Integration Bus V10 Administration © Copyright IBM Corp. 2015

Student Exercises
Trademarks
The reader should recognize that the following terms, which appear in the content of this training
document, are official trademarks of IBM or other companies:
jurisdictions
AIX® worldwide: Data Power®
DB2® CICS® Express®
Informix® developerWorks® Notes®
ObjectGrid® MQSeries® PowerHA®
RACF® PartnerWorld® Tivoli®
WebSphere® Redbooks®
z/OS®
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries,
or both.
trademarks or trademarks (the "Marks") of VMware, Inc. in the United States and/or other
jurisdictions.
© Copyright IBM Corp. 2015 Trademarks v

Student Exercises

Student Exercises
Exercises description
This course includes the following exercises:
• Integration node setup and customization
• Connecting to IBM MQ
• Using the IBM Integration Toolkit
• Administering the IBM Integration Bus runtime components
• Using file-based security to control administration access
• Using queue-based security to control administration access
• Implementing web services and web services security
• Using problem diagnosis tools
• Identifying runtime problems
• Viewing runtime statistics
• Administering workload management policies
• Recording and replaying message flow data
In the exercise instructions, you can check off the line before each step as you
complete it to track your progress.
Most exercises include required sections, which should always be completed.
It might be necessary to complete these sections before you can start later
exercises. Some exercises might also include optional sections that you might
want to complete if you have sufficient time and want an extra challenge.
Use the following user name and password to log in to course image:
User name: iibadmin Password: weblsphere
© Copyright IBM Corp. 2015 Exercises description 7

Student Exercises

Student Exercises
Exercise 1. Integration node setup and

customization

In this exercise, you complete the configuration tasks that prepare the IBM
Integration Bus environment for use. You also start the IBM Integration web
user interface to view the integration node and integration server properties.

Introduction
In the first part of this exercise, you verify the maintenance (fix pack) levels of
the IBM Integration Bus software.
In this second part of the exercise, you verify that the user ID that is used in
the lab exercises has administrative privilege to create and manage IBM
Integration Bus and IBM MQ resources.
In the third part of this exercise, you use the IBM Integration command
interface to create an integration node and report integration node properties.
You then use the IBM Integration command interface and the IBM Integration
web interface to create integration servers on the new integration node.
Requirements
• IB M MQ V 8
• User ID of “iibadmin” that is a member of the “mqbrkrs” group
Student Exercises
The required licensed programs are already installed on your exercise image. These licensed
programs include:
• IBM MQ V8
• IBM DB2 Express 10.1
Your user ID (iibadmin) is a member of the Windows “Administrators” group.
For all exercises in this course, use the information that is listed in this table.
Windows user ID for lab exercises iibadmin
Windows password for lab exercises weblsphere
IBM Integration Bus installation directory c:\Program Files\lBM\lIB\10.0.0.0\

IBM MQ installation directory c:\Program Files\lEM\Websphere M2
TESTNODE iibadmin
IBM Integration Bus integration node for
development
The lab image also includes the c:\iabfiies directory that contains, test files, scripts, and other
components that you use during the course exercises.
Part 1: Get build and version information

It is important to know the current software version and build level for all your software. In this part of
the exercise, you verify the maintenance (fix pack) levels of the IBM Integration Bus software.
_ 1. Get the software version information for the IBM Integration Toolkit.
_ a. From the Windows Start menu, click All Programs > IBM Integration Bus 10.0.0.0 >
IBM Integration Toolkit 10.0.0.0. Optionally, you can double-click the IBM Integration
Toolkit shortcut icon on the Windows desktop.
After a few moments, the Integration Toolkit opens and the Welcome page is presented.
On the Welcome page, you can learn more about the features of Integration Bus, see
what is new in IBM Integration Bus V10, and install language packs for the Integration
Toolkit.

Student Exercises
b. Close the Welcome page by clicking Go to the Integration Toolkit.

c. To display configuration information about the Integration Toolkit and the Integration Bus
environment, click Help > About IBM Integration Toolkit.
The About IBM Integration Toolkit window shows the Integration Toolkit version
information.
Student Exercises
The Build ID identifies the most recent fix pack that is applied. In this example, the build
ID is 10.0.0, dated March 13 2015 (20150313).
d. The icons across the About IBM Integration Toolkit window contain information about the
features that are installed in the Integration Toolkit. Click one or more of these icons and
explore the installed elements.
e. Click Installation Details in the About IBM Integration Toolkit window to show the
installed Integration Toolkit components and their versions.
Within the Installation Details page, you can select tabs to view the installed components,
the IBM Integration Toolkit installation history, the installed features, and plug-ins.
Installed Software Installation History Features Plug-ins Configuration
Name Version Id
c> Dali Java Persistence Tools - JPA Support 3.2.2. V201301091616-...
t> ^ Data Tools Platform Connectivity org.eclipse.jpt.jpa.feature.fea 1.100.3.v20131127_00...
i> &= Data Tools Platform Enablement org.eclipse.datatools.connect
u Data Tools Platform Enablement for Apache Derby 1.100.2. v20131127_00... org.eclipse.datatools.enabler
t> ^ Data Tools Platform Enablement for IBM 1.100.3. v20131127_00... org.eclipse.datatools.enabler
i> ijì Data Tools Platform Enablement for JDBC 1.100.10.v20131127_0... org.eclipse.datatools.enabler
1.100.2.v20131127_00... org.eclipse.datatools.enabler
f. in the IBM Integration Toolkit Installation Details window, click the Configuration tab.
The Configuration tab contains the details about the installed configuration of the
Integration Toolkit environment. This page is a summary of the other tabs on the
Installation Details page.

No se podrá reproducir o Student Exercises
Hp IBM Integration Toolkit Installation Details
Installed Software j Installation History | Features ) Plug-ins Configuration j ***
Date: Thursday, October 1, 2 015 at 9:31:52 AH Pacific Day lier I ■fr** Platform
Details:
*** System properties:
CommonPath=C:\Program F iles\IBM\IIB\10.0.0.0\common\classes\ [Paths]=
applicat ionXHI=org.ec1ipse.ui.workbench/LegacyIDE.e4xmi
awt.toolkit=sun.awt.windows.UToolkit
com.ibm.cpu.endian=1ittle
com.ibm.je1.checkClassPath=
com.ibm.ot i.configurât ion=scar
com.ibm.ot1.jel.build=20141215_227395
com.ibm.ot i.shared.enab led=false
com.ibm.ot i.vm.bootstrap.library.path=C:\Program F iles\IBH\I IB\1C com.ibm.ot
i.vm.1ibrary.vers ion=27 com.ibm.packed.vers ion=2
com.ibm.system.agent.path=C:\Program F iles\IBM\IIB\10.0.0.0\comme
com.ibm.util.extralibs.properties= com.ibm.vm.bitmode= 64 com.ibm.zero.vers
ion=2
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildld=4.2.2.H20140918-1444 eclipse . commands55—os Win32
Before you update any components in the Integration Toolkit, you should use the Copy to
-ws
Clipboard action, and then paste the clipboard contents into a file. Save the file for reference
in case you need to determine which components are installed at a specific point in time.
_ g. Click Close to close the configuration details.
_ h. Click OK to close the About IBM Integration Toolkit window.
_ i. Leave the IBM Integration Toolkit open (minimize it if you want); you use it later in this
exercise.
2. Get the software version information for the IBM Integration Bus.
_ a. Start an IBM Integration Bus Console session by clicking All Programs > IBM
Integration Bus 10.0.0.0 > IBM Integration Console 10.0.0.0 from the Windows Start
menu. As an option, you can double-click the IBM Integration Console shortcut icon on the
desktop.
Student Exercises
Important
When IBM Integration Bus is installed on Windows, a special command console is also
installed from which you run Integration Bus commands. It is a Windows command shell, but it sets
some environment variables when it is started.
Be sure to use an Integration Bus command console session when you are directed to do so in the
exercise instructions. If you attempt to use a Windows command prompt session, the commands you
enter might fail because the appropriate environment variables are not set.
b. Use the iib command to report the details of an IBM Integration Bus component.
In the IBM Integration Console, enter the command:
iib version
The response message contains the version, product, build levels and
build number.
Q IBM Integration Console 10.0.0.0
_AWWWWW__AWWWWW__AWWWWWW ______________ AW ___ A

WWW ___________________________________
V///AW/// _ V///AW/// _ XAW////////AW _ AWWW ___ AW////AW__
_VW\ ______ VW\ _____ VW\ ____ \AW __ \/////W\_/W\ __ \//W\_
__\AW _____ VWN _____ VWWWWWWW __________ \AW_\AW __ \AW_
__ \/W\ ______\/\W__ XAW////////AW _____ \AW_\AW ____ \AW_
__ VW\ _______\/W\____ \/W\ ___ \/W\ ____ \/W\_\/W\ __ \AW_
__ \AW _______\/W\____ \AW ____ \AW ______ \AW_\//W\ _ AW_
_/WWW\WW„AWWWWW.VWWWWWWV ______________ \/\W \///WWW\/_
_\///////////__\///////////__\///////////// ___ V//
_____________________________________ \///////__
I Enter an Integration Bus command e.g.

IIB toolkit, IIB help
C:\Progran Files\IBM\IIB\10.0.0.0>iib uersion
Installation: C:\Program
Uersion: Files\IBM\IIB\10.G.0.0' '10 .0 .0 .0 '
Product : IBM Integration Bus'
Build Number: -735’
IB Leuel: 'ibO00-L150317.735_P'
Seruer leuel: 'S0O0-L15031G.10572'
Toolkit leuel '20150313-1900'
The Version and Level fields identify the fix pack that is applied to IBM Integration Bus.
This information is useful when working with IBM Support.
in the example, the version is 10.0.0.0, which indicates that no fix pack is applied. For
example, FixPack 1 would show as version 10.0.0.1.
c. Minimize the IBM Integration Console window; you use it later in this exercise.

podrá reproducir o
Student Exercises
Part 2: Verify user authorizations

In this part of the exercise, you verify that the user ID that is used in the lab exercises has
administrative privileges.
1. To administer the integration node components and resources, the integration node service ID
must be a member of the mqbrkrs security group.
In this step, you
I£9Computer verify that the mqbrkrs security group exists on your system and that your
Management
account File(iibadmin)
Action View Helpis a member. If the mqbrkrs group cannot be found, you create it and
Bixa i H
add your account as a member of that group.
i □
Computer Management
Description
From the Windows Start menu, click All Programs > Administrative Tools > Computer
a. (Local) B System Tools E0 © Task jk Administrators Backup Administrators have complete and
Management.
Scheduler S ^ Event Viewer Operators * Certificate u.., Backup Operators can override
Shared Folders Local Users and Service DCO... secu.. Members of this group are
Expand System
Groups □ Users Groups Tools > Local Users and Groups.
¿^Cryptographic Operators allowed t. Members are authorized
b. Performance Device Manager □
Click Groups to display the¿8users
¿2* Storage
Distributed
and COM Users
groups. to perform .. Members are allowed
Event Log Readers Jfc to launch, acti... Members of this
c. Disk Management SI
Guests II5JU5R5 group can read eve.. Guests have
Services
E i and Applications ^'NetworkConfiguration the same access as me., Built-in
Performance Log Users group used by Internet Infer..
¿§jj*Performance Monitor Members in this group can have
U... som.. Members of this group may
Power Users If Print schedule,, Members of this group
Operators djk Remote can access p... Power Users are
Desktop Users |f Replicator included for backw... Members can
$£ Users %DB2ADMN5 administer domain prin.. Members
¿fe’DB2USER5 in this group are granted t...
Supports file replication in a
domain Users are prevented from
making ac.. This group and local
administrators ... This group will
have read and execut..
If you are using the VMware image for this course, the mqbrkrs group is already
created. You do not need to create it.
IBM Integration Bus Group
mqm IBM WebSphere MQ Administration ,..

d.
Double-click the mqbrkrs group to display the members of the group.
e.
Verify that iibadmin (your user ID for this course) is listed as a member of the group.
^ V Note
If you are not using the pre-built image for this course, and the mqbrkrs group does not exist, you
can create it and then add your user ID to the Members list.
1. Right-click Users and click New > Group from the menu.
2. Type mqbrkrs in the Group name field.
podrá reproducir o
Student Exercises
3. Click OK.
4. Open the new group and then add your account ID as a member of the mqbrkrs group.
v _______________________________________________________________________________ J
_ f. Click Cancel to close the Properties window for the mqbrkrs group.
_ 2. Some Integration Bus applications require IBM MQ. In these applications, the administrator
must also be a member of the IBM MQ administration group mqm (this group is created
automatically when IBM MQ is installed).
Verify that your user ID iibadmin is a member of mqm group.
If necessary, add iibadmin to the mqm group.
Changes to a user's group
Add..
IijHSComputer Management
I File Action View Help Apply Help
H
I BIXSÈ > I
1
Computer Management
(Local) □ System Tools EE Task
y Administrators Description
Administrators have complete and
Scheduler 0 |^j Event Viewer 0 Backup u... Backup Operators can override
Shared Folders B * Local Users Operators secu,,,
and Groups ilfj Users r°l Groups mqm Properties
Certificate Servi
0 (0) Performance Cryptographic C General j
Device
Manager Storage Distributed COM
IgJ1 Disk Management 0 Event Log Readi
Guests IISJUSRS
&
Network Configi
Performance Lot
Description: IBM WebSphere MQ Administration
Performance Mo Group
Power Users
Print Operators Members:
Remote Desktop iibadmin
Replicator Users & MUSR_MQADMIN
DB2ADMNS
DB2USERS
mqbrkrs mqm
Security _Test
membership are not effective until the next time the user logs on.
_ 3. Close the Computer Management window.
Part 3: Create an integration node and integration servers

In this part of the exercise, you use the IBM Integration Bus command interface to create an integration
node. This integration node does not have an IBM MQ queue manager that is specified on the
integration node.

Student Exercises
podrá reproducir o
Note
For the following steps, you use an IBM Integration Console. Remember that command
arguments are case-sensitive.
1. Start an IBM Integration Console session with Windows “Administrator” privileges.

Optionally, you can right-click the IBM Integration Console icon on the desktop and then click
Run as administrator.
2. Type the following command to create an integration node that is named IIBNODE_NOQM:
3. Start the new integration node.
4. On Windows, a Windows service is created automatically when you create an integration node.
Verify that a Windows service is created for the new integration node.
___a. In
Start
IBM Integration Bus Component Name -*■ Description 1 Status u
IIBNODE_NOQM Manu
•ZJ Diagnostic System Host The Diagnostic System Host is u.., ;
Manu
Stop the service ‘.Disk Defragmenter Provides Disk Defragmentation ... ;
A \àPause the service §5 Distributed Link Tracking Client Maintains links between NTFS Manu
fil.., ;
Restart the service Autor
'„'¡Distributed Transaction Coordinator Coordinates transactions that s,., Started r
Autor
'„■¡DNS Client The DNS Client service (dnscach.., Started r
Enables DNS clients to resolve Autor
'„■¡DNS Server D.., Started r
Windows, Provides the core file Manu
'„'¡Encrypting File System (EFS) encryption.,. ;
click Start > Manu
'„'¡Extensible Authentication Protocol The Extensible Authentication P.., ;
All Programs Manu
'„■¡Function Discovery Provider Host The FDPHOST service hosts the ... ;
> Publishes this computer and Manu
'„'¡Function Discovery Resource Publication res,., ;
Administrativ The service is responsible for Autor
'„'¡Group Policy Client ap.., Started r
e Tools > Provides X.5Û9 certificate and Manu
'„'¡Health Key and Certificate Management
Services. k..,
Enables generic input access to
;
Manu
'„'¡Human Interface Device Access ,,. ;
Autor
b. Scroll down . ¡IBM Integration Bus 10.0,0.0 Server MasterService IBM Integration Bus 10,0.0,0 Se... Started r
Manu
and verify that ¿*iIBM Integration Bus Component IIBMODE_NOQM IBM Integration Bus Node "IIBN,.. Started a
. f'jl.TRM Tr.l-onraHnn Rue Cnmnnnanf TF^TMi''ir'lF TRM Tnhanrahinn Ri ic MnHa ÇhaHharl Mani i;
"TFÇT
you see a ¡iharlmin
service for
IBM
Integration
Bus Component l!BNODE_NOQM.
H B I ► ■ 00 B>
Services [Local)
Description:
IBM Integration Bus
Mode "IIBMODE_MOQM"
podrá reproducir o
Student Exercises
r / Note ^
You might also see a service for the IBM Integration Bus Component TESTNODEJibadmin. This is the
service for the development integration node that is created automatically the first time that the IBM
Integration Toolkit starts.
V ______________________________________________________________________________ y
_ c. Close the Services window.

_ 5. Check that the integration node environment is set up correctly.
mqsicvp IIBNODE_NOQM

BIP8873I: Starting the component verification for component 'IIBNODE_NOQM'. BIP8876I:
Starting the environment verification for component 'IIBNODE_NOQM'.
pwa6470_27sr2fpl0-20141218_02(SR2 FP10)
BIP8878I: The environment verification for component 'IIBNODE_NOQM' has finished
successfully.
BIP8874I: The component verification for 'IIBNODE_NOQM' has finished successfully.
_ 6. Verify that new integration is created in “advanced” mode.
mqsimode IIBNODE_NOQM

BIP1802I: Integration node 'IIBNODE_NOQM' is in 'advanced' mode.
BIP1831I: Integration node 'IIBNODE_NOQM' has mode extensions ''.

podrá reproducir o
Student Exercises
7. Display the node properties for the new integration node.

Last mqsistart path = 'C:\Program Files\IBM\IIB\10.0.0.OXserver' mqsiprofile
install path = 'C:\Program Files\IBM\IIB\10.0.0.0\server' Work path =
'C:\ProgramData\IBM\MQSI'
Integration node UUID = ''
Process id = '3004'
Queue Manager = ''
User lil path = ''
User exit path = ''
Active user exits = ''
LDAP principal = ''
LDAP credentials = ''
ICU converter path = ''
Trusted (fastpath) Queue Manager application = 'false'
Configuration change timeout = '300' seconds Internal configuration timeout =
'60' seconds Statistics major interval = '60' minutes Operation mode =
'advanced'
Fixpack capability level = '' (effective level 'unrestricted') Integration
node registry format = 'vlO.O'
Multi-instance integration node = 'false'
Shared Work Path = 'none'
Start as WebSphere MQ Service = 'undefined'
HTTP listener port = '7080'
Cache manager policy = 'disabled'
Cache manager port range = '2820-2039'
Integration registry hostname = ''
Default integration node CCSID = '5348'
podrá reproducir o
Student Exercises
_ 8. Report integration node service details.

mqsiservice IIENODE_NOQM
BIPmsgs en_US
Console OEM CP=437, ICU CCSID=5348
Default codepage=ibm-5348 P100-1997, in ascii=ibm-5348 P100-1997 JAVA
console codepage name=cp437
Install Path = C:\Program Files\IBM\IIB\10.0.0.OXserver

Shared Work Path = NOT_HA_ENABLED_BROKER
Local Work Path = C:\PrograraData\IBM\MQSI
process id = 888
service userid = LocalSystem
general default userid = LocalSystem
pubsub migration = no
fastpath Queue Manager = no
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
ComponentType = Broker
Fixpack capability level = (effective level unrestricted)

podrá reproducir o
Student Exercises
9. Get web interface port number for the integration node.

_ a. In the IBM Integration Console, type:
HTTPConnector
uuid='HTTPConnector'
address=''
port='4415'
maxPostSize=''
acceptCount=''
compressableMimeTypes='text/html,text/css,application/javascript, image/gi f,
image/png,application/json' compression='on' connectionLinger=''
connectionTimeout='' maxHttpHeaderSize='' maxKeepAliveRequests='' maxThreads=''
minSpareThreads=' ' noCompressionUserAgents='' restrictedUserAgents=''
socketBuffer='' tcpNoDelay='' enableLookups='false' serverName=''
_ b. Record the value for HTTPConnector port property. You use this value in the next step
to start the IBM Integration web interface for this integration node.
Information
IBM Integration Bus assigns a web user administration port number dynamically. When
the first integration node is started, it is assigned the default port of 4414. For subsequent integration
nodes, the port number increments and the node is assigned the next port number in sequence.
J
10. Create an integration server by using a command.

mqsicreateexecutiongroup IIBNODE_NOQM -e serverl
BIP1124I: Creating integration server 'serverl7 on integration node 'IIBNODE_NOQM7
Student Exercises
11. Confirm the components on the integration node by using the mqsilist command. Type:
mqsilist IIBNODE_NOQM
BIP8071I: Integration server 'serverl' on integration node 'IIBNODE NOQM' is running.
__ a. Open a web browser. Your course image includes both Internet Explorer and Mozilla
Fi refox.
http: //localhost: port
Replace port in this command with the FITTPConnector port value that the
For example, if the port number that the mqsireportproperties command returns in
Step 9 is 4417, type http: //localhost: 4417.
c. After a brief pause, the IBM Integration user interface for the IIBNODE_NOQM integration node starts.

Student Exercises
13. Display the current integration servers that are defined on the integration node.
Click the down arrow that is to the left of the Servers folder.
You should see one integration server that is named server!. You should also see that icon
next to the integration server name contains an up pointing green arrow, which indicates that
the integration server is running.
^ II BNODE_MOQM
serverl
2n Operational Policy
Security
Evi
Monitoring
14. Create an integration server that is named server2 on the integration node by using the IBM
_ a. In the IBM Integration web interface, click the down arrow to the right of the Servers
folder and then click Create.
J IIBNODEJNOQM
server
► ll2] Operation
► QE Data
_ b. In the New Integration Server window, type server2 and then click OK.
_ c. After a brief pause, you should see a message that the integration server was created.
You should also see that the Servers folder now contains two integration servers:
serverl and server2.
15. Start the IBM Knowledge Center for IBM Integration Bus V10 from the IBM Integration web
user interface.
_ a. Click the Help icon in the IBM Integration web interface.
|4-3‘llBNODE_NOqM - IBM Integration - Internet Explorer
http: //localhost : IIBNODE_NOQM - IBM Integ... X | Eg IBM Knowledge Center

4415/#broke
Filter Options.
IIBNODE_NOQM - Integration Node
© Copyright IBM Corp. 2015 Exercise 1. Integration node setup and customization

Student Exercises
_ b. The IBM Knowledge Center web page opens in a new tab in the web browser.
^ IBM Knowledge Center - Internet Explorer
IDlxl
? JH http : //www-01 ibm.com/supp P
**
— IIBNODE_NOQM - IBM Integration S3 IBM Knowledge Center LJ firsts
IBM Knowledge Center Sign In English - 0
Search Save Search ▼
Search Filters: IBM Integration Bus 10.0.0 x (y Auto-select | Clear All Add
Products..
ß Share ▼ Add to Collection ▼ ¿7 0
IBM Integration Bus 10.0.0 > Welcome

IsT] Table of Contents
* Back to all products
* IBM Integration Bus IBM Integration Bus

IBM Integration Bus 10.0.0 Version lo.o
Welcome
► Start here Welcome to the product documentation for IBM® Integration Bus Version 10.0, where you can
find detailed instructions about how to complete the tasks to establish and maintain your
► Product overview integration environment This information also describes concepts to help you understand the
product, and the ways in which you can use it to solve your business problems.
► Scenarios
► Planning your IBM Integration Bus solution
► Migrating
► Installing and uninstalling

Some of the links in this documentation work only if you are accessing this documentation from the IBM Integration Toolkit.
► Configuring integration nodes for development < The links that work only in the IBM Integration Toolkit are displayed with toolkit icon a.
► Configuring integration nodes for test and produ v* When the documentation is used in a user interface or local Knowledge Center, some links work only if you have a
connection to the internet, and these links are displayed with this icon ^.
ji My Collections Search
Results
(^) Getting a Commo
started What's n tasks
new?
Contact Privacy Terms of use Accessibility Feedback
_ c. Take some time to investigate the sections in the IBM Knowledge Center for IBM
Integration Bus.
For example, you can type mqsicreatebroker in the Search area to find information
about the mqsicreatebroker command.
Exercise clean-up
_ 1. Close the web browser window.
_ 2. Close the IBM Integration Console window.
End of exercise

Student Exercises

In the first part of this exercise, you verified the maintenance (fix pack) levels of the IBM Integration
Bus software.
In this second part of the exercise, you verified that the user ID that is used in the lab exercises has
administrative privileges to create and administer IBM Integration Bus and IBM MQ resources.
In the third part of this exercise, you used the IBM Integration command interface to create an
integration node and report integration node properties. You then used the IBM Integration command
interface and the IBM Integration web interface to create integration servers on the new integration
node. You also used the IBM Integration web interface to access the IBM Knowledge Center for IBM
Integration Bus V10.
Student Exercises

Student Exercises
Exercise 2. Connecting to IBM MQ

In this exercise, you create an IBM MQ queue manager and an IBM Integration
Bus integration node that uses the queue manager as a default queue
manager. You create a second integration node with the same default queue
manager as the first integration node. Finally, you create the IBM Integration
Bus system queues on the queue manager and an MQEndpoint policy.

Introduction
With the release of IBM Integration Bus V10, an IBM MQ queue manager is no
longer a prerequisite for integration nodes.
You can develop and deploy many message flow applications with Integration
Bus independently of IBM MQ; however, some Integration Bus capabilities still
require access to an IBM MQ queue manager. For example, the MQInput and
MQOutput nodes in a message flow require access to an IBM MQ queue
manager. Other Integration Bus capabilities require that a queue manager that
has special SYSTEM.BROKER queues is specified on the integration node.
For example, event driven message processing nodes such as the Collector
node and the Aggregation node require that a queue manager is specified on
Information
The IBM MQ message processing nodes do not require a queue manager to be specified on the
integration node unless you want to use a default queue manager for the local IBM MQ connection.
In IBM Integration Bus V10, multiple integration nodes can share a queue
manager. Flows that are deployed to integration servers in different

Student Exercises
integration nodes that share a queue manager can put and get from different
queues or the same queues.
Using a shared queue manager can provide high availability for an
application. If one of the flows, integration server, or integration node fails, the
other flow on the other integration node can assume the workload. In the
example in the figure, the integration nodes IIBNODE_WITHQM and
IIBNODE_WITHQM2 share the IBM MQ queue manager IIBQM.
In the first part of this exercise, you create a queue manager that is named
IIBQM.
In the second part of this exercise, you create two integration nodes
(IIBNODE_WITHQM and IIBNODE_WITHQM2). Each integration node
specifies the same queue manager (IIBQM) as the default queue manager.
You also create an integration server on each integration node.
In the third part of this exercise, you add the BROKER.SYSTEM queues to
the queue manager.
Integration Bus administrators can use an MQEndpoint policy to control the
values of IBM MQ node connection properties at run time. The MQEndpoint
policy overrides any equivalent properties that are specified for the MQ
Connection properties in the message flow definition.
In the fourth part of the exercise, you create an MQEndpoint policy on the
development integration node TESTNODEJibadmin by using the IBM
Integration web interface. The TESTNODEJibadmin integration node is the
development integration node that is created automatically for developers the
In this part of the exercise, you also export an MQEndpoint policy and then
import it into another integration node (IIBNODE_NOQM).

Student Exercises
Requirements
• A lab environment with the IBM Integration Bus V10 Bus and IBM MQ V8
• A user iibadmin who is a member of the mqbrkrs and mqm groups
• The IIBNODE_NOQM Integration node and integration servers that are
created in Exercise 1, Part 3. It also requires that the integration node
IIBNODE_NOQM is running.

Student Exercises
Part 1: Use IBM MQ Explorer to create the queue manager
In this part of the exercise, you use IBM MQ Explorer to create a queue manager that is named IIBQM
and a dead-letter queue that is named DLQ.
_ 1. Start IBM MQ Explorer.
From the Windows Start menu, click All Programs > IBM WebSphere MQ > WebSphere MQ
(Installation 1) or double-click the WebSphere MQ Explorer (Installationl) icon on the
desktop.
_ 2. Create a queue manager that is named IIBQM with a dead-letter queue that is named DLQ.
_ a. In the MQ Explorer Navigator view, right-click Queue Managers and then click New >
Queue Manager.
WebSphere MQ Explorer (Installationl)
fe. MQ Explorer - Navigator £3 4^ - □ Hi MQ Explorer - Co

E-@ IBM WebSphere MQ
Queue Mana
& Queue
Ma
& Queue Mar & Show/Hide Queue Managers,..
Add Remote Queue Manager,,. Filter: Standard h
JM5 Adminl &
Managed F È? Queue Manager.
Service Del Transfer Queue Managers.,.
Tests ►
Sets ►
b. For the Queue Manager name, type: IIBQM

c. For the Dead-letter queue, type: DLQ
d. Click Finish.

Student Exercises
After a brief pause, the queue manager is created and started. A listener is also started
on the default TCP port of 1414.
The queue manager is shown under the Queue Managers folder in the MQ Explorer -
Navigator view.
3. Create a queue that is named DLQ for the dead-letter queue.
_ a. In the MQ Explorer - Navigator view, expand the IIBQM queue manager folder.
_ b. Right-click Queues and then click New > Local Queue.
BM WebSphere MQ Explorer (Installation!)

'tSL MQ Explorer - Navigator £3 ^ :-] □ ft MQ Exp I orer - '

B"@ IBM WebSphere MQ
B" tzh Queue Managers Ë Queues
5¡ IIBQM
Filter: Standarc
& TopU & Local Queue.,,
Subs. Alias Queue...
Status,,,
Model Queue,,,
0 & Char Tests Remote Queue Definition.
►
& Liste Object Authorities ►
& ServTces
c. For the queue Name, type: DLQ

d. Click Finish.
e. Click OK in the Confirmation window.
f. Verify that the queue DLQ is listed in the Queues content view.
^>IBM WebSphere MQ Explorer (Installation!)
File Edit Window Help ¡§7. MQ Explorer - Navigator S3
“□
H) MQ Explorer - Content « I! ™ I & ~
iQueues
<£> B ~
□ Q} IBM WebSphere MQ Queue Managers B 53
IIBQM Filter: Standard for Queues
•£> Queues Topics
Subscriptions 0 Channels ' Queue name Queue type | Open input count | Open output count | Current queue depth | Put messages Get messages
Listeners Services y DLQ Local 0 0 0 Allowed Allowed
_ 4. Minimize IBM MQ
Explorer.
Part 2: Create the integration nodes and integration servers

In this part of the exercise, you use the IBM Integration Bus command interface to create two
integration nodes that use the same queue manager as the default queue manager. You also create an
integration server on each integration node.
_ 1. Create an integration node that is named IIBNODE_WITHQM.
_ a. Start an IBM Integration Console session with Windows “Administrator” privileges.

Student Exercises
Optionally, you can right-click the IBM Integration Console icon on the desktop and
then click Run as administrator.
_ b. Enter the following command to create an integration node that is named
IIBNODE_WITHQM that specifies the queue manager IIBQM:
mqsicreatebroker IIBNODE_WITHQM -q IIBQM
_ c. Start the new integration node.
_ 2. Check that the integration node environment is set up correctly for l!BNODE_WITHQM.
Verify that the integration node properties for the integration node indicate that queue manager
IIBQM is specified on the integration node.
mqsicvp IIBNODE_WITHQM
BIP8873I: Starting the component verification for component 'IIBNODE_WITHQM'.
BIP8876I: Starting the environment verification for component 'IIBNODE_WITHQM'.
pwa6470_27sr2fpl0-20141218_02(SR2 FP10)
BIP8878I: The environment verification for component 'IIBNODE_WITHQM' has finished
successfully.
BIP8841I: The WebSphere MQ verification for component 'IIBNODE_WITHQM' had finished
successfully.
BIP8874I: The component verification for 'IIBNODE_WITHQM' has finished successfully.
_ 3. Create an integration server on IIBNODE_WITHQM that is named serverl.

Student Exercises

mqsicreateexecutiongroup IIBNODE_WITHQM -e server!
BIP1124I: Creating integration server 'serverl' on integration node '
IIBNODE_WITHQM'
4. Get the IBM Integration web interface port number for the IINODE_WITHQM integration node.
__ a. In the IBM Integration Console, type the following command to get the HTTP Connection
port number:
mqsireportproperties IIENODE_WITHQM -b webadmin -o HTTPConnector -a
__ b. Record the value for HTTPConnector port. You use this value in the next step to start
the IBM Integration web interface for this integration node.
Information
IBM Integration Bus assigns a web user administration port number dynamically. When the first
integration node is started, it is assigned the default port of 4414. For subsequent integration nodes,
the port number increments and the node is assigned the next port number in sequence.
J
__ a. Open a web browser.
http://localhost: port
For example, if the port number that the mqsireportproperties command returns in Step 4
is 4416, type http: //localhost: 4416.
__ c. After a brief pause, the IBM Integration user interface for the IIBNODE_NOQM
integration node starts.
6. Following the same procedure that you used for creating the integration node
IIBNODE_WITHQM and the integration server serverl, create another integration node that is
named IIBNODE_WITHQM2 and an integration server that is named server2.
Be sure to specify the same queue manager, IIBQM, as the queue manager on the integration
node.

podrá reproducir o
Student Exercises
Part 3: Create the SYSTEM.BROKER queues and topics on the integration

node queue manager
Some Integration Bus capabilities and message processing nodes require access to an IBM MQ queue
manager and SYSTEM.BROKER queues and topics on the integration node queue manager.
In this part of the exercise, you use an Integration Bus sample command file to add the
SYSTEM.BROKER queues and topics to the IIBQM queue manager that the IINODE_WITHQM and
IIBNODE_WITHQM2 integration nodes use.
_ 1. In IBM MQ Explorer, check the SYSTEM queues on the queue manager IIBQM.
__ a. In the IBM MQ Explorer Queues content view, click the Show System Objects icon to
:
display the SYSTEM queues and topics.
IBM WebSphere MQ Explorer (Installation!)
__ b. Locate the current set of SYSTEM.BROKER queues.

IBM MQ created these queues. They are generic queues that are automatically set up for
all brokers and queue managers on a network. These queues are not specific to Integration
Bus.
MQ Explorer - Content ZÌ | ±j|| | t-jsf | □ Q
¡Queues
Queue name Queue type Open input count Open output count Current queue depth Put mes |
Local 1 1 99 Allowed
y SYSTEM.BROKER.ADMIN,STREAM Local 1 1 0 Allowed
|0j SYSTEM.BROKER.CONTROL,QUEUE Local 30 0 Allowed

y SYSTEM.BROKER.DEFAULT,STREAM Local 10 o Allowed
y SYSTEM. BROKER. INTER .BROKER. COMMUNICATIONS Local 10 0 Allowed
y SYSTEM.CFIANNEL,INITQ Local 10 0 Allowed
y SYSTEM.CFIANNEL,5YNCQ Local 00 0 Allowed
y SYSTEM.CHLAUTH.DATA.QUEUE Local 00 3 Allowed
2. In the IBM Integration Console, type the following command to go to the Integration Bus sample
directory for IBM MQ. This directory contains the batch file that creates the SYSTEM.BROKER
queues.
cd server\sarnple\wmq

Student Exercises
3. In the IBM Integration Console, type the following command to run the command file on the IIBQM
queue manager.
iib_createqueues.ctnd IIBQM
You should see messages that indicate that the SYSTEM.BROKER queues and topics are
created. You should also see messages that indicate that security is set on the queues by using
the IBM MQ setmqaut command.
4. In IBM MQ Explorer, check the SYSTEM queues on the queue manager IIBQM and verify that the
queue manager
now contains the
Integration Bus
SYSTEM.BROKER
queues.
£[j MQ Explorer - Content £3
iQueues
Queue name Queue type Open input count Open output count | Current queue depth |
U SYSTEM,BROKER. ADAPTER,PROCESSED Local 0 00
lai SYSTEM,BROKER.ADMIN,STREAM Local 1 1 0
lai SYSTEM.BROKER. AGGR.CONTROL Local 0 0 0
U SYSTEM,BROKER.AGGR.REPLY Local 0 0 0
lai SYSTEM,BROKER.AGGR.REQUEST Local 0 0 0
lai SYSTEM,BROKER.AGGR.TIMEOUT Local 0 00
lai SYSTEM,BROKER.AGGR.UNKNOWN Local 0 00
lai SYSTEM.BROKER.AUTH Local 0 00
SYSTEM,BROKER.CD,MODEL Model
lai SYSTEM,BROKER.CONTROL,QUEUE Local 3 00
lai SYSTEM,BROKER.DC,AUTH Local 0 0 0
lai SYSTEM,BROKER.DC,BACKOUT Local 0 0 0
lai SYSTEM.BROKER.DC.RECORD Local 0 0 0
lai SYSTEM,BROKER.DEF AULT,STREAM Local 1 0 0
lai SYSTEM,BROKER.EDA,COLLECTIONS Local 0 ID 0
lai SYSTEM,BROKER.EDA,EVENTS Local 0 00
SYSTEM,BROKER.FTE,MODEL Model
lai SYSTEM. BROKER. INTER .BROKER. COMMUNICATIONS Local 100
ÌI SYSTEM,BROKER.MODEL.QUEUE Model
lai SYSTEM,BROKER.SEQ,EXPIRY Local 0 00
lai SYSTEM,BROKER.SEQ,GROUP Local 0 0 0
|al SYSTEM,BROKER.SEQ,NUMBER Local 0 0 0
lai SYSTEM.BROKER.TIMEOUT.QUEUE Local 0 0 0
lai SYSTEM,BROKER.WS,ACK Local 0 0 0
lai SYSTEM,BROKER.WS,INPUT Local 0 ID 0
lai SYSTEM.BROKER.WS.REPLY Local 0 00
5. The command script also creates the topic SYSTEM.BROKER.MB.TOPIC, which maps to the topic
string $SYS/Broker. This topic is required for the Integration Bus record and replay, and statistics
components.

Student Exercises
Click Topics under the IIBQM queue manager in the MQ Explorer - Navigator. Verify that
the SYSTEM.BROKER.MB.TOPIC is created on the queue manager.
% IBM WebSphere MQ Explorer (Installation!)
File Edit Window Help jfe! MQ Explorer - Navigator £3 1=1 B

£0 E! ^
g MQ Explorer - Content £3
B© IBM WebSphere MQ
□-& Queue Managers - 0
Topic
IIBQM
s
;. & Queues
Filter: Standard for Topics
i i ........ & [tigjitj
!. Subscriptions I Topic type | Topic string
Topic name
i S Channels ©SYSTEM.BASE,TOPIC Local
j . & Listeners ©SYSTEM.BROKER.ADMIN,STREA Local SYSTEM,BROKER, ADMIN
i ..Services .STREAM
M Local
I & Process Definitions ©SYSTEM.BROKER.DEFAULT.STR
©SYSTEM.BROKER.MB,TOPIC
EAM Local $5Y5/Broker
_ 6. Minimize IBM MQ Explorer.
Jbïb I tm.UtrAULI . IUP1L
Part 4: Create an MQEndpoint policy

Integration Bus administrators can use an MQEndpoint policy to control the values of IBM MQ node
connection properties at run time. The MQEndpoint policy overrides any equivalent properties that are
specified for the MQ Connection properties in the message flow definition.
In this part of the exercise, you create an MQEndpoint policy on the development integration node
TESTNODEJibadmin by using the IBM integration web interface. The TESTNODEJibadmin
integration node is the development integration node that is created automatically for developers the
In this part of the exercise, you also export an MQEndpoint policy and then import it into another
integration node (IIBNODE_NOQM).
_ 1. Open a web browser and start the IBM Integration web interface for the
_ a. Ensure that the integration node TESTNODEJibadmin is running. Type:
mqsilist
If the results of this command show that TESTNODEJibadmin is not running, start it by
using the mqsistart command.
_ b. Get the HTTP Connector port value for the web interface by typing the following
command in the IBM Integration Console.
mqsireportprqperties TESTNODE_iibadmin -b webadmin -o HTTPConnector -a
_ c. Record the value for port property.
_ d. In the web browser, type the following URL to start the IBM Integration web interface for
TESTNODEJibadmin
http://localhost :port

Student Exercises
Filter Options...
TESTNODEJibadmin - Integration Node

- $ TESTNODEJibadmin ▼ i S' Qi Overview Statistics
Servers
► Ug] Operational Policy
► g Data
► ^ Security ▼ Quick View
Node Name
► 0 Monitoring TESTNOD
EJibadmin
Version 10DDO
Admin Security ©Off
Run Mode running

Short Description
Long Description
2. In the IBM Integration web interface, expand Operational Policy.

3. Click the down arrow on the right side of MQEndpoint to display the menu and then click
Create.
I
I
n
:
i
- $ TESTNODEJibadmin ▼
► Servers ▼
- ill Operational Policy

MQEndpoint i
► MQTTPublish MQEndpoint
► MQTTSubscrit Create
► (jfcip Workload Management ▼
4. Define the MQEndpoint policy for a local connection to the queue manager IIBQM.
_ a. For the Policy name, type: LocaiConnectToiiBgM
_ b. For the Connection, select Local queue manager.
__ c. For the Queue manager name, type: IIBQM
__ d. For the Queue manager host name, type: locaihost

_ e. For the Listener port number, type: 1414
_ f. For the Channel name, type: SYSTEM.DEF.SVRCQNN

Student Exercises
Operational Policy - MQEndpoint

Q Overview
]. Save As Revert
g. Click Save.
|j Use a policy to control the operational behavior of a message flow node at run time.... Oct 3,2015, 6:55:29 AM x
Policy name*
Loe alConnectTo
11BQM
Connection Queue manager
Local queue manager
name Queue manager host

IIBGM
name Listener port number
localhost
Channel name Security 1414
identity
SYSTEM.DEF.SVRCONN
Use SSL SSL peer name
SS-L cipher specification
h. After a brief pause, you should see the new MQ Endpoint policy under the MQEndpoint
policy folder in the IBM Integration web interface.
- £ TESTNODEJibadmin T
► Servers ▼
- §2 Operational Policy
- (£3 MQEndpoint
j7l Local Connection BQM
MQTTPublish ^
|ti> MQTTSubscribe ▼
5. Verify that the new policy is available to the developer in the Integration Toolkit.
__ a. Start the IBM Integration Toolkit if it is not already running.
__ b. In the Integration Toolkit, click the Integration Registries tab (in the same view as the
Integration Nodes tab).

Student
IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. Exercises
Integration Modes Integration Registries S3 >■

□ Întegration Registries
Integration Registry on IIBNODE_NOQM &
Policies 17^7 Services
Integration Registry on IIBNODE_WITHQM
□£ Policies Jj Services
Integration Registry on IIBNODE_WITHQM2
Policies ¿j' Services
É& Integration Registry on TESTNODEJibadmin
Policies Services
àS
The Integration Registries tab contains an entry for each integration node to which the
Integration Toolkit can connect. By default, the Integration Toolkit can connect to any local
integration node.
C.
You created the MQEndpoint policy on TESTNODEJibadmin.
Right-click Integration Registry on TESTNODEJibadmin and then click Refresh to
update the Integration Registry view in the IBM Integration Toolkit.
Verify that the MQEndpoint policy that is named LocalConnectTollBQM is listed under the
d. Integration Registry on TESTNODEJibadmin folder.
Integration Nodes ¡ Integration Registries £3 t- Dat
E ¿eg Integration Registries

É Integration Registry on IIBNODE_NOQM Policies jj
Services
É <5 Integration Registry on IIBNODE_WITHQM
Policies Jj Services
- £ Integration Registry on IIBNODE_WITHQM2 (£7
Policies
□ <3 Integration Registry on TESTNODEJibadmin

..................................................................................... ............................. .......................
É -|Jÿ Policies
j i ..........gj] MQEndpoint/LocalConnectToIIBQM
¿7 Services
r I# I Information
I
J
_L
The application developer can now reference the MQEndpoint policy in the message flow by specifying
the policy URL in the Policy URL field in the Policy properties on the IBM MQ message processing
nodes.
The format Of a policy URL is /apivl/policy/poi icy Type/policyName.

Student Exercises
For example, the policy URL for the MQEndpoint policy that you created in this exercise is:
/apivl/policy/MQEndpo int/LocalConnectTollBQM.
V ______________________________________________________________________________ V
_ 6. Export the MQEndpoint policy to the c: \iabfiies\Lab02-MQ directory.
__ a. In the IBM Integration Console, go to the C:\iabfiies\Lab02-MQ directory. Type:
cd C:\labfiles\Lab02-M2
__ b. Type the following command to create a policy file from the LocalConnectTollBQM
MQEndpoint policy that was created on TESTNODEJibadmin:
mqsireportpolicy TESTNODE_iibadmin -t MQEndpoint -1 LocalConnectToIIBQM -f
LocalConnectToIIBQM. xml
The command should create the file and display the current values of the MQEndpoint
policy.
__ c. Using Windows Explorer, verify that the LocalConnectToIIBQM.xml file was created in
the C:\iabfiies\Lab02-MQ directory.
_ 7. View the contents Of the LocalConnectToIIBQM.xml file.
You can double-click the file to view it in a web browser (shown in the screen capture) or open
Windows Notepad to view it as a text file.
<?xml version="1.0" encodtng="UTF-8" standalone="true"?>

- <policy type='MQEndpoint'>
- <policyProperties>
- <mqConnectionDetailsPolicy>
<queueManagerHostname>localhost</queiieManagerHostnanne>
<listenerPortNLmber>14i4</listenerPort!\lumber>
<channelName>SYSTEM.DEF.SVRCONN</channeiName>
<useSSL>false</useSSL>
</mqConrectionDetailsPolicy>
</policyProperties>
</policy>
_ 8. Import the exported MQEndpoint policy definition to create an MQEndpoint Policy on

IIBNODE_NOQM.
mqsicreatepolicy IIBNODE_NOQM -t MQEndpoint -1 LocalConnectTollBQM -f
LocalConnectToIIBQM.xml
After a brief pause, you should receive a response that the command completed successfully.
_ 9. Verify that the MQEndpoint policy was imported successfully by using the
mqsireportpolicy command.

Student Exercises
In the IBM Integration Console, type: mqsireportpolicy IIBNODE_NOQM -t

MQEndpoint -r You should receive the following response.
BIP1895I: Policy type 'MQEndpoint' Policy name 'LocalConnectToIIBQM' Policy URI
'/apivl/policy/MQEndpoint/LocalConnectToIIBQM' Policy content '<?xml version="l. 0"
encodings"UTF-8" standalone="yes"?Xpolicy type= "MQEndpoint"> <policyProperties>
<mqConnectionDetailsPolicy>
<queueManagerHostname>localhost</queueManagerHostname>
<listenerPortNumber>1414</listenerPortNumber>
<channelName>SYSTEM.DEF.SVRCONN</channelName>
<useSSL>false</useSSL> </mqConnectionDetailsPolicy>
</policyProperties></policy>'
rp/
r Note
You can also verify that the MQEndpoint policy was imported into the IIBNODE_NOQM integration
E iÜg Integration Registries
node by using the IBM Integration Integration Registry on IIBNODE_NOQM web interface for
IIBNODE_NOQM or by viewing the Integration Registry in the IBM
! S"l2 Policies
! I 1 ............. in MQEndpoint/LocalConnectToIIBQM
(ö Services
+ Integration Registry on IIBNODE_WITHQM +
Integration Registry on IIBNODE_WITHQM2 - 4
Integration Registry on TE5TNODE_iibadmin É-
|£=! Policies
i 1 .........In MQEndpoint/LocalConnectToIIBQM
Services
V _________________________________________________________________________ J
Exercise clean up
_ 1. Stop the IIBNODE_WITHQM2 integration node. In the Integration Console, type:
mqsistop IIBNODE_WITHQM2
End of exercise

Student Exercises

In the first part of this exercise, you created a queue manager that is named IIBQMGR.
In the second part of this exercise, you created two integration nodes (IIBNODE_WITHQM and
IIBNODE_WITHQM2). Each integration node specifies the same queue manager (IIBQMGR) as the
default queue manager. You also created an integration server on each integration node.
In the third part of this exercise, you added the BROKER.SYSTEM queues to the queue manager.
In the fourth part of the exercise, you created an MQEndpoint policy on the development integration
node TESTNODEJibadmin by using the IBM Integration web interface. You also exported an
MQEndpoint policy and then imported it into another integration node.

Student Exercises
Exercise 3. Using the IBM Integration Toolkit

In this exercise, you use the IBM Integration Toolkit to complete basic
configuration tasks. You also import, deploy, and test a message flow to learn
the administrative tasks available in the development environment.

Introduction
You typically administer IBM Integration Bus by using the IBM Integration web
user interface, and the IBM Integration Console command interface. Some
basic administration functions are also available in the IBM Integration Toolkit.
In this exercise, you use import, deploy, and test a message flow so that you
can gain an understanding of the administrative tasks that a developer often
does in a development environment.
In the first part of this exercise, you import an Integration Bus project
interchange file into the Integration Toolkit. The project interchange file
includes a message flow application. The message flow is shown in the
following figure.
Student Exercises
This message flow accepts a simple XML message from an IBM MQ queue of
the form:
<InMsgXVersion>2</Version></InMsg>
The message flow validates the value of <version> in a Filter node as follows:
• If <version> equals 2, send the message through the True terminal and
put the message on the REPLYQ node, which puts the message on the
REPLY queue.
• If <version> equals 1 or 3, send the message through the False terminal
to the FALSEQ node, which puts the message on the FALSE queue.
• If <version> does not equal l, 2, or 3, send the message through the
Unknown terminal to the UNKNOWNQ node, which puts the message on
the UNKNOWN queue.
• If an error occurs during message processing on the Filter node, the
message is sent through the terminal to the FAILUREQ node, which puts
the message on the FAILURE queue. If the put to the FAILURE queue
fails, the message is routed back to the IN node and sent to the
TraceExtList node.
- / Note ---------------------------------------------------------------------------------
f\
You learn more about the handling of message flow processing errors later in this course.
y
Student Exercises
In the second part of this exercise, you create a BAR file and examine the
configurable properties by using the Integration Toolkit BAR file editor. You
then deploy the BAR file to the development integration server.

In the third part of this exercise, you test the message flow by using the
Integration Toolkit Flow exerciser.
Required materials
• IBM MQ and IBM Integration Bus software components
• IIBQM queue manager that you created in Exercise 2
• Lab exercise files in the c:\iabfiies\Lab03-Tikt folder.
• RFHUtil in the C:\Software folder
Student Exercises
Exercise setup
_ 1. This exercise assumes that you successfully completed Part 1 of Exercise 2 in which you
created the queue manager IIBQM.
If you did not do Part 1 of Exercise 2, complete that part of the exercise before proceeding with
this exercise.
_ 2. Use the IBM MQ runmqsc command to define the queues that are required for this
exercise. You use a command script for this purpose. The command file is in the
C:\labfiles\Lab03-Tlkt\resources directory.
_ a. Start an IBM Integration Console session if one is not already running.
_ b. Change to the C:\iabfiies\Lab03-Tikt\resources directory.
Enter the command:
cd C:\labfiles\Lab03-Tlkt\resources
_ c. Enter the command:

runmqsc IIBQM < C:\labfiles\Lab03-Tlkt\resources\Q Defs.mqsc
You should receive a response that indicates that the queues are created, similar to the
following example.
def ql(IN) replace WebSphere MQ
AMQ8006 queue created.
~k
def ql(REPLY) replace WebSphere
MQ queue created.
AMQ8006 ~k
def ql(FAILURE) replace
AMQ8006 ~k
def ql(UNKNOWN) replace
~k
AMQ8006
def ql(FALSE) replace WebSphere
MQ queue created.
~k
AMQ8006 def ql(CATCH) replace WebSphere

MQ queue created.
AMQ8006

7 : end
6 MQSC commands read.
No commands have a syntax error.
All valid MQSC commands were processed.
podrá reproducir o
Student Exercises
_ d. Use the IBM MQ Explorer to verify that the local queues IN, REPLY, FAILURE,
UNKNOWN, FALSE, and CATCH are created on IIBQM queue manager.
Explorer - Navigator E3 =
□ 3 MQ Explorer - Content Ü
feM
Q 0B^
IBM WebSphere Queues
MQ S- Queue
Managers - 0 Filter: Standard for Queues
IIBQM_______
Open Input count | Open output Current queue depth
Queue name Queue type count |
S Topics S y CATCH Local 00 0
Subscriptions y DLQ Local 00 0
+>S y FAILURE Local 00 0
Channels S y FALSE Local 00 0
Listeners y IN Local 00 0
■ S Services y REPLY Local 00 0
■ S Process y UNKNOWN Local 00 0
Definitions -S
Namelists
_ e. Minimize the IBM Integration Console and IBM MQ Explorer.
Part 1: Work with a simple message flow

In this part of the exercise, you import an Integration Bus application into the Integration Toolkit
workspace and examine the message flow.
_ 1. Start the IBM Integration Toolkit if it is not already running.
_ a. Double-click the IBM Integration Toolkit 10.0.0.0 icon on the desktop.
You can also start the toolkit by clicking All Programs > IBM Integration Bus 10.0.0.0 >
IBM Integration Toolkit 10.0.0.0.
_ b. Close the Welcome window to go to the Integration Development perspective.
_ 2. Import an application from a project interchange file into the Integration Toolkit workspace.
® Import
Select
IÔ
Import a project and its dependent projects Prom a Zip Pile.
Select an import source:
S-(¡5? General à CVS

Ê CB5 Decision Services EHfc EJB
l^-lS’ IBM Integration

Project Interchange
erchange
EI-& Install
¿■ ■ ■ fe Java
EE
c. To the right of From zip file, click Browse.

d. Browse to the C:\labfiles\Lab03-Tlkt\resources directory.
3-5
© Copyright IBM Corp. 2015 Exercise 3. Using the IBM Integration Toolkit
podrá reproducir o
Student Exercises
__ e. Click VersionTest_ProjectInterchange.zip and then click Open.

__ f. Select the TestVersionNumber check box (if it is not already selected) and then click
Finish.
I® Import Project Int erchange Co ntents >
Import Projects
Import Projects From a zip File.
From zip file: | C:li,labPiles\Lab03-Tlkt\resources\VersionTest_Froject ^ | Browse... |
Project location root: | .1 :\Users',¡ badmin\ICM i.IIDTl 0'i wort space Browse... I
0 U_ TestVersionNumber
3. The TestVersionNumber application is now displayed in the Application Development
view.
Fully expand the TestVersionNumber application by clicking the plus (+) signs and examine its
contents.
i Application Development £3 °i£_ Patterns Explorer
□"EJ iTestVersionNumberi É-"i|§ Flows

t." TestVersionNumberFlow.msgflow É-S1 ESQLs
É-jíyl Check_for_V2.esql
■■¿es’ll Check_for_V2
You see that the project contains folders for Flows and ESQLs.
4. Double-clicking an object in the Application Development view causes the corresponding
editor to open the object in the editor pane, on the right side of the Integration Toolkit.
Open the message flow in the Message Flow editor by double-clicking the file
TestVersionNumberFlow.msgflow in the Application Development view.
5. Examine the message flow. Verify that it agrees with the figure that is displayed at the
beginning of the exercise.
6. The properties of each node in the message flow are preset to transform and route the
message as described at the beginning of the exercise.
Verify that the node properties match the following table.
You can view (or change) a property by right-clicking a node and then clicking Properties.
Student Exercises
Node properties are grouped into pages. The Basic page is initially visible for most nodes.

podrá reproducir o
Node name Node type Properties

IN MQInput
Basic: Queue name = IN MQ Connection:

Input Message Parsing: Message Domain = XMLNSC
Advanced: Transaction mode = Yes
TraceExList Trace
Basic:
Destination = File
File path = C:\TraceExList.txt
Pattern = In TraceExList! Root ===> ${Root}
ExceptionList ===> ${ExceptionList}
REPLYQ MQOutput
Basic: Queue name = REPLYQ MQ Connection:

FAILUREQ MQOutput
Basic: Queue name = FAILURE MQ Connection:

Test_Version=2 Filter Basic: Filter expression = {default}check for V2

CATCHQ MQOutput
Basic: Queue name = CATCH MQ Connection:

UNKNOWNQ MQOutput
Basic: Queue name = UNKNOWN MQ Connection:

FALSEQ MQOutput
Basic: Queue name = FALSE MQ Connection:

podrá reproducir o
Student Exercises

In this part of the exercise, you create and deploy a BAR file in the Integration Toolkit. You also
examine the configurable properties in the BAR file editor.
_ 1. In the Integration Toolkit, click File > New > BAR file.
_ 2. For the BAR file Name, type
Testversion and then click Finish.
New BAR file

Container: BARfiles
Browse...
Folder: f<default> __________
Name: ] TestVersion|
The BAR File editor opens with

the Prepare tab.
3. On the Prepare tab, you identify the resources to include in the BAR file.
Click the TestVersionNumber application from the list of Deployable Resources to select it
as a component of the BAR file.
4. Click Build and Save to build the BAR file and save the workspace. Click OK in the
confirmation window.

podrá reproducir o
Student Exercises
5. The BAR file now appears in the Application Development view under the BARs folder and
under the Independent Resources > BARfiles > BARs folder.
Application Development New...
-]-[S] TestVersionNunriber
Flows
I I ; ........... pi TestVersionNumberFlow.msgflow
¿1 ESQLs
f---|epl Check_for_V2.esql ;
.... Ipslql Check_for_V2

BARs
^ iTestVersiori.bar -> BARfiles/Test Version, bar I □■ 4
Independent Resources B \z3 BARfiles [—■ ¿3 BARs
12 Test Version, bar
6. In the BAR file editor, click the Manage tab.

On the Manage tab, you can review and manage the resources that are contained within
the BAR file. You can add, remove, or modify resources, and override configurable
properties. You can then rebuild the BAR file, in preparation for deployment.
7. Fully expand the contents of the BAR file on the Manage tab.
Student Exercises
When you expand the contents of the message flow, you see an entry for each node
in the message flow. The nodes are listed in alphabetical order.
Manage
LiHlj TestVersionNumberFlow.msgflow J L0 TestVersion.bar £3 | 1=5

13
j Deployment Log
Name
TestVersionNurnberF r law'..rnsgflow Type 1 Modified Size 1 Path
B [A] TestVersionNumber IT Application Oct 9, 2015 8:00:13 AM 4285
Filter by:(T)
[=1 application.descriptor
ConfigureHT| iE)
¡jeljqi
Workload Management Check._for_V2.esql
Configure
| <Type propertiesOct
filter text> of selected
E5QL file
built resource.
9. 2015 8:0... Oct 9, 2015 8:00:12 AM
Oct 9, 2015 8:00:12 AM “3 134
181
Consumer Policy Set Consumer Policy Set Bindings
HSEI
Coordinated Transaction Monitoring Profile Name Provider
B ËHU TestVersionNumberFlow 1
#0 CATCHQ
Policy 5et Provider Policy 5et Bindings Security Profile Name
[Sfl FAILUREQ
#0 FALSEQ
ME IN fcJ
idEfl REPLYQ
Test_Version=2 fcJ
"IP TraceExList
_____________________________________________________________________________________________ !
3
H Properties £3 Problems ( a— Outline Tasks
8. Examine the contents of the Properties view below the BAR File editor view as you
►Command For packaging the BAR contents
Prepara Manage I Jser Log Service Log
click the message flow and each node that is contained within the BAR file.
These properties are known as configurable properties. These properties can be
overridden in the BAR file. In most cases, these properties are a subset of the node
properties that you see in the Message Flow editor.
As an administrator, you might want to use the BAR file editor in the Integration
Toolkit to modify the configurable properties and update the BAR file. Take some time
to examine the configurable properties for the message flow and for each node.
9. Deploy the BAR file to the integration server that is named default on the
_ a. Verify that the integration node and the integration server are running.
In the Integration Toolkit Integration Nodes view, verify that TESTNODEJibadmin
has a green arrow and that the default integration server also has a green up
arrow.

Student Exercises
podrá reproducir o
L- integration Nodes! £3 Integration Registries
E otg Integration Nodes + 3 IIBNODE_NOQM 3-

IIBNODE_WITHQM 3 IIBNODE_WITHQM2 - 3
TE5TN0DE_iibadmin QT, default
b. In the Application Development view, right-click the TestVersion.bar and then click
Deploy from the menu. The Deploy dialog box is displayed.
c. Select the integration server that is named default under the TESTNODEJibadmin
integration node as the target for the deployment.
Deploy
Select Integration server to deploy selected resources.
E-JIj Integration Nodes 1+ IIBNODE_NOQM <3

IIBNODE_WITHQM $ IIBN0DE_WITHQM2 É- J
TESTNODEJibadmin
CD
<x Wm
_ d. Click Finish. A Deploying dialog box is displayed while the BAR file is deployed to the
integration server.
- HA Note
r
As you learn later in the course, there are several ways to deploy a message flow to an
integration server. Another commonly used method in the Integration Toolkit is to click the
BAR file in the Application Development navigator and drag it to the integration server in the
_ 10. Verify that the operation was successful by using the Integration Toolkit Integration
Nodes
view and the Deployment log.
_ a. Select the Integration Nodes view in the lower-left view of the Integration Toolkit (if
it is
not already selected).
Student Exercises
b. Expand the Integration Nodes > TESTNODEJibadmin > default hierarchy until you
IIBNODE_NOQM
see the message flow, TestVersionNumberFlow.
- Integration Nodes
IIBNODE_WITHQM ¿=i
IIBNODE_WITHQM2 I- ¿=l
TESTNODEJibadmin default
-]-^j TestVersionNumber
43} =
TestVersionNumberFlow :
... [e^qi Check_for_V2
If the icon next to a message flow is a green upward arrow, the flow is
successfully deployed and is running.
If the icon is a yellow triangle, examine the Problems view (in the lower-right
pane of the IBM Integration Toolkit) for more status information. It might be that
the message flow is deployed but not yet running.
If the message flow start is in progress, the icon changes to the green upward
arrow when the message flow is started. It is also possible that the flow might
require a manual start, in which case you right-click the message flow, and then
click Start.
You also see another item in the hierarchy (Chec_for_V2). This component is the
ESQL code that the message flow uses in the Filter node. It is included in the
BAR file automatically.
c. Click the Deployment Log tab in the lower-right pane of the Integration Toolkit.
The Deployment Log shows whether the BAR file was deployed successfully,
d. Expand the message in the Deployment Log by clicking the plus sign (+).
Properties Problems > Outline A Tasks . Deployment Log §3

Details Timestamp
B t [TestVersion.bar] has been deployed to integration server default on integration node TESTNODEJibadmin Fri Oct 09 08:29,,,
i BIP2871I; The request made by user 'W52008R2i'i64\iibadmin' to 'deploy' the resource 'C ; /User s/iibadmin/IEM/IIBT i 0/^ Fri Oct 09 08:29,,,
You should see a message that indicates that the BAR file was successfully
deployed to the integration server. BiPnnnns messages that are preceded with a
blue “i” icon (for “information”) indicate success; a yellow triangle icon indicates a
warning message, and a red exclamation point icon indicates a deployment
failure.

podrá reproducir o
Student Exercises
Part 3: Test the message flow by using the Flow Exerciser

In this part of the exercise, you test the message flow by using the Integration
Toolkit Flow exerciser.
ry
r Note
The Flow exerciser automatically builds and deploys a BAR file to the selected integration
server. When you use the Flow exerciser, you can skip the step to manually build and deploy
the BAR file. In this exercise, you manually built and deployed a BAR file in Part 2 so that, as
an administrator, you are familiar with the options for building, modifying, and deploying BAR
files in the Integration Toolkit.
_ 1. In the Message Flow editor, click the Start Flow exerciser icon to deploy the message
flow
and start the Flow exerciser.
I TestVersionNumberFlow.msgflow U ! TestVersion.bar
<] Ç"! Palette
Flow Exerciser 3] I:; ©
k \> ,
Favorites
-w Í ;■ \ -+
hi
_ 2. Select the default integration server on the TESTNODEJibadmin integration node and
then
click Finish.
i Select Integration Server
Select Integration Server

Select the integration server where you want to deploy the message flow and dick Finish,
If the integration server is not currently in recording mode, then recording mode is enabled as a result of this action,
- itg Integration Nodes + $ IIBNODE_NOQM IIBNODE_WITHQM I ¿Î TTRNODF WTTHDM?
3. The application is deployed to the default integration server on TESTNODE_iibadmin.
É TESTNODEJibadmin
1=!Ií- B, .Sv,I
ft EHH
4.
Click Close in the Record Message window.
The deployed message flow is running. It is waiting for a message to enqueue on the
IN queue. When the Flow Exerciser puts a message to the IN queue, the message
flow reads (dequeues) the message and sends it through the message flow.
Test the message flow with the Test_v2_Msg.xmi file by importing the file from the file
system and sending the message with the Flow exerciser.
a. Click the Send a message to the flow icon in the Flow Exerciser toolbar.
Student Exercises
■ T est Ver sionNumberFlo w. rnsgflow £3 TestVerslon.bar

<] Palette Flow Exerciser: a si a
1 \Ö±
L - Favorites ■Cafe . J -n. R — «lit
_ b. In the Send Message window, click the New Message icon.
Send Message
S e nd M essa g e
Create or select a message to send to the fit
-I' tS* Input Messages

new message 1
_ c. For the Name, type: versionis2

_ d. Click Import from file and then click File system.
_ e. Browse to C : \labf iles\Lab03-Tlkt\data, select the file Test_V2_msg.xml, and
then click Open.
The file is imported into the Flow exerciser.
I Send Message
Send Message
Create or select a message to send to the flow. Click the message category header (e.g, Input Messages) for more information.
Input Location: |IN ►Header Message Details —
Import from file

Name | VersionIs2
File name: I C:\labflles\Lab03-Tlkt\data\Test_V2_Msg,xml Workspace... File system...
□ {£' Input Messages
Main
■ ■ ■ 1^3 new
I <InMsg > cVersion >2 </Verslon ></InMsg>
message 1 iJP new
message 2
__ f. Examine the data that was read from the file. In this test file, version is set to 2.
5. You are ready to send the test message to the queue for processing by the message flow.
Before you do, reexamine the message flow diagram.

podrá reproducir o
Student Exercises
Given the test data that you are about to send to the queue, where should the
incoming message go? The possible destination queues are REPLY, UNKNOWN,
FALSE, CATCH, and FAILURE.
6. Click Send.
The Progress Information window shows that the message is sent to the input queue
IN. It also shows the
destination. i^TñTrn
□-[bj Invoke Message Flow(VersionIs2)

v'' Message flows deployment successfully completed S'
Starting
mCL Sending Message to MQ Queue "IN"
S& MQ Queue Monitor "REPLY"
H Stopped listening for response Li
Stopped
7. When the Progress Information window displays Stopped, the test is complete.
Click Close.
8. The message path is highlighted on the message flow. Where did the message
go?
The message path should indicate that message is routed to the REPLYQ node
(which references the REPLY queue) because the Version = 2.
Im I
r Information
_
i
I 1 Progress Information
If you view the queues by using IBM MQ Explorer, you see that the Current queue depth for
the output queue is empty. The Integration Toolkit Flow exerciser does not put the message
to the output queue; it shows the message path only. If you want to view the messages on
the queues, you can use the IBM MQ amqsput sample program or the RFHutil SupportPac to
test the flow by putting a message to the IN queue.
For example, to use the amqsput sample program to verify that the Test_v2_msg.xmi message is
put on the REPLY queue on the IIBQM queue manager, type the following command in an
IBM Integration Console window:
podrá reproducir o
amqsput IN IIBQM < C:\labfiles\Lab03-Tlkt\data\Test V2 msg.xml

J

podrá reproducir o
Student Exercises
9. Following the same procedure that you followed in Steps 4-8, test the flow by using the
other test messages in the c:\iabfiies\Lab03-Tikt\data\ directory.
You should be able to predict the message destination based on the message
Troubleshooting
content and the filter rules that are described in the exercise Introduction.
r
If the message did not go the expected queue, check the following conditions on the IBM MQ
queue manager or the Windows Event Log.
Is the message flow getting The message flow might be in a stopped
messages from the IN queue (is the state.
IBM MQ Open Input Count on the Check the Integration Nodes view in the
IN queue = IBM Integration Toolkit. If necessary, start
i)? the message flow.
If Open Input Count for IN = 0, but the
Is the number of messages on the deployment was successful, you might
IBM MQ Backout Requeue Queue = have a typographical error in the queue
0? name on the MQInput node. Check the
Windows Error Log for one or more error
If Open Input Count for IN > 1, there are
messages.
multiple message flows getting messages
Is the number of messages on the
from IN. This situation is more likely to
IBM MQ Backout Requeue Queue >
happen in later exercises, should you
0 and increasing?
duplicate one flow to serve as a starting
point for another.
Was the message sent to the Check the Windows Event Log to
CATCH queue? determine the cause of the runtime error.
Was the message sent to the Check your test message. Is the
FALSE or UNKNOWN queue? <version> field present? Does <version>
= 2?
Exercise Clean up
_ 1. In the Integration Toolkit, complete the following steps:
_ a. Close the message flow in the Message Flow editor.
_ b. Close the BAR file in the BAR file editor.
_ c. In the Integration Nodes view, right-click the default integration server on
TESTNODEJibadmin and then click Stop recording.
_ d. In the Integration Nodes view, delete all flows and resources from default integration
server on TESTNODEJibadmin.
Right-click the default integration server in the Integration Nodes view, and then
click Delete > All Flows and Resources. Click OK in the confirmation window.
_ 2. Close the IBM Integration Toolkit.
podrá reproducir o
Student Exercises
End of Exercise

podrá reproducir o
Student Exercises

In the first part of this exercise, you imported an Integration Bus project interchange file
into the Integration Toolkit.
In the second part of this exercise, you created a BAR file and examine the configurable
properties by using the Integration Toolkit BAR file editor. You then deployed the BAR file to
the development integration server.
In the third part of this exercise, you tested the message flow by using the Integration
Toolkit Flow exerciser.
Student Exercises
Exercise 4. Administering the IBM Integration Bus

runtime components
In this exercise, you use the IBM Integration Bus commands and IBM
Integration web user interface to manage IBM Integration Bus runtime
components and deploy message flow applications. You also back up
and restore the integration node configuration data.

• Administer IBM Integration Bus components by using the IBM
Integration Bus commands, IBM Integration web user interface, and
IBM Integration API Exerciser
• Deploy IBM Integration Bus message flow applications by using the
IBM Integration Bus commands, IBM Integration web user interface,
and IBM Integration API Exerciser
Introduction
IBM Integration Bus administrators can manage and manipulate the
IBM Integration Bus components by the IBM Integration command
interfaces and the IBM Integration web user interface. While the IBM
Integration web user interface is easier to use and more intuitive,
commands give the ability to fully automate the management tasks by
using scripts.
In this part of the exercise, you use the IBM Integration command
interface to check the status and configuration of the integration node,
integration servers, and message flows. You also use the IBM
In the second part of the exercise, you use the IBM Integration web
interface to check the status and configuration of the integration node,
integration servers, and message flows. You also use the IBM
In the third part of the exercise, you use the IBM Integration API
Exerciser sample program to manage the integration node, integration
server, and integration node. You also used the Integration API
Exerciser sample program to create a script the creates an integration
server.
Student Exercises
In the fourth part of the exercise, you back up the integration node
configuration information.
Requirements
• Lab exercise files in the c:\iabfiies\Lab04-Admin directory

Student Exercises
This exercise uses the IIBNODE_NOQM integration node and integration servers from
Note
Exercise 1, Part 3.
Part 1: Use the IBM Integration command interface

In this part of the exercise, you use the IBM Integration command interface to check the
status and configuration of the integration node, integration servers, and message flows.
You also use the command interface to deploy a BAR file that contains an application.
Important
When you enter commands, do not press Enter where you see a line break in the command.
You must enter commands on a single line, although it is permissible for the command to
wrap to subsequent lines as you type it. Press Enter only after you type the entire command.
1. IBM Integration Bus supplies a special command console from which you run
Integration Bus commands. To view what happens if you try to work outside of the
Integration Console, open a Windows command prompt window.
_ a. From Windows, click Start
_ b. Enter cmd in the Open field and then click OK.
_ c. Enter the command: mqsilist iIBNODE_NOQM
You know that the integration node is deployed and running, so what might cause
this problem?
In the lecture material, you learned that you must run mqsiprofiie.cmdto set up
the environment for various components. Do not run the mqsiprofile command
now.
_ d. Close the Windows command prompt window.
2. Review the mqsiprofile. cmd file in the C: \<Integration Bus Install Path>\server\bin
directory.
In the lab exercise image for this course, the Integration Bus Install Path is c:\Program
Files\IBM\IIB\10.0.0.0\server.
_ a. Use Windows Explorer to locate the mqsiprofile. cmd file.
_ b. Right-click the file and then click Edit to open the file in Notepad.
You can see that the command file sets some environment variables. When you
use the IBM Integration Console in the Windows environment, mqsiprofiie.cmd is
automatically called to set the command environment.
Student Exercises
__ c. Close the file when you are done looking at it. Do not save any changes if you are
prompted to do so.
3. If it is not already running, start the IBM Integration Console as an administrator.
Right-click the shortcut icon on the desktop, or click Start > All Programs > IBM
Integration Bus 10.0.0.0, right-click IBM Integration Console, and then click Run as
administrator.
4. Get a list of running integration servers and message flows on IIBNODE_NOQM by
entering the command:
mqsilist IIBNODE_NOQM -d2
For most commands, you can enter the command followed by a question mark character (?)
to get a summary of the command syntax.
You should see that two integration servers are running on IIBNODE_NOQM: server!
and server2.
You should also see that no message flows are currently running on the integration servers.
5. Deploy the AdminApp.bar BAR file to the server2 integration server.
The AdminApp.bar file contains an application that is named Transfomation_Map. The
application contains a message flow that is also named Transformation_Map.
When deploying a BAR file, the mqsideploy command looks for the file in the current
directory (the one from which the command is run) by default. If the BAR file is not
in that directory, you must specify the full path.
__ a. In the IBM Integration Console, change directories to the directory that contains
the BAR
file (C:\iabfiies\Lab04-Admin\resources) before you deploy the file. Type:
cd C:\labfiles\Lab04-Admin\resources
__ b. Type the following command to verify that the file AdminApp.bar is in the
C: \labfiles\Lab04-Admin\resources directory.
dir
__ c. Type the following command to view the contents of the BAR file:
mqsireadbar -b AdminApp.bar

BIP1052I: Reading Bar file using runtime mqsireadbar...
AdminApp.bar: Transformation_Map.appzip (10/12/15 2:51 PM):
__ d. Type the command to deploy the AdminApp.bar file:

mqsideploy IIBNODE_NOQM -e server2 -a AdminApp.bar
Student Exercises


BIP1039I: Deploying BAR file
'C:\labfiles\Lab04-Admin\resources\AdminApp.bar' to integration node
'IIBNODE_NOQM' <integration server 'server2'>
BIP1092I: The integration node successfully processed the deployment request.
_6. Verify that the flow was successfully deployed. Type:
mqsilist IIBNODE_NOQM -e server2
You should see a response that is similar to the following example:

BIP1275I: Application 'Transformation_Map' on integration server 'server2' is
running.
_7. Remove the deployed message flow application from the server2 integration server:
mqsideploy IIBNODE_NOQM -e server2 -d Transformation_Map
r rf Him ---------------------------------------------------------------------------------------------------------------------------------------------
To reduce the amount of typing you do, you can press the up arrow key on your keyboard in
the IBM Integration Console window to retrieve a previous command. You can then edit the
portion of command that changed (if necessary), by using the left arrow, right arrow, Delete,
and Backspace keys. Press Enter to run the command after you finish editing it.
For example, the command you enter in the next step is identical to the command you
entered in step 7. Press the up arrow key until the mqsideploy command is displayed, edit
the command, and then press Enter to reissue the command.
V _______________________________________________________________________ y
_8. Redeploy the AdminApp.bar BAR file to the server2 integration server on IIBNODE_QM:
mqsideploy IIBNODE_NOQM -e server2 -a AdminApp.bar 9. Enter a command that
stops the message flow application that you deployed in Step 8:
mqsistopmsgflow IIBNODE_NOQM -e server2 -k Transformation_Map
_10. Restart the message flow:

mqsistartmsgflow IIBNODE_NOQM -e server2 -k Transformation_Map
You should see a confirmation message that the application started.

_11. Minimize or close the IBM Integration Console window. You use it later in the exercise.
Student Exercises
Part 2: Use the IBM Integration web interface

In this part of the exercise, you use the IBM Integration web interface to complete basic
administration on the integration node, integration server, and message flow applications.
_ 1. Start the IBM Integration web interface for IIBNODE_NOQM.
If you do not already know the HTTPConnector port for this integration node, type
the following the command to find the port.
_ 2. Display the IIBNODE_NOQM QuickView and Advanced Properties.

_ a. Select IIBNODE_NOQM in the IBM Integration web interface navigator in the left
pane.
_ b. Show the integration node Advanced Properties by clicking the down arrow on the

r Advanced Properties
Platform Name
niter Options...
1IBNODEJJOQM - Integration
Fixpack Capability Operation Mode Node
¿I IIBNODE_NOQM OverviewPlatform Architecture Platform
Statistics
Version Queue Manager Build
Servers -r
&
► ®3 Operational Policy
Level
/“Edi
► 0 Data
Admin Agent Process ID
t
► Security r QuickView
► ^ Monitoring
IIBNODE_NQQM
10DQQ
Admin Security ©off

Run Mode Short running
Description Long
Description
Windows Server 2008 R2 Standard
unrestricted
advanced
AMD64
6.1 build 7601 Service Pack 1
SD0Q-L150316.10572 3004
►Component Properties
3. Display the properties for the server2 integration server.

__ a. Expand Servers by clicking the down pointing arrow on the left side of Servers.
b. Click server2.

Student Exercises
c. Show the integration server Advanced Properties by clicking the down arrow on the
Welcome, Default
IBM Integration
Filter Options...
server2 - Integration Server # Edit

$ I1BNODE_NOQM Q Overview [^v Resource Statistics [*v Statistics
Servers ▼ Quick View
Integration Server Name server2
& Run Mode running
►serverl ~ UUID 7f6a21 da-2ba1 -4d52-920D-b2d74b857816
server2
Running true
► 11=1 Operational Policy Short Description
► ¡g Data Long Description
► Security
► Monitoring
| ▼ Advanced Properties
Injection Mode Disabled
Process ID 2948
Trace Level none
Soap Nodes use Embedded Listener true

Thread Local Proxy Name Managers false
Console Mode off

HTTP Nodes use Embedded Listener false

Trace Node Level on

►Resource Manager Properties
4. Display the properties of a message flow that is deployed to the server2 integration
server.
_ a. Click the arrowon theleft side of server2 to show its contents.
_ b. Click the arrowon theleft side of Applications to show its contents.You should see
that
the application Transformation_Map is deployed to server2.
_ c. Click the arrowon theleft side of Transformation_Map to show itscontents.
_ d. Click the arrowon theleft side of Message Flows to show its contents.
_ e. Click the Transformation_Map message to display its properties and then expand the
Advanced Properties and Deployed Properties sections.
Student Exercises
5. Stop the message flow that is running on server2.
_ a. Click the down arrow next to the Transformation_Map message flow and then
click
Filler
Options... EHI Transformation_Map -
Message Flow
J liBNODEJJOQM » g
Q Overview |*v Statistics (j^ Operational Policy
Serrera r►il serrer! f
r
Edit
& serreß ▼ g Services g ▼ Quick View

REST APIs gl Applications
* 51 TransfQíma!icn_Map Message Flow Name T ransformation_Map
¡§ Libraries ■y ¡P Massanp Version
Flows UUID 3a88e189-9b67-480f-iyD954eOQe«6ea5bb

Commit Count 1
gm Additional Instances 0
Transformation_Map
Subflows t Start Mode Maintained
g Resources ¡¡p Coordinated Transaction no

References Commit Interval 0
Ubraries Running true
jK, Shared Ubraries 0 Run Mode running
Message Flows gl
SuWows gj,
Resources
►¡?j| Operational Policy
1 - Advanced Properties 1
► g Data
►^ Security
►0 Monitoring
▼ Deployed Properties
Modified time 2015-10-12 15:18:28.000 -0700
Deployed time 2015-10-1212:26:51.702 -0700
Bar file name C:\labfiles\Lab04-
Admin\resources\AdmiriApp.bar
Stop.
Version
UUID
▼ @ Applications
Service T
V ^ Transfornnalion_Map v (5
Commit C
Libraries T EG Message Flows
Additions
p Transformation_Map ▼ ¡
^ Subflows ff Transformation_Map 3(i
► £L, Resources
j|| References Stop —r
r
^ Libraries Force stop 3
b. Verify that the runMode property for the message flow is now set to stopped.

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunatgob.pe>. La impresión está destinada únicamente para uso personal y privado.
Student Exercises
6. Delete all deployed applications and resources on server2.

_ a. Click the down arrow on the right side of server2 to display the menu, and then click
Delete All.
IIBNODE_NOQM v ¡g Servers ▼
► serverl ▼
- server2 ▼i
CD
¿5 Servie <£: server^
g REST Start
’ ©Applic Start All Application Types
- ^ Tr; Start All Message Flows
s Stop
-& Stop All Application Types
Stop All Message Flows
Eta Rename
Delete All
s
Delete
3 Librari Deploy
_ b. A confirmation window asks if you are sure that you want to delete all deployed
contents. Click Yes on the confirmation window.
_ c. Verify that no applications are deployed to server2.
7. Deploy the AdminApp.bar file to serverl.
_ a. Click down-arrow on right of serverl and then click Deploy.
» ¿I IIBNODEJNQQM y r= Servers v
►serverl 3
r ^ server2 {£. server!
¡g Servie Start
(3 REST Start All Application Types
- gj Applio Start All Message Flows
- SI Tr; Stop
3 Stop All Application Types
-m Stop All Message Flows
Rename
& Delete All

►
m Deploy
3 Librari Start recording
fé Share Stop recording
b. Click Browse and browse to C:\labfiles\Lab04-Admin\resources, click AdminApp.bar,

and then click Open.
Student Exercises
c. Expand the contents of the BAR file to view the configurable properties of the
message flow
and the
message flow
BAR file: AdminApp.bar Browse

Deploy
Content Value
T
Transformado nJYIap.appzip A
startMode <unset>
javal solation <unset>
T
Transformatton_Map ...
additionaJ Instances <unset>
ntotificationTtireshold M sg sPerSec <unset>
maximum RateMsgsPerS ec <unset>

V
processing! ¡meo utSec <unset>
Overrides
node.
Deploy BAR File

Select a BAR file to deploy. Optionally, provide an overrides file.
Cancel
__ d. Click Deploy.
__ e. Verify that the Transformation_Map message flow application is deployed to server!.
8. The IIBNODE_NOQM integration node that you are using in this exercise does not
have a queue manager that is associated with it. In this step, you see what happens
r teg ration
a. In the IBM Integration web interface for IIBNODE_NOQM, click down-arrow on
right of server!Filter
and then click
Options... Deploy.
£) The deployment of the BAR file 'Adminl .bar* to 'serverl' has failed. BIP2087 06:03 X
3NODE NOQM b. ▼ Click Browse and browse to C:\labfiles\Lab04-Admin\resources,

Q Overview ['V Resource Statistics ['V Statistics
click Adminl .bar,
I Servers -w and then click Open.
^ Edit
¿1, serverl ; *r] Click Deploy. After a brief pause, an error message displays in the web interface
c.
çŒ. Services
M REST APIs
that indicates that the deployment | ▼ Quick View
failed. A
when you try to deploy a message flow that requires a default queue manager.
Welcome, Default '

- 0 Applications Course materials may not be reproduced in whole or in part
Intearation Server Name
podrá reproducir o
Student Exercises
9. The error detail is provided in the Admin Log in the IBM Integration web interface.
_ a. Click the arrow on the left side of the Monitoring folder to show its contents.
_ b. Click Admin Log.
_ c. Review the messages in the Admin Log.
One of the error messages in the Admin Log describes the reason why the
deployment failed. In this case, deployment failed because the message flow in the
BAR file requires a default queue manager on the integration node.
Welcome, Default -
IBM Integration
Filter Options...
Admin Log
▼ $ IIBNODE_NOQM ▼
^ Overview
▼ {jj= Servers v
► £ serverl ▼ <£* Refresh
► ^ server2 ▼ Message Source Timestamp ▼ Message Detail

► llg Operational Policy
► ¡gj Data
Integration server 'serverl' received an administration request
A

that encountered an exception. While attempting to process a n
▼ Monitoring administration request, an exception was encountered. No u
Y Admin Log pdates have been made to the configuration of the integration
server. Review related error messages to determine why the
administration request failed.
0 BIP2683E Runtime Response 2015-10-13 06:03:45.237 A component was configured to use the queue manager that i s
Pacific Daylight Time specified on the integration node, but no queue manager wa s
found for the integration node. By default, components in IB M
Integration Bus use the queue manager that is specified on the
integration node to connect to WebSphere MQ. No queue
manager is specified on the integration node, so the compone
nt cannot resolve the connection to a queue manager. For M
Qlnput, MQOutput, and MQGet nodes, it is possible to specify a
queue manager on the message flow node, but for Aggrega
tion, Collector, Sequence, and Resequence nodes, the queue
manager must be specified on the integration node. Specify a
queue manager on the integration node, or use a queue man
ager that is specified on a MQInput, MQOutput, or MQGet no de.
t) BIP28711 Administration Result 2015-10-13 06:03:45.237

The request made by user 'SYSTEM[Default]' to 'deploy' the r
Pacific Daylight Time esource Adminl.bar' of hype ’BAR' on parent 'serverl' of type
'ExecutionGroup' has the status of FAILED'.
Integration node 'IIBNODE_NOQM' was unable to process th e
internal configuration message. The entire internal configura V
tion message failed to be processed successfully. Use the me
ssages following this message to determine the reasons for th
10. Minimize the IBM Integration web interface browser window.
Student Exercises
Part 3: Use the IBM Integration API Exerciser

In this part of the exercise, you use the IBM Integration API Exerciser to manage an
integration node and its resources. You also use the Integration API Exerciser to create an
administration script.
_ 1. Start the IBM Integration API (CMP) Exerciser.
_ a. In Windows Explorer, browse to the C:\Program
Files\lEM\lIB\10.0.0.0\server\sample\lntegrationAPI\ directory.
_ b. Double-click the startintegrationAPiExerciser.bat file to start the IBM
Integration
API Exerciser.
_ 2. To connect to the local integration node, right-click Right-click to connect and then
click
Connect to Local Integration node.
[& IBM Integration API (CMP) Ewerciser

I [Right-dick to correct! I ----------------—
Connect to Local Integration node,,,

Connect to Remote Integration
node,,,
F=
3. Select the IIBNODE_NOQM integration node, and then click Submit.

podrá reproducir o
Student Exercises
4. After a connection is established, the status information is displayed in the lower part
of the Integration API Exerciser window. The upper part of the window displays
information about the integration node.
Student Exercises
5. Select the message flow Transformation_Map.msgflow that you deployed to the

integration server server! to display the message flow properties.
6. By right-clicking the message flow, you can turn on tracing, start and stop the
message flow, delete the message flow, and complete other operations.
J&V IBM Integration API (CMP) Exerciser
File View Scripting
fi> MessageFk
IIBNODE_ getDeployedPolicySet
NOQM getDeployedPolicybet
serverl
B-ia Transformation_Map,appzipRefresh
Show raw property table for this
■ MM Transformation_M?nobject
mcnF|n
> Li Transformation_Mi 5
Ci Transformation_Mc Ci Start
Stop
A
InputXMLSchema.>
JË
■ Ci
OutputXMLSchema =L, Delete
E
server2 Y Administration !oc
Get Activity Log
Log |_J Administration y
Queue Configurable
Services
User Trace
Service Trace
Flow statistics
Set additional instances,..

Set runtime property... Success Set user
defined property,, Success Properties...
Stop the flow by clicking Stop on the menu.

7. Verify that the flow stopped by verifying that the runMode property is now stopped for
the Transformation_Map.msgflow.
I&IBM Integration API (CMP) Enerciser

i> IIBNODEJÖQM Fl- = . serverl coordinatedTransactlon no
B"E Transformation_Map,app!lp commitlnterval

0
version
j i ........... ü[rransformat¡on_Map,msgflow
TKancFnKmahinn Man
! . fJl Transformation_MapJnputMessage, xml
runMode stopped
j .. TransformatlonJIap.map
; . i m InputXMLSchema.xsd
!
.. 5 OutputXMLSchema.xsd getCommitCountO
!*■■=, serverE: g e tC o m mit In te r val()
0
V Administration Log :—U Administration Queue É- getConfigurationObjectT ype() <Message Flow>
& Configurable Services getConfigurationObjectTypeOfParent() <Application>
getCoordinatedTransactionO else
You can also use the IBM Integration web interface for IIBNODE_NOQM to verify the
status of the message flow.
8. Delete the server2 integration server.
Right-click the server2 integration server on IIBNODE_NOQM and then click Delete.
The delete is completed without confirmation.

podrá reproducir o
Student Exercises
9. With the IBM Integration API Exerciser, you can record a script of an operation, which
captures it for reuse. You can then run this script against other integration node
environments.
Create a script that records the steps for creating an integration server and save it in the
a. From the IBM Integration API Exerciser menu bar, click Scripting > Record New
Script.
b. Browse to the C:\iabfiies directory and specify a descriptive name, such as
CreateNewIS. xml.
c. Click Save. Scripting is now active.
d. Right-click the IIBNODE_NOQM integration node and then click Create integration
server.
Á IBM Integration API (CMP) Exerciser
File View Scripting
1=
=í> IIBMOÜE NO™
Refresh
+]-5 server 1 ■’p’
Adrninist ■ Adrninist
Í1 Configur
Create integration server,,,
_ el
Start all message flows el
el
Stop all message flows
el
_ e. Name the new integration server server2, and then click Submit.
_ f. After you see the new integration server show in the list of integration servers, stop the
script recording by clicking Scripting > Stop Recording.
10. From the IBM Integration API Exerciser, delete the server2 integration server.
11. Re-create the server2 integration server from the script.
_ a. Click Scripting > Play Back Recorded Script.
_ b. Browse to the C:\iabfiies directory.
_ c. Click the XML file that you created in Step 9 and then click Open.
The script runs and creates the server2 integration server again. The integration
server is displayed in the list after it is created.
Student Exercises
_ 12. Verify the server2 integration server by deploying an Integration Bus application.
_ a. Right-click the server2 integration server and click Deploy BAR.
I ft. IBM Integration API (CMP) Exerciser
Scripting
I File View
I =i> IIBNODEJOQM
1 + server 1
: ■“
! D -' rpKiJ Refresh
i .. f Adm
i .. _ Adm Show raw property table for this object
Deploy BAR.,.
EE& Coni 1
Start
Stop
_ a. Browse to the c:\iabfiies\Lab04-Admin\resources directory and then select the

AdminApp.bar file. Click Open and wait for the deployment to complete.
_ b. Verify that the message flow was deployed and running.
Part 4: Back up and restore the integration node

In this part of the exercise, you back up the integration node configuration information.
Normally, you want to back up the integration node configuration information to a separate
drive. For this exercise, you create a local folder and back up to that location.
_ 1. Use Windows Explorer to create a directory that is named iiBNODE_Backup in the
_ 2. Open an IBM Integration Console and back up the integration node configuration to the
new
folder. You can use the -a option to name the archive. You do not use it here so that
you can see the default file name for the archive.
Type the following command to back up IIBNODE_NOQM:
mqsibackupbroker IIBNODE_NOQM -d C:\labfiles\lIENODE_Backup
The command should return a message similar to the following example:

BIP125I: Creating backup file
'C:\labfiles\IIBNODE_Backup\IIBNODE_NOQM_ccmmdd_him7mss.zip' for integration node '
IIBNODE_NOQM'.
In the response message, ccmmdd is the year, month, and day, and hhmmss is the hour,
minute, and second of the backup file creation time.
_ 3. With Windows Explorer, browse to the c: \iabfiies\iiBNODE_Backup directory and verify
that the backup file is in the directory.

podrá reproducir o
Student Exercises
You now have all the necessary information to restore your integration node. This file
c
a Important
n
be copied and stored elsewhere (on some type of external media) or, at a minimum,
on a separate drive from where the domain exists.
r
The integration node backup command does not back up all the resources that message
flows require to function correctly. These resources include:
- IBM MQ queues
- Data that is stored in user databases
- Transient information for inflight aggregations or collections
- Runtime code, including resources that are associated with user-defined extensions
such as nodes, parsers, and exits
4. Simulate a system failure by deleting the integration node and integration node
components. After you complete the system failure simulation, you restore the
integration node and components by using the backup file that you created in Step 2.
_ a. From the IBM Integration web interface for IIBNODE_NOQM, stop any message
flows
that are running on server! and server2.
_ b. From the IBM Integration web interface, delete the integration servers.
_ c. From the IBM Integration Console, stop and then delete the integration node
IIBNODE_NOQM and all files in its workpath.
Type:
mqsistop IIBNODE_NOQM mqsideletebroker
IIBNODE_NOQM -w
You can also stop the integration node services by using the Windows Services control panel.
Click All Program > Administrative Tools > Services.
Scroll to the IBM Integration Bus component for the integration node and then click Stop.
5. Attempt to start the integration node from a command console:

You should receive a message that indicates that the integration node does not exist.
6. Re-create the integration node IIBNODE_NOQM.
Type: mqsicreatebroker IIBNODE_NOQM
Student Exercises
Do not start the IIBNODE_NOQM integration node after you create it. The integration node
Important
must be stopped before you can restore it.
7. Using the IBM Integration Console, restore the integration node. Type:
mqsirestorebroker IIBNODE_NOQM -d C:\labfiles\lIBNODE_Backup -a arch±ve_flle
In the command, replace arch±ve_f±ie with the name of the archive file that the
mqsibackupbroker command creates in Step 2.
After the restore completes, you receive a message that indicates that the integration
node was restored.
8. Start the integration node by using the IBM Integration Console.
9. Get the port number for the IBM Integration web interface for IIBNODE_NOQM.
Type:
10. Using the IBM Integration web interface, verify that the integration node is restored
correctly. It might be necessary to enter the URL for the IIBNODE_NOQM integration
node again.
You should have two integration servers that are named server! and server2.
The integration server server2, should be running the Transformation_Map
application.
Exercise clean up
_ 1. Stop any message flow applications that are running on server! and server2 on
IIBNODE_NOQM.
_ 2. Delete any message flow applications from server! and server2 on IIBNODE_NOQM.
End of exercise

podrá reproducir o
Student Exercises

In this part of the exercise, you used the IBM Integration command interface to check the
You also used the IBM Integration command interface to deploy a message flow.
In the second part of the exercise, you used the IBM Integration web interface to check the
You also used the IBM Integration command interface to deploy a message flow.
In the third part of the exercise, you used the IBM Integration API Exerciser sample program
to manage the integration node, integration server, and integration node.
In the fourth part of the exercise, you backed up the integration node configuration
information. Having complete this exercise, you should be able to:
• Administer IBM Integration Bus components by using the IBM Integration Bus
• Deploy IBM Integration Bus message flow application by using the IBM Integration Bus
Student Exercises

Student Exercises
Exercise 5. Using file-based security to control


In this exercise, you use roles and file-based security to control
administration access to the IBM Integration web user interface,
integration nodes, integration servers, and message flows.

• Use IBM Integration Bus file-based security to assign permissions
for integration nodes, integration servers, and message flows
Introduction
Administration security controls the rights of users to complete
administrative tasks for an integration node and its resources.
IBM Integration Bus V10 can control access to Integration node
resources through the IBM Integration web user interface. Different
web users can have different access rights across these functions, and
access can be granted, denied, or revoked.
The access authorities are defined against a set of user definitions that
represent the available security roles. A role is a set of security
permissions that control access to an integration node and its
resources, and each web user account is associated with a particular
role. The permissions are checked to determine a web user's
authorization to complete tasks in the web user interface or the REST
application programming interface (API). Each web user is then defined
to use one or more of these security roles.
In this lab, you use an integration node that does not have a queue
manager that is associated with it (IIBNODE_NOQM) and create three
user roles.
iibRoiei For integration node administration access, read-only
iibRoie2 For integration node administration access, read, write
iibRoie3 For integration administration access, all functions
In the second part of the exercise, you create web users and assign
them to one of the defined roles.
Finally, you explore the IBM Integration web user interface as each
user.
Student Exercises
Requirements
• Lab files in the c: \iabfiies\Lab05-Sec directory

podrá reproducir o
Student Exercises
Exercise set up
_ 1. Check the status of file-based administration on the integration node IIBNODE_NOQM.
In an IBM Integration Console window, type:
Ensure that you see the line: Administration security = 'inactive'

If security is active on the integration node, deactivate it by typing the following commands:
2. If not already open, open a web browser and start the IBM Integration web interface for
IIBNODEJMOQM.
You should see that you are currently logged in as a user this is named Default.
|45'IIBNODE_NOQM - IBM Integration - Internet Explorer
» |@http:/flocahostl441S/#bcoter/0 p_^j |*t 'ÿ IIBNODE_NOQM - IBM Integ.,.

x[_l
IBM Integration Welcome, Default ”■ 1
Filter Options... *=3

' IIBNODE.NOQM ~ 0 overview ^Statistics
▼ £= Servers ▼
▼ ^{servai] ▼
I llBNODE_NOQM - Integration Node
The Default user has full update access to all deployed integration node resources.
3. Click IIBNODE_NOQM to display its properties. In the Quick View properties, you should see
that Admin Security is off.
Filter Options... IIBNODE_NOQM - Integration Node
- ill illBNODEJJQQM: v Overview | •. Statistics
T • servers ▼
▼ Q.. serverl ▼
T Quick View
g Services g REST APIs g
Applications g Libraries
Node Name IIBNODE_NOQM Version 10000
Spared Libraries g Message
Admin Security Off
Flows ifj Subflows Q, Resources ▼ £
server2 ▼ ^Run Mode running Short Description Long Description
4. Using the Integration web interface, deploy the file

C:\iabfiies\Lab05-sec\resources\AdminApp.barto the serverl integration server.
Student Exercises
After a brief pause, you should see that the Transformation_Map application deployed
successfully.
- J IIBNODE_NQQM ▼ T ¡S
servers -r - ^ serverl T (g
Services jg REST APIs ¡g
Applications
T Transformation_Map T ^5
Libraries ■r EG Message Flows
Transformation_Map T ^
Subflows T & iResou'ces
lnputX.MLSctiema.xsd ^
OurtputXMLSchema.xsd rg.
Transfornnation_Map.n(iap jj
Transfbrmation_MapJnputMessage„xiril gjl
References
If the integration node web administration HTTP listener is enabled, and security is not active
for the integration node, then any user can access the Integration web user interface and
control the integration node resources.
Part 1; Activate file-based security on the integration node

In this part of the exercise, you activate security for the IIBNODE_NOQM integration node.
_ 1. If an IBM Integration Console is not already open, start an Integration Console session with
Windows “Administrator” privileges.
_ a. Click Start > All Programs > IBM Integration Bus 10.0.0.0, right-click IBM Integration
Console 10.0.0.0, and then click Run as administrator.
Optionally, you can right-click the IBM Integration Console icon on the desktop and then
click Run as administrator.
_ b. Click Yes to run the IBM Integration Console with “Administrator” privileges.
_ 2. Security can be activated only when the integration node is shut down. Type the following
command to stop the integration node:
When you enter the mqsistop command, you should see that the IBM Integration web
interface page is unavailable with the message Real-time updates disabled.
_ 3. In the Integration Console, view the status of administration security and the current
authorization mode. Type:
mqsireportauthmode IIHNODE_NOQM

Student Exercises

Authorization mode = 'file'
As expected the administration security is returned as inactive. Also, this integration node was
created without a default queue manager, so default authorization mode is file.
4. Activate administration security on IIBNODE_NOQM. In the IBM Integration Console, type:
mqsicdiangeauthmode IIBNODE_NOQM -s active -m file

5. Restart the integration node. In the IBM Integration Console, type:

6. After a short pause, reload the IBM Integration web user interface by clicking the indicator in the
address page.
You are now presented with a sign-on screen because administrative security is now active.
IBM Integration
User ID:
Licensed Materials - Property of IBM Corp. Copyright by IBM Corp. and others) 2001, 2015.
IBM, and the IBM logo are trademarks of International Business Machines Corporation, registered in many jurisdictions
worldwide. Java and all Java-based marks and legos are trademarks or registered trademarks ctf Oracle and/or its affil
iates. Other prodluct or service names may be trademarks of IBM or ether companies. Microsoft: is a trademark of
Microsoft Corporation in the United States, other countries, or both.
Student Exercises
Part 2: Define administration roles and set file-based permissions.

In this part of the exercise, you create administration roles and grant administration authorities to
these roles. You reference these roles in the Integration Bus web user definitions that you create
later in this exercise.
Three levels of authorization are supported for IBM Integration Bus administration security: read, write,
and execute. You can assign permissions to a role (user) by specifying the type of permission followed
by a plus (+) to grant permissions, or a minus (-) to revoke permissions.
The following table shows the file-based authorities that are required for different types of users in this
exercise:
Role Authority
iibRolel Read (view resources)
iibRole2 Read, write (view resources,create integration servers, and modify settings)
iibRole3 Read, write, execute (start, stop, deploy, and modifying resources)
_ 1. Check whether there are any roles that are defined on the integration node. In the
mqsireportfileauth IIBNODE_NOQM -1
You should see the response:

No defined roles are returned.

_ 2. Create the iibRolel role. In the Integration Console, type:
mqsichangefileauth IIBNODE_NOQM -r iibRolel -p read+

mqsichangefileauth IIBNODE_NOQM -r iibRole2 -p read+,write+

mqsichangefileauth IIHNODE_NOQM -r iibRole3 -p all+
_ 5. Enter the command for displaying any defined roles again. In the Integration Console, type:
mqsireportfileauth IIHNODE_NOQM -1
The returned response should be as follows:

BIP8931I: Role = 'iibRolel', Resource = '', Permissions =
'read+,write-,execute-
'read!,write!,execute-
'read!,write!,execute!
_ 6. Define an Integration Bus web user that has read-only access.
This user can see deployed applications, but cannot control the status of these applications.

Student Exercises
In an Integration Console, type:

mqsiwebuseradmin IIBNODE_NOQM -c -u adminl -a passwOrd -r iibRolel
This command defines a new web user, adminl. The user has the security profile that the
iibRolel role defines. In this case, the user can view the integration node and any deployed
applications.
7. Define an Integration Bus web user that has read and write access.
This user can see deployed applications, and can change properties on the integration node and
integration server.
iibRole2 role defines. In this case, the user can view the integration node and integration
servers, and edit their properties. This user can also view the deployed resources.
8. Define an Integration Bus web user for all access.
This user can see deployed applications, and can control all the integration node resources. In
the Integration Console, type:
iibRole3 role defines. In this case, the user can view the integration node, integration servers,
and any deployed applications. This user can also control all resources.
9. Display the defined web users. In the Integration Console, type:
The response should be similar to the following example:

BIP2837I: Web user 'adminl' is defined as having a role of
mqsiwebuseradmin IIBNODE_NOQM -1
'iibRolel'.
'iibRole2'.
'iibRole3'.
Student Exercises
Part 3: Test the IBM Integration web interface with security

In this part of the exercise, you log in the IBM Integration web interface and test each user role.
_ 1. Log in to the IBM Integration web user interface as the admini user. The role for this user is
“read-only”.
In the IBM Integration browser window for the IIBNODE_NOQM integration node, login with
the user ID admini (password is password).
_ 2. Verify that Quick View properties for IIBNODE_NOQM show that Admin Security is On.
IIBMODE_NOQM ■ Integration Node

Q Overview |*v Statistics
▼ Quick View
Node Name
IIBNQDE_NQQ
M
Version 1DD00
Admin Security On
Run Mods running
Short Description Long Description
_ 3. In the Integration web interface, expand the Servers folder.

You should see the available integration servers but you cannot view any of the resources.
_ 4. You gave the role iibRolel 'read' authorities at an integration node level. Setting integration
server authority provides more granular approach to authorization. You can authorize each
integration server with a separate command.
Also, with Integration Bus file-based authorization, you can change the roles' permissions
without a restart of the integration node; changes are recognized dynamically.
Change the integration server authorization so that the admini user with role iibRolel can
view the integration server resources. In the Integration Console, type:
mqsichangefileauth IIHNODE NOQM -e serverl -r iibRolel -p read+
The -e serverl parameter specifies the integration server, which means that now you are
applying the permissions at the integration server level.
_ 5. In the IBM Integration web interface, refresh the page.
_ 6. Expand the serverl integration server.
You can now view the resources on the integration server.
Although you can expand the serverl resources folders, you do not have permission to start,
stop, or other actions to the deployed artifacts.
_ 7. Try to create an integration server.
_ a. Click the arrow to the right of Servers and then click Create.

IBMIIBNODE
b. Integration
theNOQM Filter Options...
type(5 Overview
The integration server
adminiserver could not be created Welcome, adminl
Student Exercises
c. InHover dialog
with your box,mouse over
BIP2852 the notification and then click
message. OK.You should see that this message is
a
IMPRESO POR: Jafert Frank Rabines Escorza hyperlink. Click
You<jrabinese@sunat.gob.pe>.
should see a messagethe link. that está
La impresión thedestinada
integration únicamente server paracoulduso personal not be created.
y privado. No se
podrá reproducir o
retransmitir ninguna parte de iftie intiera
Ôeste You
libro ton
sin la æ'rvër
see acöufdnöt
detailed
autorización be created
previa del 5ÌP2352
message,
editor. ........................................................................................................................
Todo explaining
infractor será objeto whydethe attempt
acciones legales. to create the integration 1 11:34 x server
failed.
BIP2852E: The user '¡¡bRolef is not authorized to perform the requested operation 'create' against the object 'adminiserver of
type 'ExecutionGroup'. The user 'iibRolef'' needs to have Write' permission on the object 'adminiserver' of type 'ExecutorGroup'. The
user initiated a request to the integration node to complete an action on an object. The request was rejected by the integration node
because the user does not have the required authorization. Set up authorizations for Iris object to grant the required authority to this
user ID.
8. After exploring the options for the user adminl, log out of the IBM Integration web user interface.
Click the arrow next to the Welcome, adminl banner and then click Log Out.
Welcome, adminl ”
Edit Profile
Log Out
9. Log in to the IBM Integration web user interface as the admin2 user, which is the user with read
and write permissions. The password is password.
This user can view resources, edit integration node properties, and create Integration servers.
10. Expand Servers.
You should see that although you can view the available servers, the role to which admin2 is
associated is not authorized to access the integration server. The role for admin2 has read and
write access for the integration node, but not for any integration servers.
11. Set read and write access to the server! integration server for role iibRole2. In the Integration
Console, type:
mqsichangefileauth IIBNODE NOQM -e serverl -r iibRole2 -p read+,write+
This command allows this role to view the resources on the serverl integration server.
podrá reproducir o
Student Exercises
_ 12. In the IBM Integration web user interface, refresh the login for admin2 (press F5 or click
Refresh).
_ 13. Click the server! integration server in the Integration web interface. You now see an Edit
icon on the properties view (which was not available for user admini).
Welcome, adminZ
Filter Options...
Q Overview [ry Resource Statistics [*y Statistics
server2
► Operational Policy
► g Data ▼ Quick View
► Security Integration Server Name server!
► ^ Monitoring
Run Mode running
UUID 13fca595-530f-418b-be00-a1 b85170eeb8
Running true
Short Description
Long Description
IBM Integration

_ 14. Click Edit.
The table with the properties for the serverl integration server should open. The user admin2
should now have the authority to change the integration server properties.
_ 15. You do not change the integration server properties in this exercise. When you are done
reviewing the properties, click Cancel.
_ 16. The user admin2 has 'write' authorities, which allows the user to create an integration server
on the integration node.
Try to create an integration server that is named admin2server.
This action should succeed because admin2 has the required authorization.
_ 17. Even though admin2 can create the integration server, the administrator must authorize the
role to which admin2 is associated to allow the user to control the new integration server.
In the Integration Console, type;
mqsichangefileauth IIBNODE_NOQM -e admin2server -r iibRole2 -p reach-,write+
This command sets the permissions for this role on the admin2server integration server as
read and write.
_ 18. Refresh the IBM Integration web user interface. If necessary, log in as admin2 again.
Now, the web user can view the new integration server and its resources (although no
resources are currently deployed). The user can also edit the integration server properties.
_ 19. Log out of the IBM Integration web user interface.
_ 20. Log in to the IBM Integration web user interface as admin3.

podrá reproducir o
Student Exercises
This user has full control for the integration node resources, which includes stopping, starting,
and deploying applications and starting and stopping statistics.
21. Although admin3 has full authorities for the resources on the integration node, the
administrator must provide extra permissions to iibRole3 so that the user can manage the
integration server.
mqsichangefileauth IIBNODE_NOQM -e serverl -r iibRole3 -p all+
22. Refresh the Integration web interface and then expand the Servers > serverl.
You should see that now there is an arrow on the right side of serverl, which was not there for
admini and admin2 web users.
Click the arrow to display the menu.
You should see a menu that contains all the administration tasks that web user admin3 can
complete.
Overview
- ^ IIBNODE_NOQM -
► serverl ^ server2
admin2se fla <g=. serverl
Operational F Data Start
►Security m
Start All Application Types Start
►Monitoring Al I Message Flows
► Stop
► Stop All Application Types Stop
All Message Flows
Rename
L
Delete All n
Delete
Deploy
Start recording
Stop recording
Statistics on
Statistics off
Resource statistics on
Resource statistics off
¡g! Servers <*■

23. Click Stop to stop the integration server.
After a few seconds you should see that the integration server stopped, as indicated by the down
pointing red arrow.
▼ Servers ▼
herverl jVj ^
servetZ
^ admin2server
podrá reproducir o
Student Exercises
24. Expand the server! menu again and then click Start to start the integration server.
25. When the integration server starts, expand the Applications group and then click
Transformation_Map.
26. Click Stop on the Transformation_Map menu.
- <3 I1BN0DE_N0QM -r Overview
■» (= Servers ▼
"■ served ▼
¿5 Services
- Quick View
0 REST APIs
- çjSJ Applications Integrati
► ^1 Transfer mation_Map
Libraries 55 Tran sforma tior_Map
The application and all its flows are stopped,
g Message Flows Stop
as the down pointing red SubHows Delete arrows indicated.
27. Delete the Resources Statistics on
server2 Statistics off

Transformation_Map application.
28. Log out user as user admin3.
Exercise clean up
_ 1. Deactivate administration security on the IIBNODE_NOQM integration node.
_ 2. Delete the integration server admin2server.
mqsideleteexecutiongroup IIBNODE_NOQM -e admin2server
End of exercise

Student Exercises

In the first part of this exercise, you activated file-based security and then created three user roles.
In the second part of this exercise, created web users and assigned them to one of the defined roles.
In the third part of this exercise, you explored the IBM Integration web user interface as each user and
configured security authorizations for integration servers.
• Use IBM Integration Bus file-based security to assign permissions for integration nodes,
integration servers, and message flows
Student Exercises

Student Exercises
Exercise 6. Using queue-based security to control


In this exercise, you use the IBM Integration Bus security queues on IBM MQ
to set and test IBM Integration Bus access control for the integration nodes,
integration servers, and message flows.

• Use the IBM Integration Bus security queues on IBM MQ to assign
permissions for integration nodes, integration servers, and message
flows
Introduction
IBM Integration Bus can use a special set of IBM MQ SYSTEM.BROKER
queues to control access to each entity that must be secured in terms of
administrative access. Each administrative action, such as creating an
integration server, and deploying or stopping a message flow, is mapped to
one of three categories; read, write, or run. These categories are mapped to
IBM MQ security properties as follows:
• Inquire maps to Read
• Put maps to Write
• Set maps to Run
One or more of the IBM MQ security permissions are set on a particular queue
to control access to the object that queue represents; an integration node or an
integration server. This design uses a familiar, already present mechanism
(queue security) and provides excellent granularity and flexibility.
In the first part of this exercise, you set up user and group authorities for a non-
privileged Windows user (No_Auth_iD). That same user ID is used in testing
the next parts of this lab.
In the second part of the exercise, you activate IBM Integration Bus security.
You then use the same non-privileged user ID (No Auth iD) to show that the
user cannot use any functions in the IBM Integration Bus environment.
In the third part of the exercise, IBM Integration Bus security is activated. The
same non-privileged user ID is used to demonstrate that the user cannot use
Student Exercises
any functions in the Integration Bus environment until authorization is
configured on the IBM MQ authorization queues.
r / Note ---------------------------------------------------------------------------------------------- ^
This exercise uses the IBM Integration API Exerciser to test queue-based security. It is important that
you understand that all Integration Bus applications are subject to security authentication when
administrative security is active. Those applications include the IBM Integration Toolkit and the IBM
V ______________________________________________________________________________ J
Requirements
• The IIBNODE_WITHQM integration node and the IIBMQ IBM MQ manager
• Lab files in the c : \iabfiies\Lab06-QSec directory
• Microsoft Windows user that is named No_Auth_iD and group that is
named Securityjrest with IBM Integration Bus permissions as shown in
Part 1 of the exercise

Student Exercises
Exercise set up
_ 1. To effectively test administrative security, you must run under a different user ID than the
administrator ID iibadmin because it has full authority over the integration node
environment. Logging out of that account and logging in as another user is not a good
solution on Windows because that starts a different or unique configuration of installed
software. The solution is to use the Windows option to Run as different user. With this
option, you can run a program with different permissions than the currently logged-on user ID
provides.
In this exercise, you use the Run as different user option in this lab to run the IBM
Integration API Exerciser under the No_Auth_iD user ID. The No_Auth_iD is a member of
the group security_Test. The No_Auth_ID user ID is not a member of the mqbrkrs or
mqm groups.
Verify that you have a user ID that is named No Auth iD user ID and that this user is
member of the group security_Test.
_ a. Start the Windows Computer Management application by clicking Start >
Administrative Tools > Computer Management.
_ b. In the Computer Management window, expand Local Users and Groups.
_ c. Click Users. A list of all users and groups is displayed in the right pane.
_ d. In the right pane, double-click the user ID No_Auth_iD.
_ e. Click the Member of tab and review the groups to which the user ID belongs. Notice that
the user ID is not a member of the mqbrkrs, mqm, or Administrators groups.
_ f. Click Cancel to exit without saving any changes to the user ID.
P Computer Management
File Action View Help
_ g. Close the Computer Management window.
'■1- Computer Management Name Full Description

(Local) B ' System Tools E 0 Administrat
Name
h o A u t h i D Properties irmi
Task Scheduler E I Event Viewer or ^4 Guest
E ;■/ Shared Folders B iP Local iibadmin Remote Desktop Services Profile Personal Virtual Desktop Dlal-ln
Users and Groups 3 Users MUSP._MQAD General Member Of j Profile | Environment | Sessions | Remote control
Groups No_Auth_ID
E 'V Performance Member of:
A Device Manager E ^
Securlty_Tes
Storage
:: t jfc Users
- Disk Management E
Student Exercises
_ 2. In this exercise, you use the IIBNODE_WITHQM integration node with the default queue
manager IIBQM that were created in Exercise 2.
Verify that the IIBNODE_WITHQM integration node and IIBQM are created and running.
_ a. Start IBM MQ Explorer if it is not already running. Verify that the queue manager IIBQM
is defined and running.
_ b. In an IBM Integration Console, type the following command to verify that the integration
node IIBNODE_WITHQM is running.
mqsilist IIBNODE_WITHQM
_ 3. Start the IBM Integration web interface for IIBNODE_WITHQM.

If you do not know the HTTP Connector port for the web interface, type the following
command in the Integration Console.
mqsireportproperties IIBNODE_WITHQM -b webadmin -o HTTPConnector -a
Part 1: Set IBM MQ permissions for users

If you are using any Integration Bus functions that require access to IBM MQ, permissions are
required to enable users to connect to the integration node.
In this part of this exercise, you set up IBM MQ permissions for a non-administrator users
(No_Auth_iD) that is a member of the security_Test group. That same user ID is used in testing the
next parts of this exercise.
_ 1. In IBM MQ Explorer, grant the group Security Test Connect and Inquire privileges for
the integration node queue manager IIBQM.
_ a. Under the Queue Managers folder, right-click IIBQM and then click Object Authorities
> Manage Queue Manager Authority Records. The Manage Authority Records window
is displayed.
jl IIBQM - Manage Authority Records
Groups user;
Name Alternate user authority Change Connect Delete Display Inquire Set
|j|mqbfcs§WS200TCS ■V V1 V
(¡E) * ✓ V V ✓ ✓ *•
mqrn(ô)W520Q8R2!i64
b. Review the existing groups and users by clicking the Groups tab and then the Users tab.
The only two groups that you see are mqm and mqbrkrs.
The only user that you see is iibadmin.
c. On the Groups tab, click New (at the bottom of the window). The New Authorities dialog
box is displayed.
d. For Entity name, type: Security_Test
Student Exercises
e. Under the MQI authorities options, click Connect and Inquire.

f. Click OK, and then click OK again on the result dialog box.
The Security_Test group is displayed in the Groups list with Connect and Inquire
authority.
g. Close the Manage Authority Records window.
Student Exercises
Part 2: Test the default unsecured environment

In this part of the exercise, you verify that permissions you configured in Part 1 of this exercise are
correct and that the No_Auth_iD user can successfully connect to the IIBNODE_WITHQM integration
node.
_ 1. So that you can run as another user without having to log off and back on, use the Run as
different user option in Windows and start the Integration API Exerciser.
__ a. In Windows Explorer, browse to the C:\Program
Files\IBM\IIB\10.0.0.0\server\sample\IntegrationAPI directory.
b. While holding down the Shift key, right-click the StartlntegrationAPIExercise.bat file and
then click Run as different user.
Name
5/18/2015 7:07 AM
IntegrationAPISamples.jar U
3/16/2015 9:44 PM
5tartBrokerInfo.bat 5tartDeployBAR.bat
3/16/2015 9:44 PM
3/16/2015 9:44 PM
Date modified
lapi
__ c. A login window opens and you are prompted to enter the user ID and password.
For the user ID, type: No_Auth_iD
For the password, type: webisphere
After a few moments, the Integration API Exerciser starts.
2. Adjust the timeout values for the Integration API Exerciser.
__ a. Click File > Set Timeout Characteristics.
__ b. Modify the timeout values as follows:
- Set Maximum wait time for BAR deployment to 60
- Set Maximum wait time for integration server creation to 60
- Set Maximum wait time for other requests to 2 0
Set Timeout Characteristics... IZ
Wait for the integration node to fully complete requests before returning W 3
Maximum wait time for BAR deployment (seconds) ||60
Maximum wait time for integration server creation (seconds) [&u
Maximum wait time for other requests (seconds) l20f

Maximum wait time for policy requests (seconds) |30
Submit ] Cancel

Student Exercises
__c. Click Submit.

3. The next steps assume that the IIBNODE_WITHQM integration node is running.
If the integration node IIBNODE_WITHQM is not running, start it now.
4. The Integration API Exerciser is running under No_Auth_iD and gets all permissions from the
settings for that user and its group, which is security_Test.
Connect the Integration API Exerciser to the integration node.
__a. Right-click Right-click to connection and then click Connect to Remote Integration
node
__b. Specify the connection values.
• For the Host Name, type: 127.0.0.1
• For the Port, type: 4416
• For the User Name, type: No_Auth_iD
• For the Password, type: webisphere
__c. Click Submit.

After a few seconds, the Integration API Exerciser connects to the integration node and
displays the integration node properties.
5. Using the Integration API Exerciser, verify that Administrative Security is turned off in
IIBNODE_WITHQM.
__a. With the IIBNODE_WITHQM integration node selected in the Integration API Exerciser
navigator (left pane), scroll to the bottom of the data window (right pane).
Student Exercises
b. Verify that isAdminSecurityEnabled() shows false, indicating that administrative security

is not enabled.
I® IBM Integration API (CMP) Enerci ser
File View Scripting
■fk> jHB[\IODE_WITHQM BrokerProxy Method Result

1. =, server 1 [InboundMessagesTotal, RepliesSentTotal^
getResourceTypeStatisticsPropertyNames("SOAPInput") Inbc
I.. 'p Administration Log getResourceTypeStatisticsPropertyNames("5ecurity") [TotalOperations, TotalSuccessfulOperations, Ti
; .. Administration Queue getResourceTypeStatisticsPropertyNames("5ockets") [TotalSockets, TotalMessages, TotalData5ent_K
+ -{¿p Configurable Services getResourceTypeStatisticsPropertyNames("TCPIPClientNo... [OpenConnections, ClosedConnections,
Messag
getResourceType5tatisticsPropertyNames("T CPIPServerN,.. [OpenConnectionSj ClosedConnectionSj
Messag
getSecurityCachePropertyNamesO
SecurityCache/cacheSweepInterval 300
SecurityCache/cacheTimeout 60
SecurityCache/uuid SecurityCache
getShortDescriptionO
getTimeOfLastCompletionCodeO Oct 14, 2015 8:46:22 AM

getTimeOfLastUpdate() Oct 14, 2015 8:46:22 AM
getTypeO Broker
getUUIDO 395c52f4-9fbd-47f9-90f4-b58ad91c4072
hasBeenPopulatedByBrokerQ true
1. _ _
1 ------------------------------- !------------ - ----------------------------------------------------
1 : AdminSecurityEnabledQ false
||j|''u ...... . i'-1
When the Integration API Exerciser is connected to the integration node, information about the
integration node is displayed under the integration node in the navigation pane.
The display of the integration server server! in the Integration API Exerciser implies that
some level of access is granted to the user. In this case, the No_Auth_iD user has “read”
access to the integration node.
_ 6. Attempt to deploy a BAR as the No_Auth_iD user.
_ a. Click the server! integration server in the Integration API Exerciser navigator.
_ b. Right-click serveii and then click Deploy BAR from the menu.
r / Note -------------------------------------------------------------------------------------------- ^
Be sure to select an entity before right-clicking it in the IBM Integration API Exerciser.
V ______________________________________________________________________________ V
_ c. Browse to the C: \iabfiies\Lab06-QSec\resources directory, select

Admin_Security_Testl .bar, and then click Open.

Student Exercises
The request succeeds, as indicated in the status log in the bottom pane of the IBM
Integration API Exerciser.
------------------------------- 3
D e p I o y R e s u 11. g e tD e p I o y Sta rtTi rn e ( ) = Oct 14, 2015 10:06:32 AM
DeployResultgetDeployStopTimeQ = Oct 14, 2015 10:06:45 AM (12s)
DeployResult.getDeployResponsesO : BIP2871I: The request made by user 'SYSTEM[Default]' to 'deploy'
'C:\labfiles\Lab06-QSec\resources\Admin_Secunty_Testl.bar' of type 'BAR' on parent'serverl' of type 'ExecutlonGroup'
'COMPLETE',
' SUCCESS: The integration node completed the request.
<—- iapi.exerciser. ClassTesterForExecutionGroupProxy. testDeployBAR
H ______________________________________________________________________________________________ 1 -
►l~
7. Determine whether this user can stop a message flow.

__ a. Fully expand the server! integration server in the navigator.
b. Right-click Admin_securityi_MsgFiow. cmf and click Stop from the menu.
c. Verify that the message flow stopped by selecting the message flow and checking the
runMode status, which should now be set to stopped.
1 & IBM Integration API (CMP) EHercisi -r n
File View Scripting
ft IIBNODE_WITHQM E serverl MessageFlowProxy Method Result

traceLevel none
j A- HI Admin_5ecurity 1 J'lsgFlow, additionallnstances 0
cmf startMode Maintained
; .F Administration Log
! .IJ Administration Queue coordinated! ransaction no
É-& Configurable Services commitlnterval 0
version
i-L-i r- --- :L... «—
1 runMode [stopped
k ............. y IQI3G
getCommitCountO 1
getCommitlntervalQ 0
getConf IguratlonObjectT ype() <Message Flow>
getConfigurationObjectTypeOfParentO Execution Group >
getCoordinatedT ransactlonQ false
modifyTime 2009-06-18 16:36:40,000 -0700
deployTime 2015-10-14 10:06:32.925 -0700
Q5ec\resources\Admin_5ecurity_Testl,bar
_ 8. Restart the flow by right-clicking Admin_Securityi_MsgFiow.cmf and clicking Start from

the menu.
_ 9. Verify that the flow is started by reviewing the status log. The runMode status should now
be set to running.
_ 10. Disconnect the Integration API Exerciser from the integration node by right-clicking
IIBNODE_WITHQM in the navigation pane and clicking Disconnect.
This step completes the testing in the unsecured environment. You saw that, given a minimum set of
authorizations, the No Auth iD has access to the integration node.
Do not exit from the IBM Integration API Exerciser. You use it again in the next part of the exercise.
Student Exercises
Part 3: Activate administration security and test the secured

environment
In this part of the lab, IBM Integration Bus security is activated, and the same non-privileged user ID is
used to demonstrate that the user cannot use any functions in the IBM Integration Bus environment.
_ 1. Activate integration node administration security.
_ a. Start an IBM Integration Console session as the administrator.
_ b. Stop the integration node so that you can make the necessary configuration change.
Type:
_ c. View the status of administration security and the current authorization mode. Type:
mqsireportauthmode IIBNODE_WITHQM

BIP8930I: Integration node name 'IIBNODE_WITHQM'
Authorization mode = 'mq'
As expected the administration security is returned as inactive. Also, this integration
node was created with a default queue manager, so default authorization mode is mq.
_ d. Activate administration security on IIBNODE_WITHQM. Type:
mqsichangeauthmode IIBNODE_WITHQM -s active -m mq
_ e. Restart the integration node. Type:

_ 2. When you activate administration security, the Integration web interface requires a user
name and password to log in.
_ a. Enable the Integration web interface for the administration user iibadmin. In the
mqsiwebuseradmin IIBNODE_WITHQM -c -u iibadmin -a weblsphere -r iibadmin
_ b. Log in to the Integration web interface with the administrator credentials.
For the user ID, type: iibadmin For the password, type: weblsphere
_ 3. You must also enable the Integration web interface for the No_Auth_ID so that this user can
connect to the integration nodes port.
mqsiwebuseradmin IIBNODE_WITHQM -c -u No_Auth_ID -a weblsphere -r No_Auth_ID

Student Exercises
4. Verify that the authorization queues exist on the queue manager.

_ a. In IBM MQ Explorer, click Queues under the IIBQM queue manager to display the
Queues content view.
_ b. In the Queues content view, click the Show System Object icon to display the SYSTEM
queues.
_ c. Confirm that the following authorization queues exist:
• SYSTEM.BROKER.AUTH (the authorization queue for the integration node)
• SYSTEM.BROKER.AUTH.serverl (the authorization queue for integration server)
0| MQ Explorer - Content £3
Queues
i Queue name Queue type Open Input count I Open output count
H SYSTEM, BROKER, AGGR. REQUEST Local 0 0
IM) SYSTEM.BROKER.AGGR.TIMEOUT Local 0 0
l_l cwrTrM on/M/cn A.--vn i 1__ 1 n n
HI SYSTEM. BROKER.AUTH
U SYSTEM. BROKER, AUTH, server 1
Local
Allas
0 o
r
i
4J i Ï 5 1 tn, BKUK.EK, LU, mUULL Humei
l
5. The SYSTEM.BROKER.AUTH queue controls authorization for the integration. Give the
group Securityjrest “Inquire” authority on the queue so that member of that group can
view the integration node properties.
_ a. In the IBM MQ Explorer, right-click the SYSTEM.BROKER.AUTH queue and then click
Object Authorities > Manage Authority Records from the menu.
_ b. Expand Specific Profiles and select SYSTEM.BROKER.AUTH.
Securityjrest is not displayed in the profiles. It does not have permissions on the
SYSTEM.BROKER.AUTH queue. The group must be defined to the queue and it must have
Read (“inquire”) authority.
_ d. For the Entity name, type: Securityjrest
_ e. Under the MQI authorities options, click Inquire.
_ f. Click OK, and then click OK again on the result window.
Student Exercises
_ g. Click Close to close the Manage Authority Records window.

6. In the IBM Integration API Exerciser, connect to IIBNODE_WITHQM.
With the security changes, the queue and integration server shows in the navigation pane.
You can see the integration server server! but it has a lock icon next to it. You cannot see the
integration server properties or the message flow that is running on the server. Granting
authority to the integration node did not grant authority to the integration servers contained
within it.
7. Click the server! integration server. You should see the BIP2852 error message in the Result
field that indicates the user is not authorized.
To list the contents of an integration server, the user ID must have Read (“inquire”) access to
the integration server.
<6^ IBM Integration API (CMP) Exerciser
File View Scripting
ExecutionGroupProxy Method Result

serverl getConf igurationObjectT ype() <Execution Group>
39 getConfigurationObjectTypeOfParentQ <Broker>
Configurable Services [1] ¡3IP2852E: The user 'No_Auth_ID' is not authorized to perforin the requested operation View' |
get Nam ef)

getTimeOfLastCompletionCode() Oct 14, 2015 11:19:46 AM
getTimeOfLastUpdateQ Oct 14, 2015 11:19:46 AM
getTypeO ExecutionGroup
getUUIDQ
4930952e-6d74-4604-8165-d 1 da806cf cd5
ha s 3 e e n
P o p u la t ed B y B r o he r ( ) hasBeenRestrictedByBroker()

_ b. Expand Specific Profiles and then click SYSTEM.BROKER.AUTH.serverl.
_ d. Enter Securityjrest as the Entity name.
_ e. Under the MQI authorities options, select Inquire.
_ f. Click OK, and then click OK again on the result dialog box.
_ g. Click Close to close the Manage Authority Records dialog box.
8. In the Integration API Exerciser, right-click the server! integration server and then click
Refresh from the menu.
You now see the properties of the server! integration server. You can also see the message
flow that is running on the integration server.
9. Try to deploy a BAR file to serverl from the Integration API Exerciser.
_ a. Right-click the serverl integration server and click Deploy BAR from the menu.
_ b. Go to the c: \iabfiies\Lab04-QSec\resources directory and then select
Admin_Security_Test2.bar.

Student Exercises
_ c. The deployment fails. The message in the Integration API Exerciser indicates that the
user does not have authorization and must have “write” permissions on the integration
server.
The ability to deploy requires Write (Put) permission on the integration server.
10. Add Write (Put) permissions for the Securityjrest group on the integration server
SYSTEM.BROKER.AUTH.serverl queue.
_ a. Expand Specific Profiles and then select SYSTEM.BROKER.AUTH.serverl.
_ b. Click the Groups tab, and then select the Security_Test row in the table.
_ c. Click Edit.
_ d. Under the MQI authorities options, select Put.
The Security Test group now has both Inquire (Read) and Put (Write) permissions.
_ e. Click OK, and then click OK again on the result dialog box.
_ f. Close the Manage Authority Records dialog box.
11. Try to deploy the Admin_security_Test2 .bar in the Integration API Exerciser.
Verify that the flow was successfully deployed by reviewing the messages in the Integration
API Exerciser status log. You should also see the message flow in the Integration API
Exerciser navigator pane.
Student Exercises
ft IBM Integration API (CMP) Exerciser

File View Scripting
=¡> PBNODE_WITHQM1 ExecutionGroupProxy Method

serverl getAdvancedPropertiesO
; f -mn Admin_5ecurityl_MsgFlôw.cmf ; i-— processld 5464
HHU Adrnin_5ecurity2_MsgFlow.cmf injectionMode Disabled
; . r Homimstration Log soapNodesUseEmbeddedListener true
; . U Administration Queue traceLevel none
El- Configurable Services threadLocalProxyNameManagers false
consoleMode off
httpNodesUseEmbeddedListener false
activellserExitList
inactivellserExitList
traceNodeLevel on
userTraceLevel none
getApplications(null)
getBasicPropertiesO
label serverl
runMode running
uuid 493B952e-6d74-4684-8165-dl da806cfcd5
shortDesc
DeployResult.getCompletionCode() = success DeployResult.getDeployStartTimeQ = Oct 14, 2015 11:49:53 AM

DeployResult.getDeployStopTime() = Oct 14, 2015 11:50:10 AM (17s) DeployResult.getDeployResponses() :
BIP2871I: The request made by user 'No_Auth_IC C:\labfiles\Lab06-QSec\resources\Admin_Security_Test2.bar'
of type 'BAR' on parent 'serverl' of type 'E
SUCCESS: The integration node completed the request.
12. Stop the Admin_Security2_MsgFiow. cmf message flow from the Integration API Exerciser.
Right-click Adminj3ecurity2_MsgFiow.cmf in the Integration API Exerciser and then click Stop.
The stop command fails because the security_Test group does not have Set (Run) authority
on the integration server, which is required for a “stop” or “start” command.
13. In IBM MQ Explorer, modify the permissions for the Security_Test group to include Set (Run)
permissions on the SYSTEM.BROKER.AUTH.serverl queue.
Review the substeps in step 10 if you need help. This time, select Set authority in addition to
the authorities that are already set.
14. In the Integration API Exerciser, try to stop the message flow now that the permissions are
modified.

Student Exercises
15. To verify that the Admin_Security2_MsgFiow.cmf message flow stopped, scroll to the last entry in
the MessageFlowProxy Method list. The last entry in the Result column is the isRunning
method with a result of false, which indicates that the flow is stopped.
If, IBM Integration API (CMP) Exerciser
File View Scripting

#i> IIBNOOE_WITHQM - ser veri traceLevel none
! hü Admin_Securityl_MsgFlow,cmf i additionallnstances 0
nÌl|Admin_5ecurity2_MsgFlow,cmf startMode Maintained
j-ït1' Administration Log j-U coordinatedTransaction no
Administration Queue 0-Q, commitlnterval 0
Configurable Services version
I.L.I
runMode stopped
isRunnina false
getCommitCount() 1
getCommitInterval()
0
getConfigurationObjectT ype() <Message Flows
getConfigurationObjectTypeOfParent() «Execution Groups
getCoordinatedT ransaction() false
modifyTime 2009-06-18 15:58:08,000 -0700
deployTime 2015-10-14 11:49:53,819-0700
QSec\resources\Admin_Security_Test2.bar
16. Attempt to create an integration server in the Integration API Exerciser.

__ a. Right-click IIBNODE_WITHQM and then click Create integration server from the
menu.
__ b. Enter Admin Security for the New integration server name and then click Submit.
The requested action fails because the Security_Test group does not have Write (Put)
permission on the integration node authorization queue.
17. In IBM MQ Explorer, add Write (Put) permissions to the SYSTEM.BROKER.AUTH queue
for Security_Test.
When you complete this step, the security_Test group should have both Read (Inquire) and
Write (Put) permissions.
18. Attempt to add the Admin_Security integration server to IIBNODE_WITHQM again. Refer to
step 16 if necessary.
This time, the command is successful.
19. Attempt to deploy the Admin_Security_Test2 .bar file that is in the C:\iabfiies\Lab06-
QSec\resources directory to the Admin_Security integration server.
The deployment fails because the group securityjrest does not have sufficient authority to
deploy to the new integration server.
The process of creating the integration server automatically creates the queue
SYSTEM.BROKER.AUTH.Admin_Security, but it does not automatically create the required
authorities.
Student Exercises
§ MQ Explorer - Content £3
Queues
Queue name Queue type | Open Input count | Open output count
y SYSTEM.BROKER, Local
AGGR,REQUEST Bl Local
SYSTEM.BROKER,AGGR,TIMEOUT
y Local
SYSTEM.BROKER,AGGR,UNKNOW
yNSYSTEM.BROKER,AUTH Local
Ì I SYSTEM. BROKER, AUTH, IHIM
H Admin_Secunty
SYSTEM. BROKER, AUTH, Allas
server 1 [%J Model
SYSTEM.BROKER,CD.MODEL
The deployment operation requires that you add Put (Write) authority on the
SYSTEM.BROKER.AUTH.Admin_Security queue for the Security Test group.
Exercise clean up
_ 1. In the IBM Integration API Exerciser, disconnect from the integration node by right-clicking
IIBNODE_WITHQM and then clicking Disconnect.
_ 3. From the IBM Integration web interface:
_ a. Delete the integration server Admin_Security.
_ b. Stop all message flow on the serverl integration server.
_ c. Delete all flows from the serverl integration server.
_ 4. Disable administrative security on IIBNODE_WITHQM from a command in the IBM
Integration Console.
_ a. Stop the integration node and verify that it is stopped. Type:
_ b. Disable administration security. Type:

mqsichangeauthmode IIBNODE_WITHQM -s inactive -m mq
_ c. Restart the integration node. Type:

End of exercise

Student Exercises

In the first part of this exercise, you set up user and group authorities for a non-privileged Windows
user (No Auth ID).
In the second part of the exercise, you added basic authorizations for a non-administrative user.
In the third part of the exercise, you activated Integration Bus administration security. The same non-
privileged user ID was used to demonstrate that the user cannot use any functions in the Integration
Bus environment until authorization was configured on the IBM MQ authorization queues.
• Use the IBM Integration Bus security queues on IBM MQ to assign permissions for integration
nodes, integration servers, and message flows
Student Exercises

podrá reproducir o
Student Exercises
Exercise 7. Implementing web services and web

services security

In this exercise, you configure the integration node runtime environment to
support web services. You use the supplied tools to set up a web service that
can accept information from, or deliver it to, a transport with secure HTTP
(HTTPS).

• Implement a web service message flow application that uses HTTPS for
secure transport
Introduction
A web service is a callable program that is at a web location, and can create
unlimited extensions to the classic remote procedure call (RPC) paradigm. As
standards stabilize, web services of all types are becoming common.
In the first part of this exercise, you configure an integration node HTTP
listener.
In the second part of this exercise, you review the web services messages flow
and build and deploy a BAR file.
In the third part of this exercise, you build the BAR file and then use the
Integration Toolkit BAR file editor to modify the configurable properties.
In the fourth part of this exercise, you test the web service.
In the fifth part of this exercise, you implement SSL for the web service
application.
Required materials
• The IIBNODE_WITHQM integration node and the IIBQM queue manager
Student Exercises
• Lab files in the C:\iabfiies\Lab07-webSvc directory

podrá reproducir o
Student Exercises
Exercise set up
_ 1. If it is not already open, open IBM Integration Toolkit.
_ 2. To prevent any conflicts with any existing message flow applications, switch to a new
workspace that is named C:\workspace\webSvc.
_ b. For the Workspace, type: C:\workspace\webSvc
_ c. Click OK. After a brief pause, the IBM Integration Toolkit restarts in the new workspace.
_ 3. Import an existing project that contains the message flows for this exercise.
_ a. From the menu bar, click File > Import. The Import selection dialog box is displayed.
_ b. Expand General.
_ c. Select Existing Projects into Workspace, and then click Next.
_ d. To the right of Select root directory, click Browse, browse to the
C:\labfiles\Lab07-WebSvc\resources\WebSvc folder, and then click OK.
_ e. Ensure that websvc is selected in the Projects window.

_ f. Select the Copy projects into workspace option.
g. Click Finish. The WebSvc project is imported into the Independent Resources folder in the
Application Development view.
Student Exercises
_ 4. In the IBM Integration Toolkit Integration Nodes view, verify that the integration node
IIBNODE_WITHQM is running.
_ 5. Create the local queues (PINGJN, PING_OUT, and FAILURE) that are required for this
exercise on the IIBQM queue manager.
_ a. In an IBM Integration Console, type the following command:
runmqsc IIBQM < C:\labfiles\Lab07-WebSvc\Q_Defs.mqsc
_ b. Open IBM MQ Explorer and verify that the local queues were created on the IIBQM
queue manager.
Part 1: Configure the integration node HTTP listener

In this part of the exercise, you configure the integration node HTTP listener.
The integration node HTTP listener requires that you use an integration node that is configured with a
default queue manager. In this exercise, you use the integration node IIBNODE_WITHQM that you
created in Exercise 2. It is defined to use the IIBQM queue manager as its default queue manager.
_ 1. In this exercise, you use port 7085 for the integration node HTTP listener. Verify that port
7085 is not already in use by another application.
_ a. From a Windows command prompt, type the following command to get the network
information and save it to a text file. Type:
_ b. Open the text file in Notepad and examine the list of assigned and active port numbers.
Verify that port number 7085 is not already in use.
_ 2. Configure the integration node HTTP listener to use port 7085.
_ a. Check the current port for the HTTP listener on the integration node. In the IBM
The results should show that the current port is 7800.

_ b. Change the port for the integration node listener to 7085. In the IBM Integration
Console, type:
mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPConnector -n
port -v 7085
_ c. Verify that the HTTPConnector port is now 7085. In the IBM Integration Console, type:
The results should show that the current port is now 7085.
_ 3. For the changes to take effect, the integration node must be stopped and restarted after
entering the mqsichangeproperties command.
_ a. Stop the integration node. In the Integration Console, type:

Student Exercises
After a few moments, a confirmation message is displayed, b.
podrá reproducir o Restart the integration node. In the Integration Console, type:
After
Note a few moments, a confirmation message is displayed.
'A
The mqsistop command waits for a signal that the integration node was shut down successfully before
it displays the confirmation message.
The mqsistart command returns a confirmation message when you enter start commands, but it does
not wait for the integration node and its components to signal that they are ready. As a result, if an error
occurs during start, it is possible for the mqsistart confirmation message to show even though the
components did not start.
Always check the status of the integration node and its components to ensure that they started
correctly.
Part 2: Review the message flows

_ 1. In the IBM Integration Toolkit, review the CallWebSvc message flow.
_ a. In the Application Development view, expand Independent Resources > WebSvc >
Flows.
_ b. Double-click CailWebSvc.msgflow to open it in the Message Flow editor.
2. Notice the names of the MQInput node (PINGJN) and MQOutput nodes (FAILURE and
PING_OUT). The node names are the same as the queue names that are specified as
properties and should match the queues that you created in the Exercise set up.
If you want to confirm these queue names, right-click those nodes and click Properties.
3. Click the HTTP Request node to view its properties in the Properties view.
In the Basic properties view, view the entry for Web service URL. The format of the URL is:
http://server:inode_listener_port/service
Student Exercises
The value of service must agree with a similar value that is specified in the properties of the
HTTPInput node in the target web service message flow.
_ Properties £3 . Problems Outline ^ Tasks 0 Deployment Log
** HTTP Request Node Properties - HTTP Request

Settings for working with the HTTPRequest node,
Description
Basic Web service URL* http ://localh ost : 7085/httpprotocol
HTTP Settings e,g, http'.jlserv&lpahhjtojservke

S5L
Request timeout (sec)* 1120
Response Message Parsing
Do not change any of the properties, but do remember them.

4. Open the HTTPProtocol message flow in the Message Flow editor by double-clicking
HTTPProtocol.msgflow in the Application Development view. It should contain three nodes
as shown in the following figure.
Click the HTTPInput (7085) node to see its properties.
The Path suffix for URL value on the Basic tab exactly matches the URL on the previous flow
HTTP Reply
■■ —# >-
HTTPInput (7085) Add_Time_5tamp
(the HTTPRequest node in that flow is starting this flow by using that URL).
(T Problems Outline •£* Tasks Deployment Log
HTTP Input Node Properties - HTTPInput (7085)

Settings for working with the HTTPInput node.
Description
Basic Path suffix for URL* | http://localhost:7085/httpprotocol
Advanced e,g: ¡path/to/'service, where the full uri is

Input Message Parsing http://se.fver:78DD/path/to/service Use HTTPS I“
Parser Options
_ 6. Close both of the message flows.

podrá reproducir o
Student Exercises

In this part of the exercise, you create and deploy a BAR file that contains the web services message
flows.
_ 1. In the IBM Integration Toolkit, create a BAR file that is called Webservice .bar.
_ a. From the menu bar, click File > New > BAR file.
_ b. For Container, select: WebSvc.
_ c. For Folder, use the <defauit> value.
_ d. For the Name, type: Webservice.bar
New BAR file

_ e. Click Finish. The new BAR file opens in the BAR File editor.
_ f. Select the Flows check box to add both message flows.
_ g. Under the Build Options, select Compile and in-line resources.
Cl *WebService.bar H
Prepare
Select deployable resources to include in the BAR
B O & Independent resources 3 □&,!
Deployable Resources Build Options

Build and Save..
0 Compile and in-line resources ;
Select a library to package all of its contained resources, or select independent resources to package for deployment. These resources will
be visible to other deployed resources in the same integration server. CJ r\CIMUVC LUI ILC.| 115 Ul U 1C Cl u live uefore b
0 Override configurable property values O
Add workspace project source files

O Applications, shared libraries, services, and REST APIs © Message flows, static libraries and other message flow dependencies Text filter: (type
filter text Working set filter: j <all resources>
E5QL*
□ ¡jeî CallWebSvc.esql - /WebSvc/CallWebSvc.esql
■""^¿^^P-otocoI.esql - /Web5vc/HTTPProtocol.esql
3 0 Hi7 Flows
M ■ bSvc.msgflow - /WebSvc/CallWebSvc.msgflow
0 ÜIl HTTPProtocol.msgflow -
/WebSvc/HTTPProtocol.msgflow - □ ÿ XSLT*
1 .... 0 [Ï] WebSvcTestMsg.xml-/Web5vc/Web5vcTestMsg.xml
_ h. Click Build and Save.

_ i. Click OK on the success message. The message flows are added to the BAR file.
Student Exercises
2. You can view and modify the message flow configurable properties, such as the queue
names, by editing the BAR on the BAR File editor Manage tab.
_ a. In the BAR File editor, click the Manage tab (at the bottom of the BAR File editor
window).
_ b. Fully expand the two compiled message flows (.cmf files).
■ 0 WebServIce.bar £3
Manage
gf s£] -^1 Q Filter by: | <Type filter text>
Name Type I Modified Size
El HHU Call WebSvc. cmf Compiled messa... Oct 15, 2015 7:27:26 AM 23577
El UHI CallWebSvc
^ Add_MQMD
l [g I] FAILURE
HTTP Request
Jjä PING_IN
ILÿli PING_OUT
Ö UHI HTTPProtocol.cmF Compiled messa... Oct 15j 2015 7:27:25 AM 5294
B HHB HTTPProtocol
Add Time Stamp
B-Sf. HTTPInput (7085)
HTTP Reply
jd __________________________________________________________________________________________________________ \
Jl
Prepar Manage ser Log Service Log
c. Click the HTTPRequest and the HTTPInput (7085) nodes in the tree to view their
configurable properties.

podrá reproducir o
Student Exercises
The properties for the HTTPRequest node are shown here.

Properties tl Problems Outline Tasks ¡3 Deployment Log
HTTP Request
I(T) Configure properties of selected resource.

Configure
built
Workload Management Accept compressed responses by default r
Allowed SSL ciphers 1---------------------
Enable HTTP/1.1 keep-alive Y
Enable SSL certificate hostname checking
Enable certificate revocation list checking
r
r
HTTP version U
HTTP(S) proxy location
1---------------------
Protocol SSL
Request timeout (sec) 120

SSL client authentication key alias 1---------------------
Security profile
Use compression none

Validate ¡None
Web service URL 1 http : //localhost : 7085/httpprotocol

e.g. http:f/serverfeathftofeervice
Before you deploy the BAR file, you can change the URL for the target web service, which
overrides the value that was used for development testing. Similarly, a developer can test
locally by simulating a remote web service.
To start the actual target web service, no changes need to be made to the calling
message flow. You need only to specify a different URL by using the BAR File editor
Manage tab and then redeploy the BAR file.
In this exercise, you use the provided values for the connections. Do not change the
configurable properties for message flow nodes.
3. For this exercise, you allow for more than one instance of the flow to run.
__ a. While still on the BAR File editor Manage tab, click HTTPProtocoi. cmf to display the
message flow configurable properties.
__ b. In the Properties view, click Workload Management to display the Workload
Management configurable properties.
Student Exercises
c. Change the Additional Instances property value to 2.

Í _] Properties S3 til Problems a- Outline | Tasks H Deployment Log
HT1 PI’rotor nl.rmf

Workload Management Policy

Details
Notification Threshold (Messages per second) [| 0 Maximum Rate (Messages per second) |
0 Processing Timeout (Second) | 0 Processing Action None
Additional Instances | 2|
Start additional instances when flow starts I- Start Mode | Maintained
_ d. Similarly, change the Additional Instances property for the Caiiwebsvc.cmf message
flow to 2.
_ e. Save the BAR file updates by typing Ctrl+S, or by clicking File > Save from the menu
bar.
_ f. Close the BAR file editor.
4. Deploy the BAR to the server! integration server on IIBNODE_WITHQM.
_ a. In the Application Development view, right-click the Webservice.bar file and then
click Deploy from the menu.
I Application Development £3 Patterns Explorer
& -
B BARS
; tr ----------- -- ---------- - -------- ---
I-1 !& Ind.
Ö-fif Web5vc
b. In the Deploy window, click server! (under IIBNODE_WITHQM), and then click Finish.

podrá reproducir o
Student Exercises
The message flows should show under the serverl integration server in the Integration
Nodes view.
c. Verify that the deployment was successful by reviewing the Deployment Log and the
□■•filg Integration Nodes
[+1 TTRMnnF MnnM
□■■■ <3............... IIBNODE_WITHQM
serverl
; CallWebSvc P
HTTPProtocol
IIBN0DE_WITHQM2 É $
TESTNODEJibadmin
5. Deploying the message flows should activate the HTTP port 7085. Verify the port 7085 is in a
LISTENING state.
_ a. From a Windows command prompt, type:
_ b. Examine this list in Notepad, the listener that uses port 7085 should now be displayed as
LISTENING.
jf] network.tut - Notepad
File Edit Format View Help
Active connections
Proto Local Address Foreign Address State
TCP 0.0.0.0:88 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:464 0.0.0.0:0 LISTENING
TCP 0.0.0.0:523 0.0.0.0:0 LISTENING
TCP 0.0.0.0:593 0.0.0.0:0 LISTENING
TCP 0.0.0.0:636 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2414 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3268 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3269 0.0.0.0:0 LISTENING
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4414 0.0.0.0:0 LISTENING
TCP 0.0.0.0:4416 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5722 0.0.0.0:0 LISTENING
TCP 0.0.0.0:5800 0.0.0.0:0 LISTENING
TfD n n n n-sann n n n n ■ n 1 T RT IT MT MC
LISTENING
i Lr U . ' J . U. U . 5U0Ï 0.0.0.0:0 LI u i tim nu
TCP 0.0.0.0:47001 LISTENING
u. u. u. u . u
0.0. 0.0:0
The listener for port 7085 is now active because you deployed a web service message flow that
contains an HTTPInput node. The integration node compared the HTTP port number (7085) with
the port that is assigned to the integration node. Because they matched, the integration node
listener became active.
Student Exercises
r / Note ------------------------------------------------------------------------------------------- ^
The mqsicreatebroker and mqsichangebroker commands can also be used to assign or change the
integration node listener port number by using the -P HTTPPort parameter. Be sure to use an
uppercase “P” when entering this command as lowercase “p” is also a valid parameter.
Later in this exercise, you learn howto configure SSL, which uses a different port.
v ______________________________________________________________________________ _y
Part 4: Test the web service application

In this part of the exercise, you use the Integration Toolkit Unit Test Client and a pre-defined test to
test the web service.
_ 1. Enable the Integration Toolkit Unit Test Client.
_ a. In the Integration Toolkit, click Window > Preferences.
_ b. Expand Integration Development.
_ c. Click Unit Test Client.
d. Select Enable menus for test client and then click OK.

Student Exercises
2. In the Application Development view of the IBM Integration Toolkit, expand Independent
Resources > WebSvc > Flow Tests.
3. Double-click the file TestEnq.mbtest to open it in the Test Client.
4. Under Detailed Properties, change the properties in the Test Client as follows:
_ a. Change the Queue manager to match your integration node queue manager name
(IIBQM).
_ b. Change the Port to 0 (this port is not the HTTP port that you set earlier in the exercise by
Using the mqsichangeproperties command).
H *TestEnq S3 □
Events
Message Flow Test Events ► General Properties

Detailed Properties
....... I . __________ II _ L
■lljp ¿9 SIB iö
□ Enqueue Port: 0|
mq. Message sent to MQ Queue "PINGJN" Server channel: SYSTEM.BKR,CONFIG
Queue manager: | IIBQM
eue ; irii ni
“ Message — ►Header
Body : I Edit
as text
U
l~l Show in hexadecimal viewer (Read Only)
<InMsg> ~7\
<text>Hello Again</text>
</InMsg>
bJ
Import Source... Send Message
_ c. Type Ctrl+S to save the file.

_ 5. In the Unit Test Client, click Send Message to put a message on the PINGJN queue.
The message flow starts, calls the webservice flow, obtains the response, adds a message
descriptor, and delivers it to the output queue called PING_OUT.
/ Note -------------------------------------------------------------------------------------------- v
The only result that you see is Message sent to Queue. You do not see the response message until
you complete the next step.
V ______________________________________________________________________________ J
_ 6. Use the IBM MQ Explorer to see whether the message is on the output queue PING_OUT.
You can right-click the queue and click Browse Messages to view the message on the
queue.
Student Exercises
The message data should contain the following text:

<OutMsg>
<NewText>The date/time is:</NewText>
<DateTime>date_and._timestarrp when the flow was run</DateTime>
</OutMsg>
_ 7. Close the Unit Test Client in the IBM Integration Toolkit. Do not save the changes when
prompted.
Part 5: Implement SSL for the web service application

It is possible that a developer tested in an unsecured environment so that when the application is
moved to the production environment you must take steps to secure it. HTTP can be run over SSL to
ensure that the data is not altered while it is in transit.
Imagine, a scenario where a flow that calls a web service is being allowed to flow across non-SSL
HTTP connections. However, other users might start that same web service by using an HTML form
in a browser. In that case, you want to allow only trusted access. There is no requirement to change
the message flows. You set up a new archive file to make necessary changes to one message flow to
allow this scenario to work.
First, you must set up SSL for use. In a real-world environment, it is likely that you would obtain
certificates from an external certificate authority. However, for the purposes of testing or internal only
use, the keytool utility is included with the IBM Integration Bus. With the keytool utility, you can
generate certificate keys to use with SSL for testing. You use it for this exercise.
_ 1. Open an Integration Console as an Administrator user, if one is not already open.
_ 2. Change directories to the keytool utility directory:
cd C:\Program F±les\lBM\WebSphere MQ\j ava\jre\bin
_ 3. Run the keytool utility without any options to display a list of all the possible parameters:
keytool
Briefly review the parameters and options.

_ 4. Create a keystore.
_ a. Type the following command in the Integration Console:
keytool -genkey -keypass devkey -keyalg RSA -alias tomcat -keystore
dev.keystore -storepass devkey -validity 360 -keysize 2048

Student Exercises
__ b. You are asked a series of questions for the key generation process; respond to them as
shown here. You can use any name when prompted for first and last names.
What is your first and last name?
[Unknown]: Mary Smith
What is the name of your organizational unit?
[Unknown]: WM646
What is the name of your organization?
[Unknown]:
What is the name of your City or Locality?
[Unknown]:
What is the name of your State or Province?
[Unknown]:
What is the two-letter country code for this unit?
[Unknown]: US
Is CN=Mary Smith, OU=WM645, 0=Unknown, L=Unknown, ST=Unknown, C=US correct? (type
"yes" or "no")
[no] : yes
The keystore is created with the values that you specified. The keystore file is written to the
C:\Program Files\IBM\WebSphere MQ\java\jre\bin directory.
5. Use Windows Explorer to create a directory that is named C:\iabfiies\keystores.
6. Copy the dev.keystore file from the C:\Program Fi le s \ I BM\Web Sphere
M2\java\jre\bin directory to the C:\labfiles\keystores directory.
7. Make the integration node IIBNODE_WITHQM aware of the keystore file, and configure the
HTTPListener to use the SSL port. This port is not the default HTTP port that you used earlier.
Type the following commands in the order shown.
These commands are case-sensitive.
r
To reduce the amount of typing you must do, you can press the up arrow key on your keyboard in the
Integration Console to retrieve a previous command. You can then edit the portion of command that
changed, by using the left arrow, right arrow, Delete, and Backspace keys.
Press Enter to run the command after you finish editing it.
v
__ a. Enable SSL for the integration node:
mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPListener -n
enableSSLConnector -v true
__ b. Configure the integration node with the keystore information:
mqsichangeproperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -n
keystoreFile -v C:\labfiles\keystores\dev.keystore
Student Exercises
__ c. Set the keystore password in the integration node:

keystorePass -v devkey
__ d. Set the port for HTTP SSL connections:
port -v 7083
__ e. Configure the integration node with the truststore information:
truststoreFile -v C:\labfiles\keystores\dev.keystore
__ f. Configure the truststore password in the integration node:
truststorePass -v devkey
__ g. Disable client authentication in the integration node:
clientAuth -v false
8. Use the mqsireportproperties command to verify the configuration changes that you made:
mqsireportproperties IIBNODE_WITHQM -b httplistener -o HTTPSConnector -a
Verify the values that are reported for uuid, keystoreFile, keystorePass, truststoreFile,
truststorePass, clientAuth, and port.
uuid='HTTPSConnector'
clientAuth='false'
keystoreFile='C:\labfiles\keystores\dev.keystore'
keystorePass='********1
truststoreFile='C:\labfiles\keystores\dev.keystore'
truststorePass='********1 port='7083'
9. Restart the integration node from the Integration Console so that the configuration changes
take effect.
Type:
mqsistop IIBNODE_WITHQM mqsistart IIBNODEJWITHQM
10. You are now ready to deploy message flows that use SSL. The message flows must request
the correct SSL port to function correctly. For testing purposes in this exercise, you use only
one of the two message flows.
In the IBM Integration Toolkit, create a BAR file that is called ssiArchive.bar.
Add only the HTTPProtocol message flow to the BAR file; do not add the CallWebSvc
message flow.
__ a. Right-click the BARs folder in the Application Development view.

Student Exercises
__ b. Click New > BAR file.

__ c. For Container, select WebSvc.
__ d. Use the <default> value for Folder.
__ e. For Name, enter ssLArchive.bar
__ f. Click Finish. The new BAR file is opened in the BAR File editor.
__ g. Select the check box for HTTPProtocoi .msgf low (do not include the caiiwebsvc
message flow).
__ h. Click Build and Save. The message flow is added to the BAR file.
__ i. Click OK to the confirmation dialog box when the build completes.
11. Modify the message flow properties to use SSL.
__ a. In the Manage tab of the BAR File editor, expand HTTPProtocoi.msgflow.
__ b. Expand HTTPProtocoi.
__ c. Click the HTTPInput (7085) node. The node properties are displayed in the Properties
view.
__ d. Modify the Path suffix for URL to use port 7083 (SSL) instead of 7085.
__ e. Select the Use HTTPS check box.
[r *55LArchive,bar £3
Manage
EÉ1 *3 Hi @l Filter by: | <Type filter text>
Name Type Modified Size Path
fe^ql HTTPProtocoi.esql ESQL file Oct 15, 2015 9:41:05 AM 599
□ m HTTPProtocoi.msgflow Message flow Oct 15, 2015 9:41:05 AM 2527
E BHll HTTPProtocoi
^ Add_Time_Stamp
m HTTPInput (7G85)
ß HTTP Reply
JLl ________________________________________________________________________________________ I
il
Prepare Manage User Log Service Log
& —
Ö Properties £3 . Problems a— Outline ffl Deployment Log

5T
cu
VI
t
HTTPInput
Configure(7085)
(T) Configure properties of selected built resource.
Path suffix for URL http : //localhost :7083/htt pprotocol
s-. g.- fpetn/tofservice, mere me run uri ts nttp;f¡serven TSQQfpethftofservice
Decompress input message Fault r
|sOAP 1 . 1
format Security profile
Maximum client wait time (sec) r '

Use HTTPS I 180 F
Student Exercises
12. Change the number of instances to 5 to allow multiple copies of the flow to run to increase
message throughput.
__ a. In the Manage tab of the BAR File editor, select HTTPProtocoi .msgf low.
__ b. Select the Workload Management section on the Properties tab.
__ c. Change Additional Instances to 5.
Properties £3 _ Problems □!: Outline Deployment Log
HTTPProtocoi .msgflow
Workload Management p0|¡

Details
Notification Threshold (Messages per second) fo Maximum Rate
(Messages per second) 0 Processing Timeout (Second) 0 Processing
Action None
Additional Instances 15l
13. Save the changes by typing Ctrl+S or clicking File > Save.
14. Create an integration server that is named ssLWebServices on IIBNODE_WITHQM.
__ a. In the Integration Nodes view of the Integration Toolkit, right-click IIBNODE_WITHQM.
__ b. Click New Integration Server.
__ c. For the integration server name, type: ssLWebServices
__ d. Click OK.
15. Deploy the BAR file ssLArchive.bar to the SSLWebServices integration server.
Important
Do not deploy the ssLArchive.bar file to the same integration server where the non-SSL flow is
running (the default integration server).
16. Verify that deployment was successful by reviewing the Deployment Log.
17. Verify that a listener for port 7083 is now active by entering the netstat -an command from
the IBM Integration Console session.
18. Test the web service message flow.
__ a. In Windows Explorer, browse to the C:\labfiles\Lab07-webSvc\resources\WebSvc
folder.
__ b. Right-click the webSvcform.html file and then click Open with > Firefox.

Student Exercises
c. In the browser window, click Obtain Date/Time.

file:///C:/labfiles/Lab 10/resources/WebSvc/WebSvcform. html
^ - --
To obtain current date and time, click below
Obtain Date/Time
If you set up the keystore correctly, you get a security message about the certificate that is
being used. It might take a few moments before the browser responds.
This Connection is Untrusted

You have asked FireFox to connect securely to localhost:7083, but we can't confirm that your connection is secure.
Normallyj when you try to connect secured sites will present trusted identification to prove that you are going to the
right place. However, this site's identity can't be verified.
What Should I Do?

If you usually connect to this site without problems,, this error could mean that someone is trying to impersonate the
site., and you shouldn't continue.
G et rn e o ut of h e re! |
Tethnical Details
I Understand the Risks
If you understand what's going on, you can tell Firefox to start trusting this site's identification, Even if you trust the
site, this error could mean that someone is tampering with your connection.
Don't add an exception unless you know there's a good reason why this site doesn't use trusted identification.
| Add Exception... |
If you use Internet Explorer to open the websvcform.html file, your output results
are different because of the differences in the browsers.

J
d. Expand I Understand the Risks and then click Add Exception. The Add Security
Exception window opens.
Student Exercises
_ e. Click Confirm Security Exception. A confirmation window opens.

_ f. Click Resend on the confirmation window. You should receive the response from the
web service in the form of an XML file with the date and time that is similar to the example.
<OutMsg>
<NewText>The date/time is: </NewText>
<DateTime>2015-10-19 05:51:04.28613l</DateTime>
</OutMsg>
While it might not be obvious, the combination of the two flows used in this exercise approximates to a
“What time is it?’’ application. The “calling” flow can be altered to call different web services by
changing the URL value in the BAR file before deployment.
Exercise clean up
_ 1. In the IBM Integration Toolkit Integration Nodes view:
_ a. Right-click the SSLWebServices integration server and then click Delete > All flows
and resources.
_ b. Delete the SSLWebServices integration server.
_ c. Right-click the serverl integration server and then click Delete > All flows and
resources.
_ 2. Close any open windows and programs.
End of exercise

Student Exercises

As you saw, it is possible to change how a message flow that behaves as a web service can be
called in different ways. You also configured an integration node to use SSL and non-SSL HTTP
transports.
• Implement a web service message flow application that uses HTTPS for secure transport
Student Exercises

Student Exercises
Exercise 8. Using problem diagnosis tools

In this exercise, you enable and disable message flow Trace nodes, and use a
user trace and service trace to capture runtime information. You also configure
and activate an integration server JVM Debug Port.

Introduction
In this exercise, you use various problem determination tools to administer
message flows with trace nodes and administration tools to generate and
control tracing.
This exercise uses a flow that is similar to the message flow that is used in a
previous exercise but with the addition of a trace node.
In the first part of the exercise, you import a BAR file that contains a Trace
node into IBM Integration web interface. You examine the Trace node
properties and then deploy the BAR file to the IIBNODE_WITHQM integration
node.
In the second part of this exercise, you use the IBM MQ SupportPac RfhUtil to
put messages on the message flow input queue and test the message flow.
Student Exercises
In the third part of this exercise, you control Trace nodes and enable a user
trace and a service trace. A service trace provides more detailed tracing, and
generates a large amount of output.
In the fourth part of this exercise, you activate an integration server flow debug
port.
Requirements
• IBM Integration Bus V10 and IBM MQ Explorer V8
• The integration node IIBNODE_WITHQM and queue manager IIBQM that
were created in Exercise 2
• The lab exercise files in the c: \iabf iies\Lab08-Trc folder
• The IBM MQ SupportPac IH03 (RfhUtil) in the C:\Software\ih03 folder

Student Exercises
Exercise set up
Use the IBM MQ runmqsc command to define the queues that are required for this exercise.
_ 1. Start an IBM Integration Console session if one is not already running.
_ 2. Type following command:
runmqsc IIBQM < C:\labfiles\Lab08-Trc\resources\Q_Defs.txt
_ 3. Using IBM MQ Explorer, verify that the following local queues are defined on queue
manager IIBQM: CATCH, FAILURE, FALSE, IN, REPLY, and UNKNOWN.
Part 1: Examine and deploy the BAR file

In this part of the exercise, you deploy an existing BAR file by using the IBM Integration web interface
for the IIBNODE_WITHQM integration node. The BAR file contains a message flow that contains a
Trace node.
_ 1. Open the IBM Integration web interface for the IIBNODE_WITHQM integration node if it is
not already open.
_ 2. Expand Servers.
_ 3. Click the down arrow to the left of the server! integration server and then click Deploy.
_ 4. Click Browse and go to the c:\iabfiies\Lab08-Trc\resources directory.
_ 5. Click PD.bar and then click Open.

_ 6. Examine the Trace node properties in the PD.bar file.
__a. The BAR file contains an application that is named SIMPLEFLOW_WITH_TRACE. In
the Deploy BAR File window, expand the application until you see the message flow
nodes.
__b. Expand the Trace node to display the Trace node configurable properties.
Student Exercises
Deploy BAR File

Select a BAR file to deploy, Optionally, provide an overrides file.
Deploy preview:
Content Value
BAR file: PD. bar Browse
► FALSEO
► CATCHQ
► Test_Versii>n=2
► TraceExList
► FAILUREQ
T
Trace
fflePafii C:\lafofilestLabD8-TnASi mple Flowtrace .txt

► REPLY
Overrides
The developer specified that the Trace node should create a trace file. Based on this
setting at design time, the only property that the administrator can change is the location
of the trace file. In this BAR file, the trace file destination (filePath) is set to:
C: \labf iles\Lab08-Trc\SirnpleFlowtrace. txt.
7. Click Deploy.
You should see a message flow that the deployment was successful. You should also see that
the message flow SimpleFlowWithTrace is running under the server! integration server.
T £ IIBNODE_WIThQM w - j S
Servers
¿1. serveM T g
Services g REST
APIs » g
Applications
-r ¿g SIM P LEFIOW_WI T H_TRAC E
Tg Libraries
T £ Message Fiawsj
SimpleFlowWithTrace T
Subflows ► & Resources gp
References

Student Exercises
Part 2: Test the message flow

In this part of the exercise, you test the message flow by using the IBM MQ SupportPac RfhUtil.
_ 1. Start RfhUtil.
__ a. In Windows Explorer, browse to the C:\Software\ih03 directory.
__ b. Double-click the rfhutil.exe file.
_ 2. Put a test message on the IN queue on the IIBQM queue manager.
__ a. On the Main tab in RfuUtil, select IIBQM for the Queue Manager Name.
__ b. Select IN for the Queue Name.
__ c. Click Open File. A file selection window is displayed.
__ d. Go to C : \labf iles\LabO8-Trc\data and then select the file Test_V2_msg. xml.
Click Open.
Student Exercises
__ e. Click Write Q to send the test message to the IN queue.

_ 3. Open another RfhUtil instance and check the REPLY queue.
__ a. On the Main tab in Rfulltil, select IIBQM for the Queue Manager Name.
__ b. Select REPLY for the Queue Name.
__ c. Click Read Q.
__ d. Switch to the Data tab and click XML as the Data Format. The message should show
as follows:
<OutMsg>
<Version>2</Version>
</OutMsg>
_ 4. Do not close the RfhUtil session, as you use it later in this lab.
Part 3: Manage traces and Trace nodes

In this part of the exercise, you use the IBM Integration Console to activate a user trace and manage
the Trace node.
_ 1. In the IBM Integration web interface, verify the current state of the Trace nodes on the
integration server.
__ a. Click server! to display the integration server properties in the Overview tab.
__ b. In the Overview tab, expand the Advanced Properties section.
__ c. The Trace Node Level property identifies the current state of the Trace nodes. Verify
that the Trace Node Level is on.

Student Exercises
serveM - Integration Server

Q Overview Resource
Statistics Statistics
T Quick View
served
Integration Server Name running
Run Mode 4S3Q952e-6d74-46jß4-S165-d1 daSOScfcdS

UUID true
Running
Short Description Long

Disabled
Description Record Mode
▼ Advanced Properties
Disabled
Injection Mode Process ID Trace Level
6904
Soap Nodes use Embedded Listener Thread
none
Local Proxy Name Managers Console Mode
true
HTTP Nodes use Embedded Listener Inactive
false
User Exit List
off
false
Trace Node Level on
UserTrace Level none
2. In the IBM Integration web interface, verify the current state of the User Trace Level for the
SimpleFlowWithTrace message flow that is running in the IIBNODE_WITHQM server!
integration server.
_ a. Expand the application under the serverl integration server to show the message flow.
_ b. Click the SimpleFlowWithTrace application flow to show its properties in the Overview
tab.
The message flow Advanced Properties indicate that user trace is not active (User
Trace Level is set to none).
Student Exercises
SîmpleFlowWithTrace - Message Flow

Overview Statistics Operational Policy
Edit
T Quick View
Message Flow Name SimpleFlowWittiT race
Version
UUID Mcc 19a7-eSfQ-42e0-83d3-2074d5c50e99

Commit Cou nt 1
Additional Instances 0
Start Mode Maintained
Coordinated Transaction no
Commit Interval 0
Running true
Run Mode running
T .Advanced Properties
User Trace Level
MtUVC USCI LKIl LI3SL
3. In an IBM Integration Console, activate a debug level user trace for the
SimpleFlowWithTrace message flow.
Type:
mqs i change trace IIBNODE_WITHQM -e severl -u -f SimpleFlowWithTrace -k
SIMPLEFLOW_WITH_TRACE -1 debug
4. In the Integration web interface, verify that the User Trace Level for the message flow is
now set to debugTrace.
5. Send another test message to the IN queue by clicking Write Q in the first RfhUtil session that
you started.
6. Verify that the reply message was put on the REPLY queue on queue manager IIBQM.
7. Retrieve the user trace data and deactivate tracing by running the GETTRACE script.
This command file runs several IBM Integration Bus commands:
- mqsireadiog reads the binary trace data that the trace node generated
- mqsif ormatiog translates the binary trace data into human-readable format
- mqsichangetrace disables tracing (and can also be used to start tracing or change
trace parameters)
Student Exercises
The command file then starts Windows Notepad to display the trace output.
In the Integration Console, run the GETTRACE script. Enter the commands:

cd C:\labfiles\Tools gettrace
IIBNODE_WITHQM serverl
8. Review the user trace output. You should find all the runtime events (or errors) in the trace file.
The trace shows the path that each message took through the message flow, and how each
node responded to the message. The trace listing also shows a detailed listing of all ESQL
statements that were run in the flow.
When you are done reviewing the trace listing, close the Notepad window.
A copy of user trace file serverl. txt is provided for your reference in the
9. Review the output from the Trace node in the file you configured in the Trace node properties
(in this case, C:\labfiles\Lab08-Trc\SimpleFlowTrace.txt).
__ a. Use Windows Explorer to locate the Trace node output file.
__ b. Open the file and examine the contents. The entire message that the Trace node
received is displayed in the output because the developer specified ${Root} for the trace
pattern.
A copy of the trace file that the Trace node generates is provided for your reference in the
10. In the Integration Console, disable the user trace on the SimpleFlowWithTrace message
flow. Type:
mqs i change trace IIBNODE_WITHQM -e severl -u -f SimpleFloWWithTrace -k
SIMPLEFLOW_WITH_TRACE -1 none
11. Trace nodes generate trace records that you can use to monitor the behavior of a message
flow. After a developer finishes testing a message flow, the developer or the administrator
must disable the Trace nodes to avoid the performance impact that tracing causes. In
Integration Bus, you can turn off the Trace nodes without removing them from the message
flow.
Disable the Trace nodes on the serverl Integration server.
mqs i change trace IIBNODE_WITHQM -n off -e serverl
12. Using the Integration web interface, verify that the User Trace Level on the message flow is
now none and the Trace Node Level on the integration server is off.
Student Exercises
13. A service trace provides more detailed tracing, and generates a large amount of output. In this
part of the exercise, you can enable and disable a service trace by using the
mqsichangetrace command.
Important
You typically generate a service trace under the direction of IBM Support.
V __________________________________________________________ y
__a. In the Integration Console, type the following command to start a service trace for the
server! integration server. The -r flag resets trace to delete any previous trace data that
was collected.
mqs i change trace IIENODE_WITHQM -t -e server! -1 debug -r
The character before debug in the command is a lowercase “L”, not a “l”.
__b. Type the following command to verify the trace settings on the integration server.
mqsireporttrace IIBNODE_WITHQM -t -e serverl
You should see a response that indicates that the trace level is “debug”.
14. Go to the first RFHUtil session and send another message to the IN queue.
15. Turn off the service trace. In the Integration Console, type:
mqs i change trace IIBNODE_WITHQM -t -e serverl -1 none
16. After you generate a service trace, you must retrieve the service trace data into a file. For this
exercise, the command file getsvctrace. cmd in the c: \iabf iies\Toois directory
retrieves the service trace data. The command file is similar to the gettrace.cmd that you
used when retrieving the user trace data.
__a. Retrieve the service trace data from an IBM Integration Console session.
In the Integration Console, type the commands:
cd C:\labfiles\Tools getsvctrace 11BNODE_WITHQM serverl
__b. Review the service trace output in the Notepad session that the getsvctrace. cmd
opens.
The information that is captured in the service trace is more detailed. It includes trace
information about the interactions of the various components (such as the toolkit and the
integration nodes).
Close the Notepad window when you are done reviewing the service trace information.
A copy of the service trace file is provided for your reference in the
V _____________________________________________________

Student Exercises
Part 4: Administer the message flow debugger

Developers can use the message flow debugger in the IBM Integration Toolkit to help diagnose
unexpected behavior within message flows. Breakpoints can be set to pause the flow and examine
and change the contents of the message, Extended Structured Query Language (ESQL), and Java
variables and mappings. While developers normally do these tasks, an administrator might be called
upon to help with setting up the debugging environment.
Since the Java runtime debug environment is used for all message flow debugging, you must
configure the JVM debug port for the integration server in which the message flow is running.
The debug port can be configured in the development environment by using the IBM Integration
Toolkit, or in the administration environment by using IBM Integration web interface or a command. As
an administrator, you must also be aware of the status of the debugger because of the potential
impact on overall performance. In this exercise, you configure and manage the message flow
debugger from IBM Integration web interface.
You must configure the JVM debug port once for each integration server. The integration server
QuickView in the IBM Integration web user interface identifies whether a debug port is configured for
an integration server.
1. Determine whether a debug port is defined in the server! integration server on the
IIBNODE_WITHQM queue manager.
_ a. In the Integration web interface for IIBNODE_WITHQM, click server! to display its
properties on the Overview tab.
_ b. Expand the Resource Manager Properties section.
_ c. Verify that the current value for the JVM Manager - JVM Debug Port property is 0.
Student Exercises
c
g_j serverl - Integration Server
<Q> Overview Resource Statistics ■ ■ Statistics
► Quick View
► Advanced Properties
T Resource Manager Properties
JVM Manager - JVM Debug Port 0

JVM Manager - JVM Min Heap Size -1
JVM Manager - JVM Max Heap Size -1
JVM Manager - JVM Native Stack Size -1

JVM Manager - JVM Verbose Option none
JVM Manager - JVM System Property
2. Using the IBM Integration web interface, set the JVM debug port to 9997 .
__ a. Click Edit on the Overview tab for the server! integration server.
__ b. Scroll down until you see the JVM Manager - JVM Debug Port property.

Student Exercises

Overview Resource Statistics |^v Statistics
S Cancel
Cache Manager - Domain Name

L-J
Cache Manager - Clients Default to SSL L-J
Cache Manager - SSL Protocol
Cache Manager - SSL Alias L-J

Content Based Filtering - Enabled false L-J
Content Based Filtering - s/alidation
Threads
1 L-J
Content Based Filtering - Evaluation
1 ...
Threads
JVM Manager - JVM Debug Port

Ü ...
_ c. Click the edit icon (the icon in the same row as the property).
_ d. In the Edit Value window, type 9997 and then click OK.
_ e. Click Save.
r Note --------------------------------------------------------------------------------------------------------------------------------------------------- v
You can also use the mqsichangeproperties command to configure the JVM debug port:
mqsichangeproperties <intNodeName> -e <intServerName> -o ComlbmJVMManager -n
jvmDebugPort -v <portNumber>
If you use mqsichangeproperties to set the debug port, you must also manually stop and
restart the integration server by using the mqsistop and mqsistart commands.
V _______________________________________________________________________ V
_ 3. The integration server Resource Manager Properties update to show that a debug port
is
enabled.
The developer can now start the debugger from the Integration Toolkit. When the
developer is done debugging the message flow, you should disable the JVM debug
port.
_ 4. Disable the integration server JVM debug port by changing the JVM Resource Manager -
JVM Debug Port property to 0.
Student Exercises
Exercise Clean up
_ 1. Delete the deployed message flow application from the serverl integration server on
_ 2. Clear the messages from the REPLY queue on IIBQM.
_ 3. Close the RfhUtil windows.
End of Exercise

Student Exercises

In this exercise, you used some of the troubleshooting tools available to developers and
administrators, which include the Trace node, user trace, and service trace. This exercise
also showed you how to use the IBM Integration web interface and command to monitor
and manage the troubleshooting tools. Managing the state of the troubleshooting tools in a
production environment is especially important as many of these tools negatively affect
performance.
In this exercise, you worked with a local integration node. The same tools are also available
for managing remote integration nodes after a connection is established to the remote
integration node from the IBM Integration web interface.
Student Exercises

Student Exercises
Exercise 9. Identifying runtime problems

In the first part of this exercise, you analyze a series of message flows
that produce runtime errors and determine where the incoming
message is found after the errors occur. In the second part of the
exercise, you analyze and correct error situations that involve an IBM
Integration Bus integration node that connects to an IBM MQ queue
manager.

Introduction
In the first part of the exercise, you examine message flows that cause
a runtime exception. You evaluate the runtime exceptions and identify
what happens to the message when the designated processing node
In the second part of this exercise, you are given a preconfigured BAR
file and some information about its content and what to expect in terms
of what constitutes successful completion of the flow. You deploy and
run the message flow. The message flow fails with one or more errors.
You identify the errors and propose a correction to the problem.
Requirements
• A lab environment with IBM Integration Bus V10 and IBM MQ V8
• Successful completion of Exercises 2
• The exercise files in the C:\iabfiies\Lab09-PD and
C:\iabfiies\Toois directories
directory

podrá reproducir o
Student Exercises
Part 1: Analyze message flow runtime failures
This part of the exercise presents some message flows that connect to IBM MQ. Each
message flow shows a runtime exception. In each of the following scenarios, determine what
happens to the message that is being processed when the designated processing node
In each of the flows, TxMode is the state of the Transaction mode property for the input
message processing node.
_ 1. In this example, the error occurs on the Out node. The queue manager has a defined
dead-letter queue (DLQ) and a backout queue for the input queue (IN_BOQ).
I
Failure
E>=
Record your answer 8

here: Out

IN_BOQ B
a >
B Out
Failures:
Failure
l IN TxMode=No Compute
_ 3. Queue manager dead-letter queue = DLQ; IN queue has no backout queue.

Student Exercises
Failure
- E
+ }=
D
HJ TxMode=Yes Compute
Out
_ 4. Queue manager dead-letter queue = DLQ; IN queue backout queue =

IN_BOQ
B
Failure
B
E> =
TxMode=Yes Compute
..
Out

podrá reproducir o
Student Exercises

IN_BOQ

IN_BOQ

Student Exercises

Hint: The Out node generated the original exception, but more exceptions occurred
during explicit exception handling.

podrá reproducir o
Student Exercises
Part 2: Isolate and identify problems

In this part of the exercise, you apply your accumulated knowledge to deploy and test a
message flow and then identify the problems. The instructions in this exercise are
intentionally brief.
In this part of the exercise, you are given a preconfigured BAR file. You are also given some
information about its content and what to expect, in terms of what constitutes successful
completion of the flow.
Some general hints and tips are provided.
• What is (or are) the expected result (or results) of the BAR file content? This result is
likely to be the initial criterion to determine whether all is well (or not).
• Recall that several components can participate in the IBM Integration Bus environment:
the integration node, integration server, and in some case, IBM MQ queue managers,
and queues. When, and if, something goes wrong, error messages are likely to be
generated. The question to ask is, from which component?
• What do you know, or what can you determine, about the message flow and its use of
CATCH or FAILURE logic? What do you know about the integration node queue manager
in terms of a dead-letter queue? Consider these factors when you answer the question
“Where is the message?” in the context of the default behaviors that were described in
the lecture.
• Even though this course is about IBM Integration Bus, there are cases where the
interaction, and dependence between the integration node and the queue manager are
significant. When it comes to problem recognition and problem resolution, there is can
be overlap between the two products.
• Although you have access to the IBM Integration Toolkit in this class, the focus of the
exercise is to use the IBM Integration web user interface, IBM MQ Explorer, and system
tools.
You can find solutions to this error scenario in Appendix A.
The message flow in this error scenario triggers when a message is put on the IBM MQ IN
queue. The Filter node in the message flow routes the message to an output queue based
on the message content.

podrá reproducir o
Student Exercises
1. In the IBM MQ Explorer, verify that the following local queues exist on the IIBQM
queue manager:
• CATCH
• IN
• REPLY
• FAILURE
• FALSE
• UNKNOWN
If any of the queues are missing, create them as local queues on IIBQMGR.
2. Delete any deployed message flows from the server! integration server on
3. Deploy FindTheError.bar (in the C:\labfiles\Lab09-PD\resources directory) to the
serverl integration server.
4. Verify that the message flow SimpleFlowWithTrace message flow is deployed
and running.
- J IIBNODE_WJTHQM ▼
- ¡S Servers ^
¿g, serverl ▼
¿5 Services
gl REST APIs
m (J5 Applications
■r SIMPLEFLOW WITH TRACE
Libraries
- ™ (Message Fiows;
SimpleFlowWithTrace •*
^ Subflows
5. Use RfhUtil to test the message flow.

Use test message Test_v2_Msg.xmi that is in the C:\iabfiies\Lab09-PD\data directory.
Write the message to queue IN in queue manager IIBQM.
See Exercise 8 if you need detailed instructions for the steps to test the message flow.
V ______________________________________________________________________ J
6. Evaluate the results. Where was the message sent?
Use whatever problem determination tools you think are required to understand
exactly what is taking place. Apply corrective action as you see fit. If there is a
problem, can you correct it more than one way?
Consider this exercise complete when you identify why the message is not being put
on the REPLY queue.
Student Exercises
Exercise clean up
© Copyright IBM Corp. 2015 Exercise 9. Identifying runtime problems 9-7

_ 1. In IBM MQ Explorer, clear any remaining messages from the queues.

_ 2. Close any open windows and programs (such as RFHUtil). You can leave the IBM MQ
Explorer open.
_ 3. Delete the message flow that is running on in the server! integration server on
IIBNODE_WITHQM.
_ 4. If you enabled any traces in this exercise, turn them off.
End of Exercise

Student Exercises

The first part of the exercise helped you to understand integration node default behavior if
an error (that is, an exception) occurs in a message flow. Message flow design and IBM MQ
queue definitions and specifications also affect where the messages are ultimately found.
Part two simulated, to a degree, the nature of runtime and environmental errors that are
likely to be encountered in a typical installation. Probably the most important thing to
remember is the close relationship between the IBM Integration Bus and the queue manager
for some message flows. Although a problem might manifest itself in one product, the
contributing cause might be the other.

Student Exercises

podrá reproducir o
Student Exercises
Exercise lO.Viewing runtime statistics

In this exercise, you enable integration node statistics collection and
view the collected statistics with the IBM Integration web user
interface. You also create a subscription for the integration node
statistics and write them to a queue.

• View integration node statistics in the IBM Integration web user
interface
Introduction
In this first part of this exercise, you use the IBM Integration web
interface to enable resource statistics collection on an integration server
and message flow statistics collection on a message flow.
In the second part of this exercise, you use the IBM Integration web
interface to examine the statistics data.
In the third part of this exercise, you use IBM MQ Explorer to subscribe
to an IBM Integration Bus statistics publication. You then use the IBM
MQ SupportPac RfhUtil to retrieve and view the statistics data.
Requirements
• The integration node IIBNODE_WITHQM and the queue manager
IIBQM that were created in Exercise 2
• The lab exercise files in the C:\labfiles\LablO-Stats\resources
directory
• The IBM MQ IH03 SupportPac in the C:\software\ih03 directory
Student Exercises
Exercise set up
Import and run a message flow application by using the Flow Exerciser in the IBM
Integration Toolkit if it is not already running.
_ 1. Start the IBM Integration Toolkit, if it is not already running.
_ 2. In the IBM Integration Toolkit, switch to a new workspace.
_ a. To prevent any conflicts with any existing message flow applications, switch to a
new
workspace that is named c:\workspace\stats.
_ b. For the Workspace, type: c:\workspace\stats
_ c. Click OK. After a brief pause, the IBM Integration Toolkit restarts in the new
workspace.
_ 3. Import the simpieFiowWithMap_Pi. zip project interchange file from the
C:\labfiles\LablO-Stats\resources directory.
_ c. To the right of From zip file, click Browse.
_ d. Browse to the C:\labfiles\LablO-Stats\resources directory.
_ e. Click sinpieFiowWit±Map_Pi. zip and then click Open.
_ f. Click Transformation_Map (if it is not already selected) and then click Finish.
The Transformation_Map application is now displayed in the Application
Development view.
_ 4. Open the Transformation_Map.msgfiow message flow in the message flow editor.
_ a. Fully expand the Transformation_map application by clicking the plus (+) signs and
examine its contents.
_ b. Double-click the Transformation_Map.msgfiow message flow to open it in the
message
flow editor.

podrá reproducir o
Student Exercises
_ 5. Start the Flow Exerciser and deploy the message flow to the serverl integration server on
IIBNODE_WITHQM. ~
_ a. In the Message Flow editor, click the Start Flow exerciser icon to deploy the message
flow and start the Flow exerciser.
_ b. Select the serverl integration server on the IIBNODE_WITHQM integration node and
then click Finish.
_ c. The application is deployed to the serverl integration server on IIBNODE_WITHQM.
_ d. Click Close on the Record Message window.
Part 1: Enable message flow and resource statistics

In this part of the exercise, you enable message flow statistics and resource statistics from IBM
web user interface for the integration node IIBNODE_WITHQM.
_ 1. If it is not already open, open the IBM Integration web user interface for the
_ 2. Verify that the Transformation_Map message flow is running on serverl.
- $ IBNODEJMTHQM T
e Servers <r ^
serverl ¡gj
Services g. REST
APIs T g
Applications
- £0 Transformation_Map ▼ £
Libraries T Ep Message Flows
jTransformation_Mapi T
Up Subflows
_ 3. Enable message flow statistics collection on the Transformation_Map message flow.

_ a. Click the down pointing arrow on the right side of the Transformation_Map message
flow and then click Statistics on.
podrá reproducir o
Student Exercises
/ Note
. ^ llBNODE_WITHQM T T (=
Overview
Servers ^
^ serverl T g
Services g REST
APis -r g ■ Quick View
Appiicatiens
Message
•m .53 Transfomnation_Map
Version
Libraries
v g Message Fiows UUID
@0 Trarsformation_Map j v
g Subtlows ► Resources gp References ^
Libraries @0 Trarsformatlori_Map

g Message Flows g Stop
Subflows Resources Force stop
► in Operational Policy Statistics on ...............................
b. A confirmation message that indicates that message

Statistics off flow statistics are enabled
is displayed. Attach policy

Defach policy
r
You can view the message flow statistics collection status by running the
mqsireportfiowstats command from an IBM Integration Console.
For example, to view the message flow statistics collection status for the message flows that
are running on the serverl integration server, type:
mqsireportfiowstats IIBNODE WITHQM -a -e serverl -j
v_ J
_ 4. Enable resource statistics collection on the serverl integration server that is running on
IIBNODE_WITHQM.
_ a. Click the down pointing arrow on the right side of the serverl integration server and
then click Resource statistics on.
_ b. A confirmation message that indicates that resource statistics are enabled is
displayed.

Student Exercises
^fj IIBNODE_WITHQM *w, QS¡ Servers -*■

5
' < * serverl l
rjSj Servic serverl

(S REST Start
■wr |g3. AppliC- Start All Application Types

- m TR Start All Message Flows
e Stop
-m Stop All Application Types Stop All
Message Flows
1
S Rename
Delete All
►&
£fp Delete
, Librari Deploy
g* Share Start recording

¡gKp Messa Stop recording
Subflo Statistics on
C~t, Resoi Statistics off
¡Jg Operational F Resource statistics on

QB Data Resource statistics oft
► See urity
r / Note -------------------------------------------------------------------------------------------- ^
You can also view the resource statistics collection status by running the
mqsireportresourcestats command from an IBM Integration Console.
For example, to view the resource statistics collection status for the server! integration server
that is running on the IIBNODE_WITHQM enter:
mqsireportresourcestats IIBNODE WITHQM -e serverl
Part 2: View message flow and resource statistics

In this part of the exercise, you use the IBM Integration web interface to view the
integration server resource statistics and then message flow statistics.
_ 1. Send a test message to the flow by using the Integration Toolkit Flow Exerciser.
_ a. Click the Send a message to the flow icon in the Flow Exerciser toolbar.
Student Exercises
b. In the Send Message window, click Messagel in the Input Messages folder.
c. Click Send.
_ d. Click Close on the Progress Information window.

2. View the integration server resource statistics for server! in the IBM Integration web
interface.
a. Click the serverl integration server to display its properties and tabs.
b. Click the Resource Statistics tab to display the Resource analysis view.

Student Exercises
server! - Integration Server
se podrá reproducir o Q\ Overview Resource Statistics ['v Statistics
Resource analysis in, Download data
Used Memory (MB)
Used Memory (MB) Latest

87.0 Highest Average Lowest
87.0
Latest 87.0
Highest 87.0
Average
Lowest
354.0
10:39:45
354.0
10:39:45 10:40:00 10:40:15 10:40:30 354.0
10
354.0
I ▼ server! resource statistics Resource type: Java Virtual Machine (JVM)
:40:00
Initial Used Committed Maximum Cumulative Cumulative
Number Of
NameCommitted
▼ Memory Memory Memory Memory Memory GC Time
(MB) (MB) (MB) (MB) (Seconds) Garbage
Collections
| summary
(MB)
32 87 354 -1 89 84
Non-Heap Memory 0
32
51
36
304
50
-1
256
Heap Memory Garbage
Collection -
MarkSweepCompact 88 10
Garbage Collection -
Copy 1 74
Committed Memory (MB)
__ c. In the table at the bottom

of the Resource analysis view, click Heap Memory to add it
to the graph view. You should see a new line in the graph view that matches the
color that is shown for Heap Memory in the resource table.
_ d. In the table at the bottom of the Resource analysis view, click Non-Heap Memory to
add it to the graph view. You should see a new line in the graph view that matches
the color that is shown for Non-Heap Memory in the resource table.
_ e. In the Used Memory graph, hover you cursor over any of the graph lines to display the
data points.
If you are doing these exercises on a course image, it might take a few seconds for
the interface to recognize that your cursor is stopped over a line in the graph.
3. View the message flow statistics for Transformation_Map message flow.
_ a. Click IIBNODE_WITHQM to display its properties and tabs.
_ b. Click the Statistics tab to display the Flow comparison view.
Student Exercises
)1BN0DE_W1THQM - Integration Node
Qi Overview Statistics
Flow comparison
• Throughput per message flow for last 19 seconds. Last updated at 11:03:18 Pacific Daylight Time.
Average Elapsed
Flow name Timet Invocation Average CPI Time/
Message Rate - (messages/s) (ms) Invocatici (ms
T ransformation_Mal%| 189 7.
0.06
T Nodes for all flows In IIBNODE_WITHQM

Average -
Node Elapsed Time Average CPU Time Total Elapsed
(ms) (ms) Time (ms)
Map 11.0 0.1 11.0
HTTP Input 7.1 7.0 7.1
HTTP Reply 0.9 0.1 0.9
The Flow comparison view displays statistical information for all message flows in
the selected resource. You can use this information to see where you might
enhance performance in terms of resource usage, message flow throughput, and
response times.
c. When you identify a message flow that requires attention, you can use the Flow
analysis view to see more detailed statistical information about the nodes in the
flow.
Click the magnifying glass icon to the right of the message flow name
(Transformation_Map) to go to the Flow analysis view for the message flow.
d. The Flow analysis view contains statistical information about the selected
message flow. The view includes data such as the message rate, CPU time, and
elapsed time for messages that are processed by each node in the message flow.

Student Exercises
The charts in this view show data for three statistics at a time. By default the
charts show the message rate, average elapsed time, and average CPU time for the
selected message flow.
Ek J Transformation_Map - Message Flow
•j Overview Statistics |g=i Operational Policy
Flow analysis
▼ Updates from 09:26:51 Pacific Daylight Time (60 minutes ago). Last updated at 10:27:03 Pacific Session
e. Change the statistics to display in the charts by clicking the arrow in the table next
0.04 Latest 0.00
0.03 Average 0.01
Highest 0.05
0.02
Lowest 0.00
0.01
0
9:36 AM 9:48 AM * # # # # # # # #
40 Average Elapsed Time/ Invocation (ms)

Average Elapsed Time/ Invoci
30
Latest 0.0
20 Average 0.3
Highest 37.5
10 Lowest 0.0
0
9:36 AM 9:48 AM ### ### ### Average CPU Time/
40 Invocation (ms)
Average CPU Time/ Invocatioi ~
30
Latest 0.0
20 Average 0.2
Highest 30.6
10 Lowest 00
to each graph and then selecting the required statistic from the list.
Student Exercises
Transformation_Map - Message Flow
Q Overview Statistics (f^ Operational Policy
Flow analysis
[ ▼ Updates from 09:28:51 Pacific Daylight Time (60 minutes ago) Last updated at 10:29:03 Pacific (fgpfgianHftj Session ^ | [
f. Scroll down in this view to also see the average elapsed time and average CPU
0.05 Message Rate (messages/s) ^

0.03 Average Elapsed Time/ Invocation (ms)

A
0.02 Average CPU Time/ Invocation (ms)
0 01 Total CPU Time Waiting for Input Message (ms) Total Elapsed
0 9:36 AM 9:48 AM 10:00 AM 10:12 AM 10:24 AM Average Elapsed

Time Waiting for Input Message (ms) Maximum CPU Time (ms)
Maximum Elapsed Time (ms)

Time/ Invocation (ms)
Maximum Size of Input Messages (Kb)
40
Minimum CPU Time (ms)
30 Minimum Elapsed Time (ms)

20
10
Times Maximum Number of Threads Reached
0 Total CPU Time (ms)

9:36 AM 9:48 AM 10:00 AM 10:12 AM 10:24 AM Average CPU Time/
Total Elapsed Time (ms)
Invocation (ms) Total Input Messages
40
Total Number of Backouts
30 Total Number of Commits
Total Number of Errors Processing Messages

20
Total Number of Messages with Errors
10
Total Number of MQ Errors
0 Total Aggregation Timeouts
time for each message processing node and the map profile.
r --------------------------------------------------------------------------------------------------------------
To see real-time updates in the Statistics view, go back to the Integration Toolkit and send
another test message by using the Flow Exerciser.
V _______________________________________________________________________ J
4. Review the statistics.
Part 3: Set up subscriptions for resource statistics

If you enable resource statistics collection for one or more integration servers on an
integration node, you can subscribe to the messages that the integration node publishes.
In this part of the exercise, you subscribe to the resource statistics topic from IBM MQ
Explorer.
1. In IBM MQ Explorer, create the local queue that is named EVENTS.

Student Exercises
2. In IBM MQ Explorer, create a subscription for the resource statistics.

_ a. Right-click Subscriptions under IIBQM and then click New > Subscription.
_ b. For the subscription name, type HBResourceStatistics and then click Next.
_ c. Configure the subscription properties on the Change properties window:
• For Topic name, click Select, select SYSTEM.BROKER.MB.TOPIC, and then click
OK.
• For Topic String, type: +/ResourceStatistics/#
• For Destination queue manager, type: IIBQM
• For Destination name, type: EVENTS
_ d. Click Finish, and then click OK on the confirmation window.

_ e. The new subscription IIBResourceEvents with a topic string of
$SYS/Broker/+/ResourceStatistics/# should now appear in the Subscriptions content
view.
3. Use RfhUtil to view the resource statistics from the subscription destination message
queue and create an XML file that contains the resource statistics.
_ a. Start RfhUtil.
_ b. Select IIBQM for the Queue Manager Name.
c. Select EVENTS for the Queue Name.
Student Exercises
_ d. Click Browse Q.
_ e. Click the Data tab. You should see the resource statistics.
_ f. Under
Data ead Write View Ids MQ Help
Format,
select XML so the data can be viewed as XML data.
File Edit^^gj
Main [Data J MQMD ] PS | UsrProp | RFH ] PubSub pscr ] jms ] usr ] other | CICS | IMS ] DLQ
Message uata |o310) from EVENTS
<ResourceStatistics brokerLabel="IIBWODE_WITHQM" brokerUUID= "395c52 f 4-_t.

<ResourceType name="JYM">
■iresource Identifier -naitie= " s ummar y " I nit ia iMemo r y I nMB="32"
iresource Identifier -Use dMemo r ^ name="Heap Memory"
iresource IdentifierInitialMemoryInMB="32" UsedMe name="Non-Heap Memory"
i <resourceIdentifier InitialMemoryInMB="0" Use name=" Garb age Collection
i ■iresource Identifier- Copy" CumulativeGCTirt name=" Garb age Collection -
i </ResourceType> MarkSweep Compact” Cult
i <Re so urce Type name="
i ■iresource Identifier ODBC">
i </ResourceType>
name="summary" ExecuteSuccess="0" ExecuteFailure
i <Re so urce Type name=" Sockets"> —

( -iresource Identifier name="summary" Total5ockets="0" TotalMessages="C
</ResourceType>
Parsers">
<Re so urce Type name=" -Char Format
name="summary" Threads="0" ApproxMemKB="0.00" Ms
iresourceIdentifier (Alt)— (* Ascii C
name="[Deleted]" Threads="2" ApproxMemKB="0.DD"
iresourceIdentifier Ebcdic C Simp
name="[Administration]" Threads="2" ApproxMemKB=
iresourceIdentifier Chinese r Korean
</ResourceType> 5ecurity"> Trad Chinese C
<ResourceType name=" name="summary" TotalCacheEntries="0" TotalOperat Japanese C Thai f-
iresourceIdentifier " Russian
</ResourceType>
<ResourceType name=" - Dotïïet GC">
iresource Identifier
</ResourceType> name="summary" ExplicitGCCount="0" GenGCollectic
V CR/LF IT Indent I EDI
<ResourceType name=" -
T" Validate
iresource Identifier - DotWet App Domains">
BrowseNewt |
iresource Identifier name="summary" CurrentlyInUseInMB="0" TotalAlloc
</ResourceType> name="DefaultDomain" CurrentlylnUseInMB="G" Tote BrowsePrev I
il “
Copybook I
To make it easier to read the statistics data, copy the data into Windows Notepad, save it as
an XML file, and open it in a web browser.
a. Select the message data in RFHUtil, right-click the selected data, and then click Copy.
b. Open Windows Notepad.
c. Right-click in the Notepad session and then click Paste.
d. Save the file in c:\iabfiies\Labio-stats directory as statistics.xml and then close
Windows Notepad.
e. In Windows Explorer, locate the statistics.xml file and then double-click it to start a web
browser window.
Review the statistics. When you are finished, close the web browser window.

Student Exercises
Exercise clean up
1. In the IBM Integration web interface, stop the collection of resource statistics.
Click the down pointing arrow on the right side of the server! integration server and
then click Resource statistics off.
2. In the IBM Integration web interface, stop message flow accounting and statistics.
Click the down pointing arrow on the right side of the Transformation_Map message
flow and then click Statistics off.
3. Close the RFUtil session.
_ 4. Delete the Transformation_map message flow components from the server! integration
server on IIBNODE_WITHQM.
5. In the IBM Integration Toolkit, stop the Flow Exerciser.
6. In the IBM Integration Toolkit Integration Nodes view, right-click the server! integration
server and then click Stop recording.
End of exercise
Student Exercises

In this exercise, you used the IBM Integration web interface to enable integration node and
message flow statistics collection. You then used the IBM Integration web interface to view
the resource and message flow statistics.
Finally, you used IBM MQ Explorer to create a subscription for resource statistics.
• View integration node statistics in the IBM Integration web user interface

Student Exercises
Exercise 11.Administering workload management

policies
In this exercise, you use the IBM Integration web interface and IBM
Integration commands to create workload management policies. You
also attach workload management policies to a message flow.

Introduction
Administrators can use a workload management policy to control the
workload management attributes without the need to redeploy the
message flow or integration services resources.
Workload management policies are set at the message flow level. Using
a workload management policy, the system administrators can
complete the following tasks:
• Restrict the maximum rate at which a message flow can run
• Cause a notification message to be sent if the number of messages
that arrive in the flow exceeds a specified threshold
A workload management policy can be set up and administered within
the Integration Registry by using the IBM Integration web interface,
IBM Integration commands, and the IBM Integration API.
In the first part of this exercise, you create a workload management
policy by using the IBM Integration web interface.
In the second part of the exercise, you attach a workload management
policy to a message flow. You also use message flow statistics to
observe the effects of the attached workload policy on the message
flow.
Requirements
• The IIBNODE_NOQM integration node that was created in Exercise
1
Student Exercises
• Lab files in the c : \iabfiies\Labii-WLM directory

podrá reproducir o
Student Exercises
Part 1: Create a workload management policy
In this part of the exercise, you use the IBM Integration web interface to create a workload
management policy that is defined within a configurable service.
_ 1. Open the IBM Integration web interface for the IIBNODE_NOQM integration node.
_ 2. In the navigator, expand Operational Policy.
_ 3. Click the down arrow on the right
side of Workload Management and then Overview
click Create.
» ¿1 IIBNODE_NOQM ▼
► = Servers -w-*•
Operational Policy
► Configurable
» Quick View
Services ▼
► (ffj MQEndpoint ▼
► ¡£p MQTTPublish ▼
► MQTTSubSCribe v Version
Node Name
1
l®ÿ Workload Management V Admin Se CL
► £0 Data fo Workload Management e

► ^ Security Creat SCI
e
► gg Monitoring Long Descr
_ 4. For the policy name, type: DefauitwimPolicy

_ 5. The Additional Instances property specifies the additional threads that the integration
node can use to service the message flow.
For this exercise, set the Additional Instance property to 3.
Also, set the Start additional instances when flow starts property to Yes.
_ 6. The Processing Timeout property is the maximum time a message flow can process a
message before taking a specified action. The time is measured in seconds. The time
For this exercise, set the Processing Timeout to
r _#j
I# I 60. Information -------------------------------------------
is taken from the point that the message is received on an input node.
Automatically stopping a flow by using the workload management policy, stops the flow after
the specified amount of processing time.
There is no way to know whether the message flow was in a loop, only that it used too many
cycles, and should be stopped. When restarted, it might automatically restart again or
© Copyright IBM Corp. 2015 Exercise 11. Administering workload management policies 11-3
podrá reproducir o
continue processing until finished. If problems continue with the message flow, you can
manually force it to stop by using
the mqsistopmsgflow -f command.
J

podrá reproducir o
Student Exercises
7. The Processing timeout action property specifies the action to take when the
Processing timeout is exceeded.
For this exercise, set Processing timeout action to restartExecutionGroup, which
restarts the integration server. Set the Processing timeout to 60.
Operational Policy - WorkloadManagement : DefaultWImPolicy

0 Overview
Policy URL f^j'l Save Hä. Save As ^ Revert

/apivl /policy/Workload Management/Defau ItWlm Policy
Use a policy io control the operational behavior of a message flow at run time. [ Afore... ] Oct 21, 2015, 7:27:29 AM x
► Targets and Limits r Additional Instances
Additional instances
▼ Start Mode
Maintained
► Transactional ity
▼ Unresponsive Message Flows

_ 8. Click Save.
_ 9. Create another workload management policy that is named TenAdditionaiinstances
Use the same values that you used for the DefaultWImPolicy policy but set the
Additional instances property to io.
Part 2: Attach a workload management policy to a message flow

In this part of the exercise, you deploy a message flow and then attach a workload
management policy. You also use message flow statistics to observe the effects of the
Processing timeout action

Restart execution group
Processing timeout seconds
attached workload policy on the message flow.

_ 1. Using the IBM Integration web interface, deploy the BAR file simpieFiow.bar (in the
C:\iabfiies\Labii-WLM\resources directory) to the serverl integration server.
podrá reproducir o
Student Exercises
2. The simpieFiow.bar file contains the Transformation_Map application, which contains the
Transformation_Map message flow.
Expand the Transformation_Map application until you see the Transformation_Map
message flow.
You should see that the Transformation_Map message flow is running.
- $ IIBNODE_NOQM T := Servers v T
^ server! w g Services g REST

AP Is g Applications
53 Transfornnation_Map ▼
^ Libraries T as Message
Flows
0)H Transfornnation_Map -*■
Sutjflows ► Q3, Resources S

References
3. Click the down arrow on right side of Transformation_Map message flow and then click
Attach Policy. The Operational Policy view opens.
4. The Operational Policy view shows the list of available workload management policies for
Click Attach policy for the DefaultWImPolicy workload management policy and then click
Apply.
TransformationJVlap - Message Flow

y Overview [yy Statistics Operational Policy
Available policies
Att
ach policy
No attached policy
0
DefaultWIm Policy <s>

Ten Additional! nstaces
0
You should see a message that the policy was successfully attached.
5. Enable message flow statistics for the message flow.
6. Click the Statistics tab to view the message flow statistics for the Transformation_Map
T Flow £ Apply Cancel

Policies
message flow.

podrá reproducir o
Student Exercises
7. Change the information that the first graph displays to Number of threads in pool.
Flow analysis
Updates from 07:34:02 Pacific Daylight Time (<1 minute ago). Last updated at 07:34:22 Pacific Daylight Time Time range: Session
Average Elapsed Time/ Invocation (ms)
Average CPU Time/ Invocation (ms)
Total CPU Time Waiting for Input Message (ms) Total
Elapsed Time Waiting for Input Message (ms) Maximum
7:34:04 AM 7:34:08 AM 7:34:12 AM 7:34:16 AM 7:34: 7:34:06 AM
CPU Time (ms)
7:34:10 AM 7:34:14 AM 7:34:18 AM
Average Elapsed Time/ Invocation (ms) Maximum Elapsed Time (ms)
Maximum Size of Input Messages (Kb) Minimum CPU

Time (ms)
Minimum Elapsed Time (ms)
7:34:04 AM 7:34:08 AM 7:34.12 AM 7:34.16 AM 7:34: 7:34:06 AM Times Maximum Number of Threads Reached Total
7:34:10 AM 7:34:14 AM 7:34:18 AM
CPU Time (ms)
You should see that one thread is running.

9. In the Statistics view, you should now see that four instances are available in the
thread pool (the original instance plus three more instances).
=Ha TransformationJVlap - Message Flow

j1 Overview |rv Statistics ^ Operational Policy
Flow analysis
T Updates from 07:11:08 Pacific Daylight Time (2 minutes ago). Last updated at 07:13:11 Pacific Daylig ht Time Time range: Session
10. Detach the DefaultWImPolicy policy.

Click down arrow to the right of message flow and then click Detach policy.
11. Attach the TenAdditionallnstances workload management policy to the message flow.
13. View the Number of threads in pool in the Statistics view. You should now see that 11
instances are available in the thread pool.
podrá reproducir o
▼ Updates from 07:38:05 Pacific DaylightTime (1 minute ago). Last updated at 07:39:05 Pacific Daylight Time Timerange: Session
Student Exercises
- Transformation_Map - Message Flow
0 Overview Statistics 9 v Operational Policy
Flow analysis
Exercise clean up
_ 1. Stop the Transformation_Map message flow application from serverl on the
IIBNODE_NOQM integration node.
_ 2. Delete all flows and resources from serverl on the IIBNODE_NOQM integration node
_ 3. Close the IBM Integration web interface browser window for IIBNODE_NOQM.
End of exercise
podrá reproducir o
Student Exercises

In the first part of this exercise, you created a workload management policy by using the IBM
In the second part of the exercise, you attached a workload management policy to a message
flow. You also used message flow statistics to observe the effects of the attached workload
policy on the message flow.

Student Exercises
Exercise 12.Recording and replaying message flow

data

In this exercise, you define message flow events and then record them
in a database. You also replay messages and capture and report failed
events.

• Replay a message to an IBM MQ queue by using the IBM
Integration web interface
Introduction
This exercise uses an application that contains several message flows
(summarized in the following figure).
Student Exercises
The application processes stock trade requests, and each trade runs
five message flows: TRD1, TRD2, TRD3*, TRD4, and TRD5. The TRD3
message flow is selected based on the customer type:
• If the customer type is “Gold”, the TRD3a message flow runs.
• If the customer type is “Regular”, the TRD3b message flow runs.
• If the customer type is “Guest”, the TRD3c message flow runs.
The TRD6 flow runs if a validation failure occurs in the first messaqe
flow, TRD1.
Several of the message flow nodes have monitoring points that are
defined on them by using the Monitoring node properties. These
monitoring points publish certain items of the message payload data.
The Data viewer in the IBM Integration web user interface uses this
data to access processed messages, and to resubmit (replay) the
message for reprocessing.
r / Note ---------------------------------------------------------------------------------------------- ^
Flow monitoring can also be achieved noninvasively by using monitoring templates, which
are not covered in this lab.
V________________________________________________________________________ y
In this second part of this exercise, you set up a DB2 database for
record and replay database. You also configure the JDBC connection to
the database, and the IBM MQ queues that are required for the Trades
application. Command and batch files are provided in the
C:\iabfiies\Labi2-RandR\instaii directory to automate this process.
Requirements
• IBM MQ V8 and a queue manager that is named IIBQM
• IBM DB2
• An IBM Integration Bus integration node with an IBM MQ queue manager
specified on the integration node. The exercise instructions refer to
IIBNODE_WITHQM that is created in Exercise 2
• Lab files in the C:\iabfiies\Labi2-RandRdirectory
• The IBM MQ queues (created in the exercise): TRADE.VALIDATE.IN,
TRADE.CUST.TYPE.IN, TRADE.GOLD.IN, TRADE.REGULAR.IN,
TRADE.VALIDATION.FAILURE.IN, TRADE.GUEST.IN,
TRADE.RECONCILIATION.IN, TRADE.COMPLETE.IN,
TRADE. REPLAY. INPUT

Student Exercises
Part 1: Set up the environment for record and replay
In this part of the exercise, you set up the record and replay database, JDBC connections,
and the queues that are required for the Trades application.
Command and batch files are provided in the C:\iabfiies\Labi2-RandR\instaii directory to
automate the setup process. You can examine any of the files by using Notepad.
_ 1. Create the queues and subscriptions for the TRADES message flows on the queue
manager that is specified on the integration node.
_ a. Start an IBM Integration Console as the administrator (right-click the IBM Integration
Console shortcut on the desktop and then click Run as administrator).
_ b. In the IBM Integration Console, change directories to
C:\labfiles\Labl2-RandR\install\MQsetup. Type:
cd C:\labfiles\Labl2-RandR\install\M2setup
_ c. Enter the command to create the queues on the integration node queue manager
IIBQM:
runmqsc IIBQM < TradeQueues.mqsc d. In IBM MQ Explorer,
verify that the following objects were created:
• The local queues TRADE.VALIDATE.IN, TRADE.CUST.TYPE.IN,
TRADE.GOLD.IN, TRADE.REGULAR.IN, TRADE.VALIDATION.FAILURE.IN,
TRADE.GUEST.IN, TRADE.RECONCILIATION.IN, TRADE.COMPLETE.IN,
TRADE.REPLAY.INPUT, and RECORD.REPLAY.SUB
• The subscription RECORD.REPLAY.SUB with the topic string of
IIBNODE_WITHQM/Monitoring/#
_ 2. Create the record and replay database.
_ a. In the IBM Integration Console, type the following commands to create the DB2
database and tables:
cd ..\DBSetup CreateTRADES_Tables.bat
This command opens a DB2 command window and creates the record and replay
tables in the TRADES database. The tables are re-created so that this lab exercise
starts with a clean display of monitor events, and so that new events are easily
viewable in the IBM Integration web user interface.
It might take a few minutes for this batch file to complete.
Verify that the command ran successfully and then press Enter in the DB2
command window to close the window.
_ 3. Define the JDBC connections from the IIBNODE_WITHQM integration node to the
TRADES
database tables.
podrá reproducir o
Student Exercises
In the IBM Integration Console, type the following command:

Conf igureJDBC
_ 4. Import the data store configurable service.

The record and replay function uses a data store, which represents the database that
holds the captured monitoring events. The data store is defined to the integration
node by using configurable services.
You can define the configurable services manually. For this lab, the configurable
services are already created but they must be imported into the IIBNODE_WITHQM
integration node.
_ a. In the IBM Integration web interface for IIBNODE_WITHQM, expand the
Operational
Policy folder.
_ b. Click the down arrow to the right of the Configurable Services folder and then click
Import *.configurableservice.
^ $ IIBNODE_WlTHQM ▼ Overvi
- ¡jS Servers T
► ^ serverl ▼
- fia Operational Policy ▼
► Configurable Services
iâa Configurable Services
Qu
(Rj MQEndpoirt T(SJ Create
MQTTPublish T (R§! Import '.configurableservice
MQTTSubscribe -w (Ry
Workload Management
__ C. Browse to the C: \labfiles\Labl2-RandR\configurable_services directory and then

select the Trades_data_capture_store. configurableservice file. Click OK.
_ d. The Trades configurable service should now be listed under the Configurable
Services
> DataCaptureStore folder.

podrá reproducir o
Student Exercises
5. Following the same process as in the step 4, import Trades_source.configurableservice and
Trades_BPM_Data_Destination.configurableservice from the C:\labfiles\Labl2-
Filter Options... ^§a Trades - DataCaptureStore Configurable Service

▼ $ IIBNODEJMTHQM ▼
Q Overview
▼ Servers ^
► 45 ? serverl ▼
▼ |i] Operational Policy
-r Configurable Services ▼
► 5 ActfvityLog
► 5 Aggregation
► 5 CDServer ▼
► 5 CICSConnection Properties
► 5 CORBA commitCount
10
► 5 Collector useCoordinatedT ransaction false
► 5 ConnectoriProviders
thread Pool Size 10
► 5
queueName SYSTEM. BROKERJDC RECORD
DataCaptureSource ▼ 5 data Source Name TRADES
DataCaptureStore schema IIBAOMIN

5 DefaultCaptureStore ▼
egForView serverl
5 Trades ▼
► 5 DataiDesti nation backoutQueue SYSTEM. BROKE RJ DC .BACKOUT
egForRecord serverl
► 5 DecisionServiceRepository
commitlntervalSecs 5
RandR\configurable_services directory.
You should now have three new configurable services for the Trades application:
• DataCaptureSource > Trades_Source
• DataCaptureStore > Trades
• DataDestination > Trades Redirect to BPM
^ gi IIBNODE_WITHQM -w•r Servers ■m►
^ serverl -rr - Bn Operational Policy
— Config urable Services
► y ActivityLog
► V Aggregation
► |Vj CDServer
► ¡Vj CICSConnection
► |V| CORBA
► ¡Vj Collector
► y ConnectorPnoviders -*■ V
DataCaptureSource
V DataCaptureSourceTemplate -r iV,
Trades_Source -r
- gj DataCaptureStore
j\j DefaultCaptureStore -r |\j Trades »■
- ^ DataDestination
jVj Trades_RedBrect_to_BPM -w
[*\ Wft4Ano(iHnaKnnTQmnliita _____________________________
podrá reproducir o
Student Exercises
The Trades_Source service subscribes to the topic
$SYS/Broker/iiBNODE_wiTHQM/Monitoring/serveri/#. So this data source collects all monitoring

events that the applications in the serveri integration server generate. This data source does
not collect events that are emitted in other nodes or integration servers.
Part 2: View messages in the IBM Integration web interface

_ 1. In the IBM Integration web interface, expand Data > Data Capture Stores in the navigator
and then select the Trades data capture store.
The events list for the Trades database is empty.
IBM Integration
No data to display
Welcome, Default ’
Filler Options...
0 Data Capture Store
T £ IIBNODE_WITHQM T
0 Data viewer ^Replay list
> ¡o Servers »
> tj Operational Trades ^ Mark for replay
Policy T 0Data
Ÿ Customize ▼ ^ Filter ▼ Display Time ▼ ^Refresh
T g Data Capture |p No filler applied
Stores Q Trades
> Security □ Event time Local
Transaction ID
Parent
Transaction ID
Global
Transaction ID
Data Errors
> 0 Monitoring
2. In the IBM Integration web interface, deploy the BAR File that is named Trades .bar
from the c:\iabfiies\Labi2-RandR\appiication directory to the serveri integration
server.
3. Validate that the Trades application is deployed.
Expand the Trades application in the IBM Integration web user interface. Verify that
the application contains eight message flows. The message flows are run in sequence,
with just one of the TRD3* messages flows used, depending on the type of customer.

podrá reproducir o
Student Exercises
^ $ IIBNODE_WlTHQM ▼ T
Servers -v» serverl

g Services g REST APIs -
¡jEJ, Applications T ^ Trades Tg
Libraries gi iMessage Fiowsj
§1 TRD1_Validate ▼ gl
TRD2_Custoiner_Type T gffl T RD
3a_Gold_Trade ▼ g®
TRD3b_Regular_Trade ▼ gffl
TRD3c_Guest_Trade ▼ gSI
TRD4_Final_Reconciliation gBI
TRD5_Trade_Complete ■*- ga
TRD6_Failed_Trade_Woriiflow w¿5^
Subflows
4. Enable flow monitoring on the message flows in the Trades application.

Type the following command to enable monitoring on each of the message flows:
cd ..\•\monitoring
enableMbnitoringTrades
1
r l]
0 I Information
A
This command runs the integration node commands:
mqsichangeflowmonitoring IIENODE_WITHQM -e serverl -k Trades -
f TRDl_Validate -c active
It also runs equivalent commands for the other message flows in the Trades application.
If you redeploy the Trades application, the flow monitoring status is reset. You must
enter the enabieMonitoringTrades command again to reactivate flow monitoring.
V _____________________________________________________________________ J
_ 5. Use RfhUtil to send some new events to the Trades application queue
TRADE.VALIDATE.IN on the IIBQM queue manager.
_ a. In RFHUtil, open the file for a “Gold” customer:
C:\labfiles\Labl2_RandR\data\TradeMessageGold_BNY347290.xml
_ b. Send one instance of the data to the queue TRADE.VALIDATE.IN on IIBQM.
podrá reproducir o
Student Exercises
_ c. Send a message to TRADE.VALIDATE.IN for a “Regular” customer:

C:\labfiles\Labl2-RandR\data\TradeMessageRegular_BNY809092.xml.
_ d. Send a message to TRADE.VALIDATE.IN for a “Guest” customer:
C:\labfiles\Labl2-RandR\data\TradeMessageGuest_BNY348475.xml.
6. Click Refresh on the Data viewer in the IBM Integration web interface to show the new
events.
r rrNote _______________________________________________________________________ A
If you receive an error when trying to access the Data Capture Store, restart the server!
integration server and try to access the Data viewer again.
v ________________________________________________________________________ y

Student Exercises
Data Capture Store
Q Data viewer Replay list
Trades ▼ Mark for replay & Customize ▼ Filter ▼ Display Time v ^Refresh
No filter applied
Q Event time Local Parent Global Data Errors Event name

Transaction ID Transaction ID Transaction ID
□ CR100200-A BNY809092 APPL $500 * Trade

A
□ 2015-10-20 18:22:19.781 UTC GU123456 BNY348475 MSFT $5000 % - Trade
reconciliation
□ CR100200-A BNY809092 APPL $500 % -

Trade
□ CR100200-A BNY809092 -
Trade instruction
2015-10-20 18:21:58.125 UTC %
received
-
Trade instruction
□ 2015-10-20 18:22:19.684 UTC GU 123456 BNY348475 %
received
-
Trade instruction
□ 2015-10-20 18:22:31.490 UTC CR100200-A BNY809092 %
received
□ 2015-10-20 18:21:58.234 UTC CR100200-A BNY809092 APPL $500 % - Regular Trade:
Processing
□ CR100200-A BNY809092 APPL $500 -
Regular Trade:
2015-10-20 18:22:31.496 UTC %
Processing
□ GU123456 BNY348475 MSFT $5000 % Guest: Start
2015-10-20 18:22:19.733 UTC
□ CR100200-A BNY809092 APPL $500 -
Deciding customer
2015-10-20 18:21:58.162 UTC %
type
□ GU 123456 BNY348475 MSFT $5000 %
Deciding customer
2015-10-20 18:22:19.684 UTC
type
□ 2015-10-20 18:22:19.687 GU 123456 BNY348475 MSFT $5000 % Decision: Guest
7. The Data viewer uses the standard column heading names. You can customize the
headings so that they are more descriptive.
There are several options for customizing the column headings:
• You can change the display name of each column by double-clicking the required
display name, and entering another name. These changes are stored in the
Integration Registry, and are retained uniquely for each data capture store. All users
who display data from the same data capture store see the changes that this user
makes. If you want to record and view data with different headings, record the
events in a separate data capture store.
• You can select or clear any of the recorded fields for display.
• You can override the width of the displayed column. The widths can also be
overridden by using the divider bars.
Click Customize and change the column heading name as follows:
__a. Change Local Transaction ID to Customer number.
__b. Change Parent Transaction ID to Trade number.
__c. Change Global Transaction ID to Stock/Trade amount.
__d. Change Event name to Trade processing stage and change the field width to 160.
__e. Change hasBitstream (Data) so that it is not selected for display.
Student Exercises
w Markfor replay ; Customize

r
Customize Columns
Select the columns to display in the Data viewer. Double-click a name or width that you want to edit. You can sort the order by clicking
the header. You can also reorder tine columns and change their widths by using the header In the main Data viewer and saving your
changes here. The saved changes apply only to the current data capture store: other data capture stores retain their current settings.
Field ID Display Maine Width (px)
eve ntTi me stamp F Event time 160 j
localTransactlonld F Customer number 100
parentTransactionld F Trade number 100
globali ransactionld F Stock/Trade amount 100
hasBitstream □ Data 70
d
__ f. Click Apply. The column names are updated with the new values.
8. You can click the column headers to change the order of the events in the Data
Build Filter
Rules
viewer. For example, click the Event time column to display the oldest events first.
'll
u t^_= , v-K,“jr
Trades - Mark for replay Customize — ■ 3jt* Filter ▼
Customer Mumbeij x - starts with ■* CR

-J L±J
Filter Clear Cancel
9. _ You can limit the data that is displayed in the Data viewer by using the Filter
function. a. Click Filter.
__ b. Specify the filter criteria of: Customer number starts with CR
c. Click Filter to activate the defined filters.
i i ?ni5-1 ridn cRinn^nn-A R M Y f u i A P P I -
_ 10. You can add more filters to the display.

__ a. Click Filter again, and click the green plus sign to add a second filter.
__ b. Specify the filter criteria Of: Trade processing stage contains Complete.

Student Exercises
_ c. Click Filter to activate the new filter.
r '"7' Note ______________________________

J
The values for each filter are case-sensitive.
V __________________________________
11. Clear the filters by selecting Filter from the Data viewer tab and then clicking Clear.
Part 3: Replay messages

In this part of the exercise, you configure the IIBNODE_WITHQM integration node to replay
messages. Replay allows messages that are listed on the IBM Integration web interface to
be selected and sent to the same, or a different, message flow for further processing.
In this lab, you replay the message by sending it to a separate IBM MQ queue; another
application does not process it.
Depending on the message flow and the types of events that you want to replay, the replay
queue might be the same input queue that the original message flow uses or a different
queue. The replay might also be a separate (and different) message flow.
_ 1. Review the configurable service that was defined to enable the replay.
_ a. In the IBM Integration web interface, expand the Configurable Services folder.
_ b. Select the DataDestination > Trades_Redirect_to_BPM configurable service.
This configurable service enables messages to be routed to the TRADE.FIX.IN
queue on the IIBQM.
In this lab, a simple message flow in the Trades application processes this queue.
In another scenario, a business process management application might process it
and amend the message before sending it to the Trades application again.
_ 2. In the IBM Integration web interface Data viewer, enable the Data column.
_ a. Click Customize,
_ b. Enable the hasBitstream (Data) column.
_ c. Click Apply.
_ 3. Select some of the messages for replay.
_ a. Select the check box for the message to enable it.
_ b. Make sure that at least one of the selected messages shows the colored bitstream
icon
in the Data column.
_ c. Click Mark for replay, which is now active.
Student Exercises
Data Capture Store

Q Data viewer ££> Replay list
Trades - Mark for replay $!* Customize ▼ Filter ▼ Display Time - ^ Refresh
No fitter applied
Trade
Customer Stoek/Trade
Ü Event time Trade Number Data Errors processing
Number amount
stage
□ 2015-10-20 CR1Q0200-A BNY809092 APPLS500 - Trade

18:22:81.499 reconciliation
UTC
2015-10-20 CG123456 BNY347290 %' Trade instruction
0 18:36:13.032 received
UTC
2015-10-20 - Trade instruction

0 CR100200-A BNY809092 %
18:21:58.125 received
UTC
n 9M*i-HV?n minrfR RWVîaa?*; IS. - Trade insfnirlinn
4. Clicking Mark for replay displays the Replay list. However, you still cannot start the
Replay function. You must first select the Data Destination.
On the Data Destination menu, select the destination Trades_Redirect_to_BPM.
Data Capture Store

y Data viewer [> Replay list
Data Destination ¡Select destination x ▼ S* Replay All
T rades_Redirect_to_B PM
e Customer Trade S
5. On the Replay list view, click Replay All (or you can replay each item individually by
clicking the green arrow next to each message).
You should see that the item that contained the data bitstream was successfully sent
to the replay destination. It does not mean that the application successfully
processed data; it was successfully sent to the receiving destination.
You cannot reply items that do not contain a data bitstream.

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>. La impresión está destinada únicamente para uso personal y privado. No Student Exercises
Data Capture Store
Data
Destination
Q Data viewer [> Replay list
Trades_RedirectJo_8PM [> Replay All
Trade
Customer Trade Stock/Trad e
Replay Status Event time Data Errors processing
Number Number amount stage
*!/ P ^ Success CG123456 BNY347290 % "

2015-10-20 Trade
2 GMT received
p ¡Q¡ Success CR100200-A BNY809Q92 %
2015-10-20 Trade
5 GMÍT received
6. Confirm that the messages were sent to the replay queue.

_ a. Open IBM MQ Explorer.
_ b. Select Queues under IIBQM.
_ c. The Current queue depth of TRADE.FIX.OUT should increase by 2 (or the number of
messages that you sent for replay).
Part 4: Handle failed messages

If a message flow encounters an error during processing, it can be captured and reported
by using the IBM Integration web interface.
To enable this feature, the monitoring point on the message flow node must include the
$ExceptionList string in the monitoring event message.
_ 1. Using RFHUtil, send a bad message to the Trades application.
_ a. Open the file C: \labfiles\Labl2-RandR\data\TradeMessage_BadMessage.xml
_ b. Send the message to TRADE.VALIDATE.IN queue on IIBQM.
Although this message is a valid XML message, it is missing a required XML
element. It fails validation on the ReceiveTrade node because validation is set to
Content and Value
_ 2. In the IBM Integration web interface, you should see three new entries.
The Trade processing stage for the first event is Gold customer Processing trade.
The Trade processing stage for the second event Trade instruction received.
The Trade processing stage for the third event is Data validation failure.
Student Exercises
I j Data viewer [> Replay list
Trades Mark for replay F[< Customize tjjr- Filter ~ Display Time rr Refresh
3ji> No flier applied
Event time Trade Number Data Errors
Trade
□ Customer
Number
Stocki'Trade
amount processing
stage
n 2015-10-20
CG123456 BNY347290 IBM $1000 % "
Gold customer
18:36:13 135 UTC Processing trade
n 2015-10-20
19:19:36.538
CG123456 BNY590012 % Trade instruction
received
UTC
□ CG123456 BNY590012 Data validation
2015-10-20
19:19:36.537 failure
UTC
3. Failed events can be highlighted in the IBM Integration web interface Data viewer by
customizing the displayed columns. Click Customize.
_ a. If it is not already selected, enable the hasException (Errors) column.
_ b. Click Apply.
The Errors (hasException) column shows a red cross for all monitoring events
that contain the $ExceptionList data.
Exercise clean up
_ 1. In the IBM Integration web interface, stop the running application and then delete it
from the
_ 2. Close RFHUtil.
_ 3. Close the IBM Integration web interface.
End of exercise

Student Exercises

In Part 1 of this exercise, set up the environment for recording and replaying messages. Set
up included building the database tables and importing the configurable services.
In Part 2 of this exercise, you viewed event messages in the IBM Integration web interface,
customized the Data viewer, and defined filters to limit the data that is displayed.
In Part 3 of this exercise, you replayed messages by sending them to an alternative queue.
In Part 4 of this exercise, you configured the message flow to generate the $ExceptionList
string and identified failed messages in the IBM Integration web interface.
• Replay a message to an IBM MQ queue by using the IBM Integration web
interface
Student Exercises

podrá reproducir o Student Exercises
Appendix A. Exercise solutions
Exercise 9, Identifying runtime problems
Part 1
1. Queue manager dead-
letter queue = DLQ; IN queue
I D
#
backout queue = IN_BOQ
J
I zl. c-
Out
Answer:
The message is rolled back to the input queue. After rollbacks reach the backout
threshold, the message is put to IN_BOQ
-+o
-+ ComputeD 4»
E
Failure2 >
Failure
U
IN TxMode=No
Out
Answer:
The message is discarded because the flow is not transactional (TxMode=No) and cannot be
rolled back. The MQInput node Catch terminal is not wired so, you cannot consider that
option.

podrá reproducir o
Student Exercises
3. Queue manager dead-letter queue = DLQ; IN queue has no backout queue.
Out
Answer:
The message is rolled back to the input queue. After the backout threshold is reached, the
message is put to the DLQ. The MQInput node Catch terminal is not wired.
Out
Answer:
The message is propagated through the Compute node Failure terminal. The message
that is written to the Failure queue.
Catch
Answer:
The message is propagated through the Compute nodes Failure terminal; this action fails,
so it is propagated to the Catch terminal and thus to the Catch queue, regardless of the
transactional nature of the flow.

podrá reproducir o
Student Exercises
Failure
Failure2 at
10 gr E
>
IN TxMode=Ye: Compute =
■
Catch
Out
Answer:
The message is written to the Failure2 queue (regardless of transaction
mode). 7. Queue manager dead-letter queue = DLQ; IN queue backout
queue = IN_BOQ
*
Faillirez
Failure
E
Catch
Out
Answer:
The message is put onto the IN_BOQ after 2*BackoutThreshold retries that failed in
FAILURE2. If the IN_BOQ was full or PUT is disabled, the integration node tries to put
the message onto the DLQ. If that fails as well, the message loops between the MQInput
node and the Failure2 MQOutput node.
Part 2
After submitting the test message, you should see that message did not go to the REPLY
queue as expected. Instead, it went to the CATCH queue.
To determine why the message flow failed, enable Trace nodes on the integration server
and then run the message flow again. The command to enable Trace nodes on server! is:
mqs i change trace IIBNODE WITHQM -n on -e serverl

Student Exercises
In the Windows Event Viewer Application log you see a Warning message:
( IIBNODE_WITHQM.serverl ) Operating system error ''The system cannot find the path
specified.
'' opening trace file ''C:\labfiles\TraceFiles\SimpleFlowtrace.txt'' for trace node
'SimpleFlowWithTrace.Trace'.
The trace node 'SimpleFlowWithTrace.Trace' attempted to open the trace file

''C:\labfiles\TraceFiles\SimpleFlowtrace.txt'' but the operating system reported the
error ''The system cannot find the path specified.
''. Message flow processing will continue, but trace output will not be written. The
node will continually attempt to open the file until it succeeds.
If the name or location of the file was not specified correctly, then correct the
message flow configuration and redeploy the integration node. If the file could not
be opened due to an environment or system error, take appropriate action to correct
this situation. This message indicates that the message flow contains a Trace node
that is attempting to write its output to a directory that does not exist. Recall
that if a Trace node is sending its output to a file, the directory path that is
specified in the trace node properties must exist, or the file is not created. To
correct this problem, you must either create the specified directory or modify the
.bar file to change the path. If you correct this problem before correcting the next
error in the log, the trace output that is written to the file provides further
details on the error.
Create the folder c: \iabfiies\TraceFiies and then rerun the message flow.
When you examine the properties for the Trace node that is connected to the CATCH
terminal, you should see that it is writing to a User Trace, not a file.
Activate a User Trace on the message flow and then rerun the flow. The command is:
mqs i change trace IIBNODE_WITHQM -e severl -u -f SimpleFlowWithTrace
-k SIMPLEFLOW_WITH_TRACE -1 debug
Run the gettrace.cmd in the C:\iabfiies\Toois directory to convert the trace file and
open it in Notepad.
The error message in the log shows that the message flow fails with a reason code 2085
when it attempts to write to queue REPLYx, which does not exist. To correct this
problem, you must define this queue to the queue manager or modify the queueName
property for the REPLY node to a queue name that exists.
MessageException BIP2666E: An error occurred when opening queue ''REPLYx'' on
destination queue manager ''IIBQM''. State = '-1' ''MQW101'' '2085' '''' An error
occurred when opening a queue. The reason code from the MQOPEN is displayed as the
3rd (native error) state.
Check the WebSphere MQ completion and reason codes in the WebSphere MQ Application
Programming Reference manual to establish the cause of the error,
Student Exercises
taking any appropriate action. It may be necessary to restart the integration node
after you have performed this recovery action.

A complete copy of a sample user trace is provided in the C:\iabfiies\Lab09-PD\soiution

directory.

Student Exercises

IMPRESO POR:
Jafert Frank
Rabines
Escorza
<jrabinese@su
nat.gob.pe>. La
impresión está
destinada
únicamente
para uso
personal y
privado. No se
podrá
reproducir o
retransmitir
ninguna parte
de este libro
sin la
autorización
previa del
editor. Todo
infractor será
objeto de
acciones
legales.

Instructions

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Instructions

Transféré par

Droits d'auteur :

Formats disponibles

IMPRESO POR: Jafert Frank Rabines Escorza <jrabinese@sunat.gob.pe>.

La impresión está destinada únicamente para

IBM Integration Bus V10 System Administration

December 2015 edition

© Copyright International Business Machines Corporation 2015.

Exercises description ........................................................................................................................ vii

Exercise 1. Integration node setup andcustomization .................................................................. 1-1

Exercise 2. Connecting to IBM MQ ................................................................................................. 2-1

Exercise 3. Using the IBM Integration Toolkit ............................................................................... 3-1

Exercise 5. Using file-based security to control administration access ..................................... 5-1

Exercise 6. Using queue-based security to control administration access .............................. 6-1

Exercise 8. Using problem diagnosis tools ................................................................................... 8-1

© Copyright IBM Corp. 2015 Contents iii

Part 3: Manage traces and Trace nodes ................................................................................... 8-6

Exercise 9. Identifying runtime problems ............................................................................................ 9-1

Exercise 10. Viewing runtime statistics ............................................................................................. 10-1

Exercise 11. Administering workload management policies .......................................................... 11-1

Appendix A. Exercise solutions ........................................................................................................... A-1

iv Integration Bus V10 Administration © Copyright IBM Corp. 2015

© Copyright IBM Corp. 2015 Trademarks v

6 Integration Bus V10 Administration © Copyright IBM Corp. 2015

© Copyright IBM Corp. 2015 Exercises description 7

8 Integration Bus V10 Administration © Copyright IBM Corp. 2015

Exercise 1. Integration node setup and

What this exercise is about

What you should be able to do

IBM Integration Bus installation directory c:\Program Files\lBM\lIB\10.0.0.0\

Part 1: Get build and version information

1-2 Integration Bus V10 Administration © Copyright IBM Corp. 2015

b. Close the Welcome page by clicking Go to the Integration Toolkit.

Installed Software Installation History Features Plug-ins Configuration

1-4 Integration Bus V10 Administration © Copyright IBM Corp. 2015

Pacific Daylicfl ■fr** platform Details:

(^) View Error Log Copy to Clipboard Close

_AWWWWW__AWWWWW__AWWWWWW ______________ AW ___ A

I Enter an Integration Bus command e.g.

1-6 Integration Bus V10 Administration © Copyright IBM Corp. 2015

Part 2: Verify user authorizations

mqm IBM WebSphere MQ Administration ,..

Part 3: Create an integration node and integration servers

1-8 Integration Bus V10 Administration © Copyright IBM Corp. 2015

1. Start an IBM Integration Console session with Windows “Administrator” privileges.

3. Start the new integration node.

You should receive a response similar to the following example.

_ c. Close the Services window.

You should receive a response similar to the following example.

You should receive a response similar to the following example.

1-10 Integration Bus V10 Administration © Copyright IBM Corp. 2015

7. Display the node properties for the new integration node.

You should receive a response similar to the following example.

_ 8. Report integration node service details.

You should receive a response similar to the following example.

Install Path = C:\Program Files\IBM\IIB\10.0.0.OXserver

1-12 Integration Bus V10 Administration © Copyright IBM Corp. 2015

9. Get web interface port number for the integration node.

You should receive a response that is similar to the following example.

10. Create an integration server by using a command.

You should receive a response that is similar to the following example.

You should receive a response that is similar to the following example.

© Copyright IBM Corp. 2015

|4-3‘llBNODE_NOqM - IBM Integration - Internet Explorer

http: //localhost : IIBNODE_NOQM - IBM Integ... X | Eg IBM Knowledge Center

Exercise 1. Integration node setup and customization

Search Save Search ▼

_AWWWWWAWWWWWAWWWWWW ____________ AW _ A