Discard0

From DOC

INSV0_20110218

All other trademarks are the property of their respective owners.

This guide presents an enterprise installation procedure that includes multiple steps, most of which can be customized for a specific environment. We strongly recommend that you follow the default/recommended installation steps the first time you install the Tolven Platform (Tolven). After your initial default installation, you can then consider making changes.

Click Printable version in the navigation pane to the left to print a copy of this guide before you start.

CR/LFs in Code Samples
Carriage Return/Line Feeds were added to some code samples for the sake of formatting when you print this guide:

If you are copying and pasting code from this guide to the command line, be aware that those CR/LFs may carry over.

Related Documentation
If you intend to use the Tolven Platform Web Services API, after following the instructions in this Installation Guide, see the Configuring Tolven V2 Web Services Tech Note for instructions.

Installation Checklist
Use this installation checklist to help keep track of the progress of your installation.

Installation Step	Installation Sub-Step	Completed?	Notes
Step 1 - Install Prerequisite Software	1.1.1 Download & Install Java
	1.1.2 Verify Java Installation
	1.1.3 Verify JAVA_HOME Setup
	1.2 Install Database
	1.2.1 Install PostgreSQL
	1.2.1.1 Install PostgreSQL on Windows		Port #: Username: Password:
	Install phpPgAdmin Tool
	1.2.1.2 Install PostgreSQL on Linux		Port #: Username: Password:
	1.2.2 Install Oracle
	1.2.2.1 Create a Tolven User
Step 2 - Install OpenLDAP	2.1 Download & Install OpenLDAP on Windows		Port #:
	2.2 Download & Install OpenLDAP on Linux		Port #:
	2.3 Download & Install JXplorer
Step 3 - Install JBoss Application Server	3.1 Download the Tolven JBoss Zip File
	3.2 Unzip & Install the Tolven JBoss Zip File
	3.3 Download & Install JDBC Driver
	3.4 - Customize Log4j Messages
Step 4 - Install Tolven	4.1 Download and Unzip the Installation File
	4.2 Install the Initial Tolven Kit
	4.3 Verify Installation Kit Version
Step 5 - Configure Your Database	5.1 Configure PostgreSQL
	5.1.1 Modify pg_hba.conf
	5.1.2 Modify postgresql.conf
	5.2 Configure Oracle
Step 6 - Configure LDAP	6.1 Initially Set Up OpenLDAP for Windows
	6.1 Initially Set Up openLDAP for Windows
	6.1.2 Set Up the LDAP Database
	6.1.3 Test LDAP in non-SSL Mode
	6.2 Initially Set Up OpenLDAP for Linux
	6.2.1 Add/Modify slapd.conf Entries
	6.2.2 Configure the LDAP Database
	6.2.3 Test LDAP in non-SSL Mode
	6.3 Did OpenLDAP shut down abruptly?
Step 7 - Configure Tolven	7.1 Modify Plug-in Properties
	7.1.1 Configure LDAP Properties
	7.1.2 Configure Database Properties
	7.1.3 Configure JDBC Driver Properties
	7.1.4 Configure Tomcat Properties
	7.1.5 Configure Application Server Properties
	7.1.6 Configure Global Properties
	7.2 Set Up Environment Variables
	7.3 Initialize the Runtime Repository
	7.4 Run the Integrity Check Command
	7.5 Run Phase 1 Configuration
	7.6 Configure Credentials
	7.6.1 Configure LDAP Credentials
	7.6.1.1 Start openLDAP
	7.6.2 Configure PostgreSQL Credentials
	7.6.3 Configure Oracle Credentials
	7.6.4 Configure JBoss Credentials
	7.6.5 Configure pgadmin Credentials
	7.7 Test Database And LDAP Connections After ConfigPhase1
	7.8 Run Phase 2 Configuration
	7.9 Update MDBUser
	7.10 Test LDAP Connection Prior To Starting Application Server
	7.11 Start Application Server
	7.11.1 Test Application Server Connection After Start
	7.12 Update Database Indexes
	7.13 Update Server Properties
	7.14 Add Application Metadata to plugins.xml
	7.14.1 Add Metadata Supplied By Tolven to plugins.xml
	7.14.2 Add Custom Metadata to plugins.xml
	7.14.3 Add Vocabulary Metadata to plugins.xml
	7.15 Run repositoryInit
	7.16 Run Phase 3 Configuration
	7.17 Activate Vocabulary Plug-ins
Step 8 - Next Steps

Step 1 - Install Prerequisite Software

A Tolven installation requires that a number of prerequisite software products be installed. Later, during configuration, you will be directed how to configure these prerequisite components to work with Tolven.

After the prerequisite software packages are installed, they do not need to be changed when a new version of Tolven is installed unless specifically directed to do so in the Tolven release notes.

1.1 Install Java

1.1.1 Download & Install Java

Tolven requires Java 1.6 SE (desktop) to be installed. Java EE components will then be installed later, as part of the application server install. Tolven generally requires the latest released version.

Windows:

Install the Java JDK if it is not already installed. Tolven requires JDK version 1.6.0 or newer. You can download the Java JDK here:

JDK download site

You can install it anywhere you want, but we recommend something like the following (depending on the version):

c:\jdk1.6.0

This kit will also install the corresponding Java Runtime Environment (JRE). This is the JRE that Tolven will use. We recommend that you accept the default location for the JRE. Tolven does not use any applets or Java-based browser plug-ins.

After installing Java, the JAVA_HOME environment variable should point to this (new) JDK. You can verify this on Windows as follows:

Start > Control Panel > System > Advanced > Environment Variables

Linux:

Install the Java JDK if it is not already installed. Tolven requires JDK version 1.6.0 or newer.

JDK download site

You can install it anywhere you want, but we recommend something like the following (depending on the JDK version and your Linux flavor):

/usr/java/jdk1.6.0_10

This kit will also install the corresponding Java Runtime Environment (JRE). This is the JRE that Tolven will use. Tolven does not use any applets or Java-based browser plugins.

1.1.2 Verify Java Installation

Verify that Java is set up correctly. Execute the following from the command line:

Windows:

java -version

Linux:

which java

Verify that the version number is 1.6 or greater.

1.1.3 Verify JAVA_HOME Setup

After installing Java, the JAVA_HOME environment variable should point to this (new) JDK. You can verify this as follows:

Windows:

set JAVA_HOME

Linux:

echo $JAVA_HOME

Verify that this environment variable refers to a Java JDK (not JRE) installation.

1.2 Install Database

Install PostgreSQL or Oracle as described below.

