View RSS Feed

jBPM Process

jBPM processes

  1. Configuring Delegations

    by , 04-27-2012 at 06:52 PM
    Delegation classes contain user code that is called from within a process execution, the most common example being an action. In the case of action, an implementation of the ActionHandler interface can be called on an event in the process. Delegations are specified in the processdefinition.xml file. One can supply any of these three pieces of data when specifying a delegation:

    1. the class name (required): this is the delegation class' fully-qualified name.
    2. configuration type
  2. The Process Class Loader

    by , 04-27-2012 at 06:51 PM
    Delegation classes are loaded through their respective process class loader. The process class loader has the JBPM class loader as its parent. It adds the classes deployed with one particular process definition. To add classes to a process definition, put them in the classes directory of the process archive. Note that this is only useful when one wishes to version the classes that have been added to the process definition. If versioning is not required, make the classes available to the JBPM class ...
  3. Migrating Process Instances

    by , 04-27-2012 at 06:50 PM
    An alternative approach to changing a process definition is to migrate each process instance to a new version. Please consider that migration is not trivial due to the long-lived nature of business processes. There is a clear distinction between definition data, execution data and logging data. Because of this distinction, a new version of the process has to be deployed first, and then process instances are migrated to the new version. Migration involves a translation if tokens or task instances ...
    jBPM Process
  4. Process Versioning

    by , 04-27-2012 at 06:50 PM
    Process instances always execute on the same process definition as that in which they were started. However, the JBPM allows multiple process definitions of the same name to co-exist in the database. Typically, a process instance is started in the latest version available at that time and it will keep on executing in that same process definition for its complete lifetime. When a newer version is deployed, newly created instances will be started in the newest version, while older process instances ...
    jBPM Process
  5. Deploying a Process Archive

    by , 04-27-2012 at 06:48 PM
    One can deploy a process archive in any of three different ways:
    via the Process Designer Tool
    with an ant task
    To deploying a process archive with the Process Designer Tool, follow this step. (This process is supported in the starter's kit.)

    1. Right-click on the process archive folder and select the Deploy process archive option.
    The starter's kit server contains the JBPM application, which has a servlet to upload process ...
    jBPM Process