Global service integration platform

Abstract

The global service integration platform is a lightweight hybrid integration platform designed to help organizations quickly and easily realize flexible flow and agile integration between data, applications, and services. The product is based on a three-layer architecture of service connection, namely: service decoupling, microservices, and capabilities, helping enterprises decouple systems, reorganize business logic and processes, and ultimately output IT capabilities, improve delivery efficiency, and enable organizational technological innovation and digital transformation, thereby facilitating business innovation. The service integration platform is mainly composed of a design center, a management center, a monitoring center, a runtime, and an open and sharing center.

Description

Technical Field

[0001] The Global Service Integration Platform (GIGP) adopts a loosely coupled service architecture with high performance, high availability and scalability. The front-end design center provides developers with graphical development and configuration through a Web interface. The development team does not need to rely on complex underlying network communication protocols and programming languages. With flexible and lightweight RESTful APIs, rich connectors and various components as the medium, a new type of parameterized development agile IT delivery production line has been built. According to business needs, enterprises rely on the powerful functional system of the Global Service Integration Platform (GIGP) to independently and efficiently create business processes, realize the interconnection between different local applications within the enterprise, between cloud applications, and between local applications and cloud applications, and respond to business quickly. Based on the Global Service Integration Platform (GIGP), service resources are built to form enterprise IT specifications, and the construction of an innovation capability platform is enabled to help enterprises transform digitally. The Global Service Integration Platform (GIGP) supports a high-availability deployment architecture. Each module supports multiple instance expansions to avoid single point problems. The system is equipped with health detection, and abnormal nodes are automatically shielded to ensure stable business operation. At the same time, multiple instances also increase the overall processing capacity of the cluster, and the overall performance increases linearly with the increase of components. The Global Service Integration Platform (GIGP) adopts one-click deployment to minimize deployment requirements. According to business needs, it can be deployed in a single machine or in a cluster. Application servers and data storage servers can be deployed centrally or in a physically dispersed and logically interconnected manner, which maximizes the principle of loosely coupled system construction. Background Art

[0002] With the in-depth development of cloud computing, big data, the Internet of Things, and mobile applications, many companies have applied new technologies to accelerate the digital transformation process, promote business development, and cope with increasingly fierce market competition in combination with their own development status. In order to make enterprises invincible in market competition, a series of keywords such as business innovation, cross-functional collaboration, process optimization, quality and efficiency improvement, service upgrade, and customer experience improvement have attracted much attention from enterprises. These keywords have gradually become the key elements for enterprises to enhance their core competitiveness. "Sustainable IT delivery capability" is its infrastructure and the "core" of digital transformation. The diversity of customer needs, the complexity and agility of business demands, and the increasing demand for enterprise IT have forced enterprises to apply more and more new technologies to respond to business needs. However, the sustainable IT delivery capability of enterprises has not been significantly improved. The main reasons are: First, after years of precipitation and development, enterprises have become highly dependent on core systems. Most of the core systems were built a few years ago and run very core business content. They are mainly stable and cannot be easily changed. Even if they need to be transformed, it will take a long time and cost a lot, which may also affect the current business development. Secondly, the new technology used to build new systems cannot be separated from the core business and run independently. When the old and new systems interact, heterogeneity in standards, protocols, and formats will occur, which will limit enterprise innovation. In order to better cope with the various pressures and challenges brought by the digital age and improve the sustainable IT delivery capabilities of enterprises, an agile, efficient, and lightweight resource is urgently needed. A system and data interaction method based on API (Application Programming Interface) is becoming a new focus. Summary of the invention

[0003] Global Service Integration Platform (GIGP) 1. The Global Service Integration Platform (GIGP) is a lightweight hybrid integration platform (HIP) designed to help organizations quickly and easily realize flexible flow and agile integration between data, applications, and services. The product is based on a three-layer architecture of service connection, namely: service decoupling, microservices, and capabilities, helping enterprises decouple systems, reorganize business logic and processes, and ultimately output IT capabilities, improve delivery efficiency, and enable organizational technological innovation and digital transformation, thereby facilitating business innovation. The service integration platform (GIGP) is mainly composed of a design center, a management center, a monitoring center, a runtime, and an open and sharing center.

[0004] Design Center is an easy-to-use, powerful and reliable data processing and distribution system for designing business processes and encapsulating them as RESTful APIs to become lightweight, reusable resources. The design concept is based on the flow-based programming model. The platform is based on a web graphical interface. Through dragging, connecting and configuring, it completes process-based design. It supports highly configurable data routing, conversion and system intermediate logic, supports dynamic data extraction from multiple data sources, automates data flows between systems, realizes data collection and processing, and then assists in data consolidation and integration, providing powerful and convenient assistance for connecting business systems. "Data flow" refers to the automated and managed information flow between systems. Because enterprises have multiple systems, some of which generate data and some of which consume data, the industry has discussed and summarized the problems, solutions and patterns that arise when integrating systems into a set of mature enterprise integration patterns (Enterprise Integration Patterns [EIP]). As a product, the integrated orchestration platform can help users implement various enterprise integration patterns. Design Center supports a variety of design components, which are divided into 7 major categories and 13 subcategories, including data processing, converters, databases, networks, files, big data, and execution. It supports mainstream database connections, network protocols, data format conversion, cloud service access, big data ecology, industrial Internet OPC and other standards, enterprise-level application access, process logic control, etc., enabling developers to achieve high-quality drag-and-drop rapid development in a code-free state and avoid reinventing the wheel.