1.2.1 Install PostgreSQL

You can use phpPgAdmin (also installed with the Windows one-click installer at the end of the PostgreSQL install) to test communication with the database.

You must download an appropriate JDBC driver and point to this driver in the plugins.xml file. This will be done later in the installation process.

1.2.1.1 Install PostgreSQL on Windows

PostgreSQL provides a one-click installer for Windows.

1. Download the latest version of PostgreSQL from the PostgreSQL Windows packages site:

PostgreSQL Windows Package Downloads

2. Double click the executable file. For example, double click:

postgresql9.0.3-1-windows_x64.exe

3. Click Next.

3. For this example, in the installation options step, no options will be changed from the default, but we will change the installation directory to the following using the Browse button and then click Next:

c:\postgreSQL\9.0\

4. Select your data directory and then click Next.

5. Enter the postgres username (postgres) and password (postgres) and click Next. This means that you will have a database named postgres and a super user named postgres. Use this default password to avoid additional steps in the configuration process.

6. Specify the port number on which the server should listen and click Next. Write this port number in your checklist.

7. Select your locale and click Next.

8. Click Next to begin installing the database. If the installation completes successfully, you should see something similar to the following:

9. Next, you will need to install the phpPgAdmin utility that you will use to start, stop, and manage your database. You can download it here:

phpPgAdmin Tool Download

10. Run the PGadminIII tool which should look like this:

This tool will allow you to start and stop the database server when the time comes and to look at the database contents. To connect to the database, provide the super user and password (postgres for the username and password).

The Postgres installation is complete. You will add some configuration later in this installation process, namely digital certificates for secure communication via SSL.

10. Now that you've had a look around the empty database, stop the database server:

1.2.1.2 Install PostgreSQL on Linux

The PostgreSQL documentation describes building PostgreSQL from source but that is not needed for Tolven. The binary kit is adequate. If PostgreSQL is not installed on your system, please following package installation guidelines for your flavor of Linux. One important note, is that Tolven assumes that you have installed PostgreSQL in the directory /usr/local/pgsql, although /var/lib/pgsql is also a well-known location. For a new installation it will be simpler to use /usr/local/pgsql. The various options are presented below. Note that no advice is given where the pgsql's data directory already exists, because it is assumed that it contains a live database.

If the original install was in /var/lib/pgsql, then step 1.2.1.2.1 With No Existing Postgres Database below can be carried out first, followed by step 1.2.1.2.2 With An Existing Postgres Database. Otherwise, only step 1.2.1.2.2 With An Existing Postgres Database is required.

1.2.1.2.1 With No Existing Postgres Database

Where there is no existing postgres database, moving PostgreSQL installed in /var/lib/pgsql to /usr/local/pgsql This assumes that PostgreSQL is already installed in /var/lib/pgsql, but there is no postgres database as yet.

The postgres home directory is likely to be /var/lib/pgsql. It can remain here, but if it's empty you can consider moving postgres home to /usr/local/pgsql. It is not absolutely necessary to do so, but just a convenience. First create the home directory and give it postgres permissions:

mkdir /usr/local/pgsql
chown postgres:postgres /usr/local/pgsql

