DBMS

Internet-DBMS Strategies

By Stewart McKie
DBMS, October 1996

From Web enabling to CyberApp: The impact of the Internet on business applications.


The Internet is in a state of transition. As businesses around the world see the potential for riding an essentially toll-free and platform-independent information highway, we are seeing a rapid change in the users and uses of the Internet.

Early corporate uses of the Internet were largely document- or message-centric. These uses included: posting home pages as online corporate advertisements, riding on the Internet backbone for managing inter-location messages or file transfers, and placing corporate information or policies and procedures as HTML pages on Web servers for access by internal and external information consumers. Basically, these uses were an extension of what the original non-business consumers and academic users of the Internet were doing.

However, businesses and software vendors soon realized that the Internet represents the ultimate client/server network. Now business is redefining the real value of the Internet as the connection between platform-independent desktop browser software andWeb-enabled applications that front end database servers. The Internet is also proving to be an ideal environment for exploiting the synergies among a whole gamut of maturing technologies such as workflow, document management, software agents, database replication, and application business objects.

If the client/server business application vendors have their way, and notwithstanding well-documented security and bandwidth concerns, the Internet is set to become the world's biggest transaction-processing system. (For more information, see Brian Black's article "OLTP on the Web" in the October Internet Systems supplement) Transactions are the lifeblood of business - whether they perform orders, payments, or information-retrieval queries. The Internet and its progeny, the firewall-protected corporate Intranet, hold great potential for adding value to and extending the reach of transaction-oriented business applications. For this reason, there is a frenzy of activity among software vendors to Web-enable their applications, whether those applications are oriented to accounting, supply chain, manufacturing, sales automation, or OLAP.

Web-Enabling Business Applications

In general, the "Web-enabling" necessary to let a business application manage transactions across the Internet takes three forms:
  1. Enabling the application functionality to be deployed in a more granular form as individual Internet-compatible applets or as forms within HTML pages.
  2. Enabling the application to publish information in HTML formats and distribute it to Web servers for access from desktop browsers.
  3. Enabling the application to interact with Internet email and file transfer protocols for transporting data files and messages.
The investment made - to deliver three-tier or n-tier client/server applications - by forward-looking application vendors in granular application design will pay off big-time on the Internet. As a result, previously monolithic applications (such as a financials suite) can be splintered into dozens of functional granules and then dynamically deployed either as standard client software on desktop workstations or as SunSoft Java or Microsoft ActiveX applets across the Internet. Table 1 lists examples of some Web-enabled business applications.

Client/server applications that make use of middle-tier application servers, such as CODA Inc.'s CODA Financials, or workflow-architected functional architectures, such as Dun & Bradstreet Software's (soon to be acquired by Bain Capital) SmartStream, have an advantage. The application server can be easily extended to act as the client application delivery arbiter, delivering applets or HTML pages to connected Internet servers when requests originate from the Internet rather than from standard desktop clients. Applications designed around the concept of individual workflow activities instead of functional modules already have a basic functional granularity that can be leveraged for deployment in mixed Internet and non-Internet client environments.

Publishing report and query data in HTML formats or sending them as Internet email attachments is all very well and good, but applications that make use of the Internet should also offer built-in data compression and encryption capabilities for faster and more secure transfer of data. Sending the month-end financial reporting pack for a multi-entity enterprise across the Internet could be a slow, nail-biting task if compression and encryption of the report data are not performed by the sending application. Internet email output for reports or posting of reports as files to FTP Web servers can be used as the basis for new electronic report workflows, business alert and notification systems, or centralized report repositories for information disseminated and accessible enterprisewide and worldwide. When Web-enabled in these ways, business applications can use the Internet for a variety of tasks, some of which are listed in Table 2.

One effect of this Web-enabling is that more casual users can use an application that previously might have been excluded from a particular transaction workflow. For two reasons, the Internet can help extend the reach of business applications in this way. First, Internet browser software is easy to use and runs on a variety of client platforms. Second, this new Internet functionality can be deployed cheaply, without the need for a full application client license, and it can deliver a small, focused piece of functionality that is easy for the casual user to understand and use. Consequently, another effect of Web-enabling is that the pricing and licensing of business applications will have to change to reflect the functional splintering of applications and their availability to a wider range of casual users.

Extended Enterprise Intranets

