+

WO2004031990A1 - Procede pour integrer des donnees dans un systeme d'integration - Google Patents

Procede pour integrer des donnees dans un systeme d'integration Download PDF

Info

Publication number
WO2004031990A1
WO2004031990A1 PCT/SE2003/001524 SE0301524W WO2004031990A1 WO 2004031990 A1 WO2004031990 A1 WO 2004031990A1 SE 0301524 W SE0301524 W SE 0301524W WO 2004031990 A1 WO2004031990 A1 WO 2004031990A1
Authority
WO
WIPO (PCT)
Prior art keywords
module
data
data source
server unit
business object
Prior art date
Application number
PCT/SE2003/001524
Other languages
English (en)
Inventor
Johan Palmaer
Original Assignee
Johan Palmaer
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 Johan Palmaer filed Critical Johan Palmaer
Priority to AU2003267897A priority Critical patent/AU2003267897A1/en
Publication of WO2004031990A1 publication Critical patent/WO2004031990A1/fr

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/25—Integrating or interfacing systems involving database management systems

Definitions

  • the method is for integrating data in an integration system.
  • the method comprises providing an integration server unit and an external data source that has an external business object.
  • a repository module with a business object of the integration server is created.
  • the connection module is connected to the external data source.
  • a table of the external data source is mapped with the business object.
  • a flow direction of data information between the data source and the server unit is determined by an action module.
  • the data information is then transferred between the data source and the server unit activated and managed by a transaction module.
  • Fig. 1 is a schematic overview of the integration system of the present invention
  • Fig. 2 is a schematic view of external sources in communication with the integration server of the present invention.
  • Fig. 3 is a detailed schematic view of the integration server of the present invention.
  • the integration system 10 of the present invention has an integration server unit 12 in communication with an external data source 14 and/or an external data source 16.
  • the data source 14 may have a business object 15.
  • One purpose of the system 10 is to serve as a middleware and to integrate data received from one source 14 and to be able to send information in a converted form to the other external source 16.
  • the unit 12 may both receive and send information.
  • the server unit 12 has an adapter module 18, a transaction module 20, an action module 22, a linked data source module 24, a connection module 26, a repository module
  • the adapter module 18 may include an adapter or an adapter package with many adapters.
  • the module 18 may be used between the data source 14 and the server unit 12 and the module 18 has preprogrammed configurations between the modules so that the integration can be done smoothly between the source 14 and the unit 12. In this way, no configuration may be necessary between the various modules by the administrator 32.
  • the integration may be done with or without the adapter module 18.
  • the module 18 may have an application program interface.
  • the transaction module 20 is used to actually transfer data information from one source to another.
  • the action module 22 is a module that may determine the direction of the information flow.
  • the link table module 24 is used to map tables from the business object 15 of the data source 14 to the business object module 30 of the repository module 28. It is possible to select which business object from the source 14 and which business object of the repository that should be activated.
  • the connection module 26 is to be used to connect the server unit 12 to the data source 14 so that the unit 12 may access the data of the data source 14. All data may be stored in the repository module 28.
  • Fig. 2 shows an administrator interface 32 that handles the set up of the integration between the data sources 4 and the server unit 12.
  • the interface 32 has many displays so that the user can set up the integration and management 34 of all the projects 36.
  • the integration may involve integrating different systems such as a customer relation management system with an accounting system.
  • the data of the projects 36 are usually separated into definitions 38 that are stored in module databases 40 and external data 14 stored in repository databases 44.
  • the definitions 38 may include the items to be included in the modules such as the repository module and the business object module etc.
  • the administrator 32 often configures the definitions 38.
  • the definitions could include, for example, a repository database.
  • the repository database could be an existing database or a new database.
  • the definitions of a business object could be the name of a client, address, identification number etc.
  • connection module 26 linked tables module 24, actions module 22 and transactions module 20
  • connection module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24, actions module 22 and transactions module 20
  • connections module 26 linked tables module 24
  • actions module 22 and transactions module 20 between the module database 40 and the external data source 14
  • data may be physically transferred from the data source 14 to the repository database 44 or from the database 44 to the data source 14, as indicated by the transportation arrow 46.
  • Fig. 3 outlines some of the steps of the using the system 10 of the present invention for a project 50.
  • the repository module 28, that may include the business object 30, is created and set up.
  • tne connection module 26 is set up to connect to the external data source 14 as shown by an arrow 58.
  • the linked data source module 24 but the module 24 requires that the module 26 is properly set up and that the business object 30 exists so that the external business object
  • the linked data source module 24 may be used to select the definitions from the business object 30 that are to be transferred.
  • the arrow 60 shows communication between the linked data sources 24 and the business object in the repository 30 and the business object in the external data source 15.
  • the action module 22 may be used to determine or select which type of data information is to be selected by using defined linked data sources 24. For example, only customers from a particular region may be selected.
  • the action module 22 also determines the direction of the data flow since the mapping itself does not indicate the direction so that it is clear whether the data is to be imported from or exported to the external data source 14, as indicated by the arrow 62.
  • the transaction module 20 is used to actually transact the integration between the server unit 12 and the external data source 14, as indicated by the arrow 64.
  • the transaction may include one or more actions so that no transaction can be carried out without first configuring one or many actions.
  • the order in which the information is transferred is often important. It is also important when and under which conditions the transaction is to be carried out .
  • the data information flow in the arrow 64 is equivalent to the arrow 46 of Fig. 2.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

