This process can be defined within the rules-processing layer of the integration server by creating a rule to dynamically translate data, depending on its content and schema. Moving information from one system to another demands that the schema/format of the message be altered as the information is transferred from one system to the next.

Although most integration servers can map any schema to any other schema, it is prudent to try to anticipate extraordinary circumstances. For example, when converting information extracted from an object-oriented database and placing it in a relational database, the integration server must convert the object schema into a relational representation before it can convert the data within the message. The same holds true when moving information from a relational database to an object-oriented database. Most integration servers break the message moving into their environment into a common format and then translate it into the appropriate message format for the target system.

Related to the concept of accounting for the differences in application semantics, accounting for content changes is another important aspect of transformation. In short, it’s the reformatting of information so that it appears native when sent to a target system. The information needs to appear native, requiring that changes be made to source or target systems. More later...