Messaging engines
每個服務整合伺服器或叢集匯流排成員,都包含一個稱為傳訊引擎的元件,用來處理傳訊功能的傳送和接收要求,以及管理目的地。
When you add an application server or a server cluster as a bus member, a messaging engine is automatically created for this new member. If you add the same server as a member of multiple buses, the server is associated with multiple messaging engines (one messaging engine for each bus). 如果匯流排成員是伺服器叢集,它可以有更多傳訊引擎來提供高可用性或工作量分散性質。 如果匯流排成員是 IBM MQ 伺服器,它沒有傳訊引擎,但它可讓您直接從 IBM MQ 佇列管理程式和(針對 WebSphere® MQ for z/OS®)佇列共用群組存取 IBM MQ 佇列。
為了管理佇列類型目的地,傳訊引擎包括一個訊息儲存庫,必要之時,它可以將訊息存放在這裡,直到消費端應用程式準備好接收它們,或保留訊息來預防傳訊引擎失敗。 There are two types of message store, file store and data store. For further information, see Administering message stores.
Messaging engines are given a name which is based on the name of
the bus member. Each messaging engine also has a universal unique
identifier (UUID) that provides a unique identity for the messaging
engine.
Note: If you delete and recreate a messaging engine, it will
have a different UUID and will not be recognized by the bus as the
same engine, even though it might have the same name. For example,
the recreated messaging engine will not be able to access the message
store that the earlier instance used. If you accidentally delete a
messaging engine configuration, and save the updated incorrect configuration,
you must restore the configuration from a previous configuration backup.