2 Replies Latest reply on Dec 15, 2017 9:56 PM by Carey Walker

    MAP ESB(enterprise service bus) Interfaces in CMDB

    Rahul Priyadarshy
      Share:|

      Hi All,

       

      How and where to MAP- ESB (enterprise Service Bus) Interfaces.

      We have an ESB product Namely IBM MQ Series (as an Application CI).

       

      We have Many Interfaces Defined between various application Using ESB (IBM MQ Series).

      Sample Data Looks like as below.

       

      Env - ITSM 9.1.02, CMDB 9.1.02

       

      ESB Interface Data looks like below-Source and Destination Application is already present in System in Application Class.

       

      Interface No

      Interface Name

      Source Application CI

      Destination Application CI

       

      A001

      Interface_x

      SApp1

      DApp1,DApp2

       

      A002

      Interface_y

                 Sapp2,Sapp3

      DApp3,DApp4,DApp5

       

       

       

       

       

       

       

      Here where to fit  Interfaces in CMDB (interface_x, Interface_y)?

      Also how and what relationship we should use here to connect  Interfaces,Source Application CI and Destination Application CI

       

      @experts your though and input please.

       

      Regards

      Rahul

        • 1. Re: MAP ESB(enterprise service bus) Interfaces in CMDB
          Rahul Priyadarshy

          Carey Walker  and Other Experts please - Any thought?

           

          Regards

          RP

          • 2. Re: MAP ESB(enterprise service bus) Interfaces in CMDB
            Carey Walker

            Hi Rahul

             

            If the ESB is implemented via MQ Series (is that the same as what's now called Websphere MQ/Websphere Process server?), then you have a software server CI delivering that 'bus' or interface. One option therefore is to create an S/S CI for MQ Series, and place between the source and destination applications.

            SApp1 Application CI -> MS Series Software Server CI -> DApp1 for example.

             

            This isn't 100% ideal since the dependency interpretation for an ESB won't be totally correct. i.e. if it's a bus, there will be traffic in both directions. That mean the source and destination apps are both consuming and providing data from/to the SB. However you can probably model that by creating more 'detailed' S/S CIs in the model, since there will likely be message queues for the outbound AND inbound traffic. i.e. model the message queues granularly and it will probably look right. Does that make sense?