Under Gateway Caching:
Using the Minimum Cache Time and Maximum Cache Time settings, specify the amount of time you want the portlet and gatewayed content to be cached. In the text box, type the number of seconds, minutes, hours, or days you want the portal to cache the content; then, in the drop-down list, click the appropriate period.
You should cache content for as long as possible, to lower the burden on your remote servers.
If the portlet content should not be cached, you can disable caching on the portal by setting both the minimum and maximum to 0 (also, disable error suppression, mentioned in step 2).
Note: Caching can also be controlled through the portlet code. For more information on caching, refer to the Oracle WebCenter Interaction Web Service Development Guide, which is located on the Oracle Technology Network at http://www.oracle.com/technology/documentation/bea.html.If you want to display cached content if an error occurs, rather than displaying an error message, select Suppress errors where possible (show cached content instead). This option is enabled (selected) by default.
Under Settings:
These settings are used primarily for existing Web applications that
are surfaced through the portal through a remote portlet.
Select Use hosted display mode on gateway pages if you want to display gatewayed content in the entire region between the portal header and footer. Otherwise, the content is displayed within the portlet that presents the gateway pages. This setting allows users to maintain their portal navigation and other features while working in the remote application.
(Recommended) Select Transform JavaScript files to run JavaScript files of a remote Web application through the portal transformer. This ensures that pages are displayed correctly and that portal navigation is not lost.
(Recommended) Select Transform CSS files to run CSS files of a remote Web application through the portal transformer. This ensures that pages are displayed correctly and that portal navigation is not lost.
Under Gateway URL Prefixes, you can allow users
access to remote content they would not normally be able to access, you
might need to gateway the content. Gatewayed content is downloaded from
the computer hosting the content to the portal.
Do not gateway content that is openly accessible over the Internet,
as this will unnecessarily burden your portal servers.
To add a prefix for which you want to gateway content, click
Add Gateway Prefix and type the prefix in the newly
displayed box. For example, if you enter http://myServer/ContentCrawler/
as the prefix, all content having a URL beginning with this prefix will
be gatewayed, and all other content will be left in its original location.
If you associated a remote server on
the Main Settings page, you can type a relative path (/myPortlet/) or
an absolute path (http://myServer/myPortlet/). If you enter an absolute
path, ignore the base URL.
To gateway everything on the remote server, type a period followed by a forward slash (./).
Note: Gateway URL prefixes must end with a forward slash (/).If you want the content in the portlet to refresh when a gatewayed link is clicked, in the Inline Refresh column, check the box next to the prefix.
To delete a prefix, select the prefix and click
.To select or clear all of the prefix check boxes, select or clear the box to the left of Prefix.