Before you begin
A directory for the file store that must already exist on your file system, so be sure to create it before completing this page.
A file store is a file-based repository for storing subsystem data, such as persistent JMS messages or durable subscriber information.
Note: Once you create a file store, you cannot rename it. Instead, you must delete it and create another one that uses the new name.
Note: In a clustered environment, a recommended best practice is to target a file store to a migratable target, so that a member server will not be a single point of failure. Migratable JMS-related services require a custom file store that is targeted it to the same migratable target as the migratable JMS services. See Configure migratable targets for JMS-related services.
Note: If you plan to migrate clustered servers in the event of a failure, unless you are using pre/post migration scripts to move the store data across migrated servers, then make sure that the store is configured such that all the candidate servers in the migratable target have access to the custom file store. For highest reliability, use a shared storage solution that is itself highly available—for example, a storage area network (SAN).
For more information about these fields, refer to Configuration Options.
For more information about these fields, refer to Configuration Options.
After you finish
You do not need to restart the Administration Server after creating and initially configuring a file store. However, if you modify an existing file store, you must restart the Administration Server.