Effective Administration in WMB and

IBM Integration Bus

Matthew Golby-Kirk
IBM

Session # 1477 2013 IBM Corporation

Please Note
IBMs statements regarding its plans, directions, and intent are subject to change
or withdrawal without notice at IBMs sole discretion.
Information regarding potential future products is intended to outline our general
product direction and it should not be relied on in making a purchasing decision.
The information mentioned regarding potential future products is not a
commitment, promise, or legal obligation to deliver any material, code or
functionality. Information about potential future products may not be incorporated
into any contract. The development, release, and timing of any future features or
functionality described for our products remains at our sole discretion.
Performance is based on measurements and projections using standard IBM
benchmarks in a controlled environment. The actual throughput or performance
that any user will experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in the users job stream,
the I/O configuration, the storage configuration, and the workload processed.
Therefore, no assurance can be given that an individual user will achieve results
similar to those stated here.

2 2013 IBM Corporation

IBM Integration This Week: Selected Sessions
Mon 10.30am: Integration and Messaging Trends (Palazzo N) Message Broker V8
Mon 10.30am: Healthcare Integration in WMB (Delfino 4001A) Integration Bus V9
Mon 1.00pm: Meet the Experts (San Polo 3401 Zone C)
Mon 1.00pm: Integration and Business Rules (ODM) (Marcello 4503)
Mon 1.00pm: Introduction to WMB & IB (Palazzo O)
Mon 2.30pm: WMB and WESB: Integration Bus Strategy (Palazzo O)
Mon 2.30pm: Zystems: Customer Experience WMB V8 (Marcello 4401A)
Mon 4.00pm: Mobile and WMB & IB (Palazzo O)
Mon 4.00pm: Customer Feedback roundtable (Zeno 4710)
Mon 4.00pm: Retail: Panel Discussion (Lido 3001A)
Mon 5.15pm: Kroger: Retail Integration with WMB (Lando 4303)
Mon 5.15pm: Services and WMB & IB (Palazzo O)
Tues 10.15am: Whats New in WMB & IB (Palazzo N)
Tues 10.15am: DFDL Introduction (Palazzo O)
Tues 2.30pm: Industry Formats in DFDL (Palazzo O)
Tues 2.30pm: Customer Feedback roundtable (Zeno 4710)
Tues 2.30pm: Healthcare: Documenting an Influenza Outbreak (Murano 3204)
Tues 4.00pm: Meet the Experts (San Polo 3401 Zone D)
Tues 4.00pm: Integrating with BPM (Palazzo O)
Tues 4.00pm 6.15pm: Lab (Murano 3303)
Tues 5.15pm: Effective Administration in WMB & IB (Palazzo O)
3 2013 IBM Corporation
IBM Integration This Week: Selected Sessions
Message Broker V8
Integration Bus V9
Weds 8.30am: Effective App Dev in WMB & IB (Palazzo O)
Weds 10.15am: .NET Integration (Palazzo O)
Weds 1.00pm: Workload Management and Registry in IB (Delfino 4005)
Weds 1.00pm: WMB & IB Transformation Options (Palazzo P)
Weds 1.00pm: Customer Feedback roundtable (Zeno 4710)
Weds 2.15pm: WMB & IB Record and Replay (Palazzo P)
Weds 3.45pm: WMB & IB Cloud Provisioning Options (Palazzo P)
Weds 3.45pm: Travelport: Customer Experiences (Marcello 4501B)
Weds 3.45pm: WebSphere ESB Best Practices (Lando 4203)
Weds 5.00pm: BMW: SeeBeyond to WMB (Marcello 4403)
Thurs 8.45am: Whats New in WMB & IB (Palazzo E)
Thurs 8.45am 11.15pm: Lab (Murano 3303)
Thurs 10.15am: Introduction to WMB & IB (Palazzo P)
Thurs 1.00pm: WMB and WESB: Integration Bus Strategy (Palazzo O)
Thurs 1.00pm: DFDL Introduction (Palazzo P)
Thurs 2.15pm: Mobile and WMB & IB (Palazzo N)
Thurs 2.15pm: Workload Management and Registry in IB (Palazzo O)
Thurs 3.45pm: .NET Integration (Palazzo N)

4 2013 IBM Corporation

What will this session cover?

WMB and IIB have support for two main user roles
Integration Developer
Administrator

This session will aim to cover accepted best practice for the most
typical administrator tasks.
Including some essential top tips

Topics to discuss
Tools of the trade
Administrative tasks
Under the hood

