ITGumbo: spicing IT up

Hello to all service enablers,

I would like to elaborate the discussion about service enabling.

It is tempting and also less work expose the service in a specific technology e.g. HTTP/SOAP.

As seen in my another post:

This should work.

The question now is: Is this satisfactory? Do you really can plan of having only a single technology?

The answer as you could expected, is NO.

In real life we are working in more than one service consumption technology. Just take the good old Purchase order. We want to query it with HTTP/SOAP for our Portal, we want to download it to a file, we want send it by mail and this just contemporary technologies that we are working with now.

The sad truth is that we accumulate legacy technologies over time and we cannot dispose them. For example: EDI, SQL views, FTP.
Should I mention more?

So, the conclusion is: for the same business content we need more than one exposure technology. That brings me to the following:

The layer of Service logic is focused only on producing and processing the service business content, the message.

The Service technology layer knows how to handle data object that could be processed by the Service logic layer.

• In case of inbound calls, the Service technology layer will handle the call and create the data object and pass it to an object in Service logic layer to process it.

• In case of outbound calls, an object in the Service logic layer will prepare the data object and will pass it to Service technology object that will handle the sending.

Have a good week and service well.

Yours truly,

Noam