After you install and configure the User Application, take care of the post-installation tasks.
Immediately after installation, copy the encrypted master key and record it in a safe place.
Open the master-key.txt file in the installation directory.
Copy the encrypted master key to a safe place that is accessible in event of system failure.
WARNING:Always keep a copy of the encrypted master key. You need the encrypted master key to regain access to encrypted data if the master key is lost, for example because of equipment failure.
If this installation is on the first member of a cluster, use this encrypted master key when installing the User Application on other members of the cluster.
For more information on the master key, see the Identity Manager User Application: Administration Guide sections on Encryption of Sensitive User Application Data and Clustering JBoss.
Check your cluster installations. Ensure that each JBoss server in a JBoss cluster has
A unique partition name (partition name)
A unique partition UDP (partition.udpGroup)
A unique Workflow Engine ID
The same (identical) WAR file. The WAR is written by the installation to the jboss\server\IDM\deploy directory by default.
Ensure that each server in a WebSphere cluster has a unique Workflow Engine ID.
For more information, see the section on Clustering in Chapter 4 of the Identity Manager User Application: Administration Guide
If you select in the User Application configuration file during installation, you must configure SSL communication between the JBoss servers on which you are deploying the User Application WAR and the IDMPwdMgt.war file. Refer to your JBoss documentation for directions.
If you have an external password WAR and want to test the Forgot Password functionality by accessing it, you can access it:
Directly, in a browser. Go to the Forgot Password page in the external password WAR, for example http://localhost:8080/ExternalPwd/jsps/pwdmgt/ForgotPassword.jsf.
Or, at the User Application login page, click the link.
You can change the values of and after installation. Use either the configupdate utility or the User Application.
To use the configupdate utility. At a command line, change directories to the install directory and enter configupdate.sh (Linux or Solaris) or configupdate.bat (Windows). If you are creating or editing an external password management WAR, you must then manually rename that WAR before you copy it to the remote JBoss server.
To use the User Application. Log in as the User Application Administrator and go to . Modify these fields:
(for example: http://localhost:8080/ExternalPwd/jsps/pwdmgt/ForgotPassword.jsf)
(for example: https://idmhost:sslport/idm)
To implement Forgot Password and Workflow e-mail notification capabilities:
In iManager, under Roles and Tasks, select Workflow Administration, then select Email Server Options.
Specify your SMTP server name under Host Name.
Next to From, specify an e-mail address (for example, noreply@novell.com), then click OK.
Start your database. Refer to your database documentation for directions.
Start the User Application server (JBoss). At the command line, make the installation directory your working directory and execute the following script (provided by the User Application installation):
start-jboss.sh (Linux and Solaris)
start-jboss.bat (Windows)
If you need to stop the application server, use stop-jboss.sh or stop-jboss.bat, or close the window in which start-jboss.sh or start-jboss.bat is running.
Start the User Application driver. This enables communication to the User Application driver.
Log into iManager.
In the Roles and Tasks display in the left navigation frame, select under .
In the content view that appears, specify the driver set that contains the User Application driver, then click . A graphic appears, showing the driver set with its associated drivers.
Click the red and white icon on the driver.
Select . The driver status changes to the yin-yang symbol, indicating that the driver is now started.
The driver, upon starting, attempts a “handshake” with the User Application. If your application server isn’t running or if the WAR wasn’t successfully deployed, the driver returns an error.
To launch and log in to the User Application, use your Web browser to go to
http://hostname:port/ApplicationName
Where hostname:port is the application server hostname (for example, myserver.domain.com) and the port is your application server’s port (for example, 8080 by default on JBoss). ApplicationName is IDM by default. You specified the application name during the install when you provided application server configuration information.
The Novell Identity Manager User Application landing page should appear.
In the upper right corner of that page, click to log in to the User Application.
If the Identity Manager User Application page does not appear in your browser after completing these steps, check the terminal console for error messages and refer to Section 5.12, Troubleshooting.
Set up your Provisioning Team and Provisioning Team Requests to enable workflow tasks. For directions, see the Identity Manager 3.5.1 User Application: Administration Guide.
For improved performance of the IDM User Application, the eDirectory Administrator must create indexes for the manager, ismanager and srvprvUUID attributes. Without indexes on these attributes, User Application users can experience impeded performance of the User Application, particularly in a clustered environment. Refer to the Novell eDirectory Administration Guidehttp://www.novell.com/documentation for directions on using Index Manager to create indexes.