ISPConfig3 single website using mod_jk connector

Discussion in 'General' started by DantePasquale, Nov 6, 2011.

  1. DantePasquale

    DantePasquale HowtoForge Supporter

    Hi All,

    I'm just looking for advice on this setup that I'm planning for a customer. I've installed ISPConfig3 latest update on Ubuntu 11.10 64. The customer will have a single website, www.cust.com for example. This website needs to connect to an Oracle Linux server, running Oracle 10g + JBoss 6.

    I can add mod_jk to the web server's apache2.conf file and it works OK. But, how will this all workout with ISPConfig CP?

    I'll need to modify the vhost file for the website to use jk_load etc. What would be the best way to do this so it doesn't get wiped out if they use the ISPConfig3 CP for other modifications?

    I'm thinking that ISPConfig CP may be overkill since this is a single web site, but it's easy to use and the customer has no IT experience so I thought this would be the best way to manage it.
     
  2. falko

    falko Super Moderator

    You can use the Apache Directives field on the Options tab of your website in ISPConfig. Alternatively, you can customize the vhost.master.conf template in /usr/local/ispconfig/server/conf and save your customized template in /usr/local/ispconfig/server/conf-custom (it will override the template in /usr/local/ispconfig/server/conf).
     
  3. DantePasquale

    DantePasquale HowtoForge Supporter

    Hi Falko,

    Here's what I ended up doing in the Control Panel->Sites->MySite->Options:

    Code:
    # I need to rewrite the webpage from the old webapp to the new webapp:
    RewriteEngine On
    #
    RewriteRule ^/old-webapp/(.*) /new-webapp/$1 [L,R]
    #
    # now put the directives used by jk_ajp13 to connect
    # to JBoss 6 running on the data warehouse server where our
    # EJB App is located
    # First copy the globals, used for /manager /stat
    JKMountCopy ON
    #
    #Then tell Apache to use the JkMounter to tie URLs into the worker
    #
    [B]JkMount /new-webapp/* ajp13_worker[/B]
    #
    
    Here's the workers.properties file to tell Apache to use ajp13 connector for this webpage:

    Code:
    worker.list=ajp13_worker
    
    #
    #------ ajp13_worker WORKER DEFINITION ------------------------------
    #---------------------------------------------------------------------
    #
    
    # Define worker.template so all workers can be derived from a common starting point
    #
    worker.template.type=ajp13
    worker.template.host=warehouse
    worker.template.socket_connect_timeout=5000
    worker.template.socket_keepalive=true
    worker.template.ping_mode=A
    worker.template.ping_timeout=10000
    worker.template.connection_pool_minsize=0
    worker.template.connection_pool_timeout=600
    worker.template.reply_timeout=300000
    worker.template.recovery_options=3
    worker.template.lbfactor=1
    #
    # now define our actual worker
    #
    [B]worker.ajp13_worker.reference=worker.template
    worker.ajp13_worker.port=8009[/B]
    
    And now, the web server sends the request for new-webapp to the data warehouse server running JBoss 6 and Oracle 10g on Oracle Linux 5u2.

    Thanks for the suggestion of where to put this info in the CP.
     

Share This Page