Much of the early growth in business use of the Internet and of Web-enabled business applications is coming from corporate Intranets. The Intranet is an ideal infrastructure for realizing the concept of the extended enterprise. An extended enterprise consists of "stakeholders" comprising combinations of employees, customers, suppliers, shareholders, analysts, outsourcing, and other external partners. Web-enabled business applications act as a catalyst for opening up enterprise information systems and extending their reach to the people who can make best use of the information. For example: Although some corporations remain skeptical about opening up their business systems with an extended enterprise Intranet, others have embraced the concept as a competitive advantage.

Web-Enabled Accounting

Over a dozen client/server accounting vendors have articulated their Web strategy; some have even delivered real products. Some favored approaches for Web-enabling applications include generating reports as FTP files or HTML hyperlinked documents and generating functional applets for downloading to Internet clients using SunSoft's Java, Microsoft's ActiveX and FrontPage technology, or OneWave's (formerly Business@Web) OpenScape technology. Some software companies' recent announcements of Web strategies include:

SBT Corp. shipped and implemented two Web-enabled business applications that link to its Pro Series accounting software. Web Trader captures orders from a Web-based storefront and transmits them as email to the merchant's Internet email address. Polling software recognizes receipt of the email order, parses the message, and automatically generates an unapproved order in the Pro Series Sales Order module. Once the order is approved, an acknowledgment can be automatically emailed to the customer's Internet address, and other order status messages can also be generated and mailed if required. This approach reengineers a traditional paper-driven process by enabling order life cycles to be managed almost completely electronically without the need for clerical input. SBT's Web Alert is a database notification system that can generate Internet email alerts from user-defined exception triggers applied against the Pro Series accounting database tables. Both applications are shipping, and WebTrader is already being used by a new generation of Internet merchants, including New York Smoked Fish (http://www.business1.com/nysf/) and Woodmere Cameras (http://www. woodcam.com/).

Web-Enabled Document Management and OLAP

Document management vendors such as Viewstar and Saros are opening up their document library servers to access across the Internet. Saros announced @Mezzanine, which provides access to its document server for searching and retrieving documents from Internet browser software. Viewstar announced a similar product called InfoServer@Work for accessing Viewstar document and image servers.

Almost all of the significant OLAP vendors on the market have announced or released Web-enabled versions of their OLAP query and reporting tools. Essentially, Web-enabled OLAP lets multidimensional databases, such as Arbor Software's Essbase, be queried from forms embedded in HTML format pages; the results of queries are then displayed as linked HTML pages. Alternatively, reports can be generated by other OLAP application users and output in HTML format to Web server report repositories for access by Internet users through standard browser software.

Both of these directions are further examples of the opening up of business systems by permitting document retrieval and decision support to take place anytime, anywhere. This is a critical next step in the maturity of business applications and an essential prerequisite for managing today's global, mobile enterprise. It's remarkable to think that, in less than a decade, we have moved from largely closed, mainframe-based business applications to anytime, anywhere business management based on the Internet.

Internet Electronic Data Interchange (EDI)

