Configuring a messaging engine to use a data store

Use this task to obtain an overview of configuring a messaging engine to use a data store.

About this task

Each messaging engine has its own data store. A messaging engine uses an instance of a JDBC data source to interact with the database that contains the data store for that messaging engine.

When a new messaging engine which uses a data store is created on a single server, it is configured to use a Cloudscape 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, refer to 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 the Purge policy to EntirePool. For more information, refer to 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, refer to Adding a server as a new bus member.




In this information ...


Related concepts

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 7:21:45 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=vela&product=was-nd-dist&topic=tjm0005
File name: tjm0005_.html