Then execute the following to move the postgres home directory (assumed to be /var/lib/pgsql) to /usr/local/pgsql (double check that it doesn't contain more data in it subdirectories, than you want to move):

usermod -d /usr/local/pgsql postgres

1.2.1.2.2 With An Existing Postgres Database

Where there is no existing postgres database and PostgreSQL is installed in /usr/local/pgsql. The first two commands are the same as those executed in step 1.2.1.2.1 With No Existing Postgres Database, if that step was necessary.

mkdir /usr/local/pgsql/data
chown postgres:postgres /usr/local/pgsql/data

Now log in as posgres:

su - postgres

Execute the env command to see if it contains PGDATA. If not, then you can default it for the next time you log in, by creating/editing the .bash_profile in the postgres home directory, which is where you should be after executing the command above. It is not critical if the home directory is elsewhere. Add the following lines to .bash_profile for postgres:

PGDATA = /usr/local/pgsql/data
export PGDATA

If you have just edited the .bash_profile, then exit and re-execute 'su - postgres' again to pick up the changes. Check with the env command.

As the postgres user, execute the following to create the database:

initdb -E UTF8 -D /usr/local/pgsql/data

The /usr/local/pgsql/data directory should now have contents, and you should be able to start the database:

As postgres:

pg_ctl start

or, if you exit back to root, then:

su -c 'pg_ctl -D /usr/local/pgsql/data start' postgres
<pre>

Check that PostgreSQL is running by using the 'ps' command, or:

<pre>
netstat -a | grep postgres
<pre>

or

<pre>
netstat -a | grep 5432

Following the guidelines in PostgreSQL and your Linux documentation to set the server as a service.

1.2.2 Install Oracle

The database server does not need to be on the same machine as the Tolven Application Server. Installing Oracle depends on the operating system. Please consult both the Oracle documentation, and also the documentation for your operating system.

While installing Oracle, the following information will be required during the configuration of Tolven:

Server name on which Oracle is being installed (default: localhost)
Port number (default: 1521)
Database name or SID (default: ORCL)

A number of Oracle tools including Oracle SQL Developer, can be used to test communication with the database once it is installed.

1.2.2.1 Create a Tolven User

You will need to add one user named tolven which will need permission to create, populate and query tables, views, indexes, and perhaps sequences (core Tolven does not use sequences).

Step 2 - Install OpenLDAP

The LDAP server does not need to be on the same machine as the Tolven Application Server. Installation instructions for Windows and Linux are given below.

2.1 Download & Install OpenLDAP on Windows

Installing openLDAP is straightforward. We expect many Tolven installations will have an existing production LDAP. Yet for this step, you will be installing openLDAP. It will be configured to use port 636 (ldaps) and digital certificates for mutual authentication between it and the application server.

1. Download OpenLDAP for Windows from the following site:

Download OpenLDAP Windows Installer

2. Click the .exe file. The opening screen, after answering security and language questions, should look like this:

3. Click Next.

4. Accept the license agreement terms and click Next.

5. Change the openLDAP installation directory to c:\OpenLDAP as shown and click Next.

6. For the Custom Setup step, select OpenLDAP Backup Tool. DO NOT select the option to install OpenLDAP as a service. Click Next.

7. By default, LDAP is installed using the unencrypted port which you will reconfigure to be encrypted. Leave the defaults and click Next.

8. Leave LDAP checked and click Next. If the installation is successful, the final screen should look like this:

9. Click Finish.

2.2 Download & Install OpenLDAP on Linux

The installation of OpenLDAP in Linux depends on the flavor of Linux. Consult both the OpenLDAP documentation, and also the documentation for your flavor of Linux.

If all goes well, you should have a directory whose default directory is usually /etc/openldap. Preparing to start LDAP is covered in a later section.

2.3 Download & Install JXplorer

You will be configuring openLDAP later in this install process to configure the security aspects and the Tolven schema. At that time, you will need a tool that allows you to view LDAP. You can download JXplorer at the following site if you don't already have it or a similar tool:

Download JXplorer Tool

Step 3 - Install JBoss Application Server

The next step is to download and install the Tolven-customized version of the JBoss application server.

3.1 Download the Tolven JBoss Zip File

Download tolven-jboss-4.2.2.GA.zipfile from:

http://sourceforge.net/projects/tolven/files/tolven-jboss-4.2.2.GA.zip/download

3.2 Unzip & Install the Tolven JBoss Zip File

This is basically a typical JBoss distribution, with some modifications for Tolven. In previous versions of Tolven, the unzipped contents of this file were located in the tolvenVersion directory. It could always have been moved from there, but for new installations, you can choose to extract this file wherever you want. To install the specialized version of JBoss, unzip the tolven-jboss-4.2.2.GA.zip file to a directory of your choice:

unzip tolven-jboss-4.2.2.GA.zip

Note: At this point, the location of the unzipped application server is not known to Tolven. You will need to add the location of the server (known as appserver.home) to the <tolven-config>/plugins.xml file later when you have installed Tolven.

3.3 Download & Install JDBC Driver

1. Download the appropriate PostgreSQL or Oracle JDBC Driver.

Oracle:

If you are installing Tolven with an Oracle database, then you need to obtain the corresponding JDBC driver at:

Oracle JDBC Driver Download

PostgreSQL:

If you are installing Tolven with a PostgreSQL database, then download the corresponding JDBC driver at:

PostgreSQL JDBC Driver Download

2. Place the driver in the server lib directory, which by default is:

tolven-jboss-4.2.2.GA/server/tolven/lib

3.4 - Customize Log4j Messages

After you install the Application server, you are free to customize certain files. One such file, which Tolven does not touch, is the following:

tolven-jboss-4.2.2.GA/server/tolven/conf/jboss-log4j.xml

The default version of this configuration file causes log4j to display a large amount of informational messages to both the console and the server.log file. This level of output can make it difficult to detect actual errors, especially during startup.

You can fine-tune the log4j configuration, even during operation, to adjust the amount of output for selected modules.

We have provided a complete replacement for this file which dramatically reduces the amount of informational output for most non-Tolven components. All errors and warnings are still displayed. A few debug messages are also displayed.

1. Make a backup copy of the original tolven-jboss-4.2.2.GA/server/tolven/conf/jboss-log4j.xml file.

2. Right click the link below and select Save Target As to download the replacement file. Download it to the tolven-jboss-4.2.2.GA/server/tolven/conf/ folder and specify that you want to replace the version that is already in the folder.

jboss-log4j.xml

Step 4 - Install Tolven

In order to install Tolven, you must already have followed the prerequisite steps in the Installation Guide.

4.1 Download and Unzip the Installation File

The Tolven installer is shipped as a zip file and is platform-independent. It runs on both 32- and 64-bit hardware and operating systems. Download it from:

http://tolven.org/download/installer/tolven-RC1.zip.

The unzipped directory is called tolven-RC1 by default and will be referred to as the Tolven software home directory.

Windows

Unzip the tolven-RC1.zip file to the c:\ directory, for example, and the Tolven software home directory becomes:

c:\tolven-RC1

Linux

cd /usr/local
wget http://tolven.org/download/installer/tolven-RC1.zip
unzip tolven-RC1.zip

This creates the Tolven software home directory called:

/usr/local/tolven-RC1

4.2 Install the Initial Tolven Kit

This step installs the initial Tolven software, which is a bootstrap for the many plug-ins that will be added during configuration. This step also creates a tolven-config directory that contains data specific to your configuration and is not overridden from release to release.

Windows:

cd tolven-RC1\bin
install

Linux:

cd tolven-RC1/bin
./install.sh

You will be prompted for the following (default values are suggested by the installer):

The tolven-config directory (by default c:\tolven-config or /usr/local/tolven-config). If you have a previous tolven-config directory, then you would normally reuse it, in order to pick up previous installation information.

Once installed, the configuration directory (tolven-config) will not be overwritten by subsequent installations and upgrades. However, over time, many different Tolven installation directories (tolvenVersion) will be created. You may delete obsolete installations without affecting the Tolven configuration directory. We recommend that you never make changes in the installation directory.

4.3 Verify Installation Kit Version

Windows:

cd <install-dir>\bin
tpf -version

Linux:

cd <install-dir>/bin
./tpf.sh -version

Versions prior to 0.0.1 will not recognize this option, which in effect identifies them as being prior to Version 0.0.1. The version number may be useful when documentation is referring to functionality which only exists in certain versions.

Step 5 - Configure Your Database

Configure your selected database.

5.1 Configure PostgreSQL

In a later step, the Tolven configuration Manager will add SSL certificates to the postgres directory and add schemas to the PostgreSQL database. Here, you must configure postgreSQL to use SSL.

5.1.1 Modify pg_hba.conf

Use Notepad or wordpad to modify postgreSQL/version/data/pg_hba.conf to allow network access to the database. JDBC, even from localhost, requires network access to the database. Documentation is included in that file. The uncommented line should look something like this:

# TYPE   DATABASE    USER        CIDR-ADDRESS          METHOD
hostssl  postgres    postgres    127.0.0.1/32          md5

You are done with the pg_hba.conf file, although remember to change this file if you need to access postgreSQL from clients not on localhost. You can also change the TYPE from hostssl to host, which will allow connections via non-ssl clients, but this is not recommended.

5.1.2 Modify postgresql.conf

5.1.2.1 Modify postgresql.conf to Enable SSL

Next, edit the postgreSQL/version/data/postgresql.conf file so that its security configuration enables SSL.

In the postgresql.conf file this line:

# ssl = off

should be changed to:

ssl = on

(remove the # and change off to on)

5.1.2.2 Modify postgresql.conf Maximum Transactions

The postgres.conf file has a property value which can lead to a warning message:

WARN [loggerI18N] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa] [com.arjuna.ats.internal.jta.resources.arjunacore.norecoveryxa]
Could not find new XAResource to use for recovering non-serializable XAResource...

To resolve this issue, change the max_prepared_transactions property to be greater than zero. For example, uncomment and change the following:

max_prepared_transactions = 5 # zero disables the feature

You must restart the PostgreSQL server for this change to take effect.

5.2 Configure Oracle

Add a user to Oracle called tolven, which has permissions to create tables, indexes etc.

Step 6 - Configure LDAP

Note that after the configuration below, LDAP will not start, until SSL credentials are in place, and that will occur later during the configuration process. This step only needs to occur once for a Tolven installation.

6.1 Initially Set Up openLDAP for Windows

6.1.1 Add/Modify slapd.conf Entries

1. Edit the slapd.conf file in the openLDAP directory. The slapd.conf file varies over time with different versions and configurations. Below are the directives known and used by Tolven. Copy or replace the equivalent lines in the slapd.conf file of your openLDAP installation.

These schema includes below must be present. Core is usually there by default; if not, add it.

include		./schema/core.schema
include		./schema/cosine.schema
include		./schema/inetorgperson.schema

2. The next four lines allow use of TLS for encrypting connections using a self-signed test certificates. These lines will prevent the LDAP server from starting until the credentials indicated a put in place later during this configuration process.

TLSCipherSuite          HIGH:MEDIUM:+SSLv2
TLSCACertificateFile	./tolvendev-ldap-cacerts.pem
TLSCertificateFile	./tolvendev-ldap-cert.pem
TLSCertificateKeyFile	./tolvendev-ldap-key.pem

3. Cleartext passwords, especially for the rootdn, should be avoided. See slappasswd(8) and slapd.conf(5) for details. Use of strong authentication is encouraged. This hashed password is secret by default.

suffix	dc=tolven,dc=com
rootdn	cn=Manager,dc=tolven,dc=com
rootpw	{SSHA}KHCgqfsybbtXVI4yPkAFKlE2gQPXNemf

4. The following is an LDAP directive for the database directory, which must exist prior to running slapd and should only be accessible by the slapd and slap tools:

directory ./tolvendata

Index on the following attributes to improve performance

index objectClass eq
index sn eq
index uid eq

6.1.2 Set Up the LDAP Database

The LDAP database is very important. The LDAP user entries that it contains have the encryption keys for the data created by those users in the database. Those keys are the only way to decrypt the data. Therefore, you should back up the LDAP database appropriately. Create a new directory to hold the tolven LDAP data:

c:\openLDAP> md tolvendata

Add the root elements into this new LDAP database using the slapadd command. Ensure that the required entries exist in the slapd.conf as specified in the Configure OpenLDAP section.

c:\openLDAP> slapadd -f slapd.conf -l tolveninitial.ldif

NB: The file tolveninitial.ldif can be empty, but at least on one version of openldap, this command does not error, but won't complete without the -l option.

6.1.3 Test LDAP in non-SSL Mode

Temporarily comment out the four lines beginning with TLS, which were added above, from the slapd.conf, by placing a '#' at the start of each line. Now execute the following command, to start LDAP in non-secure mode.

c:\openLDAP> slapd -h ldap://

Now use an application e.g. JXplorer to access LDAP on port 389 and ensure that it is running correctly. You can also use the 'netstat -a' command. If you have trouble accessing LDAP, then again temporarily start it with debug on:

c:\openLDAP> slapd -d 256 -h ldap://

Now you can stop LDAP and reactivate the commented lines so that when you return with the SSL credentials later on, you will be ready to restart LDAP in secure mode.

6.2 Initially Set Up openLDAP for Linux

6.2.1 Add/Modify slapd.conf Entries

Edit the slapd.conf file in the openLDAP directory. The slapd.conf file varies over time with different versions and configurations. Below are the directives known and used by Tolven. Copy or replace the equivalent lines in the slapd.conf file of your openldap installation.

1. The schema includes below must be present. core is usually there by default. If not, add it as well. On Linux, the full path to the files below may be required; therefore, the entries below assume that openLDAP is installed in /etc/openldap. These lines will prevent the LDAP server from starting, until the credentials indicated are put in place later during this configuration process.

include		/etc/openldap/schema/core.schema
include		/etc/openldap/schema/cosine.schema
include		/etc/openldap/schema/inetorgperson.schema

2. The next four lines allow use of TLS for encrypting connections using a self-signed test certificates. These lines will prevent the LDAP server from starting, until the credentials indicated are put in place later during this configuration process.

TLSCipherSuite          HIGH:MEDIUM:+SSLv2
TLSCACertificateFile	/etc/openldap/tolvendev-ldap-cacerts.pem
TLSCertificateFile	/etc/openldap/tolvendev-ldap-cert.pem
TLSCertificateKeyFile	/etc/openldap/tolvendev-ldap-key.pem

3. Cleartext passwords, especially for the rootdn, should be avoided. See slappasswd(8) and slapd.conf(5) for details. Use of strong authentication encouraged. This hashed password is secret by default.

suffix	dc=tolven,dc=com
rootdn	cn=Manager,dc=tolven,dc=com
rootpw	{SSHA}KHCgqfsybbtXVI4yPkAFKlE2gQPXNemf

4. The following is an LDAP directive for the database directory, which must exist prior to running slapd and should only be accessible by the slapd and slap tools (Linux mode 700 recommended).

directory /etc/openldap/tolvendata

5. Index on the following attributes to improve performance:

index objectClass eq
index sn eq
index uid eq

6.2.2 Configure the LDAP Database

The LDAP database is very important. The LDAP user entries that it contains, have the encryption keys for the data created by those users in the database. Those keys are the only way to decrypt the data. Therefore, the LDAP database should be backed up appropriately.

1. Use the following command to create a new directory to hold the Tolven LDAP data:

Linux:

/<your_openldap_installation_directory>; mkdir tolvendata

2. Add the root elements into this new LDAP database using the slapadd command.

NB: The file tolveninitial.ldif can be empty, but at least on one version of openLDAP, this command does not error, but won't complete without the -l option.

Linux:

<your_openldap_installation_directory>; slapadd -f slapd.conf -l tolveninitial.ldif

3. Change the permissions of the openldap directory to that of the user LDAP (for example, on fedora):

Linux:

chown -R ldap:ldap /etc/openldap

6.2.3 Test LDAP in non-SSL Mode

1. In the slapd.conf file, temporarily comment out the four lines beginning with TLS that were added above by placing a '#' at the start of each line.

2. Execute the following command, to start LDAP in non-secure mode:

c:\openLDAP> slapd -h ldap://

3. Use an application such as JXplorer or the command below to access LDAP and ensure that it is running correctly:

ldapsearch -x -W -D cn=Manager,dc=tolven,dc=com -b "dc=tolven,dc=com" -LLL "(uid=*)" dn

4. If you have trouble accessing LDAP, then again temporarily start it with debug turned on:

c:\openLDAP> slapd -d 256 -h ldap://

5. Stop LDAP and reactivate the commented lines in slapd.conf so that when you return with the SSL credentials later on, you will be ready to restart LDAP in secure mode.

6.3 Did openLDAP shut down abruptly?

Troubleshooting: The Berkeley DB software (BDB) underlying openLDAP can become corrupted if openLDAP is shut down abnormally such as when power fails. A convenient way to harmlessly repair the database is to use the BDB db_recover command:
db_recover -c -h tolvendata
You can even include this command in a batch file that starts up openLDAP so that the repair is attempted, if needed, automatically every time openLDAP is started.

Step 7 - Configure Tolven

Online Installation

In an on-line installation, plug-ins are downloaded from http://tolven.org/download by default.

If you need to change the plug-in Library Repository, edit <config-dir>/plugins.xml file, and change the following property:

<property name="repositoryLibraryURL" value="http://tolven.org/download,file:///#{globalProperty['config.dir']}/repositoryLocal" />

There is no need to edit this property under most circumstances. The first represents the main Tolven download site for Tolven plug-ins, while the second is a local repository, which by default is <config-dir>/repositoryLocal.

Additional libraries can be added to this property separating each with a comma. Multiple repositories will be treated as one large, combined repository from which to draw plug-ins.

7.1 Modify Plugin Properties

The default plugins.xml file is located in the tolven-config directory. It is identical to the file called jboss-legacypostgresql-ldap-plugins.xml located in the <install-dir>/examples/rootPlugins directory. If you are configuring for Oracle, then you should copy the jboss-oracle-ldap-plugins.xml from that directory, rename it plugins.xml and place that in <config-dir> directory before proceeding.

This file is important since it determines which plug-ins will be downloaded from the Library Repositories, and allows the user to configure plug-ins. Each plugin named in this XML file may have the optional one <root/> tag. The presence of a <root> tag guarantees that the plug-in and all its dependencies will be downloaded. A given plugin can have any number of <property> tags specific to that plug-in. The <property> tags can also exist outside of any particular plugin, making them global <property> tags.

The plugins.xml file contains a list of plug-ins, some of which contain a <root> tag. Those are the ones which will be downloaded under all circumstances if found in the library repository. They are deemed required for the most part. Other plugins may be downloaded if there is a direct or indirect dependency.

Now we will cover the minimum changes required when using a default installation. There are many other properties in the plugins.xml which you may want to change.

7.1.1 Configure LDAP Properties

When these properties are changed, it is necessary to run configPhase1 for them to take effect. Only the basic of the LDAP properties are shown below:

<plugin id="org.tolven.config.ldap">
    <root />
    <property name="ldap.hostname" value="localhost" />
    <property name="ldap.port" value="389" />
</plugin>

7.1.2 Configure Database Properties

When these properties are changed, it is necessary to run configPhase1 for them to take effect. The hostname, port and databaseName can be set here:

PostgreSQL:

<plugin id="org.tolven.config.database">
    <root />
    <property name="database.hostname" value="localhost" />
    <property name="database.port" value="1521" />
    <property name="database.databaseName" value="postgres" />
    <property name="database.user" value="postgres" />
</plugin>

Oracle:

Oracle has two possible formats:

<plugin id="org.tolven.config.database">
	<root />
	<property name="database.hostname" value="localhost" />
	<property name="database.port" value="1521" />
	<property name="database.databaseName" value="ORCL" />
	<property name="database.user" value="tolven" />
</plugin>

or:

<plugin id="org.tolven.config.database">
	<root />
	<property name="database.user" value="tolven" />
	<property name="database.url" value="jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)
          (HOST=localhost)(PORT=1521))(CONNECT_DATA=(SERVER=DEDICATED)(SERVICE_NAME=ORCL)))" />
