Archive for February, 2007

Generating Browser Script

When I first needed to add some funky client-side functionality in Siebel 7.5 I was hit with a problem: how to get hold of the browser scripts for testing?

SupportWeb Alert 365 covers using the genbscript utility to build the scripts from the repository using the following format:

genbscript <config_file> <destination_dir> <language_code>

This is all well and good and works fine – I’d recommend the method outlined for migrating browser scripts up to a server.

What the alert fails to mention, though, is that the officially ‘deprecated’ method of letting Tools generate the scripts for you still works. When you compile an object in Tools, any associated browser scripts are generated in the default directory tools_root\public\language_code\srf_timestamp\. This srf_timestamp directory is the same one produced by genbscript – except it only includes scripts for objects you’ve compiled.

For local debugging and unit testing this avoids an extra step. The destination directory for browser scripts can be changed by going to View > Options > Scripting and changing the ‘Browser script compilation folder’. You’ll want to set this to your Mobile Client’s public directory (e.g. Siebel\7.8\client\PUBLIC\enu) .

Then if you also have the usual parameters on the Debug tab pointing at your mobile client, and the location of the Siebel Repository File on the Compile dialog correctly set, then unit testing of browser scripts is a simple Ctrl+F7 > Enter > F5 away…

Advertisements

February 28, 2007 at 7:51 pm 2 comments

Client-side Logging

An invaluable debugging step. I first came across this a few years ago, when I returned from holiday to find Siebel 6 clients running incredibly slowly in all environments. After much digging around, I found out that a Siebel Professional Services contractor had been in and borrowed my workstation while I was away. He’d set up the environment variable for maximum logging and never gotten around to switching it off…

Client-side logging relies on the two environment variables SIEBEL_LOG_EVENTS and SIEBEL_LOG_DIR.

To switch on logging for a single session, open a command prompt and:

set SIEBEL_LOG_EVENTS=<event level 0-5>

set SIEBEL_LOG_DIR=<dir>

Then launch the Siebel client using the usual command string:

<base_path>\siebel /c <config_file> /u <username> /p <password>

Alternatively, the variables can be set globally by adding system environment variables. Do remember remove the variables when you’re done, though…

More details in the FAQ: SupportWeb FAQ 1322.

February 27, 2007 at 10:47 am


Feeds