IC5Notice: We have upgraded developerWorks Community to the latest version of IBM Connections. For more information, read our upgrade FAQ.
Topic
  • 5 replies
  • Latest Post - ‏2013-05-21T12:20:08Z by wxyzabc
wxyzabc
wxyzabc
29 Posts

Pinned topic Same Service Instance but Diffrent status change in there respective parent service

‏2013-05-15T06:51:40Z |

Hi ,
Need a help for the service instances.
If A and B are two Service Instances. Both having child as C. So by any means is it possible that status change of C in Parnet A Service will not affect status of C in Parent B Service.

  • randybrown
    randybrown
    59 Posts
    ACCEPTED ANSWER

    Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-16T15:35:13Z  
    • wxyzabc
    • ‏2013-05-16T05:16:59Z

    Hi Randy Brown,

    Thanks for Your Reply.

    As per my understanding ,You want to say that Service Instance C ,will have two diffrent Service Instance Name (ex- C1 ,C2) but same Service display name as C.Then I can map it to its parent like A->C1 and B->C2, as display name will be C only so in Service Tree it will look like A->C, and B->C. Now alerts which are impacting C1 service status will not impact C2 service status as Identification field of both (C1 and C2)will be differ same as the Service Instance Name. 

     

    Thanks & Regards

    wxyzabc

    Hi,

    Yes, as long as the service instances have different service instance names, you can map the alerts as you need to. Of course this assumes that your events will also have a field that can be used to correlate to the appropriate TBSM service instance. For example, in the simplest case, the object server Node field is used to match to the TBSM service instance name.

    Since you are having to change the instance name to get the unique behavior you require, you may also have to tweak the source of the events to the object server so that the appropriate events are matched to the appropriate instance of "C". TBSM has the concept of Identification Fields that can be used to change the fields used to match a service instance to an event.

    Beyond that, the only other difficulty might be in figuring out which "C" you want when working with lists of services in the UI that show the display name. At least for the tree it will be obvious due to the relationships.

    Hope that helps...

     

    Randy Brown

  • randybrown
    randybrown
    59 Posts

    Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-15T12:38:56Z  

    Hi,

    In the scenario you describe I assume that you have a single service with instance name "C". TBSM will have only one set of attributes for this unique service instance, including the overall status. The location of the service in the service hierarchy will not affect this behavior.

    If it is possible, you would need 2 distinct service instances with unique service instance names (though they could have the same display name C). But this solution will require that both instances are affected by alerts that are unique to its relationship with A or B, and alerts that would be common to both A and B.

    Hope this helps clarify the TBSM capabilities...

     

    Randy Brown

  • wxyzabc
    wxyzabc
    29 Posts

    Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-16T05:16:59Z  

    Hi,

    In the scenario you describe I assume that you have a single service with instance name "C". TBSM will have only one set of attributes for this unique service instance, including the overall status. The location of the service in the service hierarchy will not affect this behavior.

    If it is possible, you would need 2 distinct service instances with unique service instance names (though they could have the same display name C). But this solution will require that both instances are affected by alerts that are unique to its relationship with A or B, and alerts that would be common to both A and B.

    Hope this helps clarify the TBSM capabilities...

     

    Randy Brown

    Hi Randy Brown,

    Thanks for Your Reply.

    As per my understanding ,You want to say that Service Instance C ,will have two diffrent Service Instance Name (ex- C1 ,C2) but same Service display name as C.Then I can map it to its parent like A->C1 and B->C2, as display name will be C only so in Service Tree it will look like A->C, and B->C. Now alerts which are impacting C1 service status will not impact C2 service status as Identification field of both (C1 and C2)will be differ same as the Service Instance Name. 

     

    Thanks & Regards

    wxyzabc

  • randybrown
    randybrown
    59 Posts

    Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-16T15:35:13Z  
    • wxyzabc
    • ‏2013-05-16T05:16:59Z

    Hi Randy Brown,

    Thanks for Your Reply.

    As per my understanding ,You want to say that Service Instance C ,will have two diffrent Service Instance Name (ex- C1 ,C2) but same Service display name as C.Then I can map it to its parent like A->C1 and B->C2, as display name will be C only so in Service Tree it will look like A->C, and B->C. Now alerts which are impacting C1 service status will not impact C2 service status as Identification field of both (C1 and C2)will be differ same as the Service Instance Name. 

     

    Thanks & Regards

    wxyzabc

    Hi,

    Yes, as long as the service instances have different service instance names, you can map the alerts as you need to. Of course this assumes that your events will also have a field that can be used to correlate to the appropriate TBSM service instance. For example, in the simplest case, the object server Node field is used to match to the TBSM service instance name.

    Since you are having to change the instance name to get the unique behavior you require, you may also have to tweak the source of the events to the object server so that the appropriate events are matched to the appropriate instance of "C". TBSM has the concept of Identification Fields that can be used to change the fields used to match a service instance to an event.

    Beyond that, the only other difficulty might be in figuring out which "C" you want when working with lists of services in the UI that show the display name. At least for the tree it will be obvious due to the relationships.

    Hope that helps...

     

    Randy Brown

  • alexsey
    alexsey
    1 Post

    Ответ: Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-18T11:15:41Z  

    Hi,

    In the scenario you describe I assume that you have a single service with instance name "C". TBSM will have only one set of attributes for this unique service instance, including the overall status. The location of the service in the service hierarchy will not affect this behavior.

    If it is possible, you would need 2 distinct service instances with unique service instance names (though they could have the same display name C). But this solution will require that both instances are affected by alerts that are unique to its relationship with A or B, and alerts that would be common to both A and B.

    Hope this helps clarify the TBSM capabilities...

     

    Randy Brown

    >>If it is possible, you would need 2 distinct service instances with unique service instance names (though they could have the same display name C). But this solution will require that both instances are affected by alerts that are unique to its relationship with A or B. and alerts that would be common to both A and B.<<

    And unless one is enough?

    Updated on 2013-05-18T11:16:08Z at 2013-05-18T11:16:08Z by alexsey
  • wxyzabc
    wxyzabc
    29 Posts

    Re: Same Service Instance but Diffrent status change in there respective parent service

    ‏2013-05-21T12:20:08Z  

    Hi,

    Yes, as long as the service instances have different service instance names, you can map the alerts as you need to. Of course this assumes that your events will also have a field that can be used to correlate to the appropriate TBSM service instance. For example, in the simplest case, the object server Node field is used to match to the TBSM service instance name.

    Since you are having to change the instance name to get the unique behavior you require, you may also have to tweak the source of the events to the object server so that the appropriate events are matched to the appropriate instance of "C". TBSM has the concept of Identification Fields that can be used to change the fields used to match a service instance to an event.

    Beyond that, the only other difficulty might be in figuring out which "C" you want when working with lists of services in the UI that show the display name. At least for the tree it will be obvious due to the relationships.

    Hope that helps...

     

    Randy Brown

    Hi Randy Brown,

    Thanks for your suggestion.

    In my case there are more than 5000 of service instances , so it is not possible to mannualy change the Identification field of the Service instances to match a service instance to an event.

    So this time I am going with the 1st option (diffrent instance name but same display name) of service instance, however I am also searching for the autoediting of Identificationfield same as Autopopulation of Service Instances.

    Thanks

    wxyzabc