The agent needs to be installed on the same machine as your WebSphere server, and your WebSphere server needs to be installed on machine that does not contain any Access Manager components.
You need to know the following about your WebSphere installation:
Base directory of the application server.
Name of the administrator.
Password of the administrator.
The WebSphere server must be enabled for global security and disabled for Java 2 security.
To verify, check your global security options in the WebSphere console. When you enable global security, Java 2 security is enabled by default.
IMPORTANT:If you have not enabled global security before installing the agent, the installation program enables it for you.
To install the agent on a Linux WebSphere server:
Verify that the machine meets the minimum requirements. See Section 1.1.2, WebSphere Agent Requirements.
Make sure that the WebSphere server is running.
Download the agent from Novell.
Untar the file.
Change to the Access Manager directory.
At the command prompt of the Access Manager directory, enter the following:
./install.sh
Press Enter to review and accept the License Agreement.
Enter the IP address of the Administration Console machine.
Enter the username of the administrator user you created for the Administration Console.
Enter and re-enter the password for this administrator.
Enter the base directory for the WebSphere server.
The default directory is /opt/IBM/WebSphere/AppServer.
Enter the name for the WebSphere administrator.
Enter and re-enter the password for the WebSphere administrator.
When the installation completes, restart the WebSphere server.
The agent is not imported into the Administration Console until the WebSphere server is restarted.
(Optional) To verify the installation of the agent, log in to Administration Console, then click > .
If the installation was successful, the IP address of your agent appears in the list. The import into Administration Console can take a few minutes, so if your agent does not appear in the list, wait a few minutes, then refresh the screen.
If an agent starts to import into the Administration Console but fails to complete the process, the following message appears:
Server agent-<name> is currently importing. If it has been several minutes after installation, click repair import to fix it.
If you have waited at least ten minutes, but the message doesn’t disappear and the agent doesn’t appear in the list, click the link. If the agent isn’t in the list and you don’t receive a repair import message, verify that you have restarted the J2EE server after installing the agent. The J2EE server must be running for the import process to begin. For additional help, see Section 8.1, Troubleshooting the J2EE Agent Import.
The agent must be configured before it can be used for access control. See Section 2.0, Configuring the Agent for Authentication.
To install the agent on a Windows WebSphere server:
Verify that the machine meets the minimum requirements. See Section 1.1.2, WebSphere Agent Requirements.
Make sure that the WebSphere server is running.
Download the agent from Novell.
Execute the file.
Read the welcome information, then click .
Note where additional Access Manager information can be found, then click .
Review the License Agreement, accept it, then click .
Select the installation directory for the Server Communications module, then click .
Select , then click .
Enter the information required for modifying the WebSphere server:
WAS Administrator ID: Specify the name of the WebSphere administrator.
WAS Administrator Password: Specify the password of the WebSphere administrator. Confirm the password by re-entering it.
Enter the information required for server communication between the agent and the Administration Console. Fill in the following fields and carefully review your information:
Administration Console Admin Username: Specify the username of the admin user of the Administration Console.
Administration Console Admin Password: Specify the password for the admin user of the Administration Console. Confirm the password by re-entering it.
Administration Console IP Address: Specify the IP address of your Administration Console.
IP Address of the Application Server: Review the entered address. If your server is configured for more than one IP address, make sure the one you want to use is specified in this box.
Click , then review the installation summary.
To install the agent, click .
When the installation has finished, click .
(Optional) If your WebSpehere server is running a non-English version of the software, follow the steps in Section 1.3.4, Additional Steps for Servers Running the Non-English Version, before you proceed with Step 16.
Determine when you want to restart WebSphere:
To restart it immediately, select , then click .
To select another time to restart WebSphere, click . The agent does not import into the Administration Console until WebSphere is restarted.
(Optional) To verify the installation of the agent, log in to Administration Console, then click > .
If the installation was successful, the IP address of your agent appears in the list. The import into Administration Console can take a few minutes, so if your agent does not appear in the list, wait a few minutes, then refresh the screen.
If an agent starts to import into the Administration Console but fails to complete the process, the following message appears:
Server agent-<name> is currently importing. If it has been several minutes after installation, click repair import to fix it.
If you have waited at least ten minutes, but the message doesn’t disappear and the agent doesn’t appear in the list, click the link. If the agent isn’t in the list and you don’t receive a repair import message, verify that you have restarted the J2EE server after installing the agent. The J2EE server must be running for the import process to begin. For additional help, see Section 8.1, Troubleshooting the J2EE Agent Import.
The agent must be configured before its health status turns green. See Section 2.0, Configuring the Agent for Authentication.
If your WebSpehere runs a non-English language version:
If WebSpehere server is not running, start it.
Change to the directroy where J2EE Agents for WebSpehere is installed.
Run the following command:
$> <Path-to-websphere-directory>\bin\wsadmin.bat -username <admin username> -password <admin password> -lang jython -f websphere_set_jcc_dir.jy c:\Novell\devman\jcc
Replace, <Path-to-websphere-directory> with the directory path where IBM WebSpehere is installed, <admin username> with the user name of the WebSphere server administrator, <admin password> with the password of the WebSphere administrator.
Restart the WebSpehere server.