Upgrade Guide › JBoss Version › Upgrade on a Single JBoss Node › Migrate a Node to a New JBoss › Install the CA Identity Manager Server on a JBoss Node

Install the CA Identity Manager Server on a JBoss Node

Once you have uninstalled CA Identity Manager server, you can install the CA Identity Manager server.

Note: If you see options to upgrade the workflow database and migrate task persistence data during the installation, enable those options. They appear in some situations when your previous installation was CA Identity Manager r12.

Follow these steps:

1. Install the new version of JBoss.

   Note: (for JBoss 5 only) If you are upgrading CA Identity Manager on a system which already has JBoss 5, perform these steps:

   1. Back up the jboss_home\server\all directory on all nodes.
   2. Remove the jboss_home\server\all directory.
   3. Install the all directory from the JBoss install source under jboss_home\server.
2. Perform a new install of the CA Identity Manager Server.
   • Windows: From your installation media, run the following program:

     ca-im-release-win32.exe
     

   • UNIX: From your installation media, run the installation program. For example, for Solaris:

     ca-im-release-sol.bin
     

   release represents the current release of CA Identity Manager.

3. Select the option to install the CA Identity Manager Server.
4. Supply the details for the JBoss that you collected in your worksheet.
5. For database credentials, provide the same values that existed at the previous installation.

   

   Important! If you are upgrading from CA Identity Manager r12 and you have different database stores for task persistence, workflow, audit, and reports, you will need to update the data sources manually after installation to point to the separate stores.

6. Create a user on the Login Information section using a password you can recall.

   

7. Review the summary of your upgrade choices and click Install.

   The installer installs the components you selected and gradually update the progress bar.

   

8. When the installation completes, inspect the Install Complete message. If you see errors on the screen, note the path for the logs, which explain the errors.
9. Install the latest version of the JK Connector and be sure that the workers.properties file has the following parameters set:

   worker.worker.ping_mode=A 
   worker.worker.fail_on_status=400,404,500,503
   worker.worker.recovery_options=28
   

Upgrade the Workflow Database

This procedure applies only if you are upgrading from CA Identity Manager r12.

To work with WorkPoint 3.4.2, you update the workflow database, so you can continue to use the workflow processes that you developed in WorkPoint 3.3.

Follow these steps:

1. Locate the WorkPoint scripts in the Workpoint\database under the Administrative Tools folder. The scripts are in the following default locations:
   • Windows: C:\Program Files\CA\Identity Manager\IAM Suite\Identity Manager\tools\Workpoint\database
   • UNIX: /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools/Workpoint/database
2. Run the following scripts:

   wp331_to_wp34_cnv_step1.sql

   This script creates the tables for Workpoint 3.4, adds columns the old tables, and inserts rows into the WP_*_TYPE tables.

   wp331_to_wp34_cnv_step2.sql

   This script creates the stored procedures that are required to convert the data.

   wp331_to_wp34_cnv_step3.sql

   This script converts the text data to columns and populates the new WP_BULK_DATA table from the old WP_BULK_STORAGE table.

   wp34_20060927_add.sql

   This script creates the tables for Workpoint 3.4.20060927 and inserts rows into the WP_INI and WP_*_TYPE tables.

   wp34_20070625_add.sql

   This script creates the tables for Workpoint 3.4.2.20070625 and inserts rows into the WP_INI and WP_*_TYPE tables.

   wp342_20071218_add.sql

   This script creates the tables for Workpoint 3.4.2.20071218 and inserts rows into the WP_INI and WP_*_TYPE tables.

   wp342b_to_wp342c.sql

   This script adds tables and rows to support the completion code.

   wp342c_to_wp342d.sql

   This script updates field lengths and scripts.

   wp342d_to_wp342e.sql

   This script adds index definitions.

3. Save all changes to the database.

Migrate Task Persistence Data

This procedure applies only if you are upgrading from CA Identity Manager r12.

You can manually migrate tasks, depending on task state or date range, by running the task persistence data migration tool.

Follow these steps:

1. Find the tpmigration125.properties file in the following location:

   admin_tools/tpmigration/com/ca/tp/migratetpto125

   

2. Update this file with the object store and task persistence information for your database.

   Note: For any supported version of SQL Server, enter sql2005.

   

3. Be sure that the environment variable JAVA_HOME is set.
4. From a command line, navigate to admin_tools/tpmigration and run the task persistence migration tool as follows:
   • For Windows:

     runmigration.bat
     

   • For UNIX:

     runmigration.sh
     

5. Enter the following information:
   1. For the environment protected Alias, enter all.

      Note: If you do not specify all, only one environment can be entered.

   2. For task state, enter All (with a Capital A).
      Note: If you do not specify All, only one task state can be entered.
   3. For the version to migrate from, enter 2 for 12.0.
   4. Date range for the tasks to be migrated (y/n).

      Note: If you choose 'y', enter a Start Date (mm/dd/yy) and End Date (mm/dd/yy).

   The migration starts. After the migration completes, the status indicates how many tasks were migrated.

6. Be sure to verify that no errors appeared.
7. Repeat steps 4 and 5, but use the -pending option instead of All for task state.