This documentation supports the 19.02 version of Remedy Deployment.

To view the latest version, select the version from the Product version menu.

Preparing a UNIX environment

This section provides tasks for preparing your UNIX environment before installing on UNIX.

The following topics are provided:

Preparing to install with port mapper on Linux

Preparing to install with port mapper on Linux

If you are using a port mapper, start the rpcbind process with -ioption:

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

If you are using the port mapper, start the rpcbind with the –i option and perform the following procedure. You need to be a superuser to perform the procedure:

For RHEL Red Hat Enterprise Linux 6:

  1. Update the /etc/sysconfig/rpcbind file with the parameter below:

    RPCBIND_ARGS="-i".

  2. Restart the rpcbind process by using the command below:

    #service rpcbind restart

 

For RHEL Red Hat Enterprise Linux 7:

  1. Update the /etc/sysconfig/rpcbind file with the parameter below:

    RPCBIND_ARGS="-i".

  2. Restart the rpcbind process by using the command below:

    #systemctl restart rpcbind

Verify partition mount setting

Verify the following:

  • All the partitions that BMC Remedy AR System uses must not have the noexec flag set.
  • The partition on which the system's  tmp  directory is mounted must not have noexec flag set.

Setting the number of process and open files

  • Work with your system administrator to set the number of processes (nproc value) during run time. In most of the cases, the default value works successfully.
  •  Set the number of open files to 16,384.
  • Set limits on the amount of resources to be used in the limits.conf file by using the following command:
    vi /etc/security/limits.conf
    root soft nofile 20000
    root hard nofile 20000

If your system hangs, collect the Java heap dumps and thread dumps for troubleshooting. For information on collection Java dumps and thread jumps, refer to KA000101754 . 

Preparing to install as a nonroot user

Installing as a nonroot user allows a user to maintain the BMC Remedy AR System software without the help of a system administrator. However, to automatically start the AR System server when the host computer reboots, you must ask your UNIX system administrator to change the system startup scripts accordingly. When you install as a nonroot user, you must manually update the system configuration files. The installation script prompts you to do so and instructs you to start a shell in which you have root access or full read and write access.

  1. Ensure that you have access to the following directories and the files under them:

    Folder and filesReadWriteExecuteRequire access
    profile file in your home directory (tick)(tick)During the installation.
    /etc/arsystem
    If you do not have a /etc/arsystem directory, you must create it to complete the installation.
    (tick)(tick)(tick)

    /etc/profile

    /etc/.login

    /etc/bmc.cshrc

    /etc/bmc.profile

    /etc/csh.cshrc

    If you do not have these files, you must create them to complete the installation.

     (tick) 
    System's tmp directory  (tick) 

    opt/apache
    This directory is used only if mid tier is installed.

    (tick)(tick)(tick) 
    /opt/bmc
    If you do not have a /opt/bmc directory, you must create it to complete the installation.
    Note: Access to this folder is required even if you are planning to install AR System in any other directory.
    If your installation directory is in a separate folder, you might also create a symbolic link to that folder.
    (tick)(tick)(tick) 
    JREHomeDirectory /bin(tick) (tick) 
    JREHomeDirectory /lib(tick)(tick)(tick)Temporary access only during installation.
    /dev/console (tick) 
  2. Run the BMC Remedy AR System installation.
    Some of the actions you will be prompted to perform (as a nonroot user) are as follows:
    • Create several directories and set permissions for those directories. 
      For example, the script prompts you to create the  /etc/arsystem  directory with read and write permissions for all users.
    • Merge the contents of files.
      For example, merge the  <ARSystemServerInstallDir>/ar-<Database>/rpc  file with the  /etc/rpc  file.
  3. To install other BMC applications as a nonroot user, you must log in to the UNIX system under the same UNIX user ID that was used to install BMC Remedy AR System.

Running a remote installation on UNIX

  1. Ensure that you have an X Windows client on the local computer.
  2. Log on to the remote computer, and set the DISPLAY environment variable to point to the X Windows client on the local computer.
  3. Run the installer.

Note

Assigning temporary disk space

BMC recommends that you have 1.5 GB of free temporary disk space. To verify you available space, use the df- k command check /tmp. If the temporary space on UNIX is less than 1.5 GB, you can optionally set the IATEMPDIR or the TMPDIR environment variable to point to a directory that has sufficient disk space. The installer uses the IATEMPDIR variable to assign the location of a temporary directory to use during installation. If your /tmp or /home/ userName directories do not have enough free space to run the installation, it will fail.

If you have access to another drive or partition with more free space, set a new temp directory by using one of the following commands:

  • export IATEMPDIR=/ <pathName>
  • setenv IATEMPDIR=/ <pathName>

In these commands, <pathName> is a writable directory with more free space available than the default directories.

Note

The installer gives the first preference to the IATEMPDIR environment variable. If it is not available, it uses the TMPDIR environment variable.

For more information, see https://communities.bmc.com/docs/DOC-72933.

Removing sticky bit permissions on the temporary directory

