ActiveVOS Server and Resource Configuration

This section leads you through configuration of the resources required for ActiveVOS Server. You must configure your database, application server and ActiveVOS Server before deploying and running ActiveVOS. The sections below provide information for completing the configuration.

Configuration Instructions

Before running the Configuration utility, perform the following pre-configuration steps:

Create a database (or tablespace) where ActiveVOS persistence information will be stored
Create a default user with administrative rights to the computer and database for use by ActiveVOS Server
Note both the database name and port number, which you will be prompted for during configuration.
ActiveVOS Server requires a JDBC driver to connect to your database. During configuration, you will be prompted for:

The full path to a supported JDBC database driver
The driver implementation class name

Note: Please note that the Microsoft SQL Server 2005 JDBC Driver 1.2 driver, or the JDTS-1.2.jar drivers are supported. Version 1.1 of the Microsoft SQL Server will not function as it does not include all required functionality.

First Time or New Install

If you are performing a clean installation, that is, a first-time install or a new database, you can use the Configuration utility to automatically install the database schema.

Manual Install or Update of Database Schema

It is strongly recommended that you automatically install the database schema; however, you can manually install it. Customers migrating from an earlier version should follow the instructions below.

Migrating from an earlier release of ActiveVOS

If you are migrating from an earlier release of ActiveVOS Server, perform the following steps:

Manually update the ActiveVOS database schema using the DDL patches provided in {install_dir}/server/jboss_config/ddls/updates
Run the Configuration utility

ActiveVOS Server can be configured to use an RDBMS database

Use the Relational Database Schemas section for information on relational databases

Relational Database Schemas

These instructions are generalized to make sure they can be followed for each database. When creating the database schema for ActiveVOS, you can either create a new database definition or upgrade an existing definition.

Refer to the install a new database schema section for a new installation.
Refer to upgrade a database schema when performing a version upgrade.

Install a new database schema

Identify your DDL. Use the information provided in the table below to locate the correct DDL file.

Database Server	DDL File Name and Location	Notes
MYSQL	{install_dir}/server/jboss_config/ddls/ActiveBPEL_Enterprise-MYSQL.SQL	The default database name, ActiveBPEL is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the AeMetaInfo table.
MS SQL SERVER	{install_dir}/server/jboss_config/ddls/ActiveBPEL_Enterprise-SQLSERVER.SQL	The default database name, ActiveVOS is defined within the DDL file. If you edit this name, ensure that you do not replace ActiveVOS Enterprise, a name that is inserted into the AeMetaInfo table.
ORACLE	{install_dir}/server/jboss_config/ddls/ActiveBPEL_Enterprise-ORACLE.SQL	Create a tablespace prior to running the DDL.
DB2	{install_dir}/server/jboss_config/ddls/ActiveBPEL_Enterprise-DB2.SQL

Copy the DDL file from above, and rename it.

Note: The original files must remain unchanged for the Configuration utility to work properly

(Optional) Modify the database name.Be sure to see the notes above.
Execute the DDL script.

Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.

Upgrade an existing database schema

To upgrade your existing ActiveVOS database to be compatible with the new version of software, follow the instructions below:

Shutdown ActiveVOS before executing a database upgrade.
Identify your current running version of ActiveVOS. Database upgrades are provided to upgrade from one version back at a time. This means that more than one upgrade script may need to be applied to your database.
For each upgrade that needs to be applied perform the following:

Identify your DDL. Use the information provided in the table below to locate the correct DDL file. Note: The updates must be applied in ascending order.

Database Server	DDL File Name and Location
MYSQL	{install_dir}/server/jboss_config/ddls/updates/ActiveBPEL_Enterprise-MYSQL-PATCH-{patch number}.SQL
MS SQL SERVER	{install_dir}/server/jboss_config/ddls/updates/ActiveBPEL_Enterprise-SQLSERVER-PATCH-{patch number}.SQL
ORACLE	{install_dir}/server/jboss_config/ddls/updates/ActiveBPEL_Enterprise-ORACLE-PATCH-{patch number}.SQL
DB2	{install_dir}/server/jboss_config/ddls/updates/ActiveBPEL_Enterprise-DB2-PATCH-{patch number}.SQL

Modify the database name.

Make sure that the database name in the patch matches the database as you originally created it. To modify the name to match the installed database use the following steps.

Open the appropriate DDL for your database server in a text editor.
Replace the first three instances of the text ActiveBPEL with the preferred database name. Note: Be sure not to replace the ActiveVOS Enterprise that is inserted into the AeMetaInfo table or the ActiveVOS Server will not start.

Execute the DDL script.

Each database server provides its own mechanism or utility for executing a DDL script file. Execute the DDL upgrade script file using the appropriate utility. For example, if you are using Oracle, the utility to execute the DDL script file would be SQL Plus.

JBoss Application Server Requirement and Considerations

Installation of the JDBC Driver

ActiveVOS Enterprise requires that you provide a JDBC driver to connect to your database. You must install the database driver into each server in the cluster, if you are making server clustering available. Refer to your application server's user guide for information on installing the appropriate JDBC driver.

Note:Please note that the Microsoft SQL Server 2005 JDBC Driver 1.2 driver, or the JDTS-1.2.jar drivers are supported. Version 1.1 of the Microsoft SQL Server will not function as it does not include all required functionality.

Configuration of JBoss Ear-deployer.xml File

In order for ActiveVOS Enterprise to successfully deploy and run, ensure that the following attributes are set in the ear-deployer.xml file of the JBoss server instance that will be used:

<attribute name="Isolated">true</attribute>

<attribute name="CallByValue">true</attribute>

The ear-deployer.xml file is located in the {JBoss_install_dir}/server/[server name]/deploy directory

Note: By default the attributes are set with these values in the JBoss \default server configuration.

High Availability and Clustering

The default JBoss server configuration is not configured for High Availability or Clustering. As the name default implies, this is the server that is started when JBoss is started normally using the startup command file. The all server that is provided with JBoss has a default configuration that enables High Availability and Clustering.

When prompted by the Configuration and Deployment Wizard, be sure to select the appropriate server.

Using the Configuration Utility

The Configuration utility walks through the steps required to provide the property values for ActiveVOS and selected resources.

Note: Before running the utility, ensure that your server container is stopped.

Starting the Configuration Utility

Execute one of the following utilities based on your operating system:

Platform	Executable
Windows	{install_dir}/server/jboss_config/bin/config_deploy.bat
Linux	{install_dir}/server/jboss_config/bin/config_deploy.sh

If You Have Manually Installed or Updated the Database Schema

If you have manually installed or updated the database schema, when prompted, you must not select the "Install Database Schema" checkbox.

Running the Configuration Utility in Different Modes

The Configuration utility can be run with a graphical interface (default), in console mode or silently. When you run the utility your configuration options are automatically written to the install.properties file and they will be used as the defaults the next time the application is configured. One of the following parameters is accepted by the Configuration utility:

Help: help. This option displays the usage for console and silent modes.
Console mode: console. Runs the Configuration utility in text mode within a command window.
Silent mode: silent. Runs in the background requiring no user interaction. This option requires that you have already run the Configuration utility in default mode, which sets configuration options in the install.properties file.

An example of running the Configuration utility from the command line is: config_deploy help

Configuration Help

The Configuration utility contains online help for each panel of the utility. Access Help by clicking the Help button on each panel. Additionally you can access the help from {install_dir}/server/jboss_config/doc/html/config.