For the installation process, follow the steps as described in Chapter 3, Installing Policy Agent 2.2 for BEA WebLogic Server/Portal 9.2. However, see the example installation interaction that follows in this section for an example that is specific to BEA WebLogic Portal 9.2. Notice in the interaction, the following two portal-specific prompts:
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]: true
Enter the Deployment URI for the portal application that is protected by the agent. [ ? : Help, < : Back, ! : Exit ] Enter the Deployment URI for the portal Application [/]: /groupspace
As the two preceding prompt examples indicate, to install this agent on BEA WebLogic Portal 9.2, provide a response of true to the first of these prompts, which in effect invokes the second prompt. For the second prompt, provide the name of the application to be protected. For the example used in this appendix, the sample portal is the application to be protected. Again, the default portal is named groupspace.
Notice that a summary of the agent installation is included at the end of this example interaction. However, the installation summary is described more thoroughly in Summary of a J2EE Agent Installation in Policy Agent 2.2. See that section if you would like a more thorough explanation of the installation summary.
************************************************************************ Welcome to the Access Manager Policy Agent for BEA WebLogic 9.2 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/weblogic92/samples/domains/portal/startWebLogic.sh Enter the name of the WebLogic Server instance secured by the agent. [ ? : Help, < : Back, ! : Exit ] Enter the WebLogic Server instance name [myserver]: portalServer Enter the fully qualified host name of the server where Access Manager Services are installed. [ ? : Help, < : Back, ! : Exit ] Access Manager Services Host: amHost.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]: 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: agentHost.example.com Enter the WebLogic home directory [ ? : Help, < : Back, ! : Exit ] Enter the WebLogic home directory [/usr/local/bea/weblogic92]: 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]: true Enter the Deployment URI for the portal application that is protected by the agent. [ ? : Help, < : Back, ! : Exit ] Enter the Deployment URI for the portal Application [/]: /groupspace 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]: 7041 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 [VBjnVlCEgfez/ivS34ALv0c41Ym7gWyX]: 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: exampleagentportal 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/tmp/portalpasswordfile 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/weblogic92/samples/domains/portal/startWebLogic.sh WebLogic Server instance name : portalServer Access Manager Services Host : amHost.example.com Access Manager Services Port : 58080 Access Manager Services Protocol : http Access Manager Services Deployment URI : /amserver Agent Host name : agentHost.example.com WebLogic home directory : /usr/local/bea/weblogic92 Agent Installed on Portal domain : true Deployment URI for the portal Application : /groupspace Application Server Instance Port number : 7041 Protocol for Application Server instance : http Deployment URI for the Agent Application : /agentapp Encryption Key : VBjnVlCEgfez/ivS34ALv0c41Ym7gWyX Agent Profile name :exampleagentportal Agent Profile Password file name : /export/tmp/portalpasswordfile 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]: ... ... SUMMARY OF AGENT INSTALLATION ----------------------------- Agent instance name: agent_001 Agent Configuration file location: PolicyAgent-base/j2ee_agents/am_wl92_agent/agent_001/config/ AMAgent.properties Agent Audit directory location: PolicyAgent-base/j2ee_agents/am_wl92_agent/agent_001/logs/audit Agent Debug directory location: PolicyAgent-base/j2ee_agents/am_wl92_agent/agent_001/logs/debug Install log file location: PolicyAgent-base/j2ee_agents/am_wl92_agent/logs/audit/install.log Thank you for using Access Manager Policy Agent |
Once the installation is complete, perform the applicable installation-related tasks described in Implications of Specific Deployment Scenarios in Agent for BEA WebLogic Server/Portal 9.2.