Follow these steps to install Identity Manager on the IBM WebSphere Application Server.
Use the following procedure to prepare the application server for Identity Manager:
You should have a WebSphere application server and servlet engine installed.
Create a staging directory and name it idm_staging.
Copy the idm.war file from the base directory of the installation media to the idm_staging directory.
Unjar the idm.war file in the idm_staging directory:
jar -xvf idm.war
Set the environment variables JAVA_HOME and WSHOME. For example, in Windows do the following:
set JAVA_HOME=c:\Program Files\WebSphere\AppServer\java
set WSHOME=Path To IDMStaging Directory
Make sure the value of the WSHOME environment variable does NOT contain the following:
Quotation marks (" ")
A slash or backslash at the end of the path (/ or \)
Do not use quotation marks, even if the path to the application deployment directory contains spaces.
If you plan to use a database, you may need to copy one or more files to the idm\WEB-INF\lib directory. To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. When finished, launch setup to continue with installation.
If you launch setup before copying your database files, setup will not proceed correctly. Copy the files, and then use the lh setup command to restart the setup portion of the installation process.
If you plan to use the Identity Manager Service Provider feature and you are using the IBM 1.5 JDK (or later), set the following properties:
In the was-install/java/jre/lib directory, rename the jaxb.properties.sample to jax.properties and uncomment these two lines:
Save the file and restart the application server.
If you are installing multiple instances of Identity Manager on a single application server, change the waveset.serverId system property to a unique name for each Identity Manager instance. By default, the waveset.serverId Java system property is the name of the machine the application server is installed on. To set this property to another value, add the following command to the startup script for your application server.
You may install the software using one of two methods:
Using the installer Graphic User Interface
If you copy the files from the installation media to your own location, note that the idm.war and install.class files must be in the same directory.
The installer displays the Welcome panel.
Using the nodisplay option (UNIX only)
Change directory to the Identity Manager software location. Enter the following command to activate the installer in nodisplay mode:
The installer displays the Welcome text. The installer then presents a list of questions to gather installation information in the same order as the Graphic User Interface installer in these procedures.
If no display is present, the installer defaults to the nodisplay option. The DISPLAY environment variable must be set to a valid X server or the installation may fail.
Click Next to display the Install or Upgrade? panel.
Leave the New Installation option selected, and then click Next.
The installer displays the Select Installation Directory panel.
Replace the displayed directory location with the location where you want to install Identity Manager. This could be a staging location or a specific folder. Enter the location (or click Browse to locate it), and then click Next.
Click Next to begin installation.
After installing files, the installer displays the Launch Setup panel.
Select a database from the list provided. Depending on your selection, setup prompts for additional setup information.
Before you continue, if you plan to use a database, you may need to copy one or more files to the idm/WEB-INF/lib directory. For example, you may need to place a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix C, Database Reference. If you are planning to use a Data Source as your repository location, see the special instructions in Appendix D, Configuring Data Sources for Identity Manager.
When finished, click Launch Setup to launch the Setup Wizard and continue with setup steps. If you click Launch Setup before copying your database files, setup will not proceed correctly. If this happens, quit the installation program, and then use the lh setup command to restart the setup portion of the installation process.
Click Next on the Setup Wizard panel.
The product displays the Locate the Repository panel.
Select a database from the list of displayed options.
Depending on your selection, setup prompts for additional setup information.
See Appendix C, Database Reference, for selections and setup instructions.
The Continue Identity Manager Demo Setup? panel appears.
If this is a non-demo installation, click No, I will configure Identity Manager myself and go to Step 3: Deploy the Application.
Otherwise, if appropriate, click Yes, I would like to continue setting up a demonstration environment. This option allows you to quickly configure users and enter environment and server information.
Enter the following personal information:
This personal information is used to create the Approver user (with configurator privileges).
Enter the following Approver information:
Select the Server Type from the list.
Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.
If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
The installer displays the Import Save Configuration panel.
Click Execute to perform all the listed functions. If desired, click Hide Details.
When all functions complete, click Done in the setup panel.
If the application server is installed on a UNIX machine, change directories to the $WSHOME/bin directory and run the following command to allow the scripts in this directory to be executed.
chmod -R +x *
The following procedure uses the Integrated Solutions Console, Version 6.1. The configuration procedure may vary for other versions of the Integrated Solutions Console.
Delete the following files, if they exist:
Create a .war file from WSHOME:
jar -cvf idm.war *
Start the application server. You must use WebSphere’s script to do this. For example, if WebSphere’s binary files are installed in c:\Program Files\WebSphere\AppServer\bin and the application server is named server1:
cd c:\Program Files\WebSphere\AppServer\bin startServer.bat server1
Start the WebSphere Integrated Solutions Console, and then select Applications—>Install New Application.
The Preparing for the application installation panel displays.
Select the Generate Default Bindings option. (Use the default selections for Override and Virtual Host.) Click Next.
Accept the was.policy file that is displayed under the heading Application Security Warnings. Scroll down to the bottom of this file and click the Continue button.
Configure the Step 1: Select installation options page as needed.
If you want to install the application to a different location than WebSphere’s default location, enter the path to install the application in the Directory to Install Application field. For example:
Make sure the Distribute Application and Use Binary Configuration options are selected.
Make sure that the Create Mbeans for Resources and Deploy Enterprise Beans options are not selected.
Enter the name of the application in the Application Name field (the default is idm).
If desired, select the Enable class reloading option.
Click Next after configuring this dialog.
Make sure the Step 2: Map modules to servers panel displays a line for the current release of Identity Manager and that it maps to the appropriate server. Click Step 6: Map virtual hosts for Web modules.
Make sure the Step 6: Map virtual hosts for Web modules panel displays a line for the current release of Identity Manager and that it maps to the appropriate virtual host, and then click Step 8: Summary.
Review the summary of options, then click Finish.
After Identity Manager has been installed, click Save to Master Configuration to save the configuration.
Click Save, and then wait for the page to clear.
Stop the Identity Manager application.
Add the following line to your WAS_ROOT/profiles/ProfileName/installedApps/nodename/EnterpriseAppName/idm.war/WEB-INF/ibm-web-ext.xmi file
<jspAttributes xmi:id="JSPAttribute_1" name="jdkSourceLevel" value="15"/>
This line causes the application server to compile JSPTM files in Java 5.
Restart Identity Manager.
If your IT environment has Windows Active Directory, Novell NetWare, Domino, Remedy, or RSA ACE/Server resources, you should install the Identity Manager Gateway.
If your IT environment has Windows Active Directory domains, you should also install PasswordSync. The Identity Manager PasswordSync feature keeps user password changes made on Windows Active Directory domains synchronized with other resources defined in Identity Manager.
See Part III, Installing Optional Components for installation information.