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 they access a service integration bus.
To view this page in the console, click the following path:
.
The Configuration tab shows 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.
The name of the messaging engine.
Information | Value |
---|---|
Required | No |
Data type | String |
The universal unique identifier assigned by the system to this messaging engine for administrative purposes.
Information | Value |
---|---|
Required | No |
Data type | String |
An optional description for the messaging engine, for administrative purposes.
Information | Value |
---|---|
Required | No |
Data type | Text area |
The initial state determines whether the messaging engine is started automatically.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
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.
Information | Value |
---|---|
Required | No |
Data type | drop-down list |
Range |
|
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.
Information | Value |
---|---|
Required | No |
Data type | Integer |
Range | 1 through 9223372036854775807 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 are expecting large numbers of messages on
your queues, you should also modify the JVM heap size of the server
as appropriate.
|
The time delay, in milliseconds, that is introduced by the system under certain circumstances before a failed message delivery to an application will be retried. This delay can be overridden by individual Queue destination configurations.
When you configure a bus destination, you can specify an associated exception destination and a maximum number of times that an individual message fails to be consumed before it is put on that exception destination. Alternatively, if you do not specify an associated exception destination, the system continues to try to deliver the message. In this situation, the system attempts to deliver the message, without applying any delay, until it reaches the maximum failed deliveries limit set for the bus destination (a queue or a topic space). After the maximum failed deliveries limit is reached, the default blocked destination retry interval is applied before the message is retried.
The Default blocked destination retry interval specifies the time interval between retry attempts, which will be used by all queue and topic destinations that are associated with this messaging engine. You can override this default value when you configure an individual queue or topic destination.
Information | Value |
---|---|
Required | No |
Data type | Integer (milliseconds) |
Default | The value taken from the sib.processor.blockedRetryTimeout custom property, if set. Otherwise it is set to 5000. |
Range | 1 through 9223372036854775807 |
A list of names of target groups with which the messaging engine will register.
Information | Value |
---|---|
Required | No |
Data type | Text area |
The name of the service integration bus on which the messaging engine is configured.
Information | Value |
---|---|
Required | No |
Data type | String |
The universal unique identifier of the service integration bus on which the messaging engine is configured.
Information | Value |
---|---|
Required | No |
Data type | String |
The Runtime tab shows 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.
The current status of the messaging engine. Status settings are started or stopped.
Information | Value |
---|---|
Required | No |
Data type | String |