HAPPY NEW YEAR 2017

Identity And Access Management - Rajiv Dewan

OIM Deployment Manager Import DDM Exception Error

Sometimes we see a common error (refer below screenshots) while import the XML through Deployment Manager. On the screen it shows error: "Error encountered while reading the file."





When you see the server logs, you'll find below lines:

DDMException: Version m.n.o is not accepted by DDM Version a.b.c



This error comes due to DDM version mismatch. Error message tells you the DDM version of OIM Server and DDM version of XML. As per screenshot:

OIM Server DDM Version: 2.0.2.1
XML DDM Version: 11.1.2.2.0

To resolve this issue, you can edit the XML file manually and replace the existing DDM version with OIM Server's DDM version. It should look same as below screenshot:



On replacing the DDM version, save the XML file and try to re-import. It should work (always worked for me) ;)

OIM Coding Standard: Do's and Don'ts


I am not an expert but here are few Do's and Don't s based on my experience:

Do's

  • Make use of Loggers
  • Use different level of Logger Level based upon data you want to print
  • Each method must have the "Entering" and "Exiting" statements
  • Must print atleast "User Login" in Entering Statement
  • Use organization specific package and class names
  • Maintain minimum jar files
  • Make minimum use of class variables
  • Make minimum OIM API instances or Database Connection
  • Each class and method must have Java Comments
  • Make use of Try/Catch and Throws/Throw for Error Handling
  • Use meaningful names for variables and java class
  • Make use of Lookups, System Properties for storing configurable parameters
  • Close the OIM API Instances and Database at the end of Operation
  • Must print the error message before throw statement and inside catch block


Don't:

  • Do not hard code anything
  • Do not use System.out.println in Java Code
  • Do not print password in Java Code