Ill focus on WMB V8

but will point out some IIB V9 improvements too!

5 2013 IBM Corporation

Interaction With Tools

Integration Integration
Toolkit Command line Third Party
Explorer Tools

Integration API (CMP)

REST API
Web REST API WAS
Admin Admin

Integration
6
Node 2013 IBM Corporation
Integration Toolkit View for Developers

7 2013 IBM Corporation

Integration Explorer

Advanced management
option designed for
administrators
Plug-in to MQ Explorer

Extra features
Create/Manage
Configurable Services
Performance Views
Group brokers using
broker sets
Offload WS-Security onto
Datapower
Administration Log
Administration Queue
Manage statistics &
8 2013 IBM Corporation
tracing
Command line tools
A wide selection of tools for scripting actions
Requires a configured environment
mqsiprofile or mqsicommandconsole (Windows)
mqsiprofile (Linux/UNIX)
JCL or ISPF (z/OS)

Most commands work against local or remote brokers

BIP1121I: Creates an execution group.

Syntax:
mqsicreateexecutiongroup brokerSpec -e egName [-w timeoutSecs] [-v traceFileName]

Command options:
'brokerSpec' is one of:
(a) 'brokerName' : Name of a locally defined broker
(b) '-n brokerFileName' : File containing remote broker connection parameters (*.broker)
(c) '-i ipAddress -p port -q qMgr' : hostname, port and queue manager of a remote broker
'-e egName' name of the new execution group
'-w timeoutSecs' maximum number of seconds to wait for the execution group to be created
'-v traceFileName' send verbose internal trace to the specified file.

9 2013 IBM Corporation

Integration API (CMP)
Java interface that enables the administration tools
Use for custom administration requirements
Fully documented and samples available

MB v8 and later allow you to create and edit message flows too
Build your entire system programmatically!
10 2013 IBM Corporation
 Natural Integration with WAS Admin Console

Compelling choice for WebSphere Application Server

WAS provides efficient application development and delivery
Simplifies learning curve for WAS users
Addresses administrator requirements
Supported on WAS V7 and V8

WAS Admin Console Plug-in

Varied set of administration tasks available
Connect to multiple local or remote brokers
View available execution groups and their current status
View services, applications, libraries, message flows

Uses standard features for ease of configuration

Role-based access to prevent unauthorized administration
Uses REST APIs for local and remote management
Use WAS Admin Console for WAS centric administrator
Complements Web UI for the administrator

Design allows for future modification of resources, start, stop etc.

Fully compatible with WAS ND

In plugin operates at cell level.
The configuration data is stored by the Deployment manager.
All Application Servers have access to cell level configuration data.

11 2012 IBM Corporation

 Web Administration and Visualisation
A comprehensive tool for web management
Manage all integration resources from zero-footprint
client
Analyze integration performance in real-time
Supported on a variety of browsers: IE10, Firefox,
Safari
Complements Integration Explorer and WAS Admin
consoles
12
Managing Integration Resources
View top-level integration node properties
Add/remove/change integration servers
Start/Stop integration data flows
Role based access to control usage
Exploits underlying public REST/JSON API
Integration Performance Analysis
Operational experience:
No developer intervention required
View metrics in real-time
CPU & I/O time shown by default
Drill down for more details
Export collected data as CSV
Exploits MQTT web sockets
Async notification - low CPU
2013 cost
IBM Corporation
Development Lifecycle and Environments
Integration Developer
Develops message flows,
message models etc.
Unit Tests on local machine
Creates Broker Archive (BAR)
files containing required artefacts
Development
Development Test
13
Administrator
Customizes BAR for target
environment (message flow
properties including queues,
database names etc.)
Deploys BAR to target environment
Management and operational
control
Test & QA Production
or
QA Production
2013 IBM Corporation
Common Administrative Tasks
Planning and configuration
Bringing a new broker online
Securing a broker
Making a broker highly available
Planning for disaster recovery

Managing brokers
Managing whats deployed
Understanding behaviour
Optimizing and tuning
Creating/Setting Policies
Migration
Maintenance

14 2013 IBM Corporation

Bringing a new broker online
Typical steps required
Preconfiguration (e.g. OS, userids)
Installation (MQ, WMB/IIB, additional software)
Creating the broker
Creating execution groups
Creating Configurable Services
Deploying BAR files
Additional configuration (e.g. security, userids)

Ensure that the environment is reproducible

Documentation
Scripting
Virtualization

Also see this session

