Method, apparatus and machine-readable medium for transforming, converting and processing messages between multiple systems

• US 8,918,356 B2
• Filed: 11/06/2007
• Issued: 12/23/2014
• Est. Priority Date: 08/30/2001
• Status: Active Grant

• Current Assignee: Siebel Systems Inc. (Oracle Corporation)
• Original Assignee: Siebel Systems Inc. (Oracle Corporation)
• Inventors: Liou, Ming-Tao, Yeap, Hwee Har, Hsiao, Chiun-Feng
• Primary Examiner(s): Choi, Yuk Ting
• Application Number:
  US11/935,493
• Publication Number:
  US 20080077601A1
• Time in Patent Office: 2,604 Days
• Field of Search: None
• US Class Current: 707/602
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: Y10S 707/99942 Manipulating data structure, e.g. compression, compaction, compilation
• CPC Class Codes: Y10S 707/99943 Generating database or data structure, e.g. via user interface
• CPC Class Codes: Y10S 707/99952 Coherency, e.g. same view to multiple users

Abstract

A method, apparatus, and machine-readable medium are disclosed for processing change information from a first system comprising a first database at a second system comprising a second database. An embodiment of the method includes receiving a first message comprising the change information at the second system, processing the first message into a processed message, determining whether a custom script is needed in the processing, and incorporating the change information in the second database. An embodiment of the machine-readable medium includes instructions which when executed by a processor cause the processor to perform the method. An embodiment of the apparatus includes an input module configured to receive the first message comprising the change information, a processing module configured to process the first message into the processed message, and a transaction module configured to incorporate the change information in the second database.

Claims

1. A method, comprising:

receiving a first message comprising change information from a first system comprising a first database, wherein

the first message is received at a second system comprising a second database,

the change information comprises a set of transactions,

the set of transactions comprises changes made in the first database, and

the first message reflects a first data format supported by the first database;

processing the first message into a processed message, wherein

the processed message comprises a set of processed transactions,

the processed message reflects a second data format supported by the second database,

the set of processed transactions represents the change information,

the processing is performed on the second system, and

the processing comprises

identifying a command within a body portion of the first message, wherein the command relates to one of the set of transactions,

processing the one of the set of transactions to produce one of the set of processed transactions,

determining that a second body portion of the first message does not comprise another command,

passing through the second body portion of the first message into the processed message, and

packaging body portions of the first message and the one of the set of processed transactions into the second data format of the processed message;

determining whether a custom script is needed in said processing, wherein

said custom script is external to original code and configuration information of software used for said processing;

in response to a determination that a custom script is needed, employing a custom script in said processing; and

incorporating the change information in the second database, wherein the incorporating comprises

effecting the set of processed transactions in the second database.

2. The method of claim 1 wherein the processing the first message comprises:

converting the first message into a second message, wherein

the converting the first message into the second message comprises;

determining that the set of transactions comprises a first transaction,

processing the first transaction to produce a second transaction,

determining that a first data object in the first message is associated with the first transaction,

processing the first data object to produce a second data object, and

assembling the second transaction and the second data object into the second message.

3. The method of claim 2 wherein

the converting the first message into the second message further comprises:

determining that the first message comprises an envelope

attaching the second transaction and the second data object to the envelope, and

assembling the envelope into the second message.

4. The method of claim 2 wherein the processing the first message further comprises:

transforming the second message into the processed message, wherein

the transforming the second message into the processed message comprises;

identifying a body portion of the second message,

determining that the body portion comprises a command, wherein the second transaction is related to the command,

processing the second transaction to produce a third transaction, in response to the determining that the body portion comprises the command, and

packaging the third transaction and the command into the processed message, wherein the set of processed transactions comprises the third transaction.

5. The method of claim 1 wherein

the determining whether a custom script is needed comprises evaluating processing instructions included with the first message.

6. The method of claim 4 wherein

the transforming the second message into the processed message further comprises:

determining that a second body portion of the second message does not comprise another command,

passing through the second body portion of the second message into the processed message, and

packaging body portions of the second message into the second format of the processed message.

7. The method of claim 4 wherein

the effecting the set of processed transactions in the second database comprises:

processing the command of the processed message,

invoking a method based on the command of the processed message against the second database, and