If you have sticky bit permissions on the temporary directory, the installer does not create the /tmp/ARSystemInstalledConfiguration.xml file. Therefore, you must remove the sticky bit permissions from the directory before running the installer.

Installing in a headless environment

To install on a headless computer, use a remote X Windows session or the silent installation process.

Allowing long file names (UNIX)

For UNIX systems, configure the operating system to allow long file names to be read and copied. You might experience issues with configuring the operating system when you install directly from a DVD. In some cases, the DVD mount might cause long file names from the DVD to not work.

Preparing to install on Red Hat Linux

Before installing the AR System server and the BMC Remedy IT Service Management suite on a Red Hat Linux 6.x and 7.x server, complete the following steps:

  1. Install the following 32-bit RPM packages so that user interface support is available for the installer:
    You might install the minimum required version, as explained in the following list, or a later version of RPM packages.

    • libX11-1.3-2.el6.i686.rpm
    • libXau-1.0.5-1.el6.i686.rpm
    • libxcb-1.5-1.el6.i686.rpm
    • libXext-1.1-3.el6.i686.rpm
    • libXi-1.3-3.el6.i686.rpm
    • libXtst-1.0.99.2-3.el6.i686.rpm  
    • libstdc++-4.4.7-11.el6.i686  
    • glibc-2.17-105.el7.i686
    • libgcc-4.4.7-4.el6.i686.rpm
  2. Install the compat-libstdc++-33-3.2.3-69.el6.i686.rpm RPM package to ensure the BMC Remedy AR System services start.
  3. Check for the 32-bit  libstdc++.so.5  and 32-bit libstdc++.so.6 under the /lib or /usr/lib folder.

  4. Install the AR System server.
  5. Launch the installer with the setup.bin.
    This script, which is located in the Disk1 folder, implements ulimit and other checks to prevent the installation from failing.
  6. Install the following packages if you are installing BMC Service Request Management (which is part of the BMC Remedy IT Service Management suite):
    • ncurses-devel-5.7-3.20090208.el6.i686.rpm
    • ncurses-libs-5.7-3.20090208.el6.i686.rpm
  7. Install the libXtst.i686.rpm 32-bit RPM package so that user interface support is available for the installer.
  8. Install Dejavu font set by using the following command:

    # yum install dejavu-lgc-sans-fonts

    If you do not install the Dejavu fonts, you may not be able to view the fonts on installer screens.

  9. Before upgrading BMC CMDB using JDK 11, in the .profile file, set the BMC_JAVA_HOME variable to point to the JDK 11 path. For example:

    BMC_JAVA_HOME="/usr/JAVA/jdk-11.0.1/"
    export BMC_JAVA_HOME


    If you are performing silent installation, you need not set the BMC_JAVA_HOME variable in the
    .profile file

Using kernel tuning to increase the number of transactions and users

Before you install the BMC Remedy Action Request (AR) System server, consider increasing the value of kernel parameters that affect the AR System server (or any other multithreaded server process). This increase ensures that BMC Remedy applications can support the expected volume of transactions and users.

For example, consider increasing the following process features:

  • Number of threads available for a process
  • Available memory—For example, the arserverd process often requires between 500 MB and 1 GB of memory (for BMC Remedy AR System with no additional forms or applications installed).
  • Number of associated files or process descriptors—Descriptors should be at least 2.5 to 3 times the number of expected concurrent connections or 1024 (whichever is greater). Examples of connections include user logons (client or browser), the Email Engine, and custom application programming interfaces (APIs).

Contact your system administrator or operating system vendor for more information about kernel tuning.

Preparing to install on SUSE 11 and 12

You can install the BMC Remedy ITSM Suite on SUSE 11 and 12 versions.

Before installation, make sure that you have installed the following RPM:

  • libstdc++33-32bit-3.3.3-38.1.1.x86_64.rpm

Note

You will also require libstdc++.so.6.rpm when installing BMC Remedy ITSM Suite on SUSE 11 and 12 versions.

Preparing to install with external Tomcat

When you are installing BMC Remedy Mid Tier with an external Tomcat that is higher than the bundled Tomcat version, on a non-default location, Tomcat will not be auto-detected.

You must install Tomcat on the default location to get it auto-detected.

Preparing to install on Solaris 11

You can install the BMC Remedy ITSM Suite on Solaris 11.

Before installation complete install the following packages:

  • system/picl
  • compatibility/ucb 

Check the following prerequisites before running the commands:

  • Set the local_only option for the rpcbind to False.

  • You need to be the superuser.

Commands
#svccfg -s svc:/network/rpc/bind setprop config/local_only=false
#svcadm refresh svc:/network/rpc/bind 
#svcs -lv svc:/network/rpc/bind 

Before upgrading BMC CMDB using JDK 11, in the .profile file, set the BMC_JAVA_HOME variable to point to the JDK 11 path. For example:

BMC_JAVA_HOME="/usr/JAVA/jdk-11.0.1/"
export BMC_JAVA_HOME

If you are performing silent installation, you need not set the BMC_JAVA_HOME variable in the .profile file.


Was this page helpful? Yes No Submitting... Thank you

Comments