Post-Installation Tasks

After you finished with either type of installation, there are still a few pending tasks that you need to perform. These include configuring Eclipse, setting up an Audit Trail database, Infinity Process Platform work directories and environment variables. These steps are explained in the following sections.

Configuring the Working Environment

Audit Trail Database

Infinity Process Platform requires a database to store the audit trail information. Please refer to the section Configuration of the Audit Trail Database for information on how to configure your audit trail database.

Environment Variables

Infinity Process Platform uses the following environment variables:

Java VM extension libraries are supported via standard extension mechanism. To use this feature, put the extension packages in the lib/ext directory of your working environment. You can deactivate the Infinity Process Platform extension libraries by setting the environment variable CARNOT_SUPRESS_DEFAULT_EXT_DIRS to any non-empty value.

The following environment variables will be used by Infinity Process Platform tools if they are not explicitly specified during tool invocation:

Please note that environment variables take precedence over values specified in the file.

Infinity Process Platform Properties

Infinity Process Platform applications read properties controlling a number of aspects from

After receiving one of the provided Maven archetype templates, a valid file can be found in the src/main/resources folder in your Maven project. For details on Infinity Process Platform properties, refer to the Client Side Properties chapter and the Server Side Properties chapter accordingly.

Post Installation Steps

Infinity Process Platform requires few other software products in its runtime environment. These include a database system for storing the audit trail data, an application server and a Web application server. They form what we call the Infinity Process Platform runtime environment.

For more details on deployment issues, refer to Deployment Concepts and Application Server Setup chapters of the Deployment Guide to get more information on the Infinity Process Platform runtime environment.

If you want to test the Infinity Process Platform facilities (including process enactment and administration) in a single user mode, you can run it in Spring local mode (default mode). To do this, you need to:

The sections below explain how to perform these two tasks.

Running Infinity Process Platform for the First Time

Using the Rapid Application Development Environment

Infinity Process Platform provides a Rapid Application Development Environment, which allows to quickly start in application development without requiring a client-dependent development environment. For details on configuring the Eclipse workspace and create a dynamic Web project in this environment, refer to the Rapid Application Development guide.

Creating a custom Java Project

In case you create your custom Java Project to be used with Infinity Process Platform, you have to perform the following steps:

Configuring the audit trail database

Setting up the audit trail database and the configuration of Infinity Process Platform for use with this database is essential for all types of operating modes. You can find detailed instructions for this in chapter Setting up the Audit Trail Database of the Deployment Guide.

Make sure the following is configured correctly for a IPP database connection:

By default, the Infinity Process Platform setup configures your Infinity Process Platform installation for Spring local mode. The parameters for your JDBC connections can be set in the file in your %CARNOT_WORK%/etc folder. Additionally, the JAR (or ZIP) containing the JDBC driver for this database has to be copied to %CARNOT_WORK%/lib. This path is included in the classpath used by Infinity Process Platform applications.

Please note that Infinity Process Platform databases must run in read-committed mode. If the transaction isolation is set to another mode, please change it as described in the configuration section corresponding to the database you are using.

An example of SQL scripts creating a user in an ORACLE database is provided in %CARNOT_HOME%/etc/sql.

The configuration of your audit trail database depends on the database you use. Please refer to the corresponding chapter for details on the specific configurations:

Create the necessary schema by using the SysConsole utility (installed in the bin directory of your CARNOT_HOME folder). Open a command line and type:

> sysconsole.bat createschema

For detailed information, refer to the Operation Guide section SysConsole. Another option is to create it manually using a description provided in %CARNOT_HOME%/etc/sql/carnot-schema.sql.

Creating a new Java project

Create a new Java project by selecting File > New > Project... > Java Project. To prepare the project to be used with Infinity, set the build path as described in the following section.

Setting the build path

In Eclipse, each Java project has its own build path that specifies all dependencies required to compile the project. Those dependencies may come from other Java projects in the workspace, from Java archive .jar files, or from folders containing .class files. To properly set up the classpath of your project to be able to build your process models in Infinity Process Platform, you have to set up the BPM build path:

Figure: Enable BPM Support

Now the BPM Core Libraries, which contain the Infinity Process Platform classes you need, are added to the build path of your project.

Figure: The Infinity Process Platform BPM Libraries in the Build Path

Depending on your requirements, you can now proceed with one of the following topics: