Implementation Guide › Installing the Enterprise Management Server › How to Prepare the Enterprise Management Server › Prepare the Enterprise Management Server on Linux

Prepare the Enterprise Management Server on Linux

Valid on Linux

Before you install the Enterprise Management Server, you prepare the server. If you are upgrading an r12.5 or later installation, you have already prepared the Enterprise Management Server and you do not need to complete these steps again.

When you install the Enterprise Management Server, the installation program also installs CA ControlMinder Endpoint Management, if it is not already installed. If you have installed CA ControlMinder Endpoint Management, do not repeat those steps.

Follow these steps:

1. Prepare the central database for Enterprise Management.

   Note: If the database administrator wants to review and control the changes that CA ControlMinder makes to the database, you can prepare the database manually by creating and configuring the central database using the RDBMS native management tools.

2. Install a supported version of Java Development Kit (JDK) or use existing software:

   Note: You can find prerequisite third-party software on the CA ControlMinder Third Party Components DVDs. For information about supported versions, see the Release Notes.

   1. Print your system information to determine whether the server architecture is 32-bit or 64-bit:

      uname -m
      

      If the command returns"i386" or "i686", it is a 32-bit architecture. If it returns "x86_64", it is a 64-bit architecture.

   2. Change to the "x86" directory (for 32-bit) or to the "x64" directory (for 64-bit, respectively) on the installation media, and run the installer. For example:

      chmod 750 jdk-7u21-linux-x64.rpm.bin
      

      ./jdk-7u21-linux-x64.rpm.bin
      

   3. Append the JDK/bin path to the system PATH.

      For example, to set the path "/usr/java/jdk1.7.0_21/" using the bash shell, enter the following command:

      export PATH=/usr/java/jdk1.7.0_21/bin:$PATH
      

      Note: To set the path permanently, add this command to your shell startup file.

3. Install a supported JBoss version or use existing software. We recommend that you run JBoss as a daemon.

   Note: If you already have JBoss installed, we recommend that you run JBoss once before installing CA ControlMinder Enterprise Management to resolve any open ports issues. The CA ControlMinder Enterprise Management installation program does not use the default JBoss ports. For example, it uses port number 18080 rather than the default port number 8080 for HTTP connections.

   1. Extract the JBoss archive to install it.

      cp jboss-4.2.3.GA.zip /opt/
      unzip jboss-4.2.3.GA.zip
      

   2. Change the port number from 8080 to 18080, and change the redirect port from 8443 to 18443 in server.xml.

      vi /opt/jboss-4.2.3.GA/server/default/deploy/jboss-web.deployer/server.xml
      <Connector URIEncoding="UTF-8" acceptCount="150" address="${jboss.bind.address}" connectionTimeout="20000" disableUploadTimeout="true" emptySessionPath="true" enableLookups="false" maxHttpHeaderSize="8192" maxThreads="250" port="18080" protocol="HTTP/1.1" redirectPort="18443"/>
      <Connector SSLEnabled="true" URIEncoding="UTF-8" clientAuth="false" keyAlias="entm" keystoreFile="/opt/jboss-4.2.3.GA/server/default/deploy/IdentityMinder.ear/custom/ppm/truststore/ssl.keystore" keystorePass="secret" maxThreads="150" port="18443" protocol="HTTP/1.1" scheme="https" secure="true" sslProtocol="TLS"/>
      <Connector address="${jboss.bind.address}" emptySessionPath="true" enableLookups="false" port="8009" protocol="AJP/1.3" redirectPort="18443"/>
      

   3. Change the naming port from 1099 to 11099 in jboss-minimal.xml.

      vi /opt/jboss-4.2.3.GA/server/default/conf/jboss-minimal.xml
      <mbean code="org.jboss.naming.NamingService"
            name="jboss:service=Naming"
            xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
            <attribute name="CallByValue">false</attribute>
            <attribute name="Port">11099</attribute>
      

   4. Change the naming port from 1099 to 11099 in jboss-service.xml.

      vi /opt/jboss-4.2.3.GA/server/default/conf/jboss-service.xml
      <mbean code="org.jboss.naming.NamingService"
            name="jboss:service=Naming"
            xmbean-dd="resource:xmdesc/NamingService-xmbean.xml">
            <attribute name="CallByValue">false</attribute>
            <attribute name="Port">11099</attribute>
      

   5. Configure JBoss to start as a daemon. For more information see https://community.jboss.org/wiki/startjbossonbootwithlinux.
4. Change the maximum number of open files to avoid failures during the installation:

   ulimit -n 10000
   

5. Verify that the rpmbuild package from your Linux distribution is installed.

   The Enterprise Management Server requires the rpmbuild package to install the Advanced Policy Management option on the server.

You can now install CA ControlMinder Enterprise Management on the Enterprise Management Server.