I am trying to implement a very simple use case in an IBM FileNet P8 (5.5.x) environment:

Restrict a folder to a maximum size limit (MB/GB) in ACCE.

The expectation is that once the folder reaches the defined size, any further document additions should be blocked or rejected with a clear exception or message.

However, after thorough analysis, I am unable to find any feasible or supported solution to achieve this:

• ACCE / ICN do not provide any native folder-size or quota configuration.

• Change Preprocessors cannot reliably access the actual content size of a document before it is persisted.

• Event Action Handlers, while able to read content size, execute after commit, making true enforcement difficult and requiring cleanup or rollback logic.

• There is no documented IBM best practice or sample implementation for folder size enforcement.

At this point, the requirement appears deceptively simple but not realistically achievable using supported FileNet mechanisms.

Questions to the community

• Has anyone successfully implemented folder size restrictions in ACCE or ICN?

• Are there architectural patterns or external enforcement strategies recommended by IBM?

Any guidance, confirmation, or real-world experience would be greatly appreciated.

------------------------------
Wasif Khan
------------------------------

It is surely doable as an ICN plugin, but that would not stop other clients from filling up. That would be bad design. Use sync event actions.

BR,

Gerold

------------------------------
Gerold Krommer
Managing Director
The Document Content Profesionals, G.m.bH
Wien
+436602408515
------------------------------

Original Message:
Sent: Tue December 16, 2025 02:40 AM
From: Wasif Khan
Subject: Is It Possible to Restrict Folder Size in IBM FileNet ACCE? No Feasible Solution Found

I am trying to implement a very simple use case in an IBM FileNet P8 (5.5.x) environment:

Restrict a folder to a maximum size limit (MB/GB) in ACCE.

The expectation is that once the folder reaches the defined size, any further document additions should be blocked or rejected with a clear exception or message.

However, after thorough analysis, I am unable to find any feasible or supported solution to achieve this:

• ACCE / ICN do not provide any native folder-size or quota configuration.

• Change Preprocessors cannot reliably access the actual content size of a document before it is persisted.

• Event Action Handlers, while able to read content size, execute after commit, making true enforcement difficult and requiring cleanup or rollback logic.

• There is no documented IBM best practice or sample implementation for folder size enforcement.

At this point, the requirement appears deceptively simple but not realistically achievable using supported FileNet mechanisms.

Questions to the community

• Has anyone successfully implemented folder size restrictions in ACCE or ICN?

• Are there architectural patterns or external enforcement strategies recommended by IBM?

Any guidance, confirmation, or real-world experience would be greatly appreciated.

------------------------------
Wasif Khan
------------------------------