Forum Discussion

Ace_39087's avatar
Ace_39087
Icon for Nimbostratus rankNimbostratus
Nov 12, 2008

Siebel Web

We have been using F5 LTM for quite a while now. We have a fairly standard method for configuring the LTM for our web services. The setup is pretty simple. We have two Virtual servers. One for port 80 and one for SSL. We redirect port 80 to the port 443 vip. We terminate ssl on the LTM. Our pool members are the webservers on the various ports.

 

 

We have just begun to implement Siebel in our enterprise. We found that when we do any port translation to between reverse proxies and/or the LTM the Siebel app does not work. If we use the same port numbers for the LTM, the reverse proxy, and the Siebel web server the app works fine.

 

 

Has anyone else dealt with this issue? Do you have any work arounds?

 

 

Thanks!
oracle
partner

1 Reply

Sort By
  • Ace_39087's avatar
    Ace_39087
    Icon for Nimbostratus rankNimbostratus
    Nov 12, 2008
    Found this on the Siebel Bookshelf:

     

    http://download.oracle.com/docs/cd/B40099_02/books/Secur/Secur_PhysDeploy3.html

     

    Siebel Business Applications do not support the translation of port numbers or protocol switching. An example of protocol switching is changing from HTTP to HTTPS. If you deploy SSL between the client and the reverse proxy server, then you must deploy SSL between the reverse proxy server and the Web server on which the Siebel Web Server Extension (SWSE) is installed. Similarly, if you deploy SSL between the reverse proxy server and the Web server, then you must deploy it between the client and the reverse proxy server.

     

    Port Translation breaks Siebel App.