[0005] The management center provides full life cycle management of services such as design, creation, testing, deployment, integration, management, operation and maintenance, and offline, mainly based on RESTful APIs, helping enterprises gain operational insights, further optimize processes, improve product and service models, and enhance corporate business value. The management center supports the unified conversion of various types of APIs into RESTful APIs, designs and builds RESTful APIs for specific business architectures, provides fast interactive APIs for different application systems, and presents data resources in a unified format. The management center provides multi-dimensional management such as projects, environments, and tenants. Projects are logical groupings of services, including a collection of different services, routes, and backends, and are often used as management and query dimensions for a service. They can be divided and defined according to the actual project name, organization, or business system. The environment is the actual environment (host / node) in which services run within the service management platform. It is generally recommended to divide the production environment and the test environment. When registering services, services can be deployed in different environments according to actual conditions. Tenants are used to logically isolate platform resources. Tenants include: projects and resources within projects, D2A (Database to API) applications, service portals, and resources within portals. They can be divided by organization to isolate resources from different organizations. The management center is also responsible for the unified authentication and rights management (SSO) of the platform. Relevant modules build users through the management center and assign different rights, which are generally divided into ordinary users, tenant administrators, and super administrators according to business. The management center also supports integration with the enterprise's LDAP, ADFS, SSO and other authentication centers.

[0006] Monitoring Center The monitoring center is the window of the entire platform business operation, and is an indispensable module for business display, problem debugging and location within the platform. It mainly has multi-dimensional statistical analysis, monitoring and alarm management, log management, data traceability and other functions. Multi-dimensional statistical analysis: the platform supports resource statistics in the dimensions of global, tenant, and project, and displays them in the form of charts to meet the needs of multi-level users. The global mode presents the global business operation status of the platform and provides friendly services for platform operators. Tenants display resource statistics reports within different organizations for different organizations. Statistics within the project are divided into service resources within the platform and backend resources (i.e. original service resources). Service statistics within the platform mainly include QPS (Queries per second), number of requests, response time, number of requests and other types. Log management: logs are important content generated during the operation of the business, which helps to quickly locate faults and problems during the operation of the business. The log management center provides high-performance and reliable log information collection, real-time update indexes and provide users with full-text retrieval. Data traceability: the system automatically records and indexes each operation log of the data flow, and tracks the data flow from beginning to end. This information can play an important role in other scenarios such as system fault diagnosis and optimization. The recorded fine-grained historical data enables users to view and replay the intermediate data of the data flow process.

[0007] Runtime The runtime provides an elastically scalable, highly reliable, and highly available deployment and operating environment for the API integration platform. It is mainly composed of modules such as service gateway, service runtime, orchestration process runtime, and distributed cluster deployment. The service gateway is the entry and exit of resource requests, and performs unified proxy and forwarding of services to achieve the connection of different systems. The service gateway can uniformly manage services, such as authentication, authorization, flow control, monitoring, etc. During the service runtime, the service runtime is responsible for providing a parsing engine for the advanced functions of the service runtime. It supports a variety of plug-in services, mainly frequency limitation, request conversion, blacklist and whitelist restrictions, parameter verification, service cache, XML / JSON format conversion, dynamic routing and other functional plug-ins. For example, parameter mapping parsing and conversion, protocol conversion when SOAP to REST, database conversion to API (D2A), API automatic generation of Swagger documents, authorization services, cache services, logs, etc. The service runtime engine is a stateless microservice developed based on Java and Spring Boot, which supports horizontal expansion. During the integration and orchestration runtime, the integration and orchestration runtime engine is developed based on Java and runs on the Java Virtual Machine (JVM). The platform uses a modern B / S architecture, and users can use a browser to design and debug processes in an easy-to-use Web user interface. The platform provides more than 13 types of components and is continuously increasing, making it easy to connect various heterogeneous systems, databases, network protocols, and perform data format conversion and logic processing. The integrated orchestration runtime can also be deployed and run in a cluster to meet users' high performance, high availability, and horizontal performance expansion requirements. Distributed cluster deployment, the platform implements high-availability cluster deployment based on load balancing, supports horizontal expansion according to business needs, and the test environment and production environment can be deployed in clusters. The underlying database is deployed in a cluster to ensure the stable operation of the business. The monitoring server uniformly monitors the operating status of each node. If an abnormality occurs, the administrator is quickly notified to locate the problem.

[0008] Open and Sharing Center The resource opening and sharing center helps improve the service ecosystem and has three roles: service producer, service manager and service consumer. The resource opening and sharing center can achieve the maximum utilization of resources, reduce duplication within the enterprise, improve the efficiency of cross-departmental and cross-business communication, and achieve seamless connection with the outside of the enterprise. There are mainly service portal, partner management, and open service content publishing modules. Partner management, that is, the consumer of service resources, uses / calls the objects that publish services in the service portal. The corresponding partners can use the resources within the authorized scope. Different API resources are integrated into an APP business to help quickly develop business. The service portal, that is, the service portal, is a portal platform for displaying service resources, with services such as authorization, application, and approval. Service managers can publish resources to the service portal and add policies to resources according to actual conditions; service consumers apply for the resources they need to access on the portal, and use different resources to create multiple APPs to provide services to the outside world. Open service content publishing, the developer portal supports unified publishing of development service content, sharing of orchestration process resource libraries, and focuses on developer operations, developer communities, and ecological services. The Global Service Integration Platform (GIGP) is a lightweight hybrid integration platform (HIP) designed to help organizations quickly and easily realize flexible flow and agile integration between data, applications, and services. The product is based on a three-layer architecture of service connection, namely: service decoupling, microservices, and capabilities, helping enterprises decouple systems, reorganize business logic and processes, and ultimately output IT capabilities, improve delivery efficiency, and enable organizational technological innovation and digital transformation, thereby facilitating business innovation. The service integration platform (GIGP) is mainly composed of a design center, a management center, a monitoring center, a runtime, and an open and shared center.

