WO2019043462A1 - Systèmes et procédés de création de transmission d'interface automatisée entre systèmes hétérogènes dans un écosystème d'entreprise - Google Patents

Systèmes et procédés de création de transmission d'interface automatisée entre systèmes hétérogènes dans un écosystème d'entreprise Download PDF

Info

Publication number
WO2019043462A1
WO2019043462A1 PCT/IB2018/051004 IB2018051004W WO2019043462A1 WO 2019043462 A1 WO2019043462 A1 WO 2019043462A1 IB 2018051004 W IB2018051004 W IB 2018051004W WO 2019043462 A1 WO2019043462 A1 WO 2019043462A1
Authority
WO
WIPO (PCT)
Prior art keywords
web service
dxl
input
files
transformation
Prior art date
Application number
PCT/IB2018/051004
Other languages
English (en)
Inventor
Avishek DAS
Pabitra GHOSH
Pratick BHOWMICK
Ajay Kumar
Original Assignee
Tata Consultancy Services Limited
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tata Consultancy Services Limited filed Critical Tata Consultancy Services Limited
Publication of WO2019043462A1 publication Critical patent/WO2019043462A1/fr

Links

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/01—Protocols
    • H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
    • 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/565—Conversion or adaptation of application format or content

Definitions

  • the present application generally relates to an enterprise integration platform to facilitate interactions between heterogeneous systems. More particularly, the present application relates to systems and methods for creating automated interface transmission between heterogeneous systems in an enterprise ecosystem.
  • An Enterprise Application Integration is a process of integrating data or a function of two application programs. It facilitates sharing of data and processes among two different applications in an enterprise. It aims at modernizing, consolidating and coordinating the computer applications in an enterprise.
  • the EAI may also involve developing a new total view of an enterprise's business and its applications, seeing how existing applications fit into the new model, and then devising ways to efficiently reuse the existing while adding new applications and data.
  • the EAI may be a complicated process, especially when integrating existing legacy applications with new applications or Web services.
  • EAI integration challenges include cumbersome and high-maintenance point-to-point integrations that are time consuming as well as difficult to maintain during product version upgrade, real time bi-directional communications and collaborations between different products or systems requires significant manual coding efforts, difficulty in building a standardized, flexible integration and communication layer for all products or systems and unavailability of out-of- box adapters to facilitate integration of very commonly used interfaces. Still further because of wide scope of the EAI, integration efforts typically have far-reaching implications on the business. Once the processing of the most critical business functions is incorporated into an integration solution, the proper functioning of that solution becomes vital to the business. A failing or misbehaving integration solution can cost an organization millions of dollars in lost orders, misrouted payments and disgruntled customers.
  • a method for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem comprising a processor implemented steps of executing in parallel: transforming an external simple object access protocol (SOAP) web service to a different SOAP web service or a representational state transfer (RESTful) web service by: (a) mapping a source system to a target system using the SOAP web service input and output payload data structures, wherein the SOAP web service input and output payload data structures are obtained by parsing a web services description language (WSDL) file into a data exchange layer (DXL), to perform a value or a custom-logic web service transformation; and (b) generating, based on the source system being mapped to the target system, the SOAP web service input and output payload data structures and web service transformation details, the DXL generated code and package for deployment of one or more web application archive (WAR) files on an application server; transforming an external RESTful web service to a different SOAP / R
  • a system for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem comprising a memory storing instructions; one or more communication interfaces; and one or more hardware processors coupled to the memory via the one or more communication interfaces, wherein the one or more hardware processors are configured by the instructions to: transform an external simple object access protocol (SOAP) web service to a different SOAP web service or a representational state transfer (RESTful) web service by: (a) mapping a source system to a target system using the SOAP web service input and output payload data structures, wherein the SOAP web service input and output payload data structures are obtained by parsing a web services description language (WSDL) file into a data exchange layer (DXL), to perform a value or a custom-logic web service transformation; and (b) generating, based on the source system being mapped to the target system, the SOAP web service input and output payload data structures and web service transformation details, the DXL generated code and
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • FIG. 1 illustrates a block diagram of a system for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem according to an embodiment of the present disclosure
  • FIG. 2 is an architecture illustrating the components of a system for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem according to an embodiment of the present disclosure
  • FIG. 3 is a flowchart illustrating the steps involved for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem according to an embodiment of the present disclosure.
  • a Data Exchange Layer (DXL) application is an enterprise integration platform for a message transformation to facilitate interactions between one or more heterogeneous systems.
  • the DXL is an integrated platform supporting all Enterprise Architecture Integration (EAI) patterns and facilitates an interface configuration approach.
  • EAI Enterprise Architecture Integration
  • the DXL application further maintains a single repository of interface processes augmenting traceability and quicker enhancement capabilities.
  • FIG. 1 illustrates an exemplary block diagram of a system (100) for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem according to an embodiment of the present disclosure.
  • the system (100) includes one or more processors (104), communication interface device(s) or input/output (I/O) interface(s) (106), and one or more data storage devices or memory (102) operatively coupled to the one or more processors (104).
  • the one or more processors (104) that are hardware processors can be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, state machines, logic circuitries, and/or any devices that manipulate signals based on operational instructions.
  • the processor(s) is configured to fetch and execute computer-readable instructions stored in the memory.
  • the system (100) can be implemented in a variety of computing systems, such as laptop computers, notebooks, hand-held devices, workstations, mainframe computers, servers, a network cloud and the like.
  • the I/O interface device(s) (106) can include a variety of software and hardware interfaces, for example, a web interface, a graphical user interface, and the like and can facilitate multiple communications within a wide variety of networks N/W and protocol types, including wired networks, for example, LAN, cable, etc., and wireless networks, such as WLAN, cellular, or satellite.
  • the I/O interface device(s) can include one or more ports for connecting a number of devices to one another or to another server.
  • the memory (102) may include any computer-readable medium known in the art including, for example, volatile memory, such as static random access memory (SRAM) and dynamic random access memory (DRAM), and/or non-volatile memory, such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
  • volatile memory such as static random access memory (SRAM) and dynamic random access memory (DRAM)
  • non-volatile memory such as read only memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes.
  • ROM read only memory
  • erasable programmable ROM erasable programmable ROM
  • the architecture of the DXL (210) used for performing implementation of automated interface transformation between heterogeneous systems in an enterprise ecosystem may now be understood in detail.
  • the architecture of the DXL (210) comprise of a presentation layer (202), a business layer (204), a data access layer (206) and an oracle or external database (208) according to an embodiment of the present disclosure.
  • the presentation layer (202) comprises a HyperText Markup Language (HTML), one or more Cascading Style Sheets (CSS) and one or more Javascript files supporting AngularJS 1.x javascript framework.
  • the presentation layer (202) is responsible for integrating all formats of data into a standard format for effective communication between a plurality of components and other layers of the DXL (210).
  • the presentation layer (202) follows data programming structure schemes developed for different languages and provides the real-time syntax, required for communication between two objects such as layers, systems or networks.
  • the business layer (204) comprises one or more java components for one or more Spring 4.x business objects.
  • the data access layer (206) comprises one or more java components for one or more Spring 4.x data access objects (other than the business layer (204) java components above), a Hibernate 4.x, a plurality of Java Persistence Application Programming Interface (JPA) beans and an entity manager.
  • the data access layer (206) further comprises one or more methods for accessing data of the oracle or external database (208).
  • the data access layer (206) also comprises a plurality of data access objects. All interactions between the presentation layer (202) and the business layer (204) are performed over one or more Java RESTful web services (JAXRS) Jersey implementation (not shown in the figure). All interactions between the business layer (204) and the data access layer (206) are performed using one or more Spring Data Access Objects (DAO). All interactions between the data access layer (206) and the oracle or external database (208) are performed using a Hibernate Java Persistence Application Programming Interface (JPA) Entity Manager, a Java Persistence Query Language (JPQL) and one or more JPA entity relationships.
  • JPA Java Persistence Application Programming Interface
  • JPQL Java Persistence Query Language
  • FIG. 3 illustrates an exemplary flow diagram of a method for creating automated interface transformation between heterogeneous systems in an enterprise ecosystem.
  • the system (100) comprises one or more data storage devices of the memory (102) operatively coupled to the one or more hardware processors (104) and is configured to store instructions for execution of steps of the method by the one or more processors (104).
  • the steps of the method of the present disclosure will now be explained with reference to the components of the system (100) as depicted in FIG. 1 and the flow diagram.
  • the hardware processors (104) when configured the instructions performs one or more methodologies described herein.
  • the one or more hardware processors (104) perform parallel execution of the steps of transforming an external simple object access protocol (SOAP) web service to a different SOAP web service or a representational state transfer (RESTful) web service, transforming an external RESTful web service to a different SOAP / RESTful web service, importing using a RESTful web service, the data of an external database (208) into the DXL (210) for extracting the external database data into one or more input files, an extraction of the imported data of the oracle or external database (208) into the one or more files (for example, a .txt, a .csv or a .xml file) accessible using the RESTful web service finally performing, using the data of the external database (208) extracted, a transformation of one or more files of different format for creating an automated interface transformation workbench between the source system and the target system.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) perform a transformation of an external simple object access protocol (SOAP) web service to a different SOAP web service or a representational state transfer (RESTful) web service by uploading and parsing of one or more web services description language (WSDL) files (for example, a BancsEmployeeSearchSoapService.wsdl file) into the DXL (210) for generating an initial set of information on a hypertext transfer protocol uniform resource locator (HTTP URL) of the SOAP web service WSDL files uploaded, the SOAP web service implementation java class name, details of the SOAP web service operations specified in the one or more WSDL files and an input and output payload data structures for the SOAP web service operations.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) may further capture a user's preference of transforming the SOAP web service to the different SOAP web service or the RESTful web service by capturing a structural and subscription preferences from a target system and communicating the structural and subscription preferences from the target system to the DXL (210).
  • the one or more hardware processors (104) may then enable the user to upload the input and output payload data structures of the transformed web service in either one or more extensible Markup Language (XML) Schema Definition (XSD file), or as a raw XML data or as a raw JavaScript Object Notation (JSON) data for obtaining the source system details and communicating the details to the DXL (210).
  • XML extensible Markup Language
  • XSD file extensible Markup Language
  • JSON JavaScript Object Notation
  • the DXL Based on the target and source system details (like the HTTP URL, the java class name) and the input and output payload data structures details generated, the DXL (210) perform using a data translation and transformation layer (not shown in the figure), a field mapping, a value translation and populating of data, for example the data from any database in the source system, across one or more Java Nested Object Graphs.
  • the DXL (210) may then display a mapping screen to the user comprising one or more input and output tabbed sections further comprising of a left and a right panel, where the left panel include details of the source system payload data structure nested object graph and the right panel include details of the target system payload data structure nested object graph (as mentioned in the above examples of the input.xsd and output.xsd).
  • the user specifies the field-level mappings between the source system and the target system payload data structure nested object graphs by the one or more hardware processors (104).
  • the value translation may be a simple or a custom-logic based value translation.
  • the Simple value translation refers to value of a field being transferred as-is to the target system without any change.
  • the Custom-logic -based translation refers to changing the value to a different one based on a configured business logic.
  • the DXL (210) by the one or more hardware processors (104), generates a code for the transformed SOAP web service into a standard Java Platform, Enterprise Edition (J2EE) complaint one or more web archive (WAR) files that are deployment ready on an application server platform.
  • J2EE Java Platform, Enterprise Edition
  • WAR web archive
  • an application of the target system may further deploy, using the one or more hardware processors (104), a generated WAR deployment unit (the WAR deployment unit may be generated by the DXL (210) as a product of code generation for a set of one or more transformation processes) to an application server of preference (the user preference as to in which of the application server the DXL (210) is to be deployed) and retrieve the WSDL contract generated above by the source system.
  • a generated WAR deployment unit the WAR deployment unit may be generated by the DXL (210) as a product of code generation for a set of one or more transformation processes
  • the target application may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to a servlet container forming a part of the application server of choice (the user preference as to in which of the application server the DXL (210) is to be deployed).
  • the servlet container refers to a corresponding servlet container of the application server where the DXL (210) is to be deployed.
  • the servlet container may be a JBoss, Websphere, Oracle etc.
  • the DXL (210) may then communicate the information on the HTTP URL of the proxy RESTful web service and one or more blank JSON / XML data structures of the input output payload to the proxy RESTful web service. Since the DXL (210) generates a POST (a HTTP POST method) format proxy execution points as transformed web services, hence for transformation into the different RESTful web service, the HTTP URL generated above is in the POST format.
  • POST HTTP POST method
  • the proxy SOAP or RESTful web service generated by the DXL (210) is consumed by the target system that remains totally unaware of the actual SOAP web service generated initially by the source system.
  • a code generated by the DXL (210) handles one or more proxying calls from the target system and automatically calls / invokes the SOAP web service from the source system for performing the transformation of the external simple object access protocol (SOAP) web service to the different SOAP web service or the representational state transfer (RESTful) web service.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) perform a transformation of an external RESTful web service to a different SOAP or a REST web service by generating for the RESTful web service, using the one or more hardware processors (104), the HTTP end-point URL of the RESTful web service in a pre-defined template format with potential placeholders for the one or more paths and query parameters along with the input and output payload data structures as an arbitrary JSON data. This is preceded by generating of the service contract by the source system which generates the RESTful web services.
  • Example of the pre-defined template format may be http://
  • the one or more hardware processors (104) may further capture the user's preference of transforming the RESTful web service to the different SOAP web service or the RESTful web service by capturing the structural and subscription preferences from the target system and communicating the structural and subscription preferences from the target system to the DXL (210).
  • the one or more hardware processors (104) may then enable the user to upload the input and output payload data structures of the transformed web service in either the one or more extensible Markup Language (XML) Schema Definition (XSD file), or as the raw XML data or as the raw JavaScript Object Notation (JSON) data for obtaining the source system details and communicating the details to the DXL (210).
  • XML extensible Markup Language
  • XSD file extensible Markup Language
  • JSON JavaScript Object Notation
  • the DXL (210) Based on the target and source system details and the input and output payload data structures details generated, the DXL (210) perform using the data translation and transformation layer (not shown in the figure), the mapping and populating of data (the data which the source system needs to exchange with the target system in any specific format, for example, the data from any database from the source system) across the one or more Java Nested Object Graphs.
  • the DXL (210) may then display the mapping screen to the user comprising the one or more input and output tabbed sections further comprising of the left and the right panel, where the left panel include details on the source system payload data structure nested object graph and the right panel include details on the target system payload data structure nested object graph.
  • the user specifies the field-level mappings between the source system and the target system payload data structure nested object graphs by the one or more hardware processors (104).
  • the value translation may be the simple or the custom-logic based value translation as explained above.
  • the DXL (210) by the one or more hardware processors (104), generates the code for the transformed RESTful web service into the standard Java Platform, the Enterprise Edition (J2EE) complaint one or more web archive (WAR) files that are deployment ready on an application server platform.
  • J2EE Java Platform
  • WAR web archive
  • an application of the target system may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to the application server of preference (the user preference as to in which of the application server the DXL (210) is to be deployed) and retrieve the WSDL contract generated above by the source system.
  • the target application may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to the corresponding servlet container, for example, the Jboss or Oracle, forming a part of the application server of preference (the user preference as to in which of the application server the DXL (210) is to be deployed).
  • the DXL (210) may then communicate the information on the HTTP URL of the proxy RESTful web service and the one or more blank JSON / XML data structures of the input output payload to the proxy RESTful web service. Since the DXL (210) generates the POST format proxy execution points as transformed web services, hence for transformation into the different RESTful web service, the HTTP URL generated above is in the POST format.
  • the proxy SOAP or RESTful web service generated by the DXL (210) is consumed by the target system that remains totally unaware of the actual SOAP web service generated initially by the source system.
  • the code generated by the DXL (210) handles one or more proxying calls from the target system and automatically calls / invokes the SOAP web service from the source system for performing the transformation of the external simple object access protocol (SOAP) web service to the different SOAP web service or the representational state transfer (RESTful) web service.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) perform importing, using a RESTful web service, the data of the oracle or external database (208) into the DXL (210) for extracting the data of the oracle or external database (208) into one or more input files (for example, a JSON file) by connecting and establishing, using a database adapter, the DXL (210) with the oracle or external database (208) for retrieving one or more procedural language structural query language (PL/SQL) code objects from a schema of the oracle or an external database (208) and the input and output payload data structure details of the RESTful web service to be generated by the DXL (210).
  • P/SQL procedural language structural query language
  • the DXL (210) connection with the oracle or external database (208) may be further used to carry out a host of operations like a batch file processing.
  • configuration details like the database host name, port number, unique or service name, user name, password and a Java Database Connectivity (JDBC) driver class name etc need to be captured and generated while establishing the connection.
  • JDBC Java Database Connectivity
  • the DXL (210) After the connection with the external database (that is the oracle or external database (208) that the DXL (210) will connect to for exposing a database source code) is successfully tested and ascertained, the DXL (210) further retrieves a plurality of schemas from the oracle or external database (208) and generate the one or more PL/ SQL code objects in a procedure, package and function under the plurality of schemas. The user may then select the one or more PL/SQL code objects for performing operations like batch file processing. Based upon the one or more PL/SQL code objects selected by the user, the DXL (210) may identify, read and generate one or more object signatures and arguments.
  • the external database that is the oracle or external database (208) that the DXL (210) will connect to for exposing a database source code
  • the input output payload data structure details of the proxy RESTful web service will be based upon the one or more PL/SQL code objects signatures and will be generated by the DXL (210).
  • the DXL (210) may further perform an identification of one or more input files (the one or more input files containing data in any specific format to be transferred from the source system to the target system) to be generated along with structural details of the one or more input files.
  • the DXL (210) may, using a file adapter, configure a relevant metadata information relating to the one or more input files identified to capture in the file adapter a host of information relating to the one or more input file names, file extensions, an operating system network filer location and the internal data structure. Based on the above details captured in the file adapter, the DXL (210) may further identify the input and output payload data structures details and the one or more PL/SQL objects code of the one or more input files.
  • the DXL (210) may then perform using the data translation and transformation layer (not shown in the figure), the mapping and populating of the data (the data in any specific format which the source system will transfer to the target system) across the one or more Java Nested Object Graphs.
  • the DXL (210) may then display the mapping screen to the user comprising the one or more input and output tabbed sections further comprising of the left and the right panel, where the left panel include details on the source system payload data structure nested object graph and the right panel include details on the target system payload data structure nested object graph.
  • the user specifies the field-level mappings between the source system and the target system payload data structure nested object graphs by the one or more hardware processors (104).
  • the value translation may be the simple or the custom-logic based value translation as explained above.
  • the DXL (210) by the one or more hardware processors (104), generate code for the transformed RESTful web service into the standard Java Platform, Enterprise Edition (J2EE) complaint one or more web archive (WAR) files that are deployment ready on the application server platform.
  • J2EE Java Platform, Enterprise Edition
  • WAR web archive
  • the target application may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to the corresponding servlet container forming a part of the application server of the user's preference.
  • the DXL (210) may then communicate the information on the HTTP URL of the proxy RESTful web service and the one or more blank JSON / XML data structures of the input output payload to the proxy RESTful web service. Since the DXL (210) generates the POST format proxy execution points as transformed web services, hence for the transformation into the different RESTful web service, the HTTP URL generated above is in the POST format.
  • the proxy SOAP or RESTful web service generated by the DXL (210) is consumed by the target system that remains totally unaware of the actual SOAP web service generated initially by the source system.
  • the code generated by the DXL (210) handles one or more proxying calls from the target system and automatically calls / invokes the SOAP web service from the source system for performing the transformation of the external simple object access protocol (SOAP) web service to the different SOAP web service or a representational state transfer (RESTful) web service.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) perform an extraction of the imported data of the oracle or external database (208) into the one or more files (for example, a .txt, a .csv or a .xml file) accessible using the RESTful web service by connecting and establishing, using a database adapter, the DXL (210) with the oracle or external database (208) for retrieving one or more procedural language structural query language (PL/SQL) code objects from a schema of the oracle or an external database (208) and the input and output payload data structure details of the RESTful web service to be generated by the DXL (210).
  • P/SQL procedural language structural query language
  • the DXL (210) connection with the oracle or external database (208) may be further used to carry out a host of operations like a batch file processing.
  • configuration details like the database host name, port number, unique or service name, user name, password and a Java Database Connectivity (JDBC) driver class name etc need to be captured and generated while establishing the connection.
  • JDBC Java Database Connectivity
  • the DXL (210) After the connection with the external database (that is the oracle or external database (208) that the DXL (210) will connect to for exposing a database source code) is successfully tested and ascertained, the DXL (210) further retrieves a plurality of schemas from the oracle or external database (208) and generate the one or more PL/ SQL code objects in a procedure, package and function under the plurality of schemas. The user may then select the one or more PL/SQL code objects for performing operations like batch file processing. Based upon the one or more PL/SQL code objects selected by the user, the DXL (210) may identify, read and generate one or more object signatures and arguments.
  • the external database that is the oracle or external database (208) that the DXL (210) will connect to for exposing a database source code
  • the input output payload data structure details of the proxy RESTful web service will be based upon the one or more PL/SQL code objects signatures and will be generated by the DXL (210).
  • the DXL (210) may further perform an identification of one or more input files (the one or more input files containing data in any specific format to be transferred from the source system to the target system) to be generated along with structural details of the one or more input files.
  • the DXL (210) may, using a file adapter, configure a relevant metadata information relating to the one or more input files identified to capture in the file adapter a host of information relating to the one or more input file names, file extensions, an operating system network filer location and the internal data structure. Based on the above details captured in the file adapter, the DXL (210) may further identify the input and output payload data structures details and the one or more PL/SQL objects code of the one or more input files.
  • the DXL (210) may then perform using the data translation and transformation layer (not shown in the figure), the mapping and populating of the data (the data in any specific format which the source system will transfer to the target system) across the one or more Java Nested Object Graphs.
  • the DXL (210) may then display the mapping screen to the user comprising the one or more input and output tabbed sections further comprising of the left and the right panel, where the left panel include details on the source system payload data structure nested object graph and the right panel include details on the target system payload data structure nested object graph.
  • the user specifies the field-level mappings between the source system and the target system payload data structure nested object graphs by the one or more hardware processors (104).
  • the value translation may be the simple or the custom-logic based value translation as explained above.
  • the DXL (210) by the one or more hardware processors (104), generate code for the transformed RESTful web service into the standard Java Platform, Enterprise Edition (J2EE) complaint one or more web archive (WAR) files that are deployment ready on the application server platform.
  • J2EE Java Platform, Enterprise Edition
  • WAR web archive
  • the target application may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to the corresponding servlet container forming a part of the application server of the user's preference.
  • the DXL (210) may then communicate the information on the HTTP URL of the proxy RESTful web service and the one or more blank JSON / XML data structures of the input output payload to the proxy RESTful web service. Since the DXL (210) generates the POST format proxy execution points as transformed web services, hence for the transformation into the different RESTful web service, the HTTP URL generated above is in the POST format.
  • the proxy SOAP or RESTful web service generated by the DXL (210) is consumed by the target system that remains totally unaware of the actual SOAP web service generated initially by the source system.
  • the code generated by the DXL (210) handles one or more proxying calls from the target system and automatically calls / invokes the SOAP web service from the source system for performing the transformation of the external simple object access protocol (SOAP) web service to the different SOAP web service or a representational state transfer (RESTful) web service.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the one or more hardware processors (104) perform using the imported and extracted data from the oracle or external database (208), a transformation of one or more files (for example, the .txt, the .csv or the .xml file) of different format for creating automated interface transformation between the heterogeneous systems by identifying the one or more input file details such as name, extension, file format and file data and one or more output file details such as name, extension, file format and file data.
  • the identification of the one or more input and output file is performed to obtain a set of information (such as name, extension, file format and file data) relating a plurality files of different formats between which the file transformation is to be performed.
  • the DXL (210) may for performing the one or more input files data import further identify the structural details of the one or more input files.
  • the structural details of the one or more input files are identified by uploading metadata information the one or more input files to be imported into the DXL (210) and saving as the file adapter.
  • the DXL (210) may, using the file adapter, configure the relevant metadata information relating to the one or more input files identified to capture in the file adapter a host information relating to the one or more input file names, file extensions, an operating system network filer location and the internal data structure.
  • the DXL (210) may then for performing the data export (of the data imported from the one or more of the imported files) to the one or more output files identified (how it identifies) further identify the structural details of the one or more output files.
  • the DXL (210) may, using the file adapter, configure the relevant metadata information relating to the one or more input files identified to capture in the file adapter a host information relating to the one or more input file names, file extensions, an operating system network filer location and the internal data structure. Based on the one or more input and output files and the structural details identified, the DXL (210) may then perform using the data translation and transformation layer (not shown in the figure), the mapping and populating of the data (the data in any specific format that the source system needs to transfer to the target system) across the one or more Java Nested Object Graphs.
  • the DXL (210) may then display the mapping screen to the user comprising the one or more input and output tabbed sections further comprising of the left and a right panel, where the left panel include detail on the source system payload data structure nested object graph and the right panel include detail on the target system payload data structure nested object graph.
  • the user specifies the field-level mappings between the source system and the target system payload data structure nested object graphs by the one or more hardware processors (104).
  • the value translation may be the simple or the custom-logic based value translation as explained above.
  • the DXL (210) by the one or more hardware processors (104), generate code for the transformed RESTful web service into a standard Java Platform, Enterprise Edition (J2EE) complaint one or more web archive (WAR) files that are deployment ready on an application server platform.
  • J2EE Java Platform, Enterprise Edition
  • WAR web archive
  • the target application may further deploy, using the one or more hardware processors (104), the generated WAR deployment unit to the corresponding application servlet container, for example, the websphere, or the JBoss, forming a part of the application server of the user's preference.
  • the DXL (210) may then communicate the information on the HTTP URL of the proxy RESTful web service and the one or more blank JSON / XML data structures of the input output payload to the proxy RESTful web service. Since the DXL (210) generates a POST format proxy execution points as transformed web services, hence for transformation into the different RESTful web service, the HTTP URL generated above is in the POST format.
  • the proxy SOAP or RESTful web service generated by the DXL (210) is consumed by the target system that remains totally unaware of the actual SOAP web service generated initially by the source system.
  • the code generated by the DXL (210) handles one or more proxying calls from the target system and automatically calls / invokes the SOAP web service from the source system for performing the transformation of the external simple object access protocol (SOAP) web service to the different SOAP web service or the representational state transfer (RESTful) web service.
  • SOAP simple object access protocol
  • RESTful representational state transfer
  • the hardware device can be any kind of device which can be programmed including e.g. any kind of computer like a server or a personal computer, or the like, or any combination thereof.
  • the device may also include means which could be e.g. hardware means like e.g. an application- specific integrated circuit (ASIC), a field- programmable gate array (FPGA), or a combination of hardware and software means, e.g.
  • ASIC application- specific integrated circuit
  • FPGA field- programmable gate array
  • the means can include both hardware means and software means.
  • the method embodiments described herein could be implemented in hardware and software.
  • the device may also include software means.
  • the embodiments may be implemented on different hardware devices, e.g. using a plurality of CPUs.
  • the embodiments herein can comprise hardware and software elements.
  • the embodiments that are implemented in software include but are not limited to, firmware, resident software, microcode, etc.
  • the functions performed by various modules described herein may be implemented in other modules or combinations of other modules.
  • a computer-usable or computer readable medium can be any apparatus that can comprise, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
  • a computer-readable storage medium refers to any type of physical memory on which information or data readable by a processor may be stored.
  • a computer-readable storage medium may store instructions for execution by one or more processors, including instructions for causing the processor(s) to perform steps or stages consistent with the embodiments described herein.
  • the term "computer-readable medium” should be understood to include tangible items and exclude carrier waves and transient signals, i.e., be non-transitory. Examples include random access memory (RAM), read-only memory (ROM), volatile memory, nonvolatile memory, hard drives, CD ROMs, DVDs, BLU-RAYs, flash drives, disks, and any other known physical storage media.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

