This documentation applies to the 8.1 version of Remedy Action Request System, which is in "End of Version Support."

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

Preparing the UNIX environment

BMC recommends that you read through the material in this topic before installing BMC Remedy AR System server version 8.1 on UNIX or Linux. On UNIX, the installer uses a graphical user interface. (Alternatively, you can also use the silent installer.)

Preparing to install as a non-root user

You can install the BMC Remedy AR System server as a root or non-root user.

When you install as a non-root user, you must update the system configuration files manually. The installation script prompts you to do this and instructs you to start a shell where you have root access or full read and write access.

Installing as a non-root user allows a user to maintain the BMC Remedy AR System software without the assistance 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.

  1. Make sure 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)
    • /etc/arsystem
      If you do not have a /etc/arsystem directory, you must create it to complete the installation. 
    • /usr/tmp directory
    • /opt/bmc directory
      If you do not have a /opt/bmc directory, you must create it to complete the installation.

      Note

      AIX also requires execute and suid permissions to the /usr/sbin/slibclean file, for the root and non-root user.

    • JREHomeDirectory/bin (read and execute permission)
    • JREHomeDirectory/lib (read, write, and execute permission)
  2. You need to provide the non-root user with write access to the following files if they are available. 
    If you do not have these files, you must create them to complete the installation. 
    • /etc/profile
    • /etc/.login
    • /etc/bmc.cshrc
    • /etc/bmc.profile
    • /etc/csh.cshrc 
  3. Also ensure that the open files limit [ ulimit –n ] of the shell is set to 16384. For this, you must modify the/etc/security/limits.conf file.
  4. Make sure that the non-root user belongs to a group that has database access (For example, the dba group).
    • This step is valid for all the database types.
    • You must do this only for installation. 
    • You must add the user to the group where 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  and Oracle server Home directory.
  5. Run the BMC Remedy AR System installation.
    Some of the actions you will be prompted to perform (as a non-root user) include:
    • Creating several directories and setting permissions for those directories.  For example, the script prompts you to create the /etc/arsystem directory with read/write permissions for all users.
    • Merging the contents of files. For example, merge the <ARSystemServerInstallDir>/ar-<Database>/rpc file with the /etc/rpc file.
  6. On the Linux platform, if you will be starting arserverd as a non-root user, make sure that the "open files" limit of the shell is set to 16384.
  7. When installing other BMC applications as a non-root 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

Follow the steps given below to run a remote installation on a UNIX computer:

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

Note

If you do not have the X Windows client, use the silent installer .

Assigning a temporary directory

Note

Due to installer framework changes in 8.1.02, this requirement is not valid from 8.1.02 and onwards.  

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.

Note

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 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 in previous versions. To install on a headless computer, use a remote X Windows session or the silent installation process.

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 find operating system configuration issues in installing directly from a DVD. In some cases, the DVD mount might cause long file names from the DVD not to work.

Preparing to install on Red Hat Linux 6.x

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:

  1. Install the following 32-bit RPM packages so that user interface support is available for the installer:
    • 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
  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 under the /usr/lib folder.
  4. Start the rpcbind process with -ioption:

    # service rpcbind stop
    # rpcbind -i
    # service rpcbind status
  5. Install the AR System server.
  6. 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 the "Setting ulimit before installing BMC Remedy ITSM" section below.
  7. 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

Preparing to install on Red Hat Linux 7.x

Install the following 32-bit RPM packages so that user interface support is available for the installer: 

  • libXtst.i686  

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 /etc/security/limits file for the user running the installer. This ensures that the installer will not fail due to data segment size or core file size when the installer runs the arStart.sh from a shell window.

If you are installing the BMC Remedy AR System server for AIX with Oracle, the BMC Remedy AR System server installation files must reside on a local file system and not on a network file system.

Setting ulimit before installing BMC Remedy ITSM

Before you install BMC Remedy ITSM, set the size of physical memory or the number of file descriptors. For example:

For AIX, ulimit -n unlimited
For Red Hat Enterprise Linux, ulimit -n 20000 

Launch the installer with the setup.sh script. This script, which is located in the Disk1 folder, implements a ulimit check to prevent the install from failing.

Using kernel tuning to increase transactions and users

