New Server Configuration Properties

From DOC

Note: This is new as of Tolven RC1

A Tolven installation typically involves three primary components: Application Server, database, and LDAP server. The installation process needs to know how these components should be "wired up" for SSL keys and mutual authentication. In other words, the components need to know about each other.

To facilitate the wiring between components, an "identifier" is assigned to represent each component. For example, PostgreSQL and Oracle are separate, unique components. One of them would be chosen as the database that the Tolven application server will talk to. Likewise, the application server can vary. So JBoss is an app-server component.

Previously, a fourth ID was used to represent the intersection of these three components into a valid "configuration". Further, it was necessary to have variations for Windows and Linux platforms.

Migration From Previous Releases

This section contains pertinent information regarding migrating the previous configuration properties, and obtaining the new properties required to proceed.

For new installations, the properties mentioned below will alrealdy be installed with the tolven-config/tolven-config.properties.xml. However, for upgrades, these properties were not originally there, and of course, the Tolven Plugin Framework cannot yet be used to obtain them. For this situation, a command has been provided, which will basically add the new required properties to the tolven-config.properties.xml file. It will not populate them or removed the old deprecated properties so, the instructions below still need to be followed.

Go to the installation's bin directory and execute:

On Windows

cd c:\<tolven-install>\bin
legacy-migrate

On Linux

cd /usr/local/<tolven-install>/bin
./legacy-migrate.sh

This command will backup copies of the following files from your tolven-config directory to your tolven-config/archive directory, and replace them with new ones. In the case of the properties files, your original properties will be untouched (except tolven.home), and new properties will be added.

tolven-config.properties.xml
credential.xml
tolven-config.xml
server-default-config.properties.xml

New Configuration Properties

the following properties will be added to tolven-config.properties.xml

	<entry key="appserverId"></entry>
	<entry key="appserver.home"></entry>
	<entry key="databaseId"></entry>
	<entry key="database.credential.directory"></entry>
	<entry key="ldapId"></entry>
	<entry key="ldap.credential.directory"></entry>

In the next step, you will set the values of these properties.

The Change

The active.appServerId, which consisted of a hyphenated string e.g. jboss-legacy-postgresql-openldap, has now been replaced by the individual Ids which make up the three servers i.e. appserverId, databaseId and ldapId. In addition, the need to distinguish between windows and linux is no longer required, reducing the number of properties related to directory locations.