Preparing a UNIX environment
This section provides tasks for preparing your UNIX environment before installing BMC Remedy Action Request (AR) System server on UNIX.
The following topics are provided:
Preparing to install with port mapper on Linux
If you are using a port mapper, start the
rpcbind process with
# service rpcbind stop # rpcbind -i # service rpcbind status
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.
Preparing to install as a nonroot user
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.
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 your computer restarts, you must ask your UNIX system administrator to change the system startup scripts accordingly.
- Ensure that you have access to the following directories and the files under them:
- .profile file in your home directory (write and execute access)
- /etc/arsystem (read, write, and execute permission)
If you do not have a /etc/arsystem directory, you must create it to complete the installation.
- System's tmp directory
Additionally, provide execute access permission.
/opt/bmc (read, write, and execute permission)
If you do not have a /opt/bmc directory, you must create it to complete the installation.
- JREHomeDirectory/bin (read and execute permission)
- JREHomeDirectory/lib (read, write, and execute permission)
- /etc/profile (write permissions)
- /dev/console (write permission)
- /opt/apache (read, write, and execute permission)
This directory is used only if Mid-Tier is installed.
- 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.
- Create several directories and set permissions for those directories.
- 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.
Before you install or upgrade to BMC Remedy AR System 9.0, create a pluginsvrclient.log file at the root location. Give read and write permissions to the nonroot user for the pluginsvrclient.log file. For more information, see SW00488831.
Running a remote installation on UNIX
- Ensure that you have an X Windows client on the local computer.
- Log on to the remote computer, and set the DISPLAY environment variable to point to the X Windows client on the local computer.
- Run the installer.
Assigning a temporary directory
If your /tmp or /home/ userName directories do not have enough free space to run, the installation will fail. To assign the location of a temporary directory to use during installation, set the TMPDIR variable before running the installer. If you have access to another drive or partition with more free space, set a new temp directory by using the following command:
export TMPDIR = <pathName>
In this command,
<pathName> is a writable directory with more free space available than the default directories.
The installer assigns the -Djava.io.tmpdir system property the location of the temporary directory.
BMC recommends that you have 1 GB of free space.
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 server, complete the following steps:
- Install the following 32-bit RPM packages so that user interface support is available for the installer:
- Install the compat-libstdc++-33-3.2.3-69.el6.i686.rpm RPM package to ensure the BMC Remedy AR System services start.
Check for the 32-bit libstdc++.so.5 under the /usr/lib folder.
- Install the AR System server.
- 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.
- Install the following packages if you are installing BMC Service Request Management (which is part of the BMC Remedy IT Service Management suite):
- For Red Hat 7, install the libXtst.i686.rpm 32-bit RPM package so that user interface support is available for the installer.
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
With service pack 1 and later, you can install the BMC Remedy ITSM Suite on SUSE 11.
Before installation complete install the following RPM:
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, the tomcat will not be auto detected.
You must install the tomcat on the default location to get it auto detected.
Preparing to install on Solaris 11
With service pack 1 and later, you can install the BMC Remedy ITSM Suite on Solaris 11.
Before installation complete install the following packages: