WebPulse is a service provided by Blue Coat that receives URL identification requests and responds with the IDs of the category, application, and/or operation associated with the URL. When WebPulse is enabled, you will have the ability to:
- create classes based on specific URL categories, and PacketShaper will then classify web traffic that corresponds to each of these categories into the appropriate class
- auto-discover category classes (you must first create an "all categories" class and enable class discovery)
- create classes based on specific web applications and operations
- auto-discover web application classes
The WebPulse URL database is either in the cloud or stored locally on the appliance. Note that the option for a locally stored database is available only on PS-S500 appliances using WebPulse Express (see setup webpulse express).
|To perform this task from PolicyCenter, you must first select a unit or draft configuration draft in the Configurations window. Then select the Setup tab from the right pane of this window, and proceed to step 2 of the procedure below.|
To configure WebPulse:
1. Click the Setup tab.
3. For WebPulse, select on.
4. (Optional) Select which categories you want to auto-discover.
5. Click apply changes.
- By default, PacketShaper auto-discovers category classes after it sees one flow for the category in a one-minute time interval. This threshold is user configurable via the URL Categories system variable.
See Adjust System Variables.
- If you have secured the PacketShaper's outside interface, the WebPulse feature requires that you add WebPulse servers to the exception list. In addition to the servers listed on PacketShaper Port and URL Usage , be sure to add the fastest WebPulse service points (use the setup webpulse show service CLI command to find the IP addresses).
See Specify Security Settings.
- Although you can create URL category and web application classes when WebPulse is disabled, there won't be any classification into these classes until you enable WebPulse.
- If WebPulse is disabled, PacketShaper does not look up URLs in the WebPulse cloud, in the URL cache, or in the WebPulse Express local database.