The following example is a sample installation snapshot of Policy Agent 2.2 for Apache Tomcat Servlet/JSP Container. By no means does this sample represent a real deployment scenario.
The section following this example, Implications of Specific Deployment Scenarios in Agent for Apache Tomcat Servlet/JSP Container, provides a short explanation about installing a J2EE agent on multiple Apache Tomcat Servlet/JSP Container instances. If your deployment includes multiple instances of the deployment container, you might want to review that section before proceeding with the agent installation. See Installing a J2EE Agent on Multiple Apache Tomcat Servlet/JSP Container Instances.
************************************************************************ Welcome to the Access Manager Policy Agent for Apache Tomcat 5.5 Servlet/JSP Container ************************************************************************ Enter the complete path to the directory which is used by Tomcat Server to store its configuration Files. This directory uniquely identifies the Tomcat Server instance that is secured by this Agent. [ ? : Help, ! : Exit ] Enter the Tomcat Server Config Directory Path [/opt/jakarta-tomcat-5.5.9/conf]: Enter the fully qualified host name of the server where Access Manager Services are installed. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Host: accessmanager.example.com Enter the port number of the Server that runs Access Manager Services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services port [80]: 8880 Enter http/https to specify the protocol used by the Server that runs Access Manager services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Protocol [http]: Enter the Deployment URI for Access Manager Services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Deployment URI [/amserver]: Enter the fully qualified host name on which the Application Server protected by the agent is installed. [ ? : Help, < : Back, ! : Exit ] Enter the Agent Host name: mycomputer.example.com $CATALINA_HOME environment variable is the root of the tomcat installation. [ ? : Help, < : Back, ! : Exit ] Enter the $CATALINA_HOME environment variable: /opt/jakarta-tomcat-5.5.9/ Choose yes to deploy the policy agent in the global web.xml file. [ ? : Help, < : Back, ! : Exit ] Install agent filter in global web.xml ? [true]: Enter the preferred port number on which the application server provides its services. [ ? : Help, < : Back, ! : Exit ] Enter the port number for Application Server instance [80]: 8080 Select http or https to specify the protocol used by the Application server instance that will be protected by Access Manager Policy Agent. [ ? : Help, < : Back, ! : Exit ] Enter the Preferred Protocol for Application Server instance [http]: Enter the deployment URI for the Agent Application. This Application is used by the agent for internal housekeeping. [ ? : Help, < : Back, ! : Exit ] Enter the Deployment URI for the Agent Application [/agentapp]: Enter a valid Encryption Key. [ ? : Help, < : Back, ! : Exit ] Enter the Encryption Key [/gyU5SVWPY/B4TxWhC9m36Bz7pYdcXMS]: Enter a valid Agent profile name. The agent profile name is used to identify the agent in Access Manager. [ ? : Help, < : Back, ! : Exit ] Enter the Agent Profile name: j2ee Enter the path to a file that contains the password to be used for identifying the Agent. [ ? : Help, < : Back, ! : Exit ] Enter the path to the password file: /opt/test ----------------------------------------------- SUMMARY OF YOUR RESPONSES ----------------------------------------------- Tomcat Server Config Directory : /opt/jakarta-tomcat-5.5.9/conf Access Manager Services Host : accessmanager.example.com Access Manager Services Port : 8880 Access Manager Services Protocol : http Access Manager Services Deployment URI : /amserver Agent Host name : mycomputer.example.com $CATALINA_HOME environment variable : /opt/jakarta-tomcat-5.5.9/ Tomcat global web.xml filter install : true Application Server Instance Port number : 8080 Protocol for Application Server instance : http Deployment URI for the Agent Application : /agentapp Encryption Key : /gyU5SVWPY/B4TxWhC9m36Bz7pYdcXMS Agent Profile name : j2ee Agent Profile Password file name : /opt/test Verify your settings above and decide from the choices below. 1. Continue with Installation 2. Back to the last interaction 3. Start Over 4. Exit Please make your selection [1]: 1 Updating the /opt/jakarta-tomcat-5.5.9/bin/setclasspath.sh script with the Agent classpathDONE. Creating directory layout and configuring AMAgent.properties file for agent_001 instance ...DONE. Reading data from file /opt/test and encrypting it ...DONE. Generating audit log file name ...DONE. Creating tag swapped AMAgent.properties file for instance agent_001 ...DONE. Creating a backup for file /opt/jakarta-tomcat-5.5.9/conf/server.xml ...DONE. Creating a backup for file /opt/jakarta-tomcat-5.5.9/conf/web.xml ...DONE. Adding SJS Tomcat Agent Realm to Server XML file : /opt/jakarta-tomcat-5.5.9/conf/server.xmlDONE. Adding filter to Global deployment descriptor file : /opt/jakarta-tomcat-5.5.9/conf/web.xmlDONE. Adding SJS Tomcat Agent Filter and Form login authentication to selected Web applicationsDONE. |