Using a file system for external storage

Content Manager OnDemand supports data storage in a file system repository. The file system must be locally accessible to the Content Manager OnDemand library or object server.

Updating the ARS.CFG file

Perform these steps to configure Content Manager OnDemand to use a file system as external storage on a z/OS server.

  1. Two new entries must be added to the ARS.CFG file. 

    ARS_FILESYSTEM_CONFIG_FILE=/usr/lpp/ars/V10R5M0/config/ars.fs
      ARS_FILESYSTEM_CONFIG_DIR=/usr/lpp/ars/V10R5M0/config

    The ARS_FILESYSTEM_CONFIG_FILE entry specifies an existing file system configuration file which the server uses by default.

    The ARS_FILESYSTEM_CONFIG_DIR entry specifies the directory in which any alternate configuration files are kept. This directory is used if additional file system configuration files are defined. The names of these additional configuration files can be specified when defining storage nodes in Content Manager OnDemand. If no configuration file is specified in the storage node, the default configuration file is used.

    The configuration file name and directory path shown in the examples are the recommended values for these entries.

  2. The ARS_STORAGE_MANAGER entry in the ARS.CFG file might also need to be changed. If you specify ARS_STORAGE_MANAGER=CACHE_ONLY, this disables all storage managers supported by Content Manager OnDemand.

    To configure the Content Manager OnDemand server to use a file system as external storage, the value must be set to the following:
    ARS_STORAGE_MANAGER=NO_TSM
    This setting will enable all external storage managers supported by Content Manager OnDemand except Tivoli® Storage Manager, which is not supported on z/OS. This setting is used when the additional software to support Tivoli Storage Manager is not installed and Tivoli Storage Manager is not required as an external storage manager.

Creating a file system configuration file

A file system configuration file for Content Manager OnDemand contains entries specific to your file system implementation. You specify the location and name of the default configuration file in the ARS.CFG entry. Required entries must be specified. Optional entries are not required in the configuration file unless those values need to be changed.

The following list describes the entries that can be specified in a file system configuration file.

ARS_FILESYSTEM_NAME
Specifies the name of the file system for Content Manager OnDemand to use as a storage location. The file system permissions and ownership must be set to allow Content Manager OnDemand to read, write, and delete data to and from this location. This entry is required.
ARS_FILESYSTEM_HLD
Specifies the high-level directory name. This attribute is available to group sets of Content Manager OnDemand data together which might be needed if sharing this external storage among multiple Content Manager OnDemand servers. Warning: Once this value is set, it must not be changed. If it is changed, any data that is already stored may not be retrievable. There is no default value. This entry is optional.
As an example:
ARS_FILESYSTEM_NAME=/ondemand/fs

Defining a file system storage node with the Administrator client

You can define the settings for using the file system access method on the Add a Primary Node dialog of the OnDemand Administrator client.

The Storage Node field can be set to any name you choose. It is only used internally by Content Manager OnDemand.

The Logon and Password fields are not used.

The Access Method radio button is set to Use a file system. The Configuration File Name defaults to the value specified by the ARS_FILESYSTEM_CONFIG_FILE parameter in the ARS.CFG file if no value is entered. Otherwise, Content Manager OnDemand looks for the configuration file in the directory defined by the ARS_FILESYSTEM_CONFIG_DIR parameter specified in the ARS.CFG file.