[0009] Design Center Design Center is an easy-to-use, powerful and reliable data processing and distribution system for designing business processes and encapsulating them as RESTful APIs to become lightweight, reusable resources. The design concept is based on the flow-based programming model. The platform is based on a web graphical interface. Through dragging, connecting and configuring, it completes process-based design. It supports highly configurable data routing, conversion and system intermediate logic, supports dynamic data extraction from multiple data sources, automates data flows between systems, realizes data collection and processing, and then assists in data consolidation and integration, providing powerful and convenient assistance for connecting business systems. "Data flow" refers to the automated and managed information flow between systems. Because enterprises have multiple systems, some of which generate data and some of which consume data, the industry has discussed and summarized the problems, solutions and patterns that arise when integrating systems into a set of mature enterprise integration patterns (Enterprise Integration Patterns [EIP]). As a product, the integrated orchestration platform can help users implement various enterprise integration patterns. Design Center supports a variety of design components, which are divided into 7 major categories and 13 subcategories, including data processing, converters, databases, networks, files, big data, and execution. It supports mainstream database connections, network protocols, data format conversion, cloud service access, big data ecology, industrial Internet OPC and other standards, enterprise-level application access, process logic control, etc., enabling developers to achieve high-quality drag-and-drop rapid development in a code-free state and avoid reinventing the wheel.

[0010] The management center provides full life cycle management of services such as design, creation, testing, deployment, integration, management, operation and maintenance, and offline, mainly based on RESTful APIs, helping enterprises gain operational insights, further optimize processes, improve product and service models, and enhance corporate business value. The management center supports the unified conversion of various types of APIs into RESTful APIs, designs and builds RESTful APIs for specific business architectures, provides fast interactive APIs for different application systems, and presents data resources in a unified format. The management center provides multi-dimensional management such as projects, environments, and tenants. Projects are logical groupings of services, including a collection of different services, routes, and backends, and are often used as management and query dimensions for a service. They can be divided and defined according to the actual project name, organization, or business system. The environment is the actual environment (host / node) in which services run within the service management platform. It is generally recommended to divide the production environment and the test environment. When registering services, services can be deployed in different environments according to actual conditions. Tenants are used to logically isolate platform resources. Tenants include: projects and resources within projects, D2A (Database to API) applications, service portals, and resources within portals. They can be divided by organization to isolate resources from different organizations. The management center is also responsible for the unified authentication and rights management (SSO) of the platform. Relevant modules build users through the management center and assign different rights, which are generally divided into ordinary users, tenant administrators, and super administrators according to business. The management center also supports integration with the enterprise's LDAP, ADFS, SSO and other authentication centers.

[0011] Monitoring Center The monitoring center is the window of the entire platform business operation, and is an indispensable module for business display, problem debugging and location within the platform. It mainly has multi-dimensional statistical analysis, monitoring and alarm management, log management, data traceability and other functions. Multi-dimensional statistical analysis: the platform supports resource statistics in the dimensions of global, tenant, and project, and displays them in the form of charts to meet the needs of multi-level users. The global mode presents the global business operation status of the platform and provides friendly services for platform operators. Tenants display resource statistics reports within different organizations for different organizations. Statistics within the project are divided into service resources within the platform and backend resources (i.e. original service resources). Service statistics within the platform mainly include QPS (Queries per second), number of requests, response time, number of requests and other types. Log management: logs are important content generated during the operation of the business, which helps to quickly locate faults and problems during the operation of the business. The log management center provides high-performance and reliable log information collection, real-time update indexes and provide users with full-text retrieval. Data traceability: the system automatically records and indexes each operation log of the data flow, and tracks the data flow from beginning to end. This information can play an important role in other scenarios such as system fault diagnosis and optimization. The recorded fine-grained historical data enables users to view and replay the intermediate data of the data flow process.

[0012] Runtime The runtime provides an elastically scalable, highly reliable, and highly available deployment and operating environment for the API integration platform. It is mainly composed of modules such as service gateway, service runtime, orchestration process runtime, and distributed cluster deployment. The service gateway is the entry and exit of resource requests, and performs unified proxy and forwarding of services to achieve the connection of different systems. The service gateway can uniformly manage services, such as authentication, authorization, flow control, monitoring, etc. During the service runtime, the service runtime is responsible for providing a parsing engine for the advanced functions of the service runtime. It supports a variety of plug-in services, mainly frequency limitation, request conversion, blacklist and whitelist restrictions, parameter verification, service cache, XML / JSON format conversion, dynamic routing and other functional plug-ins. For example, parameter mapping parsing and conversion, protocol conversion when SOAP to REST, database conversion to API (D2A), API automatic generation of Swagger documents, authorization services, cache services, logs, etc. The service runtime engine is a stateless microservice developed based on Java and Spring Boot, which supports horizontal expansion. During the integration and orchestration runtime, the integration and orchestration runtime engine is developed based on Java and runs on the Java Virtual Machine (JVM). The platform uses a modern B / S architecture, and users can use a browser to design and debug processes in an easy-to-use Web user interface. The platform provides more than 13 types of components and is continuously increasing, making it easy to connect various heterogeneous systems, databases, network protocols, and perform data format conversion and logic processing. The integrated orchestration runtime can also be deployed and run in a cluster to meet users' high performance, high availability, and horizontal performance expansion requirements. Distributed cluster deployment, the platform implements high-availability cluster deployment based on load balancing, supports horizontal expansion according to business needs, and the test environment and production environment can be deployed in clusters. The underlying database is deployed in a cluster to ensure the stable operation of the business. The monitoring server uniformly monitors the operating status of each node. If an abnormality occurs, the administrator is quickly notified to locate the problem.

[0013] Open and Sharing Center The resource opening and sharing center helps improve the service ecosystem and has three roles: service producer, service manager and service consumer. The resource opening and sharing center can achieve the maximum utilization of resources, reduce duplication within the enterprise, improve the efficiency of cross-departmental and cross-business communication, and achieve seamless connection with the outside of the enterprise. There are mainly service portal, partner management, and open service content publishing modules. Partner management, that is, the consumer of service resources, uses / calls the objects that publish services in the service portal. The corresponding partners can use the resources within the authorized scope. Different API resources are integrated into an APP business to help quickly develop business. The service portal, that is, the service portal, is a portal platform for displaying service resources, with services such as authorization, application, and approval. Service managers can publish resources to the service portal and add policies to resources according to actual conditions; service consumers apply for the resources they need to access on the portal, and use different resources to create multiple APPs to provide services to the outside. Open service content publishing, the developer portal supports unified publishing of development service content, sharing of orchestration process resource libraries, and focuses on developer operations, developer communities, and ecological services.

