WAS v8.5 > Administer applications and their environment > Welcome to administering Service integration > Administer message stores > Administer file stores > Configure file store attributes for a messaging engineDelete files following removal of a messaging engine
Removing a messaging engine from the configuration does not automatically delete the file store files. You must also find and delete the log file, the permanent store file, and the temporary store file from the disk to reclaim disk space.
Files comprising a file store still remain when the messaging engine is deleted. If we are using the default values for the file store directory names, we can delete and then re-create a messaging engine with the same name without manually removing the files. This is due to the presence of the universal unique identifier (UUID) of the messaging engine in the default log and store directory names of a file store.
For example, if the deleted messaging engine is called messagingengine0, and the new one is called messagingengine1, then the log file in the old file store is:
C:\{USER_INSTALL_ROOT}\filestores\..\messagingengine0\..\logfile
The log file in the new files store is:
C:\{USER_INSTALL_ROOT}\filestores\..\messagingengine1\..\logfile
The two log files coexist in the same file stores directory. We do not have to delete the old files.
- Locate the directory in which your old file store log files and store files are stored.
- Delete the redundant files using the facilities of the operating systems.
Results
After deleting the files left by the redundant file store, free disk space becomes available to your file system.
Related
Create a bus
Add a server as a new bus member