WAS v8.5 > Reference > Administrator best practicesAvoiding errors when creating a messaging engine with a file store or a data store using wsadmin
Using 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 using administrative commands (by specifying createSIBEngine -server) 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 specify -createDefaultDatasource or -dataSourceJndiName, then a data store is created.
- If you choose to use a file store (by specifying -filestore), then only file store attributes can be specified.
- If you choose to use a data store (by specifying -datastore):
- Only data store attributes can be specified.
- If you set -createDefaultDatasource to False then specify -dataSourceJndiName.
Cluster scope
When you add a cluster as a new bus member using administrative commands (by specifying createSIBEngine -cluster) take note of the following:
- If you choose to use a file store (by specifying -filestore):
- You must not use the default log file, permanent store file and temporary store file directories because they are not suitable for cluster engines.
- Specify -logDirectory, -permanentStoreDirectory and -temporaryStoreDirectory to be at locations that all members of the cluster can access on your file system.
- If you choose to use a data store (by specifying -datastore):
- You must not specify -createDefaultDatasource because the default data source is not suitable for cluster engines.
- Specify -dataSourceJndiName, giving the name of an existing data source.