Migrating Database From MySQL to PostgreSQL

1. Stop JBoss.

   Linux: Run the /etc/init.d/jboss_init stop command.

   Windows: Navigate to C:\Novell\idm and run the stop-jboss.bat command.

2. Stop the MySQL database.

   Linux: Run the /etc/init.d/mysql stop command.

   Windows: Manually stop the MySQL service.

3. Rename your User Application installation directory by completing the following steps:

   1. Navigate to the installation directory.

      For example, if you installed the User Application in the default installation directory, enter one of the following commands:

      Linux: cd /opt/novell

      Windows: cd C:\Novell\idm

   2. Rename the installation directory.

      Linux: Run the following command:

      mv <User Application installation directory> <idm_mysql>

      For example, if you installed the User Application in idm directory, enter the following command:

      mv <idm> <idm_mysql>

      Windows: On Windows, perform the following actions:

      1. (Optional) Terminate the Identity Manager Java process from the Windows Task Manager.

         NOTE:Sometime the directory is not renamed if the Java process is still running. You are recommended to terminate this process before attempting to rename the directory.

      2. Rename the directory manually.

      NOTE:Do not modify the content of the User Application installation directory as you may need to use this directory as a backup of the current configuration during the subsequent steps.

   This step is needed to reinstall JBoss on the default path of the originally installed User Application without overwriting the contents of this directory.

4. (Conditional) On Linux, take a backup of JBoss if you have customized it.

   cp /etc/init.d/jboss_init /opt/novell/jboss_init_backup

5. Reinstall JBoss with PostgreSQL database.

   1. Navigate to the directory containing the JBossPostgreSQL.bin or JBossPostgreSQL.exe file and execute one of the following commands:

      Linux: ./ JBossPostgreSQL.bin

      Windows: JBossPostgreSQL.exe

      For example, cd/dvd_media_path/products/RBPM/ or dvd_media_path\products\RBPM\.

   2. Accept the License Agreement, and then click Next.

   3. To complete the guided process, specify values for the following parameters:

      • To install both JBoss and PostgreSQL, leave the Install set setting as default.

      • For the following parameters, enter the values that were specified during MySQL installation:

        • JBoss parent folder

          Specifies the directory where you want to install the JBoss files.

        • Database name

          Specifies the name of the database. The default value is idmuserappdb.

        • Database admin

          Specifies the idmadmin account, which is a database administrator that can create database tables, views, and other artifacts.

        • Password for admin user

          Specifies the password for the database administrator and the default postgres user.

          This installation program does not support passwords that include a " or $ character.

6. Review the pre-installation summary.

7. Start the installation process.

8. When the installation process completes, click Done.

To install the User Application with the installation wizard:

