All policy structure is configured around a flow chart of logical steps that are processed when a selected event occurs. The evaluation flow is determined by the outcome of decision type policy items and actions. This can result in policy reaching more then one outcome when the evaluation is processed.
All policies in WinGate are based on a selected event taking place during its operation. Individual components and services register the events that can occur during their operations with the Events system in WinGate. Certain WinGate modules allow you to create events which will also be registered with the Events system (e.g. Notification events). The Policy system can use all of these registered events to provide you with a suitable range of events that you can base a policy on.
When a component or service registers an event, it also makes available any data that may be associated with the event. You can use this event data to make decisions and construct actions that that policy will evaluate and perform whenever the selected event occurs. The event data made available is dependent on the source and type of event that is chosen for the policy.
These are systems in WinGate that have been specifically designed to respond to the occurrence of registered events in WinGate. The event processors obtain the list of all events registered with the Events system by WinGate service and components. The Events system will inform all event processors whenever any of these events take place so they can respond appropriately. The Policy system in WinGate is an event processor.
This is the WinGate component or service that registers the selected event with the Events system.
The Events system in WinGate is responsible for the management of events that are registered by WinGate services and components when they are loaded. The Events system notifies the Policy system, and any other event processors when the events occur, so they can trigger policy or process the event if they have been configured to do so.
WinGate components and services register all the different types of events that will happen during the course of their operations. These event types can be used by the Policy system to create policies around.
Flow arrows indicate the path that policy evaluation will take as part of the policy flow chart.
The structure of every policy in WinGate is defined by using a flow chart of steps that should be processed when the selected event occurs. Each step in the flow chart uses a policy item to define whether a decision (based on available event data) should be made, or an action that should be performed during policy processing. When a policy evaluates a decision, the outcome will determine the path the policy processing flow chart should take. As such a policy could could have paths that lead to more then one result. In some instances, a policy may only perform an action when an event occurs and so will only have one path to follow.
WinGate allows you to create lists, counters, Boolean values, and string values that are global to all WinGate services and components. You can have a policy check the value of event data against a global list, or have it check the value of a global Boolean value when required. The global data supplied by the lists, counters, Boolean and string values can be accessed regardless of what type of policy you are configuring.
Lua script is a powerful scripting language that you can use to create decisions the policy should evaluate based on available event data.
Depending on its purpose, each policy item has an output connector so that it can be joined in the flow of any policy evaluation. For example, decision type policy items will usually have two output connectors indicating that, depending on the outcome of the decision (Yes or No) two alternate paths can be followed.
This is the user interface used to construct, and edit each policy in WinGate. It provides a range of configurable policy items that you can use to graphically construct the flow chart of steps that the policy will perform when the selected event occurs.
When you configure a policy in the policy editor, there are a range of items you can use to create each evaluation step in the policy flow chart. These items can include:
The very first item in a policy flow chart should be the event the policy is based on. The chosen event is made available on the Items tab of the policy editor so it can be included in the flow chart. Once it is connected to the flow chart then the policy will be triggered whenever the event occurs (as the event has been assigned to the policy). If the event item is not connected and part of the policy flow chart then the policy will not be active (as the event is no longer assigned to the policy).
These policy items force the policy to evaluate the value of selected event data to determine a Yes/No path the policy will take for further evaluation on the policy flow chart.
These policy items allow you to have the policy perform an action as part of the policy evaluation. This can include stopping and starting services, sending an email, and starting other applications.
Result policy items can be used to provide suitable outcome or conclusion to a policy. At the end of each evaluation path a result such as allow, reject, disconnect, redirect etc can be used to bring the policy to a suitable outcome.
The Policy Panel located in the Control Panel of the WinGate Management console, lists all of the current policies that have been created. It shows a brief preview of the policy flow chart structure and any design notes about the policy. You can open a policy editor from the Policy Panel to add a new policy or edit an existing one.
The Policy system controls and manages all policy related activity in WinGate. As an event processor, the Policy system queries the Events system to discover what events have been registered by various WinGate components and services. It uses the list of discovered events for you to create policies around. When an event occurs in a WinGate service or component, the Events system notifies the Policy system which in turn triggers any policy that the event may have been assigned to.
The Symbol Browser is used to access and select relevant event data objects that have been registered by modules and components in the WinGate Schema. Some policy items allow you to you select and use the methods of these objects (from the Symbol Browser) in order to access event data when constructing policy.
This is the space provided in the policy editor to graphically construct the flow chart of policy evaluation. You can drag on to the worksheet all of the relevant policy items (such as decisions and actions) that will be processed by the policy when the event occurs. Once configured, policy items on the worksheet can be connected by flow arrows to arrange the sequence and logic by which they will be evaluated.
©2012 Qbik New Zealand Limited
no comments yet...
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
You can create a new account or reset your password at forum.wingate.com.