Businesses will always need highly efficient applications which have ability to provide outstanding user experience while maintaining security. Most of the developers today thrive in a business setting and have worked for many years to improve business transactions between the client and end users.

This book is available for purchase at packtpub.com SOA Approach to Integration

Through the developers, different applications have been created and different theories were made to increase the level of customer satisfaction and business security.

A few years ago, businesses were hiring a pool of developers to build an application according to their preference. However, this comes at a great price since building an application from the scratch will mean constant testing and retooling. Developers will have to spend time testing and working on the code again and again. A released application will not even mean that the application will work as planned.

That is why SOA (Service Oriented Architecture) were offered to businesses. Instead of building an entirely new application, developers will combine different functions to build a new and efficient application. Instead of building from the scratch where constant testing has to be done, developers will just combine functions that were already tested for functionality and security. This lessens the requirement of manpower and cuts time for application development.

This book SOA Approach to Integration aims to explain how SOA can actually be used as online application in the real world. There are many theories that you find online but the real SOA is just too hard to find since they are geared for smaller business.

---

SOA and Web Services Approach for Integration In Chapter 2 you were introduced to how Service-Oriented Architecture SOA can be used for application integration. We saw that the integration itself may be restricted within an Enterprise or may involve third parties B2B or B2C . Service-Oriented Architectures are complex. Most SOA implementations...
SOA Evolution In the 1980s applications were mostly vertical built to meet the customer requirements in a vertical market segment. The software solutions were sufficient to meet the needs of a vertical industry. For example an automobile industry never felt the need for interacting with its suppliers by electronic means. The same was true in...
IT Evolution Looking at current business needs the IT environments in today s world need to be more flexible and must quickly adapt to the constantly changing business requirements. The applications running on heterogeneous environments must communicate and integrate seamlessly. IT environments have been evolving along the lines of business requirement...
Patterns Patterns are based on the proven successful experiences of the past. The various patterns for e-business as suggested by IBM are shown in the following figure of the hierarchy of patterns. These patterns are briefly discussed in the following paragraphs. We will discuss a few of the important patterns in the context of SOA in the next...
Designing Sound Web Services for Integration The Web Services technology plays an important role when applying the concepts of Service-Oriented Architectures. The web services technology is based on open standards such as XML eXtensible Markup Language SOAP Simple Object Access Protocol WSDL Web Services Description Language...
Self-Service Business Pattern Patterns In the previous section we looked at the various patterns for e-business. We will now study these patterns in more depth in the context of an SOA implementation. In an SOA approach the focus is on creating and reusing loosely coupled services rather than creating coarse-grain applications. The building blocks...
Extended Enterprise Business Pattern The previous pattern Self-Service provided an interaction between the consumer and the service. In the extended enterprise business pattern the interaction between the two partner businesses is explored. The collaborative businesses expose their functionality as services. A business can access the service exposed...
Application Integration Pattern The application integration patterns capture the best practices in integrating the back end applications and data. They are observed in the EAI Enterprise Application Integration space and are helpful in defining process automation and workflows. Process integration help companies connecting applications and its...
Direct Connection Application Pattern This is the simplest pattern and defines a 1-to-1 interaction between a pair of applications. These interactions may be complex which might be broken down into multiple elementary interactions. The pattern addresses these connections. The following figure illustrates this pattern. The connections may require...
Broker Application Pattern The Broker application pattern is based on 1-to-N connections. A single interaction initiated by a source application is distributed across multiple target applications. This is illustrated in the following figure. This pattern helps in reducing the clutter of point-to-point connections between the applications. Among...
Serial Process Application Pattern This is an extension of the broker application pattern discussed in the previous section. In this case a source application initiates an interaction with multiple target applications as in the case of a broker application pattern. However the interaction which is essentially a consumption of a service now consists...
Parallel Process Application Pattern This is an extension of the Serial Process application pattern where the sub-processes are executed concurrently on multiple targets. This is illustrated in the following figure. The concurrent execution of sub-processes requires a more sophisticated execution engine. The processes must be split executed...
Runtime Patterns The application patterns discussed so far overlay the runtime patterns. The runtime pattern uses a set of nodes to group functional and operational components. The nodes are interconnected to form a pattern. The business logic of the application is deployed on nodes. Nodes We consider the following definitions for nodes in the...
Direct Connection Runtime Pattern The Direct Connection pattern is depicted in the following figure. In this pattern a source application connects directly to a target application using a connector. The connector itself may be explicitly or implicitly modeled. Depending on the connector and interaction variation the connector may be classified...
Direct Connection Pattern using Single Adapter This pattern is depicted in the following figure. The Basic Direct Connection pattern uses a single adapter to connect a service consumer to a service provider. The adapter provides message and data transformation to match the different protocol requirements of the consumer and the provider. This...
Runtime Patterns for Broker As in the case of application patterns discussed earlier a broker may be introduced in the runtime nodes which will act as a message distributor. A source application connects to many target applications through a broker. A typical configuration for this pattern that uses a router to connect to multiple target applications...
Differences between B2B and EAI Web Services Let us first look at the differences between B2B and EAI. The major differences may be listed as follows 1. EAI as the name suggests acts within an enterprise to solve a local problem while B2B as the name suggests acts across the enterprises. 2. EAI aims at integration of application and data sources...
Writing Interoperable WSDL Definitions As seen from the discussions in the earlier sections web services technology can easily be used to implement SOA and to integrate applications running on different platforms. Every platform has its own data representation format and data type system. A web service must provide a universally accepted data type...
Validating Interoperable WSDL As we have hand-coded the interoperable WSDL in the previous section there is no guarantee that it can be implemented as the platforms may not support all the features specified in the WSDL. To ensure that the WSDL is valid and can be implemented use the following steps 1. Create a test web service for your platform....
WS-I Specifications To resolve these issues finally the Web Services Interoperability Organization WS-I was formed in 2002 with the help of SAP IBM Microsoft and others. The main purpose of WS-I was to bring the vendors and customers together to resolve the issues of interoperability. WS-I Specifications To resolve these issues finally the...
WS-I Basic Security Profile 1.0 The Basic Security Profile was created to address the interoperability issues of secured web services. The profile addresses several key areas listed next Transport Layer Security SOAP Message Security Username Token Profile X.509 Certificate Token Profile XML-Signature XML Encryption...
Guidelines for Creating Interoperable Web Services Fundamentally web services are interoperable. Thus regardless of the client s hardware and software it should be able to run a web service. The functionality of the web service should remain independent of the following Application platform such as Weblogic server SunOne App Server .NET...
Java EE and .NET Integration using Web Services So far we have looked into the various aspects of interoperability between web services deployed on disparate platforms. If the web services follow the compliance requirements of the Basic Profile discussed earlier they can interoperate easily. Fortunately for us most of the vendors have updated...
WSDL for Java Web Service The WSDL is shown in the following listing. geshibot language XML" geshibot If you examine this document carefully against the BP conformance requirements you will find that this...
Developing the .NET Web Service Creating a .NET web service using Visual Studio IDE is as simple as creating a Java web service using NetBeans IDE. I used Visual Studio 2005 for creating the web service and the test client application. The IDE provides a template for creating an ASP.NET Web Service. Follow the default project options while creating...
Developing the Test Client We will now develop a C console application for consuming the previously created web services. Use the project wizard in VS.NET to create a console application. Follow the default while creating the application. I used TestClient as the name for my project. The wizard generates the skeleton code for a console application....