 |
Installation and Configuration |
| |
Installation and Configuration |
This is not an end-user installation procedure. End users only need a web browser or a mobile phone to access a Tolven server. Tolven maintains a demo system at http://demo.tolven.org which you may find sufficient for a functional evaluation of Tolven.
This procedure is appropriate for both binary installations and what Tolven calls a "developer installation" which is for someone that wants to build and possibly customize Tolven from source code in CVS.
In addition to installation-specific tasks, this document provides some background information on the operational capabilities of Tolven including configuration parameters. A number of post-installation tasks are also included.
To ensure a successful first install of Tolven, you should follow the instructions as written including using exact file location, password, and configuration option suggestions. Once installed and working, you can make changes as needed.
Previously, IzPack was optional. Now, it is required. This allows the deployment process to be identical to the installation and configuration of the Tolven binary kit. We've changed the kit so that IzPack is bundled so you don't need to install it separately.
The steps needed to create and deploy SSL credentials is now taken care of by the GUI-based config tool. The ant tasks stage-init-all, deploy-from-stage, and others have been removed.
Previously, installation for developers was significantly different from the binary installer. The procedures now share many common elements with just a few extra steps needed by developers.
A tolven installation involves installing a database server, an LDAP server, and a Tolven Application Server. All three can be installed on a single Windows box. Java, PostgreSQL and openLDAP have installation kits for other platforms. The java-based components such as JBoss and Tolven are platform independent.
Windows note: This installation will only work on an NTFS file system, the older FAT does not have the security features needed by some of the components. Other operating systems should not have a problem. Although not recommended, Tolven can also be installed on XP Home for non-production purposes.
Linux note: openLDAP and PostgreSQL come pre-installed on many Linux platforms. You should not have to install those products again. If your Linux platform comes with Java 1.6 or later, you do not need to install it again either. The tolven installation tasks usually separate the generic component installation steps from steps that customize the component for Tolven. Therefore, you can usually skip the installation step if that component is already installed.
When editing ant-build.properties with directory and file names, Ant always wants forward slashes. Ant will then determine how to present the slashes, forward or back, to the operating system based on platform.
Prior to installation, all the download files occupy less than 300MB of disk. The installed products require about 620MB. So a safe amount of disk to work with that won't require shuffling is about 1GB.
Tolven can be installed on a modest configuration of 512MB and ~1Ghz CPU, even a laptop. However, performance will suffer. As a database application, Tolven benefits from the database server having fast disk IO including 10,000RPM or faster drives, SCSI controllers and of course plenty of memory, 1GB per CPU or greater is recommended. Moving the database to a separate server on a dedicated high-speed LAN will help as the load increases. LDAP can also be on a separate box but that probably won't help much unless you're expecting a very large number of logins.
Multiple instances of the Tolven application server can be deployed in both a clustered and non-clustered configuration. However, for the initial installation, we suggest that you just use a single application server.
For security purposes, postgreSQL must run under a non-privileged (non-root) system user. PostgreSQL will create the operating system user account for you but you should never have to log into that account. For this installation procedure, accept the default username of postgres with a password of postgres. You should not have to log into that account.
Remain in your own administrator (root) account to perform the installation. You can either create a new account or use your existing personal account if you prefer, as long as the account has administrator permission.
Decide which task in the following list is most appropriate to you goal. When you open a task, the individual steps are listed down the left. You should complete each step, in order and complete each step in that list.
Task: New Tolven Binary Installation on Windows
This task assumes that this is the first time install for Tolven. The binary kit is downloaded from Sourceforge. The Tolven application server, database server, and LDAP server are all located on the same system.
Task: New Tolven Binary Installation on Linux
This task assumes that this is the first time install for Tolven. The binary kit is downloaded from Sourceforge. The Tolven application server, database server, and LDAP server are all located on the same system. You can later extend the configuration to multiple systems.
Task: Update Tolven Binary Installation on Windows
This procedure assumes that there is a Tolven installation on the target Windows system and that a new version of the Tolven Binary download is to be installed. The cofiguration will not be changed by this procedure. The Database and LDAP servers will remain operational during this procedure.
Task: New Tolven Developer Installation on Windows
This task assumes that this is the first time install for Tolven. The binary kit is downloaded from Sourceforge. The Tolven application server, database server, and LDAP server are all on the same system.
The beginning and ending of the developer installation and configuration is identical to installing the binary kit. The difference in the developer installation procedure is that you will install Eclipse (or an IDE of your choice), download source code from CVS on Sourceforge and create your own kit.
This type of install puts you in synchronization with the Tolven development team. However, unless you have write permission to CVS, you will not be able to commit source code changes back to CVS. See Creating a Patch File if you want to submit a change to Tolven source code.
The installation steps are described as if Eclipse is the IDE being used, but since Tolven has no specific dependency on Eclipse, you may use any other Java development environment you wish. We recommend that you use Eclipse for the first time through.