Topic
  • 3 replies
  • Latest Post - ‏2014-02-18T14:24:34Z by randybrown
kftiv
kftiv
15 Posts

Pinned topic Presenting information from a secondary template in the service viewer

‏2014-02-04T21:30:50Z |

Dear all,

In our TBSM template modelling approach our idea is to use specialized templates which describe a special aspect of the behaviour of a service instance. The idea is to use a primary template with the main goal to assign an icon and a type description and secondary templates with a specific behaviour, e.g. handling of incoming events (like the SCR_ServiceComponentRawStatusTemplate), the association of incidents registered against this service instance (affectem item/CI), etc.).

However, when visualising the service instances, we now notice that it is possible to select an icon with specific labels and attributes, but the only attributes available for associating with this view type are the attributes available for this template. Hence, we miss the opportunity to present attributes, e.g. the number of incidents or the number of events, which are part of the secondary templates.

So, we are wondering now whether we need to step away from the template specialization to allow for visualizing secondary template information. From a TBSM design approach it seems we would need something like a container template relationship in which the "container" template determines the icon etc. and the "contained" (sub) templates add specialized behaviour.

But maybe there are other options to allow for the visualization we need. I understand that we could achieve this at the service instance level, but we're looking for a way to achieve this at the service template level.

Regards,

