Open.ControlTier > ModuleForge
 

Install

Overview

This document describes the installation steps necessary to use the library.

Step #0: Prepare for installation

This module library has been tested to support a broad range of platform technologies and application topologies, far beyond the scope of this documentation to cover comprehensively. In general, you can assume that the library supports all major releases of the Apache Tomcat servlet container and the JBoss application server deployed both Linux/Unix and Windows servers. Additionally, a number of common database servers (e.g. MsSQL and Hypersonic SQL) are supported.

In order to document the journey to a working solution from a "standing start", this documentation follows a tutorial approach, aiming to:

  • Deploy both the Duke's Bank J2EE sample application (from Sun's J2EE 1.4 Tutorial) and the Apache Tomcat "Hello, World" sample application to a single box.
  • Duke's Bank is to be built and deployed to the JBoss application server running on either a Windows or Linux system.
  • The Duke's Bank data will be stored in an stand-alone Hypersonic SQL database system (external to JBoss).
  • The "Hello, World" application is built and deployed to the Tomcat application server running on either a Windows or Linux system.

Specifically, then, for this demonstration of the module library the following software versions are required:

  • JBoss 4.0.3sp1
  • Hypersonic SQL Database 1.8.0.9
  • Tomcat 6.0.14
  • Ant 1.7.0
  • Cruise Control 2.7.1
  • CentOS release 4.5 (Final), or Redhat Enterprise Linux 4 update 2 or better, or ...
  • Windows XP Professional SP2, or Windows 2003 Server R2 (and possibly other Windows versions though they haven't been tested)

In addition, the availability of the following tools in your general environment is assumed:

  • JDK 1.5.0
  • Subversion 1.1.4, or later
Note
In order to follow the tutorial, it is assumed that the machine(s) you choose to install on have access to the Internet to checkout demonstration source using Subversion from Sourceforge.
Note
In order to run the entire set of services of the sample applicatins on a single box (or virtual machine instance), you'll need around 4GB of disk space and 1024MB of memory. A three to six box configuration with separate server, build, and development and staging application server and database server systems can be run with virtual machines assigned 256-512MB of memory each and at 500MB of free disk space (1.5GB on the ControlTier server).

Step #1: Install the ControlTier platform software

This library assumes you have installed the latest stable release of the ControlTier 3.2 framework software (at least 3.2.1) on a designated server host and one or more client hosts. Refer to the general installation procedures for more info.

You will need to know the URL to the Workbench and JobCenter applications.

Note
The module library has been tested using JDK 1.5.0 with the ControlTier framework
Note
If you plan a multi-box installation be sure up update the "server.tomcat.hostname" and "client.hostname" properties in the "default.properties" command-line installer configuration file to appropriate network host names (these are also settable options in the GUI installer).

Step #2: Choose or create a project

All work is done within the context of a "project". Under ControlTier 3.2, a project called "default" is setup out of the box, and this documentation assumes that you are using it. However, you may already have a particular project in mind, or you may wish to create a new one just for the use of this library.

Note
If you are new to ControlTier and are not sure about projects see the Projects section in the ProjectBuilder tutorial.
Note
If you are building a multi-box environment, this is the moment to register your client nodes with the new project using "ctl-depot"

Step #3: Download the library archive

Binary distributions of the module library can be found in the "File Releases" section of the ModuleForge Download page on Sourceforge. The package is called "Elements Module Library" and will be named something like: elements-x.y-seed.jar where "x.y" denotes the version.

You must download the latest release of version 3.2 of the module library.

Step #4: Load the library archive

Once you have chosen the desired project, you can load the library into that project.

Be sure you have already logged into Workbench and selected the desired project where you want the library loaded. If you just created a new project, you are all ready.

  1. Navigate to the Admin page. (eg., go to the URL: http://localhost:8080/itnav/do/menu/Admin
  2. Press the "Import Seed" button. (eg., go to the URL: http://localhost:8080/itnav/do/projects/ImportSeedInput
  3. Locate and select the elements-x.y-seed.jar file in the file chooser. This is the same file you downloaded in step #2.
  4. Press the "Import" button.
Note
It takes a few minutes for Workbench to load the library.

Once the library has been installed into your chosen project the next step is to configure these modules for use.

Next: Configure →