Generally speaking, ODWEK is included under your existing licenses, and there's no restriction on the number of ODWEK Instances you need. Also, you don't need to configure the CMOD server in order to run ODWEK.

Also, it's not advisable to try and split ODWEK from the installer packages - there are common libraries shared between CMOD & ODWEK.

Have three different arsload daemons set up to search three different directories. Using the -t parameter, set up one that launches every 5 minutes, one that launches every 30 minutes, and one that launches every 3 hours.... or whatever schedule meets your needs. If you're using the GUI, there should be a 'sleep' parameter, measured in seconds.

It sounds like a bug that if a resource bundle matches an existing one, that it would try to re-write it -- it should simply record the id number of the matching resource, and then use that in the AG table.

I'd wonder if your documents are somehow slightly different. I've had customers with a 'perfect storm' of situations that led to them having over 80,000 resources in a single Application Group. We were able to retrieve the resources, and use a hash function to determine that there were only about 2000 unique resources, but because of the low default (50) it was extraordinarily unlikely that the exact same style of document would be loaded twice within that 50-load window.

the OnDemand server Fixpack appears to include a bump in the support GSKit version to 8.0.55.12 (which is not available for download from FixCentral ?!?) and includes some ODWEK CGI and ODWEK Java API bug fixes.

Absolutely! Marina solved problems that stumped me for days! Even though we haven't spoken in a few years, I'm sad to hear she won't be there anymore, but I absolutely wish her all the best in her new adventure.

I think I've got it. You've got a field called Load_Date that was set to 't' by default, but then you had to load some old data, and needed to have it reflect the date it was originally loaded, so you set the default to a specific date, then forgot to change it...

I just took a closer look at the XML - maybe the problem is that you're making a folder-related change? As a User Admin, you might not be able to make changes to a folder definition, even if the thing you're changing is specifically a user permission? I don't think you can exempt a user from the maximum number of hits defined at the folder level.