Previous Topic: Uninstall the CA IdentityMinder ServerNext Topic: Configure Workflow for Your Profile

Upgrade Guide › WebSphere Version › Upgrade on a Single WebSphere Node › Migration of a Node › Install the new CA IdentityMinder Server on the WebSphere Node

Install the new CA IdentityMinder Server on the WebSphere Node

Follow these steps:

  1. Install WebSphere and the required FixPacks and JDK.
  2. Check that you have removed all unnecessary Websphere files or they may prevent the upgrade from succeeding.
  3. Stop the following items:
  4. Start the CA IdentityMinder installation program.

    release represents the current release of CA IdentityMinder.

    Note: If you see options to upgrade the workflow database and migrate task persistence data, enable those options. These options appear in some scenarios when your previous installation was CA IdentityMinder r12.

  5. Select the option to install the CA IdentityMinder Server.

    The screen shows the options to select for installation.

  6. Supply the WebSphere details. The WebSphere section includes these fields:
    WebSphere Install Folder

    The folder or directory where WebSphere is installed. You find this location in the Windows or UNIX file system.

    Server Name

    You find this name in the WebSphere console.

    Profile Name

    You find this name in the Windows or UNIX file system at the path:

    was_home/profiles/Deployment_Manager_Profile/config/cells/

    Cell Name

    The deployment manager's cell which can be found in the WebSphere console.

    Node Name

    A node that contains the Server Name you supplied on this screen. You find this name in the WebSphere console.

    Access URL and port

    The fully-qualified system name and port number used by WebSphere.

  7. For database credentials, provide the same values that existed at the previous installation.

    The user enter information about the database.

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

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

    The user enters a user name and password.

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

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

    The progress bar appears.

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

If you are upgrading from CA IdentityMinder r12, continue by upgrading the workflow database.

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:
  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

    The user selects the tipmigrateto125.properties file.

  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.

    The user views sections to change in the tipmigrateto125.properties file.

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