WMB & IB Cloud Provisioning Options (Palazzo P)
Weds 3.45pm:

15 2013 IBM Corporation

Cloud Integration
Consider virtualization for new environments
Makes it easy to provision systems (and restore known state!)
WMB and IIB fully supports the use of them
Understand maintenance and performance aspects

WMB / IIB Hypervisor Editions

IBM Pure Application Systems

pre-optimized, ready-to-go systems
Quickly provision diverse product combinations WAS, MQ, MB etc

IBM Workload Deployer appliance

Virtual image software & hardware packages
RHEL 6.2 for VMware ESX x86-64 & IWD images
AIX 6.1 TL7 mksysb & IWD images
configure deploy
HVE
Config
pattern
16 2013 IBM Corporation
Securing WMB and IIB
Simplified administrative security
3 levels of authorisation for administrative actions
Reading (e.g. Viewbroker properties - mqsilist)
Writing (e.g. Change broker properties - mqsicreateexecutiongroup)
Executing (i.e. starting and stopping)
See topic bp43540 for more details
On two object types:
Broker and Execution Group
Administrative Security is not enabled by default
Enable through mqsichangebroker / mqsicreatebroker
Access controlled using MQ queues on the brokers queue
manager
Give authority to users or groups

17 2013 IBM Corporation

 SYSTEM.BROKER.AUTH
Security Queues SYSTEM.BROKER.AUTH.<egname>

+inq = Read
+put = Write
+set = Execute

18 2013 IBM Corporation

Making the broker highly available
How do I ensure that the broker is continually processing messages?
Active/Active vs. Active/Passive
Agree SLAs with the business (% uptime)

The broker includes restart recovery of Brokers and Execution Groups

But this is usually not sufficient on its own
Does not cover machine restart

Two main options

Third-party solutions (e.g. VCS/HACMP/MSCS)
Multi-instance queue managers and brokers

Distributed Cache
Built in cache support in 8.0.0.1 and later.
Enables HA scenarios

19 2013 IBM Corporation

Planning for disaster recovery
What would you do if your primary WMB location goes down?

Distribute WMB to multiple sites if possible

This introduces data replication and latency concerns

Keep DR concerns separate from HA!

HA: Systems at a single site with a single configuration
DR: Systems at multiple sites with replicated configurations
An HA failover can be a planned activity
DR is unplanned.

20 2013 IBM Corporation

Backing Up
Regularly use mqsibackupbroker to backup the brokers configuration
Ideally, after all configuration changes
Best run when stopped
But can be used whilst active as long as not undergoing configuration
changes

Consider any other required resources, for example:

Database tables
Source artefacts (message flows, BAR files)

Ensure regular restore testing

Prove your process works

Pattern to reconstitute message flows from a running broker

Available on MQSeries.net

21 2013 IBM Corporation

 Managing whats deployed

It can be difficult to understand what individual deployed resources are used for
Applications and libraries can allow you to understand why each file is there
Application: Encapsulates a single use case or scenario
Library: Promotes re-use of a shared set of files
Concepts are shared between developers and administrators
The developer chooses to create an application or library; the collection is then carried all the way
through to the runtime

22 2013 IBM Corporation

Managing shared resources
V8 and later also allow you to deploy source files directly to the runtime
Subflows (.subflow), ESQL (.esql) in addition to CMF etc.

Allows you to manage subflows and ESQL independently of the message flows
that use them

After deployment of a new version, all affected message flows pick up any
changes with the next message

New!

.esql .subflow

New! New! BAR

Broker
.msl .dfdl

23 2013 IBM Corporation

Understanding broker behaviour
The tools include a lot of information that is useful to the
administrator, for example:
Administration queue and log, Message flow and resource
statistics
Warnings when features that affect performance are enabled

Use this information to understand recent configuration changes

24 How the broker is performing, connected endpoints, etc. 2013 IBM Corporation
Understanding broker behaviour
The Activity Log shows you all recent activity on a message flow or
resource manager
For example, Show me all recent JMS activity
Visible in Integration Explorer and/or written to a file
Customisable rotation rules (based on age or size) and content

25 2013 IBM Corporation

Optimizing and tuning
The tools allow you modify the brokers configuration operationally
These tweaks more efficient to make than modifying message flows
Encourage developers to create message flows that enable operational tweaks
to be made, e.g.
Policy
Configurable Services
User-defined properties
User-defined configurable services

26 2013 IBM Corporation

Controlling Integrations with Policy
200

Integration Workload Management 180