L'invention concerne des systèmes et des procédés d'intégration de systèmes hétérogènes dans un écosystème d'entreprise. Les systèmes et procédés classiques procurent des interfaces configurables réduisant les efforts de codage et les traductions de messages, mais ne se concentrent pas sur des communications et des collaborations bidirectionnelles transparentes et une plateforme intégrée prenant en charge tous les patrons d'intégration d'architecture d'entreprise (EAI). Les modes de réalisation de la présente invention permettent d'obtenir une intégration simplifiée entre un ou plusieurs systèmes et une intégration synchrone avec un ou plusieurs systèmes externes par fourniture d'une transformation basée sur une application de couche échange de données (DXL) d'un service web à protocole simple d'accès aux objets (SOAP) externe à un service web SOAP différent ou à un service web conforme au transfert d'état représentationnel (RESTful) et vice versa, importation de données d'une base de données dans la DXL pour extraire les données importées en un ou plusieurs fichiers d'entrée, et réalisation, à l'aide des données de base de données extraites, d'une transformation d'un ou de plusieurs fichiers de format différent.
PCT/IB2018/051004 2017-08-30 2018-02-19 Systèmes et procédés de création de transmission d'interface automatisée entre systèmes hétérogènes dans un écosystème d'entreprise WO2019043462A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
IN201721030715 2017-08-30
IN201721030715 2017-08-30

