WebSphere Message Broker startDataFlowEngine process appears alongside DataFlowEngine process.

Technote (FAQ)


Question

When starting a WebSphere Message Broker (WMB), you want to know why you see a startDataFlowEngine process appear along with the DataFlowEngine process. This process will not terminate until the DataFlow Engine process has ended.

Cause

You will only see the startDataFlowEngine process running for the Broker if new functionality is delivered in Fix Packs and enabled via the mqsichangebroker command.

This can be verified using the mqsireportbroker command.


Answer

In WMB V7.0 Fix Pack 2, Execution Group profile support was introduced, allowing users to specify different environment variable settings at an execution group level. As part of this implementation, the AdminAgent when starting an Execution Group ( EG) actually now invokes the startDataFlowEngine script which in turn will start the DataFlowEngine process.

The startDataFlowEngine script can run the EG profile before starting the DataFlowEngine process. Both processes should remain running.

The AdminAgent will be monitoring the startDataFlowEngine process. If it dies unexpectedly, the AdminAgent will restart it. Killing the startDataFlowEngine script will therefore result in duplicate DataFlowEngine processes unless BOTH the DataFlowEngine and startDataFlowEngine process are killed together.

This design exists for WebSphere Message Broker V7.0.0.2 or later and in V8.0 or later.


Product Alias/Synonym

WMB MB Message Broker MQ Integrator WBIMB WBI-MB MQSI WMQI

Rate this page:

(0 users)Average rating

Document information


More support for:

WebSphere Message Broker
Broker

Software version:

7.0, 7.0.0.2, 8.0

Operating system(s):

AIX, Linux, Solaris, z/OS

Reference #:

1587240

Modified date:

2013-06-20

Translate my page

Machine Translation

Content navigation