|Applies To||RSA Federated Identity Manager (FIM) 2.5|
RSA ClearTrust Agent 3.5.2 for BEA WebLogic
Microsoft Windows Server 2003 SP1
|Issue||How to run RSA Federated Identity Manager (FIM) 2.5 as a Windows services|
Windows services for RSA Federated Identity Manager (FIM) do not start
Enabling debugging on the Windows service as described in the Configuring RSA Federated Identity Manager 2.5 as a Windows Service shows an exception error the debug log:
at java.lang.ClassLoader.defineClass ......
|Cause||Some customization has been done to the FIM server to allow it to also work with a ClearTrust WebLogic agent in carrying out this process the CLASSPATH has been modified and is no longer the default values as originally configured when FIM was installed. The INSTALLSERVICE option takes the original default FIM CLASSPATH value when the service is added to Windows.|
In this specific example the customization was to add an RSA ClearTrust WebLogic agent to the system; however the same symptom would occur for any other similar product. This is because the ClearTrust JAR file is required for the actual startup of WebLogic since it is part of the WebLogic SSPI system (see the BEA web site at http://e-docs.bea.com/wls/docs81/dvspisec/ for more information about SSPI).
|Resolution||When the Windows service is created a series of small utility files are generated which contain information used as the Windows service attempts to start. We must alter the <INSTALLDIR>\rsaappserver\bin\svc-classpath to include an extra CLASSPATH value.|
In the following example, RSA ClearTrust Agent 3.5.2 for BEA WebLogic was installed to c:\RSA\wl8agent and FIM installed at c:\RSASecurity\FIM25
- Edit the file c:\RSASecurity\FIM25\rsaappserver\bin\svc-classpath
- Add the value c:\RSA\wl8agent\lib\rsawl8agent.jar to the start of the line
- Save the file
The service should now start correctly.
NOTE: See the solution regarding How to run RSA Federated Identity Manager (FIM) as a Windows Service for details regarding the patch RSA Security has issued to allow RSA FIM 2.5 to run as a Windows Service. Also, note that the last page of the instructions supplied in this patch give details on how to enable debugging of the service which allows diagnosis of this type of issue.
Also, see the solution regarding How to run RSA ClearTrust Agent 3.5.2 for BEA WebLogic on RSA Federated Identity Manager (FIM) 2.5.
|Workaround||RSA Federated Identity Manager (FIM) processes have been added as a Windows service using the configtool INSTALLSERVICE command|
RSA ClearTrust Agent 3.5.2 for BEA WebLogic installed to protect RSA Federated Identity Manager (FIM) services
|Legacy Article ID||a27914|