Upgrade Guide › JBoss Version › Upgrade on a JBoss Cluster › Migrate CA Identity Manager 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.