Implementation Options | Technical Basics | Internet Commerce Model | Architecture | |
Implementation Options
An electronic commerce implementation involves a choice of content standard, a choice of business process, and a choice of how information will be conveyed - implementation options. These can be combined in many ways. This section discusses the choices of transport and routing standards. These are used to move the payload - the actual data files - and ensuring the content privacy, authentication, integrity and non-repudiation.
![]() |
The Technical Basics of eBusiness Implementations | ||
|
Basic Implementation Options - User View | ||
![]() |
Information Exchange Timing Options | ||
![]() |
Mixing and Matching Options | ||
![]() |
Barriers to Electronic Commerce | ||
![]() |
Cost Factors to Consider for Implementation Options | ||
![]() |
Technology Matrix ("EC Matrix") | ||
![]() |
Basic System Architecture Components (IT View) | ||
![]() |
eBusiness Gateways | ||
![]() |
Value Added Networks | ||
![]() |
Overviews of Specific Implementation Options | ||
![]() |
1.0 Electronic Data Interchange ("Traditional" EDI) via a VAN | ||
![]() |
|||
![]() |
2.0 Client (PC/Mac) EDI application with a VAN | ||
![]() |
|||
![]() |
3.0 Integrated B2B via the Internet - Point-to-Point (no VAN or Hub) | ||
3a. | "Standards Agnostic" (Generic B2B) | ||
![]() |
|||
3b. | EDIINT - Legacy EDI (ASC X12 and EDIFACT) over the Internet | ||
![]() |
|||
![]() |
|||
3c. | RosettaNet XML using RNIF | ||
![]() |
|||
3d. | OAGIS XML | ||
3e. | Other XML | ||
![]() |
4.0 Integrated B2B via 3rd Party (Modern VANs/Hubs) | ||
4a. | "Standards Agnostic" (Generic B2B) | ||
![]() |
|||
4b. | Legacy EDI formats - ASC X12 and EDIFACT | ||
4c. | RosettaNet XML | ||
4d. | OAGIS XML | ||
4e. | Other XML | ||
![]() |
5.0 Web Applications | ||
5a. | Buyer's Web Application (using Web Forms) - with or without back-end integration on seller side | ||
5a1. | Buyer manages own web application in its own extranet, buyer's data is mastered in back-end application, back-end application is slave | ||
![]() |
|||
5a2. | Buyer manages own web application in its own extranet, buyer's data is mastered in web application, back-end is slave | ||
5a3. | Third-party web application used, with buyer-specific forms/templates, buyer's data is mastered in back-end application, back-end application is slave | ||
5a4. | Third-party web application used, with buyer-specific forms/templates, buyer's data is mastered in web application, back-end is slave | ||
5b. | Seller's Web Application (using Web Forms), with or without back-end integration on buyer side | ||
5b1. | Seller manages own web application in its own extranet, seller's data is mastered in back-end, web application is slave | ||
![]() |
|||
5b2. | Seller manages own web application in its own extranet, seller's data is mastered in web application, back-end is slave | ||
5b3. | Third-party web application used, with seller-specific forms/templates, seller's data is mastered in back-end application, back-end application is slave | ||
5b4. | Third-party web application used, with seller-specific forms/templates, seller's data is mastered in web application, back-end is slave | ||
Emerging Technologies | |||
These technologies are emerging and/or may be variations on other technologies; models for some of these technologies are still being piloted. EIDX will be adding documentation and models for these technologies as they become better understood. | |||
![]() |
6.0 Collaborative (Shared) Applications | ||
6a. | Trading Communities - Exchanges, Hubs, etc. | ||
6b. | Collaborative (shared) web application, with or without back-end integration | ||
![]() |
7.0 Web Services | ||
![]() |
eCommerce Technology Standards - Internet Commerce Model | ||
Last updated 28 February 2003