Scripting on server side events, also known as server script, runs inside the Siebel Object Manager. This means where the server script runs depends upon where the Siebel Object Manager runs. This varies for different types of architecture, as follows:
Siebel Web Client
In both High Interactivity and Standard Interactivity modes, the Siebel Web Client connects to the Siebel Web Server, then to the Siebel Server. The Siebel Web Client uses the Object Manager residing in the Siebel Server to support its functionality. In this circumstance, the server script runs on the Siebel Server.
Siebel Dedicated Web Client and Siebel Mobile Web Client
The Siebel Dedicated Web Client and Siebel Mobile Web Client run a local version of the Application Object Manager on the machine where the client resides. In this circumstance, the server script runs in the client machine.
Impact on Scripting
The awareness of the above differences is critical for scripting, especially when the script accesses environment-specific references, components, or data sources. For example:
If the server is on a UNIX operating system, the server script running on it must be written in eScript, because there is no Siebel VB script engine on the UNIX environment.
When using server script to directly access files, the awareness of your local file system is very important, since different machines may have a different file system hierarchy and different file access permissions.
Using COM objects to access external applications is a common practice on server script, but it is not possible if the server script runs on a UNIX platform.
No comments:
Post a Comment