Enterprise Content Management and Service Oriented Architecture

Visualize the following scenario: All company content (wherever generated by any entity) goes into one repository and users can receive different services (which they received from different applications before, or completely new services) from an integrated system with the final standard front. Service Oriented Architecture, Enterprise Application Integration, and Warehousing work function to make this scenario a reality.

Data warehouses, unlike transactional databases, are designed to facilitate demand and analysis. They are separated from the transactional database so that the latter is not burdened with demand processing / analysis requests. These types of requests tend to use processing resources, slowing transaction processing response times.

Application Integration The company seeks to integrate various applications to eliminate content duplication and processing operations.

This article explores how Service Oriented Architecture works.

Service Oriented Architecture (SOA)

This architectural style groups functionality into specific service groups. Services are provided to manage business processes that support the organization’s business.

The system for the entire company is structured as a set of standard services needed by various applications by employees, suppliers and customers. These different applications can even work on different platforms and are coded in different programming languages. Each service is designed to work with whatever application is calling it, and won’t know which application is calling it. Its role is to provide services specified in a standard way for any application that requires it.

A collection of services can be configured to create new applications if needed. This kind of architecture adds flexibility and faster deployment to content management systems.

Available services are listed in the service registry that can be seen by applications to call the services they need. The service will be equipped with an attached security requirement that matches the service.

In an ideal system, one service or another will meet every type of information management needs, and there will be a standard look and feel for the interface. In addition, information management will be adjusted to the requirements of the organization’s business processes.

Internet Protocol and SOA

The Internet protocol works independently of platforms and programming languages ​​and works on service requests and delivery models. For example, client users can request certain documents and the server complies with the request by taking the document and sending it to the client.

This makes the web service approach a good Service Oriented Architecture approach. You can activate an existing web application to start building an SOA system.

All services are described in XML documents that are platform independent, and are written in the Web Service Description Language (WSDL). XML schemes allow communication between services.

Web services are not the only technology that can be used by SOA. SOA is an architecture that can be implemented using various technologies.

Conclusion

Service Oriented Architecture makes it possible to transform old applications into services that can be called by any application. By configuring services to meet all types of information management needs, and tailoring information management to specific business requirements, you can use company knowledge to gain real control over business processes. This is what the Company’s Content Management system wants to achieve.