[0014] Registration Process Add a backend. The backend is the business system that provides the original service. After registering to the management platform, a new service is formed and an association relationship is established with the original business system. The backend is the basis for the original business service to register with the Global Service Integration Platform (GIGP). Create a route. The route is a logical grouping of services within the project. Original services with different paths under the same backend can access services through the same route. There is no need to define specific services to simplify the operation steps. It has the function of a transparent proxy. For routes, you can select request plug-ins such as frequency limit, blacklist and whitelist limit, XML and JSON conversion, etc. to expand the functional attributes of the route. Add a service, set the subpath of the service, define the request method of the service, and automatically select the corresponding backend. The added service is used to associate with the backend service. Select different functional plug-ins as needed. Requests support service caching, dynamic routing, parameter validation, request conversion, frequency limit, blacklist and whitelist limit, XML and JSON conversion, etc. Responses support output parameter mapping, XML and JSON conversion plug-ins. The use of different plug-ins improves the security and function enhancement of services. The process of adding services supports Mock test settings and has a Mock switch. Service producers can set whether to enable Mock testing on demand. The service log message also has a corresponding switch, which can be turned on or off on demand to meet the needs of different service developers. The process of adding services is also a document setting process. The platform supports setting request parameters, response results and error code definitions. After setting, the document will be automatically recorded in the platform to form an online document. There is no need to manually maintain offline documents, avoiding the phenomenon of inconsistency between documents and services. Submit and save. The entire registration process of adding backends, creating routes, and adding services requires only one submission confirmation for multiple steps, reducing repeated submission operations and improving service registration efficiency. By default, the service is saved in the workspace, which is equivalent to the service "buffer" for developing and debugging services. If the service is not saved, it will not take effect. Modifying the data in the development zone does not affect the official services that have been deployed and published to the portal. Save settings can be saved in the corresponding version number. Debugging, the debugging interface is a Postman-style test interface that lists the service list, selects the service to be tested, supports filling in service request parameters and other test content, and returns the test results after sending the test request. Create a version, debug and create a project version number to record the changes in services, routes and backends under the project. Select different version numbers to view the contents of services, routes and backends under this version. Only one version is allowed online at the same time on the platform, and it also supports switching deployment to historical versions to roll back configuration changes. Deployment and launch. When deploying services, you can choose different version numbers and different environments. Generally, they are divided into test environments and production environments. It supports single environment deployment and one-click deployment to multiple environments. During the deployment process, you can choose whether the service is online, and the online services can be published to the service portal.

[0015] Release Process Create a portal, create a portal to display services, and realize the sharing and opening of services. The Honeycomb platform supports the creation of multiple portals for different business scenarios. For example, create multiple portals such as internal portals, external portals, and department portals. Creating a portal requires a specific environment, generally a production environment or a test environment. After setting the environment, select the corresponding project and publish the API in the project to the newly created portal. Select a partner to associate with the corresponding partner, then the partner can see this portal, but may not have the right to use the services in the portal. Configure resources, the process of configuring resources is the process of publishing services in the management center to the portal. After the configuration is completed, the services in the portal are visible to the selected partners. Resource authorization, resource authorization is divided into use authorization and granular authorization. The administrator of the portal can pre-authorize certain users so that these users can directly use the resources published to the portal without applying. Users who have not obtained pre-authorization need to submit a use authorization application to the administrator before using the resources. When a user obtains the right to use a service, he or she will obtain a default usage frequency limit. When the user believes that the default frequency cannot meet the needs, he or she can initiate a granular authorization application to the administrator again to adjust the limit. After the portal is published and the resource and permission settings are completed, the portal can provide services. Partners have different permissions and see different resources on the portal.

[0016] Calling process Browse the portal. Partners can access anonymous service resources when not logged in. After logging in, they can access services that are visible to the partner. After logging in, you can see the application list and your own service list, application queue services, and service application records. Find resources. Select the required service resources according to different categories. The portal will display service call status, URL, request method, service document and other information. Authorized services can be directly called for testing, and unauthorized services need to apply for authorization. For permission application, select the corresponding service in the portal and submit the application. It will be sent to the administrator's waiting application queue. The application record can be viewed after logging in to the portal. The administrator applies for permissions in the portal management office, mainly including use application and quota adjustment application. After the use application is approved, partners can test and call resources. For resource call, the authorized resources can be tested in the portal by passing in the corresponding parameters. Authentication information is required when accessing services. Application authorization is created in the application list. The authentication method supports APIkey or Basic. The call example results refer to the service document example in the portal. Data statistics. The number of service calls is displayed in the service portal. Project monitoring displays the usage of services within the project, which is divided into backend services and service usage. The main dimensions are: number of visits, request methods, QPS, response time, traffic, status code, and access ranking. The dashboard displays the overall usage of the platform's management center, the total number of platform visits, the number of project error responses, gateway inlet and outlet traffic, etc. The monitoring center displays service statistics within the tenant. Relevant statistical information shows the status of services from various dimensions, providing customers with a full range of services.

