# store

The `store` property determines where messages sent to this destination are stored. Messages may be stored in a file, or in a database.

See Store Messages in Multiple Stores for more information on using and configuring multiple stores.

Warning: When using the `setprop` or `addprop` commands to change the store settings for a topic or queue, note that existing messages are not migrated to the new store. As a result, stopping the EMS server and deleting the original store may result in data loss, if a destination still had messages in the original store.

Set the store property using this form:

       store=name

where name is the name of a store, as defined in the `stores.conf` file.

For example, this will send all messages sent to the destination `giants.games` to the store named `baseball`; messages sent to all other destinations will be stored in `everythingelse`:

       > store=everythingelse
       giants.games store=baseball

Only one store is allowed for each destination. If there is a conflict, for example if overlapping wildcards cause a topic to inherit multiple store properties, the topic creation will fail.

Note: This parameter cannot be used without first enabling this feature in the `tibemsd.conf` file. The `stores.conf` file must also exist, but can be left empty if the only store names that are associated with destinations are the default store files.

See Store Messages in Multiple Stores for more information.

Copyright © Cloud Software Group, Inc. All rights reserved.