XML Text Search Index - Where is std.html-config?

[Former Member]

Hello,

I have inherited an eSourcing system.  I did not install it and have not supported an existing system before now.  ...so my question my seem pretty basic.

We are receiving an error, "XML Extract Skipped because Database Locks Exists on Text Search Index...."  Our DBA tells us that MS SQL is not enabled for text search.

I am guessing that it is best, performance-wise, if indexing is enabled.

In my research, I found that std.html-config should be configured to exclude parts of XML and HTML files from Indexing.  However, I do not find this file anywhere our servers.  The document "Excluding Parts of XML and HTML Files From Indexing" says the file is in <TREX-installation_directory>\Lexicon\std.html-config .  I also cannot find the Lexicon directory.

So . .. my questions:

Should text search enabled in MS SQL for eSourcing?

If so, should certain parts of XML & HTML files be excluded?

If so, where is the file <TREX-installation_directory>\Lexicon\std.html-config ?

Thanks in advance,

Bruce Morgan

[former_member89217 · Accepted solution]

Hi Bruce,

There are several topics here that are of concern. When you say your DBA tells you that text search is not enabled on MS SQL.  Do you suggest that  you are running on a SQL SERVER DB?  That should not be the case as  this application is supported only on DB2 and Oracle.  Both have text search support.  The references to TREX are also not applicable. The database native search feature actually replaced TREX implementation in sourcing.   It seems the current database error needs to be looked at by the DBA.  Failure to fix that will reduce the functionality and accurracy of the full text search feature within the application.  The application will still function, but you will not be able to reliably use the text search feature.

Regards,

Gary

[Former Member · Accepted solution]

Gary, thanks for the response!

As I started out, my questions may seem pretty basic.  I should add ... also offbase or incorrect. 😞

The database is DB2.  Most all of our other systems are MS SQL, and it is the same DBAs for both so I misspoke.

TREX is no longer used.  I must have been looking at old documentation.  Good to know.  Thanks again.

I will request the DBAs to enable text search indexing.

Do I need to worry about "Excluding Parts of XML and HTML Files from Indexing" or is this handled by later releases of sourcing?

Thanks again for your help!

Regards,

Bruce.

[former_member89217 · Accepted solution]

Hi Bruce,

No problem on the questions being offbase. Glad we are back on the same page.  You do not need to configure anything to exclude XML/HTML.  The application indexes both the business documents themselves and the attachments that are part of them.   As you have already witnessed, there are some background tasks that run to update the indexed data.   The setup of the text search can be a little tedious on DB2 but the IBM documentaion on this if followed completely will get you there. I'm a bit surprised you would have a system running that had expected the text search enabled but it wasn't.  Is it possible this system was "moved" to its present landscape and not actually built/updated where it is?

Regards,

Gary

[Former Member · Accepted solution]

Hi Gary,

Do you recommend me giving this IBM DB2 guide "Text Search Guide" to our DBA to follow (ftp://ftp.software.ibm.com/ps/products/db2/info/vr101/pdf/en_US/DB2TextSearch-db2tse1010.pdf)?

This sourcing system was just upgraded the end of July by SAP since we did not have the in-house expertise to do it.  Maybe they left out a step?

Thanks again!

Bruce.

[former_member89217 · Accepted solution]

Do you happen to know what version you were on and what version you have now?

Thanks,

Gary

[Former Member · Accepted solution]

e-Sourcing 5.1/CLM 2.0 to e-Sourcing 9.0/CLM 9.0

[former_member89217 · Accepted solution]

OK this explains a few things.... in 5.0 there was no DB native text search.  Upgrading to 9.0 would introduce that.  However, the upgrade should fail if text search is not enabled in the database.  My guess is that it is enabled but there is a problem with the indexing.  Still a DBA function at this point. If the DBA is unable to address the problem you may need to file a support ticket and include the logs from the app when the failures occur. 

Regards,

Gary