IBM WebSphere DataPower SOA Appliances
This series of IBM Redbooks publications is written for architects and administrators who need to understand the implemented architecture in WebSphere DataPower appliances to successfully deploy it as a secure and efficient enterprise service bus (ESB) product. These papers give a broad understanding of the new architecture and traditional deployment scenarios. They cover details about the implementation to help you identify the circumstances under which you should deploy DataPower appliances. They also provide a sample implementation and architectural best practices for an SOA message-oriented architecture in an existing production ESB environment.
The entire IBM WebSphere DataPower SOA Appliances series includes the following papers:
- “IBM WebSphere DataPower SOA Appliances Part I: Overview and Getting Started,” REDP-4327
- “IBM WebSphere DataPower SOA Appliances Part II: Authentication and Authorization,” REDP-4364
- “IBM WebSphere DataPower SOA Appliances Part III: XML Security Guide,” REDP-4365
- “IBM WebSphere DataPower SOA Appliances Part IV: Management and Governance,” REDP-4366
Pass encrypted data through WebSphere Enterprise Service Bus and convert it to a JMS payload
This article describes in detail how to instrument WebSphere Enterprise Service Bus to accept SOAP messages containing encrypted portions of data, perform protocol switching, and then forward these messages to a JMS topic where the service providers are registered. You will learn how to:
- Properly define an export interface to get the SOAP HTTP message containing sensitive data.
- Configure a message selector to augment the JMS message header with selectors information.
- Introduce an XSLT transformation to match the import and export interfaces and, thus, add mediation logic even when the message contains encrypted data.
- Provide an import interface to send the sensitive data to the topic as a JMS payload.
WebSphere DataPower SOA Appliances extension functions for certificate-based XML standard encryption
You will learn how it’s possible to use WebSphere DataPower SOA Appliances to promote a PKI. You will learn how to dynamically select a service provider’s certificate, perform standard XML encryption, and forward the encrypted SOAP message to the ESB.
WebSphere ESB for protocol switching of encrypted data
This article gives a complete overview of a real case scenario concerning the healthcare reservation system and described the architectural picture that has been adopted. You also saw step-by-step instructions on how to configure the ESB import binding.
The Web Services Security Threat: The Risks
Can existing network security technologies ameliorate Web services risks? Are risks the same for internal and external Web Services? The benefits and ease of use make the adoption of Web Services a foregone conclusion. The real question that enterprises must ask themselves when adopting Web Services is: what are the most cost-effective steps to mitigate the risks of deploying Web Services - to an acceptable level - for the organization? Read this white paper for an enlightening discussion of these steps.
white_paper_web_service_security_threat.pdf
Business Process Visibility
IT must move towards managing service-oriented architectures (SOAs) from a business perspective, which means that IT managers must find the tools necessary to align its goals with those of the business.
whitepaper_business_process_visibility.pdf
SOA Worst Practices Vol2
SOA Worst Practices, Volume II, as the title suggests, is the follow-on white paper to SOA Worst Practices, Volume I: a collection, of dubious––and sometimes disastrous ––case studies of service-oriented architecture (SOA) implementations….
SOA Worst Practices Vol1
Make no mistake: SOA can be tricky. Learn from this compilation of “SOA Worst Practices” which traps to avoid. Learn the limits of XML firewalls. Find out how not to fall prey to consultants. Make sure you don’t hand out your WSDL to passersby… This wisdom and much, much more from the experts at Actional.
The “S” in “SOA” is Services
SOA is indeed architecture, but it’s based on the proper design, development, and testing of Services. These Services provide what’s core to SOA, and the discipline and process that software engineers put around this effort should be significant. Changes to SOA Services design, development and testing need to be made and understood right now.
Anemic Domain Model
The basic symptom of an Anemic Domain Model is that at first blush it looks like the real thing. There are objects, many named after the nouns in the domain space, and these objects are connected with the rich relationships and structure that true domain models have. The catch comes when you look at the behavior, and you realize that there is hardly any behavior on these objects, making them little more than bags of getters and setters. Indeed often these models come with design rules that say that you are not to put any domain logic in the the domain objects. Instead there are a set of service objects which capture all the domain logic. These services live on top of the domain model and use the domain model for data.


