Using a Stand-alone Web server

SiteScope has a built-in Web server to serve SiteScope Web pages. SiteScope can interface directly with this server rather than invoking a CGI script, making retrieval times quicker, and eliminating the need for configuration changes to your stand-alone or production Web server. There may be times, however, when it is necessary to serve SiteScope's pages through your own Web server, such as when you have a firewall set up and want SiteScope's pages to use that firewall.

"If you decide to configure your SiteScope server with a separate, standalone Web server you must first install SiteScope with the default embedded Web server settings to be able to configure SiteScope to use a standalone Web server. After installing SiteScope, you will need to set up two virtual server paths for the SiteScope documents. The following are instructions for doing this using either an IIS, Apache, or Netscape or other server.

Using SiteScope with an IIS Server

Connect to SiteScope through the SiteScope server (default installation), and choose the General Preferences link on the SiteScope main page.
Under the section Built-in Web Server remove anything in the SiteScope Port box, (normally 8888) and select the Create Static HTML check box.
Save these changes. This shuts down SiteScope's internal Web server and tells SiteScope to create HTML files that can be accessed using a separate Web server. The browser will normally return an error message when refreshed at this point.
From the Windows Start menu, open the Internet Service Manager and open up the IIS properties. Choose the Directories option.
In the IIS directory view or using the IIS wizard, add a new virtual directory configured to point to wherever you have SiteScope installed as follows:

Virtual Directory name or Alias: SiteScope
Physical Directory: path:\SiteScope where path represents the physical device path where SiteScope is installed.
Select Read as the only access permission
Create the virtual directory
In the IIS directory view, open the new SiteScope directory and select the cgi subdirectory. Change the properties of this subdirectory as follows :

Where applicable, verify that only the "Read", "Log visits", and "Index this resource" options are checked. Otherwise deselect all other Access Permissions and Content Controls.
Select the Execute Scripts option or set the Execute Permissions to "Scripts and Executables".
Save the changes

Now, you will be able to access SiteScope at:

http://your.machine/SiteScope/htdocs/SiteScope.html

Restricting Access To SiteScope Using an IIS Server

IIS uses NT file permissions to restrict access. By changing the NT file permissions, you can control who can access the SiteScope Web pages:

Open the Directory Permissions window for the SiteScope directory.
Select the SiteScope directory
Choose Properties from the File Menu
Choose the Security tab
Choose the Permissions button
Check Replace Permissions on Subdirectories
Check Replace Permission on Exiting Files

To restrict access to SiteScope, complete the following instructions:

Remove the Everyone group
Add the sitescope administrator account with Full Control permissions
If you want to allow read only access to some users, add these accounts with Read permission
Choose OK to save the permissions

The url for SiteScope admin access will be:

http://yourServerName/SiteScope/htdocs/SiteScope.html

The url for read only SiteScope access will be:

http://yourServerName/SiteScope/userhtml/SiteScope.html

Note: If you are using Internet Explorer, one confusing "feature" is that IE automatically logs into Web pages using your current login account, without showing you a password dialog. For example, if you are logged into the TestUser account and go to an IIS Web server that restricts access to a page, IE will invisibly log you in using TestUser. To always get the login dialog, disable the "Windows NT Challenge/Response" check box in the authentication options of IIS.

Index

Using SiteScope with an Apache Server

For the Apache Web server, make the following changes to conf/httpd.conf substituting the path of the SiteScope installation directory in the place of <SiteScope install path>.

Add the following lines to the httpd.conf file:

	AddHandler cgi-script .exe
	Alias /SiteScope <SiteScope install path>/SiteScope
	ScriptAlias /SiteScope/cgi <SiteScope install path>/SiteScope/cgi

Change the DocumentRoot to reference <SiteScope install path>.

Modify the directory sections to include this:

	<Directory />
		Options FollowSymLinks ExecCGI
		AllowOverride None
	</Directory>
	<Directory <SiteScope install path>>
		Options Indexes FollowSymLinks ExecCGI
		AllowOverride None
	</Directory>

Save the changes to the httpd.conf file
Restart the Apache server

The url for SiteScope admin access will be:

http://yourServerName/SiteScope/htdocs/SiteScope.html

The url for read only SiteScope access will be:

http://yourServerName/SiteScope/userhtml/SiteScope.html

Index

Using SiteScope with Netscape or Other Server

Determine how virtual directories are added for your server.
Add a virtual directory that maps /SiteScope to wherever you installed SiteScope.

For example, if SiteScope is installed in a folder named Applications located on your C drive, you would map /SiteScope to c:/Applications/SiteScope.
Add a virtual cgi directory for /SiteScope/cgi as follows:
- for "url prefix", use /SitesScope/cgi
- for "shell cgi directory", use C:/SiteScope/cgi (or use the path where you installed SiteScope) press OK
Save and apply your changes.

Note: it may be necessary to restart your server to apply these changes.

The url for SiteScope admin access will be:

http://yourServerName/SiteScope/htdocs/SiteScope.html

The url for read only SiteScope access will be:

http://yourServerName/SiteScope/userhtml/SiteScope.html

Index