Transcript No Slide Title

Deploying And Managing
®
®
Microsoft FrontPage 98Based Web Sites On
Internet Information Server
Objectives





Explain extended functionality provided
by Server Extensions
Provide a clear picture of the
Extensions architecture
Understand choices for deployment
of FrontPage and Extensions
Explain how to install, configure,
and manage the Extensions on Internet
Information Server
Outline security mechanism and clear
up security misunderstandings
Agenda






Server Extensions Tasks
Server Extensions Architecture
Deploying
Security
Site Management
Integration with
Internet Information Server
technologies
Server Extensions Tasks





“Impedance match” between
client and server
Platform-independent protocol
for authoring, management, and
administrative operations
Multiuser and remote authoring
Convenient packaging for
server-side functionality
Not required for 95% Browsetime functionality
Server Extensions Tasks

Authoring and managing






Create and save pages
File management: move, copy, del
Maintain hyperlink integrity
Copying and publishing Webs
Automatic Navigation Bars
and Themes
Metadata maintenance


Hyperlink map
Create date, Created by, custom
Server Extensions Tasks

Administering - Security


Browse-time Web functionality




Users and Permissions
Form Handlers: e-mail, results file
Search Form
Discussion Web
95% of browse-time functionality
does not require Server Extensions!
FrontPage Architecture
FrontPage
Extensions
Explorer
Web server
HTTP
Editor




IIS
PWS
Apache
Netscape
Author.dll
ISAPI
or
CGI
Admin.dll
Shtml.dll
Deployment Issues



Authoring scenarios
Content structure
Installation
Web Authoring And
Publishing Scenarios

Single author


Local authoring
Remote publishing to Web server
 Server Extensions NOT
installed: FTP
 Server Extensions INSTALLED
Local Authoring And Testing

Extensions on local machine



Local authoring and Web
management
Local testing for browse-time
components
Optional: Lightweight FrontPagebased personal Web in workgroup
Web Authoring - Local
Author and
Manage
Test & Preview
HTTP
HTTP
Personal
Web Server
Extensions
Hard Disk
Local Workstation
Browser
Optional: Workgroup
users browse your
lightweight personal Web
Browser
HTTP
Local Authoring,
Remote Publishing

Extensions on local machine



Local authoring
Local FrontPage component testing
Publish to remote Web Server



Works best with Server Extensions
Extensions not required on remote
Web Server: Publish via FTP
No Browse-time FrontPage
components without Extensions
Local Authoring,
Remote Publishing

Extensions on remote Web server


Smart publishing receptor
Additional 5% enhanced
browse-time functionality
 Save-results form to file and e-mail
 Search
 Hit counter
 Discussion group
Remote Publishing & Authoring
Author
Publish
via
viaHTTP
FTP
Incremental
Authoring &
Publishing
Intranet or WPP
Web Server
Internet
Information Server
Extensions
Personal
Web Server
Extensions
Hard Disk
Hard Disk
Local Workstation
Server Machine
Browse
Browser
FULL
(NO browsebrowsetime
timefunctionality)
functionality
Web Authoring And
Publishing Scenarios

Team authoring


Author local, publish to
shared server
 Extensions not required but
recommended
Author against shared server
 Extensions on shared server
 No publishing - live authoring
Team Authoring

Extensions recommended on
shared server





Live authoring and management over
network or Internet
Workgroup functionality: Conflicts, Todo
Browse-time FrontPage components
Version control with Visual SourceSafe™
Extensions on workstation


Useful for offline authoring and testing
Not required
Shared Server Model
Workstations FrontPage Clients
Production
Intranet or ISP
Web Server
Internet
Information Server
HTTP
Extensions
(optional)
Authoring or Staging
Server (IIS)
Extensions
Hard Disk
Hard Disk
Optional: Propagate to
production server
Server Machine
Server Machine
Team Authoring

Options:



Staging server - prop to
production server
 Validation
 Security
Version Control Check-in/Check-out
Review process
Deploying:
Content Structure



FrontPage-based Web concept
Web usage scenarios and
storage layout
Implementation on
Internet Information Server
FrontPage-Based Webs



All HTML, images, and other files
for a Web site
Subfolders available
Scope of FrontPage:





