Modify file store configuration
After a file store has been created, we can, if required, modify file store attributes.
When we add a new bus member that uses a file store, we can choose either to accept the default settings for the file store or make changes to these settings, depending on your requirements.
After the file store has been created, we can, if required, subsequently modify the log size, permanent store size, or temporary store size settings directly through the administrative console. The new values take effect the next time the messaging engine is started.
The directory paths for the file store are fixed when the file store is created, and cannot subsequently be modified. Create a new file store in a new location. To do this you remove the server or cluster as a bus member and then add it again choosing a new location for the file store. Any messages remaining in the original file store would be lost during this process.
The default configuration for a file store is intended to be sufficient when used in typical messaging workloads. To improve the performance or resilience of the log file, the permanent store file, or the temporary store file, we can modify the file store attributes to control where these files are placed. For example, we can achieve better performance if you place these three file store files on a faster disk. Similarly, we can control the sizes of the log file, the permanent store file, and the temporary store file so that they can handle workloads with a large number of active transactions, large messages, or a large volume of message data resident in the messaging engine.
Tasks
- Make changes to the log size, permanent store size or temporary store size:
- Open the Administrative console.
- Click Service integration -> Buses -> bus_name -> [Topology] Messaging engines -> engine_name -> [Additional Properties] Message store.
- Make required changes to the existing log size, permanent store size, or temporary store settings, then click OK. For more information about configuring the properties, see Foreign bus [Settings]
- Save changes to the master configuration.
- Choose a new location for a file store:
- To avoid losing messages on destinations that are localized on the file store, first ensure that no messages are left on the queues.
- Remove the server or cluster as a member of the bus.
- Add the server and cluster as a bus member again, choosing a new location for the file store.
Related:
Hints and tips for configuring file store size Create a bus Add a server as a new bus member Add a cluster as a member of a bus Configure the members of a bus Foreign bus [Settings]