Preparing Red Hat Enterprise Linux Systems

You must prepare the systems on which you plan to install Emptoris applications by providing sudo permissions, creating users, creating directories, and other required steps.

Before you begin

Ensure the following checks for successful installations of Emptoris applications.

  • In the /etc/sudoers file, comment the Defaults requiretty line. If this command is kept active, the[wsadmin] sudo: sorry you must have tty to run sudo error occurs during installation.
  • disable SELinux
  • Ensure that the Apache mod_ssl module is installed for the PWS. If it is not installed, use yum install mod_ssl to install it.
  • To install the HTTP Proxy module and enable the built-in test perimeter web server, add the path to your Apache installer file to your sudoers configuration for the emptoris user. For example, add /usr/sbin/httpd or /usr/sbin/httpd.worker. The HTTP Proxy module uses httpd.worker instead of httpd when the worker MPM is installed. If you do not add the path, errors occur when you are trying to automatically start or stop the HTTP Proxy module on Linux environments.

Procedure

To prepare a system for installation, complete the following steps:

  1. Create emptoris user.
  2. Create emptoris group.
    Attention: You must use the emptoris user and group for installation. Validation errors might occur if the emptoris user and group are not used for installation.
  3. Assign the following sudo permissions to the emptoris user. 
    emptoris ALL=NOPASSWD: /sbin/service, /bin/rm, /bin/mkdir,
/usr/bin/unzip, /bin/cp, /usr/sbin/apachectl, /bin/kill, /bin/ln,
/bin/chmod, /bin/chown, /bin/chgrp, /opt/IBM/WebSphere/AppServer/java/bin/java,
/opt/IBM/WebSphere/AppServer/bin/wasservice.sh, /usr/sbin/chkconfig

    Depending on your distribution, the paths to the above standard utilities might vary. You can use the 'which' command to locate the correct path. The path to the wasservice.sh script depends on your WebSphere Application Server installation.

    Note: Configure the sudo permissions for the emptoris user so that no password and no TTY is required during the installation. After the installation is complete, you may restore the requirement of password for the user.
  4. If you do not give sudo permissions to the emptoris user, complete the Prerequisites for Installing Emptoris Products with Non-Root User.
  5. If you want to use the emptoris user, reset the password for the emptoris user.
  6. Log on as emptoris user.
    Note: For Emptoris® Spend Analysis, the group ID of the emptoris group and user ID of the emptoris user on the database server must sync with the group ID and user ID of the VM node on which the primary and reporting servers will be installed. OLF jobs fail if these group and user IDs are not synced with each other.
  7. Ensure that the WebSphere Application Server Java path is set.
  8. If you are using the system as the Emptoris HTTP Proxy, install the Apache HTTP Server.
  9. For Emptoris Strategic Supply Management Platform, create a directory outside the WebSphere Application Server directory called SSM_Home, and make the emptoris user the owner of this directory.

    This directory will contain attachments, batch upload temporary files, logs, and any other file-based data. While installing the Emptoris Strategic Supply Management Platform, specify the location of the ssm_home directory in the Home Directory field.

  10. For Emptoris Supplier Lifecycle Management, create two directories: one for logs and one for attachments.
  11. For Emptoris Contract Management, create a directory for attachments and templates.
  12. For Emptoris Contract Management reporting, complete the following steps.
    1. Create a directory on the Cognos server as the home directory.

      This is the Cognos Model Home directory.

    2. Create a directory on the InfoSphere DataStage server as the projects directory.
  13. Assign ownership for these directories to the emptoris user.
Parent topic: Red Hat Enterprise Linux Systems