Messaging Engine (messagingEngine)

A messaging engine is a component, running inside a server, that manages messaging resources. Applications are connected to a messaging engine when they send and receive messages.

alias
Description: An alias destination maps an alternative name for a bus destination. You can use an alias destination for point-to-point messaging or publish/subscribe messaging.
Required: false
Data type:
Attribute name Data type Default value Description
forceReliability
  • AssuredPersistent
  • BestEffortNonPersistent
  • ReliableNonPersistent
  • ExpressNonPersistent
  • ReliablePersistent
AssuredPersistent The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
AssuredPersistent
AssuredPersistent
BestEffortNonPersistent
BestEffortNonPersistent
ReliableNonPersistent
ReliableNonPersistent
ExpressNonPersistent
ExpressNonPersistent
ReliablePersistent
ReliablePersistent
id string   The name of the alias queue or alias topic space.
sendAllowed
  • false
  • true
true Producers can send messages to this destination.
false
false
true
true
targetDestination string Default.Queue The target destination parameter identifies a destination that might be within the same Bus as the alias destination. By default, if no property is set, it points to Default.Queue.
fileStore
Description: Messaging file store.
Required: false
Data type:
Attribute name Data type Default value Description
fileStoreSize long

Minimum: 20

400 The combined size in megabytes for both permanent and temporary store. The file store size is equally divided between permanent and temporary store. For example, if you specify 400 MB as file store size then 200 MB is used for permanent store and 200 MB is used for temporary store.
logFileSize long

Minimum: 10

10 Size in megabytes of the log file. The log file size can be utmost half of the size of the file store. The recommended log file size is 25% of the file store size. For example, if the file store size is set to 400 MB then the log file size cannot exceed more than 200 MB. In this example the recommended value for the log file size will be 100 MB.
path string ${server.output.dir}/messaging/messageStore Path to the file store.
messagingSecurity
Description: Security for the wasJmsServer-1.0 feature.
Required: false
Data type:
messagingSecurity > role
Description: A set of permissions mapped to the users and groups
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
name string   The name of the role
messagingSecurity > role > group
Description: Groups that are assigned to the role
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
name string   The group that is defined as part of the user registry
messagingSecurity > role > queuePermission
Description: Permission defined on a queue for a set of users and groups
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
queueRef string   Reference to the Queue defined in the Messaging Engine
messagingSecurity > role > queuePermission > action
Description: Operations which are allowed on the destination
Required: false
Data type:
messagingSecurity > role > tempDestinationPermission
Description: Permission defined on a temporary destination for a set of users and groups
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
prefix string   Prefix defined for a temporary destination
messagingSecurity > role > tempDestinationPermission > action
Description: Operations which are allowed on the destination
Required: false
Data type:
messagingSecurity > role > topicPermission
Description: Permission defined on a topic for a set of users and groups
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
topicName string   Name of the Topic inside the TopicSpace
topicSpaceRef string Default.Topic.Space Reference to the TopicSpace defined in the Messaging Engine
messagingSecurity > role > topicPermission > action
Description: Operations which are allowed on the destination
Required: false
Data type:
messagingSecurity > role > user
Description: Users that are assigned to the particular role
Required: false
Data type:
Attribute name Data type Default value Description
id string   A unique configuration ID.
name string   The user that is defined as part of the registry
queue
Description: A queue destination represents a message queue and is used for point-to-point messaging.
Required: false
Data type:
Attribute name Data type Default value Description
exceptionDestination string _SYSTEM.Exception.Destination The destination to which a message is forwarded by the system when it cannot be delivered to this destination.
failedDeliveryPolicy
  • KEEP_TRYING
  • SEND_TO_EXCEPTION_DESTINATION
  • DISCARD
SEND_TO_EXCEPTION_DESTINATION Lists the actions that the messaging engine must take when the maxredeliverycount is reached for a message.
KEEP_TRYING
KEEP_TRYING
SEND_TO_EXCEPTION_DESTINATION
SEND_TO_EXCEPTION_DESTINATION
DISCARD
DISCARD
forceReliability
  • AssuredPersistent
  • BestEffortNonPersistent
  • ReliableNonPersistent
  • ExpressNonPersistent
  • ReliablePersistent
AssuredPersistent The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
AssuredPersistent
AssuredPersistent
BestEffortNonPersistent
BestEffortNonPersistent
ReliableNonPersistent
ReliableNonPersistent
ExpressNonPersistent
ExpressNonPersistent
ReliablePersistent
ReliablePersistent
id string   The name of the queue.
maintainStrictOrder boolean false Maintains the order in which a producer sends messages to the destination.
maxMessageDepth long

Minimum: 1

50000 The maximum number of messages that the messaging engine can place on its message points.
maxRedeliveryCount int 5 The maximum number of failed attempts to process a message. After this number of failed attempts, if an exception destination is configured, the message is forwarded from the intended destination to its exception destination. If an exception destination is not configured, a time interval between retry attempts is applied.
receiveAllowed boolean true Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.
redeliveryInterval long 5000 When no exception destination is configured, the time interval to apply between retry attempts, after the maximum failed deliveries limit is reached, for this destination.
sendAllowed boolean true Producers can send messages to this destination.
topicSpace
Description: A topic space destination represents a set of "publish and subscribe" topics and is used for publish/subscribe messaging.
Required: false
Data type:
Attribute name Data type Default value Description
exceptionDestination string _SYSTEM.Exception.Destination The destination to which a message is forwarded by the system when it cannot be delivered to this destination.
failedDeliveryPolicy
  • KEEP_TRYING
  • SEND_TO_EXCEPTION_DESTINATION
  • DISCARD
SEND_TO_EXCEPTION_DESTINATION Lists the actions that the messaging engine must take when the maxredeliverycount is reached for a message.
KEEP_TRYING
KEEP_TRYING
SEND_TO_EXCEPTION_DESTINATION
SEND_TO_EXCEPTION_DESTINATION
DISCARD
DISCARD
forceReliability
  • AssuredPersistent
  • BestEffortNonPersistent
  • ReliableNonPersistent
  • ExpressNonPersistent
  • ReliablePersistent
AssuredPersistent The reliability assigned to a message produced to this destination when an explicit reliability has not been set by the producer.
AssuredPersistent
AssuredPersistent
BestEffortNonPersistent
BestEffortNonPersistent
ReliableNonPersistent
ReliableNonPersistent
ExpressNonPersistent
ExpressNonPersistent
ReliablePersistent
ReliablePersistent
id string   The name of the topic space.
maintainStrictOrder boolean false Maintains the order in which a producer sends messages to the destination.
maxMessageDepth long

Minimum: 1

50000 The maximum number of messages that the messaging engine can place on its message points.
maxRedeliveryCount int 5 The maximum number of failed attempts to process a message. After this number of failed attempts, if an exception destination is configured, the message is forwarded from the intended destination to its exception destination. If an exception destination is not configured, a time interval between retry attempts is applied.
receiveAllowed boolean true Clear this option (setting it to false) to prevent consumers from being able to receive messages from this destination.
redeliveryInterval long 5000 When no exception destination is configured, the time interval to apply between retry attempts, after the maximum failed deliveries limit is reached, for this destination.
sendAllowed boolean true Producers can send messages to this destination.

Icon that indicates the type of topic Reference topic



Timestamp icon Last updated: Monday, 5 December 2016
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=cord&product=was-nd-mp&topic=rwlp_config_messagingEngine
File name: rwlp_config_messagingEngine.html