Handling Browser Script in Siebel Versions Prior to 20.8

This topic explains that Siebel 20.8 and later stores browser scripts in the S_RR tables so genbscript is not needed, while earlier versions require configuration updates and running genbscript to generate and deploy browser script files.

After Siebel version 20.8, browser scripts are compiled and stored in the S_RR* tables. There is no need to run the genbscript utility to extract them from the Repository and store them in a local file.

Before Siebel version 20.8, the genbscript utility is still necessary. Without following these steps genbscript may fail.

Steps to generate browser scripts in Siebel versions prior to 20.8.

Configuration Files

Update Configuration File
1. Choose the configuration file used to start your client. This could be uagent.cfg, fins.cfg and so on.
2. Update the DataSourceName parameter under the [DBSecAdpt] section to ServerDataSrc.
  Example
```
[DBSecAdpt]
 DBSecAdpt_SecAdptDllName = sscfsadb

DataSourceName = ServerDataSrc
 DBSecAdpt_PropagateChange = TRUE
```
In the same file, under the [ServerDataSrc] section, make sure the following two values are set. The ConnectString parameter points to the Data Source Name (DSN) or entry in the tnsnames.ora file that points to your database. In this example, there is a DSN or tnsnames.ora section named “DEV01”. Ensure that this DSN or tnsnames.ora entry exists on the machine and that connectivity to the database is successful.

Example
```
Docked = TRUE
 ConnectString =
      DEV01
```
Note: You can run genbscript on a client machine or on the server. If you are using the server, there are a few changes to the configuration file that are different than the changes made if you are running genbscript on a client machine. The above example uses a client configuration file such as uagent.cfg (found in the client machine’s <Siebel Installation Directory>\bin directory). If you are using a configuration file (They are the same files as found on a client machine such as uagent.cfg, fins.cfg, they are just located on the server.) from the siebsrvr\bin directory, set the ClientRootDir parameter to <install directory>\ses\siebsrvr. Also set the ServerDBODBCDataSource parameter to the DSN name or tnsnames.ora entry that connects to the database.

Example
```
ClientRootDir = <Siebel Install
        Directory>\ses\siebsrvr
ServerDBODBCDataSource = DEV01
```
You must also populate the [ServerDataSrc] section’s parameters for running genbscript on the server.

Example
```
[ServerDataSrc]
 Docked = TRUE
 ConnectString =
        DEV01
 TableOwner = SIEBEL
 DLL = sscdo90.dll
 SqlStyle =
      OracleCBO
```

Running the Genbscript Utility

Use the following command line from the \bin directory to run genbscript.
1. After the utility completes your browser scripts will be in a new browser script folder srf_xxxxxxxxxx_xxx will be created in the dest_dir. Each time your run genbscript, a different folder name is used because the current date/time is used for the folder name.
```
genbscript /c <config_file> <dest_dir> /l <LANG> /u <User id>
        /p <Password> /d <Data source name>
```
  Example of running this on a client machine:
```
cd C:\Siebel\Client\bin
genbscript.exe /c enu\uagent.cfg C:\Siebel\Client\public /l enu /u SADMIN /p SIEBEL /d ServerDataSrc
```
  Example of running this on a server machine:
```
cd C:\Siebel\ses\siebsrvr\BIN
genbscript.exe /c enu\uagent.cfg C:\Siebel\ai\applicationcontainer\webapps\siebel /l enu /u SADMIN /p 
********* /d ServerDataSrc
```

After the files have been generated, put the entire srf_xxxxxxxxxx_xxx folder and its contents in the following locations.

Client Type	Browser Script Folder Location
Web Client	siebel_home\ai\applicationcontainer\webapps\siebel
Dedicated Client	client\public