edocs Home > BEA WebLogic Server 10.0 Documentation > Administration Console Online Help > Create file stores

Administration Console Online Help

    Previous Next  Open TOC in new window 
Content starts here

Create file stores

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.

  1. If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
  2. In the left panel of the console, expand Services and select Persistent Stores.
  3. On the Summary of Persistent Stores page, click New > Create File Store.

    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.

  4. On the Create a new File Store page, update the following:
    1. Name -- Name for the File Store.
    2. Target -- Server instance or migratable target on which to deploy the file store.

      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.

    3. Directory -- Pathname to the directory on the file system where the file store is kept. This directory must exist on your system, so be sure to create it before completing this tab.

      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).

    4. Click Finish.

    For more information about these fields, refer to Configuration Options.

  5. On the Summary of Persistent Stores page, select the file store created in steps 2-3.
  6. On the File Store > Configuration tab, update any additional Advanced parameters as required:
    1. Logical Name -- Optional name that can be used by subsystems that need a way to refer to different stores on different servers using the same name.
    2. Synchronous Write Policy -- Specifies how this file store writes data to disk.

    For more information about these fields, refer to Configuration Options.

  7. Click Save.
  8. To activate these changes, in the Change Center of the Administration Console, click Activate Changes.
    Not all changes take effect immediately—some require a restart (see Use the Change Center).

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.


  Back to Top