Chapter 9. Development Installation for WAF

9.1. Installing WAF Packages

9.1.1. Installing Infrastructure Packages

9.1.1.1. Installing Infrastructure RPMs

Obtain the appropriate packages. The packages required for installation are discussed in Section 3.6 Obtaining Red Hat WAF and Application Packages. For RPM-based systems, install all RPMs using the rpm -ivh. For example:

rpm -ivh servlet-version.rpm
rpm -ivh junit-version.rpm
rpm -ivh junitperf-version.rpm
rpm -ivh httpunit-version.rpm
rpm -ivh ccm-tools-version.rpm
rpm -ivh ccm-core-version.noarch.rpm

# if you use Tomcat as the servlet container
rpm -ivh ccm-tools-servlet-tomcat-version.noarch.rpm

rpm -ivh ccm-devel-version.rpm

# if you will be building RPMs or ZIPs for custom applications
rpm -ivh ccm-scripts-version.rpm

TipTip
 

You may experience problems using rpm version 4.1x, especially trying --relocate. If that happens, try versions 4.0x or 4.2x of rpm.

9.1.1.2. Installing Infrastructure ZIPs

Obtain the appropriate packages. The packages required for installation are discussed in Section 3.6 Obtaining Red Hat WAF and Application Packages. For ZIP-based installs (Windows and other non-RPM systems), unzip the following ZIP files. On Windows, unzip the packages from the directory C:\ccm. Subsequent instructions will refer to CCM_ZIP_ROOT, which will default to C:\ccm. Be sure to set this environment variable if unpacking the ZIP files in an alternate location.

9.1.2. Installing Application Packages

Download and install the appropriate application packages. The various application packages are discussed in Section 3.6 Obtaining Red Hat WAF and Application Packages. If you will be modifying any of the Red Hat Applications packages as part of your deployment, you will need to use the equivalent source ZIP file instead of the deployment RPM or ZIP package.

For a given application package in the form packagename-version-build.noarch.rpm or packagename-version-build.zip, the source ZIP will be packagename-version-build-src.zip. The application will be maintained as a custom application, alongside any other custom applications.