Configuring Siebel eBusiness Applications > Overview of Configuring Siebel Applications > About Scripting and Object Interfaces >
Generating Browser Scripts
- Browser scripts are automatically generated when you compile objects to a repository file.
When you compile objects to a repository file, browser scripts are generated for compiled objects only. They are placed in the directory specified in the Development Tools Options dialog (View > Options > Scripting).
If you do not specify a directory, browser scripts are stored in the following default directory:
- Browser scripts can be generated using the genbscript.exe utility from the command line interface.
When you run genbscript.exe, all browser scripts in the repository are generated. They are placed in a directory that you specify using the destination directory parameter (dest_dir). The genbscript.exe utility is located in:
siebsrv_root/bin or client_root/bin
The syntax for running genbscript is:
NOTE: The language parameter is optional for ENU, but must be specified for other languages.
Browser scripts must be deployed in the following directories on the Siebel Server and the Siebel Mobile Web Client:
When browser scripts are generated, a directory path is created and named according to the version of the repository file (.srf). It is appended to the path specified as the destination directory. For example, after compiling browser scripts to the correct location on the Siebel Server, the complete path to the browser script files would be:
If you are migrating scripts from one location to another, you must be sure to copy the directories (
\srfTimestamp\bscripts\all\) to the correct location.
NOTE: If you are migrating browser scripts to a Siebel Server running on Solaris or AIX, after compiling on a Windows machine, you must FTP the directories to the correct location on the UNIX machine.
After you compile browser scripts you must do one of the following to load the scripts into the Siebel Web server extension, otherwise you may receive an Object Not Found error message: