Internal Logic Sample Clauses

Internal Logic. The component design is based on the following Apache Camel add-ons: • custom modules for accessing the short-term store through a web API; • camel-jdbc, for accessing management databases (through JDBC); • camel-hdfs2, providing the functionalities for reading and writing messages from/to the bulk-store (HDFS file systems). The main modules of the component are presented in Table 8, below. Module Name Description Message Database Connector Manages connections to the short-term store, which keeps all the messages currently processed by the middleware. Messages contain both data and context information (related to routing). Management Database Connector Manages connections to the data store for meta-information. Bulk-Storage Connector Manages connections to the database that keeps records of all events taking place and acts as the long-term storage for all messages.

Internal Logic. The following table provides a brief description of the main modules of the ExtAdapter component. Module Name Description Mediator Responsible for providing a web interface for receiving data from external systems (push), as well as invoking services for accessing data (pull) upon trigger. CimTransform This module can transform data from external systems to CIM format, using a predefined mapping of ontologies and attributes. Messaging Client Undertakes the role of the JMS client for exchanging messages with the Middleware. Scheduler This module triggers the process of accessing data from external systems (in pull mechanism). Data Manager Responsible for communicating with a local database and storing the message queue.

Internal Logic. The internal logic of the application is based on the following concepts:

Internal Logic. The design of BPE follows a modular approach, utilizing the following artefacts: • jBPM libraries, as a business process engine; • camel-jbpm (Camel add-on), providing integration with jBPM; • custom modules, enabling interaction among them and with the Middleware. In Figure 12 a structure of the BPE is illustrated, adapted from [13], depicting its main modules and their interrelations. Process Model Service Call Call Result Process Result startProcess The following table provides a brief description of the main modules of the BPE component. Module Name Description Core Engine This module is responsible for handling the steps of the business process. It is deployed as a service and can be integrated through Java API or CDI services, as well remotely through a REST and JMS API. Business Activity Monitoring Keeps track of the business processes and provides monitoring information of the status of the business process. Process Manager Handles events (both internal and external), either by invoking business processes in the Core Engine or by invoking services in the Middleware and providing the result to the Core Engine. Model Manager Provides an interface for storing the process models in the model repository. Model Repository Responsible for storing the models (in XML format) of business processes and the history of business processes’ invocation.

Internal Logic. The component design is based on the following artefacts: • camel-core – the basic module of apache camel. • camel-jms / activemq-camel (or other mq library supporting JMS) as JMS component. Table 4 presents the main modules of the component. MOM This module provides a rule-based routing and mediation engine offering the core functionalities of the Middleware. Message Broker A building block of the Middleware is the message transfer agent (message broker). It acts as the connection of the Middleware with the external world and provides a solid implementation of messaging interface. Adapter This module is responsible for communicating with the back-end and transforming data from a certain format to the canonical format. The adapter can also handle an activity flow related to security (e.g. authentication, decryption, verify or sign document) and handle error cases.