http://www.soamag.com The SOA Magazine is a monthly online publication provided by SOA Systems Inc. and Prentice Hall/PearsonPTR and is officially associated with the "Prentice Hall Service-Oriented Computing Series from Thomas Erl." SOA en-us Copyright 2010, SOA Systems Inc. http://www.soamag.com The next SOA Symposium is upon us in a few weeks. This will be the second annual event sponsored by the U.S. Department of Defense and will feature, among others, former baseball player Cal Ripken who will speak about the importance of discipline - a theme that strikes at the heart of successful SOA project delivery and governance. Leading the event will be Chief Technical Officer and the Chief Architect of the Business Mission Area, Dennis Wisnosky and also contributing with his famous "Avatar" presentation will be Grady Booch. For the first time, the post-conference events will include both the SOA Architect and SOA Security Specialist Certification workshops. SOA http://www.soamag.com/default.php#When:10.03.10 http://soamag.com/I37/0310-1.php XML Schemas are a fundamental part of any XML-based service oriented architecture. They define the structure and content of the messages that are passed among services. Enterprise architects, DBAs and software developers often devote a lot of time to carefully designing data: they create enterprise data models, data dictionaries with strict naming and documentation standards, and carefully designed and optimized relational databases. Unfortunately, service designers and implementers often do not pay as much attention to good design when it comes to XML messages. There are several reasons for this. Some people feel that since the XML messages are transitory, it is not important how they are structured. Some decide that it is easier to use whatever schema is generated for them by a toolkit. Others decide to use an industry standard XML vocabulary, but fail to figure out how their data really fits into that standard or come up with a strategy for how to customize it for their needs. As with any data design, there are many ways to structure XML messages... SOA http://soamag.com/I37/0310-1.php#When:10.03.10 http://soamag.com/I37/0310-2.php Cloud computing enables the delivery of scalable and available capabilities by leveraging dynamic and on-demand infrastructure. By leveraging these modern service technology advances and various pervasive Internet technologies, the "cloud" represents an abstraction of services and resources, such that the underlying complexities of the technical implementations are encapsulated and transparent from users and consumer programs interacting with the cloud. Cloud-based services and service-oriented solutions deployed on cloud platforms can typically leverage and be designed with existing security frameworks. However, the fact that some or all parts of a given service composition reside in an environment external to the controlled IT enterprise raises several additional security considerations... SOA http://soamag.com/I37/0310-2.php#When:10.03.10 http://soamag.com/I37/0310-3.php In Part 1 of this article series, I had used the popular Spring framework, a lightweight container that provides automated configuration and wiring of application objects, to create a contract-first Web service. Demonstrating Spring's pluggable architecture, we had seen how to configure the endpoint with Spring's support for OXM (Object-XML Mapping) and handle service-level and runtime exceptions. In this article we'll go over the security configuration using Spring's support for WS-Security providing message-level authentication, and optionally message confidentiality and message integrity services, ORM (Object-Relational Mapping) to deal with persistence at the object level, and DAO for data access to a relational database storing user-credential information. Next, we'll look at how Spring automatically generates the WSDL document using the data contract created earlier and, lastly, the client configuration required to invoke and consume the Web service... SOA http://soamag.com/I37/0310-3.php#When:10.03.10