Policy simulation fails in Designer with default driver configuration.

  • 3513756
  • 05-Nov-2007
  • 26-Apr-2012


Novell Identity Manager Designer 2.1.1
Novell Identity Manager Designer 3.0
Novell Identity Manager 3.5


While trying to simulate a default driver with extra functionality from a JAR file the simulator fails with a -9131 error stating that it cannot find the function specified in the Identity Manager (IDM) policy. The driver works properly in the IDM engine.


Some of the JAR files that are not essential to the operation of the IDM Engine are not included with Designer by default. They can be taken from the installation of the Engine and added to the Designer install so that they are read and used by going to Designer: Window: Preferences: Designer for IDM: Simulation. In this screen you can add paths where Java Extensions are located.

Create a directory accessible by multiple Designer installations if desired or within one Designer installation to keep everything together. Keep in mind that upgrading or adding additional Designer installations probably will not move these files and configurations by default. Place the JAR files used during the simulation in the directory specified. One directory may exist already and placing the JAR file in there without adding additional extension paths should work as well. These directories are checked at the beginning of each simulation so restarting Designer should not be required.

The IDM 3.5.1 microsoft active directory driver has a rule (error below) that throws this exception when it is reached.

Additional Information

Error: Policy Transformation Failed:

Reason: com.novell.nds.dirxml.engine.VRDException: Code (-9131) Error in vnd.nds.stream:/null/Driver+Set/DRIVERNAME/InputTransform:42 : Error evaluating XPATH expression'token-xpath("jadutil:translateFileTime2Epoch($current-value)")' : com.novell.xml.xpath.XPathEvaluationException: function'jadutil:translateFileTime2Epoch' not found.