User Guide

Chapter 3 Leveraging Existing Content
27
n File Transfer (FTP): These documents are served from any standard FTP
server. The engine and end users need anonymous access to these
resources. The file transfer (FTP) protocol looks like this:
ftp://someserver.com/SomeDocument.doc
n Network File (FILE): These documents are served from a shared network
resource such as a shared drive. The engine and end users need access to
these shared network resources. The engine may not have access to
shared resources on your network, depending on your security settings.
You can change the access in the RoboEngine Configuration Manager
Projects panel. Click the Network Authentication button and enter a
user name, password, and domain name that has, at least, Read
permissions on the system containing the external documents. The
network file protocol looks like this:
file://ServerName/SomeDocument.doc
Notes:
§ When you link to a document through the Hypertext (HTTP), File
Transfer (FTP), or Network File (FILE) protocol, the document is NOT
placed in the project Baggage Folder.
§ If you want to view an external document linked to your Web site
when you view content from the engine, you need to check that you
have the correct access. For more information see, “Viewing
external documents from the engine.”
Enabling the engine to scan external documents
If you have external files on a different engine than your project and these files
are linked to your project through the table of contents or a topic using the
Network File (FILE) protocol, you should enable the engine to scan the external
documents.
Note: This procedure is not necessary if you use the Hypertext (HTTP) or File
Transfer (FTP) protocol.
To enable the engine to scan external documents linked through the
network file (FILE) protocol (on a Windows NT 4 machine):
1 From the Start menu, select Programs - Administrative Tools - User
Manager for Domains.
2 From the Policies menu, select User Rights.
3 Select the check box next to Show Advanced User Rights.