Red Hat Docs  >  Manuals  >  Red Hat Applications  > 

Red Hat Enterprise Web Application Framework Installation Guide
PrevNext

Chapter 3. Installing the Binary Distribution

The Red Hat Enterprise Web Application Framework is primarily distributed in two formats, RPM and ZIP. The RPM installation has the advantages of automatically registering all of the software with RPM databases (enabling version tracking, dependency tracking, and package removal) and also requires less configuration. The ZIP package should be used for installations on operating systems without RPM support, such Solaris and MS Windows®.

RPM Installation

TipTip
 

If you are installing Red Hat Enterprise Web Application Framework 5.0, the names of your RPMs will be ccm-core-cms-* instead of ccm-core-*.

  1. Download the following RPMs:

    • ccm-core-5.x.y-z.noarch.rpm — the binary distribution of WAF.

    • ccm-core-servlet-servletname.rpm — the servlet configuration package.

  2. As the root user, install the WAF and CCM-servlet-x RPMs. You will need to install these RPMs on the same line since there is a circular dependency between the WAF RPM and the CCM-servlet-x RPM. The command will look like:

    $ rpm -ivh ccm-core-x.y.z-a.rpm ccm-servlet-x-y.z.a-b.rpm

  3. The servlet RPM will create a configuration file in /etc/ for WAF. The name of this file is package-name.cfg-servlet-container-name (for example ccm-core.cfg-resin). Copy the configuration to a new file called /etc/ccm-core.cfg so that the values you enter will not be overwritten by subsequent upgrades.

    NoteNote
     

    The ZIP build equivalent of ccm-core.cfg is system.conf.

  4. Edit the values in the new configuration file you created (/etc/ccm-core.cfg) to match your system installation. See the the section called WAF Configuration section for important information about the configuration file.

  5. Make any other changes specific to the servlet container that you are using. See the the section called Servlet Container Configuration section for details.

  6. As root, execute the command:

    /usr/sbin/package-name-configure.pl /etc/package-name.cfg

    For example, to configure the ccm-core-cms package, execute:

    /usr/sbin/ccm-core-cms-configure.pl /etc/ccm-core-cms.cfg

    This script will generate the appropriate configuration files for the servlet container you are using.

  7. It is assumed that a DBA has already created an appropriate tablespace, or set of tablespaces, and an appropriate db user (to match what you have in system.conf). You should also have the DBA load the schema, unless you have permission to do this yourself.

    The source file for loading the schema in ccm-core is:

    ccm-cms-5.x.y-z/dist/WEB-INF/sql/ccm-core/oracle-se/kernel/core-platform-create.sql

    If you are loading the CMS, the files you need to load (in this order) are:

    • ccm-cms-5.x.y-z/dist/WEB-INF/sql/ccm-core/oracle-se/kernel/core-platform-create.sql

    • ccm-cms-5.x.y-z/dist/WEB-INF/sql/ccm-cms/oracle-se/content-section/cms-create.sql

    For Red Hat Enterprise Web Application Framework 5.0, there is a single file that must be loaded for the schema:

    ccm-core-cms-5.0.y-z/dist/WEB-INF/sql/ccm-core-cms/oracle-se/kernel/core-platform-create.sql

  8. Next, start your server. The first time the server starts up, WAF will automatically populate the data with various parameters, so the initial server startup will be longer than on subsequent restarts

TipTip
 

In a multiple server installation, start the first server and make sure the initialization has finished completely (it will serve pages) before starting it on the second server.

PrevHomeNext
Installation Checklist ZIP Installation