Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Nils Engerby

Pages: [1]
MP Server / arsdoc delete vs. bulk_delete
« on: March 18, 2021, 09:47:16 AM »
Does anyone know the difference between arsdoc delete and its bulk siebling that was introduced in

The description of the bulk_delete function merely says "Use to delete a large number of documents from the system" and the command parameters are slightly different. No explanation of what the real difference is, and why would you ever want to not use the bulk_delete function?

We need to delete millions of index records from an application group and I started off using the regular arsdoc delete which totally hogged the system. Deleting 100,000 docs could run for hours.

I did one small test with bulk_delete and it was lightning fast which made me wonder if it takes some undesired shortcuts, like not deleting annotations. Haven't mustered up the courage to use it again without knowing exactly what it does and does not do ...

Appreciate any insights.


OD/WEK & JAVA API / Re: Searching mapped folder fields with multiple values
« on: December 04, 2019, 01:25:51 AM »
Sorry for late response, been a bit busy after upgrade from 9.5 to 10.1 recently ...  :)

Our front-end application currently uses a combination of folder field and application group field search. If a folder contains multiple ags, folder search is used. If a folder contains a single ag, ag seach is used. The logic is obviously different for these two paths and is of course bound to break if we add a second ag to a single ag folder.

The search in question works with the single ag folder but we must move away from that and only use folder search.

OD/WEK & JAVA API / Re: Searching mapped folder fields with multiple values
« on: November 06, 2019, 09:24:43 AM »
Thanks, RR. The filtering method has been used successfully but now the result sets are growing too large.
A typical search looks for a customer number, a date range and a variable number of document types. The "document type" is a mapped field.
Without the document type(s) in the search, the result could easily be tens of thousands, which after filtering could boil down to a few dozens.

OD/WEK & JAVA API / Re: Searching mapped folder fields with multiple values
« on: November 05, 2019, 03:19:22 AM »
Thanks, Darrell.
That approach would be possible for just a few values but the requirement is more than that.
I forgot to mention in my original post that they are using the ODWEK Java API at version They have now made a workaround and perform a separate search for each value, which of course isn't very efficient.
Maybe this is a candidate for the wish list for the product. I have often missed the ability to select multiple search values in the dropdowns in the client as well.

OD/WEK & JAVA API / Searching mapped folder fields with multiple values
« on: November 04, 2019, 03:09:50 AM »
The development team maintaining our CMOD frontend has run into a problem with searching folder fields where the underlying application group(s) have mapped values.
Some customers want to query such fields for multiple values but the only valid search operator is "equal". Also, they want to search using the database values, not the displayed values.
A typical use case is searching for all documents with certain document types (e.g. "Invoice", "Insurance Policy" etc) for a certain period.
I have tried adding a folder field with the "Internal" attribute which enables searching by database value, but it is still limited to the "equal" operator.

Any suggestions (preferrably not involving raw SQL search) would be greatly appreciated.


Announcements & News / Re: IBM CMOD Fix Pack v10.1.0.4 Released
« on: October 22, 2018, 08:11:15 AM »
Great news with Hitachi Content Platform finally being supported.
Does anyone have a technical description of how this support is implemented?

MP Server / Re: ARSLOAD AFP load error
« on: October 11, 2012, 06:56:06 AM »
Did you, by any chance, forget to transfer the index file in ASCII format this time?


MP Server / Re: ARSLOAD AFP load error
« on: October 04, 2012, 06:05:06 AM »
Your trace shows that the load program still expects an ACIF index file. See if it makes a difference if you put the load file name after all other options:

"C:\Program Files\ibm\OnDemand for Windows\bin\ARSLOAD.EXE" -f  -I atp-20tapp003 -g NAFSAG -a NAFSAPP -X G "D:\OnDemand_data\arsdoc_get.12366.NAFSAG.NAFSAPP"

You could also temporarily change the indexer setting in NAFSAPP to Generic, but remember to backup any ACIF parameters in the app and restore the original indexer settings after you are done loading.


MP Server / Re: ARSLOAD AFP load error
« on: October 03, 2012, 09:11:43 AM »
Joining the party late...  :)
The error message in the first post indicates that the AG is defined with ACIF indexing so the load program expects an index file in AFP format.
The index file produced by arsdoc get is in the Generic indexer format so you must use the -X G flag in your arsload command.

OD/WEK & JAVA API / Re: OnDemand 8.5, IIS & arswww.cgi
« on: March 23, 2011, 08:23:08 AM »
It's been a while since you asked, but since there are no responses...

I have arswww.cgi running in a new development system with exactly the same setup. The following page was very useful when configuring IIS:

Giving permissions to the built-in IUSR account seemed to be the key to your issue.

The version of the CGI hangs if you use POST requests from your web pages. This is solved in but a new bug was introduced which causes document retrievals to fail if the folder name is obtained from a cookie and the folder name contains accented characters. I have an open PMR for that.

Apart from that, everything seems to be working ok. We will upgrade our production system to this environment as soon as the accented character problem is washed out.

MP Server / Re: Setting up TSM for use with OD
« on: June 03, 2010, 07:12:26 AM »
A word of caution if you install the OnDemand client on the same machine as TSM. I recently did that in my lab environment and when I uninstalled the OD client (version it blew my TSM installation to pieces. The OD client uninstall dropped the whole registry branch below HKLM\SOFTWARE\IBM\ADSM and probably did some more nasty things since restoring this registry branch was not enough to cure the TSM server...

Pages: [1]