In the past, business-to-business electronic commerce was EDI. Now it seems likely that once the privacy and security concerns surrounding the Internet have been addressed, EDI will be almost entirely transferred from its current plethora of private, value-added networks (VANs) onto the Internet. (See Peter Benson's article "EDI and the Internet," Internet Systems, May 1996) The benefits include reduced transaction costs: VANs are a comparatively expensive, proprietary infrastructure that may require transactions to be passed from VAN to VAN to complete their life cycle. Meanwhile, the Internet provides a free communications backbone and is fully homogeneous in that it requires all EDI participants to use only one network (namely the Internet).

Significant EDI users such as General Electric have already begun the transition from private VANs, such as GE's own GEISNET, to new Web-based electronic commerce systems, such as the GE Trading Process Network. General Electric Information Systems has also partnered with Netscape Corp. to create a joint venture company called Actra Business Systems for building turnkey electronic commerce and EDI-related systems.

As the practice of extended enterprise Intranets matures, I wonder how long EDI in its traditional form will even remain relevant as a concept. After all, why generate purchase-order documents for transfer between EDI partners when an electronic inventory alert can manage the whole process automatically across the Internet? Although consumer-to-business electronic commerce is all the rage right now, it seems to me that direct business system-to-business system communication via the Internet will have a much more significant long-term impact on how business in conducted.

The CyberApp

At this point in time, business application vendors are just getting their feet wet with Web-enabling their existing application designs. But just as client/server forced a rewrite of monolithic, mainframe applications, so will the Internet act as a catalyst for the design of a new generation of business applications that one might call CyberApps. These CyberApps will require a redesign of both the client and server components of an application, recognizing these six business rules:
  1. Business users only "touch" applications in specific places, and few users make use of all the functionality in an application, so functionality must be deliverable in granules.
  2. Business users are mobile and may be accessing applications from different environments such as desktop clients or Internet browsers, so application delivery (such as screens and logic) must be varied to suit the connecting user.
  3. Business processes may include participants outside the corporation, so data security must be highly granular and much more sophisticated.
  4. Business processes can be complex, extended, and involve a wide range of human and system participants, so sophisticated workflow management is required.
  5. Business data must be delivered automatically, rapidly, and securely without users having to consider any of these aspects of the data delivery.
  6. Business interfaces should reflect the fact that business is task-driven, message-oriented, and not at all concerned with programs or files.
Rules 1 and 2 are driving the move toward delivering applications as collections of self-contained, interoperable business objects. These business objects are in turn managed by object brokers -middleware that can perform the arbitration role to determine how the business object is instantiated to the user (as a Microsoft Windows 95 data-entry form or an HTML page, for example).

Rule 3 demands far more than the typical table-based read/write security levels offered by most applications. Instead, security must govern how users interact with business objects at the method level or how applications interact with database tables at the column and column content level. This requires security management far deeper and broader in scope than is currently available.

Rule 4 demands that every application (or individual business object) contains a workflow management engine for managing and monitoring business process workflows within and across applications. Workflow and transaction monitors will essentially merge into one engine responsible for handing off and receiving workflow transactions while managing and auditing the state of those transactions. Workflow managers should also be replication-aware to provide essential store-and-forward message and data capabilities for moving data between systems or for handling irregular, remote logins from mobile users.

Rule 5 demands that business objects be capable of delivering data in a "raw" state or in a compressed and encrypted format - depending on where the request for the data originates. This decision should be made by the system and should not require user intervention. Commercially accepted business standards in both of these areas are necessary to make this happen.

Rule 6 demands a business interface to applications that is more like an inbox on steroids than the current menu- or icon-driven interfaces common to all applications. This inbox functions like the mythical dual-headed "push me/pull you" animal in the Dr. Doolittle stories. On the one hand, it acts as a launcher for managing business tasks that are "pushed down" to the user by workflow engines; it also acts as a launcher for "pulling up" business objects that the user may access. Of course, the inbox can also manage other informational, alert, and attachment messages sent as standard email. The key point is that one inbox acts as a conduit for all business object launching and message traffic across applications to provide a single business-operating console. When you look at the current leading desktop GUIs from this perspective, you realize just how far away we are from a true business operating system.

We haven't reached the CyberApp yet. But as Web-enabling business applications accelerates, it won't be long before some of today's client/server applications undergo the transformation and the first fledgling CyberApps hit the market.


Stewart McKie is principal of PinPoint Inc., a financial software consulting firm based in Redmond, Washington. He also edits the CFO/Info newsletter. You can email Stewart at 74660.3123@compuserve.com.


TABLE 1

Major Web-Enabled Business Applications

Category Company Product URL (http://www.)
Accounting Deltek Systems Inc. Costpoint deltek.com

Dun & Bradstreet Software Services Inc. SmartStream dbsoftware.com

Great Plains Software Inc. Dynamics C/S+ gps.com

Hyperion Software Corp. Hyperion Solution hysoft.com

Lawson Software Insight lawson.com

Oracle Corp. Oracle Application oracle.com

SAP America Inc. R/3 sap.com

SBT Systems Accounting Inc. ProSeries sbt.com

Software 2000 Inc. Infinium s2k.com
Documents Saros Corp. Mezzanine saros.com

ViewStar Corp. Viewstar viewstar.com
OLAP Arbor Software Corp. Essbase arborsoft.com

BusinessObjects Inc. BusinessObjects businessobjects.com

Comshare Inc Commander Decision comshare.com

Information Advantage Inc. DecisionSuite infoadvan.com
Reporting Crystal Services Inc. Crystal Reports seagatesoftware.com

FRx Software FRx Enterprise frxsoft.com

TABLE 2

Tasks for which Business Applications Can Use the Internet

Task Examples
Initiating transactions Sales orders, purchase orders, and insurance or expense claims
Transaction participation Reviewing, approving, annotating, amending, and revising
Querying transactions Order or claim status, balance inquiries, and decision support
Information dissemination Store and forward replication and report repository access
Notification systems Order acknowledgments, alerts, and push-down workflows

Table of Contents - October 1996 | Home Page


Copyright © 1996 Miller Freeman, Inc. ALL RIGHTS RESERVED
Redistribution without permission is prohibited.
Please send questions or comments to mfrank@mfi.com
Updated Wednesday, September 25, 1996