01-16-2012 07:48 PM
Would anyone know the best place to find documentation related to how IDOL works within the TRIM environment? I see there are three additional windows services devoted to it. So far my testing has gone well, but I'm not used to it and am looking for some of the configuration documentation. Specfically around: stemming, hyphenChars, augmentseparators, indexnumber, stoplist, and the rest of the configuration file.
I also noticed that when I register a document and it's processed by the event server, it can take up to 2 minutes to become available in the document content search. If I manually reindex through the TES then it's instantly available for a search. Anyone know why?
Also how do you disable the log from showing every DCI query?
01-16-2012 08:41 PM
There's always been a delay before processing events with the event processor, I expect its still the same in TRIM 7 even with the new design of the indexer.
Think the registry key is
I've done a fair bit of looking online for information on the IDOL engine but couldnt find much either, and the documentation provided by HP has been minimal.
If I find anything I will post it
01-16-2012 09:12 PM
I'm especially interested in this as well.
I would like to know what type of IDOL HP have bundled with Trim. With ISYS we got a cut down version of the product that did DCI and thats it. If you wanted the advanced features ISYS offered that was a seperate purchase.
Is this the case with IDOL, we get a basic DCI or are we getting additional features. If we don't get the full feature set is there a posibility to upgrade it with the Trim license rather than a seperate purchase.
01-17-2012 05:21 AM
The delay for content indexing (actually all events) is now configurable via Enterprise Studio - 120 seconds is the default value.
The IDOL shipped with TRIM is cut down - but mostly from the point of view of non-content indexing functionality and only "cut-down" by not having some of the 500+ features enabled in the license. You can replace it with a standard IDOL implementation, but it is not a simple product to use - the basic IDOL Administrator course is a full-on 4 day session. I suspect this is why the IDOL documentation does not ship with TRIM - just too much functionality for people to get wrong!
01-17-2012 12:51 PM
It is possible for TES to report that IDOL has finished processing something while IDOL is still working.
This can occur when creating a new IDOL instance (TES will report the operation is finished before IDOL has created the new instance) or during a Reindex (TES will report the reindex is complete, while IDOL has yet to process all of the documents).
This issue is due to the way TRIM Enterprise Studio communicates with the IDOL server, and the way the IDOL server processes incoming requests.
It is difficult for the administrator to directly check the IDOL server to see if operations have actually completed. It is suggested that an administrator waits for a short period after creating a new IDOL instance before performing an reindex. Similarly, it may take some time after a reindex has “completed” for all of the records to appear in a DCI search.
I'm still interested in the other settings asked about. Can't easily find that documented anywhere on the web.
01-17-2012 09:26 PM
It would appear that IDOL is a black box for the DCI, and if there are problems, all an administrator can do it perform a full rebuild of the index?
01-17-2012 10:10 PM
The post-release notes mention that those features (check and optimize) don't function, but also doesn't indicate if they intend to be fixed. I'd assume they do. The reindex function does work however.
01-29-2012 04:20 PM
I put up that tech note.
I accidentally made it customer visible when it was supposed to be internal only (according to the higher-ups), but glad I made it public. Looks like it's answered a few questions already. :)
If you guys need any help and have any specific questions, log a case.
Paul (Burkle) and myself have had enough IDOL training and are familiar enough with the implementation to answer most basic questions.
NOT A HP EMPLOYEE
08-20-2012 08:29 AM
With IDOL Service. AS with Space limitations by design in VM environment, How to relocate the index to new ISCSI LUN without complete uninstall and reinstall.
With a VM Guest Server we store user data separate from server images. This would also include DCI DATA. There should be a way to move a DCI to a Shared Volume or at minim a different VOL then primary install location of services applications.
In TES we only have the option to create new IDOL index and no choice to the location of it.
So I now ask how to move a Location of the IDOL Storage/Index Locations ?
08-20-2012 04:43 PM
This is all configurable in the IDOL config files.
See attached tech note.
NOT A HP EMPLOYEE
02-14-2013 08:28 PM
We recently upgraded to TRIM 7.2.1 and on build 3519. We don't have a huge database and stats show that there were about 7600 records added since the start of the year.
However the TRIM server has regular very high volume disk read/writes.
Looking at the TRIM server CPU, Memory, and Disk statistics – the server seems to go into a high load state every 10-15mins, resulting in very high disk read/writes which causes the lag. At about the same time there is a 34GB lag in the storage replication. Normal lag is a few hundred MB.
We were doing a DR Exercise and there was a 34GB lag between Production and DR storage replication but there were only 77 documents added to TRIM on that day. Has anyone have any thoughts on this?
02-14-2013 11:30 PM
Define "huge", for one 1GB may seem huge, for others 1PB may still be considered small.
Use Windows Resource Monitor to pinpoint which file operations take place. From there you can identify which application is.
If IDOL is active on that server, then it may be a likely candidate for the high amount of disk access. IDOL writes a new index file on each commit in the dynterm folder which each have a maximum size of ~12GB and then switches over.
Still a long way from your 34GB, but getting closer than any of the other TRIM components.
Since new index is built up in parallel, your DR solution may consider this a new file an try to sync the entire file size instead of just the delta between the old and new index.
You can check the IDOL logfiles to have better understanding of what it's doing.
Analytics & Data Management
Application & Business Services
HP Enterprise Services