Defines the execution order of the applications installed on a computer running Office Communications Server.
The following syntax is simplified from Managed Object Format (MOF) code and includes all inherited properties. Properties are listed in alphabetic order, not MOF order.
This class does not define any methods.
The MSFT_SIPApplicationPriorityList class has the following properties.
This class gets and sets information at the following level(s): WMI.
Only one instance of this class can be present.
The priority list is populated as applications are registered and their corresponding instances are created. As each application is registered, its GUID is added to the end of the list. Because applications on a server execute in the order in which they appear on the list, they should be installed in the order in which you want them to run.
The execution order should be chosen based on the nature of the applications. For example, an application that logs calls probably should execute before an application that looks up user endpoints because, even if no endpoints exist for a user, an administrator might still want to log the call as part of monitoring SIP traffic.
When a response is received, the applications execute in reverse order, beginning with the last application on the list.
You can change the order of execution by reordering the GUIDs in the InstanceIdList array, but you cannot add or remove an application from the list. To add an application, you must register it with Office Communications Server. To remove an application, you must delete its MSFT_SIPApplicationSetting instance.
Instances of this class support the following interface methods:
Provider::EnumerateInstances(); Provider::GetObject(); Provider::PutInstance();
Where PutInstance() supports the following flag(s):
WBEM_FLAG_CREATE_ONLY WBEM_FLAG_UPDATE_ONLY WBEM_FLAG_CREATE_OR_UPDATE
Server: Installed on computers serving the following role(s): Access Edge Server, Front End Server, Proxy Server.Namespace: Defined in \root\cimv2.