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 we add a server as a new bus member take note of the following:

• If we do not specify the type of message store, then a file store is created by default. If we set Create default data source to True or supply a Data source JNDI name, then a data store is created.

• If we choose to use a file store, then only file store attributes are presented to be specified. For example the log file directory.

• If we choose to use a data store:

  • Only data store attributes are presented to be specified. For example the Data source JNDI name.

  • If we set Create default data source to False then we must specify a Data source JNDI name.

For more information about file store and data store refer to Administer message stores.

Cluster scope

When we add a cluster as a new bus member take note of the following:

• If we 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.

  • Specify the Log directory, Permanent store directory and Temporary store directory to be at locations that all members of the cluster can access on the file system.

• If we choose to use a data store:

  • We must not use the default data source because it is not suitable for cluster engines.

  • 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.