websphere mq operations agent · visual message center websphere mq operations agent user guide the...

WebSphere MQ Operations AgentUser Guide

1.6VMC-TOQ

VISUAL Message Center WebSphere MQ Operations Agent User Guide

The software described in this book is furnished under a license agreement and may be used only in

accordance with the terms of the agreement.

Copyright Notice

Copyright © 2012 Barcelona/04. All rights reserved.

Document date: August 2012

Document version: 1.0

Product version: 1.6

No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any language or computer language, in any form or by any means, electronic mechani-cal, magnetic, optical, chemical, manual, or otherwise, without the prior written permission of Barcelona/04.

Trademarks

Any references to trademarked product names are owned by their respective companies.

Technical Support

For technical support visit our web site at www.barcelona04.com.

Barcelona/04 Computing Group SRL Avda. Federico Lacroze 2252, Piso 6to A-B (C1426CPU) Ciudad Autónoma de Buenos Aires Argentina

Tel: +54 11 4774-0112

Table of Contents

Table of Contents

Table of Contents .............................................................................. iii

How to Use this Guide.........................................................................v

Chapter 1

Introduction ...................................................................................... 11.1. Queue Manager Availability Monitor ...............................................................1

1.2. Queue Depth Monitor......................................................................................2

1.3. Channel Status Monitor ..................................................................................2

1.4. What You Will Find in this Document..............................................................2

Chapter 2

Before You Begin .............................................................................. 3

Chapter 3

Configuration .................................................................................... 43.1. Monitor Configuration......................................................................................4

3.2. Data Source Configuration..............................................................................6

Chapter 4

MQ ThinAgents ................................................................................ 114.1. Channel Status Monitor ................................................................................11

4.1.1. Default Health Settings ...........................................................................11

© 2012 Barcelona/04 Computing Group Page iii

Table of Contents

4.1.2. ThinAgent Variables ...............................................................................11

4.1.3. Field Map: SmartConsole - ThinkServer .................................................12

4.2. Queue Depth Monitor ...................................................................................13


4.2.2. ThinAgent Variables ..............................................................................13

4.2.3. Field Map: SmartConsole - ThinkServer ................................................14

4.3. MQ Channel Dashboards Collector Monitor .................................................14

4.3.1. Default Health Settings ..........................................................................14

4.3.2. ThinAgent Variables and Field Map: SmarConsole – ThinkServer........14

4.4. Queue Depth Monitor ...................................................................................15

4.4.1. Default Health Settings ..........................................................................15

4.4.2. ThinAgent Variables ...............................................................................15

4.4.3. Field Map: SmartConsole - ThinkServer .................................................16

4.5. MQ Queue Dashboards Collectors Monitor ..................................................16


4.5.2. ThinAgent Variables and Field Map: SmarConsole - ThinkServer..........16

4.6. Queue Manager Availability Monitor .............................................................17


4.7. MQ Queue Dashboards Collectors Monitor ..................................................17


4.7.2. ThinAgent Variables and Field Map: SmarConsole - ThinkServer.........17

4.8. Queue Manager Availability Monitor .............................................................17


Appendices

Appendix A: Further Information........................................................ 19A.1. Using Barcelona/04 PDF Documentation.....................................................19

A.2. Barcelona/04 University................................................................................19

A.3. Contacting Barcelona/04 ..............................................................................21

About Barcelona/04 Computing Group............................................... 22

Legal Notice .................................................................................... 23

© 2012 Barcelona/04 Computing Group Page iv

How to Use this Guide

© 2012 Computing Group Page v

How to Use this Guide

This chapter explains how to use Barcelona/04 User Guides and understand the typographical

conventions used in all Barcelona/04 documentation.

Typographical Conventions

The following conventional terms, text formats, and symbols are used throughout Barcelona/04 printed

documentation:

Convention Description

Boldface Commands, on-screen buttons and menu options.

Blue Italic References and links to other sections in the manual or further documentation containing relevant information.

Italic Text displayed on screen, or variables where the user must substitute their own details.

