Infinity Process Platform Environment

The Infinity Process Platform runtime engine is configured by a set of parameters. Those parameters can be specified in several ways, depending on the operating mode.

When operating in Spring local mode (direct connection of the client with the database), the runtime properties are obtained from two distinct places: and the Java system properties. Infinity Process Platform runtime is always searching for the file in the JVM classpath. The Java system properties can be specified using the -D option of the Java virtual machine.

When operating inside an application server, in addition to the previous configuration mechanisms, the Infinity Process Platform runtime is using the EJB or the Web environment to get the necessary properties. In the current implementation, the EJB/Web environment has precedence over the properties specified in or system properties. The EJB environment is specified in the deployment descriptors of the Infinity Process Platform Enterprise Beans or in the deployment descriptor (web.xml) of your Web application. You can manually edit the descriptors, which are located in the carnot-engine.jar module, or you can use the administrative tools of your application server.

The client configuration always uses and the Java system properties.

Client and Server Side Properties

The client side properties are used for enabling the Infinity Process Platform client tools. They include in the first instance parameters for security, audit trail, JNDI and logging settings. For instance security parameters entail authenticating the client on the server side. These properties reside in the file, which is by default located in the /etc folder of your work directory, but the user can specify alternative search locations.

The server side properties have to be available in the Infinity Process Platform runtime environment. They include among others parameters for security, audit trail, concurrency and daemon settings. The server side file is located in the root directory of the engine.jar that is included within the carnot.ear file.