openltablets/ws repository overview

⁠OpenL RuleServices WS

OpenL RuleServices WS is a web service application for executing OpenL Tablets rules. It supports hot rule updates at runtime via a rules repository.

⁠Supported Tags

• 6.3.0 latest
• 6.3.0-all
• 5.27.15 5.27.x
• 5.27.15-all `

⁠Suffix meaning

• without all - a minimal base image that allows publishing OpenL rules only. Usually, this is all that is needed.

• jre21 - variations of the 5.27.x images that run on JRE 21.

• jakarta - variations of the 5.27.x images that run on JRE 21 with Jakarta EE 10 APIs.

• all - an image that includes additional (extra) features and modules for integration with other subsystems:

  • Cassandra log storage,
  • ElasticSearch log storage
  • Database log storage
  • Git rules repository
  • AWS S3 rules repository
  • Azure BLOB storage rules repository

This image is larger in size because it includes significantly more dependencies than the base image. It also requires more resources (CPU and RAM) to run.

⁠What is OpenL Tablets?

OpenL Tablets targets the infamous gap between business requirements (rules and policies) and software implementation.

Designed to be straightforward and intuitive for business people, OpenL Tablets made its rules representation impressively close to documents usually created by business (it intends business requirements, etc.).

Users can focus on logic as all data, syntax and typing errors are checked while they write. Convenient tools help to ensure rules integrity while further using.

One-click deployment of rules as efficient, scalable and standardized services for SOA-based integration makes business logic simple to embed in application.

For Java developers, OpenL Tablets provides many rich usage scenarios in which all rules and business data are exposed through reflection-like API or wrapped as Java class.

All of OpenL Tablets is open sourced under LGPL license.

Please, visit http://openl-tablets.org/⁠ for more information.

⁠How to use this image

To run the OpenL Tablets WS:

$ docker run -d --rm -p 9080:8080 openltablets/ws

After application starts you can test it by visiting http://localhost:9080⁠ in a browser.

To use a specific version, please use a versioned tag. You can view the list of available versions⁠ in the Docker Hub Registry.

$ docker run -d --rm -p 9080:8080 openltablets/ws:[TAG]

⁠Configuration

• -e ruleservice.logging.enabled=true - enables request/response logging. Be attention, that it decreases performance.
• -e ruleservice.instantiation.strategy.lazy=false - disables lazy initialization. It is preferable for production environment. Increases startup time of the service and speedups the the first call to the service. Consumes more memory at startup but improves overall performance of the service.
• -e JAVA_OPTS="-XX:MaxRAMPercentage=50.0" -size of allocated memory as percentage of all available memory (90% by default)
• -e ruleservice.isProvideRuntimeContext=false - disables runtime context support

Please, refer to OpenL Tablets documentation⁠ for other settings.

⁠To use file system repo

To run OpenL Tablets Rule Services with filesystem datasource you can mount your local folder (e.g. ./openl-repository-folder) to the container:

$ docker run -d --rm -p 9080:8080 \
-v ./openl-repository-folder:/tmp/openl \
-e production-repository.factory=repo-file \
-e production-repository.uri=/tmp/openl \
openltablets/ws

⁠To use database repo

$ docker run --rm -d -p 9080:8080 \
-v ./mysql-connector-j-8.3.0.jar:/opt/openl/lib/jdbc.jar \
-e production-repository.factory=repo-jdbc \
-e production-repository.uri=jdbc:mysql://mysql-db-server/test \
-e production-repository.login=mysql \
-e production-repository.password=mysql \
openltablets/ws

If you use docker toolbox⁠, please, make sure that your jdbc_driver_contained_folder is shared⁠ folder in VM.

Please, refer to OpenL Tablets documentation⁠ for other settings.