32.8 Starting the Identity Applications

This section provides instructions for starting the identity applications and logging in the first time on an application server. In a cluster environment, start the procedure on the primary node. The identity applications should be installed and ready for deployment. For more information about post-installation tasks, see Section 34.0, Completing the Installation of the Identity Applications.

32.8.1 Starting the User Application on a JBoss or Tomcat Server

This section requires a startup script for your application server.

  • Linux - JBoss: etc/init.d/jboss_init start

  • Linux - Tomcat: etc/init.d/idmapps_tomcat_init start

  • Windows - JBoss: start-jboss.bat

    Windows - Tomcat: start-IDM Apps Tomcat Service

If your browser does not display the User Application page after you complete these steps, check the terminal console for error messages and refer to Section 56.0, Troubleshooting.

To start the identity applications:

  1. Start the database for the identity applications. For more information, see your database documentation.

  2. For the User Application to run reports, add the Djava.awt.headless=true flag to the startup script for the application server. For example:

    JAVA_OPTS="-Djava.awt.headless=true -Dfile.encoding=UTF-8 -Dsun.jnu.encoding=UTF-8 -server -Xms1024m -Xmx1024m -XX:MaxPermSize=512m

    NOTE:You do not need to perform this step if you are running on an X11 Windows system.

  3. Start the application server where you installed the identity applications.

    NOTE:In a cluster, start the primary node only.

  4. At the command line, make the installation directory your working directory.

  5. Execute the startup script.

  6. To enable communication with the User Application driver, complete the following steps:

    1. Log in to iManager.

    2. Under Roles and Tasks > Identity Manager in the left navigation frame, click Identity Manager Overview.

    3. In the content view, specify the driver set that contains the User Application driver, then click Search.

    4. In the graphic showing the driver set with its associated drivers, click the red-and-white icon for the User Application driver.

    5. Click Start Driver.

      Upon start, the driver attempts a “handshake” with the User Application. If your application server is not running or if the WAR was not deployed successfully, the driver returns an error. Otherwise, the driver status changes to the yin-yang symbol, indicating that the driver is now started.

  7. To start the Role and Resource Service driver, repeat the procedure in Step 6.

  8. To launch and log in to the User Application, enter the following URL in your web browser: 

    http://hostname:port/ApplicationName
    hostname

    Represents the name of the application server. For example, myserver.domain.com

    port

    Represents the port number of the application server. For example, 8180.

    ApplicationName

    Represents the name that you specified during the installation for the application when you provided application server configuration information. For example, IDMProv.

  9. In the upper right corner of the User Application landing page, click Login.

  10. (Conditional) To enable the User Application in a cluster group, complete the following steps:

    1. Click Administration.

    2. In the Application Configuration portal, click Caching.

    3. In the Caching Management window, select True for Cluster Enabled.

    4. Click Save.

    5. Restart the server.

    6. (Conditional) To use local settings, repeat this procedure for each server in the cluster.

32.8.2 Starting the User Application on the WebSphere Server

  1. Log in to the WebSphere application server that hosts the identity applications.

  2. Using the standard WebSphere deployment procedure, deploy the User Application WAR file.

  3. Log in to the WebSphere administrator’s console as an admin user.

  4. In the left navigation pane, expand Applications > Enterprise Applications.

  5. Select the check box beside the User Application context that you want to start, and then click Start.

  6. Log out of the console.

  7. To access the User Application portal, enter the following URL in a supported web browser:

    http://application-server-host:port/application-context

    For example:

    http://localhost:9080/IDMProv

NOTE:In a cluster environment, the User Application displays error messages if the active node goes down while creating or modifying roles or resources. This is a limitation with the User Application. NetIQ recommends you to use Catalog Administrator to create or modify roles or resources.

To workaround this issue, refresh the browser window and the operations should work fine. Otherwise, close the browser window and retry the operations.