The Memory Store Configuration.

This is almost deprecated, since it has performance issues for all but small stores. Yo should probably consider using a Derby store in memory mode instead.

Scope: client and server, all versions.

This will persist items in system memory. This is extremely useful in cases where long-term storage is not required or for a quick testing environment.

A Server Example

There are no attributes to configure. A very minimalist example of a server configuration would be

<config>
    <service name="default-cfg">
    <myproxy host="myproxy.teragrid.org" port="7514"/>
    </service>
</config>

Would point to a service on localhost and use the given MyProxy service. All information would be stored in memory, and there is no mail notifications enabled, so this is not useful for production, but would allow for a very quick setup and test.

A Client Example

An example for a client where assets are to be kept in memory would be 
<config>
    <client name="my-cfg">
       <memoryStore>
          <assetStore/>
       </memoryStore>
       <!-- other stuff -->
    </client>
</config>

Default Memory Storage

This is enabled, which means that if a component does not have explicit storage of some sort declared, a memory store will be used. If you wish to disable this feature, you may do so by setting the following flag in your configuration:

For servers: 
    <config>
    <service name="my-config"
            disableDefaultStores="true"
    >

etc... For Clients 
    <config>
    <client name="my-config"
            disableDefaultStores="true"
    >

It is generally advisable to disable this feature in production environments since if there is a missing storage configuration an error will be generated. If you wish to use a memory store, simply configure one explicity.