With automated servers based on XML comes the next big network infrastructure leap--a transition that stands to define who will succeed in business-to-business commerce models. Over the next six to 12 months, a new breed of automated directory-based XML (AX) servers will emerge. What makes AX servers critical, next-generation infrastructure? And isn't XML just a fancy extensible HTML that uses tags to indicate that a chunk of data might be a price, an application or a service?
Most first-generation XML "servers" are all about translating data or services into XML. But the real potential lies in taking services and mixing and matching them across B2B networks. It's the "automated XML" server and related application that recognizes a given XML pricing/inventory request, calls for specific database lookups, sets the process in motion, and routes a customized and custom-formatted response.
Initially, products such as Microsoft's BizTalk Server or those from new channel software provider Comergent will tap specific XML schema sets in combination with standards-based hard-coded routing technology, known as PIPs, to accomplish this task. Ultimately, the best B2B architectures will be based on the tight integration of AX servers with directory services--making it possible to modify business applications in a single location and govern authentication and corporate data rights.
While LDAP directories seem logical for this task, only the LDAP network protocol is truly established. Key vendor strategists are now examining whether LDAP as an API will disappear in favor of XML. It's possible the rich self-describing schema sets of XML will be used to create generic and vertical market APIs for business partners--and it wouldn't be odd to see Microsoft protect its own API set by optimizing XML API sets for Windows.
As an important aside, XML's self-describing nature (coupled with industry alignment behind XML for directories) might prove useful in bridging the LDAP standards divide--where Microsoft has opposed the majority call for directory-to-directory replication in favor of a scaled-back synchronization strategy. Microsoft is wary of security compromises given that security varies so much from directory to directory.
What does all this mean for businesses implementing AX servers? And since we're talking standards, doesn't that mean there's time to breathe? Not exactly.
Directory-based AX servers are emerging now. At least one Bowstreet customer is moving into production for the mass customization supply-chain server it expects to ship by year's end. Bowstreet reuses B2B application processes within metadata templates to which user profile information (to be stored in a wide variety of directories) is applied. At run-time an app is created that is customized to each business partner.
It wouldn't be a surprise to see Novell license Bowstreet to let users modify directory information and have it replicated in XML or native format to multiple applications/directories to maintain address lists across supply-chain directories. Novell has already hinted at supply-chain aspirations.
AX server approaches will vary: Microsoft initially is emphasizing XML routing; webMethods, Haht Software and ObjectDesign take a middleware perspective; and Commerce One is pushing the reusable components in its Common Business Library. Expect to see at least half a dozen shipping AX server products by mid-2000.
The most competitive businesses will be those exploring how to meld applications and directories with XML. They'll push W3C to adopt a standard query format for XML. It's an imperative for manufacturers because, as Forrester Research reports, most of today's supply-chain software is slated for replacement by 2001.
Send your comments on this column to Christy Hudgins-Bonafield at cbonafield@nwc.com.
Network communication, like human interaction, moves in a progression from the physical to localized tribal dialects (the LAN) to a limited Esperanto (HTML).
REPORTS
ANALYTICS
Follow 
