WebSphere® MQ Integrator for HP-UX


Installation Guide
Version 2.1

GC34-5907-02
WebSphere® MQ Integrator for HP-UX

Installation Guide
Version 2.1

GC34-5907-02
 Note!
Before using this information and the product it supports, be sure to read the general information under
Appendix E, “Notices” on page 83.

Third edition (March 2002)

This edition applies to IBM® WebSphere MQ Integrator for HP-UX Version 2.1 and to all subsequent releases and
modifications until otherwise indicated in new editions.
© Copyright International Business Machines Corporation 2000, 2002. All rights reserved.
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
 Contents
Figures . . . . . . . . . . . . . . v Installing WebSphere MQ Integrator for
HP-UX . . . . . . . . . . . . . 23
Tables. . . . . . . . . . . . . . vii Installing DB2 . . . . . . . . . . 24
Setting specific environment variables . . 24
About this book . . . . . . . . . . ix Setting up a database . . . . . . . . 25
Who this book is for . . . . . . . . . ix Performing a remote installation . . . . . 25
What you need to know to understand this Setting up the server machine . . . . . 25
book. . . . . . . . . . . . . . . ix Setting up the target machine . . . . . 26
Terms used in this book . . . . . . . . x Performing a silent installation . . . . . . 26
Accepting the licence agreement . . . . 26
Summary of changes . . . . . . . . xi Setting up a silent installation . . . . . 27
| Changes for this edition (GC34-5907–02). . . xi What to do if something goes wrong during
Changes for the previous edition installation . . . . . . . . . . . . 27
(GC34–5907–01) . . . . . . . . . . . xi
Chapter 4. Configuring a broker domain. . 29
Chapter 1. Installation overview . . . . . 1 Reviewing the assumptions about this
Installing the runtime support . . . . . . 1 configuration. . . . . . . . . . . . 34
Installing the configuration components . . . 2 Setting up user IDs and groups . . . . . 36
After you have installed the runtime and Setting up a user ID for the broker . . . 36
configuration components . . . . . . . . 2 Setting up a user ID and groups for the
Configuration Manager . . . . . . . 36
Chapter 2. Planning for installation . . . . 3 Creating and connecting to the databases . . 37
System setup . . . . . . . . . . . . 3 Creating and connecting to the database
Hardware requirements . . . . . . . 3 on HP-UX. . . . . . . . . . . . 37
Software requirements . . . . . . . . 4 Creating and connecting to databases on
License information . . . . . . . . . 7 Windows NT. . . . . . . . . . . 38
National language support . . . . . . 7 Setting up database authorizations . . . . 40
Delivery media . . . . . . . . . . . 9 Customizing the database . . . . . . . 41
Product components . . . . . . . . . 10 Configuring your broker domain . . . . . 41
Primary component . . . . . . . . 10 Creating a Configuration Manager on
Secondary components . . . . . . . 11 Windows NT. . . . . . . . . . . 42
Security considerations . . . . . . . . 13 Configuring the syslog on HP-UX. . . . 44
Migration considerations . . . . . . . . 15 Creating a broker on HP-UX . . . . . 44
Preparing for installation. . . . . . . . 15 Checking the components . . . . . . . 46
Before you start . . . . . . . . . . 15 Starting your broker domain . . . . . . 46
Starting the MQSeries listeners . . . . . 47
Defining queues and channels . . . . . 48
Chapter 3. Installing WebSphere MQ
Starting the channels . . . . . . . . 48
Integrator . . . . . . . . . . . . 21
Starting the Configuration Manager on
Installation procedure . . . . . . . . . 21
Windows NT. . . . . . . . . . . 49
Mounting WebSphere MQ Integrator for
Starting the broker on HP-UX . . . . . 49
HP-UX CDs . . . . . . . . . . . 22
Starting the Control Center on Windows
Installing New Era of Networks Rules and
NT . . . . . . . . . . . . . . 49
Formatter Support for WebSphere MQ
Connecting the broker to the domain . . 50
Integrator . . . . . . . . . . . . 23

© Copyright IBM Corp. 2000, 2002 iii

Chapter 5. Verifying your installation . . . 53 Appendix D. Applying maintenance . . . 79
Preparing for verification . . . . . . . 53 Applying maintenance to WebSphere MQ
Creating the MQSeries resources on Integrator . . . . . . . . . . . . . 79
HP-UX . . . . . . . . . . . . . 53 Restoring a previous service level . . . . . 80
Importing and deploying the WebSphere | Applying New Era of Networks maintenance 80
MQ Integrator resources on Windows NT . 54 | Removing New Era of Networks maintenance 80
Running the predefined verification Applying maintenance to IBM DB2 Universal
applications . . . . . . . . . . . . 56 Database . . . . . . . . . . . . . 81
Running the Soccer application . . . . 56 Contacting your IBM Support Center . . . 81
Running the Scribble application . . . . 59
Running the Postcard application . . . . 60 Appendix E. Notices . . . . . . . . . 83
Building and using a message flow . . . . 63 Trademarks . . . . . . . . . . . . 85
Creating the MQSeries resources . . . . 63
Creating a message flow . . . . . . . 63 Glossary of terms and abbreviations . . . 87
Assigning the message flow to the broker 64
Deploying the message flow to the broker 65 Bibliography . . . . . . . . . . . 95
Testing the message flow. . . . . . . 65 WebSphere MQ Integrator Version 2.1
cross-platform publications . . . . . . . 95
Appendix A. System changes after WebSphere MQ Integrator Version 2.1
installation . . . . . . . . . . . . 67 platform-specific publications . . . . . . 95
Directory structure . . . . . . . . . . 67 MQSeries Everyplace publications. . . . . 96
Environment variables . . . . . . . . 68 New Era of Networks Rules and Formatter
Database contents . . . . . . . . . . 69 Support for WebSphere MQ Integrator
Default MQSeries resources . . . . . . . 71 publications . . . . . . . . . . . . 96
Softcopy books . . . . . . . . . . . 96
Appendix B. Setting up an Oracle8 broker Portable Document Format (PDF) . . . . 96
database on WebSphere MQ Integrator . . 73 MQSeries publications . . . . . . . . 98
Naming conventions . . . . . . . . . 73 MQSeries Publish/Subscribe publications . . 98
Schema . . . . . . . . . . . . . 73 MQSeries Workflow publications . . . . . 98
Sizing . . . . . . . . . . . . . . 74 DB2 publications . . . . . . . . . . 98
User ID privileges . . . . . . . . . . 74 MQSeries information available on the
ODBC . . . . . . . . . . . . . . 74 Internet . . . . . . . . . . . . . 99
Rebuilding the client library . . . . . . 75
Index . . . . . . . . . . . . . 101
Appendix C. Uninstalling WebSphere MQ
Integrator . . . . . . . . . . . . 77 Sending your comments to IBM . . . . 105
Before you start . . . . . . . . . . . 77
Uninstalling WebSphere MQ Integrator: . . . 77
Unmounting the CD-ROM drive . . . . . 77

iv WebSphere MQ Integrator for HP-UX Installation Guide

Figures
1. Recommended kernel parameter values 18 3. Configuring a basic broker domain 30
2. Installing WebSphere MQ Integrator for
HP-UX . . . . . . . . . . . . 22

© Copyright IBM Corp. 2000, 2002 v

vi WebSphere MQ Integrator for HP-UX Installation Guide
Tables
1. Component disk space requirements on 5. /var/wmqi directory structure after
HP-UX . . . . . . . . . . . . 4 installation . . . . . . . . . . 68
2. Supported databases for brokers and user 6. Database tables for brokers . . . . . 70
data . . . . . . . . . . . . . 6 7. WebSphere MQ Integrator default
3. Summary of authorization in the UNIX objects . . . . . . . . . . . . 71
environments . . . . . . . . . . 13
4. /opt/wmqi/ directory structure after
installation . . . . . . . . . . 67

© Copyright IBM Corp. 2000, 2002 vii

viii WebSphere MQ Integrator for HP-UX Installation Guide
About this book
This book explains how to plan for and install IBM WebSphere MQ Integrator
for HP-UX. It also describes how to verify your installation.
v Chapter 1, “Installation overview” on page 1 provides a high-level
installation overview of WebSphere MQ Integrator for HP-UX.
v Chapter 2, “Planning for installation” on page 3 describes the preparation
you need to complete before product installation.
v Chapter 3, “Installing WebSphere MQ Integrator” on page 21 provides
detailed installation information for WebSphere MQ Integrator for HP-UX.
v Chapter 4, “Configuring a broker domain” on page 29 explains how you
configure a basic broker domain.
v Chapter 5, “Verifying your installation” on page 53 explains how to deploy
your broker network and verify its operation using the supplied verification
programs.

The appendixes cover the configuration established by the default installation

options, and details of servicing and removing the product.

For further information about the product, and planning for its use, refer to
the WebSphere MQ Integrator Introduction and Planning book.

For details of administrative tasks, including configuration and problem

determination, refer to the WebSphere MQ Integrator Administration Guide.

A glossary and bibliography are also provided.

Who this book is for

This book is intended for installers of WebSphere MQ Integrator for HP-UX.

What you need to know to understand this book

You should be familiar with:
v HP-UX system facilities.
v Windows NT® or Windows® 2000 system facilities.
v MQSeries® for HP-UX administration facilities.
v MQSeries for Windows NT and Windows 2000 administration facilities.
v The database product that will be used to support the WebSphere MQ
Integrator for HP-UX components.

© Copyright IBM Corp. 2000, 2002 ix

About this book

Terms used in this book

All references to WebSphere MQ Integrator are to WebSphere MQ Integrator
for HP-UX Version 2.1 unless otherwise stated.

All references in this book to Windows NT are also applicable to Windows

2000 unless otherwise stated. WebSphere MQ Integrator components that are
installed and operated on Windows NT can also be installed and operated on
Windows 2000.

Terms are defined in the “Glossary of terms and abbreviations” on page 87.

The book uses the following shortened names:

MQSeries
A general term for IBM MQSeries messaging products.
MQSeries Publish/Subscribe
The MQSeries Publish/Subscribe SupportPac™ that is available on the
Internet for several WebSphere MQ server operating systems. The
Internet URL is given in the section“MQSeries information available
on the Internet” on page 99.
DB2® A general term that refers to IBM DB2 Universal Database™ Enterprise
Edition, Connect Enterprise Edition, and Extended Enterprise Edition.
install_dir
Refers to the root directory for the product: /opt/wmqi

x WebSphere MQ Integrator for HP-UX Installation Guide

 Summary of changes
This section describes changes in this edition of WebSphere MQ Integrator for
HP-UX Installation Guide. Changes since the previous edition of the book are
marked by vertical lines to the left of the changes.

| Changes for this edition (GC34-5907–02)

| The changes are summarized below:
| v An Oracle database can now be accessed from within a Japanese code page;
| the national language support restriction in Chapter 2, “Planning for
| installation” on page 3 has been removed.
| v References to ″JRE″ and ″Java Runtime Environment″ have been changed to
| ″IBM Runtime Environment For the Java™ Platform″.
| v Information has been added to Chapter 3, “Installing WebSphere MQ
| Integrator” on page 21 to help you if New Era of Networks Rules and
| Formatter Support installation fails.
| v A note about the need for the IBM Runtime Environment For the Java
| Platform if you use the WebSphere MQ Integrator Command Assistant has
| been added to Chapter 4, “Configuring a broker domain” on page 29.
| v Instructions for applying maintenance to WebSphere MQ Integrator have
| been revised in Appendix D, “Applying maintenance” on page 79.
| v Information about applying and removing New Era of Networks
| maintenance has been added to Appendix D, “Applying maintenance” on
| page 79.
| v Minor editorial changes and corrections.

Changes for the previous edition (GC34–5907–01)

The changes are summarized below:
v IBM MQSeries, already an important part of the WebSphere software
platform for e-business™, is being more tightly associated with WebSphere
and is to be known as WebSphere MQ, to reflect the fundamental part that
it plays in dynamic e-business. MQSeries Integrator, now called WebSphere
MQ Integrator, is the first product to change its name; others will follow
with new releases. References to WebSphere MQ products, resources, and
concepts within this book continue to refer to MQSeries to reflect existing
product names.

© Copyright IBM Corp. 2000, 2002 xi

Changes

v Some parts of the New Era of Networks component of WebSphere MQ

Integrator have been renamed to NNSY or nnsy; other parts retain the term
NEON. References to NEON do not refer to NEON Systems Inc.
v The sections “Delivery media” on page 9 and “Preparing for installation” on
page 15 have been moved from Chapter 3, “Installing WebSphere MQ
Integrator” on page 21 to Chapter 2, “Planning for installation” on page 3.
v An additional step to display the product license agreement has been added
to the installation procedures. See sections “Installing WebSphere MQ
Integrator for HP-UX” on page 23, “Performing a remote installation” on
page 25 and “Performing a silent installation” on page 26.
v A new section has been added, called “Mounting WebSphere MQ Integrator
for HP-UX CDs” on page 22.
v Corrections have been made to the section “Installing New Era of Networks
Rules and Formatter Support for WebSphere MQ Integrator” on page 23.
v A new section about rebuilding the client library before you run db-inst
has been added, called “Rebuilding the client library” on page 75.
v An additional step to select a message set has been added to the procedure
“Importing and deploying the WebSphere MQ Integrator resources on
Windows NT” on page 54.

xii WebSphere MQ Integrator for HP-UX Installation Guide

Chapter 1. Installation overview
WebSphere MQ Integrator provides comprehensive facilities to create,
configure, and manage a broker domain on HP-UX.

A broker domain consists of:

v One or more message brokers, and optionally, a User Name Server. These
provide the runtime support, and are installed on HP-UX:
Broker
Supports diverse applications exchanging information in many
formats. A broker optionally works with a User Name Server.
User Name Server
This optional component provides access control for
publish/subscribe applications.
v Two components that are installed and configured on Windows NT to
provide configuration and management support:
Configuration Manager
This component owns and controls the configuration of the broker
domain, the procedures (message flows or business rules) that
operate within your brokers, and the definition of message formats
that can be manipulated by those procedures.
Control Center
This is a sophisticated graphical interface that runs on Windows NT
to allow controlled access to the resources defined to the
Configuration Manager. It is used to create, change, delete, and
deploy resources, and to monitor and manage their operational
status.

For a complete description of the WebSphere MQ Integrator components, the

facilities they provide, and the information formats supported, refer to the
WebSphere MQ Integrator Introduction and Planning.

Installing the runtime support

The runtime support (the message broker and optionally the User Name
Server) is installed on HP-UX. You can install and configure one or more
message brokers on one or more HP-UX systems, subject to your licence
agreement.

© Copyright IBM Corp. 2000, 2002 1

Installing runtime support

You need to configure the User Name Server on HP-UX if you want to use
topic security in a publish/subscribe environment.

Before you install WebSphere MQ Integrator, read the chapter Chapter 2,

“Planning for installation” on page 3, which provides information about:
v The hardware and software prerequisites for the WebSphere MQ Integrator
runtime support.
v The database support required by the brokers.
Instructions for installing the runtime support are given in Chapter 3,
“Installing WebSphere MQ Integrator” on page 21.

Installing the configuration components

You install and run the Configuration Manager and the Control Center
components on Windows NT. Both components are supplied on the
WebSphere MQ Integrator for Windows NT and Windows 2000 product CD.
Refer to the product CD and the WebSphere MQ Integrator for Windows NT and
Windows 2000 Installation Guide for details of the hardware and software
prerequisites for these components, and the installation instructions.

You install a single Configuration Manager in your domain. You install one,
or more, Control Centers on one, or more, systems running Windows NT.

After you have installed the runtime and configuration components

When you have installed a broker component on HP-UX, and you have
installed the Configuration Manager and Control Center components on
Windows NT, you need to configure, and then verify your installation.
Chapter 4, “Configuring a broker domain” on page 29 provides instructions
for configuring a basic broker domain. Chapter 5, “Verifying your installation”
on page 53 provides instructions for using the verification programs supplied
with the product. The verification programs introduce the basic concepts and
facilities of WebSphere MQ Integrator to enable you to verify your
installation.

2 WebSphere MQ Integrator for HP-UX Installation Guide

Chapter 2. Planning for installation
There are three steps to installing WebSphere MQ Integrator:
1. Planning and preparation:
Careful planning of your installation helps clarify your requirements and
the actions required to setup your environment. This chapter covers:
a. “System setup”.
b. “Delivery media” on page 9
c. “Product components” on page 10.
d. “Security considerations” on page 13.
e. “Migration considerations” on page 15.
f. “Preparing for installation” on page 15
2. Installation:
Decide which components you want to install, and then follow the
guidance in Chapter 3, “Installing WebSphere MQ Integrator” on page 21.
The installation program checks for any prerequisite products required by
your chosen components.
3. Configuration:
After you have installed WebSphere MQ Integrator, carry out the
configuration tasks to define and activate the resources in your
installation. The tasks are described in Chapter 4, “Configuring a broker
domain” on page 29. A set of simple tests to verify that your installation
has worked is also described.

Refer to the WebSphere MQ Integrator for Windows NT and Windows 2000

Installation Guide for details of the requirements for the Configuration
Manager and the Control Center components.

System setup
This section provides details of the prerequisite products for installation, and
related planning and setup information.
Hardware requirements
The hardware requirements for WebSphere MQ Integrator for HP-UX are
listed in the following sections.

© Copyright IBM Corp. 2000, 2002 3

System setup

General requirements
The general hardware requirements for WebSphere MQ Integrator for HP-UX
are:
v MQSeries servers:
– Any HP 9000 Series 700 or Series 800
v Any communications hardware supporting SNA LU 6.2 or TCP/IP.
v A minimum of 512MB of RAM to support runtime operation of
components.

Disk space required

Iinstallation requirements depend on the components you intend to install,
and the amount of working space you require. The latter depends primarily
on how you intend to use MQSeries resources, for example queues, and
persistent messages.

Table 1 gives the disk space requirements of each component in megabytes

(MB):
Table 1. Component disk space requirements on HP-UX
Component MB
Runtime (Broker and User Name Server) 150
Online documentation 120
Samples and SDK 1
New Era of Networks (NNSY) Interface 2
National Language Support (for each message catalog) 10
TOTAL 250

Software requirements
This section provides details of the prerequisite software and optional
products. Minimum supported levels are shown. Later compatible levels, if
any, are supported unless otherwise shown.

Prerequisite software
The following products are prerequisites:
v HP-UX Version 11.x, with June, 2001 General Patch Level, and Patches
PHSS_21906 and PHCO_22712
v IBM MQSeries for HP-UX server Version 5.2
The installation program checks that MQSeries for HP-UX Version 5.2 is
installed, and has the correct service level.
If the required MQSeries components are not installed already, you are
recommended to install them before you install WebSphere MQ Integrator.

4 WebSphere MQ Integrator for HP-UX Installation Guide

 System setup

Read the readme.txt file on the product CD to check the latest levels of
software required, and check that the MQSeries components are at the
appropriate service level.
If you want to run the Scribble or Postcard samples on HP-UX, install
MQSeries Classes for Java, supplied on the Supplemental CD, or available
from the Web.
v A database product to support your broker or brokers. All supported broker
databases are listed in Table 2 on page 6.
The use of a database by the WebSphere MQ Integrator components is
independent of the use of databases by your applications and message
flows. You are not restricted to the databases listed in Table 2 on page 6 for
application and data storage and retrieval.
A WebSphere MQ Integrator broker requires access to a database for
internal caching and for storing internal control information. The remaining
components do not need access to a database.
Ensure that a supported database is available before you can use
WebSphere MQ Integrator.
If one of the supported databases is installed already on your system, you
can use it to support WebSphere MQ Integrator.
DB2 requires an additional 250 MB of disk storage.

Note: The supplied DB2 product has restricted license terms and
agreements. You must only use this DB2 installation in association
with your licensed use of WebSphere MQ Integrator for message
management, and only the WebSphere MQ Integrator components
can make calls to the DB2 database.
v IBM Runtime Environment For the Java Platform Version 1.3 is a
prerequisite for running the Scribble and Postcard samples on HP-UX.

Optional products
The following products are options, not prerequisites:
v Connectivity
The network protocols supported are SNA LU 6.2 and TCP/IP.
For SNA connectivity:
– HP SNA plus II
v Databases
Table 2 on page 6 summarizes the supported databases.

Chapter 2. Planning for installation 5

System setup

Table 2. Supported databases for brokers and user data

Operating system DB2¹² Microsoft SQL Oracle¹ Sybase¹
Server
AIX® 6.1³⁴ not applicable 8.1.6⁴ 12
7.1³ 8.1.7
HP-UX 7.1³ not applicable 8.1.6 12⁵
8.1.7
Solaris 6.1³ not applicable 8.1.6 12
7.1³ 8.1.7
Windows NT 6.1³ 6.5 plus SP5a 8.1.6 12
7.1³ 7.0 plus SP2 8.1.7
Windows 2000 6.1³ 7.0 plus SP2 8.1.6 12
7.1³ 2000 8.1.7
OS/390®⁶ 6.1⁶ not applicable not supported not applicable
7.1⁶
z/OS™ 6.1⁶ not applicable not supported not applicable
7.1⁶
Notes:
1. Supported releases of DB2, Oracle, and Sybase can participate as a Resource Manager in a
distributed XA transaction, and can be coordinated by MQSeries as the XA Transaction Manager. In
WebSphere MQ Integrator, this is referred to as supporting a globally coordinated message flow. On
z/OS, all transactions are coordinated by RRS.
2. You must use DB2 for the configuration and message repository databases maintained by the
Configuration Manager. No other database is supported for this purpose.
3. Please check the Readme.txt file for your product to check if a Fixpack is required.
4. This version of the database is not supported on AIX Version 5.1. It is supported on AIX Version
4.3.3.
5. You must apply Sybase patch EBF9641 on HP-UX.
6. PTFs are required with this product. See the WebSphere MQ Integrator for z/OS Program Directory for
further details.

