CN105446809B - Platform migration method and device - Google Patents
Platform migration method and device Download PDFInfo
- Publication number
- CN105446809B CN105446809B CN201510860508.3A CN201510860508A CN105446809B CN 105446809 B CN105446809 B CN 105446809B CN 201510860508 A CN201510860508 A CN 201510860508A CN 105446809 B CN105446809 B CN 105446809B
- Authority
- CN
- China
- Prior art keywords
- platform
- file
- converted
- service
- resource
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/48—Program initiating; Program switching, e.g. by interrupt
- G06F9/4806—Task transfer initiation or dispatching
- G06F9/4843—Task transfer initiation or dispatching by program, e.g. task dispatcher, supervisor, operating system
- G06F9/485—Task life-cycle, e.g. stopping, restarting, resuming execution
- G06F9/4856—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration
- G06F9/4862—Task life-cycle, e.g. stopping, restarting, resuming execution resumption being on a different machine, e.g. task migration, virtual machine migration the task being a mobile agent, i.e. specifically designed to migrate
Abstract
The embodiment of the present invention discloses platform migration method and device.The described method includes: migrating the business logic codes of the first platform to the second platform；It includes: that the corresponding resource file of the first platform is converted into the corresponding resource file of the second platform that the business logic codes by the first platform, which are migrated to the second platform,；Modify front end frame.In embodiments of the present invention, migration of original platform to new platform is realized, reaches existing assets and is multiplexed to greatest extent.
Description
Technical field
The present invention relates to computer fields, more particularly to platform migration method and device.
Background technique
With the development of technology and business need, Construction Bank releases a new generation's J2EE Development Framework (platform), in order to reach
Be multiplexed to greatest extent to existing assets, need will the Module Development Method platform migration based on J2EE frame to platform.
Summary of the invention
The purpose of the embodiment of the present invention is that platform migration method and device is provided, to realize platform migration.
To achieve the above object, the present invention provides following schemes:
A kind of platform migration method, comprising:
The business logic codes of first platform are migrated to the second platform；The business logic codes by the first platform are moved
Moving to the second platform includes: that the corresponding resource file of the first platform is converted into the corresponding resource file of the second platform；
Modify front end frame.
Preferably, described the corresponding resource file of first platform is converted into the corresponding resource file of the second platform to include:
The JAVA file of first platform is subjected to code conversion, is converted into the corresponding JAVA file of second platform；It will be described
The Spring configuration file of first platform is converted into the corresponding Spring configuration file of second platform；By first platform
Name SQL file, be converted into the corresponding SQLMAP file of second platform；By the HBM file of first platform, conversion
At the corresponding SQLMAP file of second platform；It is flat that the error code resource file of first platform is converted into described second
The corresponding error code resource file of platform；The Xsd file of first platform is added to second platform to load.
Preferably, it includes: parsing that the Xsd file by first platform, which is added to second platform and carries out load,
The Xsd file of first platform generates the entity object class that can be applied to second platform.
Preferably, by the name SQL file of first platform, it is converted into the corresponding SQLMAP file of second platform
It include: that Ibatis claim information is added to the name SQL file；Increase NameSpace sound after the Ibatis claim information
Bright and packet path；SDO parameter is replaced with into Map parameter；Ibatis is integrated into spring container.
Preferably, the modification front end frame includes: the access way for increasing HTTP JSON, retains the access of AMF agreement
Mode；The corresponding front end ECS file of first platform is converted into the corresponding service registration file of second platform.
Preferably, described that the corresponding front end ECS file of first platform is converted into the corresponding clothes of second platform
Business registration file includes: to be converted into the corresponding service note of the second platform according to the fixed method of servicing of the front end ECS document
Volume file.
Preferably, the business logic codes by the first platform are migrated to the second platform further include: flat by described first
Corresponding the first process layer to second platform of the service logic of platform data analysis layer；By the first platform service process layer
The corresponding second processing layer to second platform of service logic；Other will be never called in the first platform logic process layer
The service logic of service logic, the corresponding third process layer to second platform；It will be in the first platform logic process layer
Call the service logic of other service logics, the corresponding fourth process layer to second platform.
Preferably, further includes: be converted into can run on second platform by the technology component of first platform
Technology component.
A kind of platform migration device, comprising:
Migration tools are used for, and the business logic codes of the first platform are migrated to the second platform；It is described by the first platform
It includes: that the corresponding resource file of the first platform is converted into the corresponding money of the second platform that business logic codes, which are migrated to the second platform,
Source file；
Front end frame modifiers, for modifying front end frame.
Preferably, further includes: technology component crossover tool, for the technology component of first platform to be converted into transport
Row is in the technology component on second platform.
In embodiments of the present invention, migration of original platform to new platform is realized, it is maximum to reach existing assets
Multiplexing.
Detailed description of the invention
It in order to more clearly explain the embodiment of the invention or the technical proposal in the existing technology, below will be to institute in embodiment
Attached drawing to be used is needed to be briefly described, it should be apparent that, the accompanying drawings in the following description is only some implementations of the invention
Example, for those of ordinary skill in the art, without any creative labor, can also be according to these attached drawings
Obtain other attached drawings.
Fig. 1 is P8 platform technology component diagram provided in an embodiment of the present invention；
Fig. 2 a, 2b are platform migration method flow schematic diagram provided in an embodiment of the present invention；
Fig. 3 provides platform migration apparatus structure schematic diagram for the embodiment of the present invention.
Specific embodiment
Following will be combined with the drawings in the embodiments of the present invention, and technical solution in the embodiment of the present invention carries out clear, complete
Site preparation description, it is clear that described embodiments are only a part of the embodiments of the present invention, instead of all the embodiments.It is based on
Embodiment in the present invention, it is obtained by those of ordinary skill in the art without making creative efforts every other
Embodiment shall fall within the protection scope of the present invention.
In order to make the foregoing objectives, features and advantages of the present invention clearer and more comprehensible, with reference to the accompanying drawing and specific real
Applying mode, the present invention is described in further detail.
A new generation of Construction Bank enterprise architecture is divided into seven layers: channel integration layer, customer service conformable layer, application integration layer,
External connection integrated layer, service of goods layer, data set stratification, administrative analysis layer, seven layer architectures are supported by 12 application platforms, a new generation
It will be constructed on this 12 platforms using with application component.
Above-mentioned 12 application platforms be respectively external client's channel integration service platform, interior employee's channel integration platform,
Customer service integration platform, application integration platform, external connection Integrated Service Platform, service of goods host platform, the open C of service of goods
Platform, service of goods J2EE platform, data integration platform, administrative analysis service platform, transaction controlling service platform, online transaction
Handle data service platform.
Service of goods J2EE platform (referred to as P8 platform) therein is a new generation's J2EE Development Framework.
P8 platform is in service of goods layer in seven layer architectures of new generation as P6/P7 platform.Based on answering for P8 platform
The registration publication of the online service provided by component is on application integration platform (P4).Other platforms all pass through P4 platform and call P8
The service of platform, when there are combined spots in the composite services of P8 platform, P8 platform calls other platforms also by P4 platform
(P6/P7) service of the publication on P4.Bulk service provided by each platform application component, by the lot size scheduling component tune on basis
Degree.
The technology component of P8 platform is as shown in Figure 1.Technology component is that application component (for example deposit by a loan component, housing reform finance
Money component etc.) basis, technology component realizes common technical functionality, and business logic codes are real on the basis of technology component
Existing service logic.
It is multiplexed to greatest extent to reach existing assets, needing will be based on the Module Development Method platform migration of J2EE frame
To P8 platform.The present invention provides its device of platform migration method thus, to realize platform migration.
Fig. 2 a is referred to, above-mentioned platform migration method may include following steps:
S1, the business logic codes of the first platform are migrated to the second platform；
S2, modification front end frame.
In other embodiments of the present invention, Fig. 2 b is referred to, above-mentioned platform migration method may include following steps:
S3, the technology component of the first platform is converted into the technology component that can run on the second platform.
It will be introduced one by one below.
One, business logic codes migration.
In the embodiment of the present invention, business logic codes migration be may particularly include:
The corresponding resource file of first platform is converted into the corresponding resource file of the second platform.
Wherein, the first platform is specially the Module Development Method platform (abbreviation SUP platform) based on J2EE frame, the second platform
Specially service of goods J2EE platform (abbreviation P8 platform).
SUP is migrated to P8 platform is related to the corresponding conversion of following resource items (resource file) altogether:
This means, the corresponding resource file of the first platform is converted into the corresponding resource file of the second platform can include:
1) the JAVA file of the first platform, is subjected to code conversion, is converted into the corresponding JAVA file of the second platform；
2) the Spring configuration file of the first platform, is converted into the corresponding Spring configuration file of the second platform；
3), by the name SQL file of the first platform and HBM file, it is converted into the corresponding SQLMAP file of the second platform；
4) the error code resource file of the first platform, is converted into the corresponding error code resource file of the second platform；
5) the corresponding front end ECS file of the first platform, is converted into the corresponding service registration file of the second platform；
6) the Xsd file of the first platform, is added to the second platform to load.
It should be noted that JAVA file to error code resource file is converted, belongs to business logic codes and convert, and front end
ECS file be converted into service registration file be accomplished that background business logic and front end show between mapping association conversion.
Resource file will be converted and be described in detail below.
The conversion of 1, spring configuration file.
Unified modification schema statement, modifies the data source name in spring-dao.xml, deletes spring-
Aop.xml file, the unified affairs section for configuring UCC layers.
The addition of 2, Xsd files.
In embodiments of the present invention, by the Xsd file of the first platform be added to the second platform carry out load may particularly include:
The Xsd file of SUP platform is parsed, generating can be applied to the entity object class of P8 platform (the entity object class of P8 platform is specially
PO\DO)。
For example, the information such as Xsd file, including name, age, gender of personal information, these information have in Xsd
Definition, for example the age can only be number etc..It is transformed into entity object, entity object must have name, age, gender these categories
Property, and attribute type will be corresponding on, for example the type of age attribute must be numeric type.
3, name SQL file turns SQLMAP file.
More specifically, can authoring tool class (resource handler) scan the first platform name SQL file, and it is done with
Lower modification:
(1) ibatis claim information is added in file header.
<！DOCTYPEsqlMap
PUBLIC"-//ibatis.apache.org//DTD SQL Map 2.0//EN"
"http://ibatis.apache.org/dtd/sql-map-2.dtd">
(2) increase namaspace declaration (namespace) after ibatis claim information, increase packet path.
(3) SDO parameter is replaced with into Map parameter: removal DataObject (processing ResultMap+ParameterMap,
It can choose generation entity class or be defined as Map).If class=in resultMap label
" commonj.sdo.DataObject " then regenerates the entity class that resultMap is defined, and path is the name affiliated project of SQL
Under entity class.path, entitled resultMap tag ID name initial caps of class, and by the new class of class value again assignment.
(4) ibatis is integrated into spring container.
Mainly realized by modification Spring configuration file applicationContext.xml:
1. modifying JNDI data source to obtain, SUP transaction management is replaced, removes SUP ucc MoniterInterceptor
(traffic volume measurement).
2. authoring tool class (resource handler) creates ibatis configuration file under each logic module packet.
Logical code can be divided into component packet.
3. authoring tool class (resource handler), corresponding each component packet creates sqlMapConfig.xml file, introduces
The SQLMAP file after all modifications under the component packet.
4, name SQL file/HBM file turns SQLMAP file.
The part is related to the modification of database manipulation DAO class, altogether includes the following:
(1) Sup Das Dao Support class is rewritten, SUP association is detached from
(2) Dao layers of related assisted class in SUP is rewritten
(3) Sup Das Template.java is rewritten, realizes the conversion of new and old data access API.
Sup Das Template is the master tool class of data access, and SUP platform encapsulates the data access based on SDO
Mode, new version is changed to be accessed with the mode of ibatis, but the interface exposed away is constant, is also achieved that upper
Layer identification code it is transparent.
(4) it rewrites the external of Sup Das Template class and the interface of service is provided.
(5) single table maintenance transformation:
1. writing Core Generator class, HBM file is parsed, the single table for generating SQLMAP, which adds to revise, looks into dynamic queries file.
2. the SQLMAP needed using single table maintenance is generated by tool according to project reality.
5, error code resource file is converted.
It mainly include abnormality processing/log conversion.Specific conversion includes: to rewrite SUP COMMON exception class and log
Class covers original method and entrance.
In other embodiments of the present invention, it is also necessary to correspond to the layering of service logic.
In SUP platform, service logic is forced to be divided into tri- layers of UCC/BS/DAO.In P8 platform, include DBB layers (the
One process layer), TBB layers (second processing layer), KBB layers (third process layers) and IBB layers (fourth process layer).
Then the above-mentioned business logic codes by the first platform, which are migrated to the second platform, may also include that
By corresponding DBB layer (the first processing to the second platform of the service logic of the first platform data process layer (DAO layers)
Layer)；
By the corresponding TBB layer (second processing to the second platform of the service logic of the first platform service process layer (UCC layers)
Layer)；
It will never call the service logic of other service logics in first platform logic process layer (BS layers), it is corresponding to second flat
The KBB layer (third process layer) of platform；
The service logic of other service logics will be called in first platform logic process layer (BS layers), it is corresponding to the second platform
IBB layer (fourth process layer).
Two, modify front end frame；
It should be noted that SUP platform, P8 platform are all rear ends, by SUP platform migration to P8 platform, front end frame is needed
It modifies.
Modification front end frame (message access and parsing module) specifically includes that
(1) access way for increasing HTTP JSON (for requesting access to for HFSB, retains the access of original AMF agreement
Mode).
(2) access way for modifying P8, enables the mode of JSON access, and the conversion of exploitation JSON2SDO and SDO2JSON is suitable
Orchestration can only support that entering the interface that ginseng is DataObject to interface calls, and cannot support other type adaptations to convert at present.
Three, the technology component of the first platform is converted into the technology component that can run on second platform.
SUP platform and service code are gone into P8 platform, need platform rank realize technology component conversion (conversion
Technology component is indicated in Fig. 1 with shade), while the interactive interface for retaining original service code and platform assembly is required, it needs
Interface encapsulation is carried out to each platform assembly.
Meanwhile SUP platform has used a large amount of SDO object and its data operating interface, according to technical specification of new generation, no
This part can be introduced P8 platform, so needing for SDO and its data operating interface to be replaced.
Foregoing description platform migration method, will introduce platform migration device herein below.
Refer to Fig. 3, above-mentioned platform migration device 300 can include:
Migration tools 1, for migrating the business logic codes of the first platform to the second platform；
Wherein, the business logic codes of the first platform are migrated to the second platform includes: by the corresponding resource of the first platform
File is converted into the corresponding resource file of the second platform.
Front end frame modifiers 2, for modifying front end frame.
Detail refers to record described previously herein, and therefore not to repeat here.
In other embodiments of the present invention, Fig. 3 is still referred to, above-mentioned apparatus may also include technology component crossover tool 3, use
In the technology component for being converted into the technology component of the first platform to can run on second platform.
Detail refers to record described previously herein, and therefore not to repeat here.
In other embodiments of the present invention, the corresponding resource file of the first platform is being converted into the corresponding money of the second platform
The aspect of source file, the Migration tools 1 in above-mentioned all embodiments can be used for:
The JAVA file of first platform is subjected to code conversion, is converted into the corresponding JAVA file of the second platform；
The Spring configuration file of first platform is converted into the corresponding Spring configuration file of the second platform；
By the name SQL file and HBM file of the first platform, it is converted into the corresponding SQLMAP file of the second platform；
By the HBM file of the first platform, it is converted into the corresponding SQLMAP file of the second platform；
The error code resource file of first platform is converted into the corresponding error code resource file of the second platform；
The Xsd file of first platform is added to the second platform to load.
Detail refers to record described previously herein, and therefore not to repeat here.
In specific implementation, SUP2 batch migrator can be used to assist to support the background logic part of existing SUP platform
It migrates to P8 platform.Migrator is handled by resource file different under analysis SUP using corresponding resource processor,
Generate the corresponding resource file of P8 frame.
Resource handler is the tool-class write in fact.The tool-class write uniformly is placed on
Under com.ccb.codeparser.impl packet, such as HBMResourceHandlerImpl.java (HBM file under SUP is parsed,
Generate name SQL file), (ecs.xml under parsing SUP, generates services to EcsResourceHandlerImpl.java
File), XsdResourceHandlerImpl.java (the xsd file under parsing SUP, generate data entity object) etc..Date
Tool-class, String tool-class, XML tool-class etc. have then been placed under com.ccb.codeParser.util packet.
To sum up, technical solution provided by the embodiment of the present invention, on the basis of realizing SUP platform migration to P8 platform,
Operation eliminates the reliance on SUP Server, is no longer based on the O&M deployment of Governor, application code and configuration file meet new one
For the basic fundamental specification of java frame.
Advantages of the present invention mainly uses P8 platform resource to greatest extent, can make full use of P8 infrastructure, meets
Framework specification and standard of new generation, and avoid later period P8 from upgrading bring collision problem, while providing tool to storage generation
Code is converted, and is reduced workload to the maximum extent, is remained the interface of original technology component, so that generation before and after platform migration
Code smooth transition.
Each embodiment in this specification is described in a progressive manner, the highlights of each of the examples are with other
The difference of embodiment, the same or similar parts in each embodiment may refer to each other.For system disclosed in embodiment
For, since it is corresponded to the methods disclosed in the examples, so being described relatively simple, related place is said referring to method part
It is bright.
Used herein a specific example illustrates the principle and implementation of the invention, and above embodiments are said
It is bright to be merely used to help understand method and its core concept of the invention；At the same time, for those skilled in the art, foundation
Thought of the invention, there will be changes in the specific implementation manner and application range.In conclusion the content of the present specification is not
It is interpreted as limitation of the present invention.
Claims (9)
1. a kind of platform migration method characterized by comprising
The business logic codes of first platform are migrated to the second platform；The business logic codes by the first platform migrate to
Second platform includes: that the corresponding resource file of the first platform is converted into the corresponding resource file of the second platform；Wherein resource text
Part includes: JAVA file, Spring configuration file, SQL file, HBM file, error code resource file and Xsd file；
Modify front end frame；Wherein, the modification front end frame includes:
Increase the access way of HTTP JSON, retains the access way of AMF agreement；
The corresponding front end ECS file of first platform is converted into the corresponding service registration file of second platform.
2. the method as described in claim 1, which is characterized in that described that the corresponding resource file of first platform is converted into second
The corresponding resource file of platform includes:
The JAVA file of first platform is subjected to code conversion, is converted into the corresponding JAVA file of second platform；
The Spring configuration file of first platform is converted into the corresponding Spring configuration file of second platform；
By the name SQL file of first platform, it is converted into the corresponding SQLMAP file of second platform；
By the HBM file of first platform, it is converted into the corresponding SQLMAP file of second platform；
The error code resource file of first platform is converted into the corresponding error code resource file of second platform；
The Xsd file of first platform is added to second platform to load.
3. method according to claim 2, which is characterized in that the Xsd file by first platform is added to described
Second platform carries out load
The Xsd file of first platform is parsed, the entity object class that can be applied to second platform is generated.
4. method according to claim 2, which is characterized in that by the name SQL file of first platform, be converted into described
The corresponding SQLMAP file of second platform includes:
Ibatis claim information is added to the name SQL file；
Increase namaspace declaration and packet path after the Ibatis claim information；
SDO parameter is replaced with into Map parameter；
Ibatis is integrated into spring container.
5. the method as described in claim 1, which is characterized in that described to turn the corresponding front end ECS file of first platform
Changing the corresponding service registration file of second platform into includes:
The corresponding service registration file of the second platform is converted into according to the fixed method of servicing of the front end ECS document.
6. the method as described in claim 1, which is characterized in that the business logic codes by the first platform are migrated to second
Platform further include:
By corresponding the first process layer to second platform of the service logic of the first platform data process layer；
By the corresponding second processing layer to second platform of the service logic of the first platform service process layer；
The service logic of other service logics will be never called in the first platform logic process layer, it is corresponding to second platform
Third process layer；
The service logic of other service logics will be called in the first platform logic process layer, it is corresponding to second platform
Fourth process layer.
7. the method as described in claim 1, which is characterized in that further include:
The technology component of first platform is converted into the technology component that can run on second platform.
8. a kind of platform migration device characterized by comprising
Migration tools are used for, and the business logic codes of the first platform are migrated to the second platform；The business by the first platform
It includes: that the corresponding resource file of the first platform is converted into the corresponding resource text of the second platform that logical code, which is migrated to the second platform,
Part；Wherein resource file includes: JAVA file, Spring configuration file, SQL file, HBM file, error code resource file and
Xsd file；
Front end frame modifiers, for modifying front end frame, wherein the modification front end frame includes: to increase HTTP JSON
Access way, retain the access way of AMF agreement, the corresponding front end ECS file of first platform be converted into described the
The corresponding service registration file of two platforms.
9. device as claimed in claim 8, which is characterized in that further include:
Technology component crossover tool can run on second platform for the technology component of first platform to be converted into
Technology component.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510860508.3A CN105446809B (en) | 2015-11-30 | 2015-11-30 | Platform migration method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201510860508.3A CN105446809B (en) | 2015-11-30 | 2015-11-30 | Platform migration method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105446809A CN105446809A (en) | 2016-03-30 |
| CN105446809B true CN105446809B (en) | 2019-01-25 |
Family
ID=55557045
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201510860508.3A Active CN105446809B (en) | 2015-11-30 | 2015-11-30 | Platform migration method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105446809B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111338685B (en) * | 2018-12-19 | 2023-11-21 | 卓望数码技术（深圳）有限公司 | Common component configuration method, device, equipment and storage medium |
| US20200244772A1 (en) * | 2019-01-30 | 2020-07-30 | Huawei Technologies Co., Ltd. | Method and system for cloud application and service integration using pattern-based discovery |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101714078A (en) * | 2008-10-06 | 2010-05-26 | 广东金宇恒科技有限公司 | Code generation method and device |
| CN103109271A (en) * | 2012-08-30 | 2013-05-15 | 华为技术有限公司 | Inter-platform application migration realization method and system |
| CN103440273A (en) * | 2013-08-06 | 2013-12-11 | 北京航空航天大学 | Data cross-platform migration method and device |
| CN104424002A (en) * | 2013-09-10 | 2015-03-18 | 中国科学院声学研究所 | Dynamic component loading method and system based on plug-in mechanism |
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
| CN104573121A (en) * | 2015-02-09 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | DB2 database migration tool migrating from AIX platform to K-UX platform |
| CN104699484A (en) * | 2015-03-17 | 2015-06-10 | 上海斐讯数据通信技术有限公司 | Method for transplanting Flash game to Android platform |
| CN104899332A (en) * | 2015-06-24 | 2015-09-09 | 浪潮(北京)电子信息产业有限公司 | Cross-platform migrating method and system for Sybase database |
-
2015
- 2015-11-30 CN CN201510860508.3A patent/CN105446809B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101714078A (en) * | 2008-10-06 | 2010-05-26 | 广东金宇恒科技有限公司 | Code generation method and device |
| CN103109271A (en) * | 2012-08-30 | 2013-05-15 | 华为技术有限公司 | Inter-platform application migration realization method and system |
| CN103440273A (en) * | 2013-08-06 | 2013-12-11 | 北京航空航天大学 | Data cross-platform migration method and device |
| CN104424002A (en) * | 2013-09-10 | 2015-03-18 | 中国科学院声学研究所 | Dynamic component loading method and system based on plug-in mechanism |
| CN104573056A (en) * | 2015-01-22 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | Database large data volume online migration method based on oracle |
| CN104573121A (en) * | 2015-02-09 | 2015-04-29 | 浪潮电子信息产业股份有限公司 | DB2 database migration tool migrating from AIX platform to K-UX platform |
| CN104699484A (en) * | 2015-03-17 | 2015-06-10 | 上海斐讯数据通信技术有限公司 | Method for transplanting Flash game to Android platform |
| CN104899332A (en) * | 2015-06-24 | 2015-09-09 | 浪潮(北京)电子信息产业有限公司 | Cross-platform migrating method and system for Sybase database |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105446809A (en) | 2016-03-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Zhao et al. | Strategies and methods for cloud migration | |
| US7743391B2 (en) | Flexible architecture component (FAC) for efficient data integration and information interchange using web services | |
| CA2777443C (en) | Automated enterprise software development | |
| US7131110B2 (en) | Method and apparatus for generating a code bridge | |
| US9916137B2 (en) | Rest service source code generation | |
| US20090271426A1 (en) | Converting between software objects | |
| US20050251533A1 (en) | Migrating data integration processes through use of externalized metadata representations | |
| US20050256892A1 (en) | Regenerating data integration functions for transfer from a data integration platform | |
| WO2018114366A1 (en) | Automatic ontology generation | |
| US20100064275A1 (en) | Extracting platform independent models from composite applications | |
| Kapitsaki et al. | Model-driven development of composite context-aware web applications | |
| CN104517181B (en) | Enterprise content management system and method for nuclear power station | |
| US8423561B2 (en) | Method and system for simplifying object mapping for a user interface | |
| CN102298518B (en) | Conversion from the administration order of technology the unknown to multiple management agreement | |
| CN1790343A (en) | System and method for producing interface code to use services of an enterprise information system | |
| CN105446809B (en) | Platform migration method and device | |
| Li et al. | Migrating legacy information systems to web services architecture | |
| US8555239B1 (en) | Mainframe-based web service development accelerator | |
| Kongdenfha et al. | Web service adaptation: Mismatch patterns and semi-automated approach to mismatch identification and adapter development | |
| CA2928316C (en) | Facilitating communication between software components that use middleware | |
| Sneed et al. | Linking legacy services to the business process model | |
| US8479175B1 (en) | Mainframe-based web service development accelerator | |
| AU2014338988A1 (en) | Facilitating communication between software components that use middleware | |
| TWI414995B (en) | Development and execution platform | |
| Desair et al. | Policy-driven middleware for heterogeneous, hybrid cloud platforms |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |