apache2+resin2.x Cluster Configuration Combat

apache2+resin2.x cluster configuration

Test environment:

Required Software: apache2.x, resin2.x

Required Computers: 2 units

Machine A:ip 192.168.1.119

1. Install Good apache2.x

2. Modify Apache httpd.conf configuration file, Include conf/include/remote-resin.conf

3. Generate remote-resin.conf placed in the Apache Conf/include directory, without creating a

4. remote-resin.conf file Content

<IfModule !mod_caucho.c>
LoadModule caucho_module "<your mod_caucho.dll path>/mod_caucho.dll"
CauchoHost 211.111.8.86 6804
<Location /ws2>
SetHandler caucho-request
</Location>
<Location /caucho-status>
SetHandler caucho-status
</Location>
</IfModule>

Restart Apache in the Address bar input http://192.168.1.119/caucho-status should see something, uh huh

Machine B:ip 211.111.8.86

1. Install Good resin2.x

2. Modify Resin.con

<srun host='211.111.8.86' port='6804' srun-index="1"/>

Open Srun listening port, corresponding to Apache configuration

Add a row

<web-app id="/ws2/" app-dir="/wwwroot/webapps/ws2"/>

Make sure this thing is there, the path is not wrong, write in Http-server.

3. Start resin again visit Http://192.168.1.119/caucho-status will see another scene, visit Http://192.168.1.119/ws2 will see the deployment of a good app ws2 on machine B.

If you have more than one machine, you can repeat the installation of step B machine, srun There are other uses, look at the resin manual.

In the actual application feel very good, no longer need to update n access to the program and data, update a machine can, of course, to the firewall on the limit, or anyone can connect to resin up. Configured to be more comfortable than JK2 connected Tomcat.