New Era of Networks Rules and Formatter Support for WebSphere MQ

Integrator Version 5.2 supports message definitions and processing rules
created and maintained in a number of databases. Refer to your New Era of
Networks Rules and Formatter Support documentation for details.

Note: These databases are for message definitions created through the New
Era of Networks database only. The databases required for internal
product use are listed earlier in this section.
v Application programming support
The following software compilers are supported:
– HP-UX C Compiler VB11.01.20 (bundle B3901BA)

6 WebSphere MQ Integrator for HP-UX Installation Guide

 System setup

– HP ANSI C++
– aCC V03.27
– Merant Server Express Version 1.1 (supported on HP-UX Version 11.0
only)
License information
Under the terms of the WebSphere MQ Integrator license agreement, you can
install one instance of each component at any one time on any one system,
with the exception of the Control Center. You can install the Control Center on
multiple systems providing that each Control Center is interacting with the
same single Configuration Manager. You can create multiple brokers on a
single system.
National language support
WebSphere MQ Integrator Version 2.1 is enabled for national language
support. The user interface and message catalogs are provided in the
following languages on distributed systems:
v Brazilian Portuguese
v French
v German
v Italian
v Japanese
v Korean
v Simplified Chinese
v Spanish
v Traditional Chinese
v US English
The message catalogs are provided in the following languages on z/OS:
v Japanese
v Simplified Chinese
v US English
The messages written to the z/OS operator console (which are a subset of the
messages written to the syslog) are in US English only, and are written in
mixed case or in uppercase depending on your chosen system configuration.

WebSphere MQ Integrator provides a selection of message catalogs that are

used by the product components to report any problems that occur. Products
that are used in conjunction with WebSphere MQ Integrator might cause
WebSphere MQ Integrator to report errors using its message catalogs, or
might report problems using their own techniques.

Chapter 2. Planning for installation 7

National language support

You must refer to the documentation supplied with any other products that
you use to determine the process they employ. In particular, you must check
the documentation supplied by the databases that you use, the New Era of
Networks Rules and Formatter Support documentation, and documentation
provided with any plug-in node or parser that you integrate into the
WebSphere MQ Integrator environment.

The New Era of Networks graphical user interfaces (Formatter, Rules, and
Visual Tester), supplied on Windows NT, are available in US English and
Japanese only.

You can install WebSphere MQ Integrator and MQSeries in any supported

language; all language versions for each product are compatible with all
language versions for the other product. All languages for the MQSeries
messaging products are included on the MQSeries server CD supplied with
WebSphere MQ Integrator.

All messages generated for internal intercomponent message exchange (for

example, deployed configuration messages and log files for mqsireadlog) are
generated in code page 1208 (utf-8).

DB2 Version 7.1 is fully NLS-enabled and is provided in all supported

languages.

If you are not using US English, you need to install the message catalog for
your chosen language. See “Secondary components” on page 11.
Notes:
1. Due to limited syslog support on HP-UX, messages are written to the log
in US English only.
2. HP-UX does not support Brazilian Portuguese locales. If you want to
access Brazilian Portuguese translated resources, select locale
pt_PT.iso88591 and create the following links:
v ln -s /opt/wmqi/CmdAsst/Params_pt_BR.properties
/opt/wmqi/CmdAsst/Params_pt.properties
v ln -s /opt/wmqi/CmdAsst/MCI_pt_BR.properties
opt/wmqi/CmdAsst/MCI_pt.properties
v ln -s /opt/wmqi/messages/WMQIv210_pt_BR.properties
/opt/wmqi/messages/WMQIv210_pt.properties
v ln -s /opt/wmqi/messages/Pt_BR/WMQIv210.cat
/usr/lib/nls/msg/pt_PT.iso88591/WMQIv210.cat

For further information about changing language settings, refer to the

WebSphere MQ Integrator Administration Guide.

8 WebSphere MQ Integrator for HP-UX Installation Guide

 National language support

Supported codesets
WebSphere MQ Integrator Version 2.1 can process and construct application
messages in any code page for which MQSeries supports conversion to and
from Unicode, on all operating systems. Supported code pages are listed in
the MQSeries Application Programming Reference.

This behavior might be affected by the use of other products in conjunction

with WebSphere MQ Integrator Version 2.1. You must check the
documentation for other products, including any databases that you use, and
the New Era of Networks Rules and Formatter Support component, for
further specific codeset support information.

Delivery media
The WebSphere MQ Integrator for HP-UX package contains the following:
1. WebSphere MQ Integrator for HP-UX Version 2.1 CD-ROM
This contains:
v WebSphere MQ Integrator for HP-UX Version 2.1.
v A documentation package for WebSphere MQ Integrator for HP-UX that
you can install.
v New Era of Networks Rules and Formatter Support for WebSphere MQ
Integrator.
v A readme.txt file that provides up-to-date details of the service levels
required by this product.
2. WebSphere MQ Integrator for HP-UX Version 2.1 Supplemental CD-ROM
This contains:
v WebSphere MQ Integrator for HP-UX Version 2.1 PDF documentation
package.
You can view the documentation without installing the product.
v Additional product services required for products supplied in this
package: MQSeries Classes for Java.
v A readme.txt file that provides details for installing the contents of the
Supplementary CD-ROM.
3. WebSphere MQ Integrator for HP-UX Version 2.1 ’DB2 for HP-UX 7.1’
CD-ROM
This is supplied for use specifically with WebSphere MQ Integrator. If a
suitable database is not installed already, install DB2, either before or after
installing WebSphere MQ Integrator.
4. WebSphere MQ Integrator for Windows NT and Windows 2000 Version 2.1
DB2 for Windows 7.1 CD-ROM (English and EMEA, or English and AP
Languages).
5. IBM MQSeries for HP-UX, Version 5.2

Chapter 2. Planning for installation 9

Delivery media

The WebSphere MQ Integrator runtime component requires IBM MQSeries

for HP-UX, Version 5.2. If the correct level is not installed already, install it
from this CD.
6. MQSeries Clients
This contains clients for each platform in each available national language.
7. WebSphere MQ Integrator for Windows NT and Windows 2000 Version 2.1
CD-ROM
This contains:
v WebSphere MQ Integrator for Windows NT and Windows 2000 Version
2.1
8. WebSphere MQ for Windows NT and Windows 2000, V5.21 CD-ROM
This CD contains the MQSeries prerequisites for WebSphere MQ Integrator
installation. If Version 5.0 or 5.1 is installed already, you can use this CD to
upgrade to Version 5.2.

For more details about these products, and their use with WebSphere MQ
Integrator, see “Software requirements” on page 4.

Product components
WebSphere MQ Integrator for HP-UX has one primary component and three
secondary components. A set of common files is installed with the primary
component.
Primary component
The primary component is called WMQI-RUNTIME. When you install the
Runtime component, the following two subcomponents are always installed:
v Broker
v User Name Server

The broker
After installation, you can create one or more brokers on each system on
which you have installed the Runtime component, subject to your license
agreement (see “License information” on page 7 for details). You can configure
and activate any number of brokers on these systems, subject to system
resource constraints.

Each broker requires its own queue manager. However, a single queue
manager can host a single broker, and the User Name Server, but they must
have been created on the same system.

Each broker requires access to a database to create and maintain internal data
in tables. The tables hold information about the current configuration of the
broker (for example, the message flows that are assigned to it). You are

10 WebSphere MQ Integrator for HP-UX Installation Guide

 Product components

advised to use a local database server for performance reasons, although

client connection to a remote DB2 server is supported. If you use a DB2 client
connection, consider network loading and reliability carefully. Any delays
significantly impact performance in the broker domain.

Table 2 on page 6 provides a summary of supported databases.

The User Name Server

The User Name Server requires an MQSeries queue manager to be assigned to
it. The User Name Server does not require access to a database. You are
recommended to configure one User Name Server within your broker domain
if you plan to publish and subscribe.
Secondary components
You can choose to install the following optional components in your broker
domain:
v Samples and Software Developers’ Kit (WMQI-SDK)
v Online documentation (WMQI-DOCS)
v National Language Support (NLS) message catalogs

You can install these components without a previous installation of MQSeries

or a database.

Samples and Software Developers’ Kit (SDK)

This component comprises a set of samples to help you configure your
WebSphere MQ Integrator system, and to illustrate how to extend WebSphere
MQ Integrator functionality using the plug-in interface.
v Sample verification programs
The verification programs Scribble, Postcard, and Soccer are provided to
help you test your initial installation. These are described in “Running the
predefined verification applications” on page 56. The source code and
executable files are supplied in C for Postcard and Soccer, and in Java for
Scribble. Header files and a file defining the MQSeries queues used by the
sample verification programs are also supplied.
v Sample plug-in nodes
C source code for sample plug-in nodes, a sample parser and header files
are supplied. Pseudo-XML files that can be used as input to the sample
plug-in nodes are also provided. Refer to the WebSphere MQ Integrator
Programming Guide for details about using plug-in nodes and the sample
files provided.
v Samples profiles
Sample profiles are provided for all the supported UNIX® platforms.
v Database samples
The directory xatm contains a sample file called db2swit.

Chapter 2. Planning for installation 11

 Product components

A number of additional samples are provided as WebSphere MQ Integrator

SupportPacs. Refer to http://www.ibm.com/software/mqseries for details.

Note: Before running Scribble and Postcard, install the MQSeries Classes for
Java, and then set environment variables in your profile. To find out
which environment variables need setting, check the sample profile
shipped with the product. For more details, see “Setting specific
environment variables” on page 24.

Online documentation
Information for WebSphere MQ Integrator is provided in the WMQI-DOCS
package. You can view this information online using the Adobe Acrobat
| Reader, or Acrobat Reader with Search, application. Each information unit is
supplied, in US English, in Portable Document Format (PDF). A searchable
library in PDF, which provides a cross-book index and search facility, is also
provided.

You can access the documentation without installing the product. The books
are in the wmqi_documentation subdirectory in the root directory of the
Supplemental CD.

PDF files for books in other national languages are also available. For details,
see the “Bibliography” on page 95.

To read the documentation on HP-UX:

1. Install the Online documentation component.
2. Start Acrobat Reader.
3. Move to the /panels subdirectory.
4. Open the file bipabhpx.pdf.

You can download a free copy of Acrobat Reader, or Acrobat Reader with
Search, from the Adobe Web site at:
http://www.adobe.com

This component can be installed on any system, including one that has no
other WebSphere MQ Integrator component installed. For example, you can
choose to install one copy of the documentation on a central LAN server for
all users to share.

For details of all publications supplied, see the “Bibliography” on page 95.

New Era of Networks (NNSY) Interface

This option installs the New Era of Networks interface code that enables you
to run message flows that use New Era of Networks rules and formats.

12 WebSphere MQ Integrator for HP-UX Installation Guide

 Product components

Before you can use the New Era of Networks rules and formats, you need to
separately install the New Era of Networks components. Use the swinstall
command to install the components from the NNSY/nnsy directory on the
WebSphere MQ Integrator for HP-UX CD.

NLS message catalogs

These options install message catalogs in the following national languages:
v WMQI-MC-De-DE
v WMQI-MC-Es-ES
v WMQI-MC-Fr-FR
v WMQI-MC-It-IT
v WMQI-MC-Ja-JP
v WMQI-MC-Ko-KR
v WMQI-MC-Pt-BR
v WMQI-MC-Zh-TW
v WMQI-MC-Zh-CN
If you do not install the message catalog for your national language, the
messages will default to US English.

Security considerations
Security control of WebSphere MQ Integrator components, resources, and
tasks depends on the definition of users and groups of users (principals) to the
security subsystem of the operating system. WebSphere MQ Integrator always
creates a group mqbrkrs on the system on which it is installed.

Users require the appropriate authority to access MQSeries resources (queues

and queue managers) and databases used by the broker. HP-UX users require
the appropriate authority to access MQSeries resources on HP-UX, and on any
remote queue managers, for example the Configuration Manager on Windows
NT.

The following table provides a summary of authorizations in the UNIX

environment.
Table 3. Summary of authorization in the UNIX environments
User is... UNIX domain
Creating broker, User Name Server v Member of mqbrkrs and mqm.
v In most situations, the Broker or User Name Server
runs under the login ID used to issue the create
command. When root is used to issue the create
command, it can nominate any user to run the Broker
or User Name Server.

Chapter 2. Planning for installation 13

Security and principals

Table 3. Summary of authorization in the UNIX environments (continued)

User is... UNIX domain
Installing Superuser.
Uninstalling Superuser.
Changing broker, User Name Server Member of mqbrkrs.
Deleting broker, User Name Server Member of mqbrkrs and mqm.
Starting broker, User Name Server v Member of mqbrkrs.
v Member of mqm.
v Service user ID¹.
Stopping broker, User Name Server v Member of mqbrkrs.
v Member of mqm if –q is specified
v Service user ID¹.
Listing broker, User Name Server Member of mqbrkrs.
Changing, displaying, retrieving trace Member of mqbrkrs.
information
Running User Name Server (login ID) Member of mqbrkrs. The broker or User Name Server
runs under the login ID specified in the create command.
Running broker (MQSeries non-trusted Member of mqbrkrs. The broker or User Name Server
application) (login ID) runs under the login ID specified in the create command.
Running broker (MQSeries trusted v login ID must be mqm.
application) (login ID) v mqm must be a member of mqbrkrs.
Clearing, joining, listing MQSeries Member of mqbrkrs.
publish/subscribe brokers
Running publish/subscribe applications Any user, subject to WebSphere MQ Integrator topic and
MQSeries queue access control.
Warning:
1. When the service user ID is root, all libraries loaded by the broker, including all user-written
plug-in libraries and all shared libraries that they might access, also have root access to all system
resources (for example, filesets). You must review and assess the risk involved in granting this level
of authorization.

You need to assign users (or other groups) to the local groups to enable them
to perform specific tasks.

You can find more comprehensive information in the WebSphere MQ Integrator

Administration Guide. For a more general discussion on security for WebSphere
MQ Integrator, see WebSphere MQ Integrator Introduction and Planning.

14 WebSphere MQ Integrator for HP-UX Installation Guide

 Security and principals

Migration considerations
For guidance on planning subsequent migration or integration of brokers, see
WebSphere MQ Integrator Introduction and Planning. For details of actions to
take for integration and migration, see the WebSphere MQ Integrator
Administration Guide.

Preparing for installation

This section describes the steps to take before you install WebSphere MQ
Integrator for HP-UX.
Before you start
Notes:
1. The WebSphere MQ Integrator for HP-UX files are installed in the
directory mqsi. When you create and mount a file system (see step 9
below), or if you create an alternative file system for the product code (see
“Creating a file system for the product code” on page 17), you must use
the directory name mqsi. References elsewhere to the directories /opt/wmqi,
and /var/wmqi are valid, since symbolic links exist.
2. For standalone machines, create the new user and group IDs locally. For
machines administered in a Network Information Services (NIS) domain,
create the user and group IDs on the NIS master server.
3. User IDs for WebSphere MQ Integrator installers and users can be
members of NIS or local groups. The user ID and home directory for a
user for whom a DB2 instance is created must be local to the machine
containing DB2.

Before you install WebSphere MQ Integrator for HP-UX:

1. Review the readme.txt file provided in the root directory of the product
CD.
2. Use SAM (System Administration Manager) to create a user group with
the name mqbrkrs:
a. Select Accounts for Users and Groups.
b. Select Groups.
c. Select Add from the Actions tab.
d. Enter the name mqbrkrs in the Group Name field.
3. Use SAM to add root to the mqbrkrs group:
a. Select the root ID from the list called Users to Include in group
(optional).
b. Click OK.
mqbrkrs is shown in the Groups list, and root is shown as a user of
mqbrkrs.

Chapter 2. Planning for installation 15

Preparing for installation

4. The user ID that will be used to create to create a broker, and a User
Name Server, must be a member of the groups mqbrkrs and mqm. You can
use an existing user ID, or use SAM to create a new user ID as follows:

Note: Do not create a new user ID with the same name as your computer,
otherwise the following error occurs:BIP8026 Unable to start the
component.
a. Select Accounts for Users and Groups.
b. Select Users.
c. Select Add from the Actions menu.
d. Enter a name for the user ID, for example wmqi in the Login Name
field.
e. Select Create a home directory, and enter a path for your home
directory, for example /home/wmqi.
f. Check that the Primary group field is set to users.
g. Optionally, enter a description for the user in the Real Name field, for
example WebSphere MQ Integrator user.
h. Click OK to create the new user ID.
To check that the user ID has been created, log in as the new user, for
example:
su - wmqi

Use the command pwd to display the name of the home directory.
5. Use SAM to grant permissions to the user ID:
a. Select Accounts for Users and Groups.
b. Select Groups.
c. Select the group mqbrkrs.
d. Select Actions —> Modify
e. Select the user ID, for example wmqi from the list called Users not in
group, and then select Add to move the user ID to the list called Users
in group.
f. Click OK. The user ID is displayed in the mqbrkrs list.
Repeat this procedure to add the user ID to the group mqm.
6. Run the sample profile profile.hpux. See “Setting specific environment
variables” on page 24 for more information.
7. Check that you can access MQSeries and database resources, see “Security
considerations” on page 13 for more information.
8. Review the kernel configuration for your computer. See “Checking the
kernel configuration” on page 17 for the recommended settings.
9. Create or mount a /var/mqsi file system.

16 WebSphere MQ Integrator for HP-UX Installation Guide

 Preparing for installation

Resource ownership
| After installation, the user ID mqm, in group mqbrkrs, owns all directories in
| /var/wmqi. All files and executables beneath /opt/wmqi are owned by user ID
| bin, in group bin.

If you want to run any administration commands, for example,

mqsicreatebroker (create broker) or mqsistart (start WebSphere MQ Integrator
component), ensure that your user ID is a member of group mqbrkrs.

Creating a file system for the product code

| If there is insufficient storage space in the /opt/wmqi file system for the
| product code (which requires at least 100 MB of disk space), you might want
| to create an alternative file system.

| You can create a new file system and mount it as /opt/wmqi. Alternatively,
| you can create a new directory anywhere on your machine that has sufficient
| space to contain the product, and then create a symbolic link from /opt/wmqi
| to the new directory. For example:
| mkdir /bigdisk/wmqi
| ln -s /bigdisk/wmqi /opt/wmqi

| You can install the code in a file system on a remote network device, for
| example NFS. In this case, you need to define the mount options to grant root
| access, and enable the device to run setuid programs.

You should create a new file system before you install the product code.

Checking the kernel configuration

Before you install WebSphere MQ Integrator, compare the kernel configuration
of your machine with the following minimum recommended values:

Chapter 2. Planning for installation 17

Preparing for installation

maxdsiz 0x40000000
maxssiz 0x08000000
max_thread_proc 64
maxusers 32
msgmap 258 (msgtql +2)
msgmax 4096
msgmnb 4096
msgmni 50
msgseg 1024
msgssz tbs
msgtql 256
sema 1
semaem 16384
semmni 1024 (semmni<semmns)
semmap 1026 (semmni +2)
semmns 16384
semmnu 2048
semume 256
semvmx 32767
shmmax 4194304
shmem 1
shmmni 1024
shmseg 1024

Figure 1. Recommended kernel parameter values

To obtain the latest recommended minimum kernel settings, check the

readme.txt file supplied on the product CD, and then follow the guidelines
below:
1. Check the recommended values for the following products:
v WebSphere MQ Integrator
v MQSeries Version 5.2 (refer to the WebSphere MQ for HP-UX Quick
Beginnings, GC33-1869).
v DB2 (if installed)
v Any other software that you are running, that provides a recommended
value
2. Take the highest value for each parameter and compare each one to the
corresponding value in the kernel configuration for your machine.
3. If the highest recommended value is less than the current kernel setting on
your machine, leave the value on your machine unchanged.
4. If the highest recommended value is greater than the current kernel setting
on your machine, replace the value on your machine with the higher
recommended value.

Use the SAM administration tool to change the kernel parameters:

1. Select Kernel Configuration.
2. Select Configurable parameters.

18 WebSphere MQ Integrator for HP-UX Installation Guide

 Preparing for installation

3. Make changes to the kernel parameters.

4. Select Actions —> Process New Kernel.

You also need to increase the maximum number of concurrent open file
descriptors on your system to a value greater than 256. To do this, use the
ulimit -a command in the shell from where you start the broker.

Now reboot your system for these changes to take effect.

Methods for installing the product

You can install WebSphere MQ Integrator in the following ways:
v Directly from the product CD. This is the most common method of
installing this product, and the steps are described in “Installing WebSphere
MQ Integrator for HP-UX” on page 23.
v From a server machine. This method is described in “Performing a remote
installation” on page 25.
v In an unattended (or silent) installation. This is described in “Performing a
silent installation” on page 26.

Checking for installation prerequisites

WebSphere MQ Integrator for HP-UX installation checks that prerequisite
software is isntalled. If a prerequisite product is missing, its details are
displayed in a dialog box. You can cancel the installation at this point, and
install the prerequisite from the appropriate CD.

You are advised to check the full details of prerequisites for each component
given in “Software requirements” on page 4.

Chapter 2. Planning for installation 19

Preparing for installation

20 WebSphere MQ Integrator for HP-UX Installation Guide

Chapter 3. Installing WebSphere MQ Integrator
This chapter tells you how to install WebSphere MQ Integrator for HP-UX.

It covers the following:

v “Installation procedure”
v “Performing a remote installation” on page 25
v “Performing a silent installation” on page 26
v “What to do if something goes wrong during installation” on page 27

Installation procedure
This section describes the installation of WebSphere MQ Integrator for HP-UX
Version 2.1.

© Copyright IBM Corp. 2000, 2002 21

Installation procedure

MQSeries
Action Notes

MQSeries Install MQSeries V5.2 from the root For the default installation, use the
N directory of the MQSeries CD supplied. default install options (additional
V5.2 installed
(package name: mqm) options may be added, if required).