Authoring
File and link management
Security
Publishing
FrontPage component
functionality
Usage Scenarios: WWW

Per-user subwebs (a la AOL, GeoCities)



Virtual server per user



www.isp.com/~george
Large number hosted on one machine
www.billg.com
Usually several to many per machine
Dedicated server per organization

www.arcadiabay.com
WWW Folder Structure
Hard Drive Storage
Web Structure
C:\InetPub\wwwroot
default.htm
Root Web: http://www.ISP.com
\scripts
signup.asp
\ArcadiaBay
default.htm
\products
product1.htm
Virtual Server
Arcadia Bay WWW Presence:
http://www.arcadiabay.com
\Contoso
default.htm
Virtual Server
Contoso Pharmaceuticals Web:
http://www.contoso.com
Usage Scenarios: Intranet

Server per project/department



http://arcadianet
Root area maintained by
Webmasters
Project/Department subwebs



arcadianet/HR
arcadianet/Finance
Subwebs for workgroups divide
authoring responsibility
and permissions
Intranet Folder Structure
Hard Drive Storage
Web Structure
C:\InetPub\wwwroot
default.htm
companylogo.gif
\scripts
search.asp
Root Web:
http://arcadianet/
•Index of departments
•Global scripts
C:\InetPub\wwwroot\hr
default.htm
\policies
hrpolicy.doc
Human Resources subweb:
http://arcadianet/HR
C:\InetPub\wwwroot\finweb
default.htm
Finance Product Group:
http://arcadianet/Finweb
Root Webs And Subwebs

Root Webs


Subwebs


One per virtual server
Many subwebs per virtual server
No functional difference for user
browsing or authoring Web
Root Web


One root Web per virtual server
Content folder defined by the
virtual root



C:\InetPub\wwwroot
Other arbitrary locations for
multihosted servers
Access via
http://www.server.com
subwebs

Stored as a sub-folder of root Web
content folder

Access as http://server/subwebname
C:\InetPub\wwwroot
default.htm
Root Web: http://arcadianet
C:\InetPub\wwwroot\sales
default.htm
\promotions
Arcadia Bay Sales subweb:
http://arcadianet/sales
Subwebs




Logically excluded from
root Web authoring space
Nested subwebs:
Extensions do
not allow
Can inherit permissions
from root Web
Number of subwebs:
No hard-coded limit
Deployment: Installation





Get the extensions
Basic installation
Configure servers
Upgrade issues
Finishing details
Get The Extensions

FrontPage client product


Windows NT® 4.0 Option Pack,
Internet Information Server 4.0


Client setup installs
Extensions locally
Integrated Extensions setup
Windows® and UNIX Extensions
setup kits

http://microsoft.com/frontpage/wpp/
Basic Installation

Get the FrontPage 98 Server
Extensions Resource Kit (SERK)




At minimum read Security and
Installation sections
Run Installer to copy Extensions
to HD
Create virtual servers
Configure each virtual server
Configuring Servers
With Extensions


Setup automatically configures
single-hosted servers
If multihosted, or adding new
virtual server, use:



FrontPage Server Administrator
Remote HTML Administration Forms
Create subwebs with
FrontPage Explorer
Upgrade Issues

When required



Compatibility




New version of extensions for
each client version
Intermediate patches and updates
New client with old extensions
New extensions with old client
Setup automatically upgrades
May reparse content
FrontPage 98 Server
Extensions Improvements




No memory leaks
Quicker to install
New remote HTML
Administration Forms
Better scalability and robustness

Open Web not a limitation
FrontPage 98 Scalability

No hard-coded subweb or file limits


Possible scalability limits



May hit Internet Information Server limits
Recalculate hyperlinks - linear scaling
Saving change to shared border on manypaged Web (~ 2 pages / second)
Break up content into different subwebs
Finishing Details






Web-specific options in
FRONTPG.INI
Visual SourceSafe
integration for Web
E-mail transport
Import existing documents
HTML Administration Forms
Security
Agenda






Server Extensions Tasks
Server Extensions Architecture
Deploying
Security
Site Management
Integration with
Internet Information Server
technologies
Security



FrontPage Security Model
Implementation with
Internet Information Server
Security Management Strategies

Custom ACLs
FrontPage Security Model

