Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

Chapter 7. WebSphere Integration Brokers Monitoring 251

– Stop and start the agent using the CandleAgent commands in

Example 7-11.

Example 7-11 Stop and start the agent

./CandleAgent -o WBRK_BROKER1 -p BRK1 stop qi

./CandleAgent -o WBRK_BROKER1 -p BRK1 start qi

7.12.2 Working with the CandleMonitor Node

The CandleMonitor node can be customized to control how it functions using the

following information.

򐂰 Customizing the CandleMonitor Node

– This allows the behavior of the CandleMonitor node to be controlled.

– Changes to these variables require a restart of the broker to take effect.

– All variable names and values are case sensitive.

– On Windows, the variables are stored in the registry.

• Modify the variables using Manage Candle Services.

• Right-click the primary agent and select Advanced → Edit Variables.

•Select Edit or Add, depending on the current settings.

– On UNIX and z/OS, these variables are stored in a configuration file

named kqipnode.cfg.

• UNIX location: CANDLEHOME/platform-version/qi/bin. In our

environment, this would be /candle/aix433/qi/bin/kqipnode.cfg.

• z/OS location: HFS directory CANDLEHOME/kqi/lil.

– The variables and values are detailed in Table 7-6 on page 252.

252 Implementing IBM Tivoli OMEGAMON XE for WebSphere Business Integration V1.1

Table 7-6 CandleMonitor node variables

Variable name Description

KQIMemorySize The size in bytes of a shared memory

segment created by the plug-in. The

plug-in actually creates three of these for

holding different types of data. The

default value is 32768 bytes. Only modify

this value at the direction of from IBM

Software Support.

KQITempDirectory The full directory path name to be used for

shared memory and mutexes. The broker

and the agent must have the ability to

create files in, write, and read this

directory. The default is /tmp. It is not

available on Windows.

KQINodeTrace Specifies whether or not kqipnode.lil

tracing is turned on. The possible values

are Off and On. The default is Off. For

tracing to actually occur, the broker’s

normal tracing must be turned on for the

applicable broker, execution group, or

message flow.

Chapter 7. WebSphere Integration Brokers Monitoring 253

KQIActivateNode This parameter provides an override

capability for the CandleMonitor node

activateNode attribute for any broker on

the system. The default is NoOverride.

Possible values are:

򐂰 NoOverride: The value of the

activateNode attribute deployed for

each instance of the CandleMonitor

node is honored; no override takes

place.

򐂰 Yes: Every instance of the

CandleMonitor node is activated.

򐂰 No: All instances of the

CandleMonitor node are deactivated.

No statistics or message flow events

are generated.

򐂰 EventOnly: An instance of

CandleMonitor node is activated only

if the eventMessage attribute is

assigned. No statistics are produced,

only message flow events.

򐂰 InputOutputOnly: An instance of the

CandleMonitor node is activated only

if the type is input or output. Statistics

are generated (and events, if the

eventMessage attribute is assigned).

򐂰 InputOutputAndEventOnly: Instances

of CandleMonitor node are activated

only if the type is input or output, or if

the eventMessage attribute is

assigned. Statistics are produced, and

message flow events are produced if

the eventMessage attribute is

assigned.

KQIActivateNodeForBrokerName Provides the same override capability as

KQIActivateNode, except that it applies

only to the named broker. This overrides

the KQIActivateNode for the specified

broker. This variable does not exist in the

kqipnode.cfg file (UNIX and z/OS) or in the

Windows drop down and it must be added

by the user.

Variable name Description