Monospace Input commands such as System i commands or code, or text that users must type in.

UPPERCASEKeyboard keys, such as CTRL for the Control key and F5 for the function key that is labeled F5.

Notes and useful additional information.

Tips and hints that will improve the users experience of working with this product.

Important additional information that the user is strongly advised to note.

Warning information. Failure to take note of this information could potentially lead to serious problems.

Introduction

Chapter 11 Introduction

This user guide provides guidance for the latest version of the WebSphere MQ Operations ThinAgents.

These ThinAgents give you the possibility to monitor the performance attributes for the two main MQ

objects, channels and queues. They also allow you to check Queue Manager availability.

The WebSphere MQ Operation ThinAgents have three main monitors and two extra monitors that are

used in the recollection of information for Dashboards.

Figure 1 – The ThinAgents shown in the ThinkServer Configurator. Notice that the WebSphere MQ Operations ThinAgents come with three monitors—MQ Channels, MQ Queues, and Queue Manager

Availability monitors. Also notice the two extra monitors called Channel Status and Queue Depth.

A brief description of each monitor follows.

1.1 Queue Manager Availability MonitorThis monitor allows the client to get the status of an instance of the MQ Manager. If this monitor shows a

critical state, the rest of monitors won’t be able to get any information.

© 2012 Barcelona/04 Computing Group Page 1

Introduction

1.2 Queue Depth MonitorThis monitor gets the depth of a queue. Depth represents the number of messages on the queue. A

queue should never become full; if so, applications won’t be able to put messages in the queue.

Although the messages wouldn’t be lost, a full queue could cause considerable problems. Controlling a

maximum value for this parameter will let you get a warning before this occurs. Besides the depth of the

channel, the monitor will get the number of open handles for input messages to the queue as well as the

number of open handles for output messages. This will give you an idea of how many applications are

connected to the queue.

1.3 Channel Status MonitorThis monitor gets the actual status of one or more channels. Within possible statuses for a channel we

have: running, retrying, sopped, paused, etc. Besides the status of the channel the monitor will get the

bytes sent and received per channel.

Both the Queue Depth monitor and the Status monitor have an extra monitor that will work as the

collector of the metrics that will be shown in the dashboards that will be available with the WebSphere

MQ Operations ThinAgents.

All these monitors will let you use filters that will support regular expressions, thus giving you the

possibility to get information for all objects or only the ones you are interested in, without having to make

a single monitor for every object.

1.4 What You Will Find in this DocumentThis user guide describes how to configure the WebSphere MQ Operations ThinAgents, as well as any

pre-configured variables. For a full description of VISUAL Message Center ThinkServer functionality,

see the VISUAL Message Center ThinkServer User Guide.


Before You Begin


Chapter 22 Before You Begin

The WebSphere MQ Operations agents are based on the Python module PyMQi. This module is built on

top of the WebSphere MQ MQI library.

WebSphere MQ Client is a prerequisite of these agents, as it supplies the necesary MQI library. The

client can be downloaded for free from an IBM site. Please refer this link to get more information about

the client and how to download it:

http://www-01.ibm.com/software/integration/wmq/clients/

We recommend that version 7.0 is installed as the agent was tested using this version and some metrics

won’t be available from versions below 6.0.

Connection to the MQ Manager will be realized using an available MQ channel configured to accept

connections from the parameterized agents.

http://www-01.ibm.com/software/integration/wmq/clients/

Configuration

Chapter 33 Configuration

3.1 Monitor ConfigurationMost of the required settings for the WebSphere MQ ThinAgents are assigned in the data source’s

configuration. All the monitors are based on shared data sources, so once you have configured the data

source, you can set up the required monitors really quickly. Besides the data source configuration

discussed below, you only need to add a name, a description of the monitor and, if needed, a filter to get

started working with the default monitors. A number of monitors can be customized to suit your needs.

The next pictures show the main tab for both the Channel Status and the Queue Depth monitors.

Figure 2 – Naming the Channel Status Monitor, and (optionally) entering a description


Configuration

Figure 3 – This monitor shares the same data source as the Channel Status monitor

