CARNOT GeMS Business Process Manager 2.0 Released


News: CARNOT GeMS Business Process Manager 2.0 Released

  1. CARNOT has released version 2 of their J2EE/XML based Global eProcess Management Solution (GeMS), an engine and toolkit for modelling and executing workflow and business processes, deloyable on J2EE compliant appservers. V2 provides JAAS integration and other improvements.

    Check out CARNOT GeMS 2.0.

    Press Release
    Mesa, AZ - CARNOT, Inc., manufacturer of the J2EE/XML based and AppServer independent Global eProcess Management Solution (GeMS), today announced the release of version 2.0.

    Version 2.0 introduces new features and improves the performance and scalability of the product. A short list of features introduced in this version follows:

    Full support for the Java Authentication and Authorization Service (JAAS) allows the developer to integrate the CARNOT Process Engine with arbitrary JAAS-compliant security systems.

    A library for accessing Lightweight Directory Access Protocol (LDAP) via JAAS is also part of the distribution.

    Increased flexibility in the usage of integrated beans by supporting completion methods requiring parameters and providing return values.

    A new facility allowing CARNOT users to change their own user data is provided.

    Utilities for creating and upgrading schema of the audit trail database has been provided.

    Default values for data elements of pre-defined types are now supported.

    Multiversion enactment allows the CARNOT developer to perform hot deployment of model versions. Execution of existing process instances as well as instantiation of processes based on the most recent model will be transparently handled by the process engine.

    The CARNOT 2.0 eProcess engine and toolkit provides business analysts and developers with a comprehensive toolset for modelling and executing business processes, and allows for rapid deployment on a number of application servers such as Borland, BEA, IBM, Pramati, Oracle, SAP and JBOSS, to name a few. The product also provides optional ready-to-use connectivity to a number of major software solutions such as SAP, Oracle and others.

    "Meeting market demands by continuously consulting with both the software developer and the actual end user, has allowed CARNOT to maintain their leadership in the BPM solutions industry and deliver new Enterprise Business Process functionalities on time and with higher performance" says Mark Crauwels, CEO of CARNOT, Inc.

    Free 30 day download - CARNOT developer's toolkit -

    About the product: CARNOT is the leading embeddable Global eProcess Management Solution that is entirely based on J2EE/XML technology and open standards. The CARNOT Global eProcess Management Solution includes an eProcess engine, Process Definition Desktop (Modeler), Process Execution Desktop and an Administration Desktop.

    About the company: CARNOT is an innovative eProcess software company headquartered in Frankfurt, Germany, and with North American sales and support offices in Mesa, Arizona. CARNOT focuses on the emerging market of J2EE-based enterprise eProcess solutions and their integration with legacy IT infrastructures.

    All product or service names mentioned herein are the trademarks of their respective owners.

    Have more questions? Contact us through the links below or call: 480-396-4441

    Robert Verheijen
    CARNOT global processes

    voice: 480-396-4441
  2. What is the price for this software? Similar to BEA Process Integrator?
  3. I am curious to know how this BPM solution compares with the next version of Microsoft BizTalk. The process logic in BizTalk is apparently going to be created using XLANG/s, a scripting language based on C#. The equivalent approach in Java is Collaxa's WSOS ( which is based on Scenario Beans.

    These emerging solutions are in contrast to the conventional approach of using XML to model process logic. They are meant to provide needed flexibility for expressing complex non-linear interactions, such as parallelism, exceptions, events, etc.

  4. first, the intention of any bpm system should be to provide
    another layer of abstraction. a layer, where terms like
    process, activity, application, data and participant are
    used instead of statement, method invocation, etc as a
    language to communicate with business analysts and
    integrators not only coders.

    this abstraction is provided by various languages and their
    underlying metamodel, such as xlang, bpmi, wfmc/interface1
    or wsfl. as long as the intention of these metamodels is
    similar (being executable on a process engine), their
    topology is something like an activity-transition-network,
    and their format is xml, xslt can be used to convert those
    to each other (obviously with loosing specific information).

    hence, xlang is not an alternative to a bpm engine,
    but a vehicle to communicate with it - as well as any
    other representation of a process model (not everything
    is c# these days).

    second, any kind of process model specification should not
    result in code. processes are modified more often than
    business functions/components. you should be able to
    adjust process models within a shorter timeframe than
    a 3 month design/build/test cycle. hence, a generative
    approach is not suitable.

    and finally:

    if a process definition metamodel cannot cover "flexibility for expressing complex non-linear interactions, such as parallelism, exceptions, events" ... it is weak anyway.
  5. Recent articles that discuss orchestration of web services suggest that XML's role is misguided in this context:

  6. It's a lot cheaper then you think.
    A 2 developer toolkit with a 5 user runtime license for testing purposes has a list price of USD4,900
    Runtime licenses USD 16,500 per CPU

    Robert Verheijen