Publications (1)

Publication Number Publication Date
WO2019043462A1 true WO2019043462A1 (fr) 2019-03-07

Family

ID=65525043

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2018/051004 WO2019043462A1 (fr) 2017-08-30 2018-02-19 Systèmes et procédés de création de transmission d'interface automatisée entre systèmes hétérogènes dans un écosystème d'entreprise

Country Status (1)

Country Link
WO (1) WO2019043462A1 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865881A (zh) * 2019-04-30 2020-10-30 北京数聚鑫云信息技术有限公司 一种接口转换方法、装置、介质及计算机设备
CN113114757A (zh) * 2021-04-09 2021-07-13 中国工商银行股份有限公司 一种文件传输方法、装置和设备
CN115208950A (zh) * 2022-07-18 2022-10-18 广东电网有限责任公司 一种跨网络异构数据资源配置方法、装置及系统
CN116055281A (zh) * 2022-11-28 2023-05-02 中盈优创资讯科技有限公司 一种灵活封装网元平台webservice接口为标准soap接口方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040181537A1 (en) * 2003-03-14 2004-09-16 Sybase, Inc. System with Methodology for Executing Relational Operations Over Relational Data and Data Retrieved from SOAP Operations
US20070150574A1 (en) * 2005-12-06 2007-06-28 Rizwan Mallal Method for detecting, monitoring, and controlling web services
US20170093827A1 (en) * 2015-09-24 2017-03-30 Heat Software Usa Inc. Dynamic web services server

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040181537A1 (en) * 2003-03-14 2004-09-16 Sybase, Inc. System with Methodology for Executing Relational Operations Over Relational Data and Data Retrieved from SOAP Operations
US20070150574A1 (en) * 2005-12-06 2007-06-28 Rizwan Mallal Method for detecting, monitoring, and controlling web services
US20170093827A1 (en) * 2015-09-24 2017-03-30 Heat Software Usa Inc. Dynamic web services server

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111865881A (zh) * 2019-04-30 2020-10-30 北京数聚鑫云信息技术有限公司 一种接口转换方法、装置、介质及计算机设备
CN113114757A (zh) * 2021-04-09 2021-07-13 中国工商银行股份有限公司 一种文件传输方法、装置和设备
CN113114757B (zh) * 2021-04-09 2022-09-30 中国工商银行股份有限公司 一种文件传输方法、装置和设备
CN115208950A (zh) * 2022-07-18 2022-10-18 广东电网有限责任公司 一种跨网络异构数据资源配置方法、装置及系统
CN116055281A (zh) * 2022-11-28 2023-05-02 中盈优创资讯科技有限公司 一种灵活封装网元平台webservice接口为标准soap接口方法及装置

