Troubleshooting
Problem
When uploading large files to IBM FileNet Content Engine via FileNet Enterprise Manager (FEM) or archiving via IBM Content Collector (ICC), the upload fails with SECURITY_ANONYMOUS_DISALLOWED.
Symptom
Errors in the application server log, FEM and the ICC P8 Collector log all report: SECURITY_ANONYMOUS_DISALLOWED: Anonymous users aren't allowed access to the Content Engine.
Cause
The symptom can be a valid security issue. But if smaller files upload successfully, then the cause can be that content is being broken into several chunks causing too many round trips to occur during the upload. Basically the authentication for the user times out during the upload causing the SECURITY_ANONYMOUS_DISALLOWED error to be generated and the upload to fail.
Diagnosing The Problem
If all documents created or archived generate SECURITY_ANONYMOUS_DISALLOWED the error could be reporting a valid security issue. Validate object store and file store security.
If smaller files upload and only larger files generate the error, enable tracing on the Content Engine for Content Storage, EJB and Error. The errors are also seen in the web application server logs and if ICC is used, the error will also appear in the ICC Collector logs.
Resolving The Problem
Increase the values for Content Retrieval and FileNet.Content.GetBlockSize KB to 5120K. This will increase the speed of the uploads by reducing the number of round trips. Note that care should be taken to test increasing the parameter values since an increase from the default setting (1024K) increases the memory footprint on the Content Engine server and client. Too many concurrent large document creations and retrievals might cause memory contention. Always make changes in a Development or Test environment before Production.
The instructions below can also be found in the P8 Performance Tuning Guide:
Adjusting the Content Retrieval Limit parameter:
- Log on as object store administrator.
- Expand the Sites node.
- Right-click a site, and select Properties.
- Go to the Content tab.
- Adjust the Inline Content Retrieval Limit (kilobytes) field.
- Click OK or Apply when you are done.
Adjusting the Put/Get Block Size parameters when an application server hosts the Content Engine client
- Place these lines in the filenet.properties file:
- FileNet.Content.PutBlockSizeKB=1024
- FileNet.Content.GetBlockSizeKB=1024
- Save the file to the following location, for example:
- WebSphere – C:\Program Files\IBM\WebSphere\AppServer\profiles\ your_profile
- WebLogic – C:\bea\user_projects\domains\your_domain
- NOTE This location corresponds with the directory in which you start the application server.
- Restart the web application server.
Adjusting the Put/Get Block Size parameters when the Content Engine client is a stand-alone Java application
- For stand-alone Java client applications, a switch needs to be applied to the application executable. For example: java.exe –DFileNet.Content.PutBlockSizeKB=1024.
Related Information
Was this topic helpful?
Document Information
Modified date:
17 June 2018
UID
swg21578642