Fixes are available
Operational Decision Manager V8.9.2 Download Document
Operational Decision Manager V8.9.2 Mod Pack
Operational Decision Manager for z/OS 8.9.2 Mod Pack
Operational Decision Manager V8.8.1.3: Interim Fix 97
Operational Decision Manager V8.8.1.3: Interim Fix 98
Operational Decision Manager V8.8.1.3: Interim Fix 101
Operational Decision Manager V8.8.1.4: Interim Fix 8
Operational Decision Manager V8.9.1.0: Interim Fix 30
Operational Decision Manager V8.9.0.2: Interim Fix 15
APAR status
Closed as program error.
Error description
Executing a Test scenario fails with an error saying 'An error has occurred while deploying the XOM to Rule Execution Server...' whereas there is no XOM to deploy (project is based on XSD) and in the log, we can see the following information: -- 01-Dec-2017 17:15:03.918 WARNING [SSP Prepare Archive Thread] ilog.rules.teamserver.ejb.service.validation.IlrTestingUtil. updateFailedTestReport [Report - 2017-12-01_05-15-01-621] nullilog.rules.teamserver.model.IlrXOMDeploymentException: An error has occurred while deploying the XOM to Rule Execution Server 'Execution Server'. If the Rule Execution Server is not deployed on the same server and port as the Decision Runner, the RES_URL init parameter of the Decision Runner web application must be set to the URL of the Rule Execution Server. Contact your administrator. at ilog.rules.teamserver.model.decisionservice. TestingXOMDeployManager.deployXOM(TestingXOMDeployManager.java: 107) at ilog.rules.teamserver.model.IlrModelUtil. getXomUrisPropValue(IlrModelUtil.java:1288) at ilog.rules.teamserver.ejb.service.validation. IlrTestSuiteService.prepareRun(IlrTestSuiteService.java:315) at ilog.rules.teamserver.ejb.service.validation. IlrTestSuiteService.asynchronousPrepare(IlrTestSuiteService. java:204) at ilog.rules.teamserver.ejb.service.validation. PrepareArchiveThreadService.run(PrepareArchiveThreadService. java:57) at com.google.common.util.concurrent. AbstractExecutionThreadService$1$2.run( AbstractExecutionThreadService.java:66) at com.google.common.util.concurrent.Callables$4.run( Callables.java:122) at java.lang.Thread.run(Thread.java:745)
Local fix
Uncheck the option "enable XOM management" in Decision Center from the Decision Service properties.
Problem summary
Decision Center always tries to collect xom information for the project being deployed. When no XOM is deployed then this exception may happen
Problem conclusion
the code is fixed
Temporary fix
Comments
APAR Information
APAR number
RS02962
Reported component name
WDS FOR RULES
Reported component ID
5725B6903
Reported release
890
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-12-07
Closed date
2017-12-26
Last modified date
2017-12-26
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Modules/Macros
999
Fix information
Fixed component name
WDS FOR RULES
Fixed component ID
5725B6903
Applicable component levels
R890 PSY
UP
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSQP76","label":"IBM Operational Decision Manager"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"890","Line of Business":{"code":"LOB45","label":"Automation"}}]
Document Information
Modified date:
17 February 2022