Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

When to use Page-level Emulation instead of the Browser-level Emulation when recording a Script.

When to use Page-level Emulation instead of the Browser-level Emulation when recording a Script.

Borland recommends using the "Page-level" Emulation when recording a new web script in Silk Performer. The primary reason for this is to take advantage of the "Context Management" feature which is provided when recording at this level. Context Management maintains the session state of a user within the API calls in the BDF script; this means that session information is managed automatically in that Session Ids, embedded objects etc are all parsed from the server response if they need to be used in subsequent BDL requests.

 

It is important to note that Page-level functions focus on Web pages rather than on single documents; this means that all embedded objects (i.e. GIF"s; JS pages etc) of a single Web Page are requested from the server in the single encapsulated BDL function. Some examples of functions which are generated at Page based Level are "WebPageUrl, WebpageLink and WebPageSubmit"; detailed information on each of these functions can be found in the online help which ships with Silk Performer.

 

Recording at the "Browser-level Emulation" means you loose the Context Management benefits which means that no automatic parsing for Java Script pages or session id"s will be performed by the Silk Performer replay engine. Instead recording at Browser-based level will result in each individual page, object or link being requested in sequential order by its own BDL function (such as WebUrl); also, many Browser Level calls result in sending a request and not waiting for a response before the next subsequent call is executed.

 

Below is a list of the various types of scenarios which best suit using the Page-level functions:

  • When your Web pages contain dynamically embedded documents.
  • When you do not want to care about session handling or when pages contain lots of session information that would require many WebParseResponseData function calls to maintain the session during replay.
  • When your server requires the "referrer" header to be set dynamically.
  • When your load balancer redirects the client to different servers dynamically.
  • When you want to use automatic verification for a page that checks whether the context between pages can be maintained.
  • For shorter, easy-to-read scripts.

 

 

When to use the Browser-level functions instead:

  • When you need to generate a higher level of throughput per virtual user.
  • When your application is not Web-browser-based, for example, multimedia clients that use HTTP for communication but do not use HTML.
  • When maintaining context between pages is not relevant.

 

 

The Browser Emulation level can be set in Silk Performer by going to:

 

SETTINGS | ACTIVE PROFILE | RECORD | WEB | RECORDING | BROWSER EMULATION LEVEL

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 18:47
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.