Application Server Solutions for Microsoft IIS and ASP.NET
       solutions   products   partners   company   support   downloads         store
ServletExec Self-Help: FAQ
Back to Search >  Back to Search Results

Faq ID 15
Product ServletExec
Category Installation
Question Can ServletExec be installed with Stronghold?
Answer Here are the steps to get SE 4.2 AS installed and running with the StrongHold 4 webserver on a Solaris 7 machine:
  1. Setup your StrongHold 4 with a server ID by following the instructions given in the StrongHold 4 installation and admin guide, and make sure it works on both port 80 and port 443.
    Note: this step involves obtaining a signed certificate request from a well-known CA and using the StongHold4 utililty "bin/getca" to install that signed certificate.
  2. If you run the SE 4.2 AS installer against StrongHold 4, the installer will fail to complete and will actually delete all the ServletExec files and folders that had been created before the failure.
    Note: In our tests, the SE 4.2 installer fails to successfully use StrongHold's apxs script to build mod_servletexec.c due to it not liking the
    "-fno-strict-aliasing" parameter specified in StrongHold's apxs script.
    For this reason you will first need to run the SE 4.2 AS installer against a regular version of Apache (i.e. a non-StrongHold version of Apache). This will "trick" the installer into creating the SE folders and files that are required for the SE AS 4.2 Java instance. If you do not want the installer to modify the httpd.conf file of this regular Apache version, then choose "no" when the installer asks whether you want it to make manual edits to httpd.conf for you. In this way, the SE adapter module will not be "hooked into" the regular Apache version in any way.
  3. Modify /extra/stronghold4/bin/apxs to remove the "-fno-strict-aliasing" portion from the 3rd variable:

    $CFG_CFLAGS = q( -DSOLARIS2=270 -DMOD_SSL=208107 -DMOD_PERL -DUSE_PERL _SSI -O2 -fno-strict-aliasing -DEAPI -DEAPI_MM -O2 '../apaci');
  4. Manually invoke the StrongHold 4 apxs script without the "-i" parameter:
    /extra/stronghold4/bin/apxs -n servletexec -a -c mod_servletexec.c
    to compile the mod_servletexec.c sitting at .../ServletExecAS/bin/mod_servletexec.c.
    Warnings can be ignored.
  5. Ensure that the created mod_servletexec.so now resides at:
    /extra/stronghold4/lib/modules/1.3
    if it does not, then copy it there.
  6. Now you must make manual edits to the StrongHold 4 httpd.conf file.
    These edits are discussed in the SE 4.2 Intallation Guide, but they look something like this:

    LoadModule servletexec_module lib/modules/1.3/mod_servletexec.so
    ...
    ...
    ServletExecInstances inst-01 127.0.0.1:8888
    ServletExecAliases inst-01 /servlet .jsp
    ServletExecApplications inst-01 /myApp1, /myApp2

    <Location /servlet>
    SetHandler servlet-exec
    </Location>

    <Location /myApp1>
    SetHandler servlet-exec
    </Location>

    <Location /myApp2>
    SetHandler servlet-exec
    </Location>

    AddHandler servlet-exec jsp


Now the SE 4.2 AS native adapter has been built and "hooked-into" StrongHold 4 and it has been configured to connect with the SE AS 4.2 Java instance that was created during the install against the regular Apache version.

Note: If you use SE 5.x (or higher) then please realize that the httpd.conf edits for SE 4.x (shown above) are different than the edits that would be made for SE 5.x.
To understand the edits that must be made for SE 5.x please see section 6.5.3.2 entitled: "Server Configuration File (httpd.conf)" in the SE 5.0 Installation Guide. With SE 5, it's only 2 or 3 lines that get added to httpd.conf.



   
company media information terms of use privacy policy contact us