How Does Siebel SmartScript Interact With the File System in Siebel 7?

Releasing a SmartScript saves (caches) a precompiled version of the SmartScript definition and all associated code (VB or JavaScript). This in turn speeds up the loading of the SmartScript. The Releasing saves the release-compiled script to a file on the file system. It also updates the SmartScript definition to indicate that a release file exists, and to create a pointer to the release file in its server location.


If different Siebel Servers are pointing to the same file system (shared across different Siebel Servers), file attachments and SmartScript will function.

If different Siebel Servers are pointing to different file systems, neither will work.

Example:

Siebel Server A - File System A
Siebel Server B - File System B

Release SmartScript on Siebel Server A, released file (.SAF) is saved to File System A.

Invoke SmartScript on Siebel Server A, the file is copied from the File System A to local machine (.../siebsrvrA/serverdatasrc/files/...) and renamed as .ssc file.

Invoke SmartScript again on SiebServer A, read from local copy of the file directly.

Invoke SmartScript on SiebServer B, trying to find the file in both local file system and main FileSystem B, no luck. Report an error.

To fix this, do either of the following:

Copy the .SAF file form FileSystem A to FileSystem B.

Copy the .SSC file from Siebel Server A to Siebel Server B.

If both Siebel Servers are pointing to the same File System, the Siebel Application should have no problem retrieving file from the File System.

http://www.siebeldigest.com/