Installation and Upgrade > Installation and Configuration Guide > Advanced Configurations > Configuring PTC HTTP Server and Embedded Servlet Engine With Other Options > Installation and Configuration of the PTC HTTP Server: Before You Begin
  
Installation and Configuration of the PTC HTTP Server: Before You Begin
The typical installation and configuration scenario for PTC HTTP Server is that PTC HTTP Server is installed on the same machine as Windchill (local) and configured to support HTTP requests. Embedded Servlet Engine must be installed on the Windchill machine, as this is the only scenario PTC supports at this time. There are, however, other scenarios you may have for your environment, for example, running PTC HTTP Server on a machine other than Windchill (remote), reinstalling PTC HTTP Server after its initial installation, or running PTC HTTP Server in a more secure environment such as HTTPS.
The additional instructions in this chapter include:
Setting Up PTC HTTP Server Ant -- PTC HTTP Server Ant is a Java-based build tool used by PTC to configure and reconfigure PTC HTTP Server (and Embedded Servlet Engine) for Info*Engine and Windchill.
Configurations When PTC HTTP Server is Installed Remotely -- Instructions for configuring PTC HTTP Server when it is installed on a different machine than Windchill.
Running Embedded Servlet Engine and PTC HTTP Server As Windows Services -- Setting up Embedded Servlet Engine and PTC HTTP Server as a Windows service using Ant.
Configuring a Non-PTC Apache (manual installation)-- Configurations for using an existing Apache installation with Windchill.
Specifying Web Server Authentication -- Using Ant commands to specify various web server authentication items for PTC HTTP Server.