Clickable Business Models eBusiness Education Acronyms Cross References
B2B Content Standards EC Technology Standards Glossary Implementation Guidelines
Implementation Options General Recommendations References Methodology/Legends
 Home | Copyright Notice and Legal Disclaimers | Navigation Help | Tour! | Downloads | Contact Us | Site Index | Search
Implementation Options | Technical Basics | Internet Commerce Model  | Architecture |
Implementation (Technology) Options

Implementation Option 5a (Buyer's Web Application) - What Buyer Needs for Implementation
Special Notes:    

Application Interface Software
Network Service Provider
Back to Implementation Option 5a Index

The buyer's needs depend on whether the buyer is using existing back-end integration and communications infrastructure or has to build one or both.

The scenario used here is that buyer is using back-end integration originally developed for legacy EDI, with a new communications interface to a web application in the buyer's extranet as the first internet communication functionality ever implemented.  In this case, the buyer's needs are limited to the needs of implementing an extranet application and communications between the intranet and the extranet.

All the items listed in the Basics of Implementations:  Initial eBusiness Implementation are required, with exceptions noted below; the links in olive green below take the reader to those lists of basics.

  1. Application Interface software
    1. The buyer's back-end application may need to be modified to support internet communications.  This may be the case if a new gateway is developed to support internet communications.  The back-end application may need to be able to identify whether a file is to be routed to the legacy gateway or EDI process or routed through the new, internet-enabled gateway.
    2. Application interface software is needed for the web application.
  1. Gateway
    1. The gateway inside the firewall specifically requires functionality and dictionaries to support secure internet communications.  The web application may require a different data format than the back-end application, and the gateway needs to support that format; an XML content standard such as OAGIS is a good candidate as an interface file for the web application.
    2. The extranet gateway on the web server requires functionality for communicating with the intranet gateway server.
  1. An Internet Service Provider is used rather than a VAN; connections are point-to-point.  In this case the buyer has only one connection to worry about - the connection to the web application.  The supplier is using a web browser for a "virtual direct connection" to the web application.
  1. Hardware  
    1. Intranet gateway server
    2. Extranet gateway server
    3. Web server for the web application - may be on the same machine as the extranet gateway
    4. Data base server for the web application - may be on the same machine as the web application, but often is maintained  on a separate server that is more secure than the web server.
    5. Client computers
    6. Requirements for communications hardware depend on whether or not a 3rd party ISP is used.



Last updated 02 March 2003