</plugin>

7.1.3 Configure JDBC Driver Properties

The value "your-jdbcDriver.jar" below needs to be the absolute path to the driver suggested by your database installation. The application server also needs this jdbc driver, which in the case of JBoss means placing it in the application server's lib directory (i.e. the full path to server/tolven/lib for tolven-jboss-4.x).

<plugin id="org.tolven.library.jdbcdriver">
    <root />
    <property name="jdbcDriver" value="your-jdbcDriver.jar" />
</plugin>

You can either use the explicit absolute path or combine both the requirements above by using one of the global properties ending with the name of your jdbc driver, to refer to the driver from the appservers' lib directory e.g.

<plugin id="org.tolven.library.jdbcdriver">
    <root />
    <property name="jdbcDriver" value="#{globalProperty['appserver.home']}/server/tolven/lib/your-jdbcDriver.jar" />
</plugin>

7.1.4 Configure Tomcat Properties

Complete this step if you are installing Tolven under the Tomcat application server.

When you change these properties, you must run configPhase1 for them to take effect. Only the basic properties of the Tomcat server are shown below....there are many more in the plugins.xml (see org.tolven.config.tomcatserver).

<plugin id="org.tolven.config.tomcatserver">
    <root />
    <property name="http.port" value="8080" />
    <property name="http.address" value="#{globalProperty['webBindAddress']}" />
    <property name="http.redirectPort" value="8443" />
    <property name="https.port" value="8443" />
    <property name="ajp.port" value="8009" />
    <property name="ajp.redirectPort" value="8443" />
