Upgrade Guide › JBoss Version › Upgrade on a JBoss Cluster › Migration on a JBoss Cluster › Configure the JK Connector

Configure the JK Connector

Follow these steps:

1. Install a JK connector based on these instructions:

   http://community.jboss.org/wiki/usingmodjk12withjboss

2. Note the following when you use this procedure:
   1. When you configure the modjk workers, use the workers.properties file in this location:

      Windows: C:\Program Files\CA\Identity Manager\IAM Suite\Identity Manager\tools\samples\ConnectorConfiguration\windows\IIS_JBoss

      UNIX: /opt/CA/IdentityManager/IAM_Suite/Identity_Manager/tools/samples/Cluster/JBoss/ConnectorConfiguration

   2. In this file, replace worker.workerN.* (the worker name) with your corresponding node’s Peer ID.

      If you have more than two nodes, copy a worker.workerN.* set for each additional node and rename the worker name.

   3. Fill in the worker.workerN.host field with your corresponding nodes’ hostnames.

      For example, consider a cluster where the CA Identity Manager server is installed on three JBoss hosts named myhostA, myhostB, and myhostC, using Peer IDs 1, 2, and 3. The workers.properties file appears as follows:

      worker.worker1.port=8009
      worker.worker1.host=myhostA
      .
      .
      worker.worker1.recovery_options=28
      
      worker.worker2.port=8009
      worker.worker2.host=myhostB
      .
      .
      worker.worker2.recovery_options=28
      
      worker.worker3.port=8009
      worker.worker3.host=myhostC
      .
      .
      worker.worker3.recovery_options=28
      .
      .
      worker.router.balance_workers=worker1,worker2,worker3
      

   4. Copy the uriworkermap.properties file in the above location to APACHE_HOME/conf.
   5. Omit the step about configuring Tomcat for session stickiness. This feature is already configured by the installer and in the workers.properties file.

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.