Novell Doc: Identity Manager Roles Based Provisioning Module 3.6.1 User Application: Installation Guide - Installing and Configuring the User Application WAR

4.1 Installing and Configuring the User Application WAR

NOTE:The installation program requires the Java 2 Platform Standard Edition Development Kit version 1.5. If you use an earlier or later version, the installation procedure does not successfully configure the User Application WAR file. The installation appears to succeed, but you encounter errors when trying to start the User Application.

Launch the installer for your platform from the command line.

Be sure to use the version of the Sun JDK to start the User Application installer as follows:

Linux/Solaris
```
$ /opt/jdk1.5.0_10/bin/java -jar IdmUserApp.jar
```
Windows
```
C:\Novell\InstallFiles\> "C:\Program Files\Java\jdk1.5.0_10\bin\java.exe" -jar IdmUserApp.jar
```
When the installation procedure asks for the full path of your Java installation, provide the root path of the Sun JDK. For example, the root path on Linux could be /opt/jkd1.5.0_10.

NOTE:SLES users: Do not use the IBM^* JDK that comes with SLES. This version is incompatible with some aspects of the installation and can cause master key corruption errors.

When the installation program launches, you are prompted for the language.

Use the following information along with the instructions on each installation panel to complete the installation:

Installation Screen	Description
Novell Identity Manager	Select the language for the Installation program. The default is English.
License Agreement	Read the License Agreement, then select I accept the terms of the License Agreement.
Application Server Platform	Select JBoss.
Standard or Provisioning	Standard: Select this option if you are installing the User Application Standard Edition. Roles Based Provisioning: Select this option if you are installing the Roles Based Provisioning Module.
Data Migration	Accept the default (verify that Yes is not selected). WARNING:Do not select Yes, If Yes is selected, you will encounter problems starting the User Application. For information on migrating, see the User Application: Migration Guide.
Where is the WAR?	If the Identity Manager User Application WAR file is in a different directory from the installer, the installer prompts for the path to the WAR.
Choose Install Folder	Specify where you want the installer to put the files.
Database Platform	Select the database platform. The database and JDBC driver must already be installed. Options include: MySQL Oracle (you are prompted for the Oracle version) MS SQL Server
Database Host and Port	Host: Specify the database server’s hostname or IP address. For a cluster, specify the same hostname or IP address for each member of the cluster. Port: Specify the database’s listener port number. For a cluster, specify the same port for each member of the cluster.
Database Name and Privileged User	Database name (or sid): For MySQL or MS SQL Server, provide the name of your preconfigured database. For Oracle, provide the Oracle System Identifier (SID) that you previously created. For a cluster, specify the same database name or SID for each member of the cluster. Database user: Specify the database user. For a cluster, specify the same database user for each member of the cluster. Database password/Confirm password: Specify the database password. For a cluster, specify the same database password for each member of the cluster.
Java Install	Specify the Java root install folder.

You are prompted for information about where your JBoss application server is installed.

Use the following information to complete this panel and to continue with the installation.

Installation Screen	Description
JBoss Configuration	Tells the User Application where to find the JBoss Application Server. This installation procedure does not install the JBoss Application Server. For directions on installing the JBoss Application Server, see Installing the JBoss Application Server and the MySQL Database. Base folder: Specify the location of the application server. Host: Specify the application server’s hostname or IP address. Port: Specify the application server’s listener port number. The JBoss default port is 8080.
IDM Configuration	Select the type of application server configuration: Select all if this installation is part of a cluster Select default if this installation is on a single node that is not part of a cluster If you select default and decide you need a cluster later, then you must reinstall the User Application. Application name: The name of the application server configuration, the name of the application WAR file, and the name of the URL context. The installation script creates a server configuration and by default names the configuration based on Application name. Make a note of the application name and include it in the URL when you start the User Application from a browser. Workflow Engine ID: Each server in a cluster must have a unique Workflow Engine ID. Workflow Engine IDs are described in the User Application: Administration Guide in Section 3.5.4, “Configuring Workflows for Clustering”.
Audit Logging	To enable logging, click Yes. The next panel prompts you to specify the type of logging. Choose from the following options: Novell Audit: Enables Novell® Audit Logging for the User Application. OpenXDAS: Events are logged to your OpenXDAS logging server. For more information on setting up Novell Audit or OpenXDAS logging, see the User Application: Administration Guide.
Novell Audit	Server: If you enable Novell Audit logging, specify the hostname or IP address for the Novell Audit server. If you turn logging off, this value is ignored. Log Cache Folder: Specify the directory for the logging cache.
Security - Master Key	Yes: Allows you to Import an existing master key. If you choose to import an existing encrypted master key, cut and paste the key into the install procedure window. No: Creates a new master key. After you finish the installation, you must manually record the master key as described in Section 8.1, Recording the Master Key. The installation procedure writes the encrypted master key to the master-key.txt file in the installation directory. Reasons to import an existing master key include: You are moving your installation from a staging system to a production system and want to keep access to the database you used with the staging system. You installed the User Application on the first member of a JBoss cluster and are now installing on subsequent members of the cluster (they require the same master key). Because of a failed disk, you need to restore your User Application. You must reinstall the User Application and specify the same encrypted master key that the previous installation used. This gives you access to the previously stored encrypted data.

You are prompted for the information that the installation program uses to configure the User Application WAR file. (If you are not prompted for this information, you might not have completed the steps outlined in Section 2.5, Installing the Java Development Kit.

Use the following information to complete the panel and continue with the installation.

Installation Screen	Description
User Application Configuration	The User Application install enables you to set User Application configuration parameters. Most of these parameters are also editable with configupdate.sh or configupdate.bat after installation; exceptions are noted in the parameter descriptions. For a cluster, specify identical User Application configuration parameters for each member of the cluster. See Section A.0, IDM User Application Configuration Reference for a description of each option.
Pre-Installation Summary	Read the Pre-Installation Summary page to verify your choices for the installation parameters. If necessary, use Back to return to earlier installation pages to change installation parameters. The User Application configuration page does not save values, so after you re-specify earlier pages in the installation, you must re-enter the User Application configuration values. When you are satisfied with your installation and configuration parameters, return to the Pre-Install Summary page and click Install.
Install Complete	Indicates that the installation is finished.

Installation Screen

Description

User Application Configuration

The User Application install enables you to set User Application configuration parameters. Most of these parameters are also editable with configupdate.sh or configupdate.bat after installation; exceptions are noted in the parameter descriptions.

For a cluster, specify identical User Application configuration parameters for each member of the cluster.

See Section A.0, IDM User Application Configuration Reference for a description of each option.

Pre-Installation Summary

Read the Pre-Installation Summary page to verify your choices for the installation parameters.

If necessary, use Back to return to earlier installation pages to change installation parameters.

The User Application configuration page does not save values, so after you re-specify earlier pages in the installation, you must re-enter the User Application configuration values. When you are satisfied with your installation and configuration parameters, return to the Pre-Install Summary page and click Install.

Install Complete

Indicates that the installation is finished.

4.1.1 Viewing Installation and Log Files

If your installation completed without error, continue with Testing the Installation. If the installation issued errors or warnings, review the log files to determine the problems:

Identity_Manager_User_Application_InstallLog.log holds results of the basic installation tasks.
Novell-Custom-Install.log holds information about the User Application configuration done during installation.