[0017] Orchestrate the design process Business combing: Before designing a process, you need to comb through the business logic of the requirements, that is, the business scenario. Common businesses are the interaction of multiple systems to form a business process, and the results are returned after the business flow is completed. For example, after a new employee joins the company, after the employee information is created in one system, the relevant information is automatically synchronized to multiple heterogeneous systems using the orchestration process design. It is necessary to comb through the interaction methods of the relevant systems. The mainstream methods are RESTful API, SOAP Service, DB, files, etc., and then determine the workflow sequence and interaction content in each system. Process orchestration: Design the process according to the combed business, use different connectors to connect the corresponding systems, and from a technical perspective, different DBs, APIs, files, etc. are generally used for data interaction. The interaction process is designed to include protocol conversion, data format conversion, logic processing, response results, etc. The designed process determines whether it needs to be encapsulated as a service as needed. Scheduling: After the process design is completed, it is generally necessary to consider the operation mode of the process, that is, active operation and passive operation. Active operation is automatically run at a scheduled time in the platform. Set a process running time, and the process will automatically run on demand. Passive operation is driven by the outside world, such as encapsulation as a service service, and the service is called by the outside world, which triggers the operation of the entire process. The scheduling settings support setting the number of parallel tasks and selecting execution nodes. Monitoring: The process design needs to consider the request status during the process operation, so as to plan the required resources in advance. Process orchestration monitoring mainly includes data processing monitoring, multi-dimensional data flow monitoring, data traceability, etc. Data flow monitoring records and graphically displays dimensional information such as data flow, read and write data volume, and flow file processing volume within a certain period of time. Data traceability is used to track the flow of data and record it in the platform library. It can also index the data flow through the system to provide traceability data processing methods, such as input, output, conversion, etc., which is crucial for supporting compliance, troubleshooting, optimization, etc. Tuning: Based on the above monitoring information, analyze the points where bottlenecks or exceptions may occur during the process operation, and make adjustments and optimizations, or enhance the exception handling function. The tuning process can also improve the alarm function, support alarm strategy setting, use the corresponding connector, and send alarm notifications. The tuning process supports global tuning and partial tuning, and corresponding diversion components can be added to the process on demand. The process information will automatically be branched, and the tuning branch can be started and stopped at any time. After the tuning is completed, verify the stability and logic of the process. Combined with the monitoring content, confirm that all nodes are normal. After meeting business needs, consider the online environment and make corresponding preparations. Package the built process as a template backup, and set the read and write permissions of the process to ensure the safe operation of the process. After going online, the process orchestration is completed and packaged as a service on demand. The process will be automatically synchronized to the management center and published to the portal. Set the corresponding permissions and security measures, and provide services to the outside world. Authorized customers do not directly use the services of the orchestration platform. The orchestration process runs as a backend service during runtime.

[0018] Powerful functions, universal in the industry Service Lifecycle Management The management of the service lifecycle covers the design, creation, testing, deployment, integration, management, operation and maintenance, and offline processes of services. The Global Service Integration Platform (GIGP) provides one-stop services to help enterprises build all-round management service assets. The General Industry Support Design Center supports a variety of technical / business components. Currently, there are more than 13 types of components, supporting mainstream IT resource support such as cloud computing, big data, protocol conversion, format conversion, and database access. It has common IT standards and is suitable for various industries. Rich components. Common components include Dubbo, HTTP, SNMP, etc. Customized Industry Support The Global Service Integration Platform (GIGP) also provides exclusive connectors for the industry, such as industrial manufacturing-related OPC connectors, medical service HL7 connectors, etc., as well as service components such as IoT MQTT. Exclusive Business Support The Global Service Integration Platform (GIGP) also has connectors for some common systems. Taking SAP as an example, it supports connectors such as RFC and HANA, which can better combine SAP to provide services. For some specific businesses, exclusive database connections are supported.

[0019] Easy to use, easy to get started Drag-and-drop canvas process design The web interface of the design center uses drag-and-drop interactive design. You only need to use the mouse to drag the corresponding modules and components to build the design process. Compared with the traditional way of writing code, it greatly reduces the threshold for process designers to get started. A rich component library quickly meets complex business needs. Different modules and processes form different business processes, which improves the efficiency of process design. Seamless compatibility with code writing modules, direct platform reference, build a more complete business system, powerful and flexible. In addition to using the design center process orchestration design service, you can also quickly build database conversion services, so that you can quickly iterate, test and release new versions, and create RESTful open services for database services. You can also create multiple types of services and use flexible dynamic data conversion functions to generate the service request methods required by the enterprise. At the same time, you can set restriction rules through the management center to avoid exhausting backend infrastructure resources during unpredictable traffic peaks, thereby helping enterprises protect the security of existing services. Rapid application of process templates Since data flows are oriented to enterprise integration design patterns, there will be a common way to solve some integration problems. The system can share some classic general processing templates and reuse these pre-designed templates during process design, which helps to reduce user workload. The template function allows users to publish design templates and share them with others. Design and management automatically synchronize the processes arranged by the design center. After being encapsulated as services, they will be automatically synchronized to the management center without manual configuration. The processes in the first-level module are presented in the form of applications, and the management center manages the entire life cycle of the service. As a service background service, the design center synchronizes the resources of the management center to realize external services. When expanding the design service, plug-in interactive service functions can also add plug-in service functions such as security, caching, dynamic routing, format conversion, and request conversion to expand the security and functions of the service. In addition to the currently commonly used plug-in services, it also supports the development of new extension plug-ins to enhance the platform's functional expansion capabilities. Easily monitor service activities After the service deployment is completed, the service management center will provide a management cockpit so that enterprises can use the platform to intuitively monitor service calls, so as to understand the performance indicators and related information, traffic, and data delay of service calls. The management center can seamlessly connect to the design center's processes and provide full-life cycle status monitoring analysis and early warning services. Users can understand the operating status of all services at a glance to ensure the stability of the service.

