With the 7.13 release, RHDM customers will notice that the distribution files for RHDM have been replaced with those
for RHPAM. Note that there is no change to the RHDM subscription - support entitlements and fees remain the same.
RHDM is a subset of RHPAM, and RHDM subscribers will continue to receive full support for the decision management
and optimization capabilities included. The business process management (BPM) capabilities exclusive to RHPAM will
be available for use by RHDM subscribers, but with development support services only. RHDM subscribers may upgrade
to a full RHPAM subscription at any time to receive full support for BPM features."
For quickstarts and Application Templates, please refer to the Red Hat Process Automation repository. For versions older than 7.13, please refer to the branch of the target release.
This repository contains all the image descriptors and files necessary to build the RHPAM images. It also includes the application templates, however they are deprecated in 7.13. Using the Red Hat Business Automation Operator is recommended.
- rhdm-7-openshift-image
- controller: RHDM Controller Container Image descriptor files.
- decisioncentral: Decision Central Container Image descriptor files.
- kieserver: Execution Server Container Image descriptor files.
- quickstarts: Quickstarts used as example on RHDM images.
- scripts: Holds scripts to help this repository maintenance.
- templates: Application templates, used to instantiate a new RHDM environment on OpenShift. (Deprecated) \
- docs: Application templates docs generated by the gen_template_docs.py script.
Inside each image directory you will find the following files:
- container.yaml: used by OSBS builds.
- content_sets.yaml: define the yum repositories needed to install dependencies for the image.
- branch-overrides.yaml: overrides file which uses the latest stable version for external dependencies.
- tag-overrides.yaml: Used to override the branchs to use the final tags to rebuild released images, for CVE respins.
- image.yaml: the main image descriptor file, here are all the pieces and configuration needed to build an image.
On the root directory you can also find the two files:
- example-app-secret-template.yaml: Contains a https certificate to be used as example where https is required.
- rhdm-image-streams.yaml: imagestreams definitions, file used to install the product image streams on OpenShift, this files contains the image stream name and the registry the image will be pulled of.
This repo depends directly on 6 repositories, which are:
- cct_module: contains some core modules, like s2i and maven.
- jboss-eap-modules: contains modules responsible to configure JBoss EAP, like datasources and the base configuration files.
- jboss-eap-image: provides the EAP modules, which is used to install the EAP on the target image.
- wildfly-cekit-modules: provides the EAP configuration modules, used to configure the EAP during startup.
- rhdm-7-image: provides the RHDM binaries modules.
- jboss-kie-modules: contains all the resources used to configure the RHDM images.
Notice that, CEKit 3.8 or higher is required to build RHDM images.
To build the images for local testing there is a Makefile which will do all the hard work for you. With this Makefile you can:
-
Build and test all images with only one command:
make
If there's no need to run the tests just set the ignore_test env to true, e.g.:
make ignore_test=true
-
Test all images with only one command, no build triggered, set the ignore_build env to true, e.g.:
make ignore_build=true
-
Build images individually, by default it will build and test each image
make image image_name=decisioncentral make image image_name=controller make image image_name=kieserver
We can ignore the build or the tests while interacting with a specific image as well, to build only:
make ignore_test=true image_name={image_name}
Or to test only:
make ignore_build=true image_name={image_name}
-
List all available Images: To list all available images in the repository do:
make list-images
-
Building the images with a different overrides file: This can be done by simpling provide the overrides file name that should reside on the same directory than the target image.
make OVERRIDES=my-overrides-file-name.yaml
The scripts needed to generate the adocs can be found here. To generate the adocs using the current branch use:
make generate_adocs
It will use the main
branch from jboss-kie-modules using the current branch from RHDM git repository.
To generate the adocs for, example, 7.13.x branch, first, switch the git branch from RHDM repository then execute the following command:
make generate_adocs branch=7.13.x
It will use the 7.13.x
branch from jboss-kie-modules using the checked out branch on RHDM repository based from 7.13.x.
Before each release, there is a need to update the product version on each repository that composes the Container
Images.
In this repo you will find the scripts directory which containers the update-version.py
script which helps to
update the version to the next release interation smoothly.
This script requires python 3.
See its usage:
$ python scripts/update-version.py --help
usage: update-version.py [-h] [-v T_VERSION] [--confirm]
RHDM Version Manager
optional arguments:
-h, --help show this help message and exit
-v T_VERSION update everything to the next version
--confirm if not set, script will not update the rhdm modules. (Dry run)
There is two options to run it, a dry-run option which will only print for you the changes, useful if you want just to see
how the changes will looks like after the script is executed, and if the chages are correct, the --confirm
flag
should be used.
Please submit an issue here with the Cloud tag or send us one email: bsig-cloud@redhat.com.