Network Deployment (Distributed operating systems), v8.0 > Reference > Administrator best practices
Avoiding message store errors when creating a messaging engine
Use different combinations of parameters can create a file store or a data store according your requirements. The outcome varies in server and cluster scopes.
Server scope
When you add a server as a new bus member take note of the following:
- If you do not specify the type of message store, then a file store is created by default. If you set Create default data source to True or supply a Data source JNDI name, then a data store is created.
- If you choose to use a file store, then only file store attributes are presented to be specified. For example the log file directory.
- If you choose to use a data store:
- Only data store attributes are presented to be specified. For example the Data source JNDI name.
- If you set Create default data source to False then specify a Data source JNDI name.
For more information about file store and data store refer to Administer message stores.
Cluster scope
When you add a cluster as a new bus member take note of the following:
- If you choose to use a file store:
- We must not use the default log file, permanent store file and temporary store file directories because they are not suitable for cluster engines.
- We must specify the Log directory, Permanent store directory and Temporary store directory to be at locations that all members of the cluster can access on your file system.
- If you choose to use a data store:
- We must not use the default data source because it is not suitable for cluster engines.
- We must specify the Data source JNDI name of an existing data source.
For more information about file store and data store refer to Administer message stores.