Installation Guide › Server Installation › Identity Management Server › High-Availability: Secure Proxy Server 2 › Identity Management Server Pre-Installation Steps

Identity Management Server Pre-Installation Steps

To prepare for installation, confirm that your server environment is properly prepared. Then install the required packages.

Note: For installation a high-availability JBoss cluster, all nodes on the cluster must be on the same subnet.

Follow these steps:

1. Install 64-bit Linux RHEL 6.1.
2. Download, but do not install, a 64-bit JDK to your local system or to a file share.

   Note: The system installer can install the JDK automatically. We recommend that you download a JDK and allow the system to install it.

   Important! The Identity Management installation requires a JDK, rather than a JRE.

3. Download, but do not install, JBoss 5.1.0 to your local system or to a file share.

   Note: The system installer JBoss automatically.

4. Verify that Oracle is configured as follows:
   • The Oracle Database server is available with all Oracle services (listener, DB, and so on) running
   • Oracle has a user with username "CamAdmin" with the privileges to create tablespace and user. CamAdmin has the DBA and Connect Oracle roles. Make a note of the password for CamAdmin for later use during installation.
   • The Oracle Database uses a UTF-8 encoded character set. If you plan to enable Advanced Authentication for your environment, install the AL32UTF8 Oracle database character set.
5. From the Oracle web site, download the JCE policy zip file, jce_policy-6.zip. Copy the file to the /tmp folder on your Identity Management server.
6. Obtain the Identity Management Server ISO image from the CA Support site and extract it.
7. Copy the kit (CAM-IM_kit-date.zip) to / (the root folder).
8. Unzip the kit.
9. Install the following packages:
   • binutils-2*x86_64*
   • glibc-2*x86_64* nss-softokn-freebl-3*x86_64*
   • glibc-2*i686* nss-softokn-freebl-3*i686*
   • compat-libstdc++-33*x86_64*
   • glibc-common-2*x86_64*
   • glibc-devel-2*x86_64*
   • glibc-devel-2*i686*
   • glibc-headers-2*x86_64*
   • elfutils-libelf-0*x86_64*
   • elfutils-libelf-devel-0*x86_64*
   • gcc-4*x86_64*
   • gcc-c++-4*x86_64*
   • ksh-*x86_64*
   • libaio-0*x86_64*
   • libaio-devel-0*x86_64*
   • libaio-0*i686*
   • libaio-devel-0*i686*
   • libgcc-4*x86_64*
   • libgcc-4*i686*
   • libstdc++-4*x86_64*
   • libstdc++-4*i686*
   • libstdc++-devel-4*x86_64*
   • make-3.81*x86_64*
   • numactl-devel-2*x86_64*
   • sysstat-9*x86_64*
   • compat-libstdc++-33*i686*
   • compat-libcap*
   • unixODBC*
   • libstdc++*
   • compat-libstdc++-33.i686
   • compat-libstdc++-296.i686
   • glibc.i686
   • ksh.x86_64
   • libgcc.i686
   • libidn.i686
   • libstdc++.i686
   • libX11.x86_64
   • libXau.x86_64
   • libxcb.x86_64
   • libXext.i686
   • libXi.i686
   • libXtst.i686
   • ncurses-devel.i686
   • nss-softokn-freebl.i686
   • dos2unix
   • telnet
10. Run the following commands to set the state of the firewall/ip tables:

    chkconfig iptables off
    service iptables stop
    

11. Run the following commands to check and set the state of SELinux:
    1. Check the status:

       sestatus
       

    2. If the response is "permissive" or "disabled", do nothing
    3. If the response is "enforcing", change the state:

       sudo vi /etc/selinux/config
       setenforce 0