Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX > Migrating Client Configurations >
Migrating Scripts
You can write two types of scripts —server scripts and browser scripts—to add procedural logic to an application configuration. For upgrades to Release 7.x, you must migrate scripts on UI objects to browser script or server script.
- Server scripts. Server scripts execute in the Object Manager. They existed in prior releases and continue to be supported in Release 7.x. These scripts are written in Siebel VB (for Windows platforms) and Siebel eScript (for Windows or UNIX). There are four types of server scripts:
- Browser scripts. Browser scripts execute in and are interpreted by the browser. Browser scripts are written in JavaScript and interact with the document object model (DOM) as well as the Siebel Object Model available in the high interactivity Web Client framework. You can script the behavior of Siebel events as well as browser events that are exposed through the DOM.
Siebel Tools allows you to write scripts by selecting the appropriate User Agent. For information about browser script techniques, see Technical Note 386 Browser Scripting Techniques in Siebel 7, available on Siebel Support Web. For more information about events that are exposed through the DOM, see Siebel Tools Online Help.
NOTE: During an upgrade from Release 7.0.x to Release 7.5, version 7.0.x browser scripts and objects that contain 7.0.x browser scripts are automatically upgraded to version 7.5.
This section describes how to modify the following types of scripts during the migration:
- Scripts attached to UI objects. See Migrating Scripts Attached to Controls and Migrating Scripts Attached to Applets.
- Scripts that reference UI methods. See Migrating Business Component, Business Service, Application Scripts.
You must migrate Release 6.x scripts written on applets to applet server scripts or business component server scripts, or you must rewrite them as browser scripts.
Applet script migration includes the following types of tasks:
- Moving Release 6.x applet scripts such as Control_Click event handlers to business components
- Rescripting Release 6.x ActiveX controls in browser script
- Rewriting other Release 6.x applet scripts in browser script
To identify the number of 6.x applet scripts to be reviewed or migrated, look at the Object List Editor in Flat mode in Siebel Tools.
You must review Release 6.x scripts on the business components, business services, and application to identify references to methods, such as UI methods, that can not be accessed from server scripts. To locate server side scripts that you may need to modify, run the Siebel Tools Validator on business components, business services, and applications for which the Scripted flag is set to
True
.You must modify Release 6.x business component and application scripts that contain references to UI methods. For example, you need to replace calls to MsgBox with calls to the RaiseError/RaiseErrorText method. Other modifications may include moving scripts to Browser script. For more information, see Siebel Tools Online Help.
Bookshelf Home | Contents | Index | Search | PDF |
Upgrade Guide for UNIX Published: 20 October 2003 |