Making Standard Interactivity Application work across browser

The biggest feature of a SI application is that it works across browsers and not restricted to just IE. Unfortunately a SI application works only on IE Out of Box (OOB). You have to configure it to work for other browsers such as Firefox, Safari and Chrome. This configuration needs to be performed in Administration – Web Browser Screen.

image

A browser record needs to be added with minimum of following two capabilities in order for Siebel to work on it.

  1. User Agent: Identifies the browser which is trying to access the application
  2. Accept: What type of content request is allowed to be accepted from that browser.

User Agent:

You can identify your user agent from online tools such as http://whatsmyuseragent.com/. Just visit this website from the browser for which you want to find the user agent string. For example when opened with Chrome 16 this what is displayed

image

Accept: As shown below Accept is comma separated list of types of content that should be accepted from the browser. You can just copy paste the values already available browser list.

image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/x-shockwave-flash, */*

To make a SI application work in Firefox, Chrome and Safari you don’t need to add separate three browsers as all these browsers share same user agent. You can follow the steps given below to make it work for all three browsers

  1. Go to Administration – Web Browser
  2. Query for Mozilla 5.0 browser record and click on the hyperlink to drill down to capabilities view
  3. Add below mentioned Capabilities to Mozilla 5.0 browser
    1. User Agent : Mozilla/5.0
    2. Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-powerpoint, application/vnd.ms-excel, application/msword, */*

Now you be able to login to your application from all types of browsers. You can add other capabilities as required some of the noteworthy capabilities are

  1. FrameSupport. Indicates whether the browser can render frame tags (for example, <swe:frameset>).
  2. CookiesAllowed. Indicates whether the browser supports cookies.
  3. HighInteract. Indicates whether the browser is among those supported for Siebel’s High Interactivity Web applications (such as Internet Explorer 5.5).
  4. ActiveX. Indicates whether the browser can support ActiveX controls.
  5. JumpTab : Required for IE to support going back to previous page by clicking on back button just once.
Note: You will need to restart your Siebel Server for changes to take effect.

Questions and Feedback are welcomed as always.

One Response to Making Standard Interactivity Application work across browser

Leave a Reply

Contribute