For example, suppose that for the user agent Jakarta, a visit to any page other than /MyXMLService.aspx indicates that the user agent is a search engine while visits to /MyXMLService.aspx indicate that the user agent is not a robot. By defining this path to be skipped during normal user agent parsing, you can specify the appropriate traffic type value for the non-robot exception (TrafficType=XMLServiceConsumer).

1. Log in to the Portal as an administrator.
2. From the Portal menu, navigate to TMS.
3. Click the WorldView tab.
4. From the Servers drop-down, select the server hosting the capture pipeline where the Reference session agent is deployed.
5. Click the Transport Service node.
6. Select Transport Service configuration.
7. In the Config Actions tab, click View/Edit (Raw).
8. The raw version of the TealeafCaptureSocket.cfg file is displayed.
   You can choose to copy and paste this content into your favorite text editor for editing.
9. In the file, locate the [TLTRef] section.
10. Look for the following configuration settings in the [TLTRef] section. If they are not present, insert them.

    
    PathsToSkip=^MyPath*$;^YourPath*$
    TrafficTypeForSkippedPaths=XMLService
    BrowserForSkippedPaths=XMLServiceConsumer
    

    Setting	Description
    PathsToSkip	Enter a list of paths, delimited by semi-colons (;). You can enter regular expressions. For example, you can enter a value of ^MyPath*$ to match all paths that contain the substring MyPath.
    TrafficTypeForSkippedPaths	For paths that match a value that is specified in PathsToSkip, this setting identifies the value to insert into the Traffic Type object.
    BrowserForSkippedPaths	For paths that match a value that is specified in PathsToSkip, this setting identifies the value to insert into the Browser Type object.

11. To save your changes, click Save.
12. To push the change to other Canisters in your environment, click Add Tasks and Submit.