|Bookshelf Home | Contents | Index | PDF|
This topic is part of General Considerations in Planning Your Siebel Deployment.
The Siebel File System is a shared directory, or set of directories, that is network-accessible to the Siebel Server and that can store files such as attachments for use by Siebel applications. Siebel File System directories may optionally exist on separate devices or partitions.
Each File System directory may be created on a server machine where you have installed a Siebel Server, or on another network server that can share the directory, so that it is available to the Siebel Server. Consult your third-party documentation for requirements for networked file systems.
A primary Siebel File System directory must be created before you configure the Siebel Enterprise. You specify this location during configuration. The location must be specified using UNC format, such as \\machine_name\FS. If this directory is located on the same machine where you are installing and configuring Siebel software, the directory must be created as a shared directory. The user running the Siebel Configuration Wizard must have write permission in this directory.
Creating multiple Siebel File System directories in different locations can enable you to store larger volumes of data. As new file attachments are inserted, they are evenly distributed across the multiple File System directories. If you create multiple File System directories, you must include all directory locations, delimited by commas, when you specify the File System location during configuration of your Siebel environment. Each File System directory location must be uniquely named within the network context where it will be accessed.
The ability to use multiple directories and devices for the Siebel File System does not apply to Siebel Mobile Web Clients, for which the Siebel File System must use a single directory on the client machine.
NOTE: If the operating systems of the machines hosting the Siebel Server and a File System directory are different (for example, one Windows and one UNIX) you may need to deploy a third-party cross-platform networking tool, such as Samba, to allow both machines to share the directory. Refer to your third-party documentation for details.
You must create a completely separate Siebel File System for each Siebel Enterprise Server. For example, if you have development and test databases, you must have two separate Siebel Enterprise Servers, and therefore two Siebel File Systems.
Each Siebel Server accesses its Enterprise's Siebel File System by means of a dedicated server component, called File System Manager (FSM). Individual Web clients require no direct knowledge of the locations of the Siebel File System directories, because they connect to FSM through the Application Object Manager (AOM) component on the Siebel Server to request file uploads or downloads. The AOM passes such requests to the FSM component, which processes the requests through interaction with the File System directories.
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 can be defined at the Enterprise level, Siebel Server level, or server component level. 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 Enterprise.
NOTE: Verify that the network names of servers that will support the Siebel File System are properly recorded in your copy of the worksheet in Deployment Planning Worksheet. Use the machine names, not the IP addresses, for the Siebel File System names. IP addresses are not supported.
For more information about the File System Manager component, about the Siebel File System parameter, and about Siebel File System management tasks using sfscleanup and sfspartition, see Siebel System Administration Guide.
For information about populating the Siebel File System with files such as correspondence templates, see Populating the Siebel File System.
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:
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 5.
NOTE: When you create a Siebel File System shared directory, only the associated Siebel Servers must be allowed to create subdirectories in that location. Do not manually create subdirectories in that location.
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 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.
|Siebel Installation Guide for Microsoft Windows||Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices.|