Install MQSeries Java Client from This is required for running the
Java Client N the root directory of the MQSeries samples. You only need to add it,
installed Supplementary CD supplied. if you did not select it on previous
(package name: ma88) install or have removed it.

WebSphere
MQ Integrator
Databases

A
compatible N Use existing N Install DB2 from the DB2 directory See documentation for detail of all
database is already (own) DB on the DB2 CD supplied. DB2 packages.
installed

Y Y
If not already installed,
Follow the instructions shipped
install a WebSphere MQ Integrator
with your database
compatible database

Warning: A compatible database must be

WebSphere installed before WebSphere MQ Integrator
MQ Integrator can be used. If you don't have your own,
it is recommended that you use the supplied
version of IBM DB2 for HP-UX.

New Era Install New Era of Networks Support

of Networks Y from the NNSY directory
Support
on the product CD
required

N
Install WebSphere MQ Integrator Install WebSphere MQ Integrator for HP-UX.
from the root directory on the See documentation for details of all
WebSphere MQ Integrator CD supplied. WebSphere MQ Integrator packages.

WebSphere
MQ Integrator Note: All paths are relative to the root of the appropriate CD
installed

Figure 2. Installing WebSphere MQ Integrator for HP-UX

Note: If you require New Era of Networks Rules and Formatter Support for
WebSphere MQ Integrator, you are recommended to install it before
installing WebSphere MQ Integrator for HP-UX. See “Installing New
Era of Networks Rules and Formatter Support for WebSphere MQ
Integrator” on page 23.
Mounting WebSphere MQ Integrator for HP-UX CDs
The WebSphere MQ Integrator for HP-UX CDs have the format ISO 9660,
with Rockridge extensions enabled. If volume management software is in use,
the CD mounts automatically when you insert it into the CD-ROM drive.
Alternatively, you can mount the CD as follows:

22 WebSphere MQ Integrator for HP-UX Installation Guide

 Installation procedure

Note: If the WebSphere MQ Integrator for HP-UX CD is mounted incorrectly,

some of the files cannot be read. This causes the installation to fail with
corrupt directory errors. It is important that you check that the CD is
mounted with Rockridge extensions enabled.
1. Log on as root.
2. Create a CD-ROM mount point directory that is accessible to all users, for
example:
mkdir /cdrom
chmod 777 /cdrom
3. Mount the CD-ROM drive on the mount point directory. To use the
pfs_mount command, NFS must be running:
/usr/sbin/pfs_mountd &
/usr/sbin/pfsd &
/usr/sbin/pfs_mount -t rrip -x unix /dev/dsk/<cdrom device> /cdrom

where <cdrom device> is the CD-ROM location, for example c5t4d0.

The CD is now readable.

Installing New Era of Networks Rules and Formatter Support for
WebSphere MQ Integrator
To install New Era of Networks Rules and Formatter Support depot, use SAM
in the NNSY directory on the main product CD, specifying nnsy as the depot.

Alternatively, run the following command:

swinstall -s /<cdrom>/NNSY/nnsy

where <cdrom> is the location of the root of your CD-ROM drive.

| The New Era of Networks Rules and Formatter Support components are
| installed in the -/opt/nnsy directory.
Installing WebSphere MQ Integrator for HP-UX
To install WebSphere MQ Integrator for HP-UX:
1. Log in as root.
2. Insert the product CD in the CD-ROM drive.
3. Enter the following command from the root directory of the CD to display
the product license agreement:
mqsilicense [-text_only]

where -text_only displays the license agreement in text mode.

4. Select the appropriate number for your language.

Chapter 3. Installing WebSphere MQ Integrator 23

Installation procedure

5. Read the license agreement, then press 1 to accept it, or 2 to decline it. You
cannot continue with the installation until you have read and accepted the
license agreement.
You can find the license agreement in the License directory on the product
CD, and in the <install_dir>/License directory after you have installed
the product.
6. Use SAM to install WebSphere MQ Integrator:
a. Enter the command:
swinstall -s /cdrom
b. Select either WMQI, or WMQI-DOCS.
c. Select Mark for Install from the Actions menu. Actions —> Modify
d. Select Actions —> Install to install your chosen package.

The installation program checks that:

v The prerequisite MQSeries for HP-UX, V5.2 has been installed.
v A user called mqm, and two groups called mqm, and mqbrkrs have been
created.
If these items are not found, the installation program displays a warning
dialog. You are recommended to cancel the installation, and then make the
required changes before starting the installation program again. Alternatively,
you can continue with the installation, but you must make the required
changes before you can use WebSphere MQ Integrator.
Installing DB2
To install DB2:
1. Mount the DB2 for HP-UX 7.1 CD with Rockridge extensions, as described
in “Mounting WebSphere MQ Integrator for HP-UX CDs” on page 22.
2. Run the db2install script on the DB2 for HP-UX 7.1 CD.
3. Run db2setup from <db2_root>install, where <db2_root> is the home
directory for DB2. The default is /opt/IBMdb2/V72
Setting specific environment variables
A profile file is supplied with the product to set the environment variables
that are required by WebSphere MQ Integrator. The path and filename of the
profile is
/opt/WMQI/sample/profiles/profile.hpux

Check the readme file readme.txt to ensure you have the latest version of the
profile.

You need to run this profile before attempting to use WebSphere MQ

Integrator. To ensure that these environment variables are set correctly each

24 WebSphere MQ Integrator for HP-UX Installation Guide

 Installation procedure

time you use WebSphere MQ Integrator, add the following line to your
profile, and to the profile of every WebSphere MQ Integrator user:
. /opt/WMQI/sample/profiles/profile.hpux

Setting up a database
After installation, you need to set up a database to use with WebSphere MQ
Integrator. A command script called mqsi_setupdatabase is provided in the
/opt/wmqi/bin directory to help you do this. The command requires two
parameters: a valid database type, and the home directory of a database. For
example, the command to set up DB2 Version 7.1 for use with WebSphere MQ
Integrator is:
mqsi_setupdatabase db2 /opt/IBMdb2/V7.1

where db2 is the database type and /opt/IBMdb2/V7.1 is the directory in which
DB2 is installed.

The following error message is displayed if the product is installed in a

mounted directory:
<libraries> not found in lib directory of <database home directory>
but links created anyway

In this case, the links created cannot be added to the package database. You
need to remove them manually from /var/wmqi/lib.

For further information about setting up a DB2 database, see Chapter 4,

“Configuring a broker domain” on page 29, for setting up an Oracle database
see Appendix B, “Setting up an Oracle8 broker database on WebSphere MQ
Integrator” on page 73, and for setting up a Sybase database, see the
WebSphere MQ Integrator Administration Guide and Sybase documentation.

Performing a remote installation

Setting up the server machine
Carry out the following on the server machine:
1. Create a directory on the server to store the installation files. For example:
mkdir /instwmqi
2. Copy the complete contents of the CD to the new directory. For example:
cp -rf /cdrom/wmqi_hpux/. /instwmqi
3. Give all licensed users access to the directory that now contains the CD
image.
4. Make the directory shareable using the exportfs command. The example
below gives all users read-only access using NFS:
exportfs -i -o ro /instwmqi
exportfs -a

Chapter 3. Installing WebSphere MQ Integrator 25

Installing from a server

Setting up the target machine

Carry out the following on the target machine:
1. Create a new directory to mount the shared directory. For example:
mkdir /remotewmqiimage

where remotewmqiimage is the name of the new directory.

2. At the command prompt, connect to the new directory using the mount
command:
mount <machine name>:/instwmqi /remotewmqiimage

where <machine name> is the name of the target machine.

3. Change to the remote image directory, for example remotewmqiimage.
4. Enter ./mqsilicense [-text_only] to display the product license
agreement, where -text_only optionally displays the license agreement in
text mode. By default, the license agreement is displayed in a graphical
user interface.
5. Select the appropriate number for your language.
6. Read the license agreement, then press 1 to accept it, or 2 to decline it. You
cannot continue with the installation until you have read and accepted the
license agreement.
7. Enter:
swinstall -s <remotewmqiimage> WMQI
8. Press Enter and follow the installation prompts.

Next, you might need to install DB2 as described in “Installing DB2” on

page 24, and you do need to set up the environment variables as described in
“Setting specific environment variables” on page 24.

Performing a silent installation

WebSphere MQ Integrator supports silent installation, where no user
interaction is expected. This method of installation is typically used where
you have to install many identical copies of the same software across many
machines. These machines can be remote to the installer.
Accepting the licence agreement
Each time you perform a silent installation, you must first read the WebSphere
MQ Integrator license agreement in the License directory on the product CD,
and then become root, and run the following command in the root directory
of the product CD:
./mqsilicense -accept

where -accept indicates that you have read and accept the license agreement.

26 WebSphere MQ Integrator for HP-UX Installation Guide

 Silent installation

Setting up a silent installation

Run the swinstall command, and direct its output to null, for example:
swinstall -s /cdrom/ WMQI > /dev/null

Next, you might need to install DB2 as described in “Installing DB2” on

page 24, and you need to set up the environment variables as described in
“Setting specific environment variables” on page 24.

What to do if something goes wrong during installation

If any problems arise during installation, review the following sources of
information:
v The readme.txt file supplied on the product CD. This contains the latest
product information, and might contain last minute changes to the
installation instructions that you must follow. You might also find
additional information on the MQSeries Web site (the address is given in
“MQSeries information available on the Internet” on page 99).
v The WebSphere MQ Integrator Messages book to find out the cause of any
error message with the WebSphere MQ Integrator prefix BIP, and any
corrective action you should take.
v Product information in /var/adm/sw/products/WMQI.
v The syslog.log in /var/adm/syslog.

When you have identified and corrected the error run the installation program
again. If this does not work, follow the steps to uninstall the product as
described in the section “Uninstalling WebSphere MQ Integrator:” on page 77,
to ensure that your system is in a consistent state, and then run the
installation program again.

| If New Era of Networks Rules and Formatter Support installation has failed,
| check the New Era of Networks documentation to determine the cause of
| failure. Before manually installing the New Era of Networks Rules and
| Formatter Support component, you might need to create an operating system
| group called NNSYGRP that resides on the database server, and then create a
| user account that becomes the New Era of Networks Rules and Formatter
| Support database object owner, adding it to the NNSYGRP group. (The need to
| do this depends on how the New Era of Networks Rules and Formatter
| Support installation has failed.) To install New Era of Networks Rules and
| Formatter Support manually, run the setup.exe file specified in the
| autorun.inf file in the nnsy folder on the product CD.

If you have checked the various sources of information listed above, and you
cannot resolve the problem, contact your IBM Support Center. See “Contacting
your IBM Support Center” on page 81 for further information.

Chapter 3. Installing WebSphere MQ Integrator 27

Installation errors

28 WebSphere MQ Integrator for HP-UX Installation Guide

 Chapter 4. Configuring a broker domain
This chapter takes you through the tasks you need to complete after you have
installed WebSphere MQ Integrator on HP-UX and Windows NT, to set up the
minimum resources required in the broker domain.

The tasks are as follows:

1. “Reviewing the assumptions about this configuration” on page 34
2. “Setting up user IDs and groups” on page 36
3. “Creating and connecting to the databases” on page 37
4. “Setting up database authorizations” on page 40
5. “Customizing the database” on page 41
6. “Configuring your broker domain” on page 41
7. “Checking the components” on page 46
8. “Starting your broker domain” on page 46

These tasks are shown in Figure 3 on page 30. You might find it helpful to
review this figure before you start, and use it to check off the tasks as you
complete them. You need to complete all the steps in each task. The figures
shows the tasks required on HP-UX and Windows NT in a logical sequence.

| Throughout this chapter, a DB2 database is assumed. Please refer to WebSphere

| MQ Integrator Administration Guide for configuration details for other
| databases.

Note: Step-by-step instructions are given for Windows NT. The instructions
for Windows 2000 might be different. Refer to your Windows 2000
documentation for more information.

© Copyright IBM Corp. 2000, 2002 29

 Configure Default
Broker Domain for
HP-UX & Windows NT Notes & Commands

To create a new instance

Create Broker DB Open/use a HP-UX
Log on as root & type the following:
on HP-UX command window /opt/IBMdb2/V7.1/instance/
db2icrt -u <fence uid> <username>
. /<insthome>/sqllib/db2profile
db2 start database manager
db2 create database MQSIBKDB
db2 connect to MQSIBKDB
db2 bind /home/db2inst1/
sqllib/bnd/@db2cli.lst
grant public CLIPKG 5

Update ODBC initiation file:

Define ODBC connections Add broker database (/var/wmqi/odbc/.odbc.ini)
on HP-UX connection At the top of file add a definition for the
Database Name:
MQSIBKDB=IBM DB2 ODBC Driver
Edit or Add at end of file
Driver=<INSTHOME>/sqllib/
lib/libdb2.sl
Description=Broker Database
Database=MQSIBKDB
NB: You must replace <INSTHOME>
with the path to your DB2 Instance Directory

DB2 ID & Password - use the ones

Create two databases specified during DB2 install
Start DB2 Control Center
on Windows NT (ID <= 8 alphanumeric characters.)
default = db2admin

Create Configuration
name & alias = MQSICMDB
Repository DB

Create Message
Repository DB name & alias = MQSIMRDB

Figure 3. Configuring a basic broker domain (Part 1 of 4)

30 WebSphere MQ Integrator for HP-UX Installation Guide

 Define ODBC connections From ODBC on Windows Control
Invoke ODBC Settings
on Windows NT Panel (System DSN tab)

Add Message Repository and Create new data source -

Configuration Repository IBM DB2 ODBC driver +
connections use database name and alias

Setup Broker DB Authorizations Authorization is implicit for

on HP-UX the creator of the database

Setup DB Authorization Start or go to

on Windows NT (optional) DB2 Control Centre
Expand broker DB folder & click on
'Users & Groups' folder
Right click on DBUsers in left hand
pane and select 'Add'
Configuration Manager DB
Choose user ID previously specified
(mqsiuid).
Select the first four entries listed.
Click OK

Message Repository DB As above

> mqsicreateconfigmgr
-i mqsiuid
Create one Configuration Manager
Configure Broker Domain -a mqsipw
(Enter commands on command line
on Windows NT -q MQSI_CONFIG_QM
or use the Command Assistant)
-d MQSISYS -n MQSICMDB
-m MQSIMRDB

mqsicreatebroker
MQSI_SAMPLE_BROKER
Open/use a HP-UX -i mqsiuid
Create one Broker -a mqsipw
command window
-q MQSI_SAMPLE_QM
-n MQSIBKDB

Figure 3. Configuring a basic broker domain (Part 2 of 4)

Chapter 4. Configuring a broker domain 31

 Start Broker Domain for Start the Listener $ runmqlsr -t tcp -p 1415 -m
HP-UX & Windows NT on HP-UX MQSI_SAMPLE_QM

Start the Listener > runmqlsr -t tcp -p 1414 -m

on Windows NT MQSI_CONFIG_QM

Or use MQSeries Services tool to

create and start listener on port 1414

Define Channels on Enter commands on a runmqsc

HP-UX command line on HP-UX:

DEF QL('MQSI_CONFIG_QM') USAGE(XMITQ) REPLACE

DEF CHANNEL('BROKER.CONFIG') CHLTYPE(SDR) TRPTYPE(TCP) +
CONNAME(’config.machine.name(1414)’)
XMITQ('MQSI_CONFIG_QM') REPLACE
DEF CHANNEL('CONFIG.BROKER') CHLTYPE(RCVR) TRPTYPE(TCP)
REPLACE

Define Channels on Enter commands on a runmqsc

Windows NT command line on Windows NT:

DEF QL('MQSI_SAMPLE_QM') USAGE(XMITQ) REPLACE

DEF CHANNEL('CONFIG.BROKER') CHLTYPE(SDR) TRPTYPE(TCP) +
CONNAME(’broker.machine.name(1415)’)
XMITQ('MQSI_SAMPLE_QM') REPLACE
DEF CHANNEL('BROKER.CONFIG') CHLTYPE(RCVR) TRPTYPE(TCP)
Start Broker Domain for REPLACE
HP-UX & Windows NT
CONTINUED...

Figure 3. Configuring a basic broker domain (Part 3 of 4)

32 WebSphere MQ Integrator for HP-UX Installation Guide

 Start Broker Domain for $ runmqchl
Start Channels on -c BROKER.CONFIG
HP-UX & Windows NT
HP-UX -m MQSI_SAMPLE_QM
...CONTINUED

> runmqchl
Start Channels on -c CONFIG.BROKER
Windows NT -m MQSI_CONFIG_QM

Start Configuration Manager

> mqsistart ConfigMgr
on Windows NT

Start Broker on $ mqsistart

HP-UX MQSI_SAMPLE_BROKER

Hostname (MQSISYS1)
Initial Configuration on Port (1414)
Initialize the Control Center
Windows NT Queue Manager
(MQSI_CONFIG_QM)

Configuration Completed

Figure 3. Configuring a basic broker domain (Part 4 of 4)

Most of the configuration tasks are carried using WebSphere MQ Integrator

commands. You can use the WebSphere MQ Integrator Command Assistant
on both HP-UX and Windows NT. (You need to install the MQSeries Classes
for Java and set up the necessary environment variables (see “Setting specific
environment variables” on page 24) before you can use the Command
Assistant on HP-UX).

| Note: If you use the WebSphere MQ Integrator Command Assistant, you

| should be aware that this tool uses the IBM Runtime Environment For
| the Java Platform. Locale support for this tool is provided by the IBM
| Runtime Environment For the Java Platform, and not all locales are
| currently supported by the version of the IBM Runtime Environment
| For the Java Platform that is shipped with WebSphere MQ Integrator
| (specifically GB18030).
Alternatively, you can run the commands from the command line. The
commands are given in full in the text, so you can choose to use either
method where appropriate.

Chapter 4. Configuring a broker domain 33

 Full descriptions of the Command Assistant and the configuration commands
are given in the WebSphere MQ Integrator Administration Guide. It also describes
the actions required if any errors arise when you are completing the tasks in
this chapter.

Reviewing the assumptions about this configuration

Before you start to define any resources, you should review the assumptions
made about the configuration that is created. If you want to understand more
about WebSphere MQ Integrator configuration in general, refer to WebSphere
MQ Integrator Introduction and Planning.

The assumptions for this configuration include resource names and user IDs.
If you want to override any of the assumptions, make a note of changes you
want to make and apply those changes as you complete the tasks illustrated.
For example, the names used for the broker and its queue manager are for
illustration only. You are recommended to follow any existing naming
conventions you have for MQSeries (or any other) resources. See WebSphere
MQ Integrator Introduction and Planning for more information about defining a
naming convention.

This chapter assumes that:

v You have installed the Runtime component on HP-UX.
v You have installed the Configuration Manager and the Control Center
components on Windows NT.
v You have installed the product using the TCP/IP hostnames MQSISYS1 on
Windows NT and MQSISYS2 on HP-UX. You must replace these names
wherever they are used with the hostnames of your systems, if they are
different.
v The MQSeries ports 1414 and 1415 are available. If these ports are not
available, replace the port values with the ones you are using.
v The local systems MQSISYS1 and MQSISYS2 define the security domain
relevant to this configuration (that is, all users and groups are defined in
the local account security domain).

Note: This illustrates a very basic security scenario. You can find more
comprehensive security information in WebSphere MQ Integrator
Introduction and Planning, and more complex scenarios illustrated in
the WebSphere MQ Integrator Administration Guide.
v You are logged on with the user ID that you used to install WebSphere MQ
Integrator. Otherwise, ensure that your current logon ID is a member of the
following:
– The mqbrkrs group on HP-UX
– The Administrator group on Windows NT

34 WebSphere MQ Integrator for HP-UX Installation Guide

 Reviewing configuration assumptions

v You have authorized the user IDs to access HP-UX, and Windows NT as
follows:
– The service user ID for use on Windows NT (specified on the
mqsicreateconfigmgr command) is defined on the machine running the
HP-UX broker.
– The ServiceUserid for use on HP-UX (specified on the mqsicreatebroker
command) is defined on the machine running the Configuration
Manager.

In this example the service user ID is mqsiuid. If you are using an

alternative service user ID, define it on HP-UX and Windows NT. Refer to
the WebSphere MQ Integrator Administration Guide for more information
about setting up user IDs and groups.
v You have decided to create a new user ID, the ‘service user ID’ (mqsiuid).
This will be used as the user ID for running WebSphere MQ Integrator
services (the Configuration Manager and the broker) and accessing
WebSphere MQ Integrator databases.
In most cases, you cannot change user IDs after your configuration has
been set up, so you are advised to check where you use them very
carefully.
v The configuration consists of a broker, installed on HP-UX, and the
Configuration Manager, installed on Windows NT, communicating through
MQSeries.
v A set of sample names and other default values are used for WebSphere
MQ Integrator, MQSeries, and database resources. You can use the sample
names and defaults exactly as they are shown, or you can decide to use
your own names, to follow the naming conventions you have in place.
If you choose to use your own names, you must change the names and
default values to match your configuration, whenever they are used in the
tasks illustrated.
v You are using DB2 for all database requirements. If you installed DB2 when
you installed WebSphere MQ Integrator, you have since restarted your
system and verified your DB2 installation.

After you have verified your installation, and understood and implemented
the basic principles of operating your broker domain, you will probably need
a more complex MQSeries network for your broker domain. You might want
to include a User Name Server in your broker domain. As you distribute
WebSphere MQ Integrator components, you will need to set up users and
groups on HP-UX and Windows NT, and authorize them between systems.
For more detailed guidance and instructions, refer to the WebSphere MQ
Integrator Administration Guide.

Chapter 4. Configuring a broker domain 35

Setting up User IDs and groups

Setting up user IDs and groups

