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.
The buyer'sback-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,
software is needed for the web application.
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.
The extranet gateway on
the web server requires functionality for communicating with the
intranet gateway server.
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.