去掉路径中的opencms.docVIP

Using mod_proxy This page explains how to integrate the Apache httpd, Apache Tomcat and OpenCms 7 so that all static resources (e.g. images or binaries) are served directly by the Apache Webserver dynamic resources are served by OpenCms through Tomcat The /opencms/opencms/ prefix usually required for OpenCms will be supressed This configuration has been tested with the following components: Apache httpd webserver 2.0.54 (should work with all stable versions of Apache httpd 2.0, version 1.3 will not work) Apache Tomcat 5.5.7 (other versions that support the CoyoteConnector should work fine) OpenCms 7 Please note: Make sure that all your server names are correctly configured in your DNS before you continue with this installation. If a server can not be reached with the name(s) used in the configuration files below, the setup will not work. This document describes the required steps to setup the following scenario: The OpenCms server is named ${DOMAIN_NAME} The server will be served from a Tomcat installation located in the directroy ${TOMCAT_HOME} Tomcat and Apache do run on the same machine (server hardware) Please note:?Replace the previous defined variables for your environment, ie. instead?of?${DOMAIN_NAME} use your domain name, ie.?, and instead of ${TOMCAT_HOME}?use your?tomcat home path, ie.? /opt/tomcat/. Please note: This document does not enable the Static-Export feature that needs additional configuration steps, a related Static-Export feature configuration document is available in the com.alkacon.documentation.documentation_staticexport documentation module. Step 1: Installing OpenCms Provided that you have a basic setup of Apache Tomcat and Apache httpd, you should install OpenCms in the ${TOMCAT_HOME}/webapps/ directory first, without modifiying the default Tomcat configuration. In order for this setup to work you must install OpenCms as the ROOT Tomcat servlet context. Read on to learn how to do so. You have to delete or rename the Tomcat default