[0020] Expand on demand and run stably The design of the high-performance, high-availability integrated orchestration platform is highly scalable. The system is based on the plug-in mode to enhance functions and expand the component library. As the scale expands, the dependencies between components will become more and more complicated. To solve this problem, the system architecture is designed to have very limited constraints between each extended component. Therefore, when creating an extended component, you don't have to pay too much attention to whether it will conflict with other components. The integrated orchestration platform can achieve horizontal expansion of performance by forming a cluster with many nodes. A single node is configured to process hundreds of megabytes of data per second. A moderate cluster configuration can process GB-level data per second, providing higher data throughput. The nodes in the cluster communicate with each other through internal protocols, share data and process information, and cooperate with load balancing to achieve high availability of the entire system. High-stability data backpressure, the system automatically manages the cache of all queue data in the data flow, and when the queue reaches the specified limit or timeout, it can provide data backpressure and suspend execution to prevent unnecessary pressure on the downstream system. Priority queues, there are often some very important data that need to be processed with low latency. The integrated orchestration platform can provide QoS guarantee services for these data streams. The queues in the data flow allow one or more priority schemes to be set to determine how the data is sorted in the queue. By default, the processing strategy is first-in-first-out, which can also be set to last-in-first-out, longest-queuing-time-first-out, or other processing strategies. To ensure data delivery, a core concept of the integrated orchestration center is that reliable data delivery must be guaranteed even in very high-scale and high-pressure environments. This is achieved by effectively utilizing customized continuous pre-write logs and content warehouse technologies. The platform is designed to support very high data throughput rates. During the flow process, data will be persisted to the hard disk through write-time copy technology to prevent data loss due to unexpected downtime. After the service is restored, the system will automatically restore the data snapshot from the hard disk. Flexible deployment and scalability With the help of the service management platform, enterprises can provide service requests with the lowest latency. It can also help manage traffic through restriction rules so that backend operations can withstand traffic peaks. In addition, the API management platform can also help improve the performance of the API by caching the output content of API calls to avoid unnecessary backend system calls.

[0021] Perfect system, safe and secure The security strategy of the Global Service Integration Platform (GIGP) mainly includes the security of the platform itself and the business security based on the platform. Platform Basic Security Unified User Identity and Authentication Management All users of the services and applications of the Global Service Integration Platform (GIGP) are authenticated through the unified user identity and authentication management system (IAM), and support OAuth2.0, OpenID Connect and SAML protocols. The platform supports docking with third-party LDAP, Active Directory or relational database user data systems to achieve rapid connection and application of the enterprise's internal authentication system. User role-based permission control mechanism All authenticated users of the Global Service Integration Platform (GIGP) use roles to control the access rights of system functions and data in each sub-application system. In addition to the basic roles built into the system, administrators can also create custom roles, define the role's functional modules and data access rights, and administrators assign permissions based on the user's responsibilities and qualifications. Users are authorized to use related functions in the platform based on role authorization. User permissions can be switched from one role to another as needed. Roles can be given new permissions based on new requirements and system mergers, and permissions can also be reclaimed from a role as needed. Encryption based on SSL / TLS ensures the security of communication links. All services open to the public in the Global Service Integration Platform (GIGP) can enable HTTPS encryption to ensure the security of data transmission in the data link when browsers and other clients access system services, effectively prevent malicious network sniffing, and avoid data and sensitive information leakage. Platform internal service security The Global Service Integration Platform (GIGP) itself is composed of various services to provide the system functions of the platform. Services may run on the same or different servers. All servers are enhanced by the system firewall. Through the configuration of firewall rules, the specified port is opened to the specified IP address, providing a trusted access environment for all platform services. Service business security within the platform Service authorization and authentication API Integration Platform (GIGP) uniformly uses the service portal as the release outlet, and all service consumers use the relevant service resources through the service portal. Services in the service portal are generally available in two modes: anonymous and authorized. Anonymous mode does not require logging in to the service portal to access the corresponding service; authorized mode requires logging in to the service portal, and the authorized service list can be accessed by logging in. Traffic control is also called frequency control. It can be used to control the access frequency based on services or projects. It can control the frequency of service calls allowed per unit time. If the request exceeds the set frequency, the actual platform business will not be accessible. It is used to protect backend services. Users can configure different traffic control strategies based on the performance and importance of the backend of the service to ensure stable operation and data security of the backend. The granularity of traffic control is: minutes, hours, and days.IP address blacklist / whitelist service providers can enable IP address blacklist and whitelist restrictions for service callers through plug-ins. After enabling, the gateway will match the IP address of the service caller with the IP blacklist / whitelist list. If the match is successful in the blacklist, the call will not be allowed. If a whitelist is configured, only the IP addresses in the whitelist can call the service. When designing services, parameter verification service providers can define the parameter type and parameter value (range, enumeration, regular expression, Json Schema) of the service. The gateway will verify the parameters of the call request based on the user-defined service parameters. The gateway will return an error code to the caller for requests that fail the verification to avoid illegal and invalid requests to the service backend. When the monitoring and alarm service request passes through the gateway, the gateway saves the important information of the request as a log and concentrates it in a unified log storage database. Users with permissions in the system can understand the operation status of the service through real-time, visual service monitoring charts, including: call volume, call method, response time, data traffic statistics and error rate. Users can also query and view detailed log information through the log query function, which is more convenient to locate the root cause of the error. It also supports custom API alarm strategies, alarms for abnormal situations, and faster response to failures. The SQL injection protection system adopts the "parameterized SQL template" method to execute database queries, which can effectively avoid SQL injection attacks. Log audit The system currently records the following types of logs, which can be used to discover risks and problems in the system. User login. User operation log API call log System service log.

