000029200 - RSA Federated Identity Manager 4.2 SP1 class loading install issue with fim.jar and deployment script

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support on Feb 1, 2018
Version 3Show Document
  • View in full screen mode

Article Content

Article Number000029200
Applies ToRSA Product Set: Federated Identity Manager
RSA Version/Condition: 4.2 SP1
IssueDuring 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?



 
ResolutionThere 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.

Attachments

    Outcomes