29.1 Performing a Guided Installation from the Command Line

To install the User Application with the command line:

1. Log on as a root user to the computer where you want to install the User Application.

2. (Conditional) If you are installing the User Application on JBoss 5.1.2 Enterprise Application Platform (EAP), copy the jbosssx.jar file from the %jboss-root%/lib directory to the %jboss-root%/common/lib directory. Complete the installation steps in this section, and then continue to Deploying the User Application on JBoss 5.1.2 EAP.

3. Open a terminal session.

4. To launch the installation program for your platform with Java, enter the following command:

   java -jar IdmUserApp.jar -i console

5. Follow the same steps described for the graphical user interface under Section 28.1.3, Installing the User Application on a JBoss Server, reading the prompts at the command line and entering responses at the command line, through the steps on importing or creating the master key.

6. Specify the language that you want to use for installation.

7. Accept the License Agreement.

8. Specify the platform for your application server.

9. Specify the folder where you want to place the installation files.

10. Specify the platform of the User Application database. For example, Oracle.

11. Specify the hostname or IP address of the server hosting the User Application database.

    For a cluster, you must specify the same name or IP address for each member of the cluster.

12. Specify the number of the listener port for the database.

    For a cluster, you must specify the same port for each member of the cluster.

13. For the Database Username and Password, specify the name of the database according to the database platform. By default, the database name is idmuserappdb.

    • For a DB2, PostgreSQL, My SQL, or SQL Server database, specify the name.

    • For an Oracle or DB2 database, specify the Security Identifier (SID) that you created with the database instance.

    • For a cluster, you must specify the same database name or SID for each member in the cluster.

14. Specify the name for the database user account to use with the User Application and the password associated with the user account.

    In a cluster environment, you must use the same user account and password for each member in the cluster.

15. Specify the JAR file for the database platform.

    The database vendor provides the driver JAR file, which represents the Thin Client JAR for the database server. For example, for PostgreSQL, specify postgresql-8.4-701.jdbc4.jar, by default in the novell\idm\Postgres folder. NetIQ does not support driver JAR files from third-party vendors.

    For a DB2 database, you must specify two JAR files. For more information, see Section 26.1.1, Providing the Database Driver JARs.

16. (Optional) For the Database Administrator window, specify the name and password for the database administrator.

    This field automatically lists the same user account and password that you specified in Step 14. To use that account, do not make any changes.

17. Specify how you want to create the database tables:

    Create Tables Now

    The installation program creates the database tables as part of the installation process.

    Create Tables at Application Startup

    The installation program leaves instructions to create the tables when the User Application starts for the first time.

    Write SQL to File

    Create a schema file at installation time for the database administrator to use later to create the tables. When selecting this option, you must also specify a name for the file in the Schema Output File window.

18. (Conditional) If you chose Create Tables Now or Write SQL to File in Step 17, specify whether the database is a new or empty database or it already exists from a previous installation.

19. (Optional) Verify that the User Application can connect to the specified database.

    This step enables the installer to connect to the database for creating tables directly or for creating the .sql file.

    NOTE:You can continue with installation if the database connection fails. However, after installation, you must manually create the tables and connect to the database. For more information, see “Recreating the Database after Installation” in the User Application Administration Guide.

20. For Java Install, specify the path to the JRE file used to launch the installation program.

21. For the JBoss Configuration, specify the path to the installation files for the JBoss server.

22. (Conditional) If you install on a JBoss application server, for the IDM Configuration, specify the server’s configuration :

    default

    Specifies that this installation is on a single node that is not part of a cluster.

    If you select this option and decide later than you need a cluster, you must reinstall the User Application.

    all

    Specifies that this installation is on a node within a cluster.

23. For Application Context, specify a name that represents the application server configuration, the application WAR file, and the name in the URL context.

    The installation script creates a server configuration, then names the configuration according to the name that you created when installing the application server. For example, IDMProv.

    IMPORTANT: NetIQ recommends that you make a note of the specified Application Context. You will use this application name in the URL when you start the User Application from a browser.

24. (Conditional) When installing the provisioning WAR file on a node in a JBoss cluster, you must also specify the Workflow Engine ID. The engine ID cannot exceed 32 characters. For more information about workflow engine IDs, see the section on configuring workflows for clustering in the User Application: Administration Guide.

25. (Optional) To send log events to an auditing server, complete the following steps in the Select Audit Logging Type window:

    1. Specify that you want to send log events to an auditing server.

    2. Specify the type(s) of logging that you want to enable:

       Novell Identity Audit or NetIQ Sentinel

       Enables logging through a Novell or NetIQ client for the User Application.

       OpenXDAS

       Enables the User Application to send events to your OpenXDAS logging server.

    3. (Conditional) If you chose in Step 25.b to send log events through a Novell or NetIQ client, specify the hostname or IP address for the client server and the path to the log cache.

       For more information about setting up logging, see the User Application Administration Guide.

26. To set the User Application configuration parameters, complete the following steps:

    1. Manually launch the configuration update utility from the command line: configupdate.sh (Linux) or configupdate.bat (Windows).

    2. Specify the values as described in Section 30.2, Configuring the User Application.

27. (Optional) If you are using an external password management WAR, manually copy the WAR to the installation directory and to the remote JBoss server deploy directory that runs the external password WAR functionality.

28. (Conditional) If you are installing the User Application on JBoss 5.1.2 Enterprise Application Platform (EAP), continue to Deploying the User Application on JBoss 5.1.2 EAP.

29. Continue with the post-installation tasks described in Section 30.0, Completing the Roles Based Provisioning Module / User Application Installation.