Previous Topic: Configure the Identity Management Server Properties FileNext Topic: High-Availability: Identity Management Server 2


Install and Verify the Identity Management Server

After you set the Identity Management Server parameters and back up the properties.sh file, run the installation program.

Verify the installation before proceeding with further installation steps.

Follow these steps:

  1. Navigate to:
    /opt/CA/saas/repo/application/
    
  2. Run:
    ./appliance_local.sh config 
    

    When installation is complete, set up JBoss. Then verify the installation as follows.

Setup Using JBoss EAP

If you are using JBoss EAP, do the following:

  1. Edit the file /opt/jboss-eap-5.1.2/jboss-as/server/all/conf/props/jmx-console-users.properties
  2. Uncomment the line "#admin=admin"
  3. Run the following command:
    dos2unix ../conf/props/jmx-console-users.properties
    
  4. Stop and Start the Identity Management Server using JBoss, using the following steps:
    cd /etc/init.d/im stop
    
    cd /etc/init.d/im start
    

JBoss Configuration

The recommended memory for the Identity Management Server on JBoss is 6GB (6144). This is physical memory rather than swap space.

During installation, the system allocates memory to JBoss. The installation process calculates the memory allocation based on the physical memory of the system, as follows:

After installation is complete, check your overall system memory and check the memory allocated to JBoss. The JBoss memory allocation is found in the run.sh file on the Identity Management Server.

If you do not have sufficient memory on the system, increase the max memory used by JBoss as follows:

  1. Edit the file /opt/jboss-5.1.0.GA/bin/run.sh as follows:
    JAVA_OPTS="$IDM_OPTS $DEBUG_OPTS -Djava.security.policy=workpoint_client.policy -Xms256m -Xmx6144m -XX:MaxPermSize=256m -XX:ReservedCodeCacheSize=50m"
    

    In this example, the memory allocated is 6GB (6144).

  2. Restart JBoss.

Verify the Server Installation

  1. Issue this command to check if Java is running:
    ps -ef|grep java
    

    The response includes the following:

    java -Xms256m -Xmx4096m -cp ./lib/* com.ca.directory.dxagent.service.DxAgentService
    
  2. Verify that the /opt/jboss-5.1.0.GA/bin/run.sh file has the multicast_address and multicast_groupname that were set in /tmp/properties.sh file.
  3. Verify that the following folders are present.

    For the community edition of JBoss:

    /opt/jboss-5.1.0.GA/server/all/deploy/iam_im.ear/user_console.war/META-INF/csp
    /opt/jboss-5.1.0.GA/server/all/deploy/iam_im.ear/user_console.war/META-INF/tenant
    

    For JBoss EAP:

    /opt/jboss-eap-5.1.2/jboss-as//server/all/deploy/iam_im.ear/user_console.war/META-INF/csp
    /opt/jboss-eap-5.1.2/jboss-as//server/all/deploy/iam_im.ear/user_console.war/META-INF
    
  4. Verify that the following files are present.

    For the community edition of JBoss:

    /opt/jboss-5.1.0.GA/server/all/deploy/iam_im.ear/user_console.war/META-INF/csp/CSP.properties
    /opt/jboss-5.1.0.GA/server/all/deploy/iam_im.ear/user_console.war/META-INF/tenant/Container.properties
    

    For JBoss EAP:

    /opt/jboss-eap-5.1.2/jboss-as//server/all/deploy/iam_im.ear/user_console.war/META-INF/csp/CSP.properties
    /opt/jboss-eap-5.1.2/jboss-as//server/all/deploy/iam_im.ear/user_console.war/META-INF/tenant/Container.properties
    
  5. For a high availability installation, edit the following file:

    For the community edition of JBoss:

    /opt/jbos-5.1.0.GA/server/all/deploy/iam_im.ear/policyserver.rar/META-INF/ra.xml 
    

    For JBoss EAP:

    /opt/jboss-eap-5.1.2/jboss-as//server/all/deploy/iam_im.ear/policyserver.rar/META-INF/ra.xml 
    

    This requires the following line:

    <config-property-value>Your SiteMinder Policy Server1 Hostname,44441,44442,44443</config-property-value>
    
  6. For a high-availability deployment, continue with installing a second Identity Management Server. For a single-instance deployment, continue with installing the Report Server.