This project allows run ADempiere Processors as service using a little struct.
The resources for this are:
/v1/accounting/{client_id}/{id}
/v1/scheduler/{client_id}/{id}
/v1/request/{client_id}/{id}
/v1/alert/{client_id}/{id}
/v1/workflow/{client_id}/{id}
/v1/project/{client_id}/{id}
Some example:
curl --location --request POST 'http://0.0.0.0:5555/v1/project/11/100'
curl --location --request POST 'http://0.0.0.0:5555/v1/workflow/11/100' --header 'Authorization: Bearer '
curl --location --request POST 'http://0.0.0.0:5555/v1/alert/11/100' --header 'Authorization: Bearer '
curl --location --request POST 'http://0.0.0.0:5555/v1/request/11/100' --header 'Authorization: Bearer '
curl --location --request POST 'http://0.0.0.0:5555/v1/scheduler/11/100' --header 'Authorization: Bearer '
curl --location --request POST 'http://0.0.0.0:5555/v1/accounting/11/100' --header 'Authorization: Bearer '
Since the ADempiere dependency is vital for this project is high recommended that the you are sure that of project adempiere-jwt-token and adempiere-business-processor is installed and the setup is runned in ADempiere Database.
gradle run --args="resources/env.yaml"
For Token validation is used JWT
docker pull openls/adempiere-processors-service:alpine-1.0.1
To use this Docker image you must have your Docker engine version greater than or equal to 3.0.
DB_TYPE
: Database Type (SupportedOracle
andPostgreSQL
). DefaultPostgreSQL
.DB_HOST
: Hostname for data base server. Default:localhost
.DB_PORT
: Port used by data base server. Default:5432
.DB_NAME
: Database name that Adempiere-Backend will use to connect with the database. Default:adempiere
.DB_USER
: Database user that Adempiere-Backend will use to connect with the database. Default:adempiere
.DB_PASSWORD
: Database password that Adempiere-Backend will use to connect with the database. Default:adempiere
.IDLE_TIMEOUT
: It sets the maximum time a connection can sit around without being used before it gets closed to free up resources. Default:300
.MINIMUM_IDLE
: It sets the minimum number of connections that should be kept open and ready to use, even if they're not currently being used. This helps improve performance by reducing the time it takes to get a connection. Default:1
.MAXIMUM_POOL_SIZE
: It sets the maximum number of connections that can be open at the same time. This helps prevent the pool from getting too big and using up too much memory. Default:10
.CONNECTION_TIMEOUT
: it sets the maximum time HikariCP will wait to get a connection from the pool before giving up and throwing an error. Default:5000
.MAXIMUM_LIFETIME
: It sets the maximum amount of time a connection can stay open in the pool before it's automatically closed. This helps keep the pool clean and prevents problems. Default:6000
.KEEPALIVE_TIME
: It sets a test query that HikariCP will run on connections to make sure they're still working properly. Default:360000
.CONNECTION_TEST_QUERY
: It sets how often HikariCP will check if a connection is still working properly. This helps prevent problems with connections that might become inactive. Default:SELECT 1
SERVER_PORT
: Port to access Adempiere-Backend from outside of the container. Default:50059
.SERVER_LOG_LEVEL
: Log Level. Default:WARNING
.TZ
: (Time Zone) Indicates the time zone to set in the nginx-based container, the default value isAmerica/Caracas
(UTC -4:00).JAVA_OPTIONS
: Custom settings to the Java Virtual Machine (JVM). Default:-Xms64M -Xmx1512M
.
You can download the last image from docker hub, just run the follow command:
docker run -d -p 50059:50059 --name adempiere-processors-service -e DB_HOST="localhost" -e DB_PORT=5432 -e DB_NAME="adempiere" -e DB_USER="adempiere" -e DB_PASSWORD="adempiere" openls/adempiere-processors-service:alpine-1.0.1
See all images here
You can also run it with docker compose
for develop enviroment. Note that this is a easy way for start the service with PostgreSQL and template.
docker compose version
Docker Compose version v2.16.0
Just go to docker-compose
folder and run it
cd docker-compose
docker compose up
You can change variables editing the .env
file. Note that this file have a minimal example.
Just run it using any gRPC client or Rest API client with envoy
Here some video (Spanish Version)