Use the. NET platform to build an enterprise application system field (below)

Link

Many materials and experts have stressed that system development should abstract and encapsulate changes so that business independence can be achieved. However, the Business independence of this system is not global, this is an abstraction of inner collapse, and currently software engineering is only used to form a manifestation that is not as powerful as it is. Even if the interface exists in the software design, it is designed only to complete a business process or purpose. These interfaces are not abstract and are highly relevant to the business! This is not a feature of agile and Application Clusters.

2. implemented partial information application

Only by implementing information technology and having a fairly independent information system-"Information Island" Can enterprises see so-called "islands ".

3. Information Communication requirements cannot be met between existing systems

Information sharing or communication requirements cannot be met between information islands, which is another necessary condition for information islands. If there is no information communication channel between "Information Island", although an isolated "island" has been formed objectively, if there is no need for information communication between these islands, it is not an information islands.

4. The system itself lacks the ability to meet new information sharing needs

There are new information sharing requirements between existing systems, and information islands arise when the communication between systems cannot be established by adjusting system configurations to meet new requirements.

How can we solve this problem and have a relatively high investment income?

Before talking about this problem, we need to first understand SOA and the concept of "system field" built on this architecture.

Multiple reusable field components

Service-Oriented Architecture (SOA) is a component model that appliesProgramDifferent functional units (called services) are linked by well-defined interfaces and contracts between these services. Interfaces are defined in a neutral way. They should be independent of the hardware platform, operating system, andProgramming Language. This allows services built in various such systems to interact in a unified and universal manner.

This neutral interface definition (not forcibly bound to a specific implementation) is called the loose coupling between services. There are two advantages of loosely coupled systems: flexibility and gradual changes in the internal structure and implementation of each service that forms the entire application, it can continue to exist. On the other hand, tight coupling means that interfaces between different components of an application are closely linked with their functions and structures. Therefore, when some or all applications need to be modified, they are very fragile.

The need for loosely coupled systems comes from the need for business applications to become more flexible as needed to adapt to changing environments, for example, the policy, business level, business focus, partnerships, industry status, and other business-related factors that often change may even affect the nature of the business. We call a business that can flexibly adapt to environment changes as an on-demand business, you can make necessary changes to the way tasks are completed or executed.

The so-called "system field" is an enterprise system model built on the idea of SOA. the business logic layers of multiple systems are abstracted as WebServices to form a global "field ", each system can use this field to obtain the required business model. Based on the procurement and production examples mentioned above, there is no specific boundary between each system. Instead, an integrated business container is used to complete their respective tasks, this is the role and way of working of the "field.

How can we implement and interact with the logic in the "field?

Web Services is a new service-oriented architecture that is relatively traditional. The computing model implements a dynamic inheritance by providing dynamic service interfaces, and implements loose coupling between the application that publishes the service and the application that uses the service. At the same time, Web services allows applications to be divided into small logical components, making it easier to integrate services with small granularity.

Web services are software applications identified by URLs. APIs and bindings can be defined, described, and discovered through XML components, web services support direct interaction with other software applications through Internet-based protocols and using XML-based messages. Its main features are as follows:

1) protocol versatility.

2) Complete platform and language independence.

3) software reuse.

In addition, Web Services standardizes various key technologies in the Web Services System in the form of technical stacks, including service description, publishing, discovery, and message transmission.

The Web Services system uses the SOAP Protocol to implement communication between applications and services, and uses the WSDL file to provide a standard description of the service. Both soap and WSDL are based on XML, which ensures cross-platform XML operations. At the same time, soap generally uses the standard HTTP protocol to transparently penetrate the firewall.

1) web services promote interoperability.

2) web services promotes real-time integration.

3) web services reduces complexity through encapsulation.

3.3 integration of web services and applications

Application Integration solutions can be presented in many forms and appear at multiple levels. Three main types of application integration middleware solutions are data integration, business process integration, and function or method integration. Web services can completely change the point-to-point integration processing method in traditional application integration. By using Web Services and loose Application Integration, you can only implement a subset of Application Integration, which can achieve results. On the contrary, application integration must implement a comprehensive solution to closely integrate and connect all systems and applications supporting the business. Web Services, in a form of loose service bundle, can quickly and cheaply develop, publish, discover, and dynamically bind applications.

Based on the Reference Model of the WfMC Workflow Management System and the specific Web Service technology, A Web Services-Oriented Workflow Model should include service portals, service driver engines, service registration centers, message bus, information resource libraries, Web services components, process definition tools, and service process management tools. and other components.

In summary, the use of WebService technology, combined with the granularity evaluation and division of the business module, the enterprise system "field" can solve the information islands, and effectively achieve business flow sharing.

 

I amAicken)Welcome to my next articleArticle