SEOTrance
SiteMap
ebusiness Architecture
ebusiness Concepts
ebusiness Solutions
ebusiness Technology
ecommerce Fundamentals
ecommerce Implementation
Site Infrastructure
«Prev
Ecommerce Implementation
Site Implementation
Planning Ecommerce Site
Business Model Revenue Strategies
ecommerce Products Services
Customer Expectations
Story Board Development
Mapping Business Concerns
Outsourcing Ecommerce Providers
Site Infrastructure
Web Server Elements
Webserver Hardware Requirements
Webserver Software
Aliases Virtual Directories
Virtual Servers
DNS Servers
Default Documents Directory
Website Development SW
Support Database SW
Configure HW Increased Performance
Multi Machine Configuration
Legacy- Integration
Middleware Solutions
Web Server Conclusion
ecommerce Security
Security Risks
Ecommerces Security Measures
Operating System Security
ecommerce System Security
Application Security
Encryption Methods Types
Application Encryption Methods
Networking Security Conclusion
Security Infrastructure
Payment Methods
Credit Card Payment Methods
Digital Cash
Digital Certificates
Public Key Infrastructure
Digital Certificate Types
Public Private CA
Certificate Issues
SSL Protocol Transaction
Set Protocol
Commerce Certificates-
Aliases and virtual directories
1) Suppose that you want your web server to present a collection of documents called doc1.html and doc2.html. They are located in the systemroot\home\sales\docs directory.
2) Make this folder accessible to users under the URL https://www.anycompany.com/sales/doc1.html.
3) If you do not make these folders accessible, the web servers would attempt to satisfy the web browser's request by looking for the directory \Inetpub\wwwroot\sales\docs\.
4) Using a virtual directory solution, the doc1.html and doc2.html files reside in the systemroot\home\sales\docs directory and are accessed by www.yoursite/sales/docs1.html
5) Using a virtual directory solution, the doc1.html and doc2.html files now reside in the systemroot\home\sales\docs directory and are accessed by the same URL