packaging a return of the method in a response message for the first database.

8. The method of claim 7, wherein

the command of the processed message corresponds to the third transaction.

9. The method of claim 7 wherein

the effecting the set of processed transactions in the second database further comprises:

processing instructions of the set of processed transactions, and

assembling the set of processed transactions for transfer to the second database.

10. The method of claim 1, further comprising:

identifying non-command-containing parts of the body portion of the first message; and

wherein said packaging further comprises packaging the non-command-containing parts into the second data format.

11. The method of claim 1, wherein

the first message reflects a first internal structure supported by the first database,

the second message reflects a second internal structure supported by the second database, and

the second internal structure is different from the first internal structure.

12. The method of claim 1, wherein

the second data format comprises a proprietary data format.

13. The method of claim 4, wherein

the transforming comprises at least one of

substituting a first value of the set of first transactions with a second value supported by the second database, and

substituting a first foreign key value with a placeholder foreign key value supported by the second database.

14. The method of claim 1, wherein

said custom script is external to information or code that would normally be accessed for said processing.

15. The method of claim 1, wherein

said custom script is not embodied in a software or database configuration.

16. The method of claim 1, wherein

said employing a custom script comprises locating the custom script during processing at the time of said employing.

17. The method of claim 1 further comprising:

determining that the set of transactions comprises a first transaction; and

determining that a first data object in the first message is associated with the first transaction.

18. The method of claim 17 further comprising:

determining that a command corresponds to the first transaction.

19. The method of claim 18 further comprising:

processing the command, wherein

the processing the command comprises custom processing of the command,

the custom processing uses pre-defined rules, and

the pre-defined rules are configured to support data of user-configured fields that are not supported by normal processing.

20. The method of claim 18 further comprising:

invoking a method corresponding to the command against the second database; and

packaging a return of the method in a response message for the first database.

21. A non-transitory machine-readable medium embodying instructions, which, when executed by a processor, cause the processor to perform a method, comprising:

receiving a first message comprising change information from a first system comprising a first database, wherein

the first message is received at a second system comprising a second database,

the change information comprises a set of transactions,

the set of transactions comprises changes made in the first database, and

the first message reflects a first data format supported by the first database;

processing the first message into a processed message, wherein

the processed message comprises a set of processed transactions,

the processed message reflects a second data format supported by the second database,

the set of processed transactions represents the change information,

the processing is performed on the second system, and

the processing comprises

identifying a command within a body portion of the first message, wherein the command relates to one of the set of transactions,

processing the one of the set of transactions to produce one of the set of processed transactions,

determining that a second body portion of the first message does not comprise another command,

passing through the second body portion of the first message into the processed message, and

packaging body portions of the first message and the one of the set of processed transactions into the second data format of the processed message;

determining whether a custom script is needed in said processing, wherein

said custom script is external to original code and configuration information of software used for said processing;

in response to a determination that a custom script is needed, employing a custom script in said processing; and

incorporating the change information in the second database, wherein

the incorporating comprises

effecting the set of processed transactions in the second database.

22. The machine-readable medium of claim 21 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the processing the first message comprises converting the first message into a second message, and

the converting the first message into the second message comprises;

determining that the set of transactions comprises a first transaction,

processing the first transaction to produce a second transaction,

determining that a first data object in the first message is associated with the first transaction,

processing the first data object to produce a second data object, and

assembling the second transaction and the second data object into the second message.

23. The machine-readable medium of claim 22 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the converting the first message into the second message further comprises;

determining that the first message comprises an envelope,

attaching the second transaction and the second data object to the envelope, and

assembling the envelope into the second message.

24. The machine-readable medium of claim 21 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the determining whether a custom script is needed comprises evaluating processing instructions included with the first message.

25. The machine-readable medium of claim 22 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the processing the first message further comprises transforming the second message into the processed message, and

the transforming the second message into the processed message comprises

identifying a body portion of the second message,

determining that the body portion comprises a command, wherein the second transaction is related to the command,

processing the second transaction to produce a third transaction, in response to the determining that the body portion comprises the command, and

packaging the third transaction and the command into the processed message, wherein the set of processed transactions comprises the third transaction.

26. The machine-readable medium of claim 25 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the transforming the second message into the processed message further comprises;