Setting up a user ID for the broker
If you are creating a new user ID for WebSphere MQ Integrator for HP-UX,
refer to “Before you start” on page 15.
Setting up a user ID and groups for the Configuration Manager
Creating a new user ID
If you want to create a new user ID for WebSphere MQ Integrator for
Windows NT, use the Windows NT User Manager to create the user
ID, and assign it to all the WebSphere MQ Integrator groups.
Using an existing user ID
If you want to use an existing user ID, use the Windows NT User
Manager to assign the user ID to the WebSphere MQ Integrator
groups.

For either a new, or existing user ID:

v Assign the appropriate authority for the user ID to run the Configuration
Manager on Windows NT.
v Ensure that the user ID is a member of the Windows NT group
Administrators. This provides the security level required by the MQSeries
operations carried out in this section.

The user ID referred to in this section is independent of the user ID that you
defined for the WebSphere MQ Integrator groups to run WebSphere MQ
Integrator components.

Take care to specify the correct user IDs wherever they are used in the
instructions in this chapter. You can define and use the sample user ID
referenced in this chapter, or you can use own user ID.

The steps below describe how to set up a new user ID:

1. Select Start —> Programs —>Administrative Tools —> User Manager.
2. Create a new user ID:
a. Select New user... from the User menu.
b. Complete the fields displayed to create the user ID mqsiuid, and
password mqsipw.
Note that the maximum length for the user ID field is 12 characters.
3. To add the new user ID to the mqbrkrs, Administrators, and mqm
groups:
a. Click Groups in the New User window. The Group Memberships window
is displayed.

36 WebSphere MQ Integrator for HP-UX Installation Guide

 Setting up User IDs and groups

b. Add the new user to the WebSphere MQ Integrator group mqbrkrs, to

the Windows NT group Administrators, and to the MQSeries group .
c. Click OK to return to the New User window.
d. Click OK.
4. To add your logon ID to the mqbrasgn, mqbrdevt, mqbrops, and
mqbrtpic groups:
a. Double-click your current user ID to display the User properties
window.
b. Click the Groups button to display the Group Memberships window.
c. Add the new user to mqbrasgn, mqbrdevt, mqbrops, and mqbrtpic.
d. Click OK.
5. Close the User Manager.

Creating and connecting to the databases

This section describes how to create, and connect to, the databases on HP-UX,
and Windows NT.
Creating and connecting to the database on HP-UX
1. If DB2 was installed already on your machine before you installed
WebSphere MQ Integrator, a default DB2 instance is probably defined
already. You are recommended to use this. However, if an instance has not
been defined (for example, because you installed DB2 when you installed
the product), or if you want to create a separate instance, log on as root
and enter the following command to create a DB2 instance:
/opt/IBMdb2/V7.1/instance/db2icrt -u <fence user ID> <username>

The DB2 instance is created with the name you specify in <username>.

Note: If you create a separate instance, the InstanceName must match an

existing user ID. You need to create a user ID if one does not exist
already. The user ID and the user’s home directory should be local
to the machine containing DB2, and should not be NIS or NFS
mounted.
2. Log on as the user specified when you created the DB2 instance
(<username>). (If you use the su command to switch user from root, ensure
that the user profile is run by specifying su - <username>.) Perform the
following commands, where <insthome> is the DB2 instance home
directory (for example home/db2inst1):
a. Run the DB2 profile for <username>:
. /<insthome></sqllib/db2profile

Chapter 4. Configuring a broker domain 37

Creating and connecting to databases

You need to run this profile to set the DB2 environment. To ensure that
the environment is set correctly each time you use DB2, add the
following line to your profile, as described in “Setting specific
environment variables” on page 24:

/u/<username>/sqllib/db2profile
b. Start the database manager:
db2 start database manager
c. Create a database called MQSIBKDB:
db2 create database MQSIBKDB
d. Connect to the database:
db2 connect to MQSIBKDB
e. Bind the db2cli package to the database:
db2 bind <insthome>/sqllib/bnd/@db2cli.lst grant public CLIPKG 5
3. To enable WebSphere MQ Integrator brokers to use the database, you need
to add the database definitions to the ODBC initiation file
/var/wmqi/odbc/.odbc.ini, supplied with the product.
Notes:
a. To trace ODBC errors, replace Trace=0 with Trace=1in the file
/var/wmqi/odbc/.odbc.ini
b. Ensure that the user ID that runs WebSphere MQ Integrator has write
access to the file /var/wmqi/odbc/.odbc.ini.
Edit the file /var/wmqi/odbc/.odbc.ini as follows:
a. At the start of the file add a definition for the Database Name:
MQSIBKDB=IBM DB2 ODBC Driver
b. At the end of the file, edit or add the following lines, replacing
<INSTHOME> with the path for your DB2 Instance directory:
Driver=<INSTHOME>/sqllib/lib/libdb2.sl
Description=Broker Database
Database=MQSIBKDB

If you are using Oracle8 to support the broker, see Appendix B, “Setting up an
Oracle8 broker database on WebSphere MQ Integrator” on page 73.
Creating and connecting to databases on Windows NT
You are recommended to create two databases for the Configuration Manager
on Windows NT as follows:
v A configuration repository for storing configuration data.
This chapter uses MQSICMDB for both the name and the alias. If you
choose a different name, remember to specify it in all the steps that refer to
this database.
v A message repository for storing message definition.

38 WebSphere MQ Integrator for HP-UX Installation Guide

 Creating and connecting to databases

This chapter uses MQSIMRDB for both the name and the alias. If you
choose a different name, remember to specify it in all the steps that refer to
this database.

Alternatively, you can create a single database to hold both repositories. You
should ensure that you use the correct database name wherever you need to
specify a database.

Creating a database using the DB2 Control Center

You can use the DB2 Control Center to create the databases, as described in
this section.

Alternatively, you can use the DB2 command line. After you have created the
databases, you need to bind the db2cli package to the configuration-manager
database using the following commands:
db2 connect to MQSICMDB
db2bind c:\sqllib\bnd\@db2cli.1st blocking all grant public
db2 connect reset

where c:\ is the drive on which you installed DB2.

1. Start the DB2 Control Center from the Start menu (Start —> Programs —>
DB2 for Windows NT —> Control Center).

Note: If you are using DB2 Version 6.1, you are prompted to enter a user
ID and password. Enter the DB2 Administrator ID you specified
when you installed DB2. The default is db2admin. Enter the
password for the DB2 Administrator ID.
2. Expand the Object tree in the DB2 Control Center until you find Databases
(if you are using Version 7.1, expand Instance DB2 to find the right
location). Right-click Databases, and select Create —> Database using Wizard
(...using SmartGuide in Version 6.1). Enter the name and alias of the
database. DB2 database names are limited to eight characters.
3. Create the database or databases you require and then click Done.

When you have completed these steps for every database, click OK. A
message confirming successful completion of the create command is displayed
at the bottom of the window.

Defining an ODBC connection

If you have created two databases, only the message repository requires an
ODBC connection. If you have created a single database for both repositories,
the single database requires an ODBC connection.

To define an ODBC connection:

Chapter 4. Configuring a broker domain 39

Creating and connecting to databases

1. From the Windows NT Start menu, select Start —> Settings —>
Control Panel.
2. Select the ODBC icon (either ODBC or ODBC Datasources).
3. Select the System DSN tab.
4. Select the Add button. The Create New Data Source window appears.
5. Select IBM DB2 ODBC DRIVER.
6. Choose the data source (database) name from the list displayed.
7. Click OK.

Setting up database authorizations

On HP-UX
You do not need to setup broker database authorizations on HP-UX
because authorization is implicit for the creator of the database.
On Windows NT
You need to authorize selected user IDs to access the database (or
databases) you have created, to enable the WebSphere MQ Integrator
resources to operate successfully. You can omit these steps if you
specified your DB2 administrator ID and password for the datasource
and database IDs and passwords in the Configuration Manager
command. This option is not illustrated here. See the WebSphere MQ
Integrator Administration Guide for further information.
To authorize access to the database follow the steps below. If you
need further guidance, use the online help facility for the DB2 Control
Center.
1. Start the DB2 Control Center, if it is not already active. Log on
with the DB2 administrator user ID you used in “Creating and
connecting to the databases” on page 37.
2. Complete the following:
a. Expand the object tree until you find the database.
b. Expand the tree under this database and click the User and
Group Objects folder. The DB Users and DB Groups folders are
displayed in the right pane.
c. Right-click the DB Users folder in the right pane and select Add
from the popup menu. The Add User notebook opens.
d. Select the ID you are using for WebSphere MQ Integrator
database access (for example db2admin) from the dropdown list.
Select the appropriate options in the box labelled Choose the
appropriate authorities to grant to the selected user for all the
databases you have created for WebSphere MQ Integrator.

40 WebSphere MQ Integrator for HP-UX Installation Guide

 Setting up database authorizations

The ID you specify as the ServiceUserID on the create

commands, mqsiuid (or the user ID you are using in place of
this sample ID), must have the following authority to the
database you created for WebSphere MQ Integrator:
v Connect database
v Create tables
v Create packages
v Register functions to execute in database manager’s process
e. Click OK. The authority or authorities are granted. The dialog
is closed.
3. Close the DB2 Control Center.

Customizing the database

If you are using DB2 Version 7.1, you are recommended to increase the
database heap size from the default value (typically 600) to at least 900 (4 KB)
pages.
On HP-UX
1. Stop the database
2. Using the DB2 command line, for example, enter:
UPDATE DATABASE CONFIGURATION FOR MQSIBKDB USING DBHEAP 900
3. Restart the database to make the new value take effect.
On Windows NT
Use the DB2 Control Center
1. Expand the object tree until you find the database.
2. Right click on the database name.
3. From the popup menu, select Configure—>Performance—>Database
heap size.
Select a minimum value of 900.

Configuring your broker domain

Now you are ready to define the components that make up the basic
configuration. In this section you will:
1. Create a Configuration Manager on Windows NT.
2. Create a broker on HP-UX.

The steps you need to carry out on Windows NT are described using the
Command Assistant. When you enter values in the entry fields, the command
that is generated is displayed on the lower part of the screen.

Chapter 4. Configuring a broker domain 41

Configuring a broker domain

The WebSphere MQ Integrator commands are given for both platforms. On

HP-UX, enter the commands at the command line. On Windows NT, enter the
commands at a command prompt window. You are recommended to enter the
commands from the \bin subdirectory of the directory in which you installed
WebSphere MQ Integrator for Windows NT and Windows 2000 (the home
directory). If you accepted the default, the home directory is:
C:\Program Files\IBM\WebSphere MQ Integrator 2.1

Creating a Configuration Manager on Windows NT

To use the Command Assistant to create the Configuration Manager:
1. Select Start—> Programs —> IBM WebSphere MQ Integrator 2.1 —>
Command Assistant —> Create Configuration Manager.
2. Complete the Service User ID field (mqsiuid), the Service Password field
(mqsipw), and the Queue Manager Name field (MQSI_CONFIG_QM).
Check that the values are correct and click Next.
3. Complete the ConfigMgr Name field (MQSICMDB) and the MRM OBDC
Data Source Name field (MQSIMRDB). Check that the values are correct
and click Next.
4. Check that the command is correct and click Finish.

Alternatively, you can enter the command directly, for example:

mqsicreateconfigmgr -i mqsiuid -a mqsipw -q MQSI_CONFIG_QM
-d MQSISYS1 -n MQSICMDB -m MQSIMRDB

where:
v -q is the queue manager that hosts the Configuration Manager
v -i is the service user ID for running the Configuration Manager (as a
Windows NT service)
v -a is the password for the service user ID
v -d is the security domain within which user authority is checked (in this
case, the local account security domain defined by the hostname of the
system)
v -n is the database for the configuration repository
v -m is the datasource name for the message repository
The queue manager is created if it does not already exist.

The service user ID and password are also used to access the configuration
and message repositories. If you are using a different user ID and password,
remember to use them as the parameters for flags -u, and -p for the
configuration repository, and flags -e and -r for the message repository.

42 WebSphere MQ Integrator for HP-UX Installation Guide

 Configuring a broker domain

The command line displays the password exactly as you type it. For security
reasons, the Command Assistant, and the Windows NT registry display the
password as asterisks.

If you are not using the sample names or values for your configuration,
remember to replace them with your own names and values in this command.

The command might take a short while to complete. The command generates
the following expected responses, unless you are using the Command
Assistant:
MQSeries queue manager created.
Creating or replacing default objects for MQSI_CONFIG_QM.
Default objects statistics : 29 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
MQSeries queue manager MQSI_CONFIG_QM’ started.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

Note: Only the message is shown in the log.

If the command detects any errors, or is unable to complete, it returns an

error message on the command line, or in the Windows NT Event viewer
(Application View), which provides an explanation and describes the action to
take. The error might have been caused by another component with which
WebSphere MQ Integrator interacts (Windows NT, DB2 or MQSeries). You
should also check for errors from these products.

On completion:
v The Configuration Manager has been created, and the Windows NT service
for it added to the Services (viewable from the Windows NT Control Panel).

Chapter 4. Configuring a broker domain 43

Configuring a broker domain

The service is called IBM MQSeries Broker ConfigMgr. It has a default startup
status of manual: you can change this to automatic if required.
v The queue manager MQSI_CONFIG_QM has been created and started. You
can check the existence and status of this queue manager using MQSeries
Services from the Start menu (Start —> Programs—> IBM MQSeries —>
MQSeries Services).
v The MQSeries resources required by the Configuration Manager have been
defined on the queue manager. These resources are detailed in “Default
MQSeries resources” on page 71.
v The authorizations required by the Configuration Manager to access
MQSeries resources have been set (the setmqaut messages seen in the
responses to the command).
v The database tables required by the configuration repository have been set
up in the database MQSICMDB.
v The database tables required by the message repository have been set up in
the database MQSIMRDB.
v The Windows NT registry has been updated to record the Configuration
Manager creation.
Configuring the syslog on HP-UX
Since all WebSphere MQ Integrator messages (other than those generated by
the command line utilities) are sent to syslog, it is useful to re-direct ‘user’
messages to a separate file. Before you create a broker on HP-UX, carry out
the following steps to configure syslog to re-direct user messages to a file
called user.log:
1. Log on as root.
2. Enter the following commands to create a file to store user facility
messages called user.log:
touch /var/adm/user.log
chown root:mqbrkrs /var/adm/user.log
chmod 750 /var/adm/user.log
3. Add the following line to the file /etc/syslog.conf to re-direct debug
level messages to the file user.log:
user.debug /var/adm/user.log

You can add similar lines to direct information, warning and error
messages to user.log.
4. Run the following command to restart the syslog daemon:
refresh -s syslogd

Creating a broker on HP-UX

1. Log on as your log on user ID (if you use the su command to switch user
from root, ensure that your user profile is run by specifying su -<user
ID>).

44 WebSphere MQ Integrator for HP-UX Installation Guide

 Creating a broker

2. Add the directory /opt/wmqi/merant/lib to the LIBPATH as follows:

set LIBPATH=/opt/wmqi/merant/lib:$LIBPATH
export LIBPATH
3. Enter the following command (all on one line) to create a broker:
mqsicreatebroker MQSI_SAMPLE_BROKER -i mqsiuid -a mqsipw
-q MQSI_SAMPLE_QM -n MQSIBKDB -u <database user ID>
-p <database password>

where:
MQSI_SAMPLE_BROKER
is the broker
-q is the broker’s queue manager
-n is the database that has been created for the broker tables
-i is the service user ID for the broker
-a is the password for the broker
-u is the user ID associated with the database. This is the user ID that
was used to create the database instance, see “Creating and
connecting to the databases” on page 37.
-p is the password associated with the database. This is the password
that was used to create the database instance, see “Creating and
connecting to the databases” on page 37.

When you enter the password on the command line, it appears on the screen
exactly as you type it.

If you are not using the sample names and values for any parameter in this
command, remember to replace them with your own names and values.

The command might take a short while to complete. A successful response is

shown below:
MQSeries queue manager created.
Creating or replacing default objects for MQSI_SAMPLE_QM.
Default objects statistics : 29 created. 0 replaced. 0 failed.
Completing setup.
Setup completed.
MQSeries queue manager ’MQSI_SAMPLE_QM’ started.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
The setmqaut command completed successfully.
BIP8071I: Successful command completion.

Chapter 4. Configuring a broker domain 45

Creating a broker

If the command detects an error, or cannot complete, an error message is

displayed on the command line, or in the syslog. The error message contains a
description of the problem, and any action required. You should also check for
errors from DB2, or MQSeries, since an error might be caused by another
component with which WebSphere MQ Integrator interacts.

When the command is successful:

v A broker called MQSI_SAMPLE_BROKER is created.
v The queue manager MQSI_SAMPLE_QM is created, and then started.
v MQSeries resources required by the broker are defined (see “Default
MQSeries resources” on page 71).
v Required authorizations for MQSeries resources are set (see the setmqaut
messages displayed when the command is run).
v The database tables required by the broker are set up in the database
MQSIBKDB. These tables are listed in Table 6 on page 70.

Checking the components

You can check the existence of the WebSphere MQ Integrator components you
have created on each platform using the mqsilist command.
v On an HP-UX command line type:
mqsilist

This displays the broker component, with the queue manager which
supports it. Now that the broker has been created, the command responds
with:
BIP8099I: MQSI_SAMPLE_BROKER - MQSI_SAMPLE_QM

BIP8071I: Successful command completion.

v At a Windows NT command prompt type:
mqsilist

This displays the Configuration Manager component, with the queue

manager that supports it. Now that the Configuration Manager has been
created, the command responds with:
BIP8099I: ConfigMgr - MQSI_CONFIG_QM
BIP8071I: Successful command completion.

Starting your broker domain

When you have created the WebSphere MQ Integrator components, you are
ready to activate your broker domain. You require Windows NT
Administrator authority on your Windows NT machine to complete these
steps.

46 WebSphere MQ Integrator for HP-UX Installation Guide

 Starting the broker domain

You are recommended to complete the tasks in the following order:

1. Starting the MQSeries listeners.
2. Defining the channels.
3. Starting the channels.
4. Starting the Configuration Manager on Windows NT.
5. Starting the broker on HP-UX.
6. Starting the Control Center on Windows NT.

The WebSphere MQ Integrator commands are used to illustrate these steps,

with sufficient information provided to complete the task. For a full
description of these commands, and possible errors, see the WebSphere MQ
Integrator Administration Guide. (You cannot use the WebSphere MQ Integrator
for Windows NT and Windows 2000 Command Assistant for these
commands.) If errors are reported, you can also check the Application view of
the Windows NT Event Viewer and the HP-UX syslog.
Starting the MQSeries listeners
Most of the resources you need to support this configuration were created and
started when you invoked the mqsicreatebroker and mqsicreateconfigmgr
commands. There is just one extra step to enable the components to
communicate:
v On an HP-UX command line enter:
runmqlsr -t tcp -p 1415 -m MQSI_SAMPLE_QM
v On Windows NT use one of the following two methods:
– You are recommended to use MQSeries Services (Start —> Programs —>
IBM MQSeries —> MQSeries Services). Expand the left-hand pane and
find and click the queue manager (MQSI_CONFIG_QM) to display its
services in the right-hand pane. If the Listener is listed, right-click the
Listener, and select All Tasks —> Start. This starts the listener as a
background task.
If the Listener is not listed, right-click the queue manager and select New
—> Listener. This creates a listener with default properties of transport
type TCP and port 1414. When it has been created, right-click the
Listener and select Start.
This starts the listener as a background task.
– Enter the following command on the command line:
runmqlsr -t tcp -p 1414 -m MQSI_CONFIG_QM

The listener is started as a foreground task and is not displayed in the

MQSeries Services window.

Note: If the default MQSeries port 1414 is not available (perhaps because it is
already in use by another queue manager), assign an alternative port

Chapter 4. Configuring a broker domain 47

 Starting the broker domain

number. Set the port value in the Listener properties dialog (on the
Parameters tab), or using the -p parameter on the runmqlsr command.
If the port is already in use, the Control Center cannot contact the
Configuration Manager. For example, if you have set up a default
queue manager on this system, it probably already has a listener started
on this port. You can check if any listeners are already active using
MQSeries Services.
Defining queues and channels
You need to define the channels between the Configuration Manager on
Windows NT and the broker on HP-UX.
On HP-UX
Use the following example to define the channels and the
transmission queue:
Notes:
1. Use the name of the queue manager for the Configuration
Manager (MQSI_CONFIG_QM) for the broker’s transmission
queue (xmitq). This enables the broker to resolve the name of the
remote queue manager for the SYSTEM.BROKER.ADMIN.REPLY
queue.
2. Replace config.machine.name with the TCP/IP hostname of the
Windows NT machine where the Configuration Manager is
installed.
runmqsc MQSI_SAMPLE_QM
define qlocal(MQSI_CONFIG_QM) usage(xmitq)
define channel(BROKER.CONFIG) chltype(sdr) trptype(tcp)
conname(’config.machine.name(1414)’) xmitq(MQSI_CONFIG_QM)
define channel(CONFIG.BROKER) chltype(rcvr) trptype(tcp)
end
On Windows NT
| Use the following example to define the channels and the
| transmission queue, replacing broker.machine.name with the TCP/IP
| hostname of the HP-UX machine where the broker is installed:
| runmqsc MQSI_CONFIG_QM
| define qlocal(MQSI_SAMPLE_QM) usage(xmitq)
| define channel(CONFIG.BROKER) chltype(sdr) trptype(tcp)
| conname(’broker.machine.name(1415)’) xmitq(MQSI_SAMPLE_QM)
| define channel(BROKER.CONFIG) chltype(rcvr) trptype(tcp)
| end

| Alternatively, you can use MQSeries Explorer instead of the runmqsc

| command program.
Starting the channels
You need to start the queue manager channel on each platform:

48 WebSphere MQ Integrator for HP-UX Installation Guide

 Starting the broker domain

On HP-UX
Enter the following command:
| runmqchl -c BROKER.CONFIG -m MQSI_SAMPLE_QM
On Windows NT
Enter the following command:
| runmqchl -c CONFIG.BROKER -m MQSI_CONFIG_QM

