CN105657053A - SOA architecture-based data integration exchange platform - Google Patents
SOA architecture-based data integration exchange platform Download PDFInfo
- Publication number
- CN105657053A CN105657053A CN201610122753.9A CN201610122753A CN105657053A CN 105657053 A CN105657053 A CN 105657053A CN 201610122753 A CN201610122753 A CN 201610122753A CN 105657053 A CN105657053 A CN 105657053A
- Authority
- CN
- China
- Prior art keywords
- service
- subsystem
- platform
- esb
- data exchange
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 230000010354 integration Effects 0.000 title claims abstract description 48
- 238000012544 monitoring process Methods 0.000 claims abstract description 17
- 230000005540 biological transmission Effects 0.000 claims abstract description 11
- 238000000034 method Methods 0.000 claims description 16
- 238000006243 chemical reaction Methods 0.000 claims description 13
- 230000008569 process Effects 0.000 claims description 12
- 239000012141 concentrate Substances 0.000 claims description 11
- 238000012795 verification Methods 0.000 claims description 8
- 230000004044 response Effects 0.000 claims description 6
- 238000004458 analytical method Methods 0.000 claims description 5
- 238000013475 authorization Methods 0.000 claims description 4
- 230000008033 biological extinction Effects 0.000 claims description 4
- 238000012545 processing Methods 0.000 abstract description 6
- 238000011161 development Methods 0.000 abstract description 4
- 238000002955 isolation Methods 0.000 abstract description 4
- 238000010276 construction Methods 0.000 abstract description 3
- 238000007726 management method Methods 0.000 description 26
- 239000003795 chemical substances by application Substances 0.000 description 8
- 238000005516 engineering process Methods 0.000 description 6
- 230000008901 benefit Effects 0.000 description 5
- 238000013461 design Methods 0.000 description 5
- 235000019580 granularity Nutrition 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000018109 developmental process Effects 0.000 description 3
- 239000006185 dispersion Substances 0.000 description 3
- 230000004899 motility Effects 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 239000002131 composite material Substances 0.000 description 2
- 230000029305 taxis Effects 0.000 description 2
- 206010019233 Headaches Diseases 0.000 description 1
- 206010021703 Indifference Diseases 0.000 description 1
- 206010033799 Paralysis Diseases 0.000 description 1
- 238000012550 audit Methods 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 238000013497 data interchange Methods 0.000 description 1
- 230000003203 everyday effect Effects 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 238000005243 fluidization Methods 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 231100000869 headache Toxicity 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 210000000653 nervous system Anatomy 0.000 description 1
- 238000013439 planning Methods 0.000 description 1
- 238000012552 review Methods 0.000 description 1
- 239000000344 soap Substances 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
- 230000009897 systematic effect Effects 0.000 description 1
- 230000009466 transformation Effects 0.000 description 1
- 238000013519 translation Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/56—Provisioning of proxy services
- H04L67/567—Integrating service provisioning from a plurality of service providers
Abstract
The invention discloses a data integration exchange platform based on SOA architecture, which adopts ESB system architecture and is divided into six subsystems: the system comprises a front-end unified entry subsystem, an ESB core agent subsystem, a provider adapter subsystem, a service registration management subsystem, an ESB monitoring management subsystem and a file transmission subsystem. The invention defines the overall strategic positioning, ensures that all subsystems are mutually cooperated on the premise of independent construction, and avoids information isolated islands among the systems; the system integration facing to the service is realized, the fault isolation is realized, one system has problems, and the normal operation of other systems can not be influenced; the system stability and the expandability are fully improved. The problem of overhigh load of the server is solved, and the stable operation of the website is ensured; the system has high stability, the processing speed and the throughput capacity of large traffic can meet the requirements of customers, and better user experience is achieved; and the internal and external network channels are thoroughly opened, and the repeated development of the same interface is avoided.
Description
Technical field
The present invention relates to web services technologies field, be specifically related to a kind of data exchange and integration platform based on SOA framework, get through the data exchange and integration platform that intranet and extranet are mutual.
Background technology
In the past few years, the management philosophy of US enterprise, under the ordering about that intensified competition and IT develop, starts the management mode towards real-time type enterprise (real-timeenterprise) and develops. Real-time type enterprise is the concept that Gartner company puts forward, want to be a real-time type enterprise, enterprise is necessary for can to occurring to make reacting the most rapidly with key business any time and event anywhere, its response speed must be moment, i.e. zero propagation, a real-time type enterprise must possess the ability processing accident in real time.
Obviously, real-time type enterprise wants to when event occurs, just make corresponding reaction at once, it makes business administration be no longer passively the situation occurred is reacted, but can carry out actively reacting in time, when business opportunity occurs, complete business operation in real time, under the situation of zero propagation, seize the first market opportunities. Management and the operating of real-time type enterprise have presented the situation by event Real Time Drive operating capability and respond.
The integration of information system is proposed unprecedented high request by one enterprise possessing real time reaction ability, because splitting, by obstruction, it becomes real-time type enterprise with scattered system. For large enterprise, wanting to integrate an existing system inherently huge engineering, also to take into account the new demand of enterprise development in addition in integration, this is just extremely difficult. Visible, to want in the environment maintaining enterprise normal operation, the information communication simultaneously take into account the fusion between new-old system, solving between each branch and all departments and data sharing, the difficulty that true shift is a real-time type enterprise is very big.
In the face of the problem of these headaches, enterprise needs a technology platform that can really dissolve a difficult problem, and it should be from a strategic height, aloof on existing all technology platforms and application platform.So could being in dispersity and the hardware and software platform that also must not concentrate future integrates. Additionally, this platform also wants to contain following constantly growth and the demand of the dynamic IT application in enterprises changed, and can complete for new system, organic and naturally combine with existing system framework.
Current enterprise through long-term informationization build, have accumulated substantial amounts of business interface, through operation for many years, inevitably encounter some difficulty and bottlenecks, mainly have following some:
1. overall strategy location ambiguity, current subsystems is independently built, and between system, information island is serious, lacks overall strategy orientation and overall situation integrated planning.
2. Technical Architecture falls behind. Owing to Technical Architecture is to design before more than ten years to build, backward in technique, cannot realize " service handling separates with Business Processing ", also cannot realize the system integration of " service-oriented ".
3. system stability, autgmentability are poor. Every day 22 can receive the warning of " CPU usage 100% ", though web site architecture being adjusted for several times over more than ten years, but tackles the problem at its root not yet. The annual web-based registration peak traffic phase, easily breaks down in website, affects being normally carried out of business of paying taxes. Along with expansion or the variation of the scope of business, existing portal website can not be rapidly performed by respective extension or adjustment.
4. interaction design falls behind, poor user experience. Existing portal website function of search is poor, and website user experiences difference, and functional design thinking falls behind, and has bigger gap compared with domestic and international outstanding government portals, also cannot meet State Tax Administration's related request simultaneously.
5., because application build is in application layer, the processing speed of high traffic, handling capacity, stability can not meet demand.
6. intranet and extranet passage is not got through, it is impossible to communicate, and identical business interface needs repeatedly to develop at intranet and extranet.
ESB full name is EnterpriseServiceBus, i.e. ESB. It is the product that traditional middleware technology is combined with the technology such as XML, Web service. ESB provides connection maincenter most basic in network, is the essential elements constructing nervous system of enterprise. The appearance of ESB changes traditional software architecture, the solution more more cheap than traditional middleware product can be provided, simultaneously it can also eliminate the technological disparity between different application, allows different application server coordinate operation, it is achieved that communication between different services and integration. Functionally seeing, ESB provides event-driven and the tupe of document guiding and distributed running fluidization air flow, and it supports content-based route and filtration, has possessed the transmittability of complex data, it is possible to provide a series of standard interface.
Summary of the invention
The technical problem to be solved in the present invention is: in order to solve problem above, and the present invention provides a kind of data exchange and integration platform based on SOA framework.
The technical solution adopted in the present invention is:
Data exchange and integration platform based on SOA framework, it is characterized in that: described platform adopts the system architecture of ESB, it is divided into six big subsystems altogether: entry subsystem, ESB core agent subsystem (Broker), provider's adapter subsystem, service registry management subsystem, ESB monitoring management subsystem, file transmission subsystem are unified in front end, wherein
Entry subsystem is unified in front end: platform externally provides plurality of access modes, jms service, ftp service, ejb service, webservice service, mq service, platform consumer unifies entry subsystem by front end and transmits the request to MQ queue, processes for core agency;
ESB core agent subsystem: be verified being unified, by front end, the request message that entry subsystem comes into, whether exist including service, whether consumer's account whether correct, consumer has permission access service, whether message format is correct etc., next MQ queue is sent the message to, for provider's adapter subsystem processes after a series of checkings;
Provider's adapter subsystem: receive the message from ESB core agent subsystem, goes to access Producer according to information, response results is fed back to consumer;
Service registry management subsystem: described platform provides service registration functionality, realize the registration of service, the business service that other system exploitation realizes can be registered on data exchange and integration platform by platform service registering functional, and other system may have access to the service of platform registration after authorization;
ESB monitoring management subsystem: each channel is serviced service condition, each channel real time service quantity etc. and is monitored by described platform;
File transmission subsystem: described platform externally provides unified ftp server, it is provided that unified file transmission channel.
Described Subsystem logical is an entirety, physically runs with independent process, it is possible to concentrate deployment, also be able to break deployment, maintain the motility of system to greatest extent.
The thickness granularity of described provider's adapter subsystem can according to actual business demand flexible customization, provider's adapter can be shared by multiple service providers, also can one provider's adapter of a service provider, its design advantage be the system failure can be isolated granularity carry out flexibly control, by list operation system fault affect be reduced to minimum.
MQ, transmits trunk, builds the underlying transport of ESB (ESB), and IBMWebSphereMQ provides the transmission of reliable message for SOA.
Entrance, ESB core agency, three subsystems of provider's adapter are unified in described front end, by F5, ApacheHTTPServer, Nginx, MQ as entrance, can support the horizontal cross extension demand of subsystem.
Described unify entry subsystem according to front end, ESB core agent subsystem, provider's adapter subsystem are to concentrate to dispose or independent dispose, and are divided into three kinds of logics to dispose architecture modes: to concentrate deployment mode, distribution deployment mode, mashed up deployment mode.
Described platform to service configuration unified management, mainly include service registry, service examination & verification, service state management, service release management, service issue, rule configuration.
Described platform can adopt message encryption and message not to encrypt two ways according to safety need.
Described platform is also equipped with service logic management function, mainly includes message route, message distribution, message conversion, protocol conversion, service quality, service orchestration.
Described platform is also equipped with service monitoring management function, mainly includes service-creation, is altered to the management of extinction life cycle and to service operation monitoring analysis two parts.
Described platform adopts uniform data codes and standards to be managed.
The invention have the benefit that
1. specify that overall strategy positions, make subsystems cooperate under premise independent construction, it is to avoid information island between system.
2. achieving " service handling separates with Business Processing ", it is achieved that the system integration of " service-oriented ", accomplished Fault Isolation, a system goes wrong, and does not interfere with the properly functioning of other system.
3. substantially improve system stability, extensibility. Solve the problem that server load is too high, it is ensured that the stable operation of website.
4. system stability is high, and the processing speed of high traffic, handling capacity disclosure satisfy that customer demand, have good Consumer's Experience.
6. thoroughly get through intranet and extranet passage, it is to avoid the overlapping development of same-interface.
Accompanying drawing explanation
Fig. 1 is for concentrating deployment mode schematic diagram;
Fig. 2 is dispersion deployment mode schematic diagram;
Fig. 3 is mashed up deployment mode schematic diagram;
Fig. 4 is data interchange platform block diagram.
Detailed description of the invention
Below in conjunction with Figure of description, by detailed description of the invention, the present invention is further described:
Embodiment 1:
As shown in Figure 4, data exchange and integration platform based on SOA framework, described platform adopts the system architecture of ESB, it is divided into six big subsystems altogether: entry subsystem, ESB core agent subsystem (Broker), provider's adapter subsystem, service registry management subsystem, ESB monitoring management subsystem, file transmission subsystem are unified in front end, wherein
Entry subsystem is unified in front end: platform externally provides plurality of access modes, jms service, ftp service, ejb service, webservice service, mq service, platform consumer unifies entry subsystem by front end and transmits the request to MQ queue, processes for core agency;
ESB core agent subsystem: be verified being unified, by front end, the request message that entry subsystem comes into, whether exist including service, whether consumer's account whether correct, consumer has permission access service, whether message format is correct etc., next MQ queue is sent the message to, for provider's adapter subsystem processes after a series of checkings;
Provider's adapter subsystem: receive the message from ESB core agent subsystem, goes to access Producer according to information, response results is fed back to consumer;
Service registry management subsystem: described platform provides service registration functionality, realize the registration of service, the business service that other system exploitation realizes can be registered on data exchange and integration platform by platform service registering functional, and other system may have access to the service of platform registration after authorization;
ESB monitoring management subsystem: each channel is serviced service condition, each channel real time service quantity etc. and is monitored by described platform;
File transmission subsystem: described platform externally provides unified ftp server, it is provided that unified file transmission channel.
The operation system unified management of described platform:
Each operation system (includes service requester, service provider) has a login account to identify its identity at data exchange and integration platform, and in some essential informations of platform registration operation system, such as systematic name, provider, contact person, telephone number, enable state, message encryption state etc. The service of data exchange and integration platform needs service requester open system, so in order to prevent the randomness to service access and uncontrollability, service requester needs propose service request to data exchange and integration platform and can service be conducted interviews by examination & approval. The information that service request is submitted to includes: service name that application is called, service call method, system title, called side department, called side type, allocating time, performance requirement, the explanation of service call purpose, contact person etc. After user submits service access application to, data exchange and integration platform administrator needs application is carried out review operation.Platform administrator will contrast application information and the information on services that user submits to, checks whether called side system meets the requirement of service call, and whether service requester system has the right to obtain the information that service provides. After service access application approval is passed through, it is possible to for the access rights of service requester distribution service. So far, service requester obtains the mandate calling this service.
Embodiment 2:
On the basis of embodiment 1, Subsystem logical described in the present embodiment is an entirety, physically runs with independent process, it is possible to concentrate deployment, also be able to break deployment, maintain the motility of system to greatest extent.
Embodiment 3:
On the basis of embodiment 1, the thickness granularity of provider's adapter subsystem described in the present embodiment can according to actual business demand flexible customization, provider's adapter can be shared by multiple service providers, also can one provider's adapter of a service provider, its design advantage be the system failure can be isolated granularity carry out flexibly control, by list operation system fault affect be reduced to minimum.
Embodiment 4:
On the basis of embodiment 1, entrance, ESB core agency, three subsystems of provider's adapter are unified in front end described in the present embodiment, by F5, ApacheHTTPServer, Nginx, MQ as entrance, can support the horizontal cross extension demand of subsystem.
Embodiment 5:
On the basis that embodiment 1-4 is arbitrary, platform described in the present embodiment, unify entry subsystem according to front end, ESB core agent subsystem, provider's adapter subsystem are to concentrate to dispose or independent dispose, and are divided into three kinds of logics to dispose architecture modes: to concentrate deployment mode, distribution deployment mode, mashed up deployment mode.
As it is shown in figure 1, concentration deployment mode: advantage: deployment is simple, O&M is convenient; Combined with virtual technology, the overall relation need not understood between the built-in system of ESB, access system extending transversely of ESB;
Shortcoming: motility is short of relatively; Many application are deployed on same station server, there is the probability that an application causes whole station server to be paralysed.
As in figure 2 it is shown, dispersion deployment mode:
Advantage: overall system stability is high, but system failure isolation, it is convenient that independent backstage adapter updates;
Shortcoming: relatively concentrate deployment mode, the overall work extending transversely of ESB is big, requires higher to system operation maintenance personnel to the deployment framework of ESB system, configuration information.
As it is shown on figure 3, mashed up deployment mode:
The pluses and minuses that mashed up deployment mode combines concentration, dispersion is disposed.
Embodiment 6:
On the basis of embodiment 5, described in the present embodiment, platform is to service configuration unified management, mainly include service registry, service examination & verification, service state management, service release management, service issue, rule configuration;
Service registry
Data exchange and integration platform provides service registration functionality, it is achieved the registration of service. The business service that each system development realizes can be registered on data exchange and integration platform by platform service registering functional, and other system may have access to the service of platform registration after authorization;
The essential information of service registry includes: Services Code, service name, service said system, function declaration, service position, COS, service request messages form, service response message format, service examination & verification state, director, establishment time, enable state etc.;
Support that the service interface type accessed has: WebService(SOAP protocol version: 1.1,1.2), EJB(EJB2.1 and above version), JMS(JMSAPI1.0+ version), MQ, FTP;
Service examination & verification
Service in the registration of data exchange and integration platform can not license to service requester before examination & verification after service registry, is only used in and audits by just that service requester is visible afterwards through manager, could be authorized to call. Only it is in examination & verification just can be called by the service interface of state;
Service state manages
The state that is switched on/off of service can be configured by platform, and the service interface being in dead status can not call by Requested Party;
Service release manages
Platform preserves each version of service lifecycle, service interface configuration is not once revised, and the version before its amendment all preserves as old version;
Service is issued
Service formal externally issue after data exchange and integration platform is registered and passed through examination & verification. The formal interface externally issued can be authorized to service requester and access;
Rule configuration
Data exchange and integration platform realizes configuration to business function parameter, data conversion rule, routing rule configuration.
Embodiment 7:
On the basis of embodiment 6, platform described in the present embodiment can adopt message encryption and message not to encrypt two ways according to safety need.
System provides message encryption configuration item, and whether configurable message is encrypted in transmitting procedure. AES adopts RSA Algorithm. Platform service can provide PKI and private key for service provider and service requester. When adopting cipher mode, service invocation procedure relates to encryption and deciphering, the performance of platform is had impact. Consider accordingly, it would be desirable to do in safety and performance.
Embodiment 8:
On the basis of embodiment 7, platform described in the present embodiment is also equipped with service logic management function, mainly includes message route, message distribution, message conversion, protocol conversion, service quality, service orchestration.
Message route
The data exchange and integration platform information on services according to registration, when service requester sends service invocation request, configuration information according to request message obtains the information of destination service, and send the requests to service provider destination service and process, after service provider has processed, result is returned to service requester by data exchange and integration platform.
Message distribution
Data exchange and integration platform realizes based on the load contents (including encryption, compression and code conversion) exchanging the information of different-format, operation information between application, the function of formatting messages between the data type of the host-host protocol of isomery.
Message is changed
Data exchange and integration platform comprises service translation function, at service requester operation system and service provider operation system format transformation, simplifies the conversion of data form and value.
Protocol conversion
Support the protocol conversion of platform support services type, the technical implementation way of isolation service requester operation system and service provider operation system.
Service quality (SLA)
The integrated switching plane of service quality aspect data can provide the control of authority of platform registration service, flow-control, message encryption, call situation monitoring, abnormity prompt and Definition of the existing problems etc.
Service orchestration
The atomic service that multiple granularities are little is carried out layout and forms new service, complete new business function. For platform, composite services are exactly a new service, it is necessary to carry out unified management on platform, access with being the same to the access of other service to composite services.
Embodiment 9:
On the basis of embodiment 8, platform described in the present embodiment is also equipped with service monitoring management function, mainly includes service-creation, is altered to the management of extinction life cycle and to service operation monitoring analysis two parts.
Service lifecycle manages
Data exchange and integration platform management service, from the whole process creating, being altered to extinction, preserves and services the historical record changed each time.Service is modified every time, is required for prior notice service call side user, in order to called side is handled it. Service call side proposes the improvement idea of service also by data exchange and integration platform to service provider operation maintenance personnel.
Service operation monitoring analysis
Data exchange and integration platform service after externally issuing and formally called, data exchange and integration platform monitoring service interface call situation, including user to the access times of service, access Annual distribution, the success rate of service call, performance indications (service response time) etc. And service operation monitoring analysis function is provided, graphically show system operation maintenance personnel. When certain service call occurs abnormal, abnormal information is sent short messages to the operation maintenance personnel of this system by data exchange and integration platform, operation maintenance personnel is analyzed in the log information of data exchange and integration platform record according to the abnormal information received and is produced abnormal reason, in order to process in time.
Embodiment 10:
On the basis of embodiment 9, platform described in the present embodiment adopts uniform data codes and standards to be managed.
In the system integration of data exchange and integration platform, uniform data specification is very necessary. Taxation informatization is more complicated, and the operating information system of tax office is in different time development & construction mostly by different companies, entity attribute identical in different operation systems is likely to different marks, different data types to express, it is such as the identity of taxpayer equally, some system Taxpayer Identification Number (nsrsbh) represents, some system encodes (nsrbm) with taxpayer and represents. This situation ubiquity, therefore to mutual after avoiding each operation system time the deviation understood, it is very necessary for setting up unified data standard specification. Paying taxes service platform provides unified data standard, the specification representation of Business Entity, and what contribute to after system is efficient, correctly mutual.
Embodiment of above is merely to illustrate the present invention; and it is not limitation of the present invention; those of ordinary skill about technical field; without departing from the spirit and scope of the present invention; can also make a variety of changes and modification; therefore all equivalent technical schemes fall within scope of the invention, and the scope of patent protection of the present invention should be defined by the claims.
Claims (10)
1. based on the data exchange and integration platform of SOA framework, it is characterized in that: described platform adopts the system architecture of ESB, it is divided into six big subsystems altogether: entry subsystem, ESB core agent subsystem, provider's adapter subsystem, service registry management subsystem, ESB monitoring management subsystem, file transmission subsystem are unified in front end, wherein:
Entry subsystem is unified in front end: platform externally provides plurality of access modes, and platform consumer unifies entry subsystem by front end and transmits the request to MQ queue, processes for core agency;
ESB core agent subsystem: be verified being unified, by front end, the request message that entry subsystem comes into, sends the message to next MQ queue, for provider's adapter subsystem processes after a series of checkings;
Provider's adapter subsystem: receive the message from ESB core agent subsystem, goes to access Producer according to information, response results is fed back to consumer;
Service registry management subsystem: described platform provides service registration functionality, realize the registration of service, the business service that other system exploitation realizes is registered on data exchange and integration platform by platform service registering functional, the service of other system access platform after authorization registration;
ESB monitoring management subsystem: each channel is serviced service condition by described platform, each channel real time service quantity is monitored;
File transmission subsystem: described platform externally provides unified ftp server, it is provided that unified file transmission channel.
2. the data exchange and integration platform based on SOA framework according to claim 1, it is characterised in that: described Subsystem logical is an entirety, physically runs with independent process, it is possible to concentrate deployment, also be able to break deployment.
3. the data exchange and integration platform based on SOA framework according to claim 1, it is characterized in that: the thickness granularity of described provider's adapter subsystem can according to actual business demand flexible customization, provider's adapter can be shared by multiple service providers, also can one provider's adapter of a service provider.
4. the data exchange and integration platform based on SOA framework according to claim 1, it is characterized in that: described unify entry subsystem according to front end, ESB core agent subsystem, provider's adapter subsystem are to concentrate to dispose or independent dispose, and are divided into three kinds of logics to dispose architecture modes: to concentrate deployment mode, distribution deployment mode, mashed up deployment mode.
5. according to the arbitrary described data exchange and integration platform based on SOA framework of claim 1-4, it is characterised in that: described platform is to operation system unified management.
6. the data exchange and integration platform based on SOA framework according to claim 5, it is characterized in that: described platform to service configuration unified management, mainly include service registry, service examination & verification, service state management, service release management, service issue, rule configuration.
7. the data exchange and integration platform based on SOA framework according to claim 6, it is characterised in that: described platform can adopt message encryption and message not to encrypt two ways according to safety need.
8. the data exchange and integration platform based on SOA framework according to claim 7, it is characterized in that: described platform is also equipped with service logic management function, mainly include message route, message distribution, message conversion, protocol conversion, service quality, service orchestration.
9. the data exchange and integration platform based on SOA framework according to claim 8, it is characterized in that: described platform is also equipped with service monitoring management function, mainly include service-creation, be altered to the management of extinction life cycle and to service operation monitoring analysis two parts.
10. the data exchange and integration platform based on SOA framework according to claim 9, it is characterised in that: described platform adopts uniform data codes and standards to be managed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610122753.9A CN105657053A (en) | 2016-03-04 | 2016-03-04 | SOA architecture-based data integration exchange platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610122753.9A CN105657053A (en) | 2016-03-04 | 2016-03-04 | SOA architecture-based data integration exchange platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN105657053A true CN105657053A (en) | 2016-06-08 |
Family
ID=56493128
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610122753.9A Pending CN105657053A (en) | 2016-03-04 | 2016-03-04 | SOA architecture-based data integration exchange platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105657053A (en) |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106331100A (en) * | 2016-08-24 | 2017-01-11 | 金蝶软件（中国）有限公司 | Method and device for pushing business information to be processed |
| CN106598758A (en) * | 2016-12-14 | 2017-04-26 | 咪咕文化科技有限公司 | Method and system for centralized transferring and calling |
| CN106713464A (en) * | 2016-12-27 | 2017-05-24 | 山东中创软件商用中间件股份有限公司 | Service management method and device for enterprise service bus |
| CN107071048A (en) * | 2017-05-12 | 2017-08-18 | 浪潮软件股份有限公司 | It is a kind of based on http request forward without intrusive mood enterprise level service bus |
| CN107634948A (en) * | 2017-09-19 | 2018-01-26 | 金在（北京）金融信息服务有限公司 | Method for interchanging data and system |
| CN107749875A (en) * | 2017-10-11 | 2018-03-02 | 四川省电科互联网加产业技术研究院有限公司 | A kind of big data artificial intelligence analysis system |
| CN108234541A (en) * | 2016-12-14 | 2018-06-29 | 陕西省地方电力（集团）有限公司 | A kind of service management and system of enterprise's bus platform |
| CN108306866A (en) * | 2018-01-16 | 2018-07-20 | 厦门明延科技有限公司 | A kind of Enterprise Service Bus platform and data analysing method |
| CN109995598A (en) * | 2019-04-24 | 2019-07-09 | 普元信息技术股份有限公司 | The system and method for information service management is carried out for traditional forms of enterprises's services system |
| CN110189229A (en) * | 2018-05-16 | 2019-08-30 | 杜鹏飞 | Insure core business system in internet |
| CN110474989A (en) * | 2019-09-05 | 2019-11-19 | 山东浪潮商用系统有限公司 | Linking integration system and method based on network protocol |
| CN110531961A (en) * | 2019-07-24 | 2019-12-03 | 百度在线网络技术（北京）有限公司 | Intelligent Service broken shell system and method |
| CN111163166A (en) * | 2019-12-30 | 2020-05-15 | 广州银行股份有限公司 | Enterprise service bus system |
| CN112822080A (en) * | 2020-12-31 | 2021-05-18 | 中国人寿保险股份有限公司上海数据中心 | Bus system based on SOA architecture |
| CN112965717A (en) * | 2021-03-22 | 2021-06-15 | 深圳市城市交通规划设计研究中心股份有限公司 | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform |
| CN113778651A (en) * | 2021-09-22 | 2021-12-10 | 武汉众邦银行股份有限公司 | Method and device for realizing ESB enterprise bus service management based on asset model |
| CN115118745A (en) * | 2022-06-08 | 2022-09-27 | 浙江工业大学 | Performance equipment information interconnection platform system and construction method thereof |
| CN115150406A (en) * | 2022-09-01 | 2022-10-04 | 江苏博云科技股份有限公司 | Cross-data center distributed ESB configuration management system |
| CN117194164A (en) * | 2023-09-15 | 2023-12-08 | 国能大渡河大数据服务有限公司 | Information integration supervision platform and method based on ESB bus |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794409A (en) * | 2009-11-18 | 2010-08-04 | 山东浪潮齐鲁软件产业股份有限公司 | Real-time data exchange model of cross-platform application system |
| CN102736900A (en) * | 2011-03-31 | 2012-10-17 | 新奥特（北京）视频技术有限公司 | System architected by SOA-based application system platform and design method |
| CN102970112A (en) * | 2012-11-30 | 2013-03-13 | 中国电子科技集团公司第十五研究所 | System and method for transmitting system data |
| CN103873332A (en) * | 2014-03-28 | 2014-06-18 | 浪潮软件集团有限公司 | Method for providing enterprise service bus of unified service environment by tax system |
-
2016
- 2016-03-04 CN CN201610122753.9A patent/CN105657053A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101794409A (en) * | 2009-11-18 | 2010-08-04 | 山东浪潮齐鲁软件产业股份有限公司 | Real-time data exchange model of cross-platform application system |
| CN102736900A (en) * | 2011-03-31 | 2012-10-17 | 新奥特（北京）视频技术有限公司 | System architected by SOA-based application system platform and design method |
| CN102970112A (en) * | 2012-11-30 | 2013-03-13 | 中国电子科技集团公司第十五研究所 | System and method for transmitting system data |
| CN103873332A (en) * | 2014-03-28 | 2014-06-18 | 浪潮软件集团有限公司 | Method for providing enterprise service bus of unified service environment by tax system |
Non-Patent Citations (1)
| Title |
|---|
| 许红: "基于ESB架构的纳税人受理平台的设计与实现", 《中国优秀学士论文全文数据库信息科技辑》 * |
Cited By (25)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106331100A (en) * | 2016-08-24 | 2017-01-11 | 金蝶软件（中国）有限公司 | Method and device for pushing business information to be processed |
| CN108234541A (en) * | 2016-12-14 | 2018-06-29 | 陕西省地方电力（集团）有限公司 | A kind of service management and system of enterprise's bus platform |
| CN106598758A (en) * | 2016-12-14 | 2017-04-26 | 咪咕文化科技有限公司 | Method and system for centralized transferring and calling |
| CN106598758B (en) * | 2016-12-14 | 2021-04-06 | 咪咕文化科技有限公司 | Centralized forwarding and calling method and system |
| CN106713464B (en) * | 2016-12-27 | 2019-12-13 | 山东中创软件商用中间件股份有限公司 | service management method and device of enterprise service bus |
| CN106713464A (en) * | 2016-12-27 | 2017-05-24 | 山东中创软件商用中间件股份有限公司 | Service management method and device for enterprise service bus |
| CN107071048A (en) * | 2017-05-12 | 2017-08-18 | 浪潮软件股份有限公司 | It is a kind of based on http request forward without intrusive mood enterprise level service bus |
| CN107634948A (en) * | 2017-09-19 | 2018-01-26 | 金在（北京）金融信息服务有限公司 | Method for interchanging data and system |
| CN107749875B (en) * | 2017-10-11 | 2021-01-08 | 成都星时代宇航科技有限公司 | Big data artificial intelligence analytic system |
| CN107749875A (en) * | 2017-10-11 | 2018-03-02 | 四川省电科互联网加产业技术研究院有限公司 | A kind of big data artificial intelligence analysis system |
| CN108306866A (en) * | 2018-01-16 | 2018-07-20 | 厦门明延科技有限公司 | A kind of Enterprise Service Bus platform and data analysing method |
| CN110189229A (en) * | 2018-05-16 | 2019-08-30 | 杜鹏飞 | Insure core business system in internet |
| CN109995598A (en) * | 2019-04-24 | 2019-07-09 | 普元信息技术股份有限公司 | The system and method for information service management is carried out for traditional forms of enterprises's services system |
| CN110531961A (en) * | 2019-07-24 | 2019-12-03 | 百度在线网络技术（北京）有限公司 | Intelligent Service broken shell system and method |
| CN110474989A (en) * | 2019-09-05 | 2019-11-19 | 山东浪潮商用系统有限公司 | Linking integration system and method based on network protocol |
| CN111163166A (en) * | 2019-12-30 | 2020-05-15 | 广州银行股份有限公司 | Enterprise service bus system |
| CN111163166B (en) * | 2019-12-30 | 2022-03-22 | 广州银行股份有限公司 | Enterprise service bus system |
| CN112822080A (en) * | 2020-12-31 | 2021-05-18 | 中国人寿保险股份有限公司上海数据中心 | Bus system based on SOA architecture |
| CN112822080B (en) * | 2020-12-31 | 2022-09-16 | 中国人寿保险股份有限公司上海数据中心 | Bus system based on SOA architecture |
| CN112965717A (en) * | 2021-03-22 | 2021-06-15 | 深圳市城市交通规划设计研究中心股份有限公司 | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform |
| CN113778651A (en) * | 2021-09-22 | 2021-12-10 | 武汉众邦银行股份有限公司 | Method and device for realizing ESB enterprise bus service management based on asset model |
| CN115118745A (en) * | 2022-06-08 | 2022-09-27 | 浙江工业大学 | Performance equipment information interconnection platform system and construction method thereof |
| CN115150406A (en) * | 2022-09-01 | 2022-10-04 | 江苏博云科技股份有限公司 | Cross-data center distributed ESB configuration management system |
| CN115150406B (en) * | 2022-09-01 | 2022-11-22 | 江苏博云科技股份有限公司 | Cross-data center distributed ESB configuration management system |
| CN117194164A (en) * | 2023-09-15 | 2023-12-08 | 国能大渡河大数据服务有限公司 | Information integration supervision platform and method based on ESB bus |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105657053A (en) | SOA architecture-based data integration exchange platform | |
| Abbas et al. | Convergence of blockchain and IoT for secure transportation systems in smart cities | |
| US20210081366A1 (en) | Method and system for real-time collaboration and annotation-based action creation and management | |
| CN102640162B (en) | Dynamic access control to the document in electronic communication in cloud computing environment | |
| CN103391185B (en) | A kind of cloud security storage of track traffic Monitoring Data and processing method and system | |
| CN109447643A (en) | A kind of data-sharing systems and data sharing method based on block chain | |
| CN107977795A (en) | A kind of government procurement manages transaction system | |
| CN108280367A (en) | Management method, device, computing device and the storage medium of data manipulation permission | |
| WO2010139167A1 (en) | Expert support application system platform for government affair and business affair decision-making and its construction method | |
| Scheid et al. | Toward a policy-based blockchain agnostic framework | |
| CN109559258A (en) | Educational resource public service system | |
| KR102312857B1 (en) | Multicast encryption scheme for data-ownership platform | |
| CN102523206B (en) | Information system associated sharing and interoperation platform | |
| CN102263809A (en) | Method for realizing service safety control based on enterprise service bus and apparatus thereof | |
| CN111835723A (en) | Service data encryption transmission system and method based on cloud platform | |
| CN102289732A (en) | Network system for institution staffing management | |
| CN111950004A (en) | Equipment data acquisition method and equipment data system based on alliance chain | |
| CN109547551B (en) | Scientific and technological project dynamic supervision system | |
| KR102535322B1 (en) | System for providing privacy protection service and method thereof | |
| US20100325244A1 (en) | Real time data network | |
| US20210359837A1 (en) | Systems and methods for secure data computing and algorithm sharing | |
| Ceccarelli et al. | Introducing meta-requirements for describing system of systems | |
| CN110532313A (en) | DEU data exchange unit | |
| CN101227472A (en) | Method and system for managing finances information | |
| CN110109949A (en) | Social credibility information service platform |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| RJ01 | Rejection of invention patent application after publication | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20160608 |