Troubleshooting
Problem
FileNet Content Engine Content Java API Compatibility Layer custom applications stops working when collocated with Workplace XT or FileNet Application Engine
Symptom
Custom applications using the FileNet Content Engine 4.x Java API Compatibility layer using the CE Web Services Transport stops working when collocated with Workplace XT or FileNet Application Engine.
The following errors appear in the custom application:
com.filenet.api.exception.EngineRuntimeException;Access to the Content Engine was not allowed because the Content Engine API library or the Web Service Interface (WSI) Listener could not find the required security context information. Expected credentials were not found in the security context. [Code=null]; OMFC/TheNetwork/NoOp//SECURITY_INVALID_CREDENTIALS com.filenet.wcm.api.InvalidCredentialsException
Cause
This issue can occur if the respective application uses the CE Web Services Transport and does not explicitly specify the FileNetP8WSI specific JAAS stanza in the wcmapiconfig.properties file used by the custom application, for example by setting:
jaasConfigurationName=FileNetP8WSI
Leaving this entry blank or having it configured for
jaasConfigurationName=FileNetP8
may work fine in conjunction with the sample jaas.conf.WSI JAAS configuration file. However, the Workplace XT or Application Engine install instructions advise using the jaas.conf.<J2EE_AppServer> file (e.g. jass.conf.Websphere), which is included with the Content Engine client installation. The latter JAAS configuration modifies the FileNetP8 JAAS stanza, and thus requiring the Content Engine 4.x Java API Compatibility layer applications that use CE Web Services to explicitly set the JAAS configuration stanza to FileNetP8WSI.
Resolving The Problem
In the wcmapiconfig.properties file used for the compatibility API program, add the following line:
jaasConfigurationName=FileNetP8WSI
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21625078