JarCasting
JarCasting JarCasting

pl.beone.promena.base:promena-transformer-contract

Spring Boot Dependencies

License

License
Categories

Categories

ORM Data
GroupId

GroupId

pl.beone.promena.base
ArtifactId

ArtifactId

promena-transformer-contract
Last Version

Last Version

1.0.0
Release Date

Release Date
Type

Type

jar
Description

Description

Spring Boot Dependencies
Project Organization

Project Organization

BeOne Sp. z o.o.

Download promena-transformer-contract

Filename Size
promena-transformer-contract-1.0.0.pom
promena-transformer-contract-1.0.0.jar 47 KB
promena-transformer-contract-1.0.0-sources.jar 14 KB
promena-transformer-contract-1.0.0-javadoc.jar 1 KB
Browse

How to add to project

<!-- https://jarcasting.com/artifacts/pl.beone.promena.base/promena-transformer-contract/ -->
<dependency>
    <groupId>pl.beone.promena.base</groupId>
    <artifactId>promena-transformer-contract</artifactId>
    <version>1.0.0</version>
</dependency>
// https://jarcasting.com/artifacts/pl.beone.promena.base/promena-transformer-contract/
implementation 'pl.beone.promena.base:promena-transformer-contract:1.0.0'
// https://jarcasting.com/artifacts/pl.beone.promena.base/promena-transformer-contract/
implementation ("pl.beone.promena.base:promena-transformer-contract:1.0.0")
'pl.beone.promena.base:promena-transformer-contract:jar:1.0.0'
<dependency org="pl.beone.promena.base" name="promena-transformer-contract" rev="1.0.0">
  <artifact name="promena-transformer-contract" type="jar" />
</dependency>
@Grapes(
@Grab(group='pl.beone.promena.base', module='promena-transformer-contract', version='1.0.0')
)
libraryDependencies += "pl.beone.promena.base" % "promena-transformer-contract" % "1.0.0"
[pl.beone.promena.base/promena-transformer-contract "1.0.0"]

Dependencies

compile (4)

Group / Artifact Type Version
pl.beone.promena.base : promena-transformer-application-model jar 1.0.0
org.jetbrains.kotlin : kotlin-stdlib-jdk8 jar
org.jetbrains.kotlin : kotlin-reflect jar
org.slf4j : slf4j-api jar 1.7.29

test (4)

Group / Artifact Type Version
org.mockito : mockito-core jar 3.1.0
org.assertj : assertj-core jar 3.13.2
org.junit.jupiter : junit-jupiter-engine jar 5.5.2
io.kotlintest : kotlintest-runner-junit5 jar 3.4.2

Project Modules

There are no modules declared in this project.

The modular general-purpose transformation system, perfectly suited to Alfresco.

Motivation

As one of the steps in a task execution, applications sometimes have to perform "heavy" long-running operations such as document converting, OCR, report generating or email sending. Executing such tasks within an application cause increase in its responsibility and consequently code complexity, 3rd party tools integration, error handling, scalability problem, queuing etc.

Promena is the transformation system that allows to delegate a task and receive the result of its execution.

Sample

There are samples of:

  • building Promena
  • deployment
  • transformers and modules
  • integration with Alfresco

Alfresco

This repository contains Alfresco Content Services modules that are required to integrate Alfresco with Promena.

Flow

A connector module doesn't have to be implemented directly on Promena. It can be, for example, a message broker which is a layer between an application and Promena connector module.

Application

  1. Send to Promena using a connector module (see Connector):
  2. Receive from Promena using given connector module:

Promena

  1. Receives on the connector (see Connector):
  2. Converts Data of TransformationDescriptor from external communication to internal communication (see Communication)
  3. Performs a transformation using transformers (see Transformer)
    • Transformation can be composed of many transformers. Each transformer can be located on a different node
  4. Converts transformed Data from internal communication to external communication
  5. Sends to the application using given connector module:

Module

The functionality of Promena can be extended by modules. Modules are added in the build stage of Promena (see Building).

Special cases of modules are, as mentioned earlier, connector module, communication module and actor creator module.

Visit Sample#Module to see examples of modules and Development Guide to implement a custom module.

Actor creator

Promena is based on Akka so it's required to specify the way of creating actors. The presence of exactly one ActorCreator implementation is required.

Name Description
promena-actor-creator-adaptive-load-balancing Performs load balancing of messages to cluster nodes based on the cluster metrics data and chooses mailbox with fewest messages locally