Similar Documents

Publication Publication Date Title
US10331422B1 (en) System and method for generating API devlopment code for integrating platforms
US7676786B2 (en) System and method and apparatus for using UML tools for defining web service bound component applications
US9916137B2 (en) Rest service source code generation
US20080282222A1 (en) Xml push and remote execution of a wireless applications
CN101847100B (zh) 扩展软件应用的方法和装置
WO2019043462A1 (fr) Systèmes et procédés de création de transmission d'interface automatisée entre systèmes hétérogènes dans un écosystème d'entreprise
CN108804618A (zh) 数据库配置方法、装置、计算机设备和存储介质
US20140207826A1 (en) Generating xml schema from json data
CN114981775B (zh) 用于api综合管理的基于云的api元数据管理方法及系统
CN113467972B (zh) 通信接口构造方法、装置以及计算机设备、存储介质
AU2022209333A1 (en) System and method for generating api development code for integrating platforms
US10747588B2 (en) Method for updating instance-based message maps using metadata
US8667083B2 (en) Simplifying provisioning of asynchronous interaction with enterprise suites having synchronous integration points
AU2018202837B2 (en) Server and method for making customized application using integrated application and recording medium therefor
US8972487B2 (en) Automated framework for testing enterprise services consumer technologies
CN110764769B (zh) 处理用户请求的方法和装置
EP2810179B1 (fr) Procédé et système de mise en uvre d'une interface de données commune pour des services web
US8200713B2 (en) Database exploration for building wireless component applications
US20140101280A1 (en) Generic serializer framework
CN103297479A (zh) 一种插件升级的分布式检测方法及装置
US11829732B2 (en) Simple object application protocol web service applications
CN112445850A (zh) 数据转换方法、装置、电子设备及可读介质
CN117215808A (zh) 一种业务处理方法、装置及服务端设备
KR101078227B1 (ko) 사용자별로 특화된 로직을 제공하는 방법 및 서버시스템
CN116225521A (zh) 记录交付方法、装置、设备、介质和程序产品

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 18852206

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18852206

Country of ref document: EP

Kind code of ref document: A1