Configuring a messaging engine to use a data store
Although the default message store for a typical messaging engine is file store, you can also configure a messaging engine to use a data store.
About this task
每個傳訊引擎都有它自己的檔案儲存庫或資料儲存庫。 如果選擇資料儲存庫,傳訊引擎會利用 JDBC 資料來源的實例,與這個傳訊引擎的資料儲存庫所在的資料庫互動。
When a new messaging engine that uses a data store is created on a single server, it is configured to use an Apache Derby data source by default. This enables the messaging engine to run without needing any additional configuration.
If you want to configure a new messaging engine to use your chosen data source when you create that messaging engine on a single server, see Adding a server as a new bus member.
When a messaging engine is created as a member of a cluster, you must explicitly configure both the data store and the JDBC data source that the messaging engine uses to interact with the data store. You must also set Purge policy to EntirePool. For more information, see Tuning the JDBC data source of a messaging engine.
If you do not want to use the default data source configuration, you can use the WebSphere® Application Server administrative console to change the configuration parameters. For example, you can change the data source or you can configure the data store to use a different JDBC provider.
If you configure a new messaging engine to use your chosen data source when you create that messaging engine as a member of a cluster, see Adding a server as a new bus member.