Starting the Configuration Manager on Windows NT

Enter the following command on the command line to start the Configuration
Manager. (You cannot use the Command Assistant to start the Configuration
Manager):
mqsistart configmgr

This command starts up the Windows NT service for the Configuration

Manager. If the service starts successfully, open the Application view of the
Windows NT Event Viewer to check that the Configuration Manager has also
initialized.

The Configuration Manager cannot contact a broker until there is a reference

to the broker in the configuration repository. Create a reference to the broker
using the Control Center, as described in “Preparing for verification” on
page 53.
Starting the broker on HP-UX
Enter the following command to start your broker:

Note: If you are not using the sample broker name

(MQSI_SAMPLE_BROKER), remember to replace it with your own
name.
mqsistart MQSI_SAMPLE_BROKER

Check the syslog to ensure that the broker has initialized successfully.
Starting the Control Center on Windows NT
Complete the following tasks on Windows NT to set up the environment
required to run the verification programs described in Chapter 5, “Verifying
your installation” on page 53.

Sufficient information is provided to enable you to complete the configuration

of a basic broker domain. For further information about the Control Center,
refer to WebSphere MQ Integrator Using the Control Center.
1. Select Start —> Programs —> IBM WebSphere MQ Integrator 2.1 —>
Control Center.

Chapter 4. Configuring a broker domain 49

Starting the Control Center

Alternatively, double-click the Control Center icon in the WebSphere MQ

Integrator program folder.The Control Center displays the Configuration
Manager Connection window.
2. Complete the following fields to connect the Control Center session to the
Configuration Manager:
Hostname
Enter the network hostname for the system on which the
Configuration Manager was created, for example MQSISYS1(or
your own hostname).
Port Enter the number of the port on which the queue manager is
listening. This was set up in “Starting the MQSeries listeners” on
page 47. The default port is 1414.
Queue Manager name
This field is empty initially. Enter the name of the queue manager
that hosts the Configuration Manager MQSI_CONFIG_QM). This
queue manager already has a definition for the server connection
required by the Control Center: channel SYSTEM.BKR.CONFIG,
type SVRCONN. This was created at the same time as the
Configuration Manager.
3. Click OK. The Control Center now contacts the Configuration Manager.
This might take a few minutes. If the Control Center fails to make contact,
the most likely reasons are:
v The Configuration Manager has not started successfully.
v The listener has not started successfully.
v The queue manager is not available.
v You are logged on to the local security domain, but this user ID is not a
member of the WebSphere MQ Integrator groups. Check the groups of
which your current user ID is a member. Also, check that you are
logged on to the same security domain as the one you were logged on
to when you installed WebSphere MQ Integrator.

Check for MQSeries or WebSphere MQ Integrator entries in the Windows NT

Event log (Application view) to track down the problem.

If you want to check, or change, these settings at a later time, from the
Control Center click File —> Connection to bring up the connection dialog.
Connecting the broker to the domain
By connecting the broker to the domain, you are adding definitions that
enable the Configuration Manager to define flows to the broker. This depends
on the Configuration queue manager routing messages to the Broker queue
manager using the channels defined.

50 WebSphere MQ Integrator for HP-UX Installation Guide

 Connecting the broker to the domain

To add a broker to the domain:

1. Select the Topology panel in the Control Center.
2. In the left-hand pane, right-click the Topology icon , and then select Check
out. A key symbol is displayed next to the Topology icon.
3. In the right-hand pane, right-click and select Create —> Broker. A dialog
box is displayed.
4. Enter the name of your broker on HP-UX (MQSI_SAMPLE_BROKER), and
the name of the broker queue manager (MQSI_SAMPLE_QM).
5. Select Finish.
An icon for the broker is displayed in the right-hand pane. At this point,
neither the Configuration Manager or the broker has been contacted.
6. Right-click on the Topology icon in the right-hand pane and select Check
in. When complete, the key symbol disappears from the Topology icon.

At this stage the broker definition has been stored in the Configuration
Manager database but nothing has been sent to the broker. To verify the
connection between the Configuration Manager and broker you should run
the default execution process against the broker.

To deploy the empty default execution group to the broker:

1. Select the Assignments tab. In the furthest right-hand pane you will see a
definition for the broker, and within the broker icon an empty box
containing the word default.
This indicates that there is one execution group defined for the broker and
that the execution group contains no definitions.
2. In the far-left panel, click with the right-click on the icon identifying your
broker and select Deploy —> Complete Assignments Configuration.
This attempts to send the default execution group definition to the broker.
After a short delay, a dialog box is displayed, indicating that the deploy
request has been submitted to the Configuration Manager.
3. To see the results of the deploy request, select the Log tab in the Control
Center.
All deployed responses are written to this panel. To refresh the display,
click the Refresh icon in the top left-hand corner of the panel.
If the deploy is successful, the Log view in the Control Center (Windows
NT) shows BIP2056I and BIP4040I, and on HP-UX you see two new
processes.
If the deploy response is successful, the broker on your HP-UX machine
starts two new processes. Use the ps -ef command to display a list of
processes. The list includes DataFlowEngine MQSI_SAMPLE_BROKER and
bipservice MQSI_SAMPLE_BROKER.

Chapter 4. Configuring a broker domain 51

Connecting the broker to the domain

If the response is not successful, refer to the messages in the Windows

Event Log (Applications View) to determine the cause of the error.

You have now:

v Created a Configuration Manager on Windows NT
v Created a broker on HP-UX
v Added the broker to the broker domain defined by the Configuration
Manager

See Chapter 5, “Verifying your installation” on page 53 for information on

creating message flows for you to deploy for the HP-UX broker and test using
the sample applications.

52 WebSphere MQ Integrator for HP-UX Installation Guide

Chapter 5. Verifying your installation
You have now completed the configuration and activation tasks. This chapter
explains how to deploy your broker domain, and how to verify your
installation. You can choose to run one or more of a set of verification
programs that illustrate different aspects of setup and operation:
v “Preparing for verification”.
v “Running the predefined verification applications” on page 56.
– “Running the Soccer application” on page 56.
– “Running the Scribble application” on page 59.
– “Running the Postcard application” on page 60.
v “Building and using a message flow” on page 63.

All the tasks illustrated here assume you have used the sample names and
values when you completed the tasks in Chapter 4, “Configuring a broker
domain” on page 29. If you have changed any of these names or values, make
sure that you use your values in this section. Note that if you are not using
MQSI_SAMPLE_QM as the name of the queue manager for your broker, you
need to change the broker queue manager name in the output nodes of the
verification programs.

You complete most of the tasks involved in running these verification

programs using the Control Center. This section gives the minimum
information you need to complete these tasks. For further information, see
WebSphere MQ Integrator Using the Control Center.

Preparing for verification

Before you can run any of the verification programs, you must complete some
preparation.
Creating the MQSeries resources on HP-UX
The verification applications require the following MQSeries queues on the
broker’s queue manager:
v For the Soccer application:
– MQSI_SOCCER_PUBLICATION_QUEUE
– MQSI_SOCCER_SUBSCRIPTION_QUEUE
v For the Scribble application:
– MQSI_SCRIBBLE_PUBLICATION_QUEUE
– MQSI_SCRIBBLE_SUBSCRIPTION_QUEUE
v For the Postcard application:

© Copyright IBM Corp. 2000, 2002 53

Creating MQSeries resources

– MQSI_POSTCARD_INPUT_QUEUE
– MQSI_POSTCARD_OUTPUT_QUEUE
– MQSI_POSTCARD_FAILURE_QUEUE

An MQSC command file that defines these resources is provided in the

sample/mqsc subdirectory of the WebSphere MQ Integrator home directory
(the default path is /opt/wmqi/samples/mqsc).

To run the command file from the command line:

1. Change to the sample/mqsc subdirectory
2. Enter the command:
runmqsc MQSI_SAMPLE_QM < samples.tst

Importing and deploying the WebSphere MQ Integrator resources on

Windows NT
You must now work with the WebSphere MQ Integrator resources that are
used by the applications.
1. Close the Control Center. Stop the Configuration Manager using the
command:
mqsistop configmgr
2. Import the message set required by the Postcard application into the
message repository. The message set is defined in the file PostcardMS.mrp.
To import the message set:
a. Change to the directory examples\postcard in the WebSphere MQ
Integrator home directory (the default home directory is C:\Program
Files\IBM\WebSphere MQ Integrator 2.1).
b. Enter the following command, using user ID and password in this
command that you specified for message repository access when you
created the Configuration Manager (flags -e and -r).:
mqsiimpexpmsgset -i -n MQSIMRDB -u mqsiuid -p mqsipw -f PostcardMS.mrp

For more details of this command, see the WebSphere MQ Integrator

Administration Guide.
3. Stop and restart the Configuration Manager (mqsistop configmgr and
mqsistart configmgr). The Configuration Manager can now access the
new message set and make it available.
4. Restart the Control Center and select the Topology view. Check out the
broker domain topology by selecting the topology, right-clicking, and
selecting Check Out. This locks the topology and allows you to make
changes to it.
5. The title bar currently displays Untitled to show that you have an empty
workspace. Import the supplied workspace import file that defines the
resources used by the verification programs.

54 WebSphere MQ Integrator for HP-UX Installation Guide

 Importing and deploying resources

a. Select File —> Import to Workspace. The Import dialog displays the file
that contains the resource definitions, the following valid resource
types:
v Message flows
v Topics
v Topology
b. Select Message flows, and Topology because the file supplied by
WebSphere MQ Integrator contains message flow and topology
definitions.
c. Click Browse and locate the \examples subdirectory (in the
WebSphere MQ Integrator home directory). Change the setting in the
Files of type box to All files (*.*). Select the sample workspace import
file SamplesWorkspaceForImport.xml, select Open, and then click
Import.
The definitions take a few minutes to import. When import has
finished, a message dialog is displayed, confirming that the resources
have been imported successfully. Click OK to close the dialog. The
sample broker (MQSI_SAMPLE_BROKER) is displayed in the
topology.
d. Select the Message Flows view. Check that the import has created the
following five message flows, in addition to the IBMPrimitives folder:
v Version 1 Migration/Compatibility
v Default Publish/Subscribe
v Soccer
v ScribbleInversion
v Postcard
The Postcard message flow is displayed in the view. This sample is
platform-independent.
6. Check that the message flows are displayed in the Domain hierarchy and
Topology panes, of the Assignments view. The message flows were
assigned to the broker’s default execution group when you imported the
workspace.
7. Select and assign a message set as follows:
a. Select the Message Sets panel.
b. Right-click and select Add to Workspace—>Message Set....
c. Select PostcardMS, and then click Finish.
d. Select the Assignments panel, and then drag PostcardMS onto
MQSI_SAMPLE_BROKER in the right-hand panel.
8. Save the changes that you have made. Select File —> Check in —>
All (Save to Shared). This causes the following to happen:

Chapter 5. Verifying your installation 55

Importing and deploying resources

a. The contents of the configuration repository are updated with the

new definitions and assignments and everything is checked into the
repository.
b. The new workspace is saved locally. Because this is a new workspace,
you are prompted for a name. Enter a name, for example
SampleWorkspace, and click Save. This name appears in the title bar.
9. Deploy your changes to the broker. When you deploy, the Configuration
Manager sends information to the broker about the resources it needs to
support the message flow services.
a. Select the Topology view.
b. Select File —> Deploy —> Complete Configuration (all types) —>
Normal, or right-click the Topology root and select Deploy.
A message dialog confirms initiation. Select OK to close the dialog.
10. Select the Log view and refresh the contents by clicking the green refresh
icon. It can take a few minutes for all the deployment messages and
responses flowing between the Configuration Manager and the broker to
be displayed. Keep refreshing this view until you see the completion
messages. If everything is successful, the log contains the following
messages: BIP4045I, BIP4040I, and BIP2056I.
11. View the deployed configuration graphically in the Operations view.
Refresh the view, and the topology view is displayed.

Running the predefined verification applications

This section describes how to run each of the three applications supplied with
WebSphere MQ Integrator. You can run any of these, in any order,
immediately after installation or at any time in the future. If you choose to
run these applications later, make sure you have your system set up in the
same way as the system you configured in Chapter 4, “Configuring a broker
domain” on page 29 (or make the appropriate adjustments as you follow these
steps).

The verification applications also illustrate how WebSphere MQ Integrator can

be used to transform and route messages outside the programming logic of
the participating applications, which can therefore run unaffected by updates
to that transformation logic, or routing logic, or both.

Note: If you are not using MQSI_SAMPLE_QM as the queue manager for
your broker, you must change the broker queue manager name in the
output nodes of the verification sample programs.
Running the Soccer application
The Soccer application is written in the C programming language and
demonstrates a number of basic publish/subscribe features. The application is

56 WebSphere MQ Integrator for HP-UX Installation Guide

 Running Soccer

a simple implementation of a soccer match results gathering service. It

consists of one or more publisher applications, and one subscriber application.
You can find the files that make up this application (source, header files, and
executables) in the sample/Soccer directory.

Run this application on HP-UX as follows:

1. Start the subscriber application soccerResults.
You must start a single subscriber that subscribes to all soccer matches
being played, and displays the results for them. The subscriber application
functions as a results server. You must start soccerResults before you start
any instances of the publisher application, so that the results server does
not miss any publications.
Start the Soccer as follows:
a. Change to the /opt/wmqi/sample/soccer/bin directory.
b. Enter the command:
soccerResults MQSI_SAMPLE_QM

The results server displays a message confirming that it has registered a

subscription and started successfully, and you can now start the match
simulator (publisher).
2. Start the publisher application, soccerGame.
You can run one or more publishers. Each instance publishes event
publications on a single soccer match. You must specify two soccer teams
as input to soccerGame.
Start the publisher application as follows:
a. Change to the /opt/wmqi/sample/soccer/bin directory.
b. Enter the command to start up a soccer game. Team names can contain
only the characters _, 0-9, a-z, and A-Z. You can use the “_” character
to represent a space in the name of a team:
soccerGame Team1 Team2 MQSI_SAMPLE_QM

soccerGame Arsenal Manchester_United MQSI_SAMPLE_QM

How the Soccer works

The Soccer application uses messages that have a standard MQSeries header,
an MQRFH2 header, and a string that specifies the playing teams and their
scores.

The soccer simulator soccerGame publishes an event publication following

this message template to the queue MQSI_SOCCER_PUBLICATION_QUEUE
on the broker’s queue manager. The MQInput node in the Soccer message
flow has been set up so that it identifies this queue as its input queue.

Chapter 5. Verifying your installation 57

Running Soccer

The input node retrieves the publication from this queue and forwards it to
the publication node. The publication can indicate that:
v A match has started.
v A goal has been scored.
v A match has ended.

The results server soccerResults subscribes to all these event publications

arriving on queue MQSI_SOCCER_SUBSCRIPTION_QUEUE. It processes
these messages and displays the information: the start of a new game, a score
update, and the end of a game.

One important feature of the soccer simulator soccerGame is its ability to

maintain a current state of all the matches being played (the multiple
publishers). It achieves this by publishing a retained publication message to
the broker with the latest score of each match every time the score changes.
This means you can restart the results server after a failure, and the results
server subscribes to all these retained publications to restore the current match
state to the state it had the last time the results server was running.

If you want to see this use of retained publications, you can start several
instances of the publisher application soccerGame. When these are running,
and a couple of goals have been scored, change to the window running the
results server application and prematurely stop that process1 using Ctrl-C.

Wait about 30 seconds, then restart the results server soccerResults. You will
see that the matches being played are restored to their last known score, and
updated by any remaining match changes that occurred whilst the Soccer was
stopped.

If you restart the results server too quickly, it might fail to open the subscriber
queue with reason 2042 (MQRC_OBJECT_IN_USE). This is because the queue
manager has not yet recognized that the application has failed, and has
therefore not released the queue that the application opened exclusively. You
can retry the restart after a few seconds; once the queue is available it will
succeed.

See the WebSphere MQ Integrator Programming Guide for more details about the
implementation of this application and the publish/subscribe techniques it
uses.

1. If you have created your broker to run as an MQSeries trusted application, you must not end this application in
this way, because the queue will not be released. For more information about WebSphere MQ Integrator and
MQSeries trusted applications, see WebSphere MQ Integrator Introduction and Planning.

58 WebSphere MQ Integrator for HP-UX Installation Guide

 Running Scribble

Running the Scribble application

The Scribble application is written in Java and demonstrates a number of
basic publish/subscribe and message transformation features. In contrast to
the Soccer which works with multiple publishers and one subscriber, Scribble
works with one publisher and any number of subscribers.

The publisher publishes the current coordinates of the line being drawn in its
window, and each subscriber receives the inverted coordinates and displays
the resulting drawing in its window.

You must ensure that:

v MQSeries Client for Java is installed on the HP-UX machine.
v IBM Runtime Environment For the Java Platform Version 1.3 is installed on
the HP-UX machine. This is supplied on the Supplemental CD.
v Environment variables are set correctly in the profile. Refer to the file
readme.txt on the product CD for information on these.

To run the Scribble application on HP-UX:

1. Start the publisher application.
a. Open a command window and change to the
/opt/wmqi/sample/scribble subdirectory
b. Execute the ScribblePublisher.sh script

You now see a dialog that prompts you for the broker queue manager
name. Enter MQSI_SAMPLE_QM and click OK. A confirmation dialog,
Scribble ready, is displayed. Click OK. The publisher window is displayed.
2. Start the subscriber application.
a. Change to the /opt/wmqi/sample/scribble subdirectory
b. Execute the ScribbleSubscriber.sh script

You now see a dialog that prompts you for the queue manager name.
Enter MQSI_SAMPLE_QM. The dialog also allows you to enter a queue
name. If you want to use the default subscriber queue,
MQSI_SCRIBBLE_SUBSCRIPTION_QUEUE, you do not have to specify
this. If you are using a different queue, you must define that queue and
enter the name here. Click OK. The subscriber window is displayed.
3. Start dragging the mouse with either mouse button depressed to draw
lines in the publisher window. These lines appear inverted in your
subscriber window.

You can start multiple Scribble subscribers, but you must specify a different
queue for each one. The definitions you completed in “Creating the MQSeries
resources on HP-UX” on page 53 contains a single subscriber queue for this

Chapter 5. Verifying your installation 59

Running Scribble

application, the default subscriber queue

MQSI_SCRIBBLE_SUBSCRIPTION_QUEUE. If you want to start additional
subscribers, define additional queues like the default one, and enter the queue
name as well as the queue manager name at the dialog you see when you
first start the subscriber.

How Scribble works

The Scribble application uses messages that have a standard MQSeries header,
an MQRFH2 header, and a message body formatted in XML that specifies the
drawing coordinates. When you drag the mouse across the publisher window
with a mouse button depressed, it draws a line that the publisher records as a
set of coordinates. It publishes each set of coordinates in an XML message to
the publication queue MQSI_SCRIBBLE_PUBLICATION_QUEUE. The
MQInput node in the ScribbleInversion message flow has been set up so that it
identifies this queue as its input queue.

The input node retrieves the publication from this queue and the message
flow inverts the drawing by manipulating the coordinates (transformation),
and publishes the resulting drawing (routing) to each ScribbleSubscriber’s
subscription queue (MQSI_SCRIBBLE_SUBSCRIPTION_QUEUE is the
default).

The details of the transformation and routing performed by the

ScribbleInversion message flow are:
v Receive the published message in the MQInput node.
v Filter on the publish/subscribe topic scribble/coord in the FilterOnTopic
node. This node is of primitive type Filter.
If the match is successful, the message is passed to the InvertCoordinates
node, which is of primitive type Compute, for transformation.
If no match is found, the message is sent directly to the publication node
without inversion.

You can see the ESQL code that implements the inversion of the coordinates
in the message. Select the Message Flows view in the Control Center, select
ScribbleInversion in the tree in the left pane, click the InvertCoordinates node
with the right mouse button to display the node’s context menu, and select
Properties.
Running the Postcard application
The Postcard application is based on the WebSphere MQ for Windows NT
and Windows 2000 Postcard application, and has been extended to
demonstrate the transformation capabilities of WebSphere MQ Integrator. It is
written in C with a Java end-user interface.

60 WebSphere MQ Integrator for HP-UX Installation Guide

 Running Postcard

Postcard allows you to send a postcard to another nickname, either known to

this instance, or to a different instance, of the application. You must run this
application on the same system as the broker. You can find the files that make
up this application (source, header files and executables) in the
sample\postcard subdirectory under the WebSphere MQ Integrator home
directory.

You must ensure that:

v MQSeries Client for Java is installed on the HP-UX machine.
v Environment variables are set correctly in the profile. Refer to the file
readme.txt on the product CD for information on these.

Run this application by following these steps:

1. Start the first Postcard application.
This first instance acts as the sending application. Change directory to
/opt/wmqi/sample/postcard and execute the postcard.sh script.
You now see a dialog that prompts you for a nickname to use for sending
or receiving messages. Enter an alphanumeric string of up to 24 characters.
The dialog also asks you for the name of the broker queue manager. This
is an optional field, but if you do not enter a queue manager name, the
default queue manager is used. Enter MQSI_SAMPLE_QM to specify the
correct queue manager for verification. Click OK. A Postcard window
appears.
2. Start the second Postcard application.
This second instance acts as the receiving application. Enter a second
nickname and the name of the broker queue manager. Click OK. A second
Postcard window appears.
3. Fill in the postcard and send the message.
In the sender (first) Postcard window, fill in the To field with the
nickname of the receiving (second) postcard application. Fill in the
remaining fields from the pulldown menus to build the content of the
postcard (location, length of stay, and weather). Click the Send button. You
see the message, marked Sent, in the box called “Postcards sent and
received (transformed)” in the lower part of the Postcard window.
4. View the received postcard message.
You will see the postcard arrive in the second (receiving) Postcard
application. Select the received message in the list and click View to see
the contents of the (received and transformed) message. The message has
been transformed to include the country of the city from which the
message was sent.
5. Return a postcard to the original sender.
From the second Postcard application, select a message from the
“Postcards sent and received (transformed)” box and click Reply. This