La présente invention concerne un procédé pour intégrer des données de traitement au moyen d'un système d'intégration. Ce procédé consiste à disposer d'une unité de serveur d'intégration (12) et d'une source de données externe (14) qui présente un ou plusieurs objets commerciaux (15). Un module d'archivage (28) avec un objet commercial (30) est créé dans le serveur d'intégration. Le module de connexion (26) est connecté à la source de données (14). La source de données externe (14) est mise en correspondance avec l'objet commercial défini (30). Un module d'action (22) calcule une direction de flux d'informations de données entre la source de données (14) et l'unité de serveur (12). Ces informations de données sont ensuite transférées entre la source de données (14) et l'unité de serveur (12) par activation d'un module de transaction (20).
PCT/SE2003/001524 2002-10-01 2003-09-30 Procede pour integrer des donnees dans un systeme d'integration WO2004031990A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
AU2003267897A AU2003267897A1 (en) 2002-10-01 2003-09-30 Method for integrating data in an integration system

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US31958802P 2002-10-01 2002-10-01
US60/319,588 2002-10-01

Publications (1)

Publication Number Publication Date
WO2004031990A1 true WO2004031990A1 (fr) 2004-04-15

Family

ID=32069487

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/SE2003/001524 WO2004031990A1 (fr) 2002-10-01 2003-09-30 Procede pour integrer des donnees dans un systeme d'integration

Country Status (2)

Country Link
AU (1) AU2003267897A1 (fr)
WO (1) WO2004031990A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
US6032147A (en) * 1996-04-24 2000-02-29 Linguateq, Inc. Method and apparatus for rationalizing different data formats in a data management system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5708828A (en) * 1995-05-25 1998-01-13 Reliant Data Systems System for converting data from input data environment using first format to output data environment using second format by executing the associations between their fields
US6032147A (en) * 1996-04-24 2000-02-29 Linguateq, Inc. Method and apparatus for rationalizing different data formats in a data management system

Also Published As

Publication number Publication date
AU2003267897A1 (en) 2004-04-23

Similar Documents

Publication Publication Date Title
US5485369A (en) Logistics system for automating tansportation of goods
US9349122B2 (en) System and method for programming point of sale devices
US8126919B2 (en) Update manager for database system
US7908398B2 (en) Software, method and system for data connectivity and integration having transformation and exchange infrastructure
US5694546A (en) System for automatic unattended electronic information transport between a server and a client by a vendor provided transport software with a manifest list
US7751417B2 (en) Accelerated system and methods for synchronizing, managing and publishing business information
US7848970B2 (en) System and method for synchronizing ledger accounts by company group
US20030097364A1 (en) System and method for data source flattening
US7966207B2 (en) Method, system and program product for managing fulfillment of orders
US20030050936A1 (en) Three-layer architecture for retail and warehouse stock audit system and method
JP2002541545A (ja) ロールを含む拡張されたオブジェクトモデル
EP3764309B1 (fr) Système et procédé de génération d'expression régulière pour améliorer le transfert de données
US20030177279A1 (en) Creation of middleware adapters from paradigms
US20070168975A1 (en) Debugger and test tool
WO2004031990A1 (fr) Procede pour integrer des donnees dans un systeme d'integration
US20120323922A1 (en) Data element categorization in a service-oriented architecture
US20010016848A1 (en) Information management system for manufacturing machines
US20050203756A1 (en) Computer network and method for manufacturing a computer network
US20020055963A1 (en) Data interchange system, data interchange instrument and method thereof
US7797149B2 (en) Integrating related data from incompatible systems for enhanced business functionality
US20090171809A1 (en) Efficient purchase order creation
US20080033590A1 (en) Method and system for managing lot transactions
JP5059002B2 (ja) コンピュータベースのブランチシステムを動作する方法及び装置システム
CN114819855A (zh) 配送任务处理方法、装置、电子设备及存储介质
CN113642853A (zh) 订单管理方法、装置、设备和存储介质

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NO NZ OM PH PL PT RO RU SC SD SE SG SK SL TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A1

Designated state(s): GH GM KE LS MW MZ SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase
NENP Non-entry into the national phase

Ref country code: JP

WWW Wipo information: withdrawn in national office

Country of ref document: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载