Web Application Developer’s Guide phần 10 pps

Using the Borland Enterprise Server Web Edition 18-11

Modifying Web component connection

Modifying Web component connection

Borland Enterprise Server Web Edition provides an operational Apache

Web Server and Tomcat Web Container connection as “out of the box”

upon start up. The two components are connected with each other via the

IIOP Plug-in. This Plug-in allows both Apache and Tomcat to

communicate via Internet Inter-ORB Protocol (IIOP) to one another with

no required configuration.

Figure 18.5 Web components connection via IIOP

jss.softCommit=<true or false> Write to disk but only for crash recovery and not

a full transaction commit.

jss.userName=<char_string> This is the name of the database user.

jss.factoryName=<char_string> The name given to the JSS factory created by this

service. The service gets registered with this

name in the Smart Agent (osagent).

jss.workingDir=<path> The path of the working directory where the

database files are stored.

jss.pstore=<char_string> The name of the database file that gets created

under the jss.workingDir.

Table 18.2 JSS Properties (continued)

Property Name Description

18-12 Web Application Developer ’ s Guide

Modifying Web component connection

Modifying Apache

To modify the Apache Web Server to a Tomcat Web Container, use the

following steps:

1 Open the configuration file, httpd.conf. It is located in the directory

path, such as:

<bes_home>\var\servers\<server_name>\apache1\conf\

You must edit the file by adding new lines of instruction discussed in

the following steps.

2 Load the mod_webapp using the LoadModule directive. You are

loading a new connection using a module name.

LoadModule webapp_module <bes-install>/lib/apache/ mod_webapp.so

Note The webapp_module is a dynamic library.

3 Tell Apache about the connection using the WebAppConnection directive.

Have a new connection based on the name of the Tomcat server.

WebAppConnection myConnection iiop "tc_inst1"

Note The name corresponds to the name you defined for the Tomcat IIOP

connector instance. In this case, "tc_inst1" is the IIOP connector

instance for Tomcat.

4 Tell Apache to use the WebAppDeploy directive for request handling.

The IIOP service will handle client request starting with the URL

/examples/.

WebAppDeploy examples myConnection /examples/

Note You can have multiple line entries for each deployments.

5 When completed, Save and exit the file.

Modifying the Connector in Tomcat

By default the Apache Web Server and Tomcat Web Container are

connected via the IIOP Plug-in. However, you can change the connection

configuration for this service in the configuration file, server.xml. This

service has a Connector named IIOP. It is capable of sending and receiving

IIOP messages by actually talking to the Apache Web Server for getting a

request and sending the response.

The IIOP service is separated into two portions; the Connector and the

Engine/Host.

Here is an example of the Connector portion:

<Service name="IIOP">

<Connector

className="org.apache.catalina.connector.iiop.IiopConnector"

name"tc_inst1"

/>

where "tc_inst1" is the name that Apache must point to.