Installing the Publishing Web Agent

If you intend to deploy Web content (static text and binary files) to your staging and production Web servers, install and configure a Publishing Web agent on each Web server. While the Publishing Web agent is installed with the Adaptive Scenario Engine, its configuration is primarily for demonstration and evaluation purposes; a Publishing Web agent is not typically run on an ATG server.

Note: You use the ATG Web Server Extensions installer to install the Publishing Web agent. You can also use it to install a DistributorServer for a Content Distributor system. For information on using the installer to do so, as well as general information on Content Distributor systems, see the Content Distribution chapter in the ATG Programming Guide.

Installing on Windows

To install the Publishing Web agent on a Web server running on Windows:

  1. Make sure the Web server machine has a Java Virtual Machine installed.

  2. Download the ATG Web Server Extensions executable file from the Oracle Web site.

  3. Run the ATG Web Server Extensions executable.

    The installer displays the Welcome dialog box.

  4. Click Next

  5. Specify the installation directory for the Publishing Web agent. The default (and recommended) directory is c:\ATG\ATGWeb2007.3

  6. Click Next

    The installer displays the list of Web server extensions you can configure during the installation process. By default, the DistributorServer and the Publishing Web agent are both selected. You can uncheck the DistributorServer option for this installation.

    For information on configuring the DistributorServer for a Content Distributor system, see the Content Distribution chapter in the ATG Programming Guide.

  7. Click Next

  8. Specify the RMI port to be used by the Publishing Web agent. The default is 8860.

    Note: Later in the deployment setup process, you must specify the same port number for the Web agent in the deployment configuration UI. See Define the Deployment Topology for more information.

  9. Click Next

  10. Specify the local directory to be used by the Publishing Web agent. The default is C:\ATG\ATGWeb2007.3\home\doc. You can specify the Web server’s document root directory or any subdirectory within the root directory.

  11. Click Next

  12. Specify a name for the program folder that the installer will create within the Windows Programs folder. The default is ATG 2007.3\ATG Web Server Extensions. The program folder will contain a shortcut for starting the Publishing Web agent.

  13. Click Next

    The installer displays the installation directory you selected and indicates it is ready to install the Publishing Web agent.

  14. Review the setup information:

    • Click Next to start the installation

    • Click Back to change any settings

  15. After installation is complete, click Finish to close the installer.

Installing on UNIX

To install the Publishing Web agent on a Web server running on UNIX:

  1. Make sure the Web server machine has a Java Virtual Machine installed.

  2. Download from the Oracle website the ATG Web Server Extensions JAR file, ATGWebServerExtensions2007.3.jar (the file name might include a build number).

  3. Unpack the JAR file:

    jar xvffilename

    This creates an ATGWeb2007.3 subdirectory within the current directory.

  4. Change to the ATGWeb2007.3/home directory.

  5. Make sure you have read and write permissions for the install script with this command or its equivalent:

    chmod +x bin/Install

  6. Run the Install script with this command:

    bin/Install

    The system lists the Web server extensions that you can configure during the installation process.

  7. To configure the Publishing Web agent, enter b

  8. Enter the local directory to be used by the Publishing Web agent. The default is:

    /rootname/username/ATGWeb2007.3/home/doc

    You can specify the Web server’s document root directory or any subdirectory within the root directory.

  9. Enter the RMI port to be used by the Publishing Web agent. The default is 8860.

    Note: Later in the deployment setup process, you must specify the same port number for the Web agent in the deployment configuration UI. See Define the Deployment Topology for more information.

 
loading table of contents...