EAServer redirector plug-in

In the EAServer redirector and Web server configuration files, set up redirects to forward the onepage Web application context and other portal Web application contexts to the HTTP listeners on each EAServer. See the EAServer System Administration Guide, Chapter 9, “Web Server Redirector Plug-in,” to configure each Web server on which the EAServer redirector plug-in is running.

For example, if you are running the Apache Web server on Solaris, you would enter:

httpd.conf:

LoadModule easredirector_module libexec/libjeas_mod.so

EASConfigFile /path_to/conn_config

<LocationMatch /onepage/*|/search/*>

SetHandler eas-handler

</LocationMatch>

conn_config:

Connector.WebApp /onepage = http://gpg0.sybase.com:8080

Connector.WebApp /onepage =      http://sushi.sybase.com:8080

Connector.WebApp /search = http://sushi.sybase.com:8080

Connector.WebApp /search = http://gpg0.sybase.com:8080

...

Configuring the redirector to use HTTPS

To use HTTPS with Enterprise Portal, you need to configure the EAServer redirector to support HTTPS. You can find instructions for configuring the EAServer redirector in the EAServer release bulletin on the Sybase documentation Web page. In the section “Special installation instructions,” select “HTTPS installation instructions for Web server plug-ins.”

For the Solaris release bulletin, access:

http://sybooks.sybase.com/onlinebooks/group-eag/ear0413e/eassolrb/@Generic__BookView

For the Windows release bulletin, access:

http://sybooks.sybase.com/onlinebooks/group-eag/ear0413e/easwinrb/@Generic__BookView

After you configure the redirector according to these instructions, add these lines to the conn_config file:

Connector.Https.qop
<sybpks_simple|sybpks_intl|sybpks_domestic|sybpks_strong>
Connector.Https.pin <sybase>
Connector.Https.cacheSize <100>
Connector.Https.SessLingerTime <28800>
Connector.Https.SessShareCount <10>

Using the EAServer redirector, you can run the Portal in either full HTTP mode or full HTTPS mode; you cannot mix the two protocols. For example, this setup works:

Connector.Webapp /onepage = http://jag.sybase.com:8080,...

Connector.Webapp /onepage = https://jag.sybase.com:8443,...

This setup does not work:

Connector.Webapp /onepage = https://jag.sybase.com:8080,...

Connector.Webapp /onepage = http://jag.sybase.com:8443,...

The Web server must run on the same HTTP and HTTPS ports as the EAServer ports on which Enterprise Portal is running. For example, if EAServer is running on ports 8080 and 8081 for its HTTP and HTTPS requests, you must configure the Web server to run on ports 8080 and 8081 as well.