Creating a List of URIs to RuleSet Mappings

After the ruleset is created, associate a domain with the ruleset using the Map URIs to RuleSets field. The following two entries are added by default to the Map URIs to RuleSets field:

• *://*.Sun.COM/portal/*|default_gateway_ruleset

  where sun.com is the install domain of the portal and /portal is the portal install context

• *|generic_ruleset

This means that for all pages from portal directory with the domain sun.com, the default_gateway_ruleset is applied. For all other pages, the generic ruleset is applied. The default_gateway_ruleset and the generic_ruleset are pre-packaged rulesets.

For all the content appearing on the standard Portal Desktop, the ruleset for the default_gateway_ruleset is used, irrespective of where the content is fetched from.

For example, assume that the standard Portal Desktop is configured to scrape the content from the URL yahoo.com. The Portal Server is in sesta.com. The ruleset for sesta.com is applied to the fetched content.

The domain for which you specify a ruleset must be listed in the Proxies for Domains and Subdomains list.

Using Wildcards Within the Syntax

You can map a fully qualified URI or a partial URI by using an asterisk in the ruleset.

For example, you could apply the java_index_page_ruleset to an index.html page as follows:

www.sun.com/java/index.html/java_index_page_ruleset

or you could apply all pages in the java directory to the java_directory_ruleset, as follows:

www.sun.com/java/* /java_directory_ruleset