Updated on 2014-02-17T13:17:21Z at 2014-02-17T13:17:21Z by kftiv
  • randybrown
    randybrown
    59 Posts
    ACCEPTED ANSWER

    Re: Presenting information from a secondary template in the service viewer

    ‏2014-02-05T19:44:41Z  

    Hi,

    I think we may need to know a little more about which specific functions you are trying to use.

    1) Custom View Definition: this sounds like what you were trying, given that you were trying to customize at the template level using one of the "N element prototypes", for example. In this case the drop-down will only show the attributes for the template being configured, but if you know the attribute name that will exist on a secondary template, you can type @attributename in the Value field rather than using the drop-down.

    2) Custom Canvas: This is used to show specific instances, so I don't think it meets your requirement to do it by template.

    3) Service Tree (also referred to as a "scorecard"): You can create a tree template using the TBSM Tree Template Editor. This tree template can then be used with the service tree portlet to show a hierarchical view of your services with specific attributes (this is not a graphical view). The tree template will allow you to map attributes from any template to a column you have created in the template. Then when the services are rendered in the tree, the value for a column will depend on what attributes have been mapped to the column by template, and what templates are tagged to the service being rendered.

    I hope this helps...

     

    Randy Brown

  • randybrown
    randybrown
    59 Posts
    ACCEPTED ANSWER

    Re: Presenting information from a secondary template in the service viewer

    ‏2014-02-18T14:24:34Z  
    • kftiv
    • ‏2014-02-17T13:15:14Z

    Randy, thanks for your reply. Indeed I was looking for the Custom View Definition approach. Thanks for clarifying this option. This indeed allows us to stick with the specialized template approach while showing "secondary template" attributes in the visualization.

    Do you know how we can find a description of all the standard attributes that can be used for visualization? I find attributes like "numIncidentsInt" and a few more for which the meaning is not clear to me.

    Also, with regards to the visualization. Is it possible (easy) to introduce new "prototypes" to visualize specific attributes in templates?

    Regarding the Tree Template Editor, do you know how identical attribute names from different "other" templates are handled. E.g. suppose our service instance is of template type A and is also tagged with secondary template B an C. If template B and C both provide an attribute labeled "numIncidents", which attribute would be presented and how could this be influenced? Would it be different if the primary template A also had an attribute called "numIncidents"?

    Thanks again

    Hello,

    For the standard attributes I do not find a single document where they are all described. Many of them are covered in the section on Custom View Definitions, under the topic TBSM prototype.

    I am not aware of any technique for adding additional prototypes for use in the Custom View Definitions. Perhaps the user community that follows this forum has addressed this problem and will chime in.

    For the tree templates, there are the default image attributes that exist for the service instance being rendered. All the other mappings are for rule attributes found on one of the templates tagged to the service. The primary template is always considered first when deciding which attribute to display in a particular column.

    If there is no attribute from the primary template that is mapped to the column, then the secondary templates are considered. If an attribute from more than one of the secondary templates is mapped to the same column, then the value that is mapped is indeterminate, as there is no priority assigned among the secondary templates. The name of the attribute does not matter, since the mapping must be defined in the tree template between a column and an attribute from a specific template.

    If more than one attribute from the same template is mapped to a column, then the value chosen is again indeterminate since the attributes on the template have no priority or precedence defined for this context. This seems like a configuration error, but the Tree Template Editor will allow it.

    I hope this helps...

     

    Randy Brown

  • randybrown
    randybrown
    59 Posts

    Re: Presenting information from a secondary template in the service viewer

    ‏2014-02-05T19:44:41Z  

    Hi,

    I think we may need to know a little more about which specific functions you are trying to use.

    1) Custom View Definition: this sounds like what you were trying, given that you were trying to customize at the template level using one of the "N element prototypes", for example. In this case the drop-down will only show the attributes for the template being configured, but if you know the attribute name that will exist on a secondary template, you can type @attributename in the Value field rather than using the drop-down.

    2) Custom Canvas: This is used to show specific instances, so I don't think it meets your requirement to do it by template.

    3) Service Tree (also referred to as a "scorecard"): You can create a tree template using the TBSM Tree Template Editor. This tree template can then be used with the service tree portlet to show a hierarchical view of your services with specific attributes (this is not a graphical view). The tree template will allow you to map attributes from any template to a column you have created in the template. Then when the services are rendered in the tree, the value for a column will depend on what attributes have been mapped to the column by template, and what templates are tagged to the service being rendered.

    I hope this helps...

     

    Randy Brown

  • kftiv
    kftiv
    15 Posts

    Re: Presenting information from a secondary template in the service viewer

    ‏2014-02-17T13:15:14Z  

    Hi,

    I think we may need to know a little more about which specific functions you are trying to use.

    1) Custom View Definition: this sounds like what you were trying, given that you were trying to customize at the template level using one of the "N element prototypes", for example. In this case the drop-down will only show the attributes for the template being configured, but if you know the attribute name that will exist on a secondary template, you can type @attributename in the Value field rather than using the drop-down.

    2) Custom Canvas: This is used to show specific instances, so I don't think it meets your requirement to do it by template.

    3) Service Tree (also referred to as a "scorecard"): You can create a tree template using the TBSM Tree Template Editor. This tree template can then be used with the service tree portlet to show a hierarchical view of your services with specific attributes (this is not a graphical view). The tree template will allow you to map attributes from any template to a column you have created in the template. Then when the services are rendered in the tree, the value for a column will depend on what attributes have been mapped to the column by template, and what templates are tagged to the service being rendered.

    I hope this helps...

     

    Randy Brown

    Randy, thanks for your reply. Indeed I was looking for the Custom View Definition approach. Thanks for clarifying this option. This indeed allows us to stick with the specialized template approach while showing "secondary template" attributes in the visualization.

    Do you know how we can find a description of all the standard attributes that can be used for visualization? I find attributes like "numIncidentsInt" and a few more for which the meaning is not clear to me.

    Also, with regards to the visualization. Is it possible (easy) to introduce new "prototypes" to visualize specific attributes in templates?

    Regarding the Tree Template Editor, do you know how identical attribute names from different "other" templates are handled. E.g. suppose our service instance is of template type A and is also tagged with secondary template B an C. If template B and C both provide an attribute labeled "numIncidents", which attribute would be presented and how could this be influenced? Would it be different if the primary template A also had an attribute called "numIncidents"?

    Thanks again

  • randybrown
    randybrown
    59 Posts

    Re: Presenting information from a secondary template in the service viewer

    ‏2014-02-18T14:24:34Z  
    • kftiv
    • ‏2014-02-17T13:15:14Z

    Randy, thanks for your reply. Indeed I was looking for the Custom View Definition approach. Thanks for clarifying this option. This indeed allows us to stick with the specialized template approach while showing "secondary template" attributes in the visualization.

    Do you know how we can find a description of all the standard attributes that can be used for visualization? I find attributes like "numIncidentsInt" and a few more for which the meaning is not clear to me.

    Also, with regards to the visualization. Is it possible (easy) to introduce new "prototypes" to visualize specific attributes in templates?

    Regarding the Tree Template Editor, do you know how identical attribute names from different "other" templates are handled. E.g. suppose our service instance is of template type A and is also tagged with secondary template B an C. If template B and C both provide an attribute labeled "numIncidents", which attribute would be presented and how could this be influenced? Would it be different if the primary template A also had an attribute called "numIncidents"?

    Thanks again

    Hello,

    For the standard attributes I do not find a single document where they are all described. Many of them are covered in the section on Custom View Definitions, under the topic TBSM prototype.

    I am not aware of any technique for adding additional prototypes for use in the Custom View Definitions. Perhaps the user community that follows this forum has addressed this problem and will chime in.

    For the tree templates, there are the default image attributes that exist for the service instance being rendered. All the other mappings are for rule attributes found on one of the templates tagged to the service. The primary template is always considered first when deciding which attribute to display in a particular column.

    If there is no attribute from the primary template that is mapped to the column, then the secondary templates are considered. If an attribute from more than one of the secondary templates is mapped to the same column, then the value that is mapped is indeterminate, as there is no priority assigned among the secondary templates. The name of the attribute does not matter, since the mapping must be defined in the tree template between a column and an attribute from a specific template.

    If more than one attribute from the same template is mapped to a column, then the value chosen is again indeterminate since the attributes on the template have no priority or precedence defined for this context. This seems like a configuration error, but the Tree Template Editor will allow it.

    I hope this helps...

     

    Randy Brown