</plugin>

Note here the use of a plug-in property called http.address. The plug-in developer indicates that this plug-in requires an http.address, so this file could provide it right here as a string literal, but this example shows that since the hostname is more global than just this plug-in, the value should be search for in a global property called 'webBindAdress', which would be located in a <property> tag outside any particular plug-in.

Note: The default configuration will only work for HTTP requests on localhost. To specify a specific host adapter to listen on, edit your <config-dir>/plugins.xml file:
<property name="webBindAddress" value="X.X.X.X" />
or to listen on all host adapters:
<property name="webBindAddress" value="0.0.0.0" />

7.1.5 Configure Application Server Properties

When these properties are changed, it is necessary to run configPhase1 for them to take effect. You can configure the application to not require a password on startup, with the disadvantage that the password for startup will be in plain text on the file system. To select this option, set the prompt for password to false:

<plugin id="org.tolven.assembler">
	<root />
	<property name="promptFor.appserver.password" value="false" />
</plugin>

The previous method for doing this is below, and is now deprecated. You can remove the entire plug-in entry from you <config-dir>/plugins.xml in favor of the one above:

<plugin id="org.tolven.config.appserverpasswordpromptoff">
	<root />
	<property name="promptFor.appserver.password" value="false" />
</plugin>

7.1.6 Configure Global Properties

