SOA based ERP architecture for enterprise "tailored"

How to make ERP system with rapid reconfiguration can dynamically adjust its structure and behavior to support enterprise's management innovation and process reengineering optimization, and realize seamless integration with other existing application systems, has become a current challenge. Therefore, based on the software reuse, software components and other technologies, this paper proposes an SOA based ERP architecture model to meet the needs of business process reengineering and has the characteristics of reliability, reusability, scalability and dynamic variability, and realizes "tailor-made" for the enterprise.

How Service-Oriented architecture (SOA) works

A) Definition of SOA

A service-oriented architecture is a component model that links the different functional units of an application, called services, through well-defined interfaces and contracts. A service is a set of features that are well-defined, self-contained, and do not depend on context and other services. Interfaces are defined in a neutral way, independent of the hardware platform, operating system, and programming language that implements the service.

Two) Architecture of SOA

There are three main roles in the service-oriented architecture:

1. Service Consumers: Use the service registry to find the services needed, and then use the service. 2. Service provider: The entity that creates the service and responds to requests that use its own services. 3. Service registry: Register the services that have been published, classify them, and provide search services. It corresponds to a database of service information, provide a platform for service providers and service consumers to make both possible, while the service Registry has a common standard for service providers to meet this standard, so that service consumers can use services that span different service providers.

In an SOA architecture, the role of each entity is not fixed, and an entity can act as one or more of the three roles.

The main operations in a service-oriented architecture are: 1. Publish: Enables service providers to register their own functions and access interfaces to the service registry.

2. Discovery: Enable service requesters to find specific types of services through the service registry. 3 binding and invocation: After obtaining the service description information, the service consumer invokes the service accordingly.

At present, many of the technologies that implement SOA, such as Web Services, CORBA, and so on, have an important common denominator in support of different programs written in different languages to communicate with each other in a standards-based way. For example, as an implementation of SOA, Web services provide a standard interface based on Extensible Markup Language (XML), with good encapsulation, loose coupling, standardization of protocol specifications, and high scalability to meet the needs of SOA application patterns. At present, a series of xml-based Web service standards have been widely accepted by the industry, forming the core technology of Web services. Service providers can describe Web services in Web Service Description Language (Web Services Description Language, WSDL): Unified description, Discovery, and integration (Universai Description,discovery and Integration,uddi) Registry publishes, registers a Web service, the requester of the service Uddl the query, discovers the required services and can use the Simple Object Access Protocol (Simpie the object access Protocol,soap) to bind, Invoke these services.

(Responsible editor: The good of the Legacy)