The INUBIT Architecture

The INUBIT software consists of different components which can be combined with each other for use in the most diverse application scenarios due to their consistency:

The INUBIT Process Engine is the central core component of INUBIT. It provides the platform for process execution and ensures the technical integration of systems and services.

Technically, it is a web application that runs on the Apache Tomcat application server. The included Tomcat instance is pre-configured so that you can operate the INUBIT Process Engine without further adjustments. You can find all configuration details here.

The communication with the INUBIT Process Engine is achieved via its REST API. This communication is SSL secured using HTTPS. Consequently, the INUBIT Process Engine can be used in both local networks and large, global corporate networks.

To automate business processes, the INUBIT Process Engine supports the integration of external systems by a wide variety of built-in system connectors. This provides an easy interaction with company-internal server systems, directory services, databases, REST applications, or cloud services.

Within the INUBIT software, XML is consistently used as a central data format.

The INUBIT Workbench is a java-based client with a graphical user interface for the following tasks:

The Business Process Center Portal can be used as a basis for a corporate intranet and for interacting with business partners. Through the integration in the INUBIT Process Engine you can realize business process scenarios requiring human interaction.

The Business Repository is used for central storing and managing data and information. These information can be accessed during the process execution. Due to the integrated versioning all changes are audit logged and safed in a revision-safe manner.

If a direct connection to other enterprise applications is not possible for security reasons, you can use a Remote Connector: A Remote Connector runs a system connector on a different machine from which access to the desired application is permitted.

The Process Engine communicates with as many Remote Connectors as required via REST (using HTTPS).