1. Install the User Application.

   1. Navigate to the directory containing the User Application installation files and run one of the following commands:

      Linux: /opt/novell/idm/jre/bin/java -jar IdmUserApp.jar

      For example, cd /dvd_media_path/products/RBPM/user_app_install

      Windows: C:\Novell\idm\jre\bin\java.exe -jar IdmUserApp.jar

      For example, dvd_media_path\products\RBPM\user_app_install\

      NOTE:When you run the installation program from the installation directory, it does not prompt you to specify the location of the WAR files as you progress through the installation.

   2. Accept the License Agreement, and then click Next.

   3. Complete the installation process by entering the values for the given parameters.

      • Leave the default setting as JBoss in the Application Server Platform page.

      • In the Install Folder window, specify the folder where you want to place the installation files.

      • In the Database Platform page, specify PostgreSQL as the platform of the User Application database.

      • In the Database Host and Port page, specify the hostname or IP address of the server hosting the User Application database.

      • For Port, 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.

      • In the Database Username and Password page, idmuserappdb is automatically populated as the database name.

        If you used a different name for the database when User Application was installed with MySQL, specify the same name in this page.

        • 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.

        • Specify the JAR file for the database platform. Browse to and choose the database driver JAR file as /opt/novell/idm/Postgres/postgresql-8.4-701.jdbc4.jar or C:\Novell\idm\Postgres\postgresql-8.4-701.jdbc4.jar.

          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 or C:\Novell\idm\Postgres directory. NetIQ does not support driver JAR files from third-party vendors.

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

        NOTE:The version of the database driver jar file might differ if you are not using the convenience installer. NetIQ recommends that you use the updated jar file to ensure continued functionality.

      • (Optional) In the Database Administrator page, specify the name and password for the database administrator.

        This field automatically lists the same user account and password that you specified in the Database Username and Password page. To use that account, do not make any changes.

      • To create the database tables as part of the installation process, select Create Tables Now in the Create Database Tables page.

      • Specify New Database in the New or Existing Database page.

        This will create the schema that you require to perform the migration.

      • To verify that the User Application can connect to the specified database, click Test Database Connection.

        NOTE:This step enables the installer to connect to the database for creating tables directly. You can continue installation if the database connection fails. However, after installation, you must manually create the tables and connect to the database.

      • In the Java Install page, specify the path to the JRE file used to launch the installation program.

      • In the JBoss Configuration page, specify the path to the installation files for JBoss.

      • In the IDM Configuration page, specify the settings for configuring JBoss as default or all.

        • 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 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.

      • 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 while installing JBoss. For example, IDMProv.

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

      • (Optional) When installing the provisioning WAR file on a node in a 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.

      • (Optional) To send log events to an auditing server, specify the type(s) of logging that you want to enable and where you want to send the log events for auditing.

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

      • In the Security - Master Key page, select Yes if you are using a cluster setup. For non-cluster setup, select No.

        NOTE:

        • The User Application uses the master key to access encrypted data.

        • You must complete these steps after installing the first instance of the User Application in a cluster. Every instance of the User Application in a cluster must use the same master key. For more information, see Using the Same Master Key for Each User Application in the Cluster in the Identity Manager Setup Guide.

        • Complete these steps if 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.

        • Complete these steps also if you are restoring your User Application and you want to access the encrypted data stored by your previous version of the User Application.

        • By default, the installation procedure writes the encrypted master key to the master-key.txt file in the installation directory.

        • If you select Yes, import an existing master key from the renamed Identity Manager directory.

        • Copy the content from the master-key.txt and paste it in the Import Master Key page.

          Linux: Copy the output of the following command and paste it in the Import Master Key page.

          cat /opt/novell/idm_mysql/master-key.txt

          Windows: C:\Novell\idm_mysql/master-key.txt

      • To configure the User Application settings after the installation, click Configure Later in the Configure IDM page.

        NOTE:

        • If you click Cancel, the installer takes you back to the Application Server Connection page.

        • To edit the settings after the installation, run the configupdate.sh or configupdate.bat file located in the installation subdirectory on your platform. Remember that in a cluster, the settings in this file must be identical for all members of the cluster.

   4. Click OK, then click Next.

2. In the Pre-Installation Summary window, click Install.

3. (Optional) Review the installation log files. For results of the basic installation, see the Identity_Manager_User_Application_InstallLog.log file.

4. Click Next and then click Done.

1. Back up your eDirectory Identity Vault. For information about backing up eDirectory, see Backing Up and Restoring eDirectory in the eDirectory Administration Guide.

2. In Designer, back up and export your Designer project. For information about exporting Designer projects, see Exporting a Project in the Identity Manager Designer Administration Guide.

3. (Conditional) If using virtual machines to host Identity Manager components, create snapshots of all the virtual machines you use. Refer to the documentation specific to your virtualization software for instructions.

4. Download the installation package: IDM-HPD-402A.zip.

To install User Application 4.0.2 A:

1. Download the Updater files to your User Application server.

2. Stop JBoss.

3. At a command prompt, navigate to the directory where you downloaded the Updater files and enter the following command:

   ./IdmHPD.bin

   NOTE:Use the chmod command to change the permissions on the IdmHPD.bin file to allow you to execute the file as a program.

4. Click Next.

5. Review the license agreement, then click Next.

6. Specify the location of the hpd-conf-runtime-4.0.2A.zip file and click Next.

7. Specify User Application is installed in your environment and click Next.

   If User Application and Identity Reporting Module are installed in your environment, then select both components.

8. Specify the location of the install.properties file on your User Application server and click Next.

9. (Conditional) If you do not have your User Application install.properties file, clear Load Properties, click Next, and specify the configuration information for your installation on the subsequent windows.

10. Confirm the default backup directory or specify a different backup directory to use, then click Next.

11. Click Install, then click Done when finished.

1. Log in to the PostgreSQL database by using PgAdmin tool with username as postgres and the same password that was specified during PostgresSQL installation.

   NOTE:This procedure assumes that you specified idmuserappdb when User Application was installed with MySQL.

2. Right-click idmuserappdb and select Delete/drop from the list.

   This will delete the database from the server.

3. Right-click Databases and select New Database from the list.

4. Specify the same name for the database that you deleted in Step 2 (idmuserappdb).

5. From the drop-down list, select idmadmin as the owner of the database.

6. Click OK.