WebSphere Application Server Network Deployment, Version 6.0.x
Operating Systems: AIX, HP-UX, Linux, Solaris, Windows
Configuring messaging engines
You can configuremessaging engines in
a variety of ways; for example you can create and apply security to a messaging
engine and then you can use this engine to send and receive messages.
Why and when to perform this task
Creating a messaging engine
You can create a new messaging engine for a cluster bus member so it can send and receive messages.
Configuring messaging engine properties
You can configure the properties of a messaging engine in the administrative console. You can select whether the messaging engine is started automatically when its associated application server is started, how many messages it can deal with, and target groups that the engine can join.
Listing the messaging engines in a bus
You can view the list of existingmessaging engines in a bus using the administrative console. You may decide which messaging engines you want to change, for example which buses they are associated with.
Removing a messaging engine from a bus
Removing a messaging engine from a from a bus means that the messaging engine can no longer be used for communicating with that bus.
Listing the messaging engines for a cluster bus member
You can display the messaging engines for a cluster bus member in the administrative console. You may decide which messaging engines you want to change, for example, which members of a cluster bus they are associated with.
Adding a messaging engine to a cluster
You can add a messaging engine to a cluster so servers that are members of the cluster can send and receive messages.
Removing a messaging engine from a cluster
You can remove a messaging engine from a cluster so servers that are members of the cluster cannot send and receive messages.
Configuring service integration bus links
You can configure service integration bus links on messaging engines in a variety of ways. For example you can add and start links or stop and remove links.