Configuring messaging engines
You can configure messaging engines in a variety of ways. For example, you can create and apply security to a messaging engine, then use this engine to send and receive messages. When you add a server cluster to a service integration bus, at least one messaging engine is created automatically. If you also use messaging engine policy assistance, some configuration properties are set automatically.
Subtopics
Adding additional messaging engines to a cluster bus member
You can add extra messaging engines to a cluster bus member, for example to provide high availability or scalability in a cluster.Configuring messaging engine properties
You can configure the properties of a messaging engine in the administrative console. For example you can select whether the messaging engine is started automatically when its associated application server is started, how many messages it can process, and target groups that the engine can join.Listing the messaging engines in a bus
You can view the list of existing messaging engines in a bus by using the administrative console. You can decide which messaging engines you want to change, for example which buses they are associated with.Removing a messaging engine from a bus
You can remove a messaging engine from a service integration bus if you no longer require it to send and receive messages on the bus.Listing the messaging engines defined for a server bus member
You can display a list of messaging engines defined for a server bus member by using the administrative console. You can decide which messaging engines you want to change, for example, which buses they are associated with.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 can decide which messaging engines you want to change, for example, to change the properties of the messaging engine.Adding a messaging engine to a cluster
You can add a messaging engine to a cluster bus member to provide additional asynchronous messaging services to the servers that are members of the cluster. Typically, you do this to provide workload sharing or scalability in the cluster.Removing a messaging engine from a cluster
You can reduce the number of messaging engines configured for a cluster bus member by removing a messaging engine.Correcting the messaging engine policy
You can change the messaging engine policy for a messaging engine in a cluster so that it conforms to one of the predefined messaging engine policy types that are available when you use messaging engine policy assistance.Deleting a redundant core group policy
If there is a core group policy that is associated with a cluster, but that is not associated with any messaging engine in the cluster, and you are using messaging engine policy assistance, you can identify and delete that policy.Creating the database, schema and user ID for a messaging engine
Before the data store for a messaging engine can be set up, you must first create the database, the schema and the database user ID that the messaging engine needs to access the data store tables.Configuring service integration bus links
You can configure service integration bus links on messaging engines in a variety of ways. For example, you can start, stop, or remove links.
Related tasks:
Related reference:


File name: tjj0050_.html