Chapter 7. Installing WAF for Development

This section contains instructions on how to compile WAF applications from the WAF development RPMs or ZIP distributions. The WAF development environment has everything you need to write Java webapp code, test it, view the results, and deploy your finished code to a production environment. This section will give you enough information to go through this entire process, provided you have:

  1. Experience writing Java and using the WAF APIs; this is not a guide to writing WAF code;

  2. Experience developing in a UNIX® environment. While it is possible to develop WAF code in this environment using a Java IDE, this guide does not cover that situation.

The entire development environment works together to configure your server, handle version control, and provide a set of tools and aliases to help you speed development. These features include:

  1. Automatic setup of multiple development environments for different developers on the same project, or even different developers working on multiple projects.

  2. Automatic creation of server startup and shutdown scripts for each developer on each project, and automatic assignment of distinct port numbers for each developer on each project.

  3. Easy upgradability of existing code base. Upgrading the WAF release your project is based on is as simple as obtaining a new WAF RPM/ZIP, installing it with a single update command, generating new configuration files, and deploying. The same goes for servlet container code, build code, and so on.

7.1. File Installation

Before you begin, you should review Chapter 2 Preparing Your System For Installation.

7.1.1. RPM Installation for Development

You will need the following RPMs to install the WAF development environment. Version numbers will change; the version numbers listed below are for example only. In general, Red Hat Network should be used to manage your RPMs, and the appropriate versions of the software will be installed on your software.

The following lists the RPMs in the order they should be installed:

  • These set up the bare development environment, with no underlying project code:

    1. ccm-config-1.1.2-1.noarch.rpm

    2. ccm-devel-1.2.3-1.noarch.rpm

  • This is the code base and documentation you will be developing on top of -- you may be using a different version or an entirely different RPM, depending on the project you are developing.

    1. ccm-core-devel-6.0.0-1.noarch.rpm

    2. ccm-core-doc-6.0.0-1.noarch.rpm (The doc RPMs are optional, but are recommended if you want local access to the Javadoc for your code base. Note that the build system will also generate javadoc for you.)

    3. ccm-cms-devel-6.0.0-1.noarch.rpm

    4. ccm-cms-doc-6.0.0-1.noarch.rpm

7.1.2. ZIP installation

The ZIP format packages the entire development environment into one ZIP file.