Dynatrace 6.

1
WebSphere Message Broker
May 11, 2016
WebSphere Message Broker

Please direct questions about your Dynatrace product or comments on this document to:

Dynatrace Customer Support

https://community.dynatrace.com/community/display/SUPPORT

Copyright 2016 Dynatrace LLC. All rights reserved. Unpublished rights reserved under the Copyright Laws of the United States.

U.S. GOVERNMENT RIGHTS-Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Dynatrace LLC
license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii) (OCT 1988), FAR 12.212
(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable.

This product contains confidential information and trade secrets of Dynatrace LLC. Disclosure is prohibited without the prior express
written permission of Dynatrace LLC. Use of this product is subject to the terms and conditions of the user's License Agreement with
Dynatrace LLC.

Documentation may only be reproduced by Licensee for internal use. The content of this document may not be altered, modified or
changed without the express written consent of Dynatrace LLC. Dynatrace LLC may change the content specified herein at any time, with
or without notice. All current Dynatrace LLC product documentation can be found at
https://community.dynatrace.com/community/display/APMDOC.

Adobe Reader is a registered trademark of Adobe Systems Incorporated in the United States and/or other countries.

All other company and product names are trademarks or registered trademarks of their respective owners.

Document exported by Dante Jara Ortiz on 11-May-2016 22:57 UTC.

Dynatrace is the innovator behind the new generation of Application Performance

Management. Our passion: helping customers, large and small, see their applications and
digital channels through the lens of end users. Over 5,700 organizations use these insights to
master complexity, gain operational agility, and grow revenue by delivering amazing user
experiences.

2Dynatrace 6.1
 WebSphere Message Broker

Table of Contents
1 Installation 4

2 WebSphere Message Broker 7.0 and higher / WebSphere Integration Bus 9 5

2.1 AIX and z/Linux 5

2.2 Windows 6

2.3 Removal of the Agent 6

2.4 Supported Protocols 7

2.5 Message Broker PurePath 7

3 Index 8

Dynatrace 6.13
WebSphere Message Broker

1 Installation
Install the dynaTrace Agent package using the appropriate command (based on your OS) to the
machine running the System under Diagnosis (SUD).

On *NIX, use java -jar packagename.jar. You will be asked for the target directory, which
will default to your current one.

On Windows, select the installation type WebSphere MB to install only the WebSphere
Message Broker Agent. With the full Windows installation package, choose installation type
Custom and ensure that the installation of the WebSphere Message Broker Agent is
enabled.

Make sure that the Dynatrace Server is running before deploying the Dynatrace Agent.

4Dynatrace 6.1
 WebSphere Message Broker

2 WebSphere Message Broker 7.0 and higher /

WebSphere Integration Bus 9
The WebSphere Message Broker Agent is integrated using a user exit library (.lel file) that must be
registered in the WebSphere Message Broker installation.

The default Agent name is Websphere_MB[<qmgr>-<broker>-< execgrp>]. To change the prefix

to something other than Websphere_MB, set the environment variable DT_AGENTNAME.

2.1 AIX and z/Linux

1. Create the file {$MQSI_WORKPATH}/common/profiles/dtwsmbagent.sh with the following
contents and change <server-address> and <dthome> for your environment:

#!/usr/bin/sh

export DT_SERVER=<server-address>
export DT_HOME=<dthome>
#If not set DT_AGENTNAME defaults to "WebSphere_MB"
#export DT_AGENTNAME=<agentname-prefix>

#Per default we store the PurePath id in variables/dynaTrace-tag

#To store it in the Message Broker's environment, set variable name/path with e.g.:
#export DT_WSMBTAGPATH=dynaTrace/pathId

if [ "$MQSI_VERSION_V" = "6" ]
then
export MQSI_USER_EXIT_PATH=${MQSI_USER_EXIT_PATH}:${DT_HOME}/agent/lib
export MQSI_USER_EXIT_PATH64=${MQSI_USER_EXIT_PATH64}:${DT_HOME}/agent/lib64
else
export MQSI_USER_EXIT_PATH=${MQSI_USER_EXIT_PATH}:${DT_HOME}/agent/lib64
export MQSI_USER_EXIT_PATH32=${MQSI_USER_EXIT_PATH32}:${DT_HOME}/agent/lib
fi

2. Open a terminal session as user with WebSphere MB administration privileges and ensure
that the Message Broker environment was set up (mqsiprofile was executed).

3. Stop WebSphere MB:

mqsistop <brokername>

Dynatrace 6.15
WebSphere Message Broker

4. Activate the Agent in WebSphere MB:

mqsichangebroker <brokername> -e dtwsmbagent

5. Start WebSphere MB:

mqsistart <brokername>

2.2 Windows
1. Create the file %MQSI_WORKPATH%\common\profiles\dtwsmbagent.cmd with the following
contents and change <server-address> and <dthome> for your environment:

@echo off
set DT_SERVER=<server-address>
set DT_HOME=<dthome>
rem If not set DT_AGENTNAME defaults to "WebSphere_MB"
rem SET DT_AGENTNAME=<agentname-prefix>

rem Per default we store the PurePath id in variables/dynaTrace-tag

rem To store it in the Message Broker's environment, set variable name/path with e.g.:
rem set DT_WSMBTAGPATH=dynaTrace/pathId

set MQSI_USER_EXIT_PATH=%MQSI_USER_EXIT_PATH%;%DT_HOME%\agent\lib

2. Open the WebSphere MB Command Console (Start > Programs > IBM WebSphere Message
Broker 7.0 > Command Console).

3. Stop WebSphere MB:

mqsistop <brokername>

4. Activate the Agent in WebSphere MB:

mqsichangebroker <brokername> -e dtwsmbagent

5. Start WebSphere MB:

mqsistart <brokername>

2.3 Removal of the Agent

If you want to remove the Agent from a Message Broker installation, first disable the dtwsmbagent
user exit. This can be done by setting a list of active user exits that does not contain dtwsmbagent.
To disable all user exits, specify an empty list as follows (it has to be executed while the broker is
not running):

6Dynatrace 6.1
 WebSphere Message Broker

mqsichangebroker <brokername> -e ""

After disabling the user exit, the Agent is not used anymore but is still loaded by the Message
Broker. To avoid this, remove the Agent from the user exit path by removing the dtwsmbagent.sh
script (on *NIX) or .cmd script (on Windows).

2.4 Supported Protocols

Tagging requests is supported for the following protocols / node types:

HTTP: on the node types HTTPInput, HTTPReply, HTTPRequest, SOAPInput, SOAPReply,

SOAPRequest, SOAPAsyncRequest, and SOAPAsyncResponse

JMS: on the node types JMSInput, JMSOutput, JMSReply, MQInput, and MQOutput

MQ: on the node types MQInput and MQOutput. Currently MQ tagging is only supported
within the WS-MB-Agent. Only MQ messages that are put into a queue by WS-MB and are
read by WS-MB are tagged.

2.5 Message Broker PurePath

When looking at a Message Broker PurePath, the PurePath nodes reflect the following information:

Node Type = Class Name

Node Name = Method Name

Message Flow = API

Dynatrace 6.17
WebSphere Message Broker

Index

M
Message 4

N
Non Oem 4

W
Websphere 4

8Dynatrace 6.1