WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

► Data stores (or, tables inside a database)
Data stores are the equivalent of file stores, but are implemented inside a
relational database as a series of tables. They are administered by the
facilities provided by the database. You can use any supported database
product. Data stores might be preferable for larger organizations with an
existing database infrastructure and skills.
Both types of message store can be subject to security, such as file
system/database encryption and physical security access.
10.6 Planning checklist for messaging
Table 10-1 provides a summary of items to consider as you plan and additional
resources that can help you.
Table 10-1 Planning checklist for messaging
Planning item
Determine if and how messaging will be used.
Choose a JMS messaging provider (default messaging, WebSphere MQ, or generic).
Design a messaging topology. If using the default messaging provider, determine the
number of buses to be used and if connections to other buses or WebSphere MQ are
required.
Determine what destinations (queues, topics) are required initially, and the reliability
levels for those destinations.
Determine the type of message data store to use.
Design a security strategy for messaging:
► Bus security
► Transport security
Plan for high availability. If clustering application servers, decide whether to use one
messaging engine (high availability) or multiple (workload management).
Resources
For a good overall reference, the WebSphere Application Server Information
Center contains numerous messaging resources:
http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/topic/com.ibm.web
sphere.nd.doc/info/ae/ae/welc6tech_msg.html
Chapter 10. Messaging 355