×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.
BMC Cloud Lifecycle Management 4.6 ... Installing Preparing for installation Setting up the installation environment

Preparing to run the installer on a Linux computer

Before you start installing the products in the BMC Cloud Lifecycle Management solution, prepare the Linux computer on which you will run the installer by using the procedures explained in this topic:

To prepare for installation on a Microsoft Windows computer, see Preparing to run the installer on a Windows computer.

Before you begin

Ensure that you review the complete list of requirements, listed at System requirements for Linux.

To check for existing installer

Check if there is an existing installer from a previous installation on the host. If there is, back up and delete the previous /opt/bmc/Planner installation folder. Also, back up and delete the /opt/bmc/ProductRegistry.xml file.

To install from the tmp directory

Ensure that you update the /etc/fstab filesystem with the correct mount property for the installationPath/tmp directory. Set the default value of the fourth column of the filesystem to exec. For more information, see Updating the fstab filesystem in Linux in the Linux documentation.

To set the screen resolution

Set your computer screen to the recommended resolution of 1280 x 800 or greater.

Oracle JRE requirements

When the product installation or upgrade requires the 64-bit Oracle JRE as a prerequisite, you cannot substitute the OpenJDK version. Before you start:

  1. Check the Java version installed on your host.
  2. If the OpenJDK is installed, uninstall it and replace it with the 64-bit Oracle JRE. 

  3. If you removed the OpenJDK and installed the Oracle JRE, verify that the environment variables are properly set to reflect the new JRE version. 

 

Otherwise, consult the following table for which version of the Oracle JRE is required for 4.6.

Oracle JRE required for new installations or upgrades  Notes
CLM components

Category 1

  • EAR
  • Mid Tier
  • AtriumWS

Category 2

  • Platform Manager
  • Cloud Portal
  • EUP
  • Self Check Monitor
 
4.6Oracle/Zulu 1.8 (public JRE)
  • Oracle/Zulu 1.8 (public JRE)
  • Use bundled JRE (1.8.0_60)

  • New installations of 4.6 require that you install two versions of the public JRE before you start the installation.
    If you use the bundled JRE to install Category II products, then you need only one version of the public JRE that is required by the Category I products. 

  • Upgrades to 4.6 require that you install two versions of the public JRE before you start the upgrade.
    If you use the bundled JRE to upgrade the Category II products, then you need only one version of the public JRE that is required by Category I products.

To configure rpcbind process

(For Red Hat Enterprise Linux 6 only) Start the rpcbind process with the -i option on Cloud Portal and Database host before installing to avoid install failures:

# service rpcbind stop
# rpcbind -i
# service rpcbind status

(For Red Hat Enterprise Linux 7 only) Update the /etc/sysconfig/rpcbind file with RPCBIND_ARGS="-i" parameter. Restart the rpcbind process by using the command below:

#systemctl restart rpcbind

To install packages on Linux 6.x computers

The following video presentation (4:05) shows you how to subscribe to the Red Hat Network.

 

 https://youtu.be/cCBUd3eQhIk

The following video presentation (8:38) shows you how to use yum and rpm to install Linux packages on your Linux host. 

 https://youtu.be/o_xPqITchyc 

You can also use the following .txt file to create a script for easy installation. 

yuminstall.txt

Specific packages are required to access the graphical user interface (GUI) on Red Hat Linux 6.2 computers.

Note

Contact your Linux system administrator to check for these packages.

Tip