Before you install the BMC Remedy AR System server, consider increasing the value of kernel parameters that affect the BMC Remedy AR System server (or any other multi-threaded 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 logins (client or browser), the Email Engine, and custom APIs.

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

Related topics

Installing silently
Accessing the Mid Tier Configuration Tool

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.

Comments

  1. Stefan Hall

    Hello,

    please, can you elaborate the 2nd task under "Preparing to install as a non-root user" for our db administration. We live in a high security environment and rights for a nonroot user like dba are very critical.

     "Make sure that the non-root user belongs to a group that has database access (For example, the dba group)."

    We still need to have several things clarified,

    • Does it applies for all db types, specially oracle?
    • which database access is meant? The communication is managed over ARAdmin as a DB user between ARS and DB, not on unix level.
    • is this requirement only for installation process or is it a permanent requirement for a nonroot environment?
    • which rights are meant - read, write, execute?
    • if it is for oracle client libraries, is it only for any special files or folders?

    Best Regards
    Stefan

    Nov 20, 2013 06:43
    1. Hemant Baliwala

      Hi Stefan, 

      Thanks for your comment. I have updated the doc to answer your queries.

      Make sure that the non-root user belongs to a group that has database access (For example, the dba group).

      • This step is valid for all the database types.
      • You must do this only for installation. 
      • You must add the user to the group which has read, write, and execute permissions.
      • For Oracle client libraries, you must give access to the Oracle client Home  and Oracle server Home directory.

      Hope this helps. 

      Thanks, 

      Hemant

      Nov 21, 2013 04:41
      1. Stefan Hall

        Hi Hermant,

        thanks for clarification.

        Write access is very critical for us. Can you elaborate what the installer exactly does? My dba fears parameter changes or login as sysdba.

        Best Regards
        Stefan

        Nov 21, 2013 05:13
        1. Hemant Baliwala

          Hi Stefan, 

          Sorry for not making this clear earlier. 

          You must add the user to the group where database is installed and give the user read, write, and execute permissions to access the database file system.

          Thanks, 

          Hemant

          Nov 21, 2013 05:23
          1. Stefan Hall

            Hi Hermant,

            I'm afraid, the information is good but is not enough for our security team.

            I have understood that the installer need access to unix filesystem (database files and folders like oracle_home) and don't use the rights to manipulate the db directly. That's sounds very good.

            Write access for db section under unix is another level. Why unix write permissions are needed. What files will be modified or created during installation.

            Regards
            Stefan

            Nov 21, 2013 05:49
            1. John Stamps

              Hi Stefan (and Hemant),

              Let me add my $.02 here. You are not the first person to ask this from BMC. Cloud admins want similar information and I tried to create a comprehensive list of permissions required for Linux installs (CLM only supports Linux for now). 

              https://docs.bmc.com/docs/display/public/clm31/Permissions+required+for+Linux+installations

              But I still see that my list only begins to answer your database questions. We also have another topic:

              https://docs.bmc.com/docs/display/public/clm31/Database+requirements

              See especially the Oracle Linux section:

              https://docs.bmc.com/docs/display/public/clm31/Database+requirements#Databaserequirements-OracleOraclerequirementsforLinux

              Maybe Hemant and I can work together to fill these holes in our documentation. Especially the question you raise – "Write access for db section under unix is another level. Why unix write permissions are needed. What files will be modified or created during installation."

              Your security really just needs a lucid explanation from BMC why UNIX write permissions are needed by our installer, yes? Do you really require a list of all files? Can we just provide pointers to directories? I ask this because BMC has a lot of products that are built on the AR System and I imagine our installers touch a lot of files. 

              There is not a wrong answer here, Stefan. I'm just trying to understand what you're asking for! And we might have to pull this information together in stages, as we move up the stack. But certainly pulling together the AR System permissions would fill a very big gap in the documentation. 

              Sincerely,

              John

              Nov 21, 2013 07:43
              1. Hemant Baliwala

                Thanks John!

                For now (I think) Stefan's query is addressed. But then yes let's work towards filling up these gaps. 

                Thanks, 

                Hemant

                Nov 21, 2013 07:55
            1. Hemant Baliwala

              Hi Stefan, 

              I just took this up with the architect over here. This is what he has to say.

              For Oracle, give read and execute permission for database client directory for the user with which AR Server installation is going to be performed.

              You need to give permissions to database client directory and all its subdirectory and files.

              Also, DBA group is nothing but has permissions to file systems containing Oracle client/libraries

              So you are giving permissions to file systems not to database. And these permissions are valid on for the client machine and not for the DB server.

              Also, DBA permissions are not same as the DBA role. What is expected is DBA permissions and not DBA role.

              These changes are not reflected in the docs as yet. 

              I hope this helps. 

              Thanks, 

              Hemant

              Nov 21, 2013 07:54
  2. Stefan Hall

    Hi John and Hemant,

    thanks for your informations. I have reading them all (smile).

    @john
    https://docs.bmc.com/docs/display/public/clm31/Permissions+required+for+Linux+installations

    For "BMC Remedy Mid Tier" are root permissions required "Install as root". Can you explain why, please? In our environment tomcat is nonroot.

    @john, @hemant

    The following both bullets from article are difficult for me

    • You must add the user to the group where 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  and Oracle server Home directory.

    Hemant wrote "for Oracle, give read and execute permission for database client directory" that's ok for our security team but the information above shows read, write(warning) and execute permissions. If write permissions are required to the Oracle client path, then I need exactly information where, why and what will be written.

    Thank you very much and greetings

    Stefan

    Nov 27, 2013 04:53
    1. Hemant Baliwala

      Hi Stefan, 

      My response (comment) answers your specific query related to Oracle. 

      Regarding what is there in the topic, I am working with the team here to get information right for Oracle, DB2, Windows and others. 

      For now please go with my response for Oracle. 

      Thanks, 

      Hemant

       

      Nov 27, 2013 05:45
  3. Debasish Hazarika

    Hello,

    Setting ulimit -n to unlimited can potentially break a unix system. I had this experience first hand when I set the ulimit -n option unlimited in a Redhat 6.6 system.Once I had set it and exited the console, I could no longer log into the console. Had to go thru Redhat recovery mode to correct this.

    If you don't set ulimit -n  the ITSM installer throws the following error message:

    "An insufficient ulimit value for open file descriptors has been detected on <server name>. Change the value to 20000 before continuing the installation".

    So if a hard limit of 20000 can be set on the ulimit -n option why does the document says it needs to be set to unlimited?

     

     

    Jan 07, 2016 05:31
    1. Poonam Morti

      Hi Debasish,

      I will verify this with the SME and get back to you.

      Thanks,

      Poonam

      Jan 07, 2016 11:21
    1. Poonam Morti

      Hi Debasish,

      Thanks for bringing this to notice. I have updated the topic.

      Thanks,

      Poonam

      Jan 14, 2016 03:27
      1. Debasish Hazarika

        OK, Thank you!!

        Regards,
        Debasish Hazarika

        Jan 14, 2016 09:52