RSA Federated Identity Manager 4.2 SP1 class loading install issue with fim.jar and deployment script
2 years ago
Originally Published: 2014-12-10
Article Number
000064969
Applies To
RSA Product Set: Federated Identity Manager
RSA Version/Condition: 4.2 SP1
Issue
During an RSA Federated Identity Manager 4.2.1 install and after the deployment script is run, page 71 of the RSA Federated Identity Manager 4.2.1 Installation and Configuration Guide states:

Once the fim-deploy.sh script executes successfully, update the catalina.properties file, common.loader property, load the fim.jar, followed by all FIM related jars as mentioned below.

common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/fim.jar,${catalina.home}/FIM/lib/*.jar.


But the deployment script already edited the properties file with this string:

common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/*.jar

What is the correct setting?


 
Resolution
There was a deployment defect found late in the release, so the correct setting was documented in the RSA Federated Identity Manager 4.2.1 Installation and Configuration Guide.

common.loader=${catalina.base}/lib,${catalina.base}/lib/*.jar,${catalina.home}/lib,${catalina.home}/lib/*.jar,${catalina.home}/FIM/lib/fim.jar,${catalina.home}/FIM/lib/*.jar

This is to ensure that the fim.jar gets loaded first and correctly.