Chapter 4: Installing and Configuring a Web Server Redirector Plug-In

Mapping Web server requests to EAServer listeners

Create and edit the redirector configuration file to add the Connector.WebApp directive, which maps requests sent to the redirector by the Web server to EAServer HTTP listeners. The syntax is:

Connector.WebApp contextpath1 [, contextpath2, and so on] =
http://host:port [, http://host:port, and so on]

For example, if “neptune” is the name of your Web server, and WEB_SERVER_HOME/https-neptune/config/conn_config is the name and location of the redirector configuration file, edit conn_config to:

Connector.WebApp /testapp = http://jaghost1:8080
Connector.WebApp /estore1, /estore2, /estore3 = http://neptune:8080
Connector.WebApp /* = http://foobar:8080, http://neptune:8080
Connector.WebApp examples=http://jaghost1:8080, http://jaghost1:3080, http://jaghost2:8080

In the first line, the “testapp” Web application maps to the EAServer HTTP listener http://jaghost1:8080.

For example, if your Web server is accepting requests on the host machine web_server on port 8020 and the client sends the request http://web_server:8020/testapp/test.jsp, the redirector forwards the request to http://jaghost1:8080/testapp/test.jsp.
In the second line, the /estore1, /estore2, and /estore3 Web applications map to the EAServer HTTP listener http://neptune:8080.

For example, if your Web server is accepting requests on the host machine web_server on port 8020 and the client sends the request http://web_server:8020/estore1/sign_in.jsp, the redirector forwards the request to http:/neptune:8080/estore1/sign_in.jsp.
In the third line, “/*” matches any request that is received by the connector, provided the request did not match any of the other specifically configured Web applications. However, you still need to configure the Netscape Web server to tell it which context paths should be serviced by this connector. For this mapping, you would supply the following NameTrans directive in the obj.conf file:
```
NameTrans fn="assign-name" from="/*" name="EASProxy"
```
The redirector configuration file must contain the following mapping rule for each EAServer that you want to handle requests:
```
Connector.WebApp /* = http://jaguar_host:jaguar_listener
```
Where jaguar_host is the EAServer host machine and jaguar_listener is the EAServer HTTP listener.
The last line in the example above is a load-balancing example, where the “examples” Web application is available at jaghost1:8080, jaghost1:3080, and jaghost2:8080.

Single-line entries

You must make entries in the redirector configuration file on a single line, but you can combine EAServer hosts in one entry or multiple entries. For example:

Connector.WebApp /*=http://rainforest:8080,http://neptune:8080

Is the same as:

Connector.WebApp /*=http://rainforest:8080

Connector.WebApp /*=http://neptune:8080

In addition, the server hosts specified by the WebApp directive (in this case, “rainforest” and “neptune”) must match the host names you define for your EAServer HTTP listeners. Use EAServer Manager to view and set host names for your EAServer HTTP listeners—see Chapter 3, “Creating and Configuring Servers,” in the EAServer System Administration Guide for more information.

View this book as PDF