1. In the Portal menu, navigate to Portal Management.
2. In the left navigation panel, click Manage Servers.
3. Select the primary Replay Server.
   Note: You can configure replay rules only on the primary Replay Server, which provides rules to all secondary servers.
4. Click Rules in the toolbar.
   Note: This option is available only for the primary Replay Server.

   Use the following format for the domain name:

   
   www.<domain_name>.com

5. To load the properties from the rule into the appropriate text boxes for editing, click the Load link.
   Note: Saving a loaded rule replaces it.

   When you enter URLs for replay rules, protocol identifiers such as http:// or https:// are not needed. You can specify the protocol to use for all replay rules or allow the Portal to resolve.

   Port identifiers such as :8080 and :443, are not applicable and must not be entered.

6. You can select the Protocol in use from the drop-down.

   Set this value to Auto so that replay server detects the appropriate protocol to use.

7. to ignore specific URLs during replay.
   URLs matching the parameters that are specified here are not displayed during replay.
8. You can configure the Replay Server to highlight only the URLs that match the parameters that are specified.

   The URL can include the wildcard character (*) to represent a pattern of URLs, such as /home/*.

9. You can add a host to track and map the port for the selected host.
   • To add a host to track, enter the host name in the Host text box and click Set.
   • To map a port for the selected host, enter the port to map and then enter the port to which it is mapped and click Add.

   The host name is used instead of the host pulled from the domain of the session. Since the host is used for the <base> to indicate the source of the content, this value can be used to remap the content in the session to a site other than the original site For example, if the original site is obscured by proxies, this setting can be used to remap to a static, available resource. It can also be used to map to an available server within the proxy from which images and other content can be loaded.

10. You can modify content in the response by using simple search-and-replace.
    Special regular expression characters (such as ( or )) must be escaped by using a backslash. For example:

    
    \(

1. Add a new XML node named DomainWhitelistURLPattern within the ReplayServerProfile node.
   Note: Do not add the new XML node inside a HostProfile.
2. Apply the following syntax rules

   <DomainWhitelistURLPattern urlpattern=".*\.foo\.com"/>

   urlpattern is a regular expression used to match allowed domain names.

   More than one DomainWhitelistURLPattern rule may be defined if needed.

To enable the whitelist rules, set WhiteListEnable to 1 in the Replay Server global options.

In Whitelist mode, you can configure URL patterns that are permitted to contact the origin server, and all other URLs are blocked.

When you enable Whitelist mode for the Replay Server, you can specify the set of URLs that are permitted to contact the origin server. By using regular expressions, you can specify a set of URL patterns that are permitted to query the origin server during replay. For the listed URL or URLs, the Replay Server references the data that is stored on the origin server during replay.

The URLs that do not match the whitelist are effectively blacklisted, which can be used to protect the source application from triggering web analytics metrics and Tealeaf data counts.

• Special regular expression characters (such as ( or )) must be escaped by using a backslash. For example:

  
  \(

• If the pattern value is empty, the default pattern is used. This pattern causes Replay Server to contact the origin server for image and static content, which is not stored as part of the session data.

  
  \.(jpg|jpeg|gif|css|js)$