Documentation Center

Changing the Application Context URL

Changing the application context lets you change the application's URL to help Legacy Content Delivery fit into your web hierarchy. It can be important to change your site URL to / if you want your site to be indexed by search engines, because many have a verification file that they want you to put into the / folder.

About this task

If you change the URL, you can access Legacy Content Delivery by browsing to http://delivery.lc.example.com/ (where lc refers to an example related to output, and delivery specifies it further as a delivery server) instead of http://delivery.lc.example.com/LegacyContentDelivery/

By default, the URL you use to access Legacy Content Delivery is http://delivery.lc.example.com/LegacyContentDelivery/. In this URL, /LegacyContentDelivery is the application context.

To access Legacy Content Delivery using a URL that does not have the port number, set the Legacy Content Delivery port number to 80, the default HTTP port.

Procedure

  1. For an Apache tomcat web server application (for any other web server application, refer to its documentation):
    1. Open the TOMCAT HOME/conf/server.xml file.
    2. Add the following before the </Host> element (before the beginning of the <Engine> element)
         <Host name="localhost"  appBase="webapps" unpackWARs="true" autoDeploy="true">
      
       
      
              <Valve className="org.apache.catalina.valves.AccessLogValve" directory="logs"
      
                     prefix="localhost_access_log." suffix=".txt"
      
                     pattern="%h %l %u %t &quot;%r&quot; %s %b" />
      
       
      
                <!-- This line should be added for removing the context from the URL --> 
      
                <Context path="" docBase="LiveContent" xmlBlockExternal="false"/>
      
       
      
            </Host>
      This makes Legacy Content Delivery the default application on the web server.
  2. Stop, and then restart the web server.
  3. Start Legacy Content Delivery .
  4. Clear the cache.
    1. In the breadcrumb trail, click Home.
    2. In the Administration Tools pane, click Manage Application.
    3. Click Global Config.
    4. Click Clear Cache.

Results

You can now invoke Legacy Content Delivery using www.delivery.lc.example.com (instead of using www.delivery.lc.example.com/LegacyContentDelivery ).