If you see an Abuse of Service error when you try to register your VM with the Red Hat network, delete the /etc/sysconfig/rhn/systemid file so that the VM gets a clean ID for registering with Red Hat. 
  1. Install the following minimum versions of the 32-bit RPM packages:

    • unixODBC-devel-2.2.14-12.el6_3.i686.rpm

    • unixODBC-2.2.14-12.el6_3.i686.rpm

    • libX11-1.5.0-4.el6.i686.rpm

    • libXau-1.0.5-1.el6.i686.rpm

    • libxcb-1.8.1-1.el6.i686.rpm

    • libXext-1.3.1-2.el6.i686.rpm

    • libXi-1.3-3.el6.i686.rpm

    • libXtst-1.0.99.2-3.el6.i686.rpm

    • libXp-1.0.0-15.1.el6.i686.rpm

    • libICE-1.0.6-1.el6.i686
    • libSM-1.1.0-7.1.el6.i686

    • openssl-1.0.0-20.el6_2.5.i686.rpm

    • libgssglue-0.1-11.el6.i686.rpm

    • krb5-libs-1.10.3-10.el6_4.2.i686.rpm

    • libcom_err-1.41.12-14.el6.i686.rpm

    • keyutils-libs-1.4-4.el6.i686.rpm

    • libselinux-2.0.94-5.3.el6.i686.rpm

    • zlib-1.2.3-29.el6.i686.rpm

    • libidn-1.18-2.el6.i686.rpm

    • libcap-2.16-5.5.el6.i686.rpm

    • libattr-2.4.44-7.el6.i686.rpm

    • libstdc++-4.4.4-13.el6.i686.rpm

    • elfutils-libelf-devel-0.152-1.el6.i686.rpm

    • elfutils-libelf-devel-static-0.152-1.el6.i686.rpm

    • libaio-devel-0.3.107-10.el6.i686.rpm

    • libgcc-4.4.7-3.el6.i686.rpm

    • libstdc++-devel-4.4.6-4.el6.i686.rpm

    • glibc-devel-2.12-1.107.el6.i686.rpm

    • glibc-2.12-1.107.el6.i686.rpm

    • compat-libstdc++-33-3.2.3-69.el6.i686.rpm

    • compat-libtermcap-2.0.8-49.el6.i686.rpm

    • xorg-x11-xauth-1.0.2-7.1.el6.i686

    • pam.i686 – Linux-PAM (Pluggable Authentication Modules for Linux) RPM

  2. Install the following minimum versions of the 64-bit RPM packages:

    • unixODBC-devel-2.2.14-12.el6_3.x86_64.rpm

    • unixODBC-2.2.14-12.el6_3.x86_64.rpm

    • libX11-1.5.0-4.el6.x86_64.rpm

    • libXau-1.0.5-1.el6.x86_64.rpm

    • libxcb-1.8.1-1.el6.x86_64.rpm

    • libXext-1.3.1-2.el6.x86_64.rpm

    • libXi-1.3-3.el6.x86_64.rpm

    • libXtst-1.0.99.2-3.el6.x86_64.rpm

    • libXp-1.0.0-15.1.el6.x86_64.rpm

    • libICE-1.0.6-1.el6.x86_64
    • libSM-1.1.0-7.1.el6.x86_64

    • openssl-1.0.0-20.el6_2.5.x86_64.rpm

    • libgssglue-0.1-11.el6.x86_64.rpm

    • krb5-libs-1.10.3-10.el6_4.2.x86_64.rpm

    • libcom_err-1.41.12-14.el6.x86_64.rpm

    • keyutils-libs-1.4-4.el6.x86_64.rpm

    • libselinux-2.0.94-5.3.el6.x86_64.rpm

    • zlib-1.2.3-29.el6.x86_64.rpm

    • libidn-1.18-2.el6.x86_64.rpm

    • libcap-2.16-5.5.el6.x86_64.rpm

    • libattr-2.4.44-7.el6.x86_64.rpm

    • libstdc++-4.4.4-13.el6.x86_64.rpm

    • elfutils-libelf-devel-0.152-1.el6.x86_64.rpm

    • elfutils-libelf-devel-static-0.152-1.el6.x86_64.rpm

    • libaio-devel-0.3.107-10.el6.x86_64.rpm

    • libgcc-4.4.7-3.el6.x86_64.rpm

    • libstdc++-devel-4.4.6-4.el6.x86_64.rpm

    • gcc-4.4.6-4.el6.x86_64.rpm

    • glibc-devel-2.12-1.107.el6.x86_64.rpm

    • glibc-headers-2.12-1.107.el6.x86_64.rpm

    • kernel-headers-2.6.32-279.el6.x86_64.rpm

    • glibc-2.12-1.107.el6.x86_64.rpm

    • glibc-common-2.12-1.107.el6.x86_64.rpm

    • gcc-c++-4.4.6-4.el6.x86_64.rpm

    • sysstat-9.0.4-20.el6.x86_64.rpm

    • compat-libstdc++-33-3.2.3-69.el6.x86_64.rpm

    • compat-libtermcap-2.0.8-49.el6.x86_64.rpm

    • Linux-PAM (Pluggable Authentication Modules for Linux) RPM

    • bc-1.06.95-1.el6.x86_64
  3. To ensure that the BMC Remedy AR System services start, install the compat-libstdc++-33-3.2.3-69.el6.i686.rpm RPM package.
  4. To ensure that the RSCD Agent installs properly, install the compat-libtermcap-2.0.8-49.el6.x86_64.rpm package.

  5. From the /usr/lib folder, verify that the libstdc++.so.5 library exists. Install the library if it does not exist.

  6. To verify whether the RPM is installed, enter the following command:

    rpm -ql package