determining that a second body portion of the second message does not comprise another command,

passing through the second body portion of the second message into the processed message, and

packaging body portions of the second message into the second format of the processed message, based on pre-defined rules, wherein

the pre-defined rules are configured to support data of user-configured fields that are not supported by normal processing.

27. The machine-readable medium of claim 25 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the effecting the set of processed transactions in the second database comprises;

processing the command of the processed message,

invoking a method based on the command of the processed message against the second database, and

packaging a return of the method in a response message for the first database.

28. The machine-readable medium of claim 27 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the effecting the set of processed transactions in the second database further comprises;

performing custom processing of the command of the processed message in addition to default processing of the command of the processed message.

29. The machine-readable medium of claim 27 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the command of the processed message corresponds to the third transaction.

30. The machine-readable medium of claim 27 further embodying instructions which, when executed by the processor, further cause the processor to perform the method wherein:

the effecting the set of processed transactions in the second database further comprises;

processing instructions of the set of processed transactions, and

assembling the set of processed transactions for transfer to the second database.

31. An apparatus, comprising:

an input module configured to

receive a first message comprising change information from a first system comprising a first database, wherein

the apparatus is associated with a second system comprising a second database,

the change information comprises a set of transactions,

the set of transactions comprises changes made in the first database, and

the first message reflects a first data format supported by the first database;

a processing module configured to process the first message into a processed message, wherein

the processed message comprises a set of processed transactions,

the processed message reflects a second data format supported by the second database,

the set of processed transactions represents the change information,

the processing module is further configured to determine whether a custom script is needed to process the first message,

said custom script is external to original code and configuration information of software used to process the first message,

the processing module is further configured, in response to a determination that a custom script is needed, to employ a custom script to process the first message,

the processing module is further configured to locate the custom script at the time of processing in order to employ it, and

the processing comprises

identifying a command within a body portion of the first message, wherein the command relates to one of the set of transactions,

processing the one of the set of transactions to produce one of the set of processed transactions,

determining that a second body portion of the first message does not comprise another command,

passing through the second body portion of the first message into the processed message, and

packaging body portions of the first message and the one of the set of processed transactions into the second data format of the processed message; and

a transaction module configured to incorporate the change information in the second database by being further configured to affect the set of processed transactions in the second database.

32. The apparatus of claim 31 wherein

the processing module comprises a converter module, and

the converter module is configured to

determine that the set of transactions comprises a first transaction,

process the first transaction to produce a second transaction,

determine that a first data object in the first message is associated with the first transaction,

process the first data object to produce a second data object, and

assemble the second transaction and the second data object into the second message.

33. The apparatus of claim 32 wherein

the converter module is further configured to

determine that the first message comprises an envelope,

attach the second transaction and the second data object to the envelope, and

assemble the envelope into the second message.

34. The apparatus of claim 32 wherein

the converter module is further configured to custom process transactions.

35. The apparatus of claim 32 wherein

the processing module further comprises a transformer module, and

the transformer module is configured to

identify a body portion of the second message,

determine that the body portion comprises a command, wherein the second transaction is related to the command,

process the second transaction to produce a third transaction, in response to the determination that the body portion comprises the command, and

package the third transaction and the command into the processed message, wherein the set of processed transactions comprises the third transaction.

36. The apparatus of claim 35 wherein

the transformer module is further configured to

determine that a second body portion of the second message does not comprise another command,

pass through the second body portion of the second message into the processed message, and

package body portions of the second message into the second format of the processed message, based on pre-defined rules, wherein

the pre-defined rules are configured to support data of user-configured fields that are not supported by normal processing.

37. The apparatus of claim 35 wherein

the transaction module is further configured to

process the command of the processed message,

invoke a method based on the command of the processed message against the second database, and

package a return of the method in a response message for the first database.

38. The apparatus of claim 37 wherein

the transaction module is further configured to custom process the command.

39. The apparatus of claim 37, wherein the command of the processed message corresponds to the third transaction.

40. The apparatus of claim 37 wherein

the transaction module is further configured to

process instructions of the set of processed transactions, and

assemble the set of processed transactions for transfer to the second database.

41. The apparatus of claim 31, wherein

the processing module is further configured to locate the custom script at the time of processing in order to employ it.