Designer 4.6 simulator cannot simulate ECMAScript anymore

  • 7019014
  • 18-May-2017
  • 18-May-2017

Environment

NetIQ Identity Manager (IDM) Designer 4.6


Situation

Designer 4.6 throws an error when simulating ECMAScirpt in its Simulator, where prior versions such as 4.5 SP5 do not.  This happens regardless of the presence of a link to the ECMAScript object on the driver config object. pr the presence of an XML namespace declaration as part of the policy XML tag.  The error from the Simulator follows when a call to ECMAScript is reached:

java.lang.NullPointerException
Code(-9010) An exception occurred: java.lang.NullPointerException
  at
com.novell.xsl.extensions.CommonScriptFunctionImpl.getScope(CommonScriptFunctionImpl.java:432)
  at
com.novell.xsl.extensions.CommonScriptFunctionImpl.invoke(CommonScriptFunctionImpl.java:92)
  at com.novell.xml.xpath.FunctionCall.evaluate(FunctionCall.java:90)
  at com.novell.xml.dom.DOMEvaluator.evaluate(DOMEvaluator.java:89)
  at
com.novell.nds.dirxml.engine.rules.RuleDynamicContext.evaluateXPath(RuleDynamicContext.java:176)
  at com.novell.nds.dirxml.engine.rules.TokenXPath.expand(TokenXPath.java:72)
  at com.novell.nds.dirxml.engine.rules.Arg.evaluate(Arg.java:469)
at com.novell.nds.dirxml.engine.rules.DoReformatOpAttr.apply(DoReformatOpAttr.java:94) at com.novell.nds.dirxml.engine.rules.ActionSet.apply(ActionSet.java:182) at com.novell.nds.dirxml.engine.rules.DirXMLScriptProcessor.applyRules(DirXMLScriptProcessor.java:310) at com.novell.idm.simulation.internal.wizards.PolicyProcessor.doTransform(Unknown Source) at com.novell.idm.simulation.internal.wizards.PolicyProcessor.startTransform(Unknown Source) at com.novell.idm.simulation.internal.wizards.ProcessingWizardPage.startTransform(Unknown Source) at com.novell.idm.simulation.internal.wizards.ProcessingWizardPage.access$0(Unknown Source) at com.novell.idm.simulation.internal.wizards.ProcessingWizardPage$SimThread.run(Unknown Source)


Resolution

This is a known issue and is reported via Bug# 1030511 which is scheduled to be resolved as part of IDM Designer 4.6 SP1.  Assuming no other errors with the ECMAScript the code should run properly in the IDM engine which does not exhibit this same problem.

Cause

Bug# 1030511

Bug Number

1030511

Feedback service temporarily unavailable. For content questions or problems, please contact Support.