Gatewaying Imported Content
When users click a link to an imported document, they can
either be directed to the actual location of the source document or
the content can be gatewayed, and the user will be redirected to a
URL (generated
from the settings in your portal configuration file) that, in turn,
displays the
document. Gatewaying content allows users to view documents they might
not otherwise be able to
view, either due to security on the source repository or firewall
restrictions. You configure gateways settings on the Main Settings
page of the Content Source Editor.
- Open the Content Source Editor by creating a new web content
source or editing an existing one.
The Main Settings page opens.
- Under URL Type, specify what happens
when users follow document links:
- If you want to direct users to the actual location of the
document, choose Does
not use the Gateway to open documents. Be warned, however,
that with this option,
even users with access to this content source's documents will not
be able to open
the documents if the documents are not publicly available and the
users are not connected to your network.
- If you want to redirect users to a URL (generated by the settings
in your
portal configuration file) that, in turn, displays the document, choose Uses the
gateway to open documents.
Note:
- If you want your users to be able to view documents even when
they are not connected
to your network, you should choose this option.
- If the associated content web service supports content upload
(specified
on the Advanced Settings page of the Content Web Service Editor),
you must use the gateway or content uploads will
fail.
By default web content sources do not gateway content, whereas
remote content sources do.
