Preparing a UNIX environment
This section provides tasks for preparing your UNIX environment before installing BMC Remedy Action Request (AR) System server 8.1 on UNIX or Linux. On UNIX, the installer uses a graphical user interface. (Alternatively, you can use the silent installer).
The following topics are provided:
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/mnttab file (write access, HP-UX 11.23 only)
If you do not have a /etc/arsystem directory, you must create it to complete the installation.
- /usr/tmp directory
If you do not have a /opt/bmc directory, you must create it to complete the installation.
AIX also requires execute and suid permissions to the /usr/sbin/slibclean file for root and nonroot users.
- JREHomeDirectory/bin (read and execute permission)
- JREHomeDirectory/lib (read, write, and execute permission)
- You must provide the nonroot user with write access to the following files, if available (if you do not have these files, you must create them to complete the installation):
- Ensure that the open files limit [ ulimit –n ] of the shell is set to 16384. For this setting, you must modify the/etc/security/limits.conf file.
- Ensure that the nonroot user belongs to a group that has database access (for example, the dba group).
Keep the following points in mind:
- This step is valid for all database types.
- You must perform this step for installation only.
- You must add the user to the group where the database is installed and give the user read, write, and execute permissions to access the database file system.
- For Oracle client libraries, you must give access to the Oracle client Home directory and the Oracle server Home directory.
- 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.
- On the Linux platform, if you will be starting
arserverdas a nonroot user, ensure that the "open files" limit of the shell is set to 16384.
- 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
- 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
Due to installer framework changes in 8.1.02, this requirement is not valid from 8.1.02 and later.
The installer uses the IATEMPDIR environment 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.
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
The installer no longer supports the command-line interface on UNIX, as it did in previous versions. To install on a headless computer, use a remote X Windows session or the silent installation process.
Allowing long file names (HP-UX and Linux)
For HP-UX and Linux 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 6.x
Before you install the BMC Remedy Action Request (AR) System server and the BMC Remedy IT Service Management (ITSM) 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 that the BMC Remedy AR System services start.
- Check for the 32-bit libstdc++.so.5 under the /usr/lib folder.
# service rpcbind stop # rpcbind -i # service rpcbind status
- Install the AR System server.
- Launch the installer with the setup.sh script.
This script, which is located in the Disk1 folder, implements ulimit and other checks to prevent the installation from failing. For more information, see Setting ulimit before installing BMC Remedy ITSM.
- If you are installing BMC Service Request Management (which is part of the BMC Remedy ITSM suite), install the following packages:
Preparing to install on Red Hat Linux 7.x
Install the libXtst.i686 32-bit RPM packages so that user interface support is available for the installer.
Preparing to install on AIX
Before running the installer in an IBM AIX environment, set data, data_hard, core, and core_hard to unlimited in the /etc/security/limits file for the user running the installer. These settings ensure that the installer will not fail due to data segment size or core file size when the installer runs arStart.sh from a shell window.
If you are installing the BMC Remedy Action Request (AR) System server for AIX with Oracle, the AR System server installation files must reside on a local file system, not on a network file system.
Setting ulimit before installing BMC Remedy ITSM
Before you install BMC Remedy IT Service Management (ITSM), set the size of physical memory or the number of file descriptors; for example:
ulimit -n unlimited ulimit -m unlimited
Launch the installer with the setup.sh script. This script, which is located in the Disk1 folder, implements a
ulimit check to prevent the installation from failing.
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.