SAS 9.1.3 Intelligence Platform: System Administration Guide

256 Options R Appendix 4
TRUSTEDUSERS="filename"
specifies the name and location of the trustedUsers.txt file. The planned
installation creates the file in SAS-config-dir\Lev1\SASMain\MetadataServer.
WORKUNITJOURNALPATH="filename"
activates workunit journaling and specifies a location to create the workunit
journal file. Do not specify the WORKUNITJOURNALPATH option without also
specifying a filename for the location. If the WORKUNITJOURNALPATH option is
specified without a filename, the metadata server will fail to initialize.
We recommend that you specify a file that is in the directory from which the
metadata server is started and that you name it something recognizable, such as
WorkunitJournal.dat. If you need to use a different location and name, keep
these things in mind:
3 Put the workunit journal file on a native file system, such as the C: (system)
drive. Do not place the file on a network-mounted file system or network
appliance.
3 Use a relative pathname to identify the file’s location. The pathname should
be relative to the directory from which the metadata server is started.
3 The standard metadata server configuration creates repositories and the
metadata server log on the same file system in which the SAS Metadata
Server is started. If it is at all likely that this file system will fill up, consider
moving the repositories to another file system. If the server file system fills
up, the workunit journal file is not threatened because it is a fixed size.
However, the metadata server log will need space to be able to record any
disk-full messages in order to send them to the metadata server
administrator.
WORKUNITJOURNALSIZE="number-of-bytes"
specifies a size, in bytes, for the workunit journal file. This space is reserved in the
file system and is unavailable to other processes, whether the workunit journal file
is full or not.
This option does not have a default value. The size that you assign to the
workunit journal file depends on the total disk space available on the SAS
Metadata Server host machine. The recommended size is 20MB (20000000), which
should be enough for most sites. If clients regularly experience delays in getting
their add, update, and delete requests processed, check the SAS Metadata Server
log. If you find messages similar to the following, you might consider setting a
higher WORKUNITJOURNALSIZE value:
WARNING: insufficient file space available in workunit journal file.
When an entry is added to the workunit journal file, it is marked as Pending.
When entries are committed to the disk repository, they are marked as Done, and
the space becomes available for new pending entries. If the rate at which entries
are being added exceeds the rate at which they are completed, the workunit journal
file can become full, and not enough space is available for new entries. When this
occurs, the metadata server waits until the update process can catch up. When the
contents of the workunit journal file are safely committed, the first new update is
written directly to repositories on disk. Then, workunit journaling resumes.
Note: When you change the WORKUNITJOURNALSIZE value, or any other
omaconfig.xml option, you must stop and restart the metadata server for the
change to take effect. R
WORKUNITJOURNALYIELDCOUNT="number-of-observations"
is designed to prevent large repository updates (for example, requests that add
hundreds of objects) from monopolizing the server. It specifies the number of