The following example is a sample installation snapshot of Policy Agent 2.2 for WebSphere Application Server 6.1. By no means does this sample represent a real deployment scenario.
The section following this example, Implications of Specific Deployment Scenarios in Agent for WebSphere Application Server 6.1, explains specific deployment scenarios, such as installing the agent on the Access Manager host. If any of these deployment scenarios apply to your site's deployment, you might be required to respond to prompts in a specified manner during the installation as explained in that section. Review the explanations in that section before proceeding with the installation. Those explanations are divided into subsections as follows:
Installing a J2EE Agent on Multiple WebSphere Application Server 6.1 Instances
Installing Agent for WebSphere Application Server 6.1 on the Access Manager Host
The following install interaction example is specific to Windows systems. A different, but similar, set of interactions have to be executed for the other supported platforms.
************************************************************************ Welcome to the Access Manager Policy Agent for IBM WebSphere Application Server 6.0 If the Policy Agent is used with Federation Manager services, User needs to enter information relevant to Federation Manager. ************************************************************************ Enter the fully qualified path to the configuration directory of the Server Instance for the WebSphere node. [ ? : Help, ! : Exit ] Enter the Instance Config Directory [C:\Program Files\IBM\WebSphere\AppServer\profiles\default\config\cells\<Hostname>Node01Cell\nodes\ <Hostname>Node01\servers\server1]: C:\Program Files\IBM\WebSphere\AppServer\profiles\default\config\cells\<Hostname> Node01Cell\nodes\<Hostname>Node01\servers\server1 Enter the Server Instance name. [ ? : Help, < : Back, ! : Exit ] Enter the Server Instance name [server1]: Enter the WebSphere Install Root directory. [ ? : Help, < : Back, ! : Exit ] Enter the WebSphere Install Root directory [C:\Program Files\IBM\WebSphere\AppServer]:C:\ProgramFiles\IBM\WebSphere\AppServer Enter the fully qualified host name of the server where Access Manager Services are installed. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Host: AMhostname.test.domain.com Enter the port number of the Server that runs Access Manager Services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services port [80]: 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: AgentHostName.test.domain.com 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]: 9080 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 [bFa6Euq9fAI0gVK+jnxyE2aNvwySJ42f]: Enter a valid Agent profile name. Before proceeding with the agent installation, please ensure that a valid Agent profile exists in Access Manager. [ ? : Help, < : Back, ! : Exit ] Enter the Agent Profile name: agentprofilename 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: C:\tmp\passfile Enter true if the Agent is being installed on the same instance of Application Server on which Access Manager is deployed. Enter false if that is not the case. [ ? : Help, < : Back, ! : Exit ] Are the Agent and Access Manager installed on the same instance of Application Server ? [false]: ----------------------------------------------- SUMMARY OF YOUR RESPONSES ----------------------------------------------- Instance Config Directory : C:\Program Files\IBM\WebSphere\AppServer\profiles\default\config\cells\ <Hostname>Node01Cell\nodes\<Hostname>Node01\servers\server1 Instance Server name : server1 WebSphere Install Root Directory : C:\ProgramFiles\IBM\WebSphere\AppServer Access Manager Services Host : AMhostname.test.domain.com Access Manager Services Port : 80 Access Manager Services Protocol : http Access Manager Services Deployment URI : /amserver Agent Host name : AgentHostName.test.domain.com Application Server Instance Port number : 9080 Protocol for Application Server instance : http Deployment URI for the Agent Application : /agentapp Encryption Key : bFa6Euq9fAI0gVK+jnxyE2aNvwySJ42f Agent Profile name : agentprofilename Agent Profile Password file name : C:\tmp\passfile Agent and Access Manager on same application server instance : false 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]: Please make your selection [1]: 1 Copy agent.jar,amclientsdk.jar to C:\WAS60\IBM\WebSphere\AppServer/lib/ext...DONE. Creating directory layout and configuring AMAgent.properties file for agent_001 instance ...DONE. Reading data from file C:\export\pass 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 C:\WAS60\IBM\WebSphere\AppServer\profiles\default\config\cells\<HostName>Node01Cell\nodes\ <HostName>Node01\servers\server1/server.xml ...DONE. Configure server.xml file C:\WAS60\IBM\WebSphere\AppServer\profiles\default\config\cells\<HostName>Node01Cell\nodes\ <HostName>Node01\servers\server1/server.xml...DONE. SUMMARY OF AGENT INSTALLATION ----------------------------- Agent instance name: agent_001 Agent Configuration file location: C:/exportwas60/j2ee_agents/am_websphere_agent/agent_001/config/AMAgent.properties Agent Audit directory location: C:/exportwas60/j2ee_agents/am_websphere_agent/agent_001/logs/audit Agent Debug directory location: C:/exportwas60/j2ee_agents/am_websphere_agent/agent_001/logs/debug Install log file location: C:/exportwas60/j2ee_agents/am_websphere_agent/logs/audit/install.log Thank you for using Access Manager Policy Agent |