The following example is a sample installation snapshot of Policy Agent 2.2 for BEA WebLogic Server/Portal 8.1 SP4. By no means does this sample represent a real deployment scenario.
The section following this example, Implications of Specific Deployment Scenarios in Agent for BEA WebLogic Server/Portal 8.1 SP4, explains specific deployment scenarios, such as installing the agent on a portal domain. If any of these deployment scenarios apply to your deployment, you might need 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 BEA WebLogic Server/Portal 8.1 SP4 Instances on the Same Domain
Installing Agent for BEA WebLogic Server/Portal 8.1 SP4 on a Portal Domain
Installing Agent for BEA WebLogic Server/Portal 8.1 SP4 on the Access Manager Host
************************************************************************ Welcome to the Access Manager Policy Agent for BEA WebLogic 8.1 SP4 Platform. If the Policy Agent is used with Federation Manager services, User needs to enter information relevant to Federation Manager. ************************************************************************ Enter the path to the location of the script used to start the WebLogic domain. Please ensure that the agent is first installed on the admin server instance before installing on any managed server instance. [ ? : Help, ! : Exit ] Enter the Startup script location [/usr/local/bea/user_projects/domains/mydomain/startWebLogic.sh]: /usr/local/bea/user_projects/domains/serverdomain/startWebLogic.sh Enter the name of the WebLogic Server/Portal instance secured by the agent. [ ? : Help, < : Back, ! : Exit ] Enter the WebLogic Server/Portal instance name [myserver]: Enter the fully qualified host name of the server where Access Manager Services are installed. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Host: subcompany22.company22.example.com Enter the port number of the Server that runs Access Manager Services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services port [80]: 58080 Enter http/https to specify the protocol used by the Server that runs Access Manager services. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Protocol [http]: 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: employee.company22.example.com Enter the WebLogic home directory [ ? : Help, < : Back, ! : Exit ] Enter the WebLogic home directory [/usr/local/bea/weblogic81]: Enter true if the agent is being installed on a Portal domain [ ? : Help, < : Back, ! : Exit ] Is the agent being installed on a Portal domain ? [false]: false 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]: 7001 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]: 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 [KpsVJMr84cwd6OATx+UgLWHSCB8KWFVW]: 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: exampleagent 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: /export/temp/passwordfile 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 ----------------------------------------------- Startup script location : /usr/local/bea/user_projects/domains/mydomain/startWebLogic.sh WebLogic domain name : myserver Access Manager Services Host : subcompany22.company22.example.com Access Manager Services Port : 58080 Access Manager Services Protocol : http Access Manager Services Deployment URI : /amserver Agent Host name : employee.company22.example.com WebLogic home directory : /usr/local/bea/weblogic81 Agent Installed on Portal domain : false Application Server Instance Port number : 7001 Protocol for Application Server instance : http Deployment URI for the Agent Application : /agentapp Encryption Key : KPsVJMr84cwd6OATx+UgLWHSCB8KWFVW Agent Profile name : exampleagent Agent Profile Password file name : /export/temp/passwordfile 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]: ************************************************************************ Welcome to the Access Manager Policy Agent for BEA WebLogic 8.1 SP4 Platform. If the Policy Agent is used with Federation Manager services, User needs to enter information relevant to Federation Manager. ************************************************************************ |