160
Provide intelligent mechanisms to control processing speed 140

Most common scenario is to reduce back-end server load 120

Notify 100
Can be applied to new or existing integration data flows 80
60
40

Policy defines threshold limits and relevant actions 20

0
Set thresholds for integration data flow throughput 200
Specify actions at threshold, for example: 180

NOTIFY: Higher (or lower) than threshold generates publication

160
140

DELAY: Excessive workload will have latency added to shape 120

throughput Delay 100

80

REDIRECT: At threshold, send to input nodes failure terminal or 60

40
backout 20
0

200
180
160
140
120

Redirect 100
80
60
40
20
0

200
180
160
140
120
Mixed 100
80
60
40
20
0
27 2013 IBM Corporation
Managing Unresponsive Integration Flows
Target unresponsive flows through policy to improve overall system reliability
Additional WLM option aimed at unresponsive integration flows
An integration flow can become unresponsive for multiple reasons
e.g. Waiting for external system, infinite loop, deadlock, malformed XML

Waiting
for
response

Granular policy defined in Web Console for unresponsive flow

Specify threshold at which flows are considered unresponsive, e.g. 1 message/minute
Define action when flow considered unresponsive
Stop flow: unresponsive flow is stopped, other integration server flows remain unaffected
Stop server: all flows in integration server stopped, and server optionally restarted)
Workload can be managed across classes of message flows (e.g. batch vs. online)
Policies stored in local registry, and dynamically configurable
Developer can also specify limits as integration data flow properties

Commands and reporting options

New command options to stop integration flow immediately: mqsistopmsgflow f
Detection of errant flows and user stop action logged for audit
28 2013 IBM Corporation
Migrating between versions
Migration from WMB V6.1, V7 and V8
All development assets (e.g. message flows, ESQL, DFDL, Java, Maps and XSLT) import directly
Right-click convert action for pre-V8 maps; some manual tasks may be required
Migrate brokers using a single command, or create new brokers for phased migration
No redeployment necessary when using built-in migrate command
All existing BAR files can be deployed to IB V9 brokers without change

Migration commands for in-place migration

Includes migration of configuration data including broker databases, queues and registry
Forwards and backwards migration of existing components, in situ
mqsimigratecomponents command (includes t option for rollback)

Flexible co-existence options remove the need for additional hardware when migrating
IB V9 co-exists on the same OS with all previous MB versions
MQ V7.5 required for all IB V9 brokers
MQ V7.5 supported with all V6.1, V7 and V8 brokers for the purposes of V9 migration

Migation to IIB from WESB

Developer task

1 Install IB V9 2 Stop broker 3 Run migrate command 4 Start broker

or

1 Install IB V9 2 Create new broker 3 Deploy existing assets 4 Stop old broker

29 2013 IBM Corporation

Maintenance
Schedule regular maintenance windows
IBM recommends that you are on the latest maintenance level
Plan exactly what will be applied and when
A highly available environment ensures that there is no downtime

WMB has an option to enable/disable new capability in fixpacks

New functionality disabled by default
New nodes and parsers are disabled by default

mqsichangebroker MB8BROKER f 8.0.0.2

30 2013 IBM Corporation

Summary
We have discussed a number of different ways that help ensure that
administration is trouble-free

My Top Tips
Always ensure your environment is reproducible
Treat DR and HA separate
Ensure regular backups
Encourage developers to create message flows that enables operational
tweaks to be made
Schedule regular maintenance windows

31 2013 IBM Corporation

Questions?

32 2013 IBM Corporation

We love your Feedback!
Dont forget to submit your Impact session and speaker feedback!
Your feedback is very important to us we use it to improve next years
conference
Go to the Impact 2013 SmartSite (http://impactsmartsite/com):
Use the session ID number to locate the session
Click the Take Survey link
Submit your feedback

33 2013 IBM Corporation

34 2013 IBM Corporation
Legal Disclaimer

IBM Corporation 2013. All Rights Reserved.

The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained
in this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBMs current product plans and strategy, which are
subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing
contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and
conditions of the applicable license agreement governing the use of IBM software.
References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or
capabilities referenced in this presentation may change at any time at IBMs sole discretion based on market opportunities or other factors, and are not intended to be a commitment to
future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by
you will result in any specific sales, revenue growth or other results.
Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.
All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs
and performance characteristics may vary by customer.
IBM, the IBM logo, and WebSphere are trademarks of International Business Machines Corporation in the United States, other countries, or both.
Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of
others.

35 2013 IBM Corporation