Messaging engines [Settings]

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 > engine_name .

Configuration tab

Configuration properties for this object. These property values are preserved even if the runtime environment is stopped then restarted. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

General properties

Name

The name of the messaging engine.

Required No
Data type Text

UUID

The universal unique identifier assigned by the system to this messaging engine for administrative purposes.

Required No
Data type Text

Description

An optional description for the messaging engine, for administrative purposes.

Required No
Data type Text area

Initial state

The initial state determines whether the messaging engine is started automatically.

Required No
Data type drop-down list
Range
Stopped
When the associated application server is started, the messaging engine is stopped and is not available to process messages.

Started
When the associated application server is started, the messaging engine is started and is available to process messages.

Message store type

The type of message store used. Either file store or data store. Once the messaging engine has been created this cannot be changed, only configured.

Required No
Data type Custom

High message threshold

The number of messages queued on a message point on this messaging engine, at which point new messages are not accepted on the message point. However, certain messages that are already in the bus and that are being transmitted to this messaging engine might be accepted.

When the messaging engine is created, the high message threshold of the bus is used to set the default value for this property. When a message point is created on this messaging engine, the value of this property is used to set the default high message threshold for the message point.
Note: There are implications for the Java Virtual Machine (JVM) heap size when using a high message threshold, if large numbers of messages are held on a queue (each message consumes approximately 200 bytes of storage). Therefore, if you increase the high message threshold because you expect large numbers of messages on your queues, you must also modify the JVM heap size of the server as appropriate.
Required No
Data type Long
Range 0 through 2147483647

Target groups

A list of names of target groups with which the messaging engine will register.

Custom target groups are a type of target group used by JMS connection factories. When an application creates a connection to a service integration bus, it uses connection factory properties to specify suitable messaging engines to connect to. When a target type of "Custom" is specified in the connection factory targetType property, the application will be connected to one of the messaging engines in the specified custom target group. A particular messaging engine is selected from the group according to the other connection factory properties that have been specified
Required No
Data type Text area

Bus name

The name of the service integration bus on which the messaging engine is configured.

Required No
Data type Text

Bus UUID

The universal unique identifier of the service integration bus on which the messaging engine is configured.

Required No
Data type Text

Additional properties

Mediation thread pool
The thread pool for allocating mediation handler threads.
Mediation execution points
Displays a list of mediation execution points assigned to this destination.
Custom properties
Arbitrary name-value pairs of data, where the name is a property key and the value is a string value that can be used to set internal system configuration properties. Defining a new property enables you to configure a setting beyond that which is available in the administrative console.
Service integration bus links
A communications link between this messaging engine and a messaging engine in a foreign service integration bus.
WebSphere® MQ links
Links between the messaging engine and WebSphere MQ networks. Each WebSphere MQ link connects the messaging engine as a queue manager to WebSphere MQ, thereby providing a bridge between the bus and a WebSphere MQ network.
WebSphere MQ client links
A WebSphere MQ client link enables JMS client applications to connect, via this messaging engine, to the service integration bus, as though it were a WebSphere MQ queue manager.

Message points

Queue points
A queue point is created on each messaging engine to which a point-to-point destination is assigned. It is used to hold messages pending delivery to receiving applications.
Publication points
A publication point is created on each messaging engine in the bus when a publish/subscribe destination is created. The publication point on a messaging engine is used to hold messages published by applications connected to that messaging engine until they are delivered to subscribers.
Mediation points
A mediation point is created on each messaging engine to which the mediation of a mediated destination is assigned. It is used to hold messages pending delivery to the mediation.

Runtime tab

Runtime properties for this object. These properties directly affect the current runtime environment, but are not preserved when that environment is stopped. To preserve runtime property values, change the equivalent property values on the Configuration tab. See the information center task descriptions for information about how to apply configuration changes to the runtime environment.

General properties

Status

Whether the messaging engine is currently started or stopped.

To be able to retrieve the status of messaging engines, you must be logged into the administrative console with at least monitor authority. If you do not have this authority, the messaging engine status is displayed as "Unavailable", even if the messaging engine has started.
Required No
Data type Text

Message points

Queue points
A queue point is created on each messaging engine to which a point-to-point destination is assigned. It is used to hold messages pending delivery to receiving applications.
Publication points
A publication point is created on each messaging engine in the bus when a publish/subscribe destination is created. The publication point on a messaging engine is used to hold messages published by applications connected to that messaging engine until they are delivered to subscribers.
Mediation points
A mediation point is created on each messaging engine to which the mediation of a mediated destination is assigned. It is used to hold messages pending delivery to the mediation.

Remote message points

Remote queue points
The remote queue points that are producing/consuming messages to/from queue points on remote messaging engines.
Remote mediation points
The remote mediation points that are producing messages for mediation points on remote messaging engines.
Remote publication points
The remote publication points that are producing messages for publication points on remote messaging engines.



Reference topic Reference topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=SIBMessagingEngine_DetailForm
File name: SIBMessagingEngine_DetailForm.html