Topic
  • 3 replies
  • Latest Post - ‏2013-12-16T15:42:10Z by DavidSeager
1EME_Tridip_Sarma
1EME_Tridip_Sarma
2 Posts

Pinned topic SLD strucuture for Composite Services

‏2013-12-09T10:04:27Z |

I have a specific requirement where we would need to build composite services in DataPower. So for a particular operation in DP we would need to call 2 or more back-end services and aggregate the individual responses into a composite response.

In this case, I am thinking if we need to have as many SLDs as the number of back-end services to be called. And the consumer SLA to that DP service operation, would be tied with those SLDs. So its a one SLA to many SLDs.

Kindly advice me on the approach to be taken.

Thanks, Tridip

 

  • DavidSeager
    DavidSeager
    67 Posts

    Re: SLD strucuture for Composite Services

    ‏2013-12-11T10:28:56Z  

    WSRR allows modelling of service consumers and providers and it lets you chain consumers and providers. So in this case, the 2 back end services can be modelled as Business Services and Service Versions in WSRR. The DataPower service can be modelled as a Business Service and a Service Version.

    You then create an SLD on each of the back end services for their Service Versions. You then create 2 SLAs from the DataPower Service Version to the SLDs on the back end services. This captures that there are 2 services offering SLDs, being used by the DataPower service via the SLAs.

    Then this DataPower service itself can offer an SLD which describes what it can offer, this SLD will likely be affected by the SLDs on the back end services, for things like response time, uptime, etc.

    Services or applications that use the DataPower service can then be modelled in WSRR and create agreements with the DataPower SLD.

  • 1EME_Tridip_Sarma
    1EME_Tridip_Sarma
    2 Posts

    Re: SLD strucuture for Composite Services

    ‏2013-12-16T06:24:45Z  

    WSRR allows modelling of service consumers and providers and it lets you chain consumers and providers. So in this case, the 2 back end services can be modelled as Business Services and Service Versions in WSRR. The DataPower service can be modelled as a Business Service and a Service Version.

    You then create an SLD on each of the back end services for their Service Versions. You then create 2 SLAs from the DataPower Service Version to the SLDs on the back end services. This captures that there are 2 services offering SLDs, being used by the DataPower service via the SLAs.

    Then this DataPower service itself can offer an SLD which describes what it can offer, this SLD will likely be affected by the SLDs on the back end services, for things like response time, uptime, etc.

    Services or applications that use the DataPower service can then be modelled in WSRR and create agreements with the DataPower SLD.

    David, thanks for the reply.

    >> The DataPower service can be modelled as a Business Service and a Service Version.........Then this DataPower service itself can offer an SLD which describes what it can offer, this SLD will likely be affected by the SLDs on the back end services, for things like response time, uptime, etc.>>

    After modelling the the DataPower service, the SLD in the DataPower service won't have any endpoint defined as it is consuming the 2 back-end service endpoints via the 2 back end services which will be modelled as Business Services and Service Versions in WSRR.

    Can we have an SLD without an endpoint?

    Thanks, Tridip

     

     

     

  • DavidSeager
    DavidSeager
    67 Posts

    Re: SLD strucuture for Composite Services

    ‏2013-12-16T15:42:10Z  

    David, thanks for the reply.

    >> The DataPower service can be modelled as a Business Service and a Service Version.........Then this DataPower service itself can offer an SLD which describes what it can offer, this SLD will likely be affected by the SLDs on the back end services, for things like response time, uptime, etc.>>

    After modelling the the DataPower service, the SLD in the DataPower service won't have any endpoint defined as it is consuming the 2 back-end service endpoints via the 2 back end services which will be modelled as Business Services and Service Versions in WSRR.

    Can we have an SLD without an endpoint?

    Thanks, Tridip

     

     

     

    The SLD tends to need an endpoint, so that clients know where to call the service. Something that just consumes other services and itself does not offer an endpoint can be modelled in WSRR as a Business Application and Application Version.

    If you are using DataPower to consume the two services, how do clients applications call the DataPower to get it to consume those services? However this is done could be exposed in WSRR as an endpoint of some type. If the DataPower is using a Multiprotocol Gateway then however this gateway is invoked (JMS, SOAP/HTTP, REST) would be your endpoint you would model in WSRR.