Configuring PQS

Removing SQL Triggers

Prior to 3.2, Milan required the following SQL triggers on all WorkSite databases in order to process updates to documents and workspaces.

• MHGROUP.DOCMASTER: DOCMASTER_to_InputQueue
• MHGROUP.PROJECT_ITEMS: PROJECT_ITEMS_to_InputQueue
• MHGROUP.PROJECTS: PROJECTS_to_InputQueue

However, with the addition of Policy Queue Service, these triggers are no longer necessary and should be uninstalled after upgrading from an earlier version of Milan.

To uninstall the SQL triggers:

1. Navigate to C:\Program Files\Prosperoware.Milan\scripts\ Policy_Service_WorkSite_DB_Script\.
2. Execute Disable_Policy_Triggers.sql against your WorkSite database.

Configuring PQS

1. Register C:\Program Files\Prosperoware.Milan\Prosperoware.Milan\bin\DMSCom.dll using regsvr32.exe.
2. If you would like to add or remove event types or change their priority, edit Prosperoware.Milan.Policy.Queue.exe.config file. See Configuring Event Types.
3. Navigate to C:\Program Files\Prosperoware.Milan\Service\SQL\ and open WorkSiteDbPreEnqueueCheck.sql in a text editor. This script executes on the WorkSite SQL database where the changed object (document or folder) exists and is called before Policy Queue Service queues up. You can optionally edit the script to apply custom business logic to exclude objects from being processed. For an object to be excluded from processing by Milan Policy Service, the script must return Boolean 0; otherwise, the script must return Boolean 1.
4. Open ~\Prosperoware.Milan\Service\SQL\MilanDbPreEnqueueCheck.sql to configure the SQL script. This script runs against the Milan database and is called before Policy Queue Service queues up. Optionally, objects can be excluded from the queue by adding custom logic to check against any table in the Milan database (including the Milan InputQueue table) to determine whether an object needs to be queued up. As with the previous script, for an object to be excluded from processing, the script must return Boolean 0; otherwise, the script must return Boolean 1. Additional information can be found in the Custom SQL article.
5. Save the file(s).
6. Start the Policy Queue Service.

Configuring Event Types

Policy Queue Service can be configured to listen for and assign a priority level to different types of events. The configuration file, Prosperoware.Milan.Policy.Queue.exe.config, can be found in C:\Program Files\Prosperoware.Milan\service\ and has the following default settings

<actionTypes>

<addtype="Insert"priority="Lowest" />

<addtype="Update"priority="Normal"/>

<addtype="Delete"priority="Highest"/>

<addtype="ProfileUpdate"priority="Normal" />

<addtype="FileUpdate"priority ="Lowest" />

<addtype="SecurityUpdate"priority="Highest"/>

<addtype="DocumentLink"priority="Lowest" />

<addtype="DocumentUnlink"priority="Highest" />

<addtype="ProjectUnlink"priority="Highest"/>

<addtype="NvpUpdate"priority="Normal" />

</actionTypes>

The default event types listed above should be sufficient for most Milan configurations. However, any of the available event types not already listed can be added and assigned one of five priority levels. To have Milan ignore an event type, remove the appropriate line from the file.

Priority Levels

The priority level determines the date, relative to the current day and time, that will be used when the PQS inserts entries into the InputQueue table for change events of a specific type. Because Milan processes items in the InputQueue table by date in ascending order, higher priority items are given earlier dates.

Priority Level	InputQueue Date
Lowest	7 days prior to current date
BelowNormal	1 day prior to current date
Normal	Current day and time
AboveNormal	1 day after current date
Highest	1 year after current date

Supported Event Types

PQS can listen for the following event types, which are listed in WorkSite's ChangeEvents table by the enum value.

Event	Enum	Occurs When
Insert	1	A document or folder is created
Update	2	A document is checked in
Delete	4	A document is deleted
Reset	8	N/A
ProfileUpdate	16	A document or folder profile is updated.
FileUpdate	32	The underlying document is changed, e.g. checking-in a document as an existing version.
SecurityUpdate	64	A document security ACL is updated.
DocumentLink	128	A document is added to a folder.
DocumentUnlink	512	A document is removed or moved from a folder.
ProjectUnlink	1024	A folder is removed from a workspace, tab or a folder.
NvpUpdate	2048	Folder metadata is updated.
ProjectLink	256	A folder is added to a workspace, tab, or folder.
DeclareRecord	4096	A document is declared as a record.
Undeclare Record	8192	A documents is undeclared as a record.