Hi IBM Community,

I'm currently working on configuring an IBM FileNet P8 environment and would appreciate some guidance on setting the maximum file upload size for both IBM Content Navigator (ICN) and IBM Administration Console for Content Engine (ACCE).

Specifically, I'd like to know:

1. For IBM Content Navigator (ICN):

   • Where and how can I configure the max file upload size?

   • Is it done through the navigator.properties file, web.xml, or elsewhere?

   • Do I need to restart the application server (WebSphere/Tomcat) after making changes?

2. For IBM ACCE:

   • Is there a way to limit the size of files uploaded through ACCE (e.g., during document creation)?

   • Are there Content Engine-level configurations (like in the FileNetEngineConfig) that control this?

Additional Context:

• The deployment is on WebSphere, and the max upload limit is currently not enforced, which is a concern for us due to bandwidth and storage restrictions.

Any documentation references or tips from your experience would be greatly appreciated!

Hi Lashan,

Technically, ACCE will only detect content using the event engine after it has been transferred, which means network bandwidth is already consumed by that point.

To avoid this, it makes more sense to place an HTTP server such as IBM HTTP Server (IHS) in front of WebSphere (using plugin-based load balancing), and configure it to limit the request body size according to your requirements. The client(browser) is informed instantly that the size is too big. This approach only works for PUT or POST operations.

In IBM Content Navigator (ICN), you also have the ability to define a request/response filter that can inspect the content before it is sent to the server. This allows you to inform the user early and abandon the upload on the client side. You can try also to utilize the WAF embedded in ICN look at this https://www.ibm.com/support/pages/node/6229174.

For other applications or upload mechanisms, you may need to implement a separate method to inform users that their request is too large to be processed by FileNet or WebSphere. Anyway it make sense to inspect this before it is send to the server (as it will cause bandwidth utilization). 

The described approach by you is not known to me.