3.6. Obtaining Red Hat WAF and Application Packages
This is the list of packages for WAF and Red Hat Applications built on top of WAF which you will need to obtain prior to installation and configuration. For RPMs, add the .noarch.rpm suffix to all package names; for ZIPs, add .zip suffix.
3.6.1. Required WAF Packages
The following packages are required for all installations:
The main WAF package: ccm-core-version.
The tools package ccm-tools-version.
The appropriate servlet package, either ccm-tools-servlet-resin-version or ccm-tools-servlet-tomcat-version.
Note You should only install one of the two ccm-tools-servlet packages. If you have more than one installed, you will need to set CCM_SERVLET_CONTAINER depending on which servlet you wish to use.
The servlet-versionis required. This is explained in Section 3.5 Other Third-party Packages.
The following packages may also be needed, depending on use:
ccm-devel-version, required for the development environment
ccm-scripts-version provides the ability to build RPM or ZIP packages for custom applications.
3.6.2. Application Packages
Each WAF application ships in one or more packages that need to be installed on top of WAF.
If installing CMS, you will need the main CMS package ccm-cms-version. In addition, you will need to install the individual content type RPMs for any content types you need. Available content types are:
Address: ccm-cms-types-address-version
Agenda: ccm-cms-types-agenda-version
Event: ccm-cms-types-event-version
FAQ Item: ccm-cms-types-faqitem-version
File Storage Item: ccm-cms-types-filestorageitem-version
Glossary Item: ccm-cms-types-glossaryitem-version
Job: ccm-cms-types-job-version
Legal Notice: ccm-cms-types-minutes-version
Minutes: ccm-cms-types-minutes-version
MOTD Item: ccm-cms-types-motditem-version
News Item: ccm-cms-types-newsitem-version
Organization: ccm-cms-types-organization-version
Press Release: ccm-cms-types-pressrelease-version
Related Link: ccm-cms-types-relatedlink-version
Service: ccm-cms-types-service-version
If installing Portal Server, you will need ccm-portalserver-version.
If installing Bookmarks, you will need ccm-bookmarks-version.
If installing Doc Manager, you will need ccm-docmgr-version.
If installing FAQ, you will need ccm-faq-version.
If installing Forum, you will need ccm-forum-version.
If installing Glossary, you will need ccm-glossary-version.
3.6.3. Obtaining Packages Through Red Hat Network
If you are installing directly from RHN, you will download and install the packages in one action. This is covered in Section 6.1.1.3 Installing WAF Applications via RHN. If you want to obtain the packages separately from installing them, follow the procedure below.
Package Downloading Procedure
Using your enterprise account or evaluation access, subscribe your system to the Red Hat Web Application Framework 6.1 channel on RHN. Also, subscribe your system to any other channels of Red Hat Applications software that you are using, such as Red Hat Content Management System 6.1. To obtain these entitlements, contact your Red Hat account manager. When available, the packages should appear in the Software tab. For more information about how to use RHN, see https://rhn.redhat.com/help/.
There are two methods for obtaining your packages:
Use up2date to download and not install your packages. This command will download those packages into /var/spool/up2date, where up2date will later pick them up for installation. To install in one action, remove the -d option.
up2date -d <list_of_packages>
Download the ISOs:
Log into your account at http://rhn.redhat.com/.
Select Software.
Select Easy ISOs and download the Red Hat Applications ISO(s) that you need. There is a separate ISO for each product.
Note You can use RHN to obtain the IBM Java 2 JDK from the Red Hat Enterprise Linux channel. You will want to be sure you have the zip and rpm-build packages installed.
up2date -d zip rpm-build IBMJava2-SDK