Electronic Commerce (Charles River Media Networking/Security)

Chapter 1: What Is Electronic Commerce?

Figure 1.1: The value transaction management technology rate for an organization by category.

Figure 1.2: The role of the TMM solution in the organization.

Chapter 2: Types of E-Commerce Technology

Figure 2.1: Business-to-business procurement environment.

Figure 2.2: Business-to-business connectivity requirements.

Figure 2.3: Typical punchout flow using WCBE and Commerce Integrator.

Figure 2.4: WCBE Commerce Integrator architecture.

Figure 2.5: Typical punchout request flow.

Figure 2.6: Trading mechanisms in WCS MPE.

Figure 2.7: RFQ process flows in WCS MPE.

Figure 2.8: RFQ process flow for local RFQ.

Figure 2.9: RFQ process flow for remote RFQ.

Figure 2.10: Typical B2B environment using protocol conversion.

Figure 2.11: Punchout request flow with protocol conversion.

Chapter 3: Types of E-Business Models and Markets

Figure 3.1: E-business model components.

Figure 3.2: E-business model business process domains.

Figure 3.3: E-business model primary interactions.

Figure 3.4: Manufacturing core processes.

Figure 3.5: E-trailer core processes.

Chapter 6: Managing E-Commerce Web Site Development

Figure 6.1: A sample commerce server site after customization.

Figure 6.2: External intrusions network configuration.

Chapter 7: Building Shopping Cart Applications

Figure 7.1: It is possible to build simple Web applications using JSP alone. However, significant business applications require Java servlets, JavaBeans, and JavaServer Pages.

Figure 7.2: Model-view-controller architecture; JSP architectures can be modeled using the MVC pattern.

Figure 7.3: Shopping cart workflow; the shopping cart application moves through stages in an interactive workflow.

Figure 7.4: Programming for the real world; production applications should define a standard interface for accessing the application model and split the model into a data access and data management tier.

Figure 7.5: Three-tier data management production applications sometimes require a three-tier architecture for data management.

Figure 7.6: The command pattern helps decouple request managers from request handlers.

Chapter 8: Mobile Electronic Commerce

Figure 8.1: Peer-to-Peer (on demand) wireless network.

Figure 8.2: Wireless LAN (Infrastructure mode).

Figure 8.3: Enterprise-wide view of the wireless infrastructure.

Chapter 9: Enhancing a Web Server with E-Commerce Application Development

Figure 9.1: The three main stakeholders of enterprise development needs.

Chapter 16: Building an E-Commerce Trust Infrastructure

Figure 16.1: Steps in forming and verifying a digitally signed message.

Figure 16.2: The Security toolbar button in a typical browser.

Figure 16.3: Security Info page.

Figure 16.4: The list of certificate signers hard coded to be trusted in a typical browser.

Figure 16.5: A VeriSign CA certificate embedded in a typical browser.

Chapter 17: Implementing E-Commerce Enterprise Application Security Integration

Figure 17.1: Traditional trusted computing base (TCB).

Figure 17.2: Distributed component security architecture.

Figure 17.3: E-commerce requires Enterprise Application Integration (EAI) across multiple security technologies.

Figure 17.4: Key e-commerce challenge: End-to-end Enterprise Application Security Integration.

Figure 17.5: EASI framework.

Chapter 18: Strong Transaction Security in Multiple Server Environments

Figure 18.1: Protected communications process.

Figure 18.2: Warning if a user tries to submit information to an unsecured site.

Figure 18.3: A visual cue that you are on a secure site.

Figure 18.4: Digital ID certificate information page.

Figure 18.5: Warning if a site has a certificate issued by an untrusted authority.

Figure 18.6: Warning if a site is falsifying its claim to a certificate.

Chapter 20: Payment Technology Issues

Figure 20.1: Online payment processing authorization.

Figure 20.2: Online payment processing authorization.

Chapter 21: Electronic Payment Methods Through Smart Cards

Figure 21.1: Magnetic stripe cards process.

Figure 21.2: Card issuing process.

Figure 21.3: P3 interface.

Chapter 25: Business-to-Business and Business-to-Consumer

Figure 25.1: Roles in B2B e-commerce.

Figure 25.2: The supplier’s perspective.

Figure 25.3: Big differences in the types of electronically recordable user behavior.

Figure 25.4: E-commerce systems cover a wider range of user behavior.

Figure 25.5: The correspondence between the business activities and their fulfillment mechanisms map.

Figure 25.6: E-commerce business activity fulfillment mechanisms map.

Figure 25.7: E-commerce information architecture component stakeholders: user-oriented value-chain view.

Figure 25.8: Key interests of e-commerce stakeholders.

Figure 25.9: Properly implemented backend e-commerce systems ensure long-term success.

Figure 25.10: Typical “highly available” e-commerce user site access solution.

Figure 25.11: Fully redundant, geographically replicated Web site hosting architecture.

Figure 25.12: Traditional brick-and-mortar retail data warehouse.

Figure 25.13: Forward-looking brick-and-mortar retail data warehouse.

Figure 25.14: E-commerce site users are more than customers.

Figure 25.15: Brick-and-mortar versus e-commerce: User Activity Facts.

Figure 25.16: Brick-and-mortar versus e-commerce: Geography.

Figure 25.17: Brick-and-mortar versus e-commerce: Time.

Figure 25.18: Brick-and-mortar versus e-commerce: Content.

Figure 25.19: Brick-and-mortar versus e-commerce: Advertising.

Figure 25.20: E-commerce clickstream/callstream data warehouse schema.

Chapter 26: Summary, Conclusions, and Recommendations

Figure 26.1: Customer satisfaction versus excess capacity.