Chapter 5. Verifying your installation 61

Running Postcard

gives you a new postcard to fill in, with the first application’s nickname
already in the To field. Fill in the remaining fields and click Send to send
the new postcard to the first application.

How Postcard works

The Postcard application sends messages to, and receives messages from, the
Postcard message flow. You deployed this message flow to the broker in
“Preparing for verification” on page 53. You also stored the message set
PostcardMS in the message repository, and deployed it to the same broker. The
message set is referenced by the message processing nodes within the flow. It
contains one message, PostcardMessage, that defines these elements:
1. Location (of type STRING)
2. Country (STRING)
3. MessageText (STRING)
4. Duration (INTEGER)
5. Recipient (STRING)
6. Sender (STRING)
7. GoodTime (INTEGER)
8. Weather (STRING)

The elements of type STRING each have an associated element length that
defines the maximum number of characters valid in this element.

The application program creates and interprets the messages based on a

structure defined in the C header file postcardstruc.h in the sample\postcard
subdirectory. This header is an identical representation of the message in the
message set in the Control Center.

When a user sends a postcard, the application puts a message to the queue
associated with the Postcard message flow
(MQSI_POSTCARD_INPUT_QUEUE). The message flow provides the
following message processing:
v The MQInput node retrieves messages from the input queue
MQSI_POSTCARD_INPUT_QUEUE.
v The input node passes the message to node AddCountry, an instance of the
IBMPrimitive Compute node. This node enhances the content of the
message by adding the Country field, containing the country of the location
you selected when you sent the postcard (for example, if you selected
“Adelaide”, it adds “Australia”).
v The AddCountry node now passes the message to the MQOutput node,
which puts it to the output queue (MQSI_POSTCARD_OUTPUT_QUEUE).
v The receiving postcard application retrieves the message from the output
queue, reads and interprets the content, and displays the element content in
the corresponding fields of the Postcard user interface window.

62 WebSphere MQ Integrator for HP-UX Installation Guide

 Running Postcard

Although this application has a message set already defined (see “Importing
and deploying the WebSphere MQ Integrator resources on Windows NT” on
page 54), you can create a message set based on a C header file (like
postcardstruc.h) by importing that C structure into the message repository
using the import function of the Control Center. This is explained in detail in
WebSphere MQ Integrator Using the Control Center.

Note: Do not try this after importing PostcardMS; this would create duplicate
entries and cause problems with deployment.

Building and using a message flow

This verification scenario illustrates how you define a basic message flow,
how you assign the resources to the broker, and deploy your changes. It uses
MQSeries Explorer to send messages through the message flow you create. It
does not use any defined message sets. It assumes you are using the sample
broker that you created in “Configuring your broker domain” on page 41. If
you want to use another broker, you must ensure that you create it (using
mqsicreatebroker) and define it in the configuration repository (from the
Topology view in the Control Center).

The tasks assume that the broker, sample queue managers, Control Center,
listeners, sender channels, and Configuration Manager are running.

The following tasks are described:

v “Creating the MQSeries resources”.
v “Creating a message flow”.
v “Assigning the message flow to the broker” on page 64.
v “Testing the message flow” on page 65.
Creating the MQSeries resources
This verification test needs two queues, one for input, the other for output. To
create the queues locally on HP-UX, type the following from a command line:
runmqsc MQSI_SAMPLE_QM
define qlocal(MQSI_INQ)
define qlocal(MQSI_OUTQ)

Creating a message flow

You must now create the message flow that will process the messages you put
to your input queue using the Control Center on Windows NT. The message
flow is very simple: it retrieves the message from the input queue and puts it
to the output queue.
1. Select File —> New Workspace to create a new (untitled) workspace. If
you have run the verification applications, and have your sample
workspace already open, you can create your new message flow in this
workspace if you prefer.

Chapter 5. Verifying your installation 63

Defining a message flow

2. Select the Message Flows (Designer) view.

3. Right-click on the Message Flows root and select Create —> Message flow.
4. Enter the name MQSI_TEST. Click Finish. The new message flow appears
in the tree view.
5. Expand the IBMPrimitives tree to display the supplied nodes.
6. Select the MQSI_TEST message flow in the left-hand pane. Drag and
drop an MQInput node into the right-hand pane.
7. Right-click the MQInput node in the right-hand pane and select
Properties. On the Basic tab, type the MQSeries input queue name of your
input queue (MQSI_INQ). Click OK.
8. Drag and drop an MQOutput node into the right-hand pane.
9. Right-click the MQOutput node in the right-hand pane and select
Properties. On the Basic tab, type in the queue manager name
(MQSI_SAMPLE_QM) and the queue name (MQSI_OUTQ) for the output
queue. Click OK.
10. Right-click the MQInput node and select Connect —> Out. This gives you
a connector attached to your mouse. Drag this to the MQOutput node
and drop by left-clicking. The connector attaches itself to the input
terminal.
11. You have now completed your first message flow. Select File —> Check in
—> All (Save to Shared). This checks in all the resources to the
configuration repository and saves a local copy of the workspace file. If
you created a new workspace for this new message flow, you will be
prompted to give the workspace a name when you save it.
Assigning the message flow to the broker
Now you have created a message flow, you have to tell WebSphere MQ
Integrator where you want to run that message flow (that is, on which
broker). To do this, you must assign the message flow to your broker.
1. Create a broker reference, if you have not already done so; the topology
must be checked out to allow this. Right click on Topology and select
Create —> Broker. The broker name should be MQSI_SAMPLE_BROKER
and the queue manager name should be MQSI_SAMPLE_QM.
2. Select the Assignments view.
3. Expand the broker name (MQSI_SAMPLE_BROKER) to display the
broker’s execution groups. The sample broker currently just has one
execution group, the default one (called default) which is always created
whenever you create a broker using mqsicreatebroker.
4. Right-click the default execution group and select Check Out. This locks
the execution group for you.
5. Expand the Message flows tree in the center pane. This displays all the
message flows available for assignment.

64 WebSphere MQ Integrator for HP-UX Installation Guide

 Defining a message flow

6. Find MQSI_TEST and drag and drop it on the default execution group in
the right-hand pane, where you can see the graphic of the broker and the
default execution group. You can drop a message flow only on an
execution group (not on the broker itself).
7. Check in the execution group by right-clicking the default execution group
in the left-hand pane and selecting Check In.
Deploying the message flow to the broker
Assignment makes the connection between a message flow and a broker, but
it is only when you deploy the change that the Configuration Manager
updates the broker with the configuration stored in the configuration
repository.
1. Before you can deploy any changes, you must have checked in everything
that you have updated. If you have followed the instructions in this
section, all the relevant resources are checked in. However, if you are in
any doubt, you can check everything in by selecting File —>Check In
—>(All) Save to Shared.
2. In the Assignments view, right-click the broker name in the left-hand pane.
3. Select Deploy —> Complete Assignments Configuration. When the
Configuration Manager receives this request from the Control Center, it
sends messages to the broker to give it the updated information it needs to
be able to support your new message flow.
4. To check the deploy, change to Log view and click the Refresh button (the
green icon above the Log pane). Look for the success messages BIP404I
and BIP405I. There might be a slight time delay before the messages
appear.
5. View the deployed configuration graphically in the Operations view.
Refresh this view and the broker, execution group and message flow are
displayed with green lights, to show they are all active.
Testing the message flow
To test your message flow, follow the steps below:
1. Change to the directory that contains the MQSeries sample programs:
/opt/mqm/samp/bin
2. Enter the following command:
./amqsput MQSI_INQ MQSI_SAMPLE_QM
3. Press Enter.
4. Enter the text of your message.
5. Press Enter twice to quit the program.
6. Use either amqsget or amqsbcg to get the message you entered. For
example:
./amqsget MQSI_OUTQ MQSI_SAMPLE_QM

Chapter 5. Verifying your installation 65

Testing a message flow

Your message is displayed.

Your test is complete.

66 WebSphere MQ Integrator for HP-UX Installation Guide

Appendix A. System changes after installation
This appendix describes the changes that installation and configuration have
made on the systems you have set up in your broker domain. It assumes that
you have followed the guidance and details of configuration given in
Chapter 4, “Configuring a broker domain” on page 29.

This appendix contains these sections:

v “Directory structure”.
v “Environment variables” on page 68.
v “Database contents” on page 69.
v “Default MQSeries resources” on page 71.
The default home directory for WebSphere MQ Integrator is:
/opt/wmqi

The default home directory for DB2 is:

/opt/IBMdb2

This is written as <db2_root> wherever it appears in this chapter.

Directory structure
The following tables list the subdirectories created and populated within your
home directories when you install the product. It also provides a brief
description of the contents.

All files are installed with default security: all users can access and execute
these files. You can use standard operating system facilities to impose stricter
security on these files, or a subset of files, if you choose.
Table 4. /opt/wmqi/ directory structure after installation
Directory Names Contents
bin Executable commands
classes Java class files
CmdAsst Command assistant files
docs PDF files
icu16 icu data files
include Header files for samples
jre IBM Runtime Environment For the Java Platform

© Copyright IBM Corp. 2000, 2002 67

Directory structure

Table 4. /opt/wmqi/ directory structure after installation (continued)

Directory Names Contents
lib Shared library files
lil WebSphere MQ Integrator lils
merant Merant Drivers
messages Description files for messages and exceptions
readmes Readme files
sample Samples
template Template files

Table 5. /var/wmqi directory structure after installation

Directory Contents
brokers Brokers directory
log WebSphere MQ Integrator logs directory
messages Messages directory
odbc ODBC files
locks Named mutex files
registry Registry files
users Users directory

Environment variables
The following environment variables are required to contain specific values
for WebSphere MQ Integrator:
v CLASSPATH
v LANG
v LC_ALL
v LD_LIBRARY_PATH
v MQSI_REGISTRY
v NLSPATH
v ODBCINI
v PATH

The following environment variables might be required to contain specific

values if you use New Era of Networks Rules and Formatter Support:
v ICU_DATA
v MQSI_PARAMETERS_FILE

68 WebSphere MQ Integrator for HP-UX Installation Guide

 Environment variables

v MQSI_PRELOAD
v NNSY_CATALOGUES
v NNSY_ROOT
v NN_CONFIG_FILE_PATH

To ensure you get the latest environment variables you must refer to the
readme.txt file on the main product CD.

A profile that contains the required environment variables is shipped with this
product. You must run this profile or a copy of it:
/opt/wmqi/sample/profiles/profile.hpux

| For more information on New Era of Networks environment settings see

| WebSphere MQ Integrator Administration Guide.

Database contents
When you create WebSphere MQ Integrator resources following installation,
database tables are created for your broker within the database you specify in
the create command.

The database you specify can be created for each set of tables or it can be
shared. The database tables schema inherits its name from the datasource
specified in the create command

Table 6 on page 70 shows the tables that are created by the mqsicreatebroker
command in the broker database. The tables are created when you create the
first broker. When you create further brokers specifying the same database,
new rows are created for each broker. Every row created in the table includes
the broker name; therefore each row is unique to a single broker.

You must add all these database tables into your standard backup and
recovery routines to ensure you can recover from system failures and other
emergencies.

Appendix A. System changes after installation 69

Database contents

Table 6. Database tables for brokers

Table name Description
BACLENTRIES ACL entries
BCLIENTUSER Maps client identifiers to durable subscriptions
BGROUPNAME Publish/subscribe principals: groups
BLOGICALTOPHYSNAME Maps logical to physical names
BMQEPUBDEST Contains list of MQSeries Everyplace™ queues on which
messages can be placed.
BMQEPUBMSGIN Holds persistent MQSeries Everyplace
publish/subscribe messages waiting to be processed by
the broker.
BMQEPUBMSGOUT Holds persistent MQSeries Everyplace
publish/subscribe messages to be placed on an
MQSeries Everyplace queue.
BMQESTDMSGIN Holds persistent MQSeries Everyplace
non-publish/subscribe messages waiting to be
processed by the broker.
BMQESTDMSGOUT Holds persistent messages to be sent to MQSeries
Everyplace destinations.
BMQPSTOPOLOGY Publish/subscribe neighbor information
BNBRCONNECTIONS Inter-broker neighbor connection information
BPHYSICALFILE Physical file mapping
BPUBLISHERS Registered publishers
BRETAINEDPUBS Retained publications
BRMCONFIG Broker configuration details
BRMINFO Registered resource managers
BRMPHYSICALRES Physical resources
BRMRTDDEPINFO Runtime dictionary dependency values
BRMRTDINFO Registered runtime dictionaries
BRMWFDINFO Registered wire format descriptors
BROKERAA Broker process details to support recovery
BROKERAAEG Execution group details to support recovery
BROKERRESOURCES Broker resources
BSCADADEST Contains list of SCADA clients to which messages can
be sent.
BSCADAMSGIN Holds persistent SCADA messages waiting to be
processed by the broker.

70 WebSphere MQ Integrator for HP-UX Installation Guide

 Database contents

Table 6. Database tables for brokers (continued)

Table name Description
BSCADAMSGOUT Holds persistent messages to be sent to SCADA
destinations.
BSUBSCRIPTIONS Durable subscription information
BTOPOLOGY Inter-broker neighbor information
BUSERCONTEXT Maps client identifiers to context information
BUSERMEMBERSHIP Publish/subscribe principals: membership
BUSERNAME Publish/subscribe principals: users
BWFFRELATIONSHIP Workfile details

These tables are maintained by processes that are internal to WebSphere MQ

Integrator components. You must not access these tables by any other means,
or change the access authority required by WebSphere MQ Integrator.

Default MQSeries resources

When you create WebSphere MQ Integrator components, some MQSeries
resources are created for their use. Table 7 lists all these MQSeries resources,
and indicates the component associated with the queue manager on which
they are created. For details of which resources are created by which create
commands, see the command descriptions in the WebSphere MQ Integrator
Administration Guide.

MQSeries resource names start with the reserved characters “SYSTEM”. A

conflict of names should not normally arise; with one exception. MQSeries
Publish/Subscribe (if it is in use) defines a queue called
SYSTEM.BROKER.CONTROL.QUEUE, which is also used by WebSphere MQ
Integrator. However, its use is compatible, and no action is required.

MQSeries resources are defined in addition to MQSeries product default

objects (which are defined when MQSeries Messaging is installed). For a full
description of default objects, refer to MQSeries System Administration,
SC33-1873.
Table 7. WebSphere MQ Integrator default objects
Resource name Type Queue Description
manager
SYSTEM.BROKER.ADMIN.QUEUE queue broker Target for messages sent by the
Configuration Manager and
commands to modify the broker’s
configuration and operation.

Appendix A. System changes after installation 71

MQSeries resources

Table 7. WebSphere MQ Integrator default objects (continued)

Resource name Type Queue Description
manager
SYSTEM.BROKER.CONTROL.QUEUE queue broker Target for publish/subscribe control
requests from applications.

MQSeries Publish/Subscribe defines

and uses a queue of the same name.
If the queue is already defined on
the queue manager, you can
continue to use it for WebSphere
MQ Integrator.
SYSTEM.BROKER.EXECUTIONGROUP.QUEUE queue broker Target for messages to the broker.
SYSTEM.BROKER.EXECUTIONGROUP.REPLY queue broker Target for response messages for the
broker from the User Name Server.
SYSTEM.BROKER.INTERBROKER.QUEUE queue broker Target for publications from
neighbor brokers.
SYSTEM.BROKER.MODEL.QUEUE queue all Model for dynamic response queues.
SYSTEM.BROKER.SECURITY.QUEUE queue User Name Target for request messages to the
Server User Name Server. queue is used by
brokers, the Configuration Manager,
and the command line tools.

72 WebSphere MQ Integrator for HP-UX Installation Guide

Appendix B. Setting up an Oracle8 broker database on
WebSphere MQ Integrator
This chapter is intended for an Oracle database administrator (DBA) who is
setting up an Oracle8 broker database for use with WebSphere MQ Integrator.

You are recommended to create a new database instance, rather than use an
existing one.

The instructions in this chapter assume that:

v A database instance is created using Oracle documentation.
v SQL*Net is used to set up Oracle communications, as described in Oracle
documentation.
v Oracle operations are carried out within the correct Oracle environment (for
example ORACLE_HOME).

Naming conventions
WebSphere MQ Integrator uses the Data Source Name (DSN) defined in the
ODBC setup. You do not have to use a specific named instance for a broker
database.

Schema
WebSphere MQ Integrator does not require that a specific schema, or a set of
tablespaces, is used for storing broker information. When you create a broker,
the ownership of the tables created in the database is defined by the user ID
specified on the command line. The user ID must already be defined in the
database. For example:

Note: Enter the following command on one line, ignoring the ’\’.
mqsicreatebroker MQSI_SAMPLE_BROKER -i bid - a bpw -q MQSI_SAMPLE_QM \
-n ORACLEDB BDB -u dbid -p dbpw

dbid is the owner of all the tables created in this command (similar to
DBID.BROKERAA).

The tables are created in the default tablespace assigned to the Oracle user ID
(the default is SYSTEM).

© Copyright IBM Corp. 2000, 2002 73

Schema

Sizing
When you create a broker, WebSphere MQ Integrator generates a small
amount of data to store in the database. Deployment of a complex flow to the
broker require more database space, but not a significant amount. When you
create an instance specifically for use as a broker database, the default settings
defined by the dbassist tool are sufficient for most applications. For example,
50 MB is sufficient for a custom setup. You can extend any tablespace that is
created specifically for use by the brokers, at a later date.

User ID privileges
The Oracle user ID that is used to store broker information requires connect,
resource and create table privileges. For example:
CREATE USER dbid IDENTIFIED BY dbpw;
GRANT CONNECT TO dbid;
GRANT RESOURCE TO dbid;
GRANT CREATE TABLE TO dbid;

Optionally, you can define the following:

ALTER USER dbid DEFAULT TABLESPACE brktbspc;

This user ID can be the same as the operating system ID that will be used to
create the broker or it can be specific to the database. If it is specific to the
database, use the ’-u’ and ’-p’ flags when you create the broker.

ODBC
1. After you have created and started the database, and have configured
SQL*Net (using listener.ora and tnsnames.ora), check that the database is
accessible through the SQL*Net interface. To check that the SQL*Net
listener is running, use:
lsnrctl status

To check the process list for tnslsnr, use:

ps -ef | grep tnslsnr
2. Oracle provides a utility called tnsping to check that a configured Oracle
Global Database Name (DSN) is accessible. For example:
tnsping myDSN
3. It is useful to test the user ID using SQL*Plus. To connect the user ID to
SQL*Plus, use:
sqlplus dbid/dbpw@myDSN

To look at a process list, use:

ps -ef | grep myDSN

74 WebSphere MQ Integrator for HP-UX Installation Guide

 ODBC

One of the entries in the list should be similar to the following:

myid 1234 5678
0 10:55:57 ? 0:00 oraclemyDSN (LOCAL=NO)

You can see that the connection is not local. This means that the
connection is using SQL*Net.
4. Update the WebSphere MQ Integrator ODBC description file
/var/wmqi/odbc/.odbc.ini to add entries for your broker database. At the
head of the file, in the [ODBC Data Sources] section, add an entry
specifying the DSN that the broker will use. This might be different from
the DSN defined by SQL*Net if required. For example:
[ODBC Data Sources] MYBRKDSN=MERANT
3.60 Oracle 8 driver
5. Create a stanza to define the driver path and Oracle DSN for your broker
DSN, for example:
[MYBRKDSN] Driver=/opt/wmqi/merant/lib/UKor815.so
Description=Oracle8
ServerName=myDSN
EnableDescribeParam=1
OptimizePrepare=1
6. Now you can create a broker using a command similar to the example
below.

Note: Enter the following command on one line, without the ’\’.
mqsicreatebroker MQSI_SAMPLE_BROKER -i uid -a pwd -q MQSI_SAMPLE_QM -n \
MYBRKDSN -u dbid -p dbpw

Rebuilding the client library

To run inst_db on HP-UX using Oracle 8.1.7, you need to rebuild the client
library, as follows:
1. Shutdown Oracle.
2. Enter cd $ORACLE_HOME/lib
3. Enter cp libclntsh.sl.8.0 libclntsh.sl.8.0.original
4. Enter cp ldflags ldflags.original
5. Edit ldflags to remove references to:
-L/u01/app/oracle/product/8.1.7/JRE/lib/PA_RISC/native_threads

and
-ljava
6. Enter cd $ORACLE_HOME/bin
7. Enter genclntsh
8. Restart Oracle.

Appendix B. Setting up an Oracle8 broker database on WebSphere MQ Integrator 75

ODBC

76 WebSphere MQ Integrator for HP-UX Installation Guide

 Appendix C. Uninstalling WebSphere MQ Integrator
This chapter gives details of the processes that allow you to uninstall any one
or all of the WebSphere MQ Integrator components on HP-UX.

Before you start

Before you uninstall WebSphere MQ Integrator for HP-UX:
1. Log on as user wmqi.
2. Stop any brokers that are running, using the mqsistop command. For an
explanation of the return codes refer to the WebSphere MQ Integrator
Administration Guide.
3. Stop your User Name Server (if you have one) using the mqsistop
command.

Uninstalling WebSphere MQ Integrator:

To uninstall WebSphere MQ Integrator:
1. Log on as user root.
2. Enter the command swremove WMQI.

An uninstall deletes the contents of the broker database tables, not the tables
themselves, and it leaves the directory structure intact.

Unmounting the CD-ROM drive

To unmount the CD-ROM drive, enter the following commands:
| 1. pfs_umount /<cdrom>
where <cdrom> is the location of the CD-ROM device.
2. List all the pfs* processes that are running:
ps −ef | grep pfs*
3. Terminate all the pfs* processes to release the CD-ROM drive:
kill −9 <PID>

