Bookshelf Home | Contents | Index | PDF     

Siebel System Administration Guide > Siebel Server Infrastructure Administration > Administering the Siebel File System >

Partitioning the Siebel File System

This topic describes how to perform the optional task of partitioning the Siebel File System,

This topic is part of Administering the Siebel File System.

About Partitioning the Siebel File System

Partitioning the Siebel File System allows you to store larger volumes of data on multiple devices. The original Siebel File System might use a single directory or might already use multiple directories on multiple devices or partitions.

In general, the term partitioning, as used in this topic, refers to running the sfspartition utility, which is provided for the purpose of adding one or more network directories to an existing Siebel File System and distributing the existing files among all of the participating directories. You can add each new directory on the same device as an existing directory or add it on a different device or partition in order to expand the overall capacity of the Siebel File System. (You must consider the future growth of the volume of data when you plan how to organize the file system directories.)

You can also use sfspartition to remove one or more existing directories from service for the Siebel File System, provided that the overall file system capacity remains sufficient.

To partition your Siebel File System, you first update the value of the enterprise parameter Siebel File System (alias FileSystem) so it specifies all of the network directories that you want to use for the Siebel File System, delimited by commas. You then run the partitioning utility and specify both the original directories containing the existing files and the updated target directories, corresponding to the updated FileSystem parameter value. The sfspartition utility distributes the files in the Siebel File System evenly across the target directories. The utility logs information into a file named sfspartition.log, which is located in the log directory within the Siebel Server root directory.

When the File System Manager component (alias FSMSrvr) starts, it verifies the existence of all of the file system directories specified using the FileSystem parameter. When new file attachments are inserted, FSMSrvr distributes them across these directories. If a file system directory is unavailable, then FSMSrvr logs an error message in the FSMSrvr log file and tries to write the file attachment to the next available directory. If no file system directory is available, then FSMSrvr terminates and writes an error message to the FSMSrvr log file.

In order to maintain the even distribution of files across file system directories, you must run the partitioning utility every time that you update the value of the FileSystem parameter, for example, if you add or remove a file system directory. The procedure in this topic describes in detail how to perform this task.

Before you partition your Siebel File System, note the following additional deployment options:

  • Mobile Web Client. A Mobile Web Client's configuration file must refer to a single directory location, unless you configure it to use the server-based data source.
  • Replication Manager requirements. Partitioning is supported on replicated nodes. For more information about replication, see Siebel Remote and Replication Manager Administration Guide.

Partitioning the File System Directories Using the sfspartition Utility

To partition the Siebel File System directories, run the partitioning utility sfspartition, as described in the following instructions.

The partitioning utility is named sfspartition.exe on Microsoft Windows or sfspartition on UNIX operating systems. This utility is located in the bin directory within the Siebel Server root directory.

NOTE:  Where necessary, before you run the sfspartition utility, you must manually create any file system directories (such as the examples siebelFS1, siebelFS2, and siebelFS3, and so on) and subdirectories (such as att, attmp, and so on) on each target file system directory and grant the appropriate permissions to all of these directories. All of the file system directories must be accessible to all of the applicable Siebel Servers using the notation by which they are represented in the value of the FileSystem parameter.

For more information about creating a Siebel File System, see the Siebel Installation Guide for the operating system you are using.