Three important properties defined in this file must be edited to reference your local installation directories:

<property name="installation.dir" value="your-installationDir" />
<property name="config.dir" value="your-tolven-configDir" />
<property name="appserver.home" value="your-appserver-homeDir" />

Property	Windows Example	Description
installation.dir	C:/tolven-RC1	Contains the static installation files including TPF and related executable files. This directory will change with each new version of Tolven. You should avoid making local configuration changes in this directory (except for the tpfenv file).
config.dir	c:/tolven-config	Contains permanent, dynamic configuration files such as credentials and the plug-in configuration used for this system. This directory usually remains active as the installation directory changes.
appserver.home	C:/tolven-jboss-4.2.2.GA	This location of the target application server. This property helps Tolven determine where to deploy the assembled Tolven EAR file.

Note: On Windows, you must use forward slashes when specifying directory paths in these Java-based properties files (backslash is taken as an escape character).

7.2 Set Up Environment Variables

When executing commands in the plugin framework, you may be required to enter the admin Id ("admin" by default), admin password (sysadmin by default) and the location of the configuration directory. The tpfenv command will set the admin ID and configuration directory location as environment variables (TOLVEN_USER and TOLVEN_CONFIG_DIR).

Execute the following command in the installation bin directory.

Windows:

cd <install-dir>\bin
tpfenv

Linux (note the extra dot followed by a space):

cd <install-dir>/bin
. ./tpfenv.sh

The script is quite straightforward. Although we do not recommend it for security reasons due to password visibility, the password can also be set using TOLVEN_PASSWORD.

Note: TOLVEN_CONFIG_DIR should not contain backslashes unless you have escaped them.

7.3 Initialize the Runtime Repository

The Plug-in Runtime Repository normally starts out empty and valid. It will contain the plug-ins that will be downloaded, selected, and used to configure Tolven. Once the root plug-ins have been selected for addition to the Runtime Repository, all the dependent plug-ins can be determined from those root plug-ins. After running the repositoryInit command, make note of any errors on the console and check the server log for details. Because having the plug-ins download correctly is essential, resolve any issues before proceeding with the installation.

Troubleshooting: If, when running repositoryInit, you get a cannot delete file for one or more of the plug-ins, manually delete the file and re-run repositoryInit.

Windows:

cd <install-dir>\bin
repositoryInit

Linux:

cd <install-dir>/bin
./repositoryInit.sh

Tolven will then contact each of the Plug-in Library Repositories and download the root plug-ins by default, followed by all the dependent plug-ins. When complete, the following directory should contain a number of plug-in zip files:

c:/tolven-config/repositoryRuntime/plugins

7.4 Run the Check Integrity Command

Check that the files below contain the properties and path files that you have used in previous steps. Do not change the username, password, and role to those that you used when you installed the policy agent. To run the check integrity command and all over commands in this installation, leave the default username <coe>admin</code>, password sysadmin, and role tolvenAdmin.

Also, the domain that is referenced in these files is dev.able.com for both the keystore and truststore. If you are installing in a domain other than dev.able.com, you must also make sure that these files reference your domain.

Windows:

tpfenv.bat and tpf.bat

Linux:

tpfenv.sh OR tpf.sh

Execute the tpfenv file for your OS and the command shell you are running from will be ready to execute the various Tolven commands. You should get output similar to the following:

TOLVEN_USER=admin
TOLVEN_REALM=tolven
TOLVEN_PASSWORD=xxxxxxxx
TOLVEN_CONFIG_DIR=C:\tolven-config
0 [main] INFO root  - Start log4j - Configuration: file:/C:/tolven-V2/bin/tolven-log4j.xml, logFileName: 
  C:\tolven-V2\log\tolven.log
21:06:29,265 INFO  [TPFBoot] TPF Version: 1.x.x
21:06:29,265 INFO  [TPFBoot] Loaded configDir C:\tolven-config

Execute the following command which carries out a light integrity check that is adequate at this stage:

checkIntegrity

There should be no errors in the command shell or in the <install-dir>/log/tolven.log.

7.5 Run Phase 1 Configuration

Phase 1 usually happens before the application server is running. It's primary function is to assemble the Tolven "ear" file and deploy it to the application server.

If there has been any misconfiguration, it will show up when you attempt your first configPhase1. Execute the following from the <install-dir>/bin directory:

configPhase1

Note: The build directory is periodically deleted if changes are made to the tolven-config/plugins.xml or if repositoryInit is used to download new plug-ins. If that is the case, then configPhase1 must be executed again to ensure the latest jar files are available for later deployment.

7.6 Configure Credentials

When you ran configPhase1, credentials were placed in the tolven-config/credentials directory (by default). This directory is configurable from within the plugins.xml file for plug-ins that manage credentials. Tolven no longer deploys credentials directly to the LDAP, database, or JBoss servers, because it is normally a one-time act anyway.

For previous users who are upgrading, the current credentials located in your database and LDAP servers should be fine, so long as you also copy your previous credentials (indicated below) from your previous JBoss directory to the new JBoss directory. There are a few additional steps indicated here: Tolven RC1

If this is your first installation, then you need to manually copy the following credentials to the servers:

7.6.1 Configure LDAP Credentials

Copy the following files to your LDAP directory:

tolven-config/credentials/ldap/tolvendev-ldap-key.pem
tolven-config/credentials/ldap/tolvendev-ldap-cert.pem
tolven-config/credentials/ldap/tolvendev-ldap-cacerts.pem

When you configured LDAP, you may recall that LDAP was waiting for these credentials in order to be able to start up in secure mode on port 636. The default password for tolvendev-ldap-key.pem is tolven, which you will be prompted for when you start LDAP. Ensure that LDAP is now accessible using JXplorer (or some other tool) or that LDAP is listening on port 636 (for example, using the 'netstat -a' command). On Linux, we recommend that these certificates are owned by the LDAP user, and that the permissions have the unix convention 400.

7.6.1.1 Start OpenLDAP

If you are using OpenLDAP, you can start it with a command such as the following:

C:\OpenLDAP\slapd.exe -f slapd.conf -d 636 -h ldaps://