In the Filters tab, you’re able to set the name or regular expression that corresponds to one or more

objects that you want to monitor. Note that the filter will be applied at the name of the object (queue or

channel).

Figure 4 – Creating filters is done in the Monitor Configuration window


Configuration

3.2 Data Source ConfigurationWebSphere MQ ThinAgents are agentless since you don´t have to install any additional software in the

target system. However, remember that the MQ WebSphere client must be installed in the computer

where the ThinkServer is installed, as mentioned in the chapter Before You Begin.

The data source is shared by all the monitors attached to it. This means that every time the data source

finishes a recollection, it will send the desired information to all the monitors configured for it.

Recollection is also refreshed when any modification is made to the data source’s configuration.

General Settings Tab

By default the data source uses a monitor’s name in the name of the data source, but you can change it

here to suit your monitoring needs and add a more detailed description of the data source if required.

Figure 5 – Connecting to a data source

The General Settings tab fields are listed here:

Configuration variables and default settings

Description

NameName of Queue Manager Server

Datasource

Replace or add the host name you are monitoring to help quickly identify where problems are occurring.

Description Enter a description of the data source

Address or Hostname

127.0.0.1This is the IP Address or hostname of the queue manager server.


Configuration

Remember that any changes you make here take effect immediately and apply to all monitors using this

data source.

Refresh Interval Tab:

Control the refresh interval of a monitor as well as its retry settings here.

Figure 6 – Refresh options for the data source

This tab’s fields are listed here:

Port 1414

The port that will be used to connect to the target data source. It appears in the TCP Listener’s configuration made at server connection.

Queue Manager Name

localhostThe name of the queue manager. It is the computer wherein WebSphere MQ is installed.

SVRCONN NameSYSTEM.DEF.SVR

CONN

The name of the channel that was assigned to connect to the queue man-ager and get the desired information.


Description


Description

Refresh Time 60The data source will be refreshed

every 60 seconds.


Configuration

Your refresh settings will apply to all monitors sharing this data source.

Advanced Tab:

These monitors are meant for use by the default WebSphere MQ Administrator role. You can enter

another user here.

Figure 7 – Entering a different role than the WebSphere MQ Administrator

Number of tries 1If we detect an error we determine that

we will retry once only...

Interval between tries

10 ...and that we will retry after 10 seconds.

Error Retry Time 60

If the number of errors exceeds the num-ber specified in Number of Tries (in this

case once), we will wait for 60 seconds

before starting the recollection process

check again.


Description


Configuration

This tab has one field:

Log Tab:

Enable logging and set logging levels here.

Figure 8 – Logging is disabled by default, and only necessary if requested

This tab’s fields are listed here:


Description

MCUser ID

The MCUserID (Message channel agent user identifier) is to be used by the MCA for authorization to access WebSphere MQ resources. It is an optional parameter and has to be set in case the channel was configured with this value. Please refer to WebSphere MQ documentation to get more information.


Description

Logging Enabled Disabled

Note: logging is to be enabled only when there is an issue with the monitor and Support has requested the log files for the monitor.

Logging Level ErrorThe level of logging of the events that will be written in the log files. There are four levels.


Configuration

Filters Tab:

Figure 9 – Filtering at the data source

Your filters will affect the amount of information that is going to be retrieved from the MQ host. Use them

to limit the amount of information that travels through the network and to improve the memory footprint

and processing time of the monitors. The filters use regular expressions to filter the elements retrieved

from an MQ System.

Exclusion filters will be evaluated before inclusion filters. The order of the filters in each group is

arbitrary.

Internally, each filtering group (inclusion or exclusion) member will be grouped using an 'OR' condition.

So if, for example, we have two exclusion filters, "Q.*" and "SYSTEM.*", internally the data source will

use the expression "Q.*|SYSTEM.*" (or vice versa) as its exclusion filter.

If, for example, you should want SYSTEM objects (queues or channels) to be excluded, you just need to

add a QUEUE or CHANNEL exclusion filter to this expression: " SYSTEM.* "

