The bpm-platform.xml file is part of the CIB seven distribution and can be used for configuration of process engines and the job executor. It is used to configure CIB seven in the following distributions:

• Apache Tomcat

Xml Schema Namespace

The namespace for the bpm-platform.xml file is http://www.camunda.org/schema/1.0/BpmPlatform. The XSD file can be found in the cibseven-engine.jar file.

Example

<?xml version="1.0" encoding="UTF-8"?>
<bpm-platform xmlns="http://www.camunda.org/schema/1.0/BpmPlatform"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.camunda.org/schema/1.0/BpmPlatform http://www.camunda.org/schema/1.0/BpmPlatform ">

  <job-executor>
    <job-acquisition name="default" />
  </job-executor>

  <process-engine name="default">
    <job-acquisition>default</job-acquisition>
    <configuration>org.cibseven.bpm.engine.impl.cfg.JtaProcessEngineConfiguration</configuration>
    <datasource>jdbc/ProcessEngine</datasource>

    <properties>
      <property name="history">full</property>
      <property name="databaseSchemaUpdate">true</property>
      <property name="transactionManagerJndiName">java:appserver/TransactionManager</property>
      <property name="authorizationEnabled">true</property>
    </properties>

  </process-engine>

</bpm-platform>

Syntax Reference

Configure Location of the bpm-platform.xml File

You can configure the location of the bpm-platform.xml, so the file can be stored externally to allow an easy update path of cibseven-bpm-platform.ear. This negates the work of unpacking / repackaging the ear when you need to change the configuration.

This feature is available for:

• Apache Tomcat

It is not available for the Wildfly subsystem implementation, because the subsystem implementation uses the JBoss specific standalone.xml to configure the platform.

To specify the location, you have to provide an absolute path or an http/https url pointing to the bpm-platform.xml file, e.g., /home/cibseven/.cibseven/bpm-platform.xml or http://example.org/bpm-platform.xml.

During startup of the cibseven-bpm-platform, it tries to discover the location of the bpm-platform.xml file from the following sources, in the listed order:

1. JNDI entry is available at java:/comp/env/bpm-platform-xml
2. Environment variable BPM_PLATFORM_XML is set
3. System property bpm.platform.xml is set, e.g., when starting the server JVM it is appended as -Dbpm.platform.xml on the command line
4. META-INF/bpm-platform.xml exists on the classpath
5. (For Tomcat only): checks if there is a bpm-platform.xml inside the folder specified by ${CATALINA_BASE} || ${CATALINA_HOME} + /conf/

The discovery stops when one of the above mentioned sources is found or, in case none is found, it falls back to the bpm-platform.xml on the classpath, respectively ${CATALINA_BASE} || ${CATALINA_HOME} + /conf/ for Tomcat. We ship a default bpm-platform.xml file inside the cibseven-bpm-platform.ear, except when you use the Tomcat or Wildfly version of the platform.

Using System Properties

To externalize environment specific parts of the configuration, it is possible to reference system properties using Ant-style expressions (i.e., ${PROPERTY_KEY}). Expression resolution is supported within the property elements only. System properties may be set via command line (-Doption) or in an implementation specific manner (Apache Tomcat’s catalina.properties for example). Complex operations are not supported, but you may combine more than one expression in a single property element (e.g., ${ldap.host}:${ldap.port}).

Example

<!-- ... -->
<plugin>
  <class>org.cibseven.bpm.engine.impl.plugin.AdministratorAuthorizationPlugin</class>
  <properties>
    <property name="administratorUserName">${camunda.administratorUserName}</property>
  </properties>
</plugin>
<!-- ... -->