where <PID> is the Process ID Number.

© Copyright IBM Corp. 2000, 2002 77

Uninstalling WebSphere MQ Integrator

78 WebSphere MQ Integrator for HP-UX Installation Guide

 Appendix D. Applying maintenance
Maintenance updates are supplied on CD in the form of a Program
Temporary Fix (PTF), referred to as a Corrective Service Diskette (CSD). You
can find the latest information about available CSDs on the Internet, at the
address given in “MQSeries information available on the Internet” on page 99.

You can also download CSDs from this Web site.

Applying maintenance to WebSphere MQ Integrator

Before applying any maintenance, read the file memo.ptf and any readme.txt
files in the root directory of the CD. If you need to apply a CSD:
1. Stop all brokers that are running.
| 2. Mount the CD as described in “Mounting WebSphere MQ Integrator for
| HP-UX CDs” on page 22.

| Note: If the CD is mounted incorrectly, some of the files cannot be read.

| This causes the maintenance installation to fail with corrupt
| directory errors. It is important that you check that the CD is
| mounted with Rockridge extensions enabled.
| 3. Type the following command:
| swinstall -s /cdrom

| This launches the Install Window containing ″WebSphere MQ Integrator

| Update″.
| 4. From the Install Window:
| a. Select the package
| b. Select Actions —> Mark for Install
| c. Select Actions —> Install

To display the current level of corrective service, enter the command:

swlist | grep WMQI

The current level is the highest value of WMQI-Uxxxxxx. WebSphere MQ

Integrator Version 2.1 returns WMQI.

After installation of the CSD, you can restart your broker or brokers.

| To remove a CSD:

© Copyright IBM Corp. 2000, 2002 79

 Applying maintenance

| 1. Launch swremove
| 2. Select the CSD image
| 3. Actions —> Mark For Remove
| 4. Actions —> Remove

Note: CSDs are cumulative, therefore you do not need to apply CSD1 before
you can apply CSD2. When you have installed a CSD, you are
prevented from installing a previous CSD without first restoring the
system using the backed-up files.

| See also “Applying New Era of Networks maintenance”.

Restoring a previous service level

Because CSDs are cumulative, you must uninstall the most recent CSD you
applied before attempting to uninstall any previous CSDs. For example, if you
have installed CSD1, CSD2, and CSD3 on your machine and you want to
revert to the CSD1 level of code, you must first uninstall CSD3 and then
uninstall CSD2.

| See also “Removing New Era of Networks maintenance”.

| Applying New Era of Networks maintenance

| Ensure that all brokers are stopped before installing maintenance, and only
| restart them once installation is complete.

| From the directory of the CSD image enter the command:

| swinstall -s location_of_CSD neonsoft -x mount_all_filesystems=false

|
| Removing New Era of Networks maintenance
| To remove the New Era of Networks maintenance:
| 1. Run swremove, select Options —> Change Options... to list the remove
| options.
| 2. Unselect the Enforce dependency analysis errors in agent option and click OK.
| 3. Repeat this step for each New Era of Networks component that was added
| or patched by a CSD, starting with the highest numbered component,
| working down the list of components, and ending with the lowest
| numbered component. For example, n7nrfdk52, n6nrfx52, ..., n0infr2:
| Scroll to the component in the Software Selection menu. If the component
| was added by a CSD, then mark the component — the component is
| marked Yes. If the component was patched by a CSD, then press Enter to
| open the Software Selection sub-menu, and mark the specific patch level of

80 WebSphere MQ Integrator for HP-UX Installation Guide

 Removing New Era of Networks maintenance

| the component to be removed. Select ..(go up). The component is marked

| Partial. If a Dependency Message dialog appears when marking a full
| component or a component patch level for removal, ignore it and click
| OK.
| 4. Select Actions —> Remove (analysis)... —> OK —> Yes —> Done.
| Note that the information provided by the swlist -v command, after removal
| of a CSD, might not reflect the actual level of the code installed. However, if
| you run the swlist -i command and examine the names of the New Era of
| Networks components individually, you can see that the CSD has been
| successfully removed.

Applying maintenance to IBM DB2 Universal Database

If DB2 was installed on this system by the WebSphere MQ Integrator
installation program, it is installed with no service applied.

You can also obtain information about the current status of maintenance of
this product, and download fix packs for DB2 from the Web site identified in
“MQSeries information available on the Internet” on page 99.

Contacting your IBM Support Center

If you are unable to resolve problems that you find when you use WebSphere
MQ Integrator, or if you are directed to do so by an error message generated
by WebSphere MQ Integrator, you can request assistance from your IBM
support center.

Before you contact them, use the checklist below to gather key information.
Some items might not necessarily be relevant in every situation. But you
should provide as much information as possible to enable the IBM support
center to recreate your problem.
v For WebSphere MQ Integrator:
– CSDs applied.
– E-fixes applied.
– All current trace and error logs, including relevant HP-UX platform
syslog or Windows NT Event log entries. User trace log files at debug
level should be obtained for all relevant message flows and should
preferably be formatted.
– A list of the components installed. This should include details of the
number of machines and their operating systems, the number of brokers
and the machine on which they are running, and the existence and
details of any User Name Servers.

Appendix D. Applying maintenance 81

Contacting IBM

– The file obtained by exporting your workspace. This action is performed

from the Control Center; see the WebSphere MQ Integrator Using the
Control Center manual for details of how to do this.
– The files obtained by exporting all relevant message sets. This action is
performed for each message set by using the mqsiimpexpmsgset
command with the -e flag set.
– A sample of the messages being used when the problem arose.
– If relevant, the report file from the C or COBOL importer. This is located
in the directory from which the file import was attempted.
v For MQSeries:
– CSDs applied.
– E-fixes applied.
– All current trace and error logs, including relevant HP-UX platform
syslog or Windows NT Event log entries and First Failure Support
Technology™ (FFST™) output files. You can find these files, which have
the extension FDC, in the errors subdirectory within the MQSeries home
directory.
– Details of MQSeries client software, if appropriate.
v For each database you are using:
– Product and release level (for example, DB2 7.1).
– CSDs applied.
– E-fixes applied.
– All current trace and error logs, including relevant HP-UX platform
syslog or Windows NT Event log entries and FFST output files. Check
database product documentation for where to find these files.
v For HP-UX:
– Version. You can find the version of HP-UX installed by using the uname
-a command.
– Service level applied. Use the swlist command.
v For Windows NT:
– Version.
– Service Pack level.
– The version of the system files msvcrt.dll, msvcp60.dll, msvcirt.dll,
and mfc42.dll. You can find these files in the WINNT\SYSTEM32 directory.
Use the Windows NT Explorer file properties to display the versions.
v Details of the operation you were performing, the results that occurred, and
the results you were expecting.

82 WebSphere MQ Integrator for HP-UX Installation Guide

Appendix E. Notices
This information was developed for products and services offered in the
United States. IBM may not offer the products, services, or features discussed
in this information in other countries. Consult your local IBM representative
for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state
or imply that only that IBM product, program, or service may be used. Any
functionally equivalent product, program, or service that does not infringe
any IBM intellectual property right may be used instead. However, it is the
user’s responsibility to evaluate and verify the operation of any non-IBM
product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this information. The furnishing of this information does not give
you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the

IBM Intellectual Property Department in your country or send inquiries, in
writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106, Japan

The following paragraph does not apply to the United Kingdom or any
other country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY,
OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow
disclaimer of express or implied warranties in certain transactions, therefore
this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will
be incorporated in new editions of the information. IBM may make

© Copyright IBM Corp. 2000, 2002 83

Notices

improvements and/or changes in the product(s) and/or the program(s)

described in this information at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those
Web sites. The materials at those Web sites are not part of the materials for
this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the
purpose of enabling: (i) the exchange of information between independently
created programs and other programs (including this one) and (ii) the mutual
use of the information which has been exchanged, should contact:
IBM United Kingdom Laboratories,
Mail Point 151,
Hursley Park,
Winchester,
Hampshire,
England
SO21 2JN.

Such information may be available, subject to appropriate terms and

conditions, including in some cases, payment of a fee.

The licensed program described in this information and all licensed material
available for it are provided by IBM under terms of the IBM Customer
Agreement, IBM International Programming License Agreement, or any
equivalent agreement between us.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available
sources. IBM has not tested those products and cannot confirm the accuracy
of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products.

84 WebSphere MQ Integrator for HP-UX Installation Guide

 Notices

Trademarks
The following terms are trademarks of International Business Machines
Corporation in the United States, other countries, or both:

AIX AS/400
DB2 DB2 Universal Database
e-business Everyplace
FFST First Failure Support Technology
IBM IBMLink
MQSeries OS/390
SupportPac VSE/ESA
WebSphere z/OS

Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States, other countries, or
both.

Microsoft, Windows, and Windows NT are registered 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.

Other company, product, and service names may be trademarks or service

marks of others.

Appendix E. Notices 85
86 WebSphere MQ Integrator for HP-UX Installation Guide
Glossary of terms and abbreviations
This glossary defines WebSphere MQ broker domain. A collection of brokers that
Integrator terms and abbreviations used in share a common configuration, together with the
this book. If you do not find the term you single Configuration Manager that controls them.
are looking for, see the index or the IBM
Dictionary of Computing, New York: C
McGraw-Hill, 1994.
callback function. See implementation function.
This glossary includes terms and definitions
category. An optional grouping of messages that
from the American National Dictionary for are related in some way. For example, messages
Information Systems, ANSI X3.172-1990, that relate to a particular application.
copyright 1990 by the American National
Standards Institute. Copies may be ordered check in. The Control Center action that stores
from the American National Standards a new or updated resource in the configuration
Institute, 11 West 42 Street, New York, New or message repository.
York 10036. Definitions are identified by the
check out. The Control Center action that
symbol (A) after the definition. extracts and locks a resource from the
configuration or message repository for local
A modification by a user. Resources from the two
repositories can only be worked on when they
Access Control List (ACL). The list of principals are checked out by an authorized user, but can
that have explicit permissions (to publish, to be viewed (read only) without being checked
subscribe to, and to request persistent delivery of out.
a publication message) against a topic in the
topic tree. The ACLs define the implementation collective. A hyperconnected (totally connected)
of topic-based security. set of brokers forming part of a multi-broker
network for publish/subscribe applications.
ACL. Access Control List.
configuration. In the broker domain, the
AMI. Application Messaging Interface. brokers, execution groups, message flows and
message sets assigned to them, topics and access
Application Messaging Interface (AMI). The control specifications.
programming interface provided by MQSeries
that defines a high level interface to message Configuration Manager. A component of
queuing services. See also MQI and JMS. WebSphere MQ Integrator that acts as the
interface between the configuration repository
and an executing set of brokers. It provides
B brokers with their initial configuration, and
BLOB. Binary Large OBject. A block of bytes of updates them with any subsequent changes. It
data (for example, the body of a message) that maintains the broker domain configuration.
has no discernible meaning, but is treated as one
configuration repository. Persistent storage for
solid entity that cannot be interpreted.
broker configuration and topology definition.
broker. See message broker.
connector. See message processing node connector.

© Copyright IBM Corp. 2000, 2002 87

Glossary

content-based filter. An expression that is element. A unit of data within a message that
applied to the content of a message to determine has business meaning, for example, street name
how the message is to be processed.
element qualifier. A tag that is applied to an
context tag. See element qualifier. element within a message to enable that element
to be treated differently in different contexts. For
Control Center. The graphical interface that example, an element could be mandatory in one
provides facilities for defining, configuring, context and optional in another.
deploying, and monitoring resources of the
WebSphere MQ Integrator network. environment. User-defined variable information
associated with a message while it is being
processed by a message flow. This information
D can be created and used by nodes within the
datagram. The simplest form of message that message flow.
MQSeries supports. Also known as
ESM. External Security Manager.
send-and-forget. This type of message does not
require a reply. Compare with request/reply. ESQL. Extended SQL.
debugger. A facility on the Message Flows view exception list. A list of exceptions that have
in the Control Center that enables message flows been generated during the processing of a
to be debugged. message, with supporting information.
deploy. Make operational the configuration and execution group. A named grouping of message
topology of the broker domain. flows that have been assigned to a broker. The
broker is guaranteed to enforce some degree of
destination list. See local environment.
isolation between message flows in distinct
distribution list. A list of MQSeries queues to execution groups by ensuring that they execute
which a message can be put using a single in separate address spaces, or as unique
statement. processes.

Document Type Definition (DTD). The rules Extended SQL. A specialized set of SQL
that specify the structure for a particular class of functions and statements based on regular SQL,
SGML or XML documents. The DTD defines the extended with functions and statements unique
structure with elements, attributes, and notations, to WebSphere MQ Integrator.
and it establishes constraints for how each
Extensible Markup Language (XML). A W3C
element, attribute, and notation can be used
standard for the representation of data.
within the particular class of documents. A DTD
is analogous to a database schema in that the external reference. A reference within a
DTD completely describes the structure for a message set to a component that has been
particular markup language. defined outside the current message set. For
example, an integer that defines the length of a
DTD. Document Type Definition.
string element might be defined in one message
set but used in several message sets.
E
External Security Manager. A program that
e-business. A term describing the commercial provides security management for users and
use of the Internet and World Wide Web to resources on z/OS.
conduct business (short for electronic-business).

88 WebSphere MQ Integrator for HP-UX Installation Guide

 Glossary

F the components of the product installed by the

installation process on Windows NT systems.
field reference. A sequence of period-separated
values that identify a specific field (which might J
be a structure) within a message tree. An
example of a field reference might be something Java Database Connectivity (JDBC™). An
like Body.Invoice.InvoiceNo. application programming interface that has the
same characteristics as ODBC but is specifically
filter. An expression that is applied to the designed for use by Java database applications.
content of a message to determine how the
message is to be processed. Java Message Service (JMS). An application
programming interface that provides Java
format. A format defines the internal structure language functions for handling messages.
of a message, in terms of the fields and order of
those fields. A format can be self-defining, in JDBC. Java Database Connectivity.
which case the message is interpreted
dynamically when read. JMS. Java Message Service. See also AMI and
MQI.
G
L
graphical user interface (GUI). An interface to
a software product that is graphical rather than local environment. Information associated with
textual. It refers to window-based operational a message while it is being processed by a
characteristics. message flow. This information includes:
v User-defined variable information that can be
created and used by nodes within the message
I flow.
v A user-defined list of internal and external
IBM Developer Kit. IBM Developer Kit for the
destinations to which a message is sent. These
Java Platform, a software package that can be
can be nodes within a message flow (for
used to write, compile, debug, and run Java
example, when using the RouteToLabel and
applets and applications.
Label nodes) or MQSeries queues (when the
IBM Runtime Environment. IBM Runtime list is examined by an MQOutput node to
Environment for the Java Platform. A subset of determine the final target for the message).
the IBM Developer Kit for the Java Platform, that v A list of destinations to which a message has
contains the core executables and files that been sent. This list is created by an output
constitute the standard Java platform. The IBM node only if it is connected to another node in
Runtime Environment includes the Java Virtual the message flow.
Machine, core classes and supporting files.
Also known as destination list in previous
implementation function. Function written by a MQSeries Integrator releases. Destination list is
third-party developer for a plug-in node or valid and can be used for compatibility.
parser. Also known as a callback function.
local error log. A generic term that refers to the
input node. A message flow node that logs to which WebSphere MQ Integrator writes
represents a source of messages for the message records on the local system.
flow. v On UNIX systems, this is the syslog.
v On Windows NT, this is the Event Viewer
installation mode. The installation mode can be (Application View).
Full, Custom, or Broker only. The mode defines v On z/OS systems, this is the operator console.

Glossary of terms and abbreviations 89

Glossary

Entries written to this log include records that message processing node. A node in the
provide information about events that are not message flow, representing a well defined
errors, but that occur normally during operation, processing stage. A message processing node can
for example, successful deployment of a be one of several primitive types or can represent
configuration. a subflow.

Also known as system log. message processing node connector. An entity

that connects the output terminal of one message
processing node to the input terminal of another.
M A message processing node connector represents
the flow of control and data between two
message broker. A set of execution processes message flow nodes.
hosting one or more message flows.
message queue interface (MQI). The
messages. Entities exchanged between a broker programming interface provided by MQSeries
and its clients. queue managers. The programming interface
allows application programs to access message
message dictionary. A repository for
queuing services. See also AMI and JMS.
(predefined) message type specifications.
message repository. A database holding
message domain. The value that determines
message template definitions.
how the message is interpreted (parsed). The
following domains are recognized: message repository manager (MRM). A
v MRM, which identifies messages defined using component of the Configuration Manager that
the Control Center. handles message definition and control. A
v NEONMSG and NEON, which identify message defined to the MRM has a message
messages created using the New Era of domain set to MRM.
Networks user interfaces.
v XML, JMSMap, and JMSStream, which identify message set. A grouping of related messages.
messages that are self-defining.
v BLOB, which identifies messages that are message template. A named and managed
undefined. entity that represents the format of a particular
message. Message templates represent a business
You can also create your own message domains:
asset of an organization.
if you do so, you must supply your own
message parser. message type. The logical structure of the data
within a message. For example, the number and
message flow. A directed graph that represents
location of character strings.
the set of activities performed on a message or
event as it passes through a broker. A message metadata. Data that describes the characteristic
flow consists of a set of message processing of stored data.
nodes and message processing node connectors.
MQI. Message queue interface.
message flow component. See message flow.
MQIsdp. WebSphere MQ Integrator SCADA
message parser. A program that interprets the device protocol. A lightweight publish/subscribe
bit stream of an incoming message and creates protocol flowing over TCP/IP.
an internal representation of the message in a
tree structure, and that regenerates a bit stream MQRFH. An architected message header that is
for an outgoing message from the internal used to provide metadata for the processing of a
representation. message. This header is supported by MQSeries
Publish/Subscribe.

90 WebSphere MQ Integrator for HP-UX Installation Guide

 Glossary

MQRFH2. An extended version of MQRFH, point-to-point. Style of messaging application

providing enhanced function in message in which the sending application knows the
processing. destination of the message. Compare with
publish/subscribe.
MQSeries Everyplace. A generally available
MQSeries product that provides proven POSIX. Portable Operating System Interface For
MQSeries reliability and security in a mobile Computer Environments. An IEEE standard for
environment. computer operating systems (for example, AIX
and Solaris).
MRM. Message Repository Manager.
predefined message. A message with a
multilevel wildcard. A wildcard that can be structure that is defined before the message is
specified in subscriptions to match any number created or referenced. Compare with self-defining
of levels in a topic. message.

primitive. A message processing node that is

N supplied with the product.
node. See message processing node.
principal. An individual user ID (for example, a
log-in ID) or a group. A group can contain
O individual user IDs and other groups, to the
level of nesting supported by the underlying
ODBC. Open Database Connectivity. facility.

Open Database Connectivity. A standard property. One of a set of characteristics that

application programming interface (API) for define the values and behaviors of objects in the
accessing data in both relational and Control Center. For example, message processing
non-relational database management systems. nodes and deployed message flows have
Using this API, database applications can access properties.
data stored in database management systems on
a variety of computers even if each database publication node. An end point of a specific
management system uses a different data storage path through a message flow to which a client
format and programming interface. ODBC is application subscribes. A publication node has an
based on the call level interface (CLI) property, subscription point. If this is not
specification of the X/Open SQL Access Group. specified, the publication node represents the
default subscription point for the message flow.
output node. A message processing node that
represents a point at which messages flow out of publish/subscribe. Style of messaging
the message flow. application in which the providers of information
(publishers) are decoupled from the consumers
of that information (subscribers) using a broker.
P Compare with point-to-point. See also topic.
plug-in. An extension to the broker, written by publisher. An application that makes
a third-party developer, to provide a new information about a specified topic available to a
message processing node or message parser in broker in a publish/subscribe system.
addition to those supplied with the product. See
also implementation function and utility function.
Q
queue. An MQSeries object. Message queuing
applications can put messages on, and get

Glossary of terms and abbreviations 91

Glossary

messages from, a queue. A queue is owned and signature. The definition of the external
maintained by a queue manager. Local queues characteristics of a message processing node.
can contain a list of messages waiting to be
processed. Queues of other types cannot contain single-level wildcard. A wildcard that can be
messages: they point to other queues, or can be specified in subscriptions to match a single level
used as models for dynamic queues. in a topic.

queue manager. A system program that SQL. Structured Query Language.

provides queuing services to applications. It
provides an application programming interface stream. A method of topic partitioning used by
(the MQI) so that programs can access messages MQSeries Publish/Subscribe applications.
on the queues that the queue manager owns.
Structured Query Language. A programming
language that is used to define and manipulate
R data in a relational database. The language used
by WebSphere MQ Integrator, ESQL, is based on
retained publication. A published message that SQL, and has many similar constructs.
is kept at the broker for propagation to clients
that subscribe at some point in the future. subflow. A sequence of message processing
nodes that can be included within a message
request/reply. Type of messaging application in flow. A subflow does not have to include an
which a request message is used to request a input node or an output node, but can do so if
reply from another application. Compare with required.
datagram.
subscriber. An application that requests
rule. A rule is a definition of a process, or set of information about a specified topic from a
processes, applied to a message on receipt by the publish/subscribe broker.
broker. Rules are defined on a message format
basis, so any message of a particular format will subscription. Information held by a broker that
be subjected to the same set of rules. records the details of a subscriber application,
including the identity of the queue on which that
subscriber wants to receive relevant publications.
S
subscription filter. A predicate that specifies a
SCADA. Supervisory, Control, And Data subset of messages to be delivered to a particular
Acquisition. subscriber.
self-defining message. A message that defines subscription point. A property of a publication
its structure within its content. For example, a node that differentiates it from other publication
message coded in XML is self-defining. Compare nodes on the same message flow and therefore
with pre-defined message. represents a specific path through the message
flow. An unnamed publication node (that is, one
send and forget. See datagram.
without a specific subscription point) is known
setup type. The definition of the type of as the default publication node.
installation requested on Windows NT systems.
Supervisory, Control, And Data Acquisition. A
This can be one of Full, Broker only, or Custom.
broad term, used to describe any form of remote
shared. All configuration data that is shared by telemetry system used for gathering data from
users of the Control Center. This data is not remote sensor devices (for example, flow rate
operational until it has been deployed. meters on an oil pipeline) and for the near real
time control of remote equipment (for example,
pipeline valves).

