soa

I've been given the task of laying the groundwork of a SOA for my client. The goal is to open up various processes in an end-client independent way and also to make data available offline e.g. for reps visiting customers. I do have extensive experience with J2EE (Websphere) and web services but I would appreciate advice on how to build up such an SOA. Where are the pitfalls? What about security? How finely granulated should services be? etc. Links to tutorials and book recommendations would also be useful. Thanks! Pitfalls Versioning/backwards compatibility: it gets really hard to change a

I am trying to wrap my head around Apache Camel, which appears to be a lightweight ESB. If I understand Camel/ESBs correctly, then you can think of a Camel Route as a graph of nodes and edges. Each node is an endpoint on the route (can consume/produce messages). Each edge is a route between two different endpoints (1 producer and 1 consumer). Assuming that's correct, I have a practical question: what do best practices dictate about deploying your application's ESB/Camel Route? Should I package it up as its own JAR, or is it worthy of being its own EAR full of EJBs, Web Services and other JARs?

I'm rather new to SOA and therefore experimenting around. Currently, the part that creates the biggest problem to me is authentication, my current thought about it involves the following: The client sends some kind of authentication message to the authentication / user service, this service queries the db and if the user is found and the password is valid, it will respond with a session id, this id will be used in all further requests of this client. This seems rather ok to me but I don't know how I should handle the requests to other services, I thought of three different approaches. Every

Is there any possibility to propagate transactions between different SOA services which are from different platforms like .NET or Java? I know the transaction can flow in and out between WCF services which is coming from .NET. But I am not familiar with Java platform. Now I am working in a project which communicates the services from different platform. How can I maintain consistency in business? Daniel P. Bullington If your client and server SOA infrastructure (and by extension, the underlying back-end systems being accessed in the various service implementations) support WS-Transaction, then