Enterprise Integrated Architecture Design

1. Enterprise Integration

After integration, enterprises provide the following functions:

1. Communication Service (network integration)

2. Information Integration Service (semantic integration)

3. Application Integration Service (Please use integration)

4. Secondary Development Tools (integrated operation and convergence integration)

5. platform operation management tools (integrated operation and convergence integration)

[Enterprise integration is actually the integration of enterprise information, as well as the integration of enterprise business processing, which is the same as the design of information systems. However, enterprise integration is closer to specific services .]

 

Ii. Trends

1. Integrated Technology for transition from Layer 2 to layer n

2. Integration supports expansion from information-oriented integration to process-oriented integration and service integration

[Process-oriented integration is actually a combination of calling business functions using a policy model]

[Service-oriented is a dynamic integration method proposed to support public service process integration in a wide range]

3. Integration and Development with commercial workflow products [industry], integration and development with underlying integrated Server products [Industrialization (combining your own service framework)], compatibility with point-to-point integration and end-to-end Integration

[CONCLUSION: The Coupling Degree of Application Integration is decreasing, the integration scope is expanding, and the Integration granularity is also decreasing]

 

Iii. Data Integration (semantic integration)

Data integration is based on network integration (syntactic interconnection. Provides data access, information query, and decision-making support services with integrity, consistency, and security for various applications, systems, or services running on the platform.

There are three main modes: Data Federation, data replication, and interface-based data integration.

[Data Federation: adding a virtual database between an application and a database]

[Data replication: Data Consistency service is added between applications and databases, that is, database replication is achieved through consistent replication between underlying application data sources]

[Interface-based data integration: different application systems use adapters to provide application programming interfaces for mutual calls (similar to using policy modes to Control Data Access )]

 

Iv. Application Integration (Pragmatic integration)

Application Integration refers to the mutual call and interoperability between two or more application systems based on the needs of business logic. [integration of business functions] Application Integration modes include integration adapter and integration messenger, integration panel, and integration proxy

Adapter: for example, the adapter converts and maps data formats and access methods between different systems to enable the integration of business functions and business data between different systems. [Playing an intermediate role, blocking at both ends, mainly used in the early stage of EAI (internal enterprise integration]

Messenger integration mode: [The main cause is that the interface problems between systems become more and more complex, and data exchange between systems is implemented through message proxy]

Panel mode: it is mainly used for Object-Oriented software design. It is called and encapsulated layer by layer like a panel, realizing the separation of server application interaction logic]

Proxy mode: there is no obvious division between the client and the server. It only needs to separate the inter-application interaction logic to be integrated from the application, encapsulate the interaction logic between applications, and then integrate the proxy to guide interactions between multiple applications. For example, WebService calls the proxy of remote server services locally]

 

Iv. Enterprise Integration (converged integration and integrated operation)

Application software systems can be divided into three layers: representation, business logic, and data. The N-layer structure system divides the business logic and database layer into more distributed business objects with less granularity. It mainly enhances the independence, configuration capability, flexibility, and scalability of the system.

Enterprise integration can be divided into: EAI (internal integration of enterprises) and B2B (mainly used for integration between enterprises)

EAI: frontend integration mode, presentation layer integration, and backend integration mode. [Application System Data Integration (data forwarding mechanism) ]. Hybrid integration [customers can access business applications or EAI servers through Web browser-based clients (thin clients]

 

5. Data interaction during Integration

1. EDI [electronic form]

2. xml

3. Step [Use Express (and related languages) to define integrated resources (how to express them) and check the consistency test of the application protocol and the implemented application protocol based on the Integration resource]

4. PDML [mainly solves the problem of insufficient XML definition, and uses the definition function in step to compensate for the disadvantages of insufficient DTD binding force in XML]

 

Vi. Integrated Basic Framework

1. OMG

2. COM +

3. J2EE

4. Web Service [UDDI is used for service registration and service search, WSDL is used to describe service interfaces and operation functions, and soap provides support for establishing communication between Web services and service requests]

 

Summary:

[Enterprise integration generally refers to the integration between the enterprise and the enterprise. In the process of integration, we need to establish a model that focuses on model reuse and componentization, when integrating an enterprise or industry, we should first conduct in-depth analysis to determine the establishment of requirements, functional models, and information models to implement system design and implementation, after completion, you can re-develop the Component Library Based on the running situation (spiral model) to determine your own component library. During the next re-development, you can quickly create a model based on the component as a prototype to understand the requirements and develop it]