Set up the CollabNet SourceForge Enterprise 5.1 environment

Before installing the CollabNet SourceForge Enterprise 5.1 application, make sure the system where it will run has the right software.

1. Stop sendmail.
   • service sendmail stop
   • chkconfig sendmail off
2. Use the environment checking utility to identify any sofware that won't work with CollabNet SourceForge Enterprise 5.1.
   • cd /usr/local/csfe-install/csfe-install-5.1.0.0.126.i386-redhat-5
   • ./environment_check.sh
   The environment checking utility lists all the packages present that do not exactly match the versions required for CollabNet SourceForge Enterprise 5.1.
   You get two kinds of feedback:

   • Messages labeled WARN indicate conflicts that you must fix before installing the application.
   • Messages labeled INFO, without a corresponding WARN message, refer to conflicts that the installer can take care of automatically. You may want to note these messages, but you don't have to do anything about them.
3. Resolve any conflicts the environment checking utility reports.
   • If your site is running on a dedicated machine, just remove all conflicting packages with the rpm -e <package_name> command. When you run the installer, any missing packages will be installed for you.
     Tip: For some packages, you may need to use the --nodeps option.
   • If other applications running on the machine may be affected, you must resolve the package conflicts case by case. Do whichever is appropriate:
     • Delete the conflicting package.
     • Upgrade the conflicting package to the version that the environment checking utility specifies.
   Important: When you clear conflicting packages, check for all variations of each package. For example, if you remove subversion-1.2.3.x86.rpm, you must also remove subversion-devel-1.2.3.x86.rpm, if it is present.
4. Run environment_check.sh as many times as needed, until no conflicting packages (WARN messages) appear.
   Tip: If you need help resolving any conflict, contact your CollabNet support representative.
   Important: Do not proceed with the installation until all package conflicts are resolved.
5. Run the installer.
   • ./install.sh --all --directory <SITE_DIR> -V | tee /tmp/install.out 2>&1
   install.sh re-checks for the necessary software and installs any missing rpms for you.