Notice that the port is now defined as ldaps (which is port 636). The default password that protects the password store is tolven.

7.6.2 Configure PostgreSQL Credentials

Copy the following to your database directory (for example, the data directory under PostgreSQL):

tolven-config/credentials/postgresql/server.key
tolven-config/credentials/postgresql/server.crt
tolven-config/credentials/postgresql/root.crt

On Linux, ensure that these certificates are owned by the database user (postgres by default), and that the permissions have the unix convention 400.

7.6.3 Configure Oracle Credentials

Consult the Oracle documentation for instructions on how to configure Oracle for SSL connections or how to use Oracle Wallet.

If no special SSL configuration is applied to Oracle, then Tolven will talk to Oracle over a non-encrypted connection. In that case, you can skip this step completely. This is reasonable if the connection between Tolven and Oracle occurs within a secure environment.

Copy the Tolven-generated credentials to the Oracle Wallet from tolven-config/credentials/oracle.

7.6.4 Configure JBoss Credentials

Copy the following to the tolven-jboss-4.2.2.GA/server/tolven/conf directory:

tolven-config/credentials/jboss/tolvendev-jboss.jks
tolven-config/credentials/jboss/tolvendev-jboss-cacerts.jks
tolven-config/credentials/tolven/tolvendev-tolven.jks
tolven-config/credentials/tolven/passwordStore.properties
tolven-config/credentials/webserver/tolvendev-webserver.p12

7.6.5 Configure pgadmin Credentials

If you are using pgadmin, it also requires credentials, which for conveniece are included with the PostgreSQL configuration. Copy the following to a directory called postgres (for linux prefix this with a dot) in the user's home directory:

tolven-config/credentials/pgadmin/postgresql.key
tolven-config/credentials/pgadmin/postgresql.crt

7.7 Test Database and LDAP Connections After ConfigPhase1

&&&&&The database and LDAP servers should be running for the following tests, although the application server is not yet ready to be started. If these tests fail, there is no point moving on until, the issues are resolved.

This test attempts to connect to the PostgreSQL database using the database superuser and the admin keystore for SSL. If using Oracle, substitute org.tolven.postgresqlmgr with org.tolven.oraclemgr :

tpf -plugin org.tolven.postgresqlmgr -testAdminDB

This test attempts to connect to the database using the database superuser and the application server keystore for SSL:

tpf -plugin org.tolven.postgresqlmgr -testAppServerDB

This test attempts to connect to LDAP using the root DN in LDAP and the admin keystore for SSL:

tpf -plugin org.tolven.ldapmgr -testRootDNLDAP

7.8 Run Phase 2 Configuration

For phase 2, (re)start both the database and the LDAP servers. The GUI Plugins contain a number of manager plug-ins (suffixed with mgr), which provide both command line and GUI tests for the connections to the database and LDAP servers. Use these to ensure that you have working connections.

The configPhase2 command activates any plug-ins that may need to initialize the LDAP and database servers before the application server is started. This extra step is required because the application won't start correctly if there are no schemas in either the database server or the LDAP server.

After the database has been initialized, you do not need to repeat this step, although there is no harm in doing so.

configPhase2

7.9 Update MDBUser

Execute the following in order to create an mdbuser in LDAP (see org.tolven.mdbuser):

Windows:

tpf -plugin org.tolven.mdbuser -update

Linux:

./tpf.sh -plugin org.tolven.mdbuser -update

7.10 Test LDAP Connection Prior to Starting Application Server

The tests executed after configPhase1 should not be affected by configPhase2, but you can check them again if desired.

The following test attempts to connect to LDAP using the admin DN in LDAP, which was placed there during configPhase2, and uses the admin keystore for SSL.

tpf -plugin org.tolven.ldapmgr -testAdminLDAP

The following test attempts to connect to LDAP using the admin DN in LDAP, which was placed there during configPhase2, and uses the application keystore for SSL.

tpf -plugin org.tolven.ldapmgr -testAppServerLDAP

7.11 Start Application Server

Start the application server by navigating to the Tolven JBoss bin directory and executing the following command:

Windows:

startTolvenJBoss

Linux:

./startTolvenJBoss.sh

On Linux, there is a startJBossNohup version which starts JBoss in the background, but we don't recommend that you use this command until you have ensured that you have configured and can start JBoss successfully. You will also have to configure JBoss to not require a password, as described above.

It is recommended that you watch the JBoss server.log carefully as it starts (server/tolven/log/server.log), to ensure that you see no errors.

7.11.1 Test Application Server Connection After Start

The following test will connect to the application server as admin and is only a simple test to check whether a context can be retrieved.

tpf -plugin org.tolven.jbossmgr -testAdminAppServer

7.12 Update Database Indexes

After JBoss has started, execute the following commands to create the database indexes for the tables, which were created during the startup process. This step is normally carried out during a first installation, and might only need to be re-run if new indexes are announced in Tolven. This process can take a few minutes to run for a large database.

Windows:

cd <install-dir>\bin
updateDBIndexes.bat

Linux:

cd <install-dir>/bin
./updateDBIndexes.sh

7.13 Update Server Properties

Next, you will configure the Tolven runtime server properties. An initial set of properties will be created which you can deploy to the database. Thereafter, you can change these properties when needed, even while the application server is running. The properties are managed by the following entry in the plugins.xml file:

<plugin id="org.tolven.appserverproperties">
	<root />
	<property name="appserver.default.propertiesFile" value="server-default-config.properties.xml" />
	<property name="guiComponentParentId" value="org.tolven.appservermgr" />
</plugin>

The filename value of the appserver.default.propertiesFile is by default a relative path to the file within the plug-in itself. These default properties are currently a part of the plug-in. If you want to edit these properties, then place all of those properties in your own file, and use an absolute path to that file. For example:

Windows:

<property name="appserver.default.propertiesFile" value="c:/tolven-config/server-default-config.properties.xml" />

Please note the forward slashes for the path which appears in the plugins.xml file.

Linux:

<property name="appserver.default.propertiesFile" value="/usr/local/tolven-config/server-default-config.properties.xml" />

You can use the example file provided in the <config-dir> or unzip the one in the plug-in itself, and then place that externally wherever you choose, and then edit it. If you already have properties in the database from a previous installation, then there is no need to run this command, otherwise:

tpf -plugin org.tolven.appserverproperties -load

If you want to use the GUI for appserver properties, then you can execute:

tpf -plugin org.tolven.appserverproperties -gui

7.14 Add Application Metadata to plugins.xml

