Using Decision Manager Open Edition projects
You develop a knowledge artifact, or KJAR, in Decision Manager Open Edition. Before you can use the KJAR in a zRule Execution Server for z/OS runtime, you must enable it for COBOL.
- Install Eclipse 2025-12 running Java™ 21:
- Eclipse 2025-12

- Download Java 21 from IBM® Semeru Runtimes Downloads

- Eclipse 2025-12
- Install the Eclipse plug-in for Decision Manager Open Edition. It can be found in
++HBRINST++/zexecutionserver/DMOE.
- Install it into Eclipse by clicking .
If nothing is visible, clear the Group Items By Category checkbox. Everything is required except the etools fragment for your operating system. Windows is required for Windows, and Linux® for Linux.
- Accept all licenses and restart Eclipse when prompted.
- To check that the plug-in is installed, there should be a new entry in the file menu called DMOE Standalone for z/OS.
- Install it into Eclipse by clicking .
- Build a Decision Manager Open Edition JAR
file.
Either build a Decision Manager Open Edition KJAR through Maven or download a prebuilt one to COBOL enable it.
- Run through the tooling.
To open the wizard, go to .
You are prompted to point to a Decision Manager Open Edition KJAR either on the file system or in your workspace.
There is a selection of options available on this page:
- Import project into Eclipse: Available if the JAR is in a Decision Manager Open Edition project structure. It creates a copy of the project in Eclipse.
- Place marshallers in lib directory: Available if the JAR is in a Decision Manager Open Edition project structure. Creates a lib and resource directory in the same directory as target and update the Decision Manager Open Edition pom to merge all JAR files from lib into the JAR when Maven is building it.
- Keep temporary files: Keeps a selection of intermediate files and projects that Eclipse used to generate the marshallers.
After clicking next, this page allows you to set COBOL mappings for the attributes that are defined in Java. This converts the Java objects into a COBOL copybook.
Clicking finish brings up a report page that shows the locations of the marshallers copybook and mappings file have been created. There may also be a deploy JAR in the same location as the original KJAR if the JAR was not in a project.
Running the tooling headlessly
Eclipse -ws ++ECLIPSEWORKSPACE++ -application com.ibm.rules.zxom.standalone.dmoe.headless -consoleLog –noSplash -DMOEjar ++JKARLOCATION++ -mappings ++COBOLMAPPINGSLOCATION++A mappings file is strongly recommended to generate the first run through the tool normally.
The output is either in the same directory as the KJAR or the directory above if it is in a maven project.