CA Service Management

  • 1.  SDM > Custom CABI report

    Posted 01-11-2016 11:37 AM

    Using WSP, we made a custom "zAmbiente" Table and a SREL attribute "zAmbiente" on the NR object.This adaptation has worked and is being used on our environment.

     

    Now we are trying to make a report using Designer / WebI to list all CIs and their zAmbiente attributes.

     

    First, we created a custom universe listing the "NR" and "zAmbiente" objects.

    We enabled "ANSI92" and "SORT_JOINS_BY_QUERY_OBJECTS" on that universe as stated on

    http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec605391.aspx

     

    After applying the relationship between the 2 objects (screenshot1), we looked at the result query on WebI (screenshot2).

    The problem is that the left join does not seem to be working, as the result lists all CIs and all zAmbientes - the ON clause does not work.

     

    We tried hardcoding the left join SQL in several ways, and none of them seemed to be working as intended. We want the report to show the CI, even if it does not have any zAmbiente related to it (hence the left join being used).

    Any ideas on how to make that report work?

     

    My guess would be that CABI works with SDM's object layer and not its database, so the query passed is understood as Majic not pure SQL.


    Screenshot1.jpg

     

    Screenshot2.jpg



  • 2.  Re: SDM > Custom CABI report

    Broadcom Employee
    Posted 01-11-2016 02:17 PM

    Hello Erico,

     

    Maybe a simple way would be to create an attribute alias like this techdoc? http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec581824.aspx

     

    The doc was about cr object, you would have to change it to nr.  Hope this helps

     

    _R



  • 3.  Re: SDM > Custom CABI report
    Best Answer

    Posted 01-12-2016 06:33 AM

    Thanks Raghu, that worked!

    After the creation of the alias / adding of the Object  to the Universe the report worked as intented.

     

    To be honest I am not totally happy with this method because it is a workaround to make SDM handle the attribute, not CABI.

    The use of aliasing might be the only resource we have to allow a proper integration with CABI.



  • 4.  Re: SDM > Custom CABI report

    Broadcom Employee
    Posted 01-12-2016 10:12 AM

    Hi Erico,

     

    Given the universe's dependency on SDM object layer,  creating joins in the universe does create a bit off an odd complexity.

     

    For SREL related real-values, Attribute Alias  is the recommended approach.

     

    _R



  • 5.  Re: SDM > Custom CABI report

    Posted 01-12-2016 11:18 AM

    Thanks for the help Raghu.