[0022] Global Service Integration Platform (GIGP) Application Scenarios Transform the integration model and enable business innovation. Traditional customer integration methods mainly use databases, RESTful APIs, SOAP Services, files, etc. for point-to-point integration and use ESB to implement enterprise integration services. Traditional methods, especially point-to-point methods, have high integration coupling and poor stability. Data synchronization between production systems is inefficient and prone to errors. The systems are highly correlated and closely linked. A single move affects the entire system. Modification of one service point can easily cause abnormalities in other related nodes, which poses a high risk. Use a new integration method of the service platform, namely, service full life cycle management + drag-and-drop process orchestration design lightweight integration method, to form a unified and standardized RESTful API, decouple system resources, reduce the difficulty of docking between systems, achieve rapid response to business needs, improve docking efficiency, help enterprises quickly deliver business, and achieve business innovation. Take a manufacturing customer of the Global Service Integration Platform (GIGP) as an example. The customer previously used a point-to-point method for system integration and encountered some challenges in IT integration: From the implementation cycle, the previous integration content implementation delivery cycle was long and did not meet the rapid business needs. From the perspective of management and control, the previous integration method lacked unified interface management, perception, alarm, display and standardization support. One integration requirement needed to adapt to multiple standards, which increased the integration cost and reduced the integration efficiency. From the perspective of service, the previous integration method relied heavily on manufacturers, lacked the autonomy to control system integration and service delivery, and did not have the ability to independently and agilely develop standard services. The following values ​​were realized after using the Global Service Integration Platform (GIGP): First, it realized all-round exploration within the enterprise: online and offline docking, internal and external data and business interaction, supply chain collaboration, establishment of a service interface information management and display platform, etc.; second, it built a lighter and faster platform: providing a unified, lightweight system integration and agile delivery platform, autonomously controlling business delivery requirements, and allowing traditional manufacturing to quickly upgrade to intelligent manufacturing; third, it realized the interconnection of enterprise ecosystems: integrating and integrating all links of the customer ecosystem chain, realizing business collaboration, and greatly improving enterprise competitiveness. Build a service ecosystem to facilitate capability opening and sharing. Enterprises can organize and integrate internal service resources based on the Global Service Integration Platform (GIGP), build unified specifications, form IT assets, realize internal sharing, meet the resource usage needs of internal developers, and open service resources to the outside world to create an ecological service for developers, connect the enterprise itself and upstream and downstream partners, and create a win-win value chain.A customer of Global Service Integration Platform (GIGP) built a service open capability management platform based on API Integration Platform (GIGP), formulated unified service design specifications, sorted out the management boundaries of the open capability management platform, built a service management system, operation system and operation and maintenance guarantee mechanism, and provided full life cycle management of services, helping the group's customers to grasp the data usage in real time, gain insight into the value of resources within the enterprise, and obtain operational insight capabilities, and further optimize processes, improve products and innovate service models. Based on empowering developers, it can not only quickly meet the needs of current business, but also meet the sustainable development of the future, and ultimately empower the business development goals of the enterprise. The value of this customer using the Global Service Integration Platform (GIGP): First, combined with the Global Service Integration Platform (GIGP), a complete interface management specification is formulated on a daily basis to promote the interface governance work within the group; second, the Global Service Integration Platform (GIGP) is used to achieve extremely simple system collaboration and system docking, and realize the transformation from centralized management mode to assisted self-service management mode; third, the internal capabilities of the enterprise are open and released, and the unified entrance for the opening of the capabilities of various systems of the group to the outside world is realized; fourth, community exchanges and knowledge accumulation are formed to create a win-win ecological chain of capability opening. Develop service strategy middle platform and reshape IT global service integration platform (GIGP) to help customers integrate, build, manage and open enterprise resources from various business systems. According to different business classifications, multiple business capability centers are established to form a unified enterprise service strategy middle platform, empower enterprise development, and quickly respond to frequently changing business renewals. Customers build new businesses based on capability centers and reuse the capabilities shared by capability centers. There is no need to build each business module from scratch, which improves development efficiency. Taking a certain group customer as an example, the global service integration platform (GIGP) platform helps customers from service design, management, and opening to building a capability center around services, and ultimately realizes the three-party ecology of service producers, managers, and consumers. The global service integration platform (GIGP) continuously gathers group IT resources, taps into dormant IT value, and uses services to create a shared ecology and innovation power belonging to CIMC, ultimately realizing the company's service strategy and leading digital transformation. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 is a three-layer architecture diagram; Figure 2 is a platform composition diagram; Figure 3 is a draggable process design center diagram; Figure 4 is the lifecycle management diagram; Figure 5 is the overall architecture diagram; Figure 6 is the deployment architecture diagram; Figure 7 is the registration process diagram; Figure 8 is the release process diagram; Figure 9 is the call process diagram; Figure 10 is the orchestration design flow diagram; Figure 11 is the customer case - business innovation diagram; Figure 12 is the customer case - management platform architecture diagram; Figure 13 is the customer case - service strategy middle platform diagram based on the platform.

Claims

1. The Global Service Integration Platform (GIGP) is a lightweight hybrid integration platform (HIP) designed to help organizations quickly and easily realize flexible flow and agile integration between data, applications, and services. The product is based on a three-layer architecture of service connection, namely: service decoupling, microservices, and capabilities, helping enterprises decouple systems, reorganize business logic and processes, and ultimately output IT capabilities, improve delivery efficiency, and enable organizational technological innovation and digital transformation, thereby facilitating business innovation. The service integration platform (GIGP) is mainly composed of a design center, a management center, a monitoring center, a runtime, and an open and sharing center.

2. Design Center Design Center is an easy-to-use, powerful and reliable data processing and distribution system for designing business processes and encapsulating them into RESTful APIs to become lightweight, reusable resources. The design concept is based on the flow-based programming model. The platform is based on a web graphical interface. Through dragging, connecting and configuring, it completes process-based design. It supports highly configurable data routing, conversion and system intermediate logic, supports dynamic data extraction from multiple data sources, automates data flows between systems, realizes data collection and processing, and then assists in data consolidation and integration, providing powerful and convenient assistance for connecting business systems. "Data flow" refers to the automated and managed information flow between systems. Because enterprises have multiple systems, some of which generate data and some of which consume data, the industry has discussed and summarized the problems, solutions and patterns that arise when integrating systems into a set of mature enterprise integration patterns (Enterprise Integration Patterns [EIP]). As a product, the integrated orchestration platform can help users implement various enterprise integration patterns. Design Center supports a variety of design components, which are divided into 7 major categories and 13 subcategories, including data processing, converters, databases, networks, files, big data, and execution. It supports mainstream database connections, network protocols, data format conversion, cloud service access, big data ecology, industrial Internet OPC and other standards, enterprise-level application access, process logic control, etc., enabling developers to achieve high-quality drag-and-drop rapid development in a code-free state and avoid reinventing the wheel.

