Home > Articles > Software Development & Management

  • Print
  • + Share This

Data-Level B2B Application Integration by Example

Just as a picture is worth a thousand words, understanding data-oriented B2B application integration is sometimes made easier by "painting a picture"—that is, examining a particular B2B application integration problem. For example, let us say that a copper wiring manufacturing company would like to hook up to the inventory control system that exists at its raw material goods producer, a client/server system using PowerBuilder and Oracle, and the Enterprise Resource Planning (ERP) system (using an Informix relational database). Because the data movement requirements are light to moderate, and because changing the proprietary ERP application to bind its logic with the inventory control system is not an option (the supplier won't allow it), the company would like to solve this B2B application integration problem using data-oriented B2B application integration and the Internet.

First, to move data from the Oracle database to Informix, the B2B application integration architect and developer need to understand the metadata for each database so that they can select the data that will move from one database to the next. In our example, let us assume that only sales data must move from one database to the other. So, when a sale is recorded in the inventory system, creating an event, the new information is copied over to the supplier's ERP system to ensure that the correct amount of raw materials will be available to create the sold copper wire.

Second, the architect and developer must determine the frequency of the data movement. In our example, let us determine that real time is a requirement for this problem domain. The event to be captured must also be defined to signal when the data needs to be copied, such as a specific increment of time (every 5 seconds) or when a state changes (an update to a table occurs).

After these two determinations are made, the architect and the developer must choose the method for moving the data. As we have come to understand, there are many technologies and techniques for moving the data from one database to the next, including database replication software, message brokers, and custom-built utilities. There are advantages and disadvantages to each. In our example, we'll choose to go with a database replication and integration solution—a piece of software that runs between the databases that can extract information from one database (say, the Informix database), reformat it (changing content and schema), if needed, and update the Oracle database.

Although ours is a one-to-one scenario, one-to-many works in the same way, as does many-to-many, albeit with more splitting, combining, and reformatting.

With the middle-tier database replication software in place, the information is extracted, reformatted, and updated from the Oracle database to the Informix database, and then back again. The information is replicated between the two databases when an update occurs at either end of the corresponding sales table.

Using this simple approach, the data moves between the databases at the data level. The application logic is completely bypassed. There are no changes to the application logic at the source or, as in this case, the target systems. Clearly, this approach provides an effective B2B application integration solution whenever an application cannot be changed, which, as we've noted many times, is generally the case with B2B application integration problem domains.

Data-oriented B2B application integration makes sense for more complex problem domains as well: domains such as moving data between traditional mainframe, file-oriented databases and more modern, relational databases, relational databases to object databases, multidimensional databases to mainframe databases, or any combination of these. As in other domains, database replication and translation software and message brokers provide the best solutions. They can tie all source and target databases together cohesively, without requiring changes to the connected databases or application logic.

There are two basic approaches to data-oriented B2B application integration and its accompanying enabling technology: database-to-database B2B application integration and federated database B2B application integration.

Database-to-Database B2B Application Integration

Just as with the point-to-point approach, we've been doing database-to-database B2B application integration well for years. Database-to-database B2B application integration allows us to share information at the database level and, by doing so, to integrate applications. Database-to-database B2B application integration can exist in a number of configurations—one-to-one, one-to-many, or many-to-many. Regardless of the configuration, our approach to database-to-database B2B application integration is essentially the same: utilizing traditional database middleware and database replication software (replication features are built into many databases, such as Sybase), or through database-integration software. Message brokers also work with database-to-database B2B application integration.

Database-to-database B2B application integration problem domains can be addressed with two types of solutions: the basic replication solution, which moves information between databases that maintain the same basic schema information on all source and target databases, and the replication and transformation solution. Either of these solutions makes it possible to move information among many different types of databases, including various brands (such as Sybase, Oracle, and Informix) and models (relational, object-oriented, and multidimensional), by transforming the data on the fly so that it is represented correctly to the target database or databases receiving the data. This is exactly what happened in our previous inventory control system example.

The advantage of this B2B application integration approach is its simplicity. Generally, when dealing with application information at the data level, there is no need to change the source or target applications. By not changing the source or target applications, we reduce the risk and cost of implementing B2B application integration. The downside to this approach, where it exists, is that there are still too many applications that bind the application logic to the data. These applications make it difficult to manipulate the database without going through the application, or at least the application interface. This is the case with SAP R/3. To avoid integrity problems, updating the database generally demands using the SAP R/3 interface.

Federated Database B2B Application Integration

Like database-to-database B2B application integration, federated database B2B application integration works at the database level. However, rather than simply replicate data across various databases, federated database software creates a single "virtual" database model that allows developers to use various brands, models, and schemas to access any number of databases. This virtual database model exists only in the software and is mapped to any number of connected, physical databases. This virtual database functions as a single point of application integration, accessing data from any number of systems through the same single database interface.

The advantage of the federated database approach is its reliance on middleware to share information between applications rather than a custom solution. An additional benefit is that the middleware hides the differences in the integrated databases from the other applications that are using the integrated view of the databases. The downside is that this approach is not a true integration approach. Although it provides a common view of many databases—a "unified model"—there is still the need to create the logic for integrating the applications with the databases. In addition, this approach does not work well for B2B problem domains because it is difficult to create a common schema among systems that are not under central control.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020