IBM Support

IlrProductionRulesetIntrospectionException when testing with SSP

Question & Answer


Question

Why is the Scenario Service Provider (SSP) not updated with the new XOM changes, after running the ANT task to update the SSP? When testing with the newly deployed XOM, an exception indicates a ruleset parsing failure.

Cause

The ANT task for updating the SSP contains a "xomClasses" target, which specifies the location from where the compiled XOM classes have to be picked. This location needs to be updated when you change the "Default Output Folder" in Eclipse, for the Java XOM project.

Answer

When testing the ruleset with SSP, you might see the following exception:


    ilog.rules.dvs.common.output.IlrProductionRulesetIntrospectionException: An error has been detected. Contact your Administrator as this error typically occurs when trying to retrieve the signature of the ruleset. The XOM may not be correctly deployed to the SSP. Check the error trace for more detailed information.
    at ilog.rules.dvs.runner.impl.IlrRunnerImpl.run(IlrRunnerImpl.java:167)
    at ilog.rules.dvs.runner.impl.IlrRunnerImpl.run(IlrRunnerImpl.java:123)
    at ilog.rules.dvs.ssp.impl.IlrSSPServiceImpl.run(IlrSSPServiceImpl.java:79)
    ....

    Caused by: java.lang.RuntimeException:
    ilog.rules.res.xu.ruleset.impl.IlrCannotCreateRulesetException: Cannot create ruleset: /prodra1328026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0/prodrs1328026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0, error code: XU.ERROR.10009
    at ilog.rules.dvs.ssp.rsi.signature.IlrSSPRulesetSignatureFactory.getRulesetSignature (IlrSSPRulesetSignatureFactory.java:101)
    at ilog.rules.dvs.runner.impl.IlrRunnerImpl.run(IlrRunnerImpl.java:164)
    ... 28 more
    ...

    Caused by: ilog.rules.res.xu.ruleset.impl.IlrCannotCreateRulesetException:  Cannot create ruleset: /prodra1328026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0/prodrs1328
    026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0,
    error code: XU.ERROR.10009
    at ilog.rules.res.xu.util.IlrResourceExceptionHelper.createCannotCreateRulesetException ( IlrResourceExceptionHelper.java:134)
    at ilog.rules.res.xu.ruleset.impl.IlrRulesetParsingWork.run(IlrRulesetParsingWork.java:80)
    at com.ibm.ejs.j2c.work.WorkProxy.run(WorkProxy.java:399)
    ... 1 more
    ....

    Caused by:
    ilog.rules.res.xu.ruleset.impl.IlrCannotCreateRulesetException: Cannot create ruleset: /prodra1328026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0/prodrs1328
    026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0,  error code: XU.ERROR.10009
    at ilog.rules.res.xu.util.IlrResourceExceptionHelper.createCannotCreateRulesetException (IlrResourceExceptionHelper.java:134)
    at ilog.rules.res.xu.ruleset.impl.IlrXURulesetFactory.createRuleset(IlrXURulesetFactory.java:130)
    at ilog.rules.res.xu.ruleset.impl.IlrRulesetParsingWork.run(IlrRulesetParsingWork.java:69)
    ... 2 more

    ....


    Caused by: ilog.rules.res.xu.ruleset.impl.IlrRulesetParseException: Ruleset /prodra1328026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0/prodrs1328
    026198513_2450c897_ece3_4a0e_9219_a42e10130fe4/1.0 parsing failed Problem occurred during translation loading: Error when translating rule
    "<rule name>": Cannot translate value "<class>/<method>", error code: XU.ERROR.10014
    at ilog.rules.res.xu.util.IlrResourceExceptionHelper.createRulesetParseException ( IlrResourceExceptionHelper.java:121)
    at ilog.rules.res.xu.ruleset.impl.IlrRulesetParser.createRulesetParseException (IlrRulesetParser.java:158)
    at ilog.rules.res.xu.ruleset.impl.IlrRulesetParser.parseArchive( IlrRulesetParser.java:141)
    at ilog.rules.res.xu.ruleset.IlrDefaultRulesetFactory.createRCERuleset( IlrDefaultRulesetFactory.java:86)
    at ilog.rules.res.xu.ruleset.impl.IlrXURulesetFactory.createRCERuleset( IlrXURulesetFactory.java:220)
    at ilog.rules.res.xu.ruleset.impl.IlrXURulesetFactory.createRuleset( IlrXURulesetFactory.java:104)
    ... 3 more

This exception indicates that the ruleset parsing has failed because the XOM classes or methods that were used in the rule could not be resolved by the rule engine. This can happen when the XOM in the SSP is not updated with the changes made in the project workspace.

One of the possible reasons is the location of the compiled XOM classes when using ANT to automate the SSP packaging. When you generate the files using the "Repackage XOM for remote DVS testing" wizard, it locates the compiled classes from the "Default output folder" of the XOM project, and creates a build file snippet as shown below:

      <xomClasses>  
       <fileset dir="${eclipse.workspace.dir}/myxom/bin" />
     </xomClasses    >

The "${eclipse.workspace.dir}/myxom/bin" folder can change depending on your XOM project settings for the "Default output folder". This location is used in future SSP repackaging operations, when running the generated build file. If the location of the "Default output folder" changes on the XOM project, make sure to reflect this change in the build file.

For more information, refer to the "Source Tab" section in the Eclipse documentation for Java Build Path. Make sure that "Default output folder" and the fileset under xomClasses are matching.

[{"Product":{"code":"SS6MXF","label":"WebSphere ILOG Decision Validation Services"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":"Installation","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"},{"code":"PF035","label":"z\/OS"}],"Version":"7.1.1.4;7.1.1;7.1.1.1;7.1.1.3","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
15 June 2018

UID

swg21586334

Page Feedback