Communication

The role of communication was described in Flow section. Promena distinguishes two types of communication:

  • External - the communication between an application and Promena. The application determines the kind of this communication. The presence of at least one external communication is required
  • Internal - the communication that determines the way of sharing data between Promena nodes. The presence of exactly one InternalCommunicationConverter implementation and exatly one InternalCommunicationCleaner implementation is required
Name Description
promena-communication-file Shares data using files placed in common location (internal and external) - preferred for production use
promena-communication-memory Shares data using memory (internal and external)

Connector

The role of a connector was described in Flow section. It's a bridge between an application and Promena.

Name Description
promena-connector-activemq Transfers serialized data using ActiveMQ - preferred for production use
promena-connector-http Transfers serialized data using HTTP
promena-connector-normal-http Transfers data using normal HTTP

Transformer

A transformer is the fundamental element of Promena ecosystem. Every Promena executable can contain many transformers (at least one is required). The transformer responsibility is performing given transformation.

Each transformer implements Transformer and is identified by name and sub name (TransformerId). The name describes the kind of a transformation (converter for example) and the sub name describes implementation details (LibreOffice for example). Each transformer also determines if it's able to perform given transformation - before a transformation Promena asks transformer if it's able to do it with given transformation parameters.

Promena groups transformers by their name. This means that an application can delegate a task using only name. It implicates that an application doesn't have to know transformers implementation details. An application also may pass sub name if it wants to perform given transformation on the specific transformer.

It may happen that many transformers can perform given transformation (if you passed only name), therefore, you can set the priority of each transformer. A priority is described by the value (a lower value indicates a higher priority). Visit the transformer repository to see how to set the transformer priority.

Promena can run many instances of transformers within one instance. Promena runs only one instance of each transformer by default but you can change it by increasing the number of actors. Visit the transformer repository to see how to set the number of transformer actors. It isn't the recommended way of scaling Promena. A better idea is to scale out Promena instances.

Promena resolves transformations. An application doesn't know if given transformation is included in Promena - it will get appropriate information as the response. If you want to find it out on an application side, you can do it using application-model dependency. Each transformer contains application-model. It includes transformer constants, you can check if the transformer supports given media type and parameters before sending a transformation. Unfortunately, it has disadvantages. It decreases the level of loose coupling and you don't know if given transformer is included in Promena.

Each transformer can by tweaked by parameters. Parameters describe a transformation. In case of lack of parameters, a transformer should use default parameters. Visit a transformer repository (Properties section) to find out how to set default parameters.

Each transformer repository contains example module. It contains the examples of transformations that you can execute using IntelliJ plugin.

Transformation character is often associated with the use of 3rd party tools. Additionally, each transformer may contain Dockerfile-fragment that is used to build Promena.

Visit Sample#Transformer to see the examples of transformers and Development Guide to implement a custom transformer.

Name Description
converter-libreoffice Based on LibreOffice - converts documents
converter-imagemagick Based on ImageMagick - converts images
converter-pdfbox Based on PDFBox - converts documents
ocr-ocrmypdf Based on OCRmyPDF - OCR documents
barcode-detector-zxing-opencv Based on ZXing & OpenCV - detects barcodes in documents and returns information about them
page-extractor-pdfbox Based on PDFBox - extract pages from documents
report-generator-jasperreport Based on JasperReports - generates reports

Building

A base project to build Promena you can generate by executing:

mvn archetype:generate -B \
    -DarchetypeGroupId=pl.beone.promena.sdk.maven.archetype \
    -DarchetypeArtifactId=promena-executable-archetype \
    -DarchetypeVersion=1.0.0 \
    -DgroupId=<group id> \
    -DartifactId=<artifact id> \
    -Dpackage=<package> \
    -Dversion=<version>

Generated pom.xml contains the following modules:

and doesn't contain any transformer. If you want to add a module or a transformer - visit its repository to get dependencies.

In order to build Promena, run mvn clean package on pom.xml. Java 11 JRE is required. You will get Promena Docker image and executable jar.

The default name of Docker image is ${promena-executable}:${project.version} (you can change it in the configuration section of promena-docker-maven-plugin plugin). Executable jar is located in target/${promena-executable}-${project.version}.jar.

promena-docker-maven-plugin scans all plugin dependencies to find docker/Dockerfile-fragment files, and then concat them and build Promena Docker image based on src/docker/Dockerfile template.

