Web Trends and Technologies

1,740
-1

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,740
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • is understanding which version of the player is required to listen and view your content. There are two dimensions to the problem, the file format of the content itself and how it was encoded. This means that you'll probably have to upgrade to the latest versions of either player, and even then you might need some new pieces to support a new encoding scheme or to get the best performance possible.
  • Web Trends and Technologies

    1. 1. Web Trends and Technologies David Strom [email_address] (516) 944-3407 T6 11/1/99
    2. 2. Outline <ul><li>Web basics and protocols </li></ul><ul><li>New web technologies and trends </li></ul><ul><li>New eCommerce technologies </li></ul><ul><li>eCommerce Service Options </li></ul><ul><li>Storefront design basics </li></ul>
    3. 3. Goals <ul><li>Describe and demonstrate new web products and services </li></ul><ul><li>Articulate some web futures </li></ul><ul><li>Debunk some myths </li></ul><ul><li>Provide the foundation for making your own technology choices </li></ul>
    4. 4. Topic 1: Web Basics and Protocols <ul><li>HTML vs. HTTP </li></ul><ul><li>SET vs. SSL </li></ul><ul><li>XML vs. OBI </li></ul>
    5. 5. HTML vs. HTTP <ul><li>History lessons </li></ul><ul><li>Similarities and differences </li></ul>
    6. 6. HTML <ul><li>Markup language of the web </li></ul><ul><li>Describes the structure and content of a page </li></ul><ul><li>Contains both display control and the actual content itself </li></ul><ul><li>Developed first for document distribution, later used for publishing </li></ul>
    7. 7. Word Processing History <ul><li>Wylbur (1974-80) </li></ul><ul><li>TeX and other VT page editors (1976-85) </li></ul><ul><li>NBI, Xerox, Vydec word processors (1977-83) </li></ul><ul><li>Multimate/Wang (1982-5) </li></ul><ul><li>Word Perfect (1984-96) </li></ul><ul><li>MS Word (1992-) </li></ul><ul><li>HTML (1993-) </li></ul>
    8. 8. HTML History <ul><li>v 1.0 : early 90s </li></ul><ul><li>HTML+: 1993 </li></ul><ul><li>v 2.0 (RFC 1866, forms): 1995 </li></ul><ul><li>v 3.0 (tables, frames): 1995, schism between Netscape and Microsoft </li></ul><ul><li>v 3.2 (style sheets): adopted 1996 </li></ul><ul><li>v 4 : 1998, three versions proposed by W3C, but nothing really adopted yet </li></ul><ul><li>XHTML: 1999, a marriage of XML and HTML </li></ul><ul><li>(see www.w3c.org ) </li></ul>
    9. 9. Lessons Learned <ul><li>Dedicated machines with incompatible formats </li></ul><ul><li>New hardware platforms every 3-4 years </li></ul><ul><li>Alternating between WYSIWIG and tagged text </li></ul>
    10. 10. HTML Features <ul><li>Operating system independent </li></ul><ul><li>Browser independent </li></ul><ul><li>The user controls the browser </li></ul><ul><li>The author controls organization </li></ul><ul><li>The server controls -- well, not much! </li></ul>
    11. 11. HTML Goals <ul><li>Interoperability (I can read your docs) </li></ul><ul><li>Cross-platform compatibility (Macs can read PC docs) </li></ul><ul><li>Collaborate with my colleagues (We can jointly author docs) </li></ul>
    12. 12. HTML Realities <ul><li>New tags don’t have the same impact of yore </li></ul><ul><li>Netscape/Microsoft battle is still relevant but not significant (remember D-HTML?) </li></ul><ul><li>Look to XML for most interesting innovations in the near future </li></ul>
    13. 13. HTTP: A Brief History <ul><li>Developed by CERN in 1990/1 </li></ul><ul><li>Became open source in 1992/3 </li></ul><ul><li>The server side of things </li></ul>
    14. 14. Typical HTTP Conversation <ul><li>Open connection from browser to server </li></ul><ul><li>Request a particular page and other objects </li></ul><ul><li>Server responds, delivers data if possible </li></ul><ul><li>Close the request </li></ul>
    15. 15. HTTP is Stateless <ul><li>Each page request is independent </li></ul><ul><li>Servers have short memories </li></ul><ul><li>One-at-a-time processing </li></ul><ul><li>This has all sorts of problems for web shopping or tracking browsers over extended time periods </li></ul>
    16. 16. So How to Fix This? <ul><li>Use cookies or crypto certificates to keep track of users </li></ul><ul><li>Run scripts or programs on your web server </li></ul><ul><li>Use a database server and logins to keep track </li></ul>
    17. 17. SET vs. SSL <ul><li>Similarities and differences </li></ul><ul><li>Protocol descriptions </li></ul><ul><li>Practical applications </li></ul>
    18. 18. SSL: Encrypt Transactions <ul><li>Why encrypt? </li></ul><ul><li>Principles of cryptosystems </li></ul><ul><li>Understand certificate management </li></ul>
    19. 19. Why Encrypt? TRUST! <ul><li>Ensure your customer is authorized to use his account </li></ul><ul><li>Customer wants to make sure you are the legit seller </li></ul><ul><li>Ensure payment is received </li></ul><ul><li>Ensure goods are received </li></ul>
    20. 20. Steps in SSL Certificate Creation <ul><li>Select a CA to use and fill out their forms and pay them </li></ul><ul><li>CA verifies information provided </li></ul><ul><li>CA creates a certificate containing public key and expiration date </li></ul><ul><li>The certificate is stored on your web server </li></ul>
    21. 21. Hierarchy of Trust for Certificate Issuance <ul><li>Visa and MasterCard will designate or become CAs </li></ul><ul><li>Merchants trust these issuers or their banks </li></ul><ul><li>Cardholders will obtain certificates from their banks’ CA and store in electronic wallet </li></ul>
    22. 22. Examples of Certificate Authorities <ul><li>VeriSign </li></ul><ul><ul><li>www.Verisign.com </li></ul></ul><ul><li>GTE CyberTrust Solutions, Inc. </li></ul><ul><ul><li>www.cybertrust.gte.com </li></ul></ul><ul><li>Thawte Consulting </li></ul><ul><ul><li>www.thawte.com </li></ul></ul>
    23. 23. Certificate Creation <ul><li>Demo of key generation and certificate request </li></ul>
    24. 24. Verisign Server Certs <ul><li>www.verisign.com/server/prod </li></ul><ul><li>Different features, ranging in price from $349 to $1295/year </li></ul><ul><li>Offer different warranties, encyrption levels </li></ul>
    25. 25. Certificate Management <ul><li>Once public key certificates are issued, they must be managed to maintain integrity </li></ul><ul><ul><li>They contain expiration dates </li></ul></ul><ul><ul><li>They may be revoked for various reasons </li></ul></ul><ul><ul><li>Upon expiration, certificates must be renewed or reissued </li></ul></ul><ul><li>This is a consideration for using an external CA, as opposed to managing an internal CA </li></ul>
    26. 26. How is this accomplished? <ul><li>Secure servers and browsers </li></ul><ul><ul><li>Capable of strong encryption (up to 128 bit) </li></ul></ul><ul><ul><li>40 bit encryption is no longer considered adequate for financial transactions </li></ul></ul><ul><li>Digital certificates </li></ul><ul><ul><ul><li>Ensure the identity of the certificate holder </li></ul></ul></ul><ul><ul><ul><li>Also called digital IDs </li></ul></ul></ul><ul><li>The common protocol in use today is Secure Sockets Layer (SSL) </li></ul>
    27. 27. Secure Sockets Layer (SSL) <ul><li>Authenticates the merchant server </li></ul><ul><ul><li>Merchant Certificate obtained from trusted Certificate Authority </li></ul></ul><ul><li>Provides privacy through encryption of the message for both the sender and receiver </li></ul><ul><ul><li>Secure “pipe” negotiates maximum encryption compatible at browser and server for each message transmitted </li></ul></ul><ul><li>Ensures integrity of data transmitted </li></ul><ul><ul><li>Message authenticity check (algorithm) </li></ul></ul>
    28. 28. Secure Sockets Layer Protocol (SSL) <ul><li>https:// in the URL = a secure connection </li></ul><ul><li>SSL allows customers to verify who the merchant is </li></ul><ul><li>The merchant’s digital ID does not certify the integrity of the merchant </li></ul>Merchant’s Certificate (Digital ID) can be viewed by any secure browser
    29. 29. Secure Sockets Layer Protocol (SSL) <ul><li>SSL encrypts the customer order, which includes the payment information </li></ul><ul><li>This data is sent from the customer to the merchant via a secure “pipe” </li></ul>Customer Order with Payment Information Encrypted order sent Customer order decrypted at merchant server
    30. 30. What SSL Doesn’t Encrypt <ul><li>Once the data arrives on the secure server, it could be stored in an insecure location! </li></ul><ul><li>Or if someone has physical access to your desktop or server </li></ul>
    31. 31. Encryption Strength <ul><li>It is illegal to export outside the US products containing encryption that is stronger than 40 bits </li></ul><ul><li>It is not illegal to use encryption stronger than 40 bits internationally </li></ul><ul><li>Financial institutions do not consider 40-bit encryption adequate for Internet transactions </li></ul>
    32. 32. Encryption Strength <ul><li>Newer browser and server software are capable of 128-bit encryption </li></ul><ul><li>128-bit encryption is exponentially stronger than 40-bit encryption </li></ul>
    33. 33. SET: Authenticate Buyers <ul><li>What is the protocol </li></ul><ul><li>How it works </li></ul><ul><li>Advantages and disadvantages </li></ul>
    34. 34. What is SET protocol? <ul><li>Secure Electronic Transaction protocol is a common standard that was developed jointly by Visa, MasterCard and other partners to ensure the processing of secure transactions. </li></ul><ul><li>Based on RSA encryption </li></ul><ul><li>Uses public and private key pairs that have a mathematical relationship </li></ul>
    35. 35. How is SET Different from SSL? <ul><li>Digital certificates for SET will be payment-specific </li></ul><ul><ul><li>Merchants will be certified as legitimate to accept branded payment card transactions </li></ul></ul><ul><ul><li>Cardholders will be certified as valid account holders </li></ul></ul><ul><ul><li>Merchants will not see customer’s account number (it will only be passed to the acquirer) </li></ul></ul>
    36. 36. How is SET Different from SSL? Customer’s Digital ID related to a specific account + Customer Order info Merchant Server gets Customer’s Digital ID minus the account number + Customer Order Acquirer gets order receipt + Customer’s Digital ID with account number With SET:
    37. 37. The Mechanics of SET <ul><li>(1) Payment info sent from user to merchant </li></ul><ul><li>(2) Merchant confirms, fees charged </li></ul><ul><li>(3) Transaction to bank, funds debited/credited </li></ul><ul><li>(4) Merchant sends item to user </li></ul>
    38. 38. MasterCard ® Example of a SET Transaction http://www.mastercard.com/set/screen1.html
    39. 39. SSL vs. SET <ul><li>SSL </li></ul><ul><li>Server authentication </li></ul><ul><ul><li>Merchant certificate as legitimate business </li></ul></ul><ul><li>Possible for client authentication </li></ul><ul><ul><li>Not tied to payment method </li></ul></ul><ul><li>Privacy </li></ul><ul><ul><li>Encrypted message to merchant includes account number </li></ul></ul><ul><li>Integrity </li></ul><ul><ul><li>Message authenticity check </li></ul></ul><ul><li>SET </li></ul><ul><li>Server authentication </li></ul><ul><ul><li>Merchant certificate tied to accept payment brands </li></ul></ul><ul><li>Customer authentication </li></ul><ul><ul><li>Digital certificate tied to certain payment method </li></ul></ul><ul><li>Privacy </li></ul><ul><ul><li>Encrypted message does not pass account number to merchant </li></ul></ul><ul><li>Integrity </li></ul><ul><ul><li>Hash/message envelope </li></ul></ul>
    40. 40. Is SET the Answer to eCommerce? <ul><li>SET has been proposed as the answer to secure and interoperable eCommerce </li></ul><ul><ul><li>It is not currently mandated by Visa and MasterCard </li></ul></ul><ul><ul><li>There are big implementation issues for all concerned </li></ul></ul><ul><li>The SET protocol is definitely more secure than SSL </li></ul>
    41. 41. SET Issues <ul><li>Implementation of SET has some big drawbacks: </li></ul><ul><ul><li>Lack of interoperability among systems </li></ul></ul><ul><ul><li>Management of public key infrastructure </li></ul></ul><ul><ul><li>Distribution of digital certificates requires action on the part of the consumer </li></ul></ul><ul><ul><li>Will banks want to become cert authorities? </li></ul></ul><ul><li>And who will pay for all this? </li></ul><ul><li>Meanwhile, eCommerce goes on </li></ul>
    42. 42. The Future of SET <ul><li>Non-repudiation of transactions through digital certificates for both merchant and customer </li></ul><ul><li>SET may be the industry standard for payments, but yet to be implemented </li></ul><ul><li>It will be far more difficult for a customer to claim no knowledge of a transaction </li></ul><ul><li>Demonstrations continue </li></ul>
    43. 43. Another View of SET (Lincoln Stein) <ul><li>“ An over-engineered, committee-designed solution to a nonproblem, a boondoggle invented by hidebound credit-card companies panic-stricken over the prospect of not getting their piece of the Internet pie.” </li></ul><ul><li>WebTechniques, 8/98 </li></ul>
    44. 44. What About eWallets and SET? <ul><li>Verifone ® vWALLET SM </li></ul><ul><li>GlobeSET (SET now, server-side non-SET later) </li></ul><ul><li>Transactor/Citibank Wallet (Jscript bookmark) </li></ul><ul><li>eWallet.com (only SSL) </li></ul><ul><li>Microsoft Wallet (in Win98, IE 4.01) (both SSL and SET) </li></ul>
    45. 45. What’s in an eWallet? <ul><li>Credit card accounts </li></ul><ul><li>Debit card accounts </li></ul><ul><li>Checking accounts </li></ul>
    46. 46. All of These Have in Common <ul><li>Access to your accounts </li></ul><ul><li>Credit card and other account numbers are stored by the service provider in a database, or on your hard disk </li></ul><ul><li>These numbers are not transmitted to the merchant </li></ul><ul><li>Consumer must initiate account set-up in advance of making any purchases </li></ul>
    47. 47. How Electronic Wallets Work Today <ul><li>Consumer must initiate request for electronic “wallet” software </li></ul><ul><li>Credit card or other account numbers are given to provider one time before any purchases are made </li></ul><ul><li>Closed system: only available to participating merchants and cardholders who have signed up in advance </li></ul>
    48. 48. How Electronic Wallets Will Work in the Future <ul><li>With SET protocol, will contain digital IDs with encrypted account information </li></ul><ul><li>Since digital IDs will be tied to specific accounts, wallets will keep track of all that information </li></ul><ul><li>At that point, wallets will be widely distributed and universally accepted </li></ul>
    49. 49. Interoperability is the Key <ul><li>Wallets will become widely used when the following events occur: </li></ul><ul><ul><li>Mass distribution of wallets to consumers is easily made </li></ul></ul><ul><ul><li>Will be accepted by all merchants, regardless of wallet brand or payment brand </li></ul></ul>
    50. 50. eWallet Demonstration
    51. 51. Some Problems with eWallets <ul><li>Not transferable to other wallets </li></ul><ul><li>Tied to a single PC </li></ul><ul><li>Not available for use at many web storefronts </li></ul><ul><li>Just solve a small part of the overall payment process </li></ul>
    52. 52. Trends <ul><li>eWallets will eventually go away </li></ul><ul><li>SET becomes a server-side issue </li></ul><ul><li>SSL still dominates eCommerce transactions for many years </li></ul>
    53. 53. XML vs. OBI <ul><li>Similarities and differences </li></ul><ul><li>Protocol implications </li></ul><ul><li>Practical applications </li></ul>
    54. 54. XML History <ul><li>v .01: First XML working group, 1996 </li></ul><ul><li>v 1.0: Feb 1998 </li></ul><ul><li>To some extent, having a version number isn’t really that important! </li></ul>
    55. 55. Key XML Points <ul><li>A method for putting structured data in a text file </li></ul><ul><li>Looks a bit like HTML but isn't </li></ul><ul><li>Is text, but meant to be read by computer programs </li></ul><ul><li>Is new, but based on SGML like HTML </li></ul><ul><li>Is license-free and platform-independent </li></ul><ul><li>Is database and file-format independent </li></ul>
    56. 56. How Did XML Come About? <ul><li>SGML was too thick for building new applications </li></ul><ul><ul><li>Complexity of building DTDs </li></ul></ul><ul><ul><li>No standard syntax or parsers </li></ul></ul><ul><li>HTML was too thin </li></ul><ul><ul><li>New tags got stuck between MS and NSCP </li></ul></ul><ul><ul><li>Adding scripts inside web pages dicey </li></ul></ul><ul><ul><li>Never designed with data structures in mind </li></ul></ul><ul><li>Solution is XML! </li></ul>
    57. 57. Why is XML a Better Mousetrap? <ul><li>Syntax standard of < .. > and &’s and ;’s </li></ul><ul><li>DTD is optional but ... </li></ul><ul><li>Tags aren’t </li></ul><ul><li>All of this makes for a better-formed document </li></ul>
    58. 58. What about OBI? <ul><li>Open Buying on the Internet </li></ul><ul><li>A bunch of standards: SSL, X12 EDI, X.509 PKI </li></ul><ul><li>Proposed 3/97, revised 6/98 </li></ul><ul><li>Emphasis is with OPEN and not point-to-point EDI </li></ul><ul><li>Products from Netscape, Commerce One, IBM, Epic Systems </li></ul>
    59. 59. OBI Components <ul><li>Buyer (could be software or a person) </li></ul><ul><li>Buyer’s server </li></ul><ul><li>Seller’s server </li></ul><ul><li>Payment authority/clearinghouse </li></ul>
    60. 60. Typical OBI Process <ul><li>Buyer connects to web site with https </li></ul><ul><li>Seller verifies buyer, then displays catalog </li></ul><ul><li>Buyer fills out forms, submits order </li></ul><ul><li>Seller checks transaction using certs </li></ul><ul><li>Servers talk to each other and approve order </li></ul><ul><li>Buyer server sends order up his chain for approval </li></ul><ul><li>Seller determines how to get paid </li></ul>
    61. 61. Unresolved OBI Issues <ul><li>Who owns the catalog (buyer or seller)? </li></ul><ul><li>How much infrastructure is really needed to connect them? </li></ul><ul><li>Does it compete with existing EDI solutions? </li></ul><ul><li>Knitting together a solid solution is more than enumerating standards! </li></ul>
    62. 62. Trends <ul><li>XML becomes more important and useful as number of products increase </li></ul><ul><li>OBI implementations still lag and are far too complex for most site operators </li></ul>
    63. 63. Topic 2: New Web Technologies <ul><li>Caching servers </li></ul><ul><li>Distributed content providers </li></ul><ul><li>Load balancing tools </li></ul><ul><li>Web monitoring services </li></ul><ul><li>Internet appliances </li></ul><ul><li>Streaming media servers </li></ul><ul><li>Web conferencing </li></ul>
    64. 64. Some General Comments <ul><li>The browser is the defacto user interface and management tool </li></ul><ul><li>The IP Internet is the defacto infrastructure </li></ul><ul><li>ISPs aren’t just about access anymore </li></ul><ul><li>Web applications need their own network infrastructure </li></ul>
    65. 65. Caching Servers <ul><li>Overall purpose </li></ul><ul><li>Typology </li></ul><ul><li>Advantages and disadvantages </li></ul>
    66. 66. Overall Purpose <ul><li>To move remote web content closer to the user </li></ul><ul><li>Reduce transit time and overall network latency </li></ul><ul><li>Reduce the world wide wait </li></ul><ul><li>Really, what is involved is just a big hard disk! </li></ul>
    67. 67. General Issues <ul><li>Freshness of cache: can you keep track of when objects change </li></ul><ul><li>Bandwidth conservation to reduce updates to the cache and avoid uncachable items </li></ul><ul><li>Size of the cache and where it is placed on your network </li></ul><ul><li>Integration into existing web and Internet access strategy </li></ul>
    68. 68. Types of Caching Servers <ul><li>Software-only </li></ul><ul><li>Specialty appliance </li></ul><ul><li>Software on Unix, other general OS </li></ul>
    69. 69. Software Only Caches <ul><li>Began with Squid, evolved into Inktomi </li></ul><ul><li>Novell, Microsoft have caches to web server line </li></ul><ul><li>(+): Inexpensive, convenient </li></ul><ul><li>(-): Don’t scale well and difficult to admin </li></ul>
    70. 70. Pre-packaged Unix Devices <ul><li>Installed Squid and tuned copy of Unix just for caching </li></ul><ul><li>Cobalt, Network Appliance, PacketStorm </li></ul><ul><li>(+): Inexpensive, convenient </li></ul><ul><li>(-): Don’t scale well and difficult to admin </li></ul>
    71. 71. Specialty Cache Appliances <ul><li>Dedicated caching device, typically running its own OS </li></ul><ul><li>Infolibria, Cacheflow, Cisco, Lucent </li></ul><ul><li>(+): Easy to admin, optimized for performance and reliability </li></ul><ul><li>(-): Costly and may need other network infrastructure improvements </li></ul>
    72. 72. Server Issues <ul><li>Microsoft, Cisco and Entera servers all require their own software and protocols to be loaded on all network routers </li></ul><ul><li>May have to change proxy setup in every browser </li></ul><ul><li>May need additional network infrastructure </li></ul>
    73. 73. Caching Resources <ul><li>Brian Davison’s comparison site www.web-caching.com/proxy-comparison.html </li></ul><ul><li>Internet Research Group www.caching.com/vendors.htm </li></ul>
    74. 74. Trends <ul><li>More caching appliances as time goes on </li></ul><ul><li>Better and cheaper caching devices appear </li></ul><ul><li>Most ISPs will use them within a few years if they want to retain customers </li></ul>
    75. 75. Distributed Content Service Providers <ul><li>Problem: even the best cache can’t get around Internet congestion issues </li></ul><ul><li>Solution: a new breed of providers who have extended co-location into content replication by using a series of products that do more than just caching pages </li></ul>
    76. 76. What Do These Things Do? <ul><li>Balance and manage loads </li></ul><ul><li>Distribute content to various data centers located on different continents </li></ul><ul><li>Guaranteed quality of service levels and response times </li></ul><ul><li>And, of course, cache your site! </li></ul>
    77. 77. Vendors <ul><li>Sandpiper, Akamai, Mirror Image </li></ul><ul><li>Skycache and Digital Island build on top of Inktomi cache servers </li></ul><ul><li>F5.com’s Global Site, merges distributed servers </li></ul><ul><li>(+): Turnkey operation ala the best of the co-los, added redundant operations </li></ul><ul><li>(-): Can be expensive </li></ul>
    78. 78. Trends <ul><li>More and more providers appear </li></ul><ul><li>Most ISPs will offer some kind of content replication as the next step in co-location </li></ul><ul><li>Prices will drop as competition gets fierce </li></ul>
    79. 79. Load Balancing, Web Switches and Redirectors <ul><li>Cisco Local Director </li></ul><ul><li>Network Engines’ Cluster Control </li></ul><ul><li>Arrowpoint's Content Smart </li></ul><ul><li>Alteon WebSystems </li></ul><ul><li>Foundry Networks Server Iron </li></ul><ul><li>iPivot’s Commerce Accelerator </li></ul>
    80. 80. How Do These Things Work? <ul><li>Typically installed between router and web server </li></ul><ul><li>Sometimes have to reconfigure routers or proxy server entries </li></ul><ul><li>Some include caching or proxy services </li></ul><ul><li>Really are layer 4 (UDP, transport) switches that examine packets for web content </li></ul><ul><li>Managed via web browser, of course! </li></ul>
    81. 82. Notable Features <ul><li>Arrowpoint ignores obvious uncachable items </li></ul><ul><li>Cisco does application server load balancing and domain load balancing </li></ul><ul><li>Network Engines' ClusterControl handles content management/replication </li></ul><ul><li>iPivot looks at ways to do SSL better, using inline crypto </li></ul>
    82. 83. Issues <ul><li>Performance </li></ul><ul><li>Overall response times </li></ul><ul><li>Security </li></ul><ul><li>Reliability </li></ul><ul><li>More information, see www.nwc.com/913/913r2.html </li></ul>
    83. 84. Trends <ul><li>Prices will remain high as these are specialty items </li></ul><ul><li>Will compete with distributed content providers </li></ul>
    84. 85. Web Monitoring Services <ul><li>WebPartner.com , monitor server uptime </li></ul><ul><li>Uptime , another one from Phil Grenspun (uptime.arsdigita.com) </li></ul><ul><li>ServerSittter.com , a monitoring card that fits inside NT machine </li></ul><ul><li>Manage.com , for entire eCommerce transaction path </li></ul>
    85. 86. Monitors, con’t. <ul><li>Sitescope from freshtech.com and Netiq.com , network monitoring software </li></ul><ul><li>Tracerlock , notify you when a page mentions your keywords (peacefire.org) </li></ul><ul><li>NetResolve , monitoring your site from 25 cities </li></ul>
    86. 87. Why Use These Things? <ul><li>Outsource a key element of your data infrastructure </li></ul><ul><li>Use the Internet to check up on itself </li></ul><ul><li>You want your web up as much as your mainframe but don’t have the staff or skills to do it </li></ul>
    87. 88. Example: WebPartner’s Services <ul><li>Free web-based registration </li></ul><ul><li>Monitors set of URLs </li></ul><ul><li>Notification via email when down and weekly reports </li></ul><ul><li>Compares performance with a set of 100 other sites </li></ul><ul><li>Demonstrate reports at www.webpartner.com </li></ul>
    88. 89. Example: Manage.com’s Services <ul><li>Transactions performance and reliability </li></ul><ul><li>Service chain analysis, including key infrastructure components </li></ul><ul><li>Traffic loads: actual vs. expected </li></ul><ul><li>User interface analysis </li></ul><ul><li>Action plan for management (all for $45k!) </li></ul>
    89. 90. Trends <ul><li>More and more of these services will be available </li></ul><ul><li>Free services will abound, some will actually be pretty good! </li></ul><ul><li>Still need some market consolidation to be truly useful </li></ul>
    90. 91. Internet Appliances <ul><li>Cobalt Qube </li></ul><ul><li>Technauts eServer </li></ul><ul><li>Encanto </li></ul><ul><li>Technologics InstaGate </li></ul>
    91. 92. What is an Internet Appliance? <ul><li>Pre-packed hardware and software </li></ul><ul><li>Simple to setup, use and manage </li></ul><ul><ul><li>usually with a web browser </li></ul></ul><ul><li>Don’t have keyboards or monitors </li></ul><ul><li>Integrate into existing Windows and other NOS environments </li></ul><ul><ul><li>AppleTalk, IPX, UNIX/NFS </li></ul></ul><ul><li>Serves a variety of needs </li></ul>
    92. 93. Target applications <ul><li>Small business Extranet </li></ul><ul><li>SOHO/ROBO Intranet server </li></ul><ul><li>Discussion Forum server </li></ul><ul><li>Workgroup file/CD ROM sharing </li></ul><ul><li>Firewall, VPN server </li></ul><ul><li>Remote access router </li></ul><ul><li>Remote access server </li></ul><ul><li>Office email server </li></ul>
    93. 94. Six categories of appliances <ul><li>Shared network storage </li></ul><ul><li>Web server </li></ul><ul><li>eCommerce server </li></ul><ul><li>Security server </li></ul><ul><li>Intranet applications server </li></ul><ul><li>Communications server </li></ul>
    94. 95. A partial taxonomy
    95. 96. General state of appliances <ul><li>Almost plug and play </li></ul><ul><li>User interfaces intentionally limited </li></ul><ul><li>Matching categories and needs not easy </li></ul><ul><li>Setup of users and groups may be tedious </li></ul><ul><ul><li>Most not well integrated with NOS access controls </li></ul></ul><ul><ul><li>Not an issue if this is first/only server </li></ul></ul><ul><li>Scalability? </li></ul><ul><ul><li>Units designed for small/branch office needs </li></ul></ul>
    96. 97. What features do you need? <ul><li>Ask yourself, ask your vendor: </li></ul><ul><li>If web or other Internet/Intranet server, </li></ul><ul><ul><li>How extensible? Expansion slots? Type? </li></ul></ul><ul><ul><li>Type of built-in OS? Type of server software? </li></ul></ul><ul><ul><li>How many ways to upload files to your web? </li></ul></ul><ul><li>If communications server, </li></ul><ul><ul><li>Types and number of network interface(s)? </li></ul></ul><ul><li>If security server, </li></ul><ul><ul><li>Firewall features? What VPN? Client software? </li></ul></ul>
    97. 98. Appliances: Pros <ul><li>Simplicity over NT & UNIX servers, </li></ul><ul><ul><li>especially for organizations with little or no OS admin expertise </li></ul></ul><ul><li>Reduced total cost of ownership </li></ul><ul><ul><li>Appliance may cost less than software to provide equivalent features </li></ul></ul><ul><li>Vendors seek to “user-proof” appliances </li></ul><ul><ul><li>limited access to OS, not as easy to shoot yourself in the foot </li></ul></ul><ul><ul><li>Often more secure “out-of-box” than OS servers </li></ul></ul>
    98. 99. Appliances: Cons <ul><li>Can’t find and manage on corporate net </li></ul><ul><ul><li>not issue for those that support SMB/AppleShare </li></ul></ul><ul><li>May need more than browser to manage </li></ul><ul><ul><li>telnet, configuration wizards and monitors </li></ul></ul><ul><li>Separate access control, authentication </li></ul><ul><ul><li>Difficult to apply uniform user and group access controls across appliances and NOS systems </li></ul></ul><ul><li>How scalable are CPU,disk, networks </li></ul>
    99. 100. Demonstration: Cobalt Qube <ul><li>For more information, check out my report at www.corecom.com/ia </li></ul>
    100. 101. Trends <ul><li>More of them and cheaper too </li></ul><ul><li>Still for SO/HO environments mainly, although that is changing </li></ul><ul><li>Already some vendor consolidation </li></ul>
    101. 102. Streaming Media Servers <ul><li>Microsoft NetShow (NT/Server-only but free) </li></ul><ul><li>Real Server (NT and Unix but $$) </li></ul>
    102. 103. Why Use These Products? <ul><li>Training films </li></ul><ul><li>Corporate speeches and briefings </li></ul><ul><li>Live broadcasts </li></ul>
    103. 104. Pieces Required <ul><li>Web server </li></ul><ul><li>Appropriate player </li></ul><ul><li>Media server </li></ul><ul><li>Encoding tools </li></ul>
    104. 105. Steps to Production <ul><li>Record your event or arrange for live broadcast </li></ul><ul><li>Encode your media </li></ul><ul><li>Copy file to media server </li></ul><ul><li>Post link on your web site to stream </li></ul><ul><li>Make sure everyone has right version of players to view </li></ul>
    105. 106. What Could Go Wrong? Everything! <ul><li>Matching file formats with correct player versions (and picking the right .avi, .wav, .au, MPEG, MP3, etc) </li></ul><ul><li>Tying the web and media server applications together </li></ul><ul><li>Setting up encoding sessions properly </li></ul>
    106. 107. Trends <ul><li>Ease of use remains biggest obstacle </li></ul><ul><li>Bandwidth-challenged users need not apply </li></ul><ul><li>Encoders, file formats, et al. are getting more complex still </li></ul><ul><li>Maybe some hope with MP3? </li></ul>
    107. 108. Web Conferencing <ul><li>Differences and typology </li></ul><ul><li>Issues </li></ul><ul><li>Typical products </li></ul>
    108. 109. Different Conferencing Types <ul><li>One to one, screen sharing </li></ul><ul><li>One to many, broadcasting seminars </li></ul><ul><li>Many to many, collaboration and distance learning </li></ul>
    109. 110. Why Conference? <ul><li>Save money on travel costs </li></ul><ul><li>Improve real-time customer support over the web </li></ul><ul><li>Collaborate on work product </li></ul>
    110. 111. Different Conferencing Data Streams <ul><li>Just text chat, AOL IM and IRC </li></ul><ul><li>Sending audio or video over the net </li></ul><ul><li>Net for visuals, phone bridge for audio </li></ul><ul><li>Real-time conference or stored/replayed lecture </li></ul>
    111. 112. Conferencing Issues <ul><li>Too many pieces and products to fit together </li></ul><ul><li>Three words: browser plug ins! </li></ul><ul><li>Better bandwidth, low latency needed </li></ul><ul><li>Can’t always share any desktop application </li></ul><ul><li>Can get pricey </li></ul>
    112. 113. Typical Products <ul><li>Webex , for collaborations and product tours </li></ul><ul><li>Webline , for collaboration and screen sharing, chat and technical support (new email management system), using the phone out of band or VoIP inband </li></ul><ul><li>Webpodium , for video events and web presentations </li></ul>
    113. 114. What Are They Good For? <ul><li>Regular sessions with the same attendees </li></ul><ul><li>One-on-one or one-to-three meetings best </li></ul><ul><li>Run tight control over computing environment of your attendees </li></ul><ul><li>Have at least T-1 connection </li></ul>
    114. 115. Trends <ul><li>Bandwidth-challenged issues as with streaming servers </li></ul><ul><li>Audio/video synchronization still a big problem due to network latencies </li></ul><ul><li>Live events can bring congestion quickly but lots of PR value (Victoria’s Secret as case in point) </li></ul>
    115. 116. Topic 3: New eCommerce Technologies <ul><li>1Click payment providers </li></ul><ul><li>eCommerce hosting vendors </li></ul><ul><li>Personal shopping portals </li></ul>
    116. 117. New Payment Providers <ul><li>1Clickcharge.com </li></ul><ul><li>qPass.com </li></ul><ul><li>Cybercash’s InstaBuy.com </li></ul><ul><li>eCharge.com </li></ul><ul><li>Others </li></ul>
    117. 118. First, Remember the Old Payment Providers? <ul><li>Digicash </li></ul><ul><li>Cybercash (first generation) </li></ul><ul><li>First Virtual </li></ul><ul><li>Mondex </li></ul><ul><li>GlobeID </li></ul>
    118. 119. Why Didn’t They Work? <ul><li>Too complex to implement </li></ul><ul><li>Too much cumbersome infrastructure </li></ul><ul><li>Not too many stores took their kind of money </li></ul><ul><li>Too many other technical challenges </li></ul><ul><li>Solved the wrong problem first (credit card snooping) </li></ul>
    119. 120. How NOT to Design a Payment Screen <ul><li>www.netmar.com/new/norderform.shtml </li></ul>
    120. 121. Characteristics <ul><li>Mainly for digital content delivery </li></ul><ul><li>Per day pass (WSJ) </li></ul><ul><li>Charge 8- 12% per transaction </li></ul><ul><li>Universal membership </li></ul><ul><li>Don’t leave site while completing purchase </li></ul>
    121. 122. Advantages <ul><li>Ease of use </li></ul><ul><li>No credit card transmission over the Internet </li></ul>
    122. 123. Disadvantages <ul><li>Need to reach critical mass of users almost at launch </li></ul><ul><li>Still rely on username/password combination which can be cumbersome </li></ul><ul><li>Small companies without a lot of depth </li></ul>
    123. 124. Ad networks/Link and Banner Exchanges <ul><li>LinkExchange/Microsoft </li></ul><ul><li>SmartAge.com </li></ul><ul><li>Eliancecorp.com, charges % of net sales </li></ul><ul><li>Netcentives’ ClickRewards </li></ul>
    124. 125. ClickRewards <ul><li>Pays you in airline miles for your patronage </li></ul><ul><li>Accrue miles on many sites </li></ul><ul><li>You redeem benefits on their site </li></ul>
    125. 126. Trends <ul><li>Is this deja vu all over again? </li></ul><ul><li>It will take a lot to dislodge SSL as king </li></ul><ul><li>Critical mass issue biggest obstacle </li></ul>
    126. 127. Turnkey eCommerce Hosting Providers <ul><li>GeoShop/Yahoo </li></ul><ul><li>ViaWeb/Yahoo </li></ul><ul><li>iCat </li></ul><ul><li>Shopsite/Open Market </li></ul><ul><li>iTool </li></ul><ul><li>Shopzone </li></ul><ul><li>Encanto </li></ul>
    127. 128. GeoShop/Yahoo <ul><li>Builds on GeoCities “communities” but for merchants ( www.geocities.com/join/geoshops ) </li></ul><ul><li>$25/month for just commercial listings </li></ul><ul><li>$180/month (or more!) for actual transactions </li></ul><ul><ul><li>working with Internet Commerce Services Corp. who uses Open Market Transact servers ( www.icoms.com/pp.htm ) </li></ul></ul>
    128. 129. ViaWeb/Yahoo <ul><li>$100/month (<50 items) or $300/month options </li></ul><ul><li>CyberCash processing $500 setup </li></ul><ul><li>Solid reporting and admin options </li></ul>
    129. 130. iCat Commerce Online Hosting Solution <ul><li>Free for <10 items, $99/mo. for 100 items </li></ul><ul><li>No per-transaction fees </li></ul><ul><li>Email and browser-based notifications of purchase completion </li></ul><ul><li>Advanced items like upsell, featured products, cybercash gateways </li></ul>
    130. 131. ShopSite demo <ul><li>www.reliablehost.com/cgi-bin/bo/start.cgi </li></ul><ul><li>Can now handle two concurrent currencies </li></ul><ul><li>username: test8 </li></ul><ul><li>password: test </li></ul>
    131. 132. iTool <ul><li>www.itool.com/admin/controlpanel.cfm </li></ul><ul><li>$25-$100/mo. </li></ul><ul><li>Username: dstrom/pwd+1 </li></ul>
    132. 133. Shopzone <ul><li>www. btsw .com , $995 </li></ul><ul><li>Real-time credit card verification through CyberCash </li></ul><ul><li>Store builder and publisher functions to both NT and Unix web servers </li></ul>
    133. 134. Encanto <ul><li>Turnkey server/software for free! </li></ul><ul><li>Payment gateway included ($50 initial, $70/month) </li></ul><ul><li>Web storefront, shopping cart, catalog </li></ul><ul><li>Also need secure cert, merchant bank acct. </li></ul><ul><li>All managed via browser, steps are clearly documented </li></ul><ul><li>Demo at www.encanto.com/ego/demo </li></ul>
    134. 135. Personalized Shopping Portals <ul><li>Shopnow.com </li></ul><ul><li>iGive.com for charities </li></ul><ul><li>eBates.com </li></ul>
    135. 136. ShopNow, eBates <ul><li>Each user registers and sets up own mini mall with links to stores </li></ul><ul><li>Basic rebate program but large collection of stores </li></ul>
    136. 137. iGive <ul><li>Percentage of sales goes towards charities </li></ul><ul><li>Clickthroughs also are measured and accumulate $ </li></ul><ul><li>Members have earned $300k for charities so far </li></ul>
    137. 138. Why Use These Services? <ul><li>Save money </li></ul><ul><li>Build loyalty, return visits </li></ul><ul><li>Make eCommerce easier? Not sure. </li></ul>
    138. 139. Topic 4: eCommerce Service Options <ul><li>Rent, Buy, or Build </li></ul><ul><li>Rent : outsource to a CSP </li></ul><ul><li>Buy suite of software </li></ul><ul><li>Build it yourself </li></ul>
    139. 140. Find an CSP <ul><li>More ISPs are offering eCommerce solutions </li></ul><ul><li>Have to use their software standards and payment schemes </li></ul><ul><li>Could be pricey </li></ul><ul><li>Just catching on in USA </li></ul>
    140. 141. Evaluating CSPs <ul><li>Do they offer storefront design? </li></ul><ul><li>Have in-house programmers? </li></ul><ul><li>Hosting of your own web server machine? </li></ul><ul><li>How many payment systems do they support? </li></ul><ul><li>What kinds of accounting reports do they offer? </li></ul>
    141. 142. The Catch-22 of CSPs: <ul><li>To be successful, a provider has to promote his products via the Internet and have detailed descriptions on their own web sites! </li></ul><ul><li>But try to find this information isn’t easy. </li></ul>
    142. 143. Some CSP Examples <ul><li>www. psi .net/web/ecommerce.shtml </li></ul><ul><li>www. Best .com/bizcomm.html </li></ul><ul><li>www. Brainlink .com/html/ </li></ul><ul><li>www. Earthlink .net </li></ul><ul><li>IBM : mypage.ihost.com </li></ul><ul><li>www. Netcom .com </li></ul><ul><li>business. Mindspring .com/prod-svc/smbiz/ </li></ul><ul><li>www. Mindrush .com/ </li></ul><ul><li>www.outer.net/ONCommerce </li></ul>
    143. 144. Price Comparison assumptions <ul><li>10 Mb disk storage </li></ul><ul><li>Single email account </li></ul><ul><li>InterNIC $75 fee included for domain name </li></ul>
    144. 145. Price Comparison
    145. 146. Earthlink pricing explained 175 40 Ecommerce 210 100 TOTAL 75 Domain fee 10 20 SSL cert. (waived) 20 Total Access Acct. 25 20 Starter Site Setup fee Monthly fee Program
    146. 147. One Way to Support Lots of Payment Systems <ul><li>Wired-2-Shop </li></ul><ul><li>www.wired-2-shop.com/TestDrive/Admin/PaymentList.asp </li></ul>
    147. 148. Storefront service providers <ul><li>www.sitematic.com, flat rate for $40/mo </li></ul><ul><li>www.stumpworld.com/Alpha Software, $99, connects to Cybercash and OM Payment systems </li></ul>
    148. 149. The Suite Approach <ul><li>Leading contenders </li></ul><ul><li>What is part of the suite and what isn’t </li></ul><ul><li>Prices and platforms </li></ul>
    149. 150. Popular eCommerce Suites
    150. 151. Popular eCommerce Suites (con’t)
    151. 152. Four Typical Elements <ul><li>Catalog </li></ul><ul><li>Storefront designer </li></ul><ul><li>Ordering/inventory system </li></ul><ul><li>Shopping cart/check out system </li></ul>
    152. 153. The Cold Hard Reality of Suites <ul><li>Suites are nothing more than collection of products </li></ul><ul><li>Lack integration among various elements </li></ul><ul><li>Difficult to setup, customize, and use </li></ul><ul><li>Require you to live “inside” their structure </li></ul><ul><li>Limited payment options </li></ul><ul><li>Sounds like early MS Office </li></ul>
    153. 154. Payment Systems Included in Each Suite <ul><li>Microsoft: Verifone, Buy Now </li></ul><ul><li>IBM (Net.Commerce): Verifone, SET/eTill </li></ul><ul><li>Domino Merchant: CyberCash, Verifone </li></ul><ul><li>OpenMarket: Verifone </li></ul><ul><li>WebSite Pro: IC Verify, PC Authorize, CyberCash, others </li></ul><ul><li>Intershop: CyberCash, ICVerify, others </li></ul>
    154. 155. Sample Stores Included in Each Suite <ul><li>Microsoft: 4 stores </li></ul><ul><li>IBM: eMall, simple and advanced sample stores </li></ul><ul><li>Domino: 1 store </li></ul><ul><li>OpenMarket: none </li></ul><ul><li>WebSite Pro: 1 bookstore </li></ul><ul><li>Intershop: 3 stores </li></ul>
    155. 156. Database Support
    156. 157. Dealing With ODBC <ul><li>Have to understand how to set up data sources </li></ul><ul><li>Intimate knowledge of your data structure </li></ul><ul><li>Re-install ODBC drivers at least once! </li></ul><ul><li>Best to start with built-in database </li></ul>
    157. 158. Store Wizards Included in Each Suite <ul><li>Net.Commerce (the best) </li></ul><ul><li>WebSite Pro (but doesn’t do much) </li></ul><ul><li>Intershop (various wizards) </li></ul><ul><li>MS Commerce (although you’ll really need to know COM!) </li></ul>
    158. 159. WebSite Professional website.ora.com <ul><li>Version 2, shipping since 9/97 </li></ul><ul><li>US$799! </li></ul><ul><li>NT (or 95) </li></ul><ul><li>Supports seven different payment processors: SSL, CyberCash </li></ul><ul><li>One sample store (bookstore) </li></ul>
    159. 160. Sample storefront <ul><li>merchant.inline.net/admin </li></ul>
    160. 161. WebSite Configuration Sheet
    161. 162. Store Properties <ul><li>Only can operate a single payment system </li></ul><ul><li>Run on a series of Access databases </li></ul><ul><li>Built-in tax table, but for N.Americans! </li></ul><ul><li>Well documented data structures in typical O’Reilly fashion </li></ul>
    162. 163. Recommendations <ul><li>Lowest priced suite by far! </li></ul><ul><li>iHTML is robust, but will take some learning </li></ul><ul><li>Nice store setup and organization of catalog </li></ul><ul><li>Good low-end solution </li></ul><ul><li>Other alternatives: ShopZone ( www.btsw.com ), Alpha Merchant ( www.alphasoftware.com ) </li></ul>
    163. 164. Intershop <ul><li>demo at demo.intershop.com (admin/admin for store) </li></ul><ul><li>Includes Sybase SQL 11 </li></ul><ul><li>US$5000, includes 3 mos. support </li></ul>
    164. 165. Seven Different Managers <ul><li>Catalog </li></ul><ul><li>Products </li></ul><ul><li>Store </li></ul><ul><li>Purchases </li></ul><ul><li>Inventory </li></ul><ul><li>Customers </li></ul><ul><li>Admin </li></ul>
    165. 166. Characteristics <ul><li>Everything managed via browser, which can get tedious </li></ul><ul><li>But you already have a database behind it </li></ul>
    166. 167. Payment Options galore
    167. 168. Recommendations <ul><li>Most flexible payment options of any suite </li></ul><ul><li>Better at processing orders than site creation </li></ul><ul><li>Not good for large catalogs </li></ul>
    168. 169. Microsoft SiteServer Commerce <ul><li>Still evolving </li></ul><ul><li>More of a development platform than a suite </li></ul><ul><li>Closely tied to IIS, SQL Server et al. </li></ul>
    169. 170. Shopping with MS Commerce
    170. 171. Recommendations <ul><li>If you are going to use any other MS apps </li></ul><ul><li>If you don’t mind doing lots of integration on your own </li></ul><ul><li>If you must stay on the cutting edge of MS products </li></ul><ul><li>Look at www.siteserver101.com for more tips </li></ul><ul><li>You’ll need at least one other piece ... </li></ul>
    171. 172. ClearCommerce.com Merchant Engine <ul><li>Complements Site Server for payments </li></ul><ul><li>Handles real-time credit card processing, fraud detection (via email) </li></ul><ul><li>Works with MS Order Pipeline, DCOM and ASP components </li></ul>
    172. 173. Commerce Server Specifics <ul><li>NT, fast Pentium with 256 M RAM essential </li></ul><ul><li>US$5000 </li></ul><ul><li>www.microsoft.com/commerce </li></ul>
    173. 174. Inex Commerce Court <ul><li>Two different versions: Lite ($595) and Pro ($995) </li></ul><ul><li>Runs on top of NT/IIS </li></ul><ul><li>Comes with catalog, publishing functions </li></ul><ul><li>Includes accounting links </li></ul>
    174. 175. IBM Net.Commerce
    175. 176. Included <ul><li>IBM’s Go Web Server </li></ul><ul><li>DB2 database </li></ul><ul><li>Shopping trolley system </li></ul><ul><li>Credit card verifier, eTill software </li></ul>
    176. 177. Several ways to setup your store <ul><li>Use nine-step wizard with populated catalog </li></ul><ul><li>Use wizard with empty catalog </li></ul><ul><li>Start from scratch </li></ul><ul><li>Import existing databases </li></ul>
    177. 178. Recommendations <ul><li>Great if you already use DB2 for inventories </li></ul><ul><li>Most security-conscious suite </li></ul><ul><li>More depth than iCat </li></ul><ul><li>Start with all IBM defaults to save time </li></ul>
    178. 179. Net.Commerce Specifics <ul><li>NT, fast Pentium with 256 M of RAM </li></ul><ul><li>AIX, 390, OS/400, Solaris </li></ul><ul><li>US$5000 Start, $20,000 Pro </li></ul><ul><li>www.internet.ibm.com/net.commerce </li></ul>
    179. 180. Latest features <ul><li>“ Intelligent Catalog” </li></ul><ul><li>Java-based wizards to setup and manage store </li></ul><ul><li>Recognizes shopping preferences and upsells </li></ul><ul><li>Improved SET payment server, ad tracking partnerships </li></ul><ul><li>Integration with Domino Merchant </li></ul>
    180. 181. Domino Merchant v2.0 <ul><li>Uses Notes server, but not Notes clients </li></ul><ul><li>Payments, catalogs, wizards galore </li></ul><ul><li>Easiest to setup, difficult to add products </li></ul><ul><li>A good entry-level product for now </li></ul><ul><li>Screencam demo </li></ul>
    181. 182. OpenMarket <ul><li>High end solution </li></ul><ul><li>Worldnet offers hosting of OM servers </li></ul><ul><li>Still needs customization! </li></ul>
    182. 183. Recommendations <ul><li>If you can afford it .... </li></ul><ul><li>Really the price covers lots of consulting time </li></ul><ul><li>High transactions and throughput needs </li></ul><ul><li>Use with Icoms.com front end service ($1000 + $100/month) </li></ul>
    183. 184. OpenMarket Specifics <ul><li>Various Unix </li></ul><ul><li>US$250,000 and up! </li></ul><ul><li>www.openmarket.com </li></ul>
    184. 185. Trends <ul><li>Suites will get better, but no one will really care </li></ul><ul><li>Rental options will continue to get cheaper and more functional </li></ul><ul><li>Web/database integration still difficult problem that suites are ignoring </li></ul><ul><li>Backoffice integration still difficult problem but getting better </li></ul>
    185. 186. Topic 5: Good and Bad Web Storefront Design
    186. 187. Sad State of Today’s eCommerce Marketplace <ul><li>Poor quality tools </li></ul><ul><li>Hard-to-find stores </li></ul><ul><li>Limited payment methods </li></ul><ul><li>Credit card snooping perceptions </li></ul><ul><li>Older browser versions can’t view latest sites </li></ul>
    187. 188. Case in Point: Buying a Bike Rack <ul><li>Item not carried: outdated catalog </li></ul><ul><li>Telesales not familiar with web </li></ul><ul><li>No cross-sell or substitutions online </li></ul><ul><li>Needed three phone calls to complete purchase </li></ul>
    188. 189. Let’s Learn From the “Real World” <ul><li>Compare what works for physical stores </li></ul><ul><li>Try to extend to the web </li></ul>
    189. 190. Critical Success Factors for Physical Storefronts <ul><li>Location </li></ul><ul><li>Branding </li></ul><ul><li>Good service </li></ul><ul><li>Good product selection </li></ul><ul><li>Proper pricing and margins </li></ul><ul><li>Traffic </li></ul>
    190. 191. First Problem: <ul><li>None of these translate on the ‘net! </li></ul>
    191. 192. Now Try to Agree on Definitions for Web Stores <ul><li>What determines a good location? </li></ul><ul><ul><li>Position on a search page </li></ul></ul><ul><ul><li>Nearness to popular destination </li></ul></ul><ul><ul><li>Ad on a popular server </li></ul></ul><ul><li>What determines branding? </li></ul><ul><ul><li>Memorable domain name </li></ul></ul><ul><ul><li>Popular search category destination </li></ul></ul>
    192. 193. An Example of bad location: Montana Meats <ul><li>www.imt.net/~lingerie/buffalo/buffalo.html </li></ul><ul><li>Can’t they afford their own domain name? </li></ul><ul><li>www.company.com/~anything is BAD NEWS! </li></ul>
    193. 194. Email Receipts Should Contain the Following Items <ul><li>Total price, including shipping </li></ul><ul><li>Your address and the store’s </li></ul><ul><li>Items ordered </li></ul><ul><li>Whether they are in stock or not </li></ul><ul><li>When they shipped </li></ul><ul><li>Bonus: order number and URL to view this info online </li></ul>
    194. 195. When to Send a Customer Email? <ul><li>To acknowledge the order was placed </li></ul><ul><li>To say items shipped (or not ) and money changes hands </li></ul>
    195. 196. Determining Traffic <ul><li>Hard to do -- is it hits, page views, registered users? </li></ul><ul><li>[HITS = How Idiots Track Success] </li></ul><ul><li>Hard to measure -- do you count gifs? Use log files? </li></ul><ul><li>No general agreement on any metrics! </li></ul>
    196. 197. Does a site actually have to sell something? <ul><li>Many actual eCommerce sites don’t do the complete transaction </li></ul><ul><li>Require faxes or telephone calls! </li></ul><ul><li>Some merely have catalogs </li></ul><ul><li>Examples: Singapore Power Authority www.spower.com.sg/readmeter.cgi?cmd=form </li></ul><ul><li>Cisco Connection Online </li></ul>
    197. 198. Principles of Good eCommerce <ul><li>Easy to find merchandize </li></ul><ul><li>Good service </li></ul><ul><li>Individual customization is key </li></ul><ul><li>Simple navigation </li></ul><ul><li>Make payments easy </li></ul><ul><li>Make buyer feel transaction is secure </li></ul>
    198. 199. AMP Connect <ul><li>Have customers in 100 countries </li></ul><ul><li>Speak many languages </li></ul><ul><li>Produce 400 catalogs covering 135,000 items </li></ul><ul><li>Mailings cost US$7MM/yr </li></ul><ul><li>Fax back cost US$800,000/yr </li></ul><ul><li>But you can’t buy anything directly! </li></ul>
    199. 200. Solution: “Step Searching” <ul><li>Saqqara.com software to enhance Oracle database </li></ul><ul><li>Provide user feedback as they do the query </li></ul><ul><li>Show how many matches in the database </li></ul><ul><li>Different mechanisms for searching: </li></ul><ul><ul><li>by part number </li></ul></ul><ul><ul><li>by alphabetical names </li></ul></ul><ul><ul><li>by part family </li></ul></ul><ul><ul><li>by picture even </li></ul></ul>
    200. 201. AMP
    201. 202. AMP Connect (con’t) <ul><li>And can set to list parts that are available in specific countries! </li></ul><ul><li>Updated daily with over 200 item changes </li></ul><ul><li>Detailed drawings saves time for customers to pick the right item </li></ul><ul><li>Saved AMP over US$5MM in production costs </li></ul><ul><li>Saved US$1MM in translation costs </li></ul>
    202. 203. Danish eShopper Survey (2/99) <ul><li>Why people shop on the web: http://www.useit.com/alertbox/990207.html </li></ul><ul><li>Convenience and ease of use are the main reasons people buy </li></ul><ul><li>After you have deliberately looked for information about a product or service, how often do you buy it? Almost always, 2%! </li></ul><ul><li>Only 5% of their visits to eCommerce sites are to buy! </li></ul>
    203. 204. First Principle of eCommerce: <ul><li>Make it easy to buy! </li></ul>
    204. 205. Amazon.com <ul><li>Services frequent readers with a variety of programs </li></ul><ul><ul><li>Editorial comments </li></ul></ul><ul><ul><li>If you liked this book, you’ll like... </li></ul></ul><ul><ul><li>Notification of new books by author, topic </li></ul></ul><ul><ul><li>Simplified “1 Click” ordering </li></ul></ul><ul><li>Uses simple pages and email </li></ul><ul><li>Associates program for commission kickbacks </li></ul><ul><li>Gift certificates via email </li></ul>
    205. 206. Use Affiliates Programs Wisely <ul><li>They bring traffic to your doorstep </li></ul><ul><li>Nice revenue sharing model </li></ul><ul><li>Lots of them to choose from to model your own on: </li></ul><ul><ul><li>AssociatePrograms.com </li></ul></ul><ul><ul><li>Refer-it.com </li></ul></ul>
    206. 207. Amazon vs Borders <ul><li>Cookies vs logins </li></ul><ul><li>www.borders.com/msprotect/ncommerce/;order/list?status=C </li></ul><ul><li>Who makes it easier to buy books? </li></ul>
    207. 208. Now Look at Hatfactory.com <ul><li>Easy to pay and track your purchases </li></ul><ul><li>Clean and effective use of graphics </li></ul><ul><li>Innovative use of cookies </li></ul><ul><li>Demo (with 2 browser windows) </li></ul>
    208. 209. Update your directories! <ul><li>This one is almost a year old </li></ul><ul><li>www.asiapage.com/alist.html#jewellery </li></ul>
    209. 210. Another Side of Service: Repeat Business <ul><li>Make the shopper feel part of the family </li></ul><ul><li>Shopping as entertainment (online auctions) </li></ul><ul><li>“Do what I mean” search function (Amazon again looks at common misspellings made in the previous 24 hours for book searches) </li></ul><ul><li>Periodic targeted email updates and reminders </li></ul>
    210. 211. Second Principle of eCommerce: <ul><li>Deliver solid service! </li></ul>
    211. 212. Dell positives <ul><li>Most notable site for computer buyers </li></ul><ul><li>Customize the features you want via a web form </li></ul><ul><li>Simplifies and personalizes the shopping experience </li></ul><ul><li>WYSIWYB (buy) </li></ul>
    212. 213. Dell problems <ul><li>Site is now very complex </li></ul><ul><li>Print ads contain “eValue” codes </li></ul><ul><li>Too many pages to get to actual PC configuration </li></ul>
    213. 214. Canadiantire.com <ul><li>eFlyer uses email notification along with web forms </li></ul><ul><li>Customize exactly what coupons and deals are sent to you </li></ul>
    214. 215. Third Principle of eCommerce: <ul><li>Individual customization is key </li></ul>
    215. 216. BMW Motors <ul><li>Example of what not to do </li></ul><ul><li>Use gratuitous graphics </li></ul><ul><li>Cheesy low-res videos </li></ul><ul><li>Toys, not tools </li></ul>
    216. 217. BMW
    217. 218. Compare with Subaru <ul><li>Find specific information about each car </li></ul><ul><li>Can price options to your particular needs </li></ul>
    218. 219. A better example: fishing licenses <ul><li>Simple, quick, and does the job with a minimum of clutter </li></ul><ul><li>www.permit.com </li></ul>
    219. 220. Fourth Principle of eCommerce: <ul><li>Make navigation simple! </li></ul><ul><li>Use small graphics, site maps, indexes </li></ul><ul><li>Avoid graphics just to display text </li></ul><ul><li>Avoid plug-ins, Jscripts to complete purchase process </li></ul><ul><li>Avoid link and button clutter, frames </li></ul>
    220. 221. Common mistakes with payments <ul><li>Provide too few or too many order confirmation pages </li></ul><ul><li>Confusing methods and misplaced buttons on order page </li></ul><ul><li>Make it hard for customers to buy things </li></ul><ul><li>Don’t make your customers read error screens </li></ul>
    221. 222. Fifth Principle of eCommerce : <ul><li>Make payments easy! </li></ul>
    222. 223. Making the Buyer Feel Secure: the Six Components of eCommerce Trust <ul><li>Seals of approval, logos of credit card co’s </li></ul><ul><li>Identifiable brand name </li></ul><ul><li>Ease of navigation </li></ul><ul><li>Order fulfillment easy to understand </li></ul><ul><li>Clear purpose and site presentation </li></ul><ul><li>Fast and simple technology </li></ul><ul><li>(Cheskin Research) </li></ul>
    223. 224. Perceptions of Credit Card Snooping Still Exist <ul><li>But are largely popularized by media, not consumers! </li></ul><ul><li>Internet fraud stories are still common from both buyer and seller sides </li></ul><ul><li>Just starting to see authentication services (such as Cybersource) ramp up </li></ul><ul><li>Trust will take a long time </li></ul>
    224. 225. Sixth Principle of eCommerce: <ul><li>Make the buyer feel secure! </li></ul>
    225. 226. Summary <ul><li>New web technologies being created at a furious pace </li></ul><ul><li>eCommerce still far from easy and obvious </li></ul><ul><li>Still lots of room for improvement in storefront design </li></ul>

    ×