Uses Web server security system


Permissions groups




No homegrown FrontPage security
mechanism
Users: Browse Web content
Authors: Manipulate files and directories
Administrators: Create new subwebs,
change permissions
Permissions are cumulative
FrontPage And
Internet Information Server
Security Process

Internet Information Server authenticates user



Internet Information Server Impersonates
Windows NT user account
FP sends HTTP request to one of three DLLs:





Basic, Windows NT Challenge/Response, DPA
Administer: admin.dll
Author: author.dll
Browse: shtml.dll
Internet Information Server grants/denies
access based on ACL of target DLL file
FP reads/writes content files based on request
FrontPage ACL Management

FP manages FP DLL ACLs



FP manages content ACLs




Maintain admin/author/browse
Protect FP configuration info: _vti_*
Conservative settings for max security
Authors/Administrators get read, write,
delete (RWD)
Browsers get read (R)
See SERK for specific list
Permissions Management
Strategies

Permissions managed by FrontPage



FP Admins use Tools | Permissions
command
FP controls content ACLs
Best Practices


Separate subwebs  finer control
Use Windows NT Groups for
easiest maintenance
Permissions Management
Strategies

Staging server/Production server



FrontPage manages staging
server security
Production server uses
custom settings
Manual/Custom management
Custom ACLs


Use FP one time to add
Windows NT groups for
Admins/Authors/Browsers
Disable FrontPage security



FP Tools/Permissions overwrites
custom ACLs
No FP Administrators
Manage ACLs with Windows Shell,
cacls.exe
Custom ACL Cautions



Windows shell replaces ACLs,
not merge
Use Recursive Replace with care
Do not overwrite key ACLs on



FrontPage DLLs
_vti_* directories
Understand Internet Information
Server Anonymous account
vs. EVERYONE
Custom ACL Downsides

Can easily get to state where:



Security worse than default
FrontPage configuration
FrontPage doesn’t work
Recovery steps:


Use Check and Fix command
Uninstall Server Extensions, Fix
ACLs, then reinstall
Agenda






Server Extensions Tasks
Server Extensions Architecture
Deploying
Security
Site Management
Integration with
Internet Information Server
technologies
FrontPage Server
Extensions Related Tools

FrontPage Server Administrator


Command line server administrator


fpsrvwin.exe
fpsrvadm.exe
Remote administration HTML forms
Maintenance Of
Server Extensions




“Check & Fix Web” feature in
Server Administrator
Reinstall Server Extensions to
correct corrupted Extensions
Enable/disable authoring
Files to know

frontpg.ini - various FrontPage settings
Recalcing Webs

Recalcing Web reparses each page
to repair or rebuild:


Normally not necessary, unless
working outside of FrontPage


Link map, WAIS index, Navigation
Bars, FrontPage Components,
Shared Borders, etc.
File System, FTP
Linear scaling, possibly high
server load
Agenda






Server Extensions Tasks
Server Extensions Architecture
Deploying
Security
Site Management
Integration with
Internet Information Server
technologies
Active Server Pages

FrontPage 98 Server Extensions
don’t corrupt ASP


Opening ASP in Editor may corrupt


Safe to store ASP documents
Partial HTML tags, unclosed HTML tags
Workarounds


Encapsulate ASP in WebBot®
Component meta-tags
DTC, WebBot Component wrapper
Other Technologies

Index Server



Possible search engines
 Index Server if installed
 Built-in WAIS
Builds IDQ files automatically
Forms to SMTP e-mail
Version Control With
Microsoft Visual SourceSafe
FrontPage 98
Visual InterDev
FrontPage 97
HTTP
LAN
connection
VSS
repository
OLE Automation
IIS
Extensions
Web staging
server
The FrontPage 98 SERK

Definitive source for in-depth Server
Extensions info for Windows and UNIX



Where:



Security, Installation, and Administration
Troubleshooting, Config Settings, more
FrontPage 98 CD in \SERK directory
http://microsoft.com/frontpage/wpp/serk
Read Security and Installation sections
Other FrontPage Resources

Server Extensions Web site


FrontPage SDK


http://microsoft.com/frontpage/wpp
FrontPage 98 CD in \SDK directory
Newsgroups