To partition the file system directories using sfspartition

  1. Where necessary, create any new directories or partitions that you will use with the Siebel File System, create required subdirectories, and grant the appropriate permissions to all of the directories. Then verify access to these directories.
  2. Note the current value of the enterprise parameter Siebel File System (alias FileSystem) for later reference.

    NOTE:  You must note this value because you will use this information later when you specify the source directories by using the /O parameter when you run the sfspartition utility.

  3. Set the value of the FileSystem parameter to include all of the directories that you want to use for the Siebel File System. Separate each directory with a comma (with no spaces), as in the examples that follow. Note the updated parameter value for later reference.

    NOTE:  You must note this value because you will use this information later when you specify the target directories by using the /F parameter when you run the sfspartition utility.

    For example, on UNIX, you might specify this value:

    /export/home/siebelFS1,/export/home/siebelFS2,/export/home/siebelFS3

    For example, on Microsoft Windows, you might specify this value:

    \\\\server1\\siebelFS1,\\\\server1\\siebelFS2,\\\\server2\\siebelFS3

    NOTE:  In this example, note that each backslash is doubled compared to the usual notation for such shared directories. For example, \\server1\siebelFS1 must be represented as \\\\server1\\siebelFS1. Alternatively, each file system directory can be represented using a mapped drive letter by which the directory can be accessed from each Siebel Server, such as D:\\siebelFS1 (note that each backslash must be doubled in this scenario also).

    CAUTION:  You must specify the file system directories in the same order for the FileSystem parameter and for the sfspartition utility. If you specify the directories using a different order, then the Siebel File System files might not be accessible after you use sfspartition.

  4. If it is not already set, then set the ServerDataSrc named subsystem parameter DSFileSystem to *FSM*.

    For information about configuring named subsystem parameters, see Configuring Siebel Enterprise Server Named Subsystem Parameters.

  5. Restart the Siebel Server after updating the FileSystem and DSFileSystem parameter values.
  6. Open a command prompt and change the directory to the bin subdirectory within the Siebel Server root directory.
  7. Run sfspartition using parameters listed in Table 24, as in the examples that follow.

    The following example for UNIX distributes the files from one file system directory into three directories, corresponding to the updated value of the FileSystem parameter from Step 3:

    sfspartition /O /export/home/siebelFS /F /export/home/siebelFS1,/export/home/siebelFS2,/export/home/siebelFS3 /H Y

    TIP:   Depending on how these network directories were created or mounted for use in UNIX environments, they might be on the same server or on different servers.

    The following example for Microsoft Windows distributes the files from one file system directory on server1 into three directories on server1 and server2, corresponding to the updated value of the FileSystem parameter from Step 3:

    sfspartition /O \\server1\siebelFS /F \\server1\siebelFS1,\\server1\siebelFS2,\\server2\siebelFS3 /H Y

Parameters for the sfspartition Utility

Table 24 describes the parameters for the sfspartition utility.

Table 24. Parameters for sfspartition Utility
Parameter
Value
Description
Required?

/O

Paths for existing source directories

Set this value to the paths of the existing source directories for the file system. Separate multiple directories using commas, with no spaces. If any of the paths themselves contain a space, then enclose the parameter value in double quotes, as in the examples.

Whether you must append att to each source directory depends on how you use the /H parameter:

  • If you use /H Y, then do not append att to each source directory that you specify by using /O. (The purpose of /H Y is to eliminate the need to append att.)
  • If you use /H N (or omit /H), then you must append att to each source directory that you specify by using /O. The utility looks both in the specified source directories and in the att subdirectories to find the files to be distributed to the specified target directories.

Yes

/F

Paths for target directories

Set this value to the paths of the target directories for the file system. Separate multiple directories using commas, with no spaces. If any of the paths themselves contain a space, then enclose the parameter value in double quotes, as in the examples.

Whether you must append att to each target directory depends on how you use the /H parameter:

  • If you use /H Y, then do not append att to each target directory that you specify by using /F. (The purpose of /H Y is to eliminate the need to append att.)
  • If you use /H N (or omit /H), then you must append att to each target directory that you specify by using /F. Otherwise, files will not be distributed to the att subdirectories of the target directories and will be inaccessible to clients.

Yes

/H

Y or N

Set /H Y if you want the utility to automatically append att to each source and target directory that you specify by using /O and /F. (Do not append att when you specify these directories.)

Set /H N (or omit /H) if you do not want the utility to automatically append att to each source and target directory that you specify by using /O and /F. (Append att when you specify these directories.)

No
    
Siebel System Administration Guide Copyright © 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices.