IBM Unable to add Centera Device in FileNet Content  Engine - United States  TECHNOTE (TROUBLESHOOTING)

PROBLEM(ABSTRACT)
 Errors received clicking "Test Connection" when configuring Centera Device in FileNet Enterprise Manager 

SYMPTOM
After entering configuration information in FEM Fixed Content Device Wizard the following error is received: 

File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ 

 

The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path). 

 

Error in the p8_server_error.log: 


2011-06-06T18:54:57.245Z 00C900C9 ENG FNRCC0110E - ERROR method name: initialize principal name: P270IH Global Transaction: true User Transaction: false Exception Info: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed.
com.filenet.api.exception.EngineRuntimeException: FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. failedBatchItem=0 errorStack={

Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path) failedBatchItem=0

Caused by: java.lang.UnsatisfiedLinkError: FPLibrary (Not found in java.library.path)


CAUSE
Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded. 


ENVIRONMENT
IBM Websphere



DIAGNOSING THE PROBLEM
Following error is received when "Test Connection" is clicked: 

File = .\FnFCSMGR.cpp, Line = 359, Rev.= $Revision: 1.20 $ 

 

The [initialize]operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenterFCP(0)]failed. FPLibrary (Not found in java.library.path).


RESOLVING THE PROBLEM
After making any changes to the setCenteraLibPath.sh or setCenteraLibPath.bat file restart WebSphere from the IBM console or the changes will not be detected.





Cross reference information Segment Product Component Platform Version Edition Enterprise Content Management FileNet Content Manager Content Engine 
HISTORICAL NUMBER
 41550
180
000

Question: P8 CPE 5.2.1 error:  FNRCC0110E - ERROR FixedContentProviderCache.getProvider failed to init provider 

New P8 CPE 5.2.1 install does not see the Centera Fixed Storage. The following error is returned:

FNRCC0110E: CONTENT_FCP_OPERATION_FAILED: The [initialize] operation on the fixed content provider [com.filenet.engine.content.fcprovider.centera.CenteraFCP(0)] failed. FPLibrary (Not found in java.library.path)

What is the cause?

Answer: Changes made to the setCenteraLibPath.sh or setCenteraLibPath were not picked up by the WAS startup script. The WAS Content Engine instance was restarted from within the WAS console and not from the command line. In this Instance the setCenteraLibPath.sh file was added to the setupcmdLine.sh file but was not recognized . This caused the CenteraSDK path to not be loaded.