Novell Role-Based Provisioning Module Install Tips, Tricks and Gotchas

A recent install of Novell’s RBPM product, has led to the reminder that documentation often lags behind product development. There are a handful of reasons for this, the main being that when product is being actively developed, the feature set is not fully decided upon. So documenting the current state is an exercise in futility as the features may change very rapidly. Thus documentation is always an after-thought. The last task to be performed.

**NOTE: As with all Tips and Tricks we provide on the IDMWorks blog, use the following AT YOUR OWN RISK. We do not guarantee this will work in your environment and make no warranties***

A recent install of Novell’s RBPM product has led me to remember that documentation often lags behind product development. There are a handful of reasons for this, the main being that when product is being actively developed, the feature set is not fully decided upon. So documenting the current state is many times an exercise in futility as the features may change very rapidly. T hus documentation is always an after-thought. The last task to be performed.

So without further ado, here are some observations. Specifically with regards to using WebSphere for web services.

  1.  AIX is not a supported platform for RBPM. Initially, the IDM 4.0 documentation stated that AIX was a supported platform. We had attempted the install but it never worked and discussions with Novell indicated that AIX was never intended to be a platform option for this version of IDM. It was subsequently removed from documentation in the IDM 4.0.1 release.
  2.  The Java environment variables are very strict. The version of Java that IBM packages with WebSphere 7 is the correct version, IBM J9 VM (build 2.4 J2RE 1.6.0) with Fix Pack 7 or higher. However, there is a step in the documentation that mentions you must apply the unrestricted policy files to JAVA_HOME/jre/lib/security. Failure to do so, results in the master key not being generated as the key size is not the proper size. REMEMBER THIS! This is very difficult to troubleshoot after the fact.
  3. WebSphere uses shared libraries to incorporate jar files with web services. There are several setup steps in the documentation but there are some slight omissions. The java class, commons-logging.jar, is not packaged with the install and must be downloaded manually. This is noted in the documentation, however the additional classes of antlr.jar and jaxb-impl.jar are also missing and must be manually downloaded as well. A simple omission that can cause a great deal of hair pulling and teeth gnashing.

Hopefully these observations prevent anyone from committing a mistake. Good luck with your future installs.