Tolven requires metadata that defines the basic application behavior. Metadata, in the form of plug-ins, is uploaded to the database where it is used a runtime. In order for these plug-ins to be available to your repositoryRuntime, you need to first add the following snippets to your tolven-config/plugins.xml file in order to make them root plug-ins.

7.14.1 Add Metadata Supplied by Tolven to plugins.xml

Note that these are prototypes (examples), which Tolven updates regularly on the download site. Add the following to your <tolven-config>/plugins.xml file:

<plugin id="org.tolven.prototype.applications">
	<root />
</plugin>
<plugin id="org.tolven.prototype.application.trim">
	<root />
</plugin>

These plug-ins will automatically be downloaded to your <config-dir>/repositoryRuntime/plugins directory the next time you execute repositoryInit, and as newer versions appear, they too will be downloaded.

7.14.2 Add Custom Metadata to plugins.xml

If you do not want to use the Tolven-supplied custom metadata above, and want to use you own custom metadata, you can execute the following to create a snapshot, or starting place, from the current prototypes. You will then maintain these from that point forwards.

Execute one the following in order to download copies of plug-ins containing application metadata. Make sure that you substitute the location of your <config-dir> directory for the defaults below. In addition, each of the commands below needs to be executed individually to allow you to enter the admin password.

Windows:

copyplugin -src http://tolven.org/download -srcId org.tolven.prototype.applications -dest 
  <config-dir>/repositoryLocal/plugins -destId com.myorg.applications
copyplugin -src http://tolven.org/download -srcId org.tolven.prototype.application.trim -dest 
  <config-dir>/repositoryLocal/plugins -destId com.myorg.trims
genMetadata -plugins <config-dir>/repositoryLocal/plugins -liburl file:///<config-dir>/repositoryLocal 
  -outdir <config-dir>/repositoryLocal

Linux:

./copyplugin.sh -src http://tolven.org/download -srcId org.tolven.prototype.applications -dest 
  <config-dir>/repositoryLocal/plugins -destId com.myorg.applications
./copyplugin.sh -src http://tolven.org/download -srcId org.tolven.prototype.application.trim -dest 
  <config-dir>/repositoryLocal/plugins -destId com.myorg.trims
./genMetadata.sh -plugins <config-dir>/repositoryLocal/plugins -liburl file:///<config-dir>/repositoryLocal 
  -outdir <config-dir>/repositoryLocal

The above commands will result in two plug-ins' being copied to your local repository directory <config-dir>/repositoryLocal/plugins.

In order for these plug-ins to then be transferred to your <config-dir>/repositoryRuntime/plugins directory, you need to first add the following plug-in requests to your tolven-config/plugins.xml file.

<plugin id="com.myorg.applications">
	<root />
</plugin>
<plugin id="com.myorg.trims">
	<root />
</plugin>

7.14.3 Add Vocabulary Metadata to plugins.xml

Applications will need some standard vocabulary. Tolven provides several vocabularies via plug-ins which can also be included by pasting some or all of the following in the plugins.xml.

<plugin id="org.tolven.deploy.allergies">
	<root />
</plugin>
<plugin id="org.tolven.deploy.breastproblems">
	<root />
</plugin>
<plugin id="org.tolven.deploy.diagnoses">
	<root />
</plugin>
<plugin id="org.tolven.deploy.immunization">
	<root />
</plugin>
<plugin id="org.tolven.deploy.problems">
	<root />
</plugin>
<plugin id="org.tolven.deploy.procedures">
	<root />
</plugin>
<plugin id="org.tolven.deploy.rxnorm">
	<root />
</plugin>

7.15 Run repositoryInit

To download the above plug-ins to your repositoryRuntime, execute repositoryInit.

Windows:

cd <install-dir>\bin
repositoryInit

Linux:

cd <install-dir>/bin
./repositoryInit.sh

7.16 Run Phase 3 Configuration

The configPhase3 command will activate those plug-ins that have account types, rules, trims, vocab, etc. to upload to the database via the application server. In other words, it uploads the Tolven application configuration. Prior to this step, the application server will have no applications defined, and therefore a user would be able to do little beyond logging in.

This is likely to be the most commonly repeated configuration command after the above installation and configuration process has been completed.

The application server must be started before executing the following command:

Windows:

configPhase3

Linux:

./configPhase3.sh

The actions taken by this command affect the database, not the tolven.ear file. For example, if changes are made that affect the tolven.ear file, then configPhase1 will need to be run before running configPhase3. If only a trim changes, then only configPhase3 is needed to upload it to the running database and application server.

Verify: Navigate to the Tolven Web application: http://localhost:8080/Tolven.
After logging in, verify that the Select Account page displays. If you have not loaded any applications, there will be no choices available and you will not be able to go any further. This is normal. If you have configured a custom vestibule, then the initial page following login may be different.

7.17 Activate Vocabulary Plug-ins

The vocabulary plug-ins are not automatically activated during configPhase3, and so have their own commands. You may be prompted for userId, password and <config-dir> unless you have taken the appropriate configuration steps given earlier in the configuration process, so these commands must be executed individually. If your userId, password and <config-dir> are set up you can simply execute them all, and they will simply execute sequencially:

Windows:

tpf -plugin org.tolven.deploy.allergies
tpf -plugin org.tolven.deploy.breastproblems
tpf -plugin org.tolven.deploy.diagnoses
tpf -plugin org.tolven.deploy.immunization
tpf -plugin org.tolven.deploy.problems
tpf -plugin org.tolven.deploy.procedures
tpf -plugin org.tolven.deploy.rxnorm

Linux:

./tpf.sh -plugin org.tolven.deploy.allergies
./tpf.sh -plugin org.tolven.deploy.breastproblems
./tpf.sh -plugin org.tolven.deploy.diagnoses
./tpf.sh -plugin org.tolven.deploy.immunization
./tpf.sh -plugin org.tolven.deploy.problems
./tpf.sh -plugin org.tolven.deploy.procedures
./tpf.sh -plugin org.tolven.deploy.rxnorm

Step 8 - Next Steps

Your installation and initial configuration of Tolven and dependent products is complete. As a developer, you will most likely want to proceed to the Developer's Guide where you will learn how to create new Tolven functionality and add it to the configuration.

From this point on, you will be making iterative changes to the application configuration and running configPhase1 or configPhase3 as needed. Likewise, if Tolven adds new functionality such as the synchronous submit feature or makes bug fixes, you will only need to do:

tpfenv
repositoryInit
configPhase1 or configPhase3

There is no need to repeat any of the installation steps.