Promena image provides the complete running environment (Promena executable jar and all 3rd party tools). Executable jar contains only the application.

Visit Sample#Image to see the examples of Promena Docker images.

Run environment variables

Default docker-entrypoint.sh runs Promena with the following JVM parameters:

  • JAVA_OPTS_MEMORY = -XX:MinRAMPercentage=50 -XX:MaxRAMPercentage=80
  • JAVA_OPTS_GC =
  • JAVA_OPTS_DEBUG_ENABLED = false
  • JAVA_OPTS_DEBUG = -agentlib:jdwp=transport=dt_socket,address=*:9999,suspend=n,server=y
  • JAVA_OPTS_ADDITIONAL = -Dfile.encoding=UTF-8 -Djava.security.egd=file:/dev/./urandom
  • JAVA_OPTS_CUSTOM =

If JAVA_OPTS_DEBUG_ENABLED is true, Promena is run with JAVA_OPTS_DEBUG parameter.

Properties

Properties can be set using environment variables. Promena is based on Spring Boot so many properties are common - Spring Appendix - Core properties.

Each module and transformer provides its own set of properties. The list of properties you can find in their repositories.

Core properties available in every Promena executable:

# See https://doc.akka.io/docs/akka/2.5.26/cluster-usage.html for more details
akka.actor.provider=cluster
akka.remote.netty.tcp.hostname=127.0.0.1
akka.remote.netty.tcp.port=2552
akka.maximun-payload-size=${core.serializer.kryo.buffer-size}b
akka.remote.netty.tcp.message-frame-size=${akka.maximun-payload-size}
akka.remote.netty.tcp.send-buffer-size=${akka.maximun-payload-size}
akka.remote.netty.tcp.receive-buffer-size=${akka.maximun-payload-size}
akka.remote.netty.tcp.maximum-frame-size=${akka.maximun-payload-size}
akka.remote.maximum-payload-bytes=${akka.maximun-payload-size}

# Maximum time to complete a transformation by transformer
core.transformation.timeout=10m
# Additional time after timeout for transformer to stop transformation 
core.transformation.interruption-timeout-delay=5s
# Number of serializer actors. If not set, the number of serializer actors will be sum of transformer actors
core.serializer.actors=
# Maxium Kryo buffer size [bytes]
core.serializer.kryo.buffer-size=104857600

# Determines if transformation may be delegated to other transformer in cluster
core.transformer.actor.cluster-aware=true
# Determines if serialization may be delegated to other serializer in cluster
core.serializer.actor.cluster-aware=false

# If application uses external communication that isn't recognized by Promena, Promena will give a try to convert data using back-pressure communication
communication.external.manager.back-pressure.enabled=true
# Name of back-pressure communication
communication.external.manager.back-pressure.id=memory

Deployment

Promena can be run in every environment with Docker support or in every environment with Java 11 JRE if you want to deploy Promena executable jar manually.

Visit Sample#Deployment to see the example configurations of manual, Kubernetes and OpenShift deployment.

IntelliJ plugin

It allows you to execute a transformation directly from IntelliJ on Promena. This plugin uses promena-connector-http connector module so it's required to include it on Promena.

Available on: https://plugins.jetbrains.com/plugin/13689-promena/.

Visit mirror-jdk/example to see Java and Kotlin examples.

Demo

Data syntax

A function has to start with data declaration. It has to be a single line comment in the following format:

// Data: <absolute/resource path> [| MediaType: <mime type>; <charset>]

The part [| MediaType: <mime type>; <charset>] is optional. If it isn't specified, the plugin tries to discover media type automatically.

Examples:

  • // Data: example.txt - file example.txt from resources with media type that is discovered automatically
  • // Data: example.txt | MediaType: text/plain - file example.txt from resources with MIME type text/plain and charset that is discovered automatically
  • // Data: /Users/skotar/Temp/example.txt | MediaType: text/plain; UTF-16 - file example.txt from absolute path with media type text/plain; UTF-16

There is no support for passing Metadata yet.

Requirements

  • The file must be in a module
  • The file must have a package name
  • The function must return Transformation

Kotlin

  • The file must contain a function that name starts with promena

Java

  • The file must contain a class
  • The class must contain a static function that name starts with promena

Development Guide

This repository explains how Promena works internally and how to implement a custom module and transformer.

pl.beone.promena.base

BeOne Sp. z o.o.

Versions

Version
1.0.0