3.1.4.12 Signal

Web Services Management Protocol Extensions for Windows Vista MUST support the Signal operation, using the following Action URIs.

 http://schemas.microsoft.com/wbem/wsman/1/windows/shell/Signal http://schemas.microsoft.com/wbem/wsman/1/windows/shell/SignalResponse
            

The set of resource URIs on which Web Services Management Protocol Extensions for Windows Vista MUST support the Signal operation is defined in the following table, and where relevant, the Xml Schema Definition (XSD) type for the data that is passed as part of the request or response is referenced.

Resource URI	Input data type	Output data type
http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd	rsp:Signal	rsp:SignalResponse

The Signal operation is used to control the Shell processor. It can be sent either asynchronously or synchronously. In the Text-based Command Shell scenario, a signal can be sent to a specific command, or in the Custom Remote Shell scenario, to the Shell itself. The Signal request message MUST be of the general form, with the only difference between the two scenarios being the value of the Resource URI. The Signal message format is as follows.

 <s:Envelope ...>
   <s:Header ...>
     <wsman:ResourceURI>
         Resource URI
     </wsman:ResourceURI>
     <wsman:SelectorSet>
        <wsman:Selector Name="ShellID">
              ...shell GUID...
        </wsman:Selector>
     </wsman:SelectorSet>
       ...other WS-Addressing & WS-Management headers...
   </s:Header>
   <s:Body ...>
     <rsp:Signal ...>
         ...Value defined by the Signal data type...
     </rsp:Signal>
   </s:Body>
 </s:Envelope>
            

The value of Resource URI will be different for the Text-based Command Shell and the Custom Remote Shell scenarios.

In case of the Text-based Command Shell, the value of Resource URI MUST be as follows. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/cmd

An example of Resource URI for Custom Remote Shell scenario is as follows. http://schemas.microsoft.com/wbem/wsman/1/windows/shell/CustomShell

Also, the CommandId attribute MUST only be used in a Text-based Command Shell scenario, and MUST NOT be applicable in a Custom Remote Shell scenario.

Note The value defined by the Signal data type is specified in Section 2.2.4.38.

If the control code of the Signal request (section 2.2.4.38) is http://schemas.microsoft.com/wbem/wsman/1/windows/shell/signal/Terminate, the Shell processor MUST decrement the server-side counter for MaxConcurrentOperationsPerUser.<118>

Upon successful processing of a Signal request message, a processor MUST return a SignalResponse message. The Signal response message MUST be of the following general form. The SignalResponse message format is as follows.

 <s:Envelope ...>
   <s:Header ...>
     <wsman:SelectorSet>
        <wsman:Selector Name="ShellID">
              ...shell GUID...
        </wsman:Selector>
     </wsman:SelectorSet>
       ...other WS-Addressing & WS-Management headers...
   </s:Header>
   <s:Body ...>
     <rsp:SignalResponse ...>
         ...Value defined by the SignalResponse data type...
     </rsp:SignalResponse>
   </s:Body>
 </s:Envelope>