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:
Run the install.bat (for Windows) or install (for UNIX) command to launch the installation process.
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)
On UNIX systems, 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. The installer displays 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.
If the directory you enter does not exist, the installer prompts for confirmation, and then creates the directory.
The WebLogic Web application home directory is ServerHome/user_projects/domains/DomainName/autodeploy
Click Next to begin installation.
After installing the files, the installer displays the Launch Setup panel.
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 into idm/WEB-INF/lib 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. 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 installer displays the Locate the Repository panel.
Select a database from the list provided. 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.
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 *
Remove the Cryptix JAR files (cryptix-jce-api.jar and cryptix-jce-provider.jar) from the $WSHOME/WEB-INF/lib directory (UNIX), or the %WSHOME%\WEB-INF\lib directory (Windows).
The Cryptix JAR files are no longer included and no longer supported. You need to remove them if you haven’t already. If you have customized your Waveset.properties file, please make sure that security.jce.workaround property is set to false or removed. An exception will be thrown if this property is set to true because the intention of this property will not be fulfilled.