How to run siebel dedicated client in a IE sandbox

Question

Hi all,
I don't know if sandbox is the right term for this, but here is what I need to do. We use Internet Explorer 8 to run our Siebel 8.1.1.10 version. Our Enterprise want's to install a newer IE version, but they cannot because Siebel requieres IE 8. I must admit, that I am not aware why it would not run on newer IE versions but they made a test and it failed. The solution to this would be to migrate to Open UI but due to high costs this is not an option.
However, our Windows Engeneers developed a package to run IE8 in a sandbox. So we have IE8 installed under C:/Program Files/Internet Explorer and have a sandbox folder C:/Workarea/SiebelApps Thinapp_V2/ where another Internet Explorer8.exe is located. We use a separate Registry within the sandbox folder. The target is to have IE12 installed under Program Files and IE8 in a sandbox. We are able to open the webclient using the sandbox IE8 exe and everything seems to work fine. But if we try to open the dedicated client the application doesn't start. IE shows "Internet Explorer cannot display the webpage". The URL is "http://localhost/start.swe" so this seems to be ok.
To start the dedicated Client we use the command line. We added the parameter /b pointing to the sandbox IE8 exe File (as you may see we use DEU language on Windows...)
START "" /D "C:\Programme\APP\SIA\Client_81110\BIN" "C:\Programe\APP\SIA\Client_81110\bin\siebel.exe" /c "C:\Programe\APP\SIA\Client_81110\bin\deu\zkbconnect_kfg2.cfg" /b "C:\Workarea\SiebelApps Thinapp_V2\Internet Explorer 8.exe" /u T580 /p T580 /d ServerDataSrc
It seems to me that start.swe command cannot be found.
If we remove the /b parameter so that siebel uses the IE installed under Program Files the dedicated client starts and works.
Has anyone tried to do something like this before or has a hint on how we could do this?
Kind Regards
Claudio
We found an issue description in Oracle SupportWeb. There is a problem with the /b parameter found in 8.1.1.6. The Bug has been closed without a solution. Just naming the workarround to use the default browser. However I would say that the workaround was just a way to close a bug they do not want or cannot close because you would not need /b to open Siebel in the default browser. You would just use it if you want Siebel to open in a  browser that is not set as default. So I will close this thread because there will never be a solution to this problem.
https://support.oracle.com/epmos/faces/DocumentDisplay?id=1378545.1
Nachricht geändert durch user3261506

Answer 1

Hello Chetan,
Thank you for the hints.
Dedicated Client itself works fine if we use the standard IE browser installed on the windows machine. We are just not able to start the Dedicated Client if we use the IE installed as a sandbox. Actually it is better to say, that the Dedicated Client starts, but IE throws an exception that it cannot connect to the website. It is maybe clearer if i put this in context:
Using the IE Standard Browser:
Shortcut: C:\APP\SIA\Client_81110\BIN\siebel.exe /b "C:\Program Files\Internet Explorer\iexplore.exe" /c "C:\APP\SIA\Client_81110\bin\deu\zkbconnect_eng1.cfg"
1. When I press the shortcut, Siebel asks for my credentials.
2. Type in logon Id and password
3. Dedicated Client starts in IE. URL is http://localhost/start.swe
4. Siebel Application starts and the siebel homepage is shown in IE.
--> So everything OK
Using the IE Standbox Browser (just the /b parameter is different):
Shortcut: C\APP\SIA\Client_81110\BIN\siebel.exe /b "C:\Workarea\SiebelApps Thinapp_V2\Internet Explorer8.exe" /c "C:\APP\SIA\Client_81110\bin\deu\zkbconnect_eng1.cfg"
1. When I press the shortcut, Siebel asks for my credentials.
2. Type in logon Id and password
3. Dedicated Client starts in IE. URL is http://localhost/start.swe
4. Siebel is unable to load the homepage. We get a connection error instead. "Internet Explorer cannot display the webpage"
--> NOK
We actually just want the Dedicated Client to start with a differen browser. But this failes for unknown reasons. As you mentioned we tried to renaming the exe-File so that it would not contain spaces. Unfortunatly it did not help.
The client log files doesn't show any connection error on debug level 5. So we have no idea what could be the problem is.
Our windows team is currently analysing the registry files in the sandbox to check if there is a problem. If they get me new information I will post this in the thread.
Kind Regards,
Claudio