Messaging engines [Collection]

A messaging engine is a component, running inside a server, that manages messaging resources for a bus member. Applications are connected to a messaging engine when accessing a service integration bus.

To view this pane in the console, click the following path:

Service integration > Buses > [Content Pane] bus_name > [Topology] Messaging engines.

To browse or change the properties of a listed item, select its name in the list.

To act on one or more of the listed items, select the check boxes next to the names of the items that you want to act on, then use the buttons provided.

To change which entries are listed, or to change the level of detail that is displayed for those entries, use the Filter settings.

General properties

Name
The name of the messaging engine.
Description
An optional description for the messaging engine, for administrative purposes.
Status
Whether the messaging engine is currently started or stopped.

Buttons

Start Start the selected items.
Stop Stop a selected messaging engine. You must first have selected the messaging engine to be stopped.
You can choose the mode of stop action:
Stop mode:
Immediate
The messaging engine is stopped on completion of all messaging operations that are being carried out at the time of the stop request. After a stop command has been issued, the messaging engine does not allow any new operations to be started.

For each existing connection, the messaging engine waits for the current operation to complete, unless the operation is one that blocks within the messaging engine, such as a receive operation. In this case, the operation is interrupted. Asynchronous consumers are allowed to complete even though they may take an arbitrary amount of time to process the current message. The messaging engine then backs out of active transactions and disallows any further operations on that connection. When all connections are in this invalidated state, the messaging engine stops.

Force
The messaging engine is stopped without allowing messaging operations to complete and applications are forcefully disconnected.

The intention of force mode is to complete the shutdown of the messaging engine in as short a time as possible. A subsequent restart of the messaging engine may take longer than if it had been stopped using immediate mode, because more recovery actions are needed. For example, force mode stop can leave messages in-doubt and you will need to deal with these messages to resolve any in-doubt transactions.

Tip: If an immediate stop is taking too long, you can escalate it to a force stop by selecting the Forced option. This overrides your previous selection of the Immediate option.



Reference topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 6:22:59 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-express-dist&topic=SIBMessagingEngine_CollectionForm
File name: SIBMessagingEngine_CollectionForm.html