3. The management center provides full life cycle management of services such as design, creation, testing, deployment, integration, management, operation and maintenance, and offline, mainly based on RESTful APIs, to help enterprises gain operational insights, further optimize processes, improve product and service models, and enhance the business value of enterprises. The management center supports the unified conversion of various types of APIs into RESTful APIs, designs and builds RESTful APIs for specific business architectures, provides fast interactive APIs for different application systems, and presents data resources in a unified format. The management center provides multi-dimensional management such as projects, environments, and tenants. Projects are logical groupings of services, including a collection of different services, routes, and backends, and are often used as management and query dimensions for a service. They can be divided and defined according to the actual project name, organization, or business system. The environment is the actual environment (host / node) in which the service runs within the service management platform. It is generally recommended to divide the production environment and the test environment. When registering a service, the service can be deployed in different environments according to the actual situation. Tenants are used to logically isolate platform resources. Tenants include: projects and resources within the project, D2A (Database to API) applications, service portals, and resources within the portal. They can be divided by organization to isolate resources from different organizations. The management center is also responsible for the unified authentication and rights management (SSO) of the platform. Relevant modules build users through the management center and assign different rights, which are generally divided into ordinary users, tenant administrators, and super administrators according to business. The management center also supports integration with the enterprise's LDAP, ADFS, SSO and other authentication centers.

4. Monitoring Center The monitoring center is the window of the entire platform business operation, and is an indispensable module for business display, problem debugging and location within the platform. It mainly has multi-dimensional statistical analysis, monitoring and alarm management, log management, data traceability and other functions. Multi-dimensional statistical analysis: the platform supports resource statistics in the dimensions of global, tenant, and project, and displays them in the form of charts to meet the needs of multi-level users. The global mode presents the global business operation status of the platform and provides friendly services for platform operators. Tenants display resource statistics reports within different organizations for different organizations. Statistics within the project are divided into service resources within the platform and backend resources (i.e. original service resources). Service statistics within the platform mainly include QPS (Queries per second), number of requests, response time, number of requests and other types. Log management: logs are important content generated during the operation of the business, which helps to quickly locate faults and problems during the operation of the business. The log management center provides high-performance and reliable log information collection, real-time update indexes and provide users with full-text retrieval. Data traceability: the system automatically records and indexes each operation log of the data flow, and tracks the data flow from beginning to end. This information can play an important role in other scenarios such as system fault diagnosis and optimization. The recorded fine-grained historical data enables users to view and replay the intermediate data of the data flow process.

5. Runtime The runtime provides an elastically scalable, highly reliable, and highly available deployment and operating environment for the API integration platform. It is mainly composed of modules such as service gateway, service runtime, orchestration process runtime, and distributed cluster deployment. The service gateway is the entry and exit of resource requests, and performs unified proxy and forwarding of services to achieve the connection of different systems. The service gateway can uniformly manage services, such as authentication, authorization, flow control, monitoring, etc. During the service runtime, the service runtime is responsible for providing a parsing engine for the advanced functions of the service runtime. It supports a variety of plug-in services, mainly frequency limiting, request conversion, blacklist and whitelist restrictions, parameter verification, service caching, XML / JSON format conversion, dynamic routing and other functional plug-ins. For example, parameter mapping parsing and conversion, protocol conversion when SOAP to REST, database conversion to API (D2A), API automatic generation of Swagger documents, authorization services, cache services, logs, etc. The service runtime engine is a stateless microservice developed based on Java and Spring Boot, which supports horizontal expansion. During the integration and orchestration runtime, the integration and orchestration runtime engine is developed based on Java and runs on the Java Virtual Machine (JVM). The platform uses a modern B / S architecture, and users can use a browser to design and debug processes in an easy-to-use Web user interface. The platform provides more than 13 types of components and is continuously increasing, making it easy to connect various heterogeneous systems, databases, network protocols, and perform data format conversion and logic processing. The integrated orchestration runtime can also be deployed and run in a cluster to meet users' high performance, high availability, and horizontal performance expansion requirements. Distributed cluster deployment, the platform implements high-availability cluster deployment based on load balancing, supports horizontal expansion according to business needs, and the test environment and production environment can be deployed in clusters. The underlying database is deployed in a cluster to ensure the stable operation of the business. The monitoring server uniformly monitors the operating status of each node. If an abnormality occurs, the administrator is quickly notified to locate the problem.

6. Open and Sharing Center The resource opening and sharing center helps improve the service ecosystem and has three roles: service producer, service manager and service consumer. The resource opening and sharing center can achieve the maximum utilization of resources, reduce duplication within the enterprise, improve the efficiency of cross-departmental and cross-business communication, and achieve seamless connection with the outside of the enterprise. There are mainly service portal, partner management, and open service content publishing modules. Partner management, that is, the consumer of service resources, uses / calls the objects that publish services in the service portal. The corresponding partners can use the resources within the authorized scope. Different API resources are integrated into an APP business to help quickly develop business. The service portal, that is, the service portal, is a portal platform for displaying service resources, with services such as authorization, application, and approval. Service managers can publish resources to the service portal and add policies to resources according to actual conditions; service consumers apply for the resources they need to access on the portal, and use different resources to create multiple APPs to provide services to the outside world. Open service content publishing, the developer portal supports unified publishing of development service content, sharing of orchestration process resource libraries, and focuses on developer operations, developer communities, and ecological services.

Images