Home > Articles > Web Services

Interview with Grand Central CEO Craig Donato Part 1

Craig Donato, CEO of Grand Central, discusses web service networks with Alex Nghiem. Learn how Grand Central's focus on security, reliability, and transactional integrity fits into the web services mix. (Part 1 of 2)
Like this article? We recommend

Like this article? We recommend

Alex: Please explain to our readers what Grand Central does.

Craig: Grand Central is a web services network that enables business systems to reliably and securely interoperate between organizational boundaries. A good metaphor for Grand Central is the public switched telephone network (PSTN): Instead of enabling any two people to communicate, Grand Central enables any two applications to interact.

Alex: What layer of the web services model or architecture does your firm address?

Craig: A large stack of agreements needs to be in place in order to have a true B2B conversation. Web services standards really only address a small subset of these issues—the bottom part of this "B2B stack"—relating to data formats (XML) and communication protocol (SOAP). Everything beyond these standards needs to be put in place to ensure appropriate levels of security, reliability, and transactional integrity (correlation, compensation). Addressing these issues within a B2B context is especially difficult because you must coordinate a solution with your partners, who are likely to operating different B2B stacks.

There are two general ways to address this issue. The traditional B2B integration approach is to get everyone to use one stack: yours. If you use a certain schema, they have to use that same schema. If you decide to authenticate identity using VeriSign technology and a certain certificate authority, they have to use it as well.

Grand Central offers a new approach that embraces heterogeneity—allowing partners to use their own B2B stacks, with Grand Central mediating the differences between implementations. For example, you may decide to use a certificate authority to authenticate yourself, but your partners may have a different method of doing so. Rather than forcing your partners to do it your way, you just set up a business rule in Grand Central that says, "I'll accept the following methods of authentication." After Grand Central authenticates their identity, it's validated against your authentication business rule.

We also do things like protocol and data format mediation. Just because you decide to deploy web services, doesn't mean that all of your partners do so. So we enable SOAP to interact with a web site speaking HTTP, or an FTP server. We also can translate ASCII into XML and vice versa.

Alex: In a recent InfoWorld survey of 500 software managers, the respondents identified security as the biggest obstacle to web services adoption. How does your product help address that particular issue?

Craig: When we talk about security, we mean four things: encryption, authentication, access control, and firewall vulnerability. Grand Central's web services network not only provides support for each of these layers of security, but more importantly provides the mediation necessary to ensure interoperability between disparate security models.

As we discussed previously, Grand Central enables companies to establish business rules that allow partners to interact in a decentralized and heterogeneous environment. Authentication and authorization are two areas that can be deployed and managed through Grand Central. We support a variety of authentication mechanisms, including username and password as well as VeriSign certificates.

Grand Central also provides rule-based access control. This allows you to decide which users have access to a service, which version they should map to, as well as functionality for things like availability windows. We also support the flip side of authorization, which is provisioning or granting new access to a service.

There is clearly a lot of activity in this area and we're working closely with the major web services toolkits to ensure interoperability with their security models.

Alex: How are the policies actually created or managed?

Craig: Policies are created via web-based forms in Grand Central. In the long run, we also expect to integrate with tools that author and manage policies within an enterprise.

Alex: One of the classic problems of doing B2B integration is non-repudiation. How does your framework handle that particular issue?

Craig: Grand Central provides both the sender and recipient with a common tracking slip. This allows either party to have a full visibility into what's happened with the message.

Alex: So it's up to the individual partner to actually resolve the issue, but you provide the audit trail?

Craig: Exactly. We provide an independent audit trail, similar to [the FedEx audit trail], that indicates when the message was sent and when it was received. This is a significant improvement over traditional integration technologies that require participants to do a lot of manual work resolving audit logs on both sides of the transaction.

Alex: Do you see web services completely replacing EAI/B2B solutions, or will they coexist?

Craig: We don't see web services completely replacing these solutions. We actually see them providing a key role within an evolved web services architecture—that of the service broker.

Alex: How do you see companies like TIBCO and webMethods evolving? What about the roles of application servers, such as WebLogic, and also of integration servers?

Craig: To extend the phone system analogy that I used earlier, it's our belief that products like TIBCO and Vitria will act like PBXs: monitoring and managing internal service interactions, weaving them together into business processes. Just as PBXs connect into a public phone network, we believe that these platforms will plug into something like Grand Central's web services network.

In addition to being a platform for services, application servers such as WebLogic are being used as service brokers. With traditional EAI vendors and application servers both attacking the service broker segment, we see this as the biggest area of contention in the web services world.

Alex: So far, the few web services that have been implemented are typically behind a firewall. What tipping point needs to occur for web services to be adopted on a mass scale beyond a firewall?

