Sample Installation for the Agent for JBoss Application Server 4.0

Example 3–5 shows a sample installation run of the agent for JBoss Application Server 4.0.

This sample run represents a JBoss Application Server 4.0 installation running with Java security manager permissions. For more information, see Installing the Agent on a JBoss Application Server 4.0 Instance Running with Java Security Manager Permissions.

Example 3–5 Sample Installation for the Agent for JBoss Application Server 4.0

************************************************************************
Welcome to the Access Manager Policy Agent for JBoss Server 4.0. If the
Policy Agent is used with Federation Manager services, User needs to enter
information relevant to Federation Manager.
************************************************************************
Enter the complete path to the directory which is used by JBoss Server to
store its configuration Files. This directory uniquely identifies the JBoss
Server instance that is secured by this Agent.
[ ? : Help, ! : Exit ]
Enter the JBoss Server Config Directory Path
[/opt/jboss-4.0.2/server/default/conf]:

Enter the fully qualified host name of the server where Access Manager
Services are installed.
[ ? : Help, < : Back, ! : Exit ]
Access Manager Services Host: am.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: agent.example.com

Indicate the specified server instance runs with Java security manager
permissions.
[ ? : Help, < : Back, ! : Exit ]
Specify whether the chosen server instance runs with Java security manager
permissions. [false]: true

Enter the complete path including the file name of Java security manager
permissions used for the chosen JBoss server instance.
[ ? : Help, < : Back, ! : Exit ]
Enter the complete path including the file name of Java security manager
permissions used for the chosen JBoss server instance.
[/opt/jboss-4.0.2/server/default/conf/server.policy]:

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 [1Ae4alVx7M9YnVcQKI5OqCXsnGyPaKAP]:

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

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/ldp
-----------------------------------------------
SUMMARY OF YOUR RESPONSES
-----------------------------------------------
JBoss Server Config Directory : /opt/jboss-4.0.2/server/default/conf
Access Manager Services Host : am.example.com
Access Manager Services Port : 8880
Access Manager Services Protocol : http
Access Manager Services Deployment URI : /amserver
Agent Host name : agent.example.com
Agent permissions gets added to java permissions policy file : true
File name of Java security manager permissions used for the chosen JBoss
server instance. :
/opt/jboss-4.0.2/server/default/conf/server.policy
Application Server Instance Port number : 8080
Protocol for Application Server instance : http
Deployment URI for the Agent Application : /agentapp
Encryption Key : 1Ae4alVx7M9YnVcQKI5OqCXsnGyPaKAP
Agent Profile name : jee
Agent Profile Password file name : /opt/ldp
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]:

Creating directory layout and configuring AMAgent.properties file 
for agent_001 instance ...DONE.
Reading data from file /opt/ldp 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/jboss-4.0.2/server/default/conf/jboss-service.xml ...DONE.
Adding Agent parameters to
/opt/jboss-4.0.2/server/default/conf/jboss-service.xml file ...DONE.
Creating a backup for file
/opt/jboss-4.0.2/server/default/conf/server.policy ...DONE.
Adding Agent parameters to
/opt/jboss-4.0.2/server/default/conf/server.policy file ...DONE.
Adding Agent parameters to am-login-config.xml file ...DONE.
Adding Agent parameters to
/opt/jboss-4.0.2/bin/setAgentClasspathdefault.sh file ...DONE.
Adding Agent parameters to agentapp.war file ...DONE.

SUMMARY OF AGENT INSTALLATION
-----------------------------
Agent instance name: agent_001
Agent Configuration file location:
/opt/j2ee_agents/am_jboss_agent/agent_001/config/AMAgent.properties
Agent Audit directory location:
/opt/j2ee_agents/am_jboss_agent/agent_001/logs/audit
Agent Debug directory location:
/opt/j2ee_agents/am_jboss_agent/agent_001/logs/debug
Install log file location:
/opt/j2ee_agents/am_jboss_agent/logs/audit/install.log
Thank you for using Access Manager Policy Agent

Installing a J2EE Agent on Multiple JBoss Application Server 4.0 Instances

After you install the agent for a specific JBoss server instance, you can install the agent on another JBoss server instance on the same host server by executing the agentadmin --install command again.

However, the JBoss server agent and the Access Manager server must run on different web containers?

Installing the Agent on a JBoss Application Server 4.0 Instance Running with Java Security Manager Permissions

If you are installing the agent on an instance of JBoss Application Server 4.0 that runs with Java security manager permissions, during the installation process, answer true to the following prompt as shown:

Indicate the specified server instance runs with Java security manager
permissions.
[ ? : Help, < : Back, ! : Exit ]
Specify whether the chosen server instance runs with Java security manager
permissions. [false]: true

Answering true to the preceding prompt, causes the following prompt to appear:

Enter the complete path including the file name of Java security manager
permissions used for the chosen JBoss server instance.
[ ? : Help, < : Back, ! : Exit ]
Enter the complete path including the file name of Java security manager
permissions used for the chosen JBoss server instance.
[/opt/jboss-4.0.2/server/default/conf/server.policy]:

Enter the appropriate path information.