rpm -ql compat-libstdc++-33-3.2.3-69.el6.i686.rpm

To install packages on Linux 5.x computers

The following packages are required to access the graphical user interface (GUI) on RedHat Linux 5.x computers.  Install the following minimum versions of the packages on your installer host:

Contact your Linux system administrator to check for these packages.

  • libXi-1.0.1-4.el5_4
  • libX11-1.0.3-11.el5
  • libXau-1.0.1-3.1
  • libICE-1.0.1-2.1
  • libSM-1.0.1-3.1
  • libXtst-1.0.1-3.1
  • libXtst-1.0.1-3.1.i386
  • libXext-1.0.1-2.1
  • compat-libstdc++-33-3.2.3-61.i386
  • compat-libtermcap-2.0.8-49.el6.x86_64
  • libXi.i386
  • xorg-x11-server-Xorg
  • xorg-x11-utils
  • xorg-x11-xauth
  • bc-1.06-21

To verify whether the RPM is installed, enter the following command:

rpm -ql package
rpm -ql compat-libstdc++-33-3.2.3-69.el6.i686.rpm

To uninstall BMC Server Automation RSCD Agent and NSH

For new installations, if you have an existing BMC Server Automation Remote Server Call Daemon (RSCD) Agent and BMC Network Shell (NSH) installed on your installer host, you must uninstall them. Because the RSCD agent will be installed with every BMC product and the NSH will be installed on the installer host, you must uninstall any existing versions.

Note

This task is not required for upgrades.

  1. Stop the RSCD agent if it is running:
    /etc/init.d/rscd stop
  2. Go to /opt/bmc/NSH.
  3. Type the command ./Uninstall and follow the uninstallation process.
  4. Go to /opt/bmc/rscd directory and delete the rscd folder (if it exists).
  5. Manually delete the /usr/lib/rsc folder, the /usr/nsh folder, and the /etc/rsc folder (if it exists).
  6. Manually delete the /etc/init.d/rscd file.
  7. Manually delete the /usr/lib/rsc/HOME file.
  8. To ensure there are no remaining artifacts (for example, if the RSCD agent was installed via rpm):
    1. Verify that the RSCD agent rpm has been removed:
      rpm -qa | grep rscd 
    2. If the agent rpm is detected, delete it. For example:
      rpm -e BladeLogic_RSCD_Agent-8.8.00-303.x86_64 
  9. Reboot the machine after you have completed the cleanup.

For more information, see the Uninstalling other components on UNIX and Linux topic in the TrueSight Server Automation (formerly called BMC Server Automation) online technical documentation.

To verify product host connectivity

Perform the following steps to ensure that you can successfully launch the installation on a product host:

  1. Ensure that you can contact all target hosts (on which you want to install BMC products) from the installer host (for example, ping <hostName>).
  2. Run the ifconfig eth0 command on the target host, and verify that the IP address returned in the preceding step matches the target computer's IP address returned in this step.

Recommendation

Use tools, such as Xmanager and VConsole for connecting to the Linux computer and running the installer. With Xmanager, X applications installed on remote UNIX based computers run seamlessly with Windows applications side by side.

Back to top

Related topics

Preparing to run the installer on a Windows computer
Installation order and product dependencies
Installing BMC Cloud Lifecycle Management

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Last modified by Shweta Hardikar on Feb 24, 2020

Comments

  1. Dirk Petzel

    Hi,

    can we highlight the fact that there is a .txt. file containing the relevant yum install commands a bit better. (i.e. create a new note? )

    Customer missed that and did it one by one, which is a pain.  

    Just a thought.

     

    Dirk

     

    Aug 08, 2017 07:26
    1. Ranu Ganguly

      Are you talking about the following one?

      You can also use the following .txt file to create a script for easy installation. 

      yuminstall.txt

      Should we make it as Tip ?

      Sep 15, 2017 03:14
  2. Dirk Petzel

    Hi, Yes, highlighting this better might be a good idea... 


    (wink)


    Thanks Ranu!

    Sep 21, 2017 05:06
    1. Ranu Ganguly

      Hi Dirk, 

      Highlighted the text as Tip.

      Regards,

      Ranu

      Sep 22, 2017 01:25

Log in or register to comment.

Preparing to run the installer on a Windows computer
Setting up BMC Network Automation on Windows
© Copyright 2013 - 2017 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.