Important We recommended that you use the filter in order to avoid the generation of an extreme

quantity of messages in the channel that is being used to connect to the MQ Server.


MQ ThinAgents

Chapter 44 MQ ThinAgents

4.1 Channel Status MonitorThis monitor gets the actual status of one or more channels. Within the possible status for a channel we

have: Running, Retrying, Sopped, Paused, etc. Beside the status of the channel the monitor will get the

sent and received bytes per channel.

The status of a channel can be: BINDING, STARTING, RUNNING, PAUSED, STOPPING, RETRYING,STOPPED, REQUESTING, PAUSED or INITIALIZING.

4.1.1 Default Health SettingsBy default health messages are generated only when monitor health changes and messages are sent

according to the ThinkServer default for automatic monitor health change messages.

Monitor health will be set according to the most critical health state in the group.

The default Health rules are:

• Critical: The channel’s status is stopped

(ChannelStatus == STOPPED)

• Warning: The channel’s status is not not available and not running.

(ChannelStatus <> RUNNING and ChannelStatus <> NOT AVAILABLE)

• Minor: The channel’s status is not available

(ChannelStatus == NOT AVAILABLE

• Success: The channel’s status is running

(ChannelStatus == RUNNING)

Note that any of these health configuration settings can be changed to suit the needs of your

environment.

4.1.2 ThinAgent Variables

Variable Description

ChannelName Channel Name


MQ ThinAgents

4.1.3 Field Map: SmartConsole - ThinkServerThinkServer sends a message to SmartConsole every time the monitor is run. By default it sends the

following variables:

ChannelStatus Channel status

QueueManagerName Queue Manager name (MQ WebSphere server)

QueueManagerAddress The IP address of the Queue Manager

QueueManagerPortThe port used to get the connection to the Queue Manager through the Listener

QueueManagerStatusIt tells you if the connection to the Queue Manager was correctly set

ServerConnectionChannelName

The name of the channel that was used to make the connection

isConnectedTrue if the data source is currently connected to the Queue Manager

MCAUserId MCA User ID used to make the connection

ChannelBytesReceived Bytes received through the channel

ChannelBytesSent Bytes sent through the channel


SmartConsole ThinkServer Description

Var01 VSMScriptID Name of the script

Var02 ChannelName Channel name

Var03 ChannelStatus Channel status.

Var04 QueueManagerName Queue Manager name (MQ WebSphere server)

Var05 QueueManagerAddress The IP address of the Queue Manager

Var06 QueueManagerPort The port used to get the connection to the Queue Manager through the Listener

Var08 QueueManagerStatus It shows if the connection to the Queue Manager was correctly set

Var09ServerConnectionChan

nelNameThe name of the channel that was used to make the connection

Var10 isConnected True if the data source is currently con-nected to the Queue Manager

Var11 MCAUserId MCA User ID used to make the connec-tion

Var12 ChannelBytesReceived Bytes received through the channel

Var13 ChannelBytesSent Bytes sent through the channel


MQ ThinAgents

4.2 Queue Depth Monitor Besides the depth of the channel, this monitor will get the number of open handles for input messages to

the queue and the number of open handles for output messages. This will give you an idea of how many

applications are connected to the queue.




The default Health rules are:

• Critical: Queue depth is bigger than 100.

• Success: It is set to True in order to process all the events that do not qualify as Critical.


environment.



QueueName Name of the queue

QueueDepth Depth of the queue

QueueManagerName Queue Manager name (WebSphere MQ server)

QueueManagerAddress

The IP address of the Queue Manager


QueueManagerStatusIt shows if the connection to the Queue Manager was cor-rectly set


The name of the channel that was used to make the connec-tion


MCAUserId The MCA User ID used to make the connection

QueueOpenOutputCount

Number of handles open in order to output/send messages

QueueInputOutputCount

Number of handles open in order to input/receive messages


MQ ThinAgents



4.3 MQ Channel Dashboards Collector MonitorThis monitor will let you activate the collection of data for Dashboards with a separate monitor. It means

that you will be able to filter the information sent to the Dashboards database.

This monitor stores these two variables: ChannelBytesReceived and ChannelBytesSent.

4.3.1 Default Health SettingsIn this case, as it is a monitor with the sole purpose of storing information for Dashboards, the following

health rules apply:

• Critical: When the connection to the Queue manager could not be set.

• Success: When the connection to the Queue manager is successful.

4.3.2 ThinAgent Variables and Field Map: SmarConsole – ThinkServerThis monitor has the same variables and the same field mapping that the Channel Status Monitor has.



Var02 ChannelName Name of the queue

Var03 QueueDepth Depth of the queue

Var04 QueueManagerName Queue Manager name (WebSphere MQ server)








Var12 QueueOpenOutputCount Number of handles open to output/send messages

Var13QueueInputOutputCoun

tNumber of handles open to input/receive messages


MQ ThinAgents

4.4 Queue Depth Monitor Beside the Depth of the channel, the monitor will get the number of open handles for input messages to

the queue and the open handles for output messages. This will give you an idea of how many

applications are connected to the queue.


according to ThinkServer’s default for automatic monitor health change messages.


The default health rules are:

• Critical: Queue depth is bigger than 100.

• Success: It is set to True, in order to process all the events that do not qualify as Critical.


environment.



QueueName Name of the queue

QueueDepth Depth of the queue

QueueManagerName Queue Manager name (WebSphere MQ server)

QueueManagerAddress

The IP address of the Queue Manager


QueueManagerStatusIt shows if the connection to the Queue Manager was cor-rectly set


The name of the channel that was used to make the connec-tion


MCAUserId MCA User ID used to make the connection

QueueOpenOutputCount

Number of handles open to output/send messages

QueueInputOutputCount

Number of handles open to input/receive messages


MQ ThinAgents



4.5 MQ Queue Dashboards Collectors MonitorThis monitor will let you activate the collection of data for Dashboards with a separate monitor. It means


This monitor stores these variables: QueueOpenOutputCount, QueueInputOutputCount and

QueueDepth.

4.5.1 Default Health SettingsIn this case, as it is a monitor with the sole purpose of storing information for Dashboards, the following

health rules are set:

• Critical: When the connection to the Queue Manager could not be set.

• Success: When the connection to the Queue Manager is successful.

4.5.2 ThinAgent Variables and Field Map: SmarConsole - ThinkServerThis monitor has the same variables and the same field mapping that the Queue Depth Monitor has.



Var02 QueueName Name of the queue

Var03 QueueDepth Depth of the queue

Var04 QueueManagerName Queue Manager name (WebSphere MQ server)








Var12 QueueOpenOutputCount Number of handles open for output/send messages

Var13QueueInputOutputCoun

tNumber of handles open for input/receive messages


MQ ThinAgents

4.6 Queue Manager Availability MonitorThis monitor is intended to check the Availability of the Queue Manager. It basically checks if the

connection can be made correctly.



Monitor health will be set at the end of the group action. Only one event will be sent for the group action.


In this case, as it is a monitor with the sole purpose of storing information for Dashboards, the next

health rules apply:

• Critical: When the connection to the Queue Manager could not be set (not isConnected).

• Success: When the connection to the Queue Manager is successful (isConnected).

4.7 MQ Queue Dashboards Collectors MonitorThis monitor will let you activate the collection of data for Dashboards with a separate monitor. It means


This monitor stores these variables: QueueOpenOutputCount, QueueInputOutputCount and

QueueDepth.

4.7.1 Default Health SettingsIn this case, as it is a monitor with the sole purpose of storing information for Dashboards, the next

health rules apply:

• Critical: When the connection to the Queue Manager could not be set.

• Success: When the connection to the Queue Manager is successful.

4.7.2 ThinAgent Variables and Field Map: SmarConsole - ThinkServerThis monitor has the same variables and the same field mapping that the Queue Depth monitor has.

4.8 Queue Manager Availability MonitorThis monitor is intended to check the Availability of the Queue Manager. It basically checks if the

connection can be made correctly.



Monitor health will be set at the end of the group action. Only one event will be sent for the group action.


In this case, as it is a monitor with the main purpose of storing information for Dashboards, the following

health rules apply:


MQ ThinAgents

• Critical: When the connection to the Queue Manager could not be set (not isConnected).

• Success: When the connection to the Queue Manager is successful (isConnected) .


Appendix A : Further Information

Appendix AAppendix A: Further Information

A.1 Using Barcelona/04 PDF DocumentationBarcelona/04 documentation is available directly from the Barcelona/04 solutions DVD.

To open the Barcelona/04 documentation that is provided in PDF files use Adobe Acrobat Reader.

Acrobat Reader lets you view, search, and print the documentation. You can download Acrobat Reader

for free from the Adobe Web site (http://www.adobe.com).

To access PDF documents on the DVD:

Step 1. Navigate to a product suite (VISUAL Message Center for example) and click on the

Product Documentation link to open a list of all the User Guides available for that

product suite. The list contains direct links to the documents in PDF format.

Step 2. Alternatively, you can navigate within the DVD menu to a particular product and click on

the Product Documentation link to open the User Guide in PDF format for that

product.

A.2 Barcelona/04 UniversityIn a continuous effort to provide all users of Barcelona/04 technologies with high quality training and

education, Barcelona/04 Computing Group presents the new training program open to partners and

users worldwide.

Barcelona/04 University is aimed at providing Barcelona/04 users and partners with the most effective

tools and knowledge to manage Barcelona/04 technologies and products and use them at their highest

potential.

Attendance of the training course and passing the related exams is mandatory in order to qualify as

Barcelona/04 Business Partner for the technology area covered by the course, and will offer you

important benefits such as:

• Barcelona/04 Official Certifications - Barcelona/04 partners will be required to have a number

of certified consultants, depending on the Business Partner Level

Tip We advise printing PDF documentation for easy reference. Please ensure you familiarize

yourself with a products user guide before attempting to use the product.


http://www.adobe.com

• Exploit the full potential of Barcelona/04 technologies - Solutions such as VISUAL Message

Center and VISUAL Security Suite are very broad solutions that feature much functionality.

Knowing all these functions and how to use them is key to getting the most out of the product

• Integration with other solutions - Barcelona/04 is constantly growing: knowing the new

products and agents may allow you to integrate other parts of the IT infrastructure into

Barcelona/04 Solutions

• Barcelona/04 Business Partners will learn how to effectively deploy a monitoring project in

order to obtain the maximum effectiveness and customer satisfaction.

Participants' profile: Consultants, System Administrators, operators and technical staff, with

knowledge of Windows, iSeries, Linux and Unix systems who will be involved in managing or deploying

Barcelona/04 technology.

Pre-requisites: Being Barcelona/04 Business Partner or Barcelona/04 Customer.


A.3 Contacting Barcelona/04

North America

Tango/04 North America

PO BOX 3301

NH 03458 Peterborough USA

Phone: 1-800-304-6872 / 603-924-7391

Fax: 858-428-2864

[email protected]

www.tango04.com

EMEA

Tango/04 Computing Group S.L.

Avda. Meridiana 358, 5 A-B

08027 Barcelona Spain

Phone: +34 93 274 0051

Fax: +34 93 345 1329

[email protected]

www.tango04.com

Italy

Tango/04 Italy

Viale Garibaldi 51/53

13100 Vercelli Italy

Phone: +39 0161 56922

Fax: +39 0161 259277

[email protected]

www.tango04.it

Sales Office in France

Tango/04 France

La Grande Arche

Paroi Nord 15ème étage

92044 Paris La Défense France

Phone: +33 01 40 90 34 49

Fax: +33 01 40 90 31 01

[email protected]

www.tango04.fr

Sales Office in Switzerland

Tango/04 Switzerland

18, Avenue Louis Casaï

CH-1209 Genève

Switzerland

Phone: +41 (0)22 747 7866

Fax: +41 (0)22 747 7999

[email protected]

www.tango04.fr

Latin American Headquarters

Barcelona/04 Computing Group SRL (Argentina)

Avda. Federico Lacroze 2252, Piso 6

1426 Buenos Aires Capital Federal

Argentina

Phone: +54 11 4774-0112

Fax: +54 11 4773-9163

[email protected]

www.barcelona04.com

Sales Office in Peru

Barcelona/04 PERÚ

Centro Empresarial Real

Av. Víctor A. Belaúnde 147, Vía Principal 140 Edificio Real Seis, Piso 6

L 27 Lima

Perú

Phone: +51 1 211-2690

Fax: +51 1 211-2526

[email protected]

www.barcelona04.com

Sales Office in Chile

Barcelona/04 Chile

Nueva de Lyon 096 Oficina 702,

Providencia

Santiago

Chile

Phone: +56 2 234-0898

Fax: +56 2 2340865

[email protected]

www.barcelona04.com


Mailto:[email protected]

www.tango04.com


www.tango04.com


www.tango04.it


www.tango04.fr


www.tango04.fr


www.barcelona04.com


www.barcelona04.com


www.barcelona04.com

About Barcelona/04 Computing Group

Barcelona/04 Computing Group is one of the leading developers of systems management and

automation software. Barcelona/04 software helps companies maintain the operating health of all their

business processes, improve service levels, increase productivity, and reduce costs through intelligent

management of their IT infrastructure.

Founded in 1991 in Barcelona, Spain, Barcelona/04 is an IBM Business Partner and a key member of

IBM's Autonomic Computing initiative. Barcelona/04 has more than a thousand customers who are

served by over 35 authorized Business Partners around the world.

Alliances

Awards

Partnerships IBM Business Partner

IBM Autonomic Computing Business Partner

IBM PartnerWorld for Developers Advanced Membership

IBM ISV Advantage Agreement

IBM Early code release

IBM Direct Technical Liaison

Microsoft Developer Network

Microsoft Early Code Release


Legal Notice

The information in this document was created using certain specific equipment and environments, and it is limited in

application to those specific hardware and software products and version and releases levels.

Any references in this document regarding Barcelona/04 Computing Group products, software or services do not

mean that Barcelona/04 Computing Group intends to make these available in all countries in which Barcelona/04

Computing Group operates. Any reference to a Barcelona/04 Computing Group product, software, or service may be

used. Any functionally equivalent product that does not infringe any of Barcelona/04 Computing Group's intellectual

property rights may be used instead of the Barcelona/04 Computing Group product, software or service

Barcelona/04 Computing Group may have patents or pending patent applications covering subject matter in this

document. The furnishing of this document does not give you any license to these patents.

The information contained in this document has not been submitted to any formal Barcelona/04 Computing Group

test and is distributed AS IS. 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. Despite the fact that Barcelona/04 Computing Group could have reviewed each item for

accurateness in a specific situation, there is no guarantee that the same or similar results will be obtained

somewhere else. Customers attempting to adapt these techniques to their own environments do so at their own risk.

Barcelona/04 Computing Group shall not be liable for any damages arising out of your use of the techniques depicted

on this document, even if they have been advised of the possibility of such damages. This document could contain

technical inaccuracies or typographical errors.

Any pointers in this publication to external web sites are provided for your convenience only and do not, in any

manner, serve as an endorsement of these web sites.

The following terms are trademarks of the International Business Machines Corporation in the United States and/or

other countries: iSeries, iSeriese, iSeries, i5, DB2, e (logo)®Server IBM ®, Operating System/400, OS/400, i5/OS.

Microsoft, SQL Server, Windows, Windows NT, Windows XP and the Windows logo are trademarks of Microsoft

Corporation in the United States and/or other countries. Java and all Java-based trademarks and logos are

trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and/or other countries. UNIX is a

registered trademark in the United States and other countries licensed exclusively through The Open Group. Oracle

is a registered trade mark of Oracle Corporation.

Other company, product, and service names may be trademarks or service marks of other companies.


websphere mq operations agent · visual message center websphere mq operations agent user guide the...

Documents