1. Installation Guide
  2. Siebel File System Requirements

Siebel File System Requirements

This topic is part of Creating the Siebel File System.

The following are requirements for the Siebel File System. Additional requirements are noted later in this topic.

  • You specify the Siebel File System directory when you configure and deploy the Siebel Enterprise using Siebel Management Console. Siebel Management Console creates the Siebel File System directory if the directory specified for the File System does not exist. However, it is recommended that you create the primary Siebel File System directory with appropriate permission before you configure the Siebel Enterprise.

    Note: The Siebel File System must not be located under a $SIEBEL_HOME. For example, if you install Siebel CRM to D:\Siebel, the File System cannot be located at D:\Siebel\fs or any other folder under that directory structure.

  • The Siebel File System directory location must be specified using UNC format, such as \\computer_name\FS. If this directory is located on the same computer or operating system instance where you are installing and configuring Siebel CRM software, then the directory must be created as a shared directory.

  • The user running the Siebel Management Console must have write permission in the Siebel File System directory.

  • It is strongly recommended that you disable short file-name generation on Windows server computers or operating system instances hosting the Siebel File System. Using this type of file-naming can cause severe performance issues when the file system grows to a large size.

  • The underlying physical file system must use file locking. Valid locks must be returned that are appropriate to the action being undertaken. For example, when a file is created or written to, an exclusive lock is needed. File locking must ensure the integrity of the files accessed. If a write lock is acquired for a file, then no other process must be able to access the file. For more information and recommendations, see 759070.1 (Article ID) on My Oracle Support.

  • If the operating systems of the computers hosting the Siebel Server and a File System directory are different (for example, one Windows and one UNIX), then you might have to deploy a third-party cross-platform networking tool, such as Samba, to allow both computers to share the directory. See your third-party vendor documentation for details.

  • You must create a separate Siebel File System for each Siebel Enterprise. For example, if you have development and test databases, then you must have two separate Siebel Enterprises, and therefore two Siebel File Systems.

  • The ability to use multiple directories and devices for the Siebel File System does not apply to the Siebel Mobile Web Client, for which the Siebel File System must use a single directory on the client computer.

  • If you operate a File System directory as part of a cluster for failover purposes, then you must create the directory on a clustered disk drive with a clustered network share resource. For information about clustering your servers and about deployment options for the Siebel File System, see Siebel Deployment Planning Guide.

  • The Siebel service owner account must have read-write access to the Siebel File System and the Migration Package Location. See also Creating the Siebel Service Owner Account.