Hi All,

Here is the latest update about the issue.
I had a word with support guys and as per them FTS doesn't fully work with
CMDB or Asset.

Regards,
RK


On Tue, Aug 28, 2012 at 11:04 AM, Goodall, Andrew C <ago...@jcp.com> wrote:

> **
>
> We’ve had a long running issue open with BMC Support (ISS03993466) that
> BMC ARS Core Engineering team have been working on with the ITSM module
> engineers.****
>
> ** **
>
> Come to find out ARS Engineers designed FTS where by even if “Index for
> FTS” = None on the field but there is a value in the property “Full Text
> MFS Category Name” then it will still be indexed – according to them that
> is “working as designed”.****
>
> ** **
>
> But apparently the ITSM side of the house were unaware of that – so
> consequently inadvertently indexed fields that do not need to be indexed.
> Additionally any join forms carry forth the “Full Text MFS Category Name”
> value on the field from the originating form – so as a result they too will
> also get indexed.****
>
> ** **
>
> This all adds up to a big mess and slow performance of FTS. How FTS ever
> passed real QA testing for enterprise customers is beyond me.****
>
> ** **
>
> Fix: remove “Full Text MFS Category Name” value on fields that do not need
> to be indexed; remove the same on all join forms; additionally remove work
> log tables from being indexed.****
>
> ** **
>
> Warning these can only be changed in base mode currently – just another
> thorn.****
>
> ** **
>
> This reduced our FTS indexing time and collection folder substantially.***
> *
>
> ** **
>
> Attached is the spreadsheet provided by ITSM engineers on what “should be”
> indexed. This doesn’t help you with CMDB questions – you might want to open
> an issue with Atrium engineering if you are experiencing a similar issue
> what find out what “should be” indexed on that side.****
>
> ** **
>
> Regards,****
>
>  ****
>
> *Andrew C. Goodall*
>
> Software Engineer****
>
> Development Services****
>
> ago...@jcpenney.com****
>
> *jcpenney*
>
> 6501 Legacy Drive****
>
> Plano, TX 75024****
>
> jcp.com****
>
> ** **
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@arslist.org] *On Behalf Of *rahul2007k...@gmail.com
> *Sent:* Tuesday, August 28, 2012 10:35 AM
> *To:* arslist@arslist.org
>
> *Subject:* Re: CMDB Fields for FTS indexing****
>
> ** **
>
> ** Thanks Nathan we are also keeping eye on the performance issue related
> FTS issue.****
>
> ** **
>
> Anyone else ever faced this issue please reply.****
>
> ** **
>
> Regards,****
>
> RK****
>
> On Mon, Aug 27, 2012 at 2:06 PM, Nathan Aker <nathan_a...@mcafee.com>
> wrote:****
>
> ** ****
>
> Not directly on topic, but we’ve basically put a moratorium on any
> additional indexing of fields by the FTS engine as it seems to have more
> than enough trouble handling the load from the base application
> functionalities with 7.6.04.   Careful how much you ask it to index, I know
> we’re not alone as I’ve seen a number of posts from others having to monkey
> with the FTS configuration to get this beast to simply do the jobs BMC has
> asked it to do in the 7.6.04 ITSM apps.  We’ve got all FTS plugins now
> running on one server per BMC direction and still have hiccups from time to
> time with it getting choked up.****
>
>  ****
>
> Nate.****
>
>  ****
>
> *Nathan Aker*
> ITSM Solution Architect****
>
> *McAfee, Inc.*****
>
>  ****
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *rahul2007k...@gmail.com
> *Sent:* Monday, August 27, 2012 1:55 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: CMDB Fields for FTS indexing****
>
>  ****
>
> ** Hi,****
>
>  ****
>
> Has anyone encountered the same kind of issue before with FTS enable on
> CMDB fields.****
>
>  ****
>
> Regards.****
>
> RK****
>
>  ****
>
> On Sun, Aug 26, 2012 at 5:31 PM, rahul2007k...@gmail.com <
> rahul2007k...@gmail.com> wrote:****
>
> Hi All,****
>
>  ****
>
> Please let me know if anyone has done FTS indexing on CMDB fields like CI
> ID, CI Name etc.****
>
> I have currently enable FTS indexes on above fields on
> BMC.Core:Base_Element form but when ever i search newly created CI I am not
> able to search it until i re index whole FTS .****
>
>  ****
>
> I have seen that there are some FTS limitation for data re-indexing on
> join form and need to schedule the data scan for those join forms which
> causes very high CPU & memory utilization.****
>
> Also the Best practice development mode doesn't allow to modify the fields
> on join form and i need to switch base development to modify those forms &
> its property which i think is not a good idea.****
>
>  ****
>
> I am not sure how to achieve this on CMDB forms as everything is based on
> join form structure and its very difficult to enable FTS on all the CMDB
> classes.****
>
>  ****
>
> Thanks,****
>
> RK****
>
>  ****
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ ****
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ ****
>
> ** **
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ ****
>
> The information transmitted is intended only for the person or entity to
> which it is addressed and
> may contain confidential and/or privileged material. If the reader of this
> message is not the intended
> recipient, you are hereby notified that your access is unauthorized, and
> any review, dissemination,
> distribution or copying of this message including any attachments is
> strictly prohibited. If you are not
> the intended recipient, please contact the sender and delete the material
> from any computer.
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Reply via email to