File system manager component siebel

For information on creating a Siebel File System, see Siebel Installation Guide for the operating system you are using. Siebel System Administration Guide. To gain access to files, Web clients connect to the appropriate Siebel Server to request file uploads or downloads. File System Manager processes these requests through interaction with the Siebel File System directories.

At the server component level, most server components, including all Application Object Managers, access the Siebel File System through the File System Manager server component when administering attachments. Application Object Managers, however, access the Siebel File System directly when saving user preference files. For examples of these cases, their potential ramifications, and client setup instructions in each case, see Configuring the Browser for Siebel Web Clients.

Files stored in the Siebel File System are compressed at the Siebel Server-level and appended with the extension. You may need to use a file-sharing tool to access the directories. As part of the Siebel Server installation, File System Manager automatically generates a set of subdirectories under each Siebel File System root directory, as described in Table 6.

Do not manually create subdirectories in that location. For more information about these subdirectories, see Siebel System Administration Guide. Use the following procedures to set up the Siebel File System directories. NOTE: In addition to the steps below, you must install the third-party software required to view standard attachment types, such as Microsoft Word, Excel, or Lotus Notes, on client machines where users will run the Siebel applications. If an appropriate GUI-based administrative tool does not exist on your platform, you can use the chmod and chgrp utilities to set these parameters.

Consult your UNIX platform documentation for more information. If you will be operating a File System directory as part of a cluster for failover purposes, you must create the directory on a clustered disk drive with a clustered network share resource.

For information about clustering your servers, see Siebel Deployment Planning Guide. Table 6. The following are requirements for the Siebel File System. Additional requirements are noted later in this topic.

These locking daemons must be tuned to the number of operating system threads. Otherwise, these daemons might not be able to manage the high volume of concurrent file system lock requests that a large scale Siebel CRM system can generate. Because the Siebel Server is the sole access mechanism to the Siebel File System, the user with administrative privileges for the Siebel Server, and no other user, must have access privileges to the File System directories.

This precaution protects the File System from direct physical access by all other users. The Siebel File System parameter defines the particular directory or set of directories that you are using for the Siebel File System.

Specify multiple File System directories delimited by commas. Use Server Manager to individually modify the parameter at the Siebel Server or component level, if the File System that is to be used by a particular Siebel Server or applicable component has different directory locations than are defined for the Siebel Enterprise. The value of the Siebel File System parameter cannot exceed characters in length.

IP addresses are not supported. Two utilities are available to help you manage your Siebel File System directories: sfscleanup and sfspartition. For information about using these utilities to partition an existing Siebel File System to use multiple File System directories or to clean up orphan files in the File System, see Siebel System Administration Guide.

Each Siebel File System directory name must be alphanumeric, must begin with an alphabetic character, and cannot contain special characters or spaces. Underscores are permitted. For example, you might name a directory something like this:.