| Visualize the following scenario: All enterprise | | | | in a standard way to whatever application calls for |
| content (wherever generated by whatever | | | | it. |
| entity) goes into a single repository and users can | | | | The pool of services can be configured to create |
| receive different services (that they were | | | | new applications if needed. This kind of |
| receiving from different applications earlier, or are | | | | architecture adds flexibility and quicker |
| completely new services) from an integrated | | | | deployment to content management systems. |
| system with a standard front end. Service | | | | Available services are listed in a service registry |
| Oriented Architecture, Enterprise Application | | | | that can be looked up by applications for calling |
| Integration, and Data Warehousing work to make | | | | the service they need. The services would come |
| this scenario a reality. | | | | with any attached security requirements |
| Data warehouses, unlike transactional databases, | | | | appropriate to the service. |
| are designed to facilitate querying and analysis. | | | | In an ideal system, one service or another would |
| They are separated from transactional databases | | | | cater to every kind of information management |
| so that the latter are not burdened with query | | | | need, and there would be a standard look and feel |
| analysis processing requests. These kinds of | | | | for the interface. Additionally, information |
| requests tend to use the processing resources, | | | | management would be customizable to the |
| slowing down transaction processing response | | | | requirements of the organization's business |
| times. | | | | processes. |
| Enterprise Application Integration seeks to | | | | Internet Protocols and SOA |
| integrate the different applications to eliminate | | | | Internet Protocols work independent of platforms |
| duplication of both content and processing | | | | and programming languages and work on the |
| operations. | | | | service request and delivery model. For example, |
| This article explores how Service Oriented | | | | a user client might request a certain document |
| Architecture works. | | | | and the server complies with the request by |
| The Service Oriented Architecture (SOA) | | | | retrieving the document and sending it to the |
| This style of architecture groups functionalities | | | | client. |
| into specific service groups. The services are | | | | This makes the web-services approach a good |
| provided to manage business processes that | | | | Service Oriented Architectural approach. You can |
| support an organization's business. | | | | make your existing applications web enabled to |
| The enterprise-wide system is structured as a | | | | start building a SOA system. |
| collection of standard services that different | | | | All services are described in XML documents that |
| applications used by employees, suppliers, and | | | | are independent of platforms, and written in Web |
| customers need. These different applications | | | | Services Description Language (WSDL). An XML |
| might even be working on different platforms and | | | | schema enables communication among the |
| coded in different programming languages. Each | | | | services. |
| service is designed to work with any application | | | | A web service is not the only technology that can |
| that calls it, and would not know which application | | | | be used by SOA. SOA is an architecture that can |
| would call it. Its role is to provide a defined service | | | | be implemented using different technologies. |