Craig: We firmly believe that in order for web services to be adopted in mass scale beyond the firewall, you need to have two things:

  • A shared infrastructure that will support a many-to-many world. FedEx, the public switched telephone network, and VISA are all modern-day examples of shared infrastructures that enable a many-to-many collaborative world.

  • Web services standards that allow business systems to interoperate with unprecedented flexibility and affordability.

Alone, these two variables are not sufficient for most business-to-business interactions. Grand Central's web services network, which is built on top of the Internet, enables businesses to harness the power of web services with the levels of security and reliability required for enterprise-class integration.

When you implement web services between firewalls, you have a higher bar when addressing the issues around security and reliability. For example, username and password may be an acceptable internal authentication scheme, but would not be suitable outside the firewall. That said, I think you'll see a lot of B2B web service deployments in conjunction with web service networks like Grand Central that address these deployment issues.

Moreover, I think B2B integration more naturally lends itself to a standards-based approach, since it's inherently involved in deployments where you don't control what's on the other end. So you can't force your partners to always do it your way. With standards like SOAP and XML, you get around the problems with proprietary protocols and data formats. But there are still a host of other issues that require you to use a web services network like Grand Central.

Alex: Would it be fair to say that the challenges are the same, but it's easier to do a pilot behind a firewall because you can control all the various factors?

Craig: Right. And I think you'll see clients first deploy a web service internally. Once they get comfortable with the internal deployment, they can share it with selected partners. At this point, they need to deal with the issues of security, authentication, provisioning, version control, etc. And if they use Grand Central, they can easily address these issues.

Alex: Can you describe the profile of a typical or an ideal client for your firm?

Craig: A firm that wants to exchange data with their partners—whether informational content or transactional content—typically in a server-to-server fashion. For example, they want to integrate their forecasting system with their partner's inventory system, or their CRM system with their partner's purchasing system.

Alex: In a recent case study by AMR, the client saved 60% on integration costs versus traditional means. Have you noticed any similar gains or benefits using your platform and/or the web services architecture—as opposed to, say, EAI or traditional B2B?

Craig: Absolutely. When we work with customers, we are about 1/20th of the cost of a traditional software implementation.

Alex: Is cost the only factor, or is time to market also important?

Craig: In addition to being more affordable, ease of deployment and manageability are two other major advantages of using Grand Central's web services network for B2B integration. Traditionally B2B integration technologies tend to be very expensive, time-intensive, and complex to manage, so only the biggest companies typically deploy, with their top 4 or 5 partners, for a limited range of interactions. With Grand Central, you have something that can be effectively deployed by [a company of any size], with all of their partners, for a very broad range of interactions.

At the end of the day, we can demonstrate that there is no need for an organization to implement and manage its own B2B integration network. We provide higher levels of service than they would implement on their own, and because it's shared infrastructure, we can do so at a fraction of the cost.

Alex: Most of us understand the concept of writing a traditional application from the ground up. Suppose I have a software development kit (SDK) and I write an application in .NET, J2EE, or whatever. Once I have that application up and running, how do I plug it into the Grand Central network?

Craig: It's very simple and it's transparent. If your application can speak SOAP, you don't need to install any software or hardware, or even open any holes in your firewall. All you do is go to Grand Central's site and create a proxy for that service in our network. You then redirect users through that proxy. One metaphor that I use for people who are a little bit more technically minded is Akamai. If I were Yahoo!, I could have implemented my own caching network. I could have purchased software from Akamai, installed caching servers out on the Internet, and had every one of my customers download some sort of caching software into their browser. But that would have been very expensive and inefficient. Instead, sites like Yahoo! create a virtual proxy for their web site in Akamai and redirect users through it. And these users don't necessarily need to know that they're using Akamai. It just gets inserted into the conversation.

This is a very good metaphor for Grand Central. You create a virtual proxy in Grand Central and you redirect users through it. But instead of making web pages faster, we enable B2B conversations to be more secure and reliable.

Alex: How does the Grand Central proxy help clients maintain existing services and provision new ones?

Craig: Customers wrap the proxy with business rules that enable them to effectively manage that interface. For example, rules can be used to support change management. All users access one logical proxy in Grand Central. Rules within the proxy then redirect those users to the appropriate version of the web service. To upgrade a user, you simply change the user's designation in your access control list. This process also supports provisioning. When you add a new user to your access control list, that user sees a listing for that service automatically pop up in his or her Grand Central directory.

Alex: What are some of the mechanisms you use to handle that mapping? Do you implement your own proprietary access control mechanism, or do you leverage UDDI?

Craig: We built our directory to be UDDI-compliant. We've built functionality on top of it, however, to enable it to support issues surrounding access control and visibility. Most of our customers are looking to deploy web services to specific partners, not make them generally available. As such, they want more control over who can access the web service and even who can see it.

End of Part 1. Part 2 of this interview will appear at InformIT next week.

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