I must say that the training that I underwent was excellent! The material is also excellent! This has propelled me to think of SOA in a different perspective. It has also helped me reinforce some of the concepts that I had about SOA.

> I have been practising SOA for sometime, but after the SOA classes that I underwent, I would need to understand the following:
> 1. In a scenario where one extracts services out of the existing applications and has infrastructure services for security, how does one do the authentication for SOBAs? Does one create a UI service which authenticates the user OR should one expose a service from an existing application for authentication, provide an UI and allow the SSO to take care of the rest? What do you perceive as the pros and cons for each? Do you know of any other way?
> 2. When creating new products based of SOA should there be additional considerations that should be kept in mind while identifying services other than the normal apsects that should be kept in mind while extracting services out of existing applications? What are the general value adds of SOA in this case since you would not have the advantage of heterogeneity? Would it be responsiveness to change, transparency in the business processes, monitoring business processes and innovation alone? Or there could be others as well? Can it cater to integration with potential existing applications also? How can it be catered to in general?
> 3. It is recommended that the service contracts generally should have a lot of Non Functional Requirements incorporated in them. How are they used? It is only for choosing services to compose with during choreography or orchestration? Or there are other purposes to it too? How would service contract extensions to WSDL get used in practical scenarios?

Hi Shantanu — Good post, but can you post this into the “LZA Forums”? We’re trying to get that started Please post into one of the relevant threads.

Thanks!
Ron