92 WebSphere MQ Integrator for HP-UX Installation Guide

 Glossary

system log. See local error log. User Name Server. The WebSphere MQ
Integrator component that interfaces with
operating system facilities to determine valid
T users and groups.
terminal. The point at which one node in a
utility function. Function provided by
message flow is connected to another node.
WebSphere MQ Integrator for the benefit of
Terminals enable you to control the route that a
third-party developers writing plug-in nodes or
message takes, depending whether the operation
parsers.
performed by a node on that message is
successful.
W
topic. A character string that describes the
nature of the data that is being published in a warehouse. A persistent, historical datastore for
publish/subscribe system. events (or messages). The Warehouse node
within a message flow supports the recording of
topic based subscription. A subscription information in a database for subsequent
specified by a subscribing application that retrieval and processing by other applications.
includes a topic for filtering of publications.
wildcard. A character that can be specified in
topic security. The use of ACLs applied to one subscriptions to match a range of topics. See also
or more topics to control subscriber access to multilevel wildcard and single-level wildcard.
published messages.
wire format. This describes the physical
topology. In the broker domain, the brokers, representation of a message within the
collectives, and connections between them. bit-stream.
transform. A defined way in which a message W3C. World Wide Web Consortium. An
of one format is converted into one or more international industry consortium set up to
messages of another format. develop common protocols to promote evolution
and interoperability of the World Wide Web.
U
X
Uniform Resource Identifier. The generic set of
all names and addresses that refer to World Wide XML. Extensible Markup Language.
Web resources.

Uniform Resource Locator. A specific form of

URI that identifies the address of an item on the
World Wide Web. It includes the protocol
followed by the fully qualified domain name
(sometimes called the host name) and the
request. The Web server typically maps the
request portion of the URL to a path and file
name. Also known as Universal Resource
Locator.

URI. Uniform Resource Identifier

URL. Uniform Resource Locator

Glossary of terms and abbreviations 93

Glossary

94 WebSphere MQ Integrator for HP-UX Installation Guide

Bibliography
This section describes the documentation For further information about ordering
available for all current WebSphere MQ publications contact your IBM authorized
Integrator products. dealer or marketing representative.

WebSphere MQ Integrator Version 2.1 WebSphere MQ Integrator Version 2.1

cross-platform publications platform-specific publications
The WebSphere MQ Integrator Each WebSphere MQ Integrator product is
cross-platform publications are: documented in at least one platform-specific
v WebSphere MQ Integrator Introduction and publication, in addition to the family books.
Planning, GC34-5599 WebSphere MQ Integrator for AIX Version
v WebSphere MQ Integrator Using the Control 2.1
Center, SC34-5602 WebSphere MQ Integrator for AIX
v WebSphere MQ Integrator Messages, Installation Guide, GC34-5841
GC34-5601
WebSphere MQ Integrator for HP-UX
v WebSphere MQ Integrator Programming Version 2.1
Guide, SC34-5603
WebSphere MQ Integrator for
v WebSphere MQ Integrator Administration HP-UX Installation Guide,
Guide, SC34-5792 GC34-5907
v WebSphere MQ Integrator ESQL Reference,
WebSphere MQ Integrator for Sun Solaris
SC34-5923
Version 2.1
v WebSphere MQ Integrator Problem
WebSphere MQ Integrator for Sun
Determination Guide, GC34-5920
Solaris Installation Guide,
v WebSphere MQ Integrator Working with GC34-5842
Messages, SC34-6039
WebSphere MQ Integrator for Windows
These books are all available in hardcopy. NT and Windows 2000 Version 2.1
WebSphere MQ Integrator for
You can order publications from the Windows NT and Windows 2000
IBMLink™ Web site at: Installation Guide, GC34-5600
http://www.ibm.com/ibmlink WebSphere MQ Integrator for z/OS
Version 2.1
In the United States, you can also order
publications by dialing 1-800-879-2755. WebSphere MQ Integrator for z/OS
Customization and Administration
In Canada, you can order publications by Guide, SC34-5919
dialing 1-800-IBM-4YOU (1-800-426-4968). WebSphere MQ Integrator for z/OS
Program Directory, GI10-2536

© Copyright IBM Corp. 2000, 2002 95

Bibliography

MQSeries Everyplace publications v New Era of Networks Rules and Formatter

Support for WebSphere MQ Integrator
If you intend to connect MQSeries Formatter Programming Reference,
Everyplace applications to message flows SC34-6086
that include the MQSeries Everyplace
v New Era of Networks Rules and Formatter
message flow nodes, you will find the
Support for WebSphere MQ Integrator
following publications useful:
Application Development Guide, SC34-6082
v MQSeries Everyplace for Multiplatforms
Version 1.2 Introduction, GC34-5843 These books are provided in US English
v MQSeries Everyplace for Multiplatforms only.
Version 1.2 Programming Guide, SC34-5845
v MQSeries Everyplace for Multiplatforms
Softcopy books
Version 1.2 Programming Reference,
SC34-5846 All the WebSphere MQ Integrator books are
available in softcopy formats.
v MQSeries Everyplace for Multiplatforms
Version 1.2 Native Client Information, Portable Document Format (PDF)
SC34-5880 | The WebSphere MQ Integrator library is
| supplied in a searchable PDF package in US
You can find these books on the MQSeries | English only on the product CD. (This
Web site (see “MQSeries information | package excludes the WebSphere MQ
available on the Internet” on page 99). | Integrator for z/OS Program Directory.) The
Translated versions of these books are also | searchable PDF package is also supplied in
available in some languages from the same | the DOC directory on the product
Web site. | Supplemental CD. The contents of the DOC
| directory can be viewed without installing
New Era of Networks Rules and | the product.
Formatter Support for WebSphere MQ
Softcopy publications are not provided for
Integrator publications the z/OS operating system. If you have
The following publications are supplied on WebSphere MQ Integrator for z/OS Version
the product CD in PDF format, and are 2.1, refer to the softcopy publications
installed with the Documentation provided on the CD for Windows NT
component. They are also available in components.
hardcopy.
v New Era of Networks Rules and Formatter | The searchable PDF package comprises a set
Support for WebSphere MQ Integrator User’s | of panels, books, and index files that are
Guide, SC34-6084 | linked together to provide a stand-alone
| method of searching the WebSphere MQ
v New Era of Networks Rules and Formatter
| Integrator library. It contains the following
Support for WebSphere MQ Integrator
| usability enhancements:
System Management Guide, SC34-6083
| v One searchable index per book
v New Era of Networks Rules and Formatter
Support for WebSphere MQ Integrator Rules | v One searchable index file for the entire
Programming Reference, SC34-6085 | WebSphere MQ Integrator library

96 WebSphere MQ Integrator for HP-UX Installation Guide

 Bibliography

| v Logical page numbering of PDF files to | and Formatter Support for WebSphere MQ
| match printed books | Integrator) on a documentation CD (order
| v Full cross-referencing within books that | number SK3T–6922), which you can order
| allows you to jump to other parts of the | following general availability. (Not every
| same document | book is available in every supported
| language.)
| v Hyperlinked URLs to enable transparent
| integration with the Web
| PDF files can be viewed and printed using
| v An expandable list of PDF Bookmarks | the Adobe Acrobat Reader. To take
| that allows you to jump directly to a | advantage of the usability enhancements
| specific section within a book | provided in the searchable library, you will
| v Thumbnail images of all pages in the | need Adobe Acrobat Reader with Search
| book to allow you to scan for diagrams, | Version 4.05 on Windows NT, or Adobe
| tables, and so on | Acrobat Reader with Search Version 4.5 on
| UNIX systems. You are not recommended to
You can install the searchable PDF package | use this package with Adobe Acrobat
as follows: | Reader with Search Version 3.xx.
v On AIX, invoke install —d and select the
documentation fileset. After installation, If you need to obtain the Adobe Acrobat
run the command mqsidocs. This Reader, or would like up-to-date
launches Acrobat Reader and opens the information about the platforms on which
PDF package. the Acrobat Reader is supported, visit the
Adobe Systems Inc. web site at:
v On HP-UX, invoke swinstall —d and
select WMQI-DOCS from the menu. After http://www.adobe.com/
installation, run the command mqsidocs.
This launches Acrobat Reader and opens | If you want to generate your own
the PDF package. | searchable index files for this collection of
| PDF files, you will need Adobe Acrobat
v On Solaris, invoke pkgadd —d and select Catalog 4 (part of Adobe Acrobat Version 4).
|
wmqi-docs from the menu. After If you want to make your own softcopy
|
installation, run the command mqsidocs. annotations in the files, you will need the
|
This launches Acrobat Reader and opens full version of Adobe Acrobat Version 4
|
the PDF package. (formerly Adobe Acrobat Exchange Version
|
v On Windows NT, select the Online | 3.01).
Documentation component on a custom
installation, or do a full installation. After If you cut and paste examples of commands
installation, select from PDF files to a command line for
Start—>Programs—>IBM WebSphere MQ execution, you must check that the content
Integrator 2.1—>Documentation. is correct before you press Enter. Some
| Translated books for national language characters might be corrupted by local
| versions of this product are provided as system and font settings.
| stand-alone PDFs with the US English PDF
| package and stand-alone PDFs of US PDF versions of all current WebSphere MQ
| English books (for WebSphere MQ Integrator books are also available from the
| Integrator and New Era of Networks Rules MQSeries product family Web site at:
http://www.ibm.com/software/mqseries/

Bibliography 97
Bibliography

MQSeries publications section “MQSeries information available on

the Internet” on page 99).
The following books are referred to in this
book to point you to the information you
need to complete MQSeries Messaging MQSeries Publish/Subscribe
product tasks as part of WebSphere MQ publications
Integrator tasks.
If you have installed MQSeries
Publish/Subscribe, and plan to migrate to
For HP-UX installation tasks you might
WebSphere MQ Integrator Version 2, or to
need:
establish a mixed broker network, refer to:
v MQSeries for HP-UX Quick Beginnings,
v MQSeries Publish/Subscribe User’s Guide,
GC33-1869.
GC34-5269.
This book provides detailed planning and
installation guidance. This book and the MQSeries
Publish/Subscribe Software Development
For Windows NT installation tasks you Kit (SDK) package are available on the
might need: MQSeries Web site. The URL is given in the
v MQSeries for Windows NT and Windows section “MQSeries information available on
2000 Quick Beginnings, GC34-5389. the Internet” on page 99).

For planning and configuration tasks you

might need: MQSeries Workflow publications
v MQSeries MQSC Command Reference, The MQSeries Workflow product has a
SC33-1369. comprehensive library. Refer to the
following book for introductory information,
This book contains the syntax of the
and for details about other product
MQSC commands.
publications:
v MQSeries System Administration,
v IBM MQSeries Workflow Concepts and
SC33-1873.
Architecture, GH12-6285.
This book supports day-to-day
management of local and remote For a complete list of MQSeries Workflow
MQSeries objects. product publications, refer to the
v MQSeries Clients, GC33-1632. information on the MQSeries Web site. The
This book describes how to install, URL is given in the section “MQSeries
configure, use, and manage MQSeries information available on the Internet” on
clients. page 99).
v MQSeries Intercommunication, SC33-1872.
This book describes MQSeries DB2 publications
Intercommunication between different The following DB2 publications are
platforms. referenced in this book.
v IBM DB2 Quick Beginnings, GC09-2835.
For a complete list of MQSeries product
publications, refer to the information on the v IBM DB2 Message Reference, GC09-2846.
MQSeries Web site. The URL is given in the v IBM DB2 TroubleShooting Guide, SI0J-8169.

98 WebSphere MQ Integrator for HP-UX Installation Guide

 Bibliography

You can download these publications from

the DB2 Web site at
http://www.ibm.com/software/db2

MQSeries information available on

the Internet
The MQSeries product family Web site is at:
http://www.ibm.com/software/mqseries/

By following links from this Web site you

can:
v Obtain latest information about the
MQSeries product family.
v Access the MQSeries books in HTML and
PDF formats.
v Obtain information about complementary
offerings by following these links:
– IBM Business Partners
– Partner Offerings (within Related links)
v Download an MQSeries SupportPac.
| v Access Redbooks.

Bibliography 99
MQSeries on the Internet

100 WebSphere MQ Integrator for HP-UX Installation Guide

Index
A C D
Adobe Acrobat 12 channels database samples 11
application programming support 6 defining 48 database tables 69
Applying New Era of Networks starting 48 database, setting up on HP-UX 25
maintenance 80 checking components exist 46 databases
assigning a message flow 64 checking kernel settings 17 authorization 40
authorizations CLASSPATH 68 connecting to 37
DB2 40 code page support 7 creating 37
MQSeries on HP-UX 13 codeset customizing 41
MQSeries on Windows NT 13 New Era of Networks Rules and DB2 5, 24
WebSphere MQ Integrator 13 Formatter Support 9 for broker 5
other products 9 for user data 5
B support 9 granting access 40
broker 10 Command Assistant Heap Size 41
connecting to the broker locales 33 Oracle 73
domain 50 complementary offerings supported by New Era of
creating 44 IBM Business Partners 99 Networks Rules and Formatter
database tables 46 Partner Offerings 99 Support 6
starting 49 Configuration Manager 1, 43 table contents 69
broker database 5 creating 42 using DB2 35
broker domain starting 49 DB2 8
changes after installation 67 configuring a broker domain 29, 34 applying maintenance 81
checking the configuration 56 MQSeries ports 34 creating a database 37
Configuration Manager 1 resource names 34 creating an instance 15, 37
configuring 29, 34, 41 TCP/IP hostnames 34 creating the ODBC
Control Center 1 user IDs 34 connection 38
creating a broker 44 connecting channels between queue db2install 24, 37
creating the Configuration managers 50, 63 db2setup 24
Manager 42 connecting queue managers 50, 63 installation 24
database authorizations 40 connecting to a database 37 publications 98
database setup 37 connectivity requirements 5, 11 defining a channel 48
defining channels 48 contents of CDs 9 defining a transmission queue 48
defining the transmission Control Center 1 deploying a message flow 65
queue 48 starting 49 deploying configuration changes 56
deploying configuration creating directory structure 67
changes 56 a Configuration Manager 41 disk space requirements 4
message broker 1 a database 37 documentation 9, 12
starting 46 a product code file system 17
starting a broker 49 brokers 41, 44 E
starting channels 48 Configuration Manager 42 environment variables
starting MQSeries listeners 47 message flows 63 CLASSPATH 68
starting the Configuration queues 53, 63 ICU_DATA 68
Manager 49 user and group IDs 15 LANG 68
starting the Control Center 49 creating a product code file LC_ALL 68
user IDs 36 system 17 LD_LIBRARY_PATH 68
User Name Server 1 creating a user ID 15 MQSI_PARAMETERS_FILE 68
creating user and group IDs 15 MQSI_PRELOAD 68
MQSI_REGISTRY 68
NLSPATH 68

© Copyright IBM Corp. 2000, 2002 101

environment variables (continued) instance name, DB2 37
NN_CONFIG_FILE_PATH 68 integration 15
N
National Language Support 7, 11
NNSY_CATALOGUES 68
NNSY_ROOT 68 J New Era of Networks interface 12
New Era of Networks Rules and
ODBCINI 68 Java Runtime Environment 43
Formatter Support 6
PATH 68
Event viewer 43, 47 L code page support restrictions 8
LANG 68 installation 23
F LC_ALL 68 installing 22
New Era of Networks Rules and
file systems for product code 17 LD_LIBRARY_PATH 68
license agreement 7 Formatter Support
G WebSphere MQ Integrator 23 publications 96
groups, listeners, NLS message catalogs 11
creating 13, 15, 36 starting 47 NLSPATH 68
locales NN_CONFIG_FILE_PATH 68
H with the Command Assistant 33 NNSY_CATALOGUES 68
hardware requirements 3 Log view, NNSY_ROOT 68
Heap Size 41 Control Center 56, 65
O
I M ODBC 74
IBM Business Partners 99 maintenance ODBC connection, defining 39
ICU-DATA 68 CSDs 79 ODBCINI 68
information on the Internet installing 79 online documentation 11, 12
complementary offerings 99 updates 79 Oracle database 73
MQSeries family libraries 99 message brokers 1 Oracle ODBC 74
MQSeries products 99 message catalog
MQSeries SupportPacs 99 NLV 7
P
install, from a server machine 25 Partner Offerings 99
plug-ins 7
installation PATH 68
z/OS 7
disk space requirements 4 PDF (Portable Document
message flows
from a server 25 Format) 96
assigning to broker 64
from the product CD 19 PDF files 12
creating 63
hardware requirements 3 plug-in products 11
deploying 65
network protocols 5 plug-ins, message catalog 7
testing 65
optional products 5 Portable Document Format
message repository, ODBC
overview 1 (PDF) 96
connection 39
pre-installation tasks 15 post-installation
message sets, importing 54
preparing for 15 directory structure 67
migration 15
prerequisites 4, 19 post-installation tasks
mqbrkrs group 13, 15, 17, 24, 34
procedure 21 tasks 2
adding a new user 36
product package 9 Postcard application
mqm group 13, 15, 17, 24
SAM program 23 how to run it 62
adding a new user 36
security 13 how to start it 61
mqm user 24
shared CD directory 26 pre-installation planning 3
MQSeries Everyplace
software requirements 4 pre-installation tasks 15
publications 96
unattended 19 prerequisites 4
MQSeries ports 34
verification 53 product components 11
MQSeries publications 98
installation errors, resolving 27 broker 10
MQSeries Publish/Subscribe
installing New Era of Networks 22
publications 98
Configuration Manager 2 online documentation 12
MQSeries resources 46, 71
Control Center 2 primary 10
MQSeries Workflow
DB2 24 runtime 10
publications 98
message broker 1 Samples and SDK 11
MQSeries, NLV support 8
New Era of Networks Rules and secondary 10
MQSI_PARAMETERS_FILE 68
Formatter Support 22, 23 User Name Server 11
MQSI_REGISTRY 68
runtime support 1 product package, contents 9

102 WebSphere MQ Integrator for HP-UX Installation Guide

publications
DB2 98
T
TCP/IP hostnames 34
MQSeries 98
testing a message flow 65
MQSeries Everyplace 96
Topology 55, 56, 63
MQSeries Publish/Subscribe 98
transmission queue, defining 48
MQSeries Workflow 98
WebSphere MQ Integrator 95 U
unattended installation 26
R uninstalling WebSphere MQ
Redbooks 99
Integrator 77
remote installation 19, 25
uninstalling,
setting up the server
before you start 77
machine 25
UNIX authorizations 13
setting up the target machine 26
user IDs
removing WebSphere MQ
authorizing database access 40
Integrator 77
user IDs and groups
Requesting support 81
MQSeries Integrator 15, 36
resolving installation errors 27
MQSeries on HP-UX 15
resource ownership 17
MQSeries on Windows NT 15
restoring a service level 80
NIS or local 15
running verification applications 56
User Name Server 1, 11, 35
runtime support 1

S V
verification applications 56
SAM program 23
Postcard 60
sample applications 11, 56
Scribble 59
sample profiles 11
Soccer 56
Scribble application
verifying an installation 53
how it works 60
creating MQSeries resources 53
how to start it 59
defining a message flow 63
SDK 11
deploying assignments 65
secondary components
importing message sets 54
NLS message catalogs 11
running sample applications 56
online documentation 11
sample applications 11
Software Developers’ Kit 11
W
WebSphere MQ Integrator on the
server installation 25 Internet 99
setting kernel parameter values 17 WebSphere MQ Integrator
setting up a broker domain 29 publications 95
silent installation 26 national language 97
Soccer application platform–specific 95
how it works 57 Windows 2000 x
how to start it 57 Windows NT Event viewer 49
softcopy books 96
software requirements 4
starting a broker 49
starting the Configuration
Manager 49
supported codesets 9
SupportPac 99
swinstall 27
swremove 79
syslog, configuring on HP-UX 44
system setup 3

Index 103
104 WebSphere MQ Integrator for HP-UX Installation Guide
Sending your comments to IBM
If you especially like or dislike anything about this book, please use one of
the methods listed below to send your comments to IBM.

Feel free to comment on what you regard as specific errors or omissions, and
on the accuracy, organization, subject matter, or completeness of this book.

Please limit your comments to the information in this book and the way in
which the information is presented.

To make comments about the functions of IBM products or systems, talk to

your IBM representative or to your IBM authorized remarketer.

When you send comments to IBM, you grant IBM a nonexclusive right to use
or distribute your comments in any way it believes appropriate, without
incurring any obligation to you.

You can send your comments to IBM in any of the following ways:
v By mail, to this address:
User Technologies Department (MP095)
IBM United Kingdom Laboratories
Hursley Park
WINCHESTER,
Hampshire
SO21 2JN
United Kingdom
v By fax:
– From outside the U.K., after your international access code use
44–1962–816151
– From within the U.K., use 01962–816151
v Electronically, use the appropriate network ID:
– IBM Mail Exchange: GBIBM2Q9 at IBMMAIL
– IBMLink: HURSLEY(IDRCF)
– Internet: idrcf@hursley.ibm.com

Whichever method you use, ensure that you include:

v The publication title and order number
v The topic to which your comment applies
v Your name and address/telephone number/fax number/network ID.

© Copyright IBM Corp. 2000, 2002 105

106 WebSphere MQ Integrator for HP-UX Installation Guide



Printed in the United States of America

on recycled paper containing 10%
recovered post-consumer fiber.

GC34-5907-02