• Customer
servers must be Windows or Unix servers.
Beyond that, there are no special requirements
for these servers. The server may be a
file server (in which case the training
will be accessed via a file:/// URL from
a shared network folder) or a web server
(in which case the training will be accessed
via an http:// URL). The server need not
include streaming media software and need
not support Active Server Pages, CGI or
any other "server-side" technology.
• End
users are presumed to have
a persistent connection
to the Internet. If they
have a dial-on-demand connection,
they may be subjected to
frequent delays for dialup
each time the courseware
transmits data to the HCCS
server upon completion of
a module or part of a module.
• HCCS customers
must configure firewalls,
proxy servers and/or end
user systems to permit:
HTTP access to the HCCS
server on port 80 and/or
Secure access to the HCCS
server using SSL (https
over port 443).
• Streaming
media delivery from the
customer’s intranet
server (or, in the ASP model,
from the HCCS server); not
required for text-and-graphics
mode. Customer intranet
servers must be Windows
NT/2000/XP or Unix/Linux
servers. Mac and other operating
systems are not supported
for these servers.
• A
web (HTTPD) or file (shared
network folder) server may
be used.
• For
customers whose end users
use Netscape version 6 or
higher, use of a file server
is not an option. See the "Client
System Requirements" section
in the complete installation
guide for details.
• Streaming
media will be delivered
from the customer’s
server using HTTP streaming
(web server), or download/file-based
streaming (file server),
not using streaming media
server software such as
RealServer or Windows Media
Services.
|
