************************************************************************
Welcome to the Access Manager Policy Agent for IBM WebSphere Portal Server
5.1.0.2 Agent. 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. Please ensure that the installer is run on
the WebSphere instance that will host the WebSphere Administration Console
first before the installer is run on the WebSphere Portal instance.
[ ? : Help, ! : Exit ]
Enter the Instance Config Directory
[/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name]: 


Enter the Server/Portal Instance name.
[ ? : Help, < : Back, ! : Exit ]
Enter the Server/Portal Instance name [WebSphereServer-instance-name]:


Enter the WebSphere Install Root directory.
[ ? : Help, < : Back, ! : Exit ]
Enter the WebSphere Install Root directory [/opt/WebSphere/AppServer]: 


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]:


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: wpshost.example.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]:


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 [r2s+z4TxPsSwBLe/FbncKrwzVudy+nU5]:


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: wpsagent


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: /tmp/password.txt


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 :
/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name

Instance Server/Portal name : WebSphereServer-instance-name
WebSphere Install Root Directory : /opt/WebSphere/AppServer

Access Manager Services Host : amhost.example.com
Access Manager Services Port : 80
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /amserver
Agent Host name : wpshost.example.com
Application Server Instance Port number : 80
Protocol for Application Server instance : http
Deployment URI for the Agent Application : /agentapp
Encryption Key : r2s+z4TxPsSwBLe/FbncKrwzVudy+nU5
Agent Profile name : wpsagent
Agent Profile Password file name : /tmp/password.txt
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]:

Copy agent.jar,amclientsdk.jar to
/opt/WebSphere/AppServer/lib/ext...DONE.

Creating directory layout and configuring AMAgent.properties file for
agent_001 instance ...DONE.

Reading data from file /tmp/password.txt 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/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name/server.xml
...DONE.

Configure server.xml file
/opt/WebSphere/AppServer/config/cells/wpshost/nodes/wpshost/servers/WebSphereServer-instance-name/server.xml...DONE.


SUMMARY OF AGENT INSTALLATION
-----------------------------
Agent instance name: agent_001
Agent Configuration file location:
/opt/j2ee_agents/am_wps_agent/agent_001/config/AMAgent.properties
Agent Audit directory location:
/opt/j2ee_agents/am_wps_agent/agent_001/logs/audit
Agent Debug directory location:
/opt/j2ee_agents/am_wps_agent/agent_001/logs/debug


Install log file location:
/opt/j2ee_agents/am_wps_agent/logs/audit/install.log

Thank you for using Access Manager Policy Agent