Home > Articles > Networking

Like this article? We recommend

Case Study

When used properly in an enterprise network environment, SOAP can provide a dramatic increase in application robustness and overall response time. A telecom company foresaw a dramatic annual increase in the number of high speed Internet access orders it would receive on its customer Web site. The daily estimated increase could be in the neighborhood of 10-fold by year's end.

Given the size increase in expected orders and some issues with the existing architecture, a better solution was required. This solution needed to provide an exponential increase in response time, the ability to be distributed across multiple tiers in order to share memory and network resources, and the capability of sharing resources across two firewall boundaries. In addition, the public Web site was deployed using Java servlet and JSP technology, whereas the DMZ and private network were deployed using Windows 2000, NT, and SQL Server. Obviously, platform interoperability creates another problem for any system architect; for the purposes of this project, it would become vital. SOAP was chosen for server-to-server communication by implementing standards that are consistent across all platforms.

In order to understand the need for redesign, it's important to understand the system that would be replaced. The previous system, as depicted in the following figure, relied on the use of RPC calls via SQL Server stored procedures on a staging server. Each order that was taken by the JSP-based Web site would submit an order record (or rather, a host of them) into a SQL Server that was located in a DMZ. The domain SQL Server, which initiated cross-firewall remote procedure calls to the staging server, executed a nightly process. Multiple stored procedures, on both the domain and DMZ staging server, were required for all data validation to occur and for the flow to happen. Next, the domain server ran a host of local stored procedures, which made RPC calls across the firewall to the staging server, which also made hosts of other stored procedure calls, eventually sending the resulting records back across the firewall to the domain server. Each individual order required about 25 cross-firewall requests, and 15-20 stored procedure calls distributed across each server. At the beginning of the redevelopment process, it was taking about 10-20 seconds per order.

Figure 4 SQL Server-initiated RPC Communication

Think of the impact of growth—if the company maintained the previous architecture and order volume increased exponentially, each "nightly" run could turn into an 80-hour (give or take a few) process. In this case, an order submitted via the Web site may not show up in the domain database for several days. If the order had not yet been picked up by the domain server, the next day it could delay order processing. Not only is speed an issue, but data integrity and customer information persistence are obviously important components to consider. Obviously, a new architecture was needed to accommodate the company's growth.

The new architecture needed to submit orders as they came from the Web site, automatically, all the way through the DMZ and into the domain database server. It would enable a semi-real-time order flow and eliminate the need for a nightly batch import process.

Initially, the Apache-SOAP implementation was deployed onto the Java Web server. The Java servlets that consume the order data and transfer it to the staging server were augmented with the Apache-SOAP packages. The servlets were redesigned to build an XML document via the XML DOM approach. This XML string is then transmitted via a SOAP call to the firewall that separated the Web site from the DMZ, where a COM+ listener accepts the XML input, creates the order, and returns a response containing various bits of information. From this point forward, the user is disconnected from the process, though they have received all pertinent information required if they need to make changes to the order via a call center.

Further analysis revealed that queuing technology was needed to enable an asynchronous messaging methodology. The COM+ component stored the XML data onto a queue using MSMQ. A separate process then picks up the messages as they come into the system for further conversion, as required by the domain database. This converted XML is once again transmitted from the DMZ area to the domain through the DMZ/Domain firewall, where it is once again queued. A queue was used in this location to protect the database component architecture from becoming overloaded. This satisfied a management requirement that Web order processing should not impact the day-to-day business.

To provide the database with a steady order flow, the messages are queued inside the domain, in their final format, where they await component pickup. An MSMQ trigger then fires multiple instances of a COM+ component, which distributes each individual section of the XML request to its destination table by way of multiple stored procedures. For instance, the Customer portion of the XML document would be handled by a Customer component, which would send it into the database by way of a stored procedure, the Order section by a separate Orders component, and so on.

Figure 5 SOAP-based Solution

The final outcome yielded a significant increase in performance and more real-time access to the data, despite the complexity of the system. By using SOAP, cross-platform and –firewall communication was made possible without the use of stored-procedure-based RPC. This fact alone frees up much of the server resources so that the database can concentrate on it's main purpose – data storage and retrieval. Additionally, given the fact that the business logic is pulled out of the database and placed into COM+ distributed components, enables greater resource sharing and distribution across multiple servers. The current architecture is distributed across six machines – two machines are utilized as queue servers, two for application logic, and two final machines that distributed the database storage.

At press time, testing had indicated that, for complete order submission and storage, a total of 1-2 seconds could be achieved, with little impact on existing systems that utilized the same network and database resources. The 3000% increase over previous daily orders had become a plausible reality, and the existing systems were minimally if at all impacted by the change. By using SOAP as a more modern method of RPC and order delivery, the client had achieved their goals and realized a more strategic position in the already competitive Internet telecommunications market.

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