Installing additional software required by Kronodoc

Additional software required by Project Portal is packaged in the latest Project Portal RPM package. Installation of the package must be done as the root user. Back up the /opt/kronodoc directory before running the infra installation as in some cases the old contents of that directory. Backup can be done by just copying the directory to another name.

If you have registered your system to Red Hat and have an Internet connection, install using yum:

yum install –-nogpgcheck "<RPMPackagePath>"

If you are offline, you need to install the package either by adding the RHEL installation DVD as a yum repository or with rpm. Installing an infrastructure package using rpm is discouraged as it will require handling the package dependencies manually.

Using rpm you should install using command:

rpm –ivh "<Paths to all required packages separated by spaces>"

Installation of the RPM package performs the following tasks:

• Creates the kronodoc user (and group) if not already available. If it creates kronodoc user, it sets its default shell to /bin/false. In order to login as the kronodoc user, the system administrator needs to update the default shell to bash and assign a password to the user
• Creates the /opt/kronodoc directory if not already available
• Installs the perl interpreter under /opt/kronodoc/perl/
• Installs the Java runtime environment under /opt/kronodoc/java/
• Installs the additional Apache web server modules under /opt/kronodoc/apache/
• Installs the Oracle 11g instant client under /opt/kronodoc/oracle11g/
• Installs the testKrono2012ServerSetup script under /opt/kronodoc/bin

If several Project Portal installations reside on the same server, you need to create a user account for each of the installations. All user accounts must have access to the required infrastructure packages and therefore are recommended to belong to the same group (kronodoc).