58、PowerShell Workflows and Transactions: A Comprehensive Guide-优快云博客

本文链接：https://blog.youkuaiyun.com/vscode5coder/article/details/154477855

PowerShell Workflows and Transactions: A Comprehensive Guide

1. Changing Default Values in a Workflow

In PowerShell workflows, if you want to change the default values, you can use the Set-PSWorkflowData activity. However, be aware that this changes the default for the rest of the workflow. A good practice is to save the original value before making the change and restore it afterward.

$PSComputerName = "SomeOtherServer"
workflow Invoke-ChangesComputerTarget
{
    $previousComputerName = $PSComputerName
    Set-PSWorkflowData -PSComputerName OtherServer
    Get-Process -Name PowerShell
    Set-PSWorkflowData -PSComputerName $previousComputerName
}

2. Workflows Requiring Human Intervention

2.1 Problem

Long - running workflows may need human intervention to continue.

2.2 Solution

Send an email to the administrative contact to signal the need for human interaction and then call the Suspend - Workflow command. You can also use a file as a communication mechanism.

workflow Invoke-SuspendWorkflow
{
    param($MailCredential)
    "Processing Step 1"
    $gotSomeError = $true
    Checkpoint-Workflow
    if($gotSomeError)
    {
        $to = "admin@example.com"
        $from = "workflows@example.com"
        $smtpServer = "smtp.example.com"
        $inputPath = "c:\Workflows\$ParentJobId.input.txt"
        Send-MailMessage -To $to -From $from -Subject "Workflow ID $ParentJobId requires intervention" -Body ("Workflow #$ParentJobId has detected an error and needs intervention. Supply required input in $inputPath and resume job #$ParentJobId.") -SmtpServer $smtpServer -Credential $MailCredential -UseSSL -PSComputerName $null
        Suspend-Workflow
        $response = Get-Content -Path $inputPath -PSComputerName $null
        Checkpoint-Workflow
        "123 times $response is: $(123 * $response)"
    }
}

2.3 Steps for the Administrator

Obtain the mail credential:

$MailCredential = Get-Credential

Start the workflow:

Invoke-SuspendWorkflow -MailCredential $MailCredential

After receiving the email, provide input:

Set-Content -Path c:\Workflows\34.input.txt -Value 321

Resume the job:

$j = resume-job -id 34
$j | Receive-Job -Wait

2.4 Security Consideration

If you use the Get-Content cmdlet to retrieve input from the administrator, secure the access controls on the file path. Otherwise, an untrusted user may provide malicious input.

3. Adding Raw XAML to a Workflow

3.1 Problem

You want to include a segment of literal XAML in a script - based workflow.

3.2 Solution

Use the Invoke-Expression command with the -Language XAML parameter.

workflow Invoke-InlineXaml
{
    Invoke-Expression -Language XAML -Command '    <WriteLine>["Hello, World"]</WriteLine>'
}

3.3 Viewing the Compiled XAML

You can use the XamlDefinition property to see how PowerShell converts the script into XAML:

Get-Command Invoke-InlineXaml | Foreach-Object XamlDefinition

4. Referencing Custom Activities in a Workflow

4.1 Problem

You want to reference custom activities written for Windows Workflow Foundation.

4.2 Solution

Use the -Assembly parameter of the #requires statement to reference an assembly containing custom workflow activities and then invoke the activity like a command.

workflow Invoke-WorkflowActivity
{
    #requires -Assembly CustomActivityDll
    CustomActivity -Text "Hello World"
}

4.3 Three Ways to Include Activity DLLs

Method	Description
Relative path	If you specify a relative path (e.g., `#requires -Assembly CustomActivityDll` ), PowerShell loads the activity assembly from the root directory of the module defining the workflow.
Absolute path	If you specify an absolute path (e.g., `#requires -Assembly c:\Workflows\CustomActivityDll` ), PowerShell loads the activity assembly from that path.
Strong name	If you specify the assembly’s strong name, PowerShell looks in the system - wide GAC for that assembly.

4.4 Invoking Generic Activities

For generic activities, place the type argument within square brackets:

workflow Invoke-GenericActivity
{
    $result = PowerShellValue[string] -Expression "'Hello world'"
    $result
}

5. Debugging or Troubleshooting a Workflow

5.1 Authoring - Time Debugging

During development, since workflows run as background jobs, interactive debugging is not supported. Use trace statements with Write - Output to check variable values and execution branches.

workflow Invoke-DebugWorkflow
{
    $a = 10
    $b = 20
    Write-Output "Current value of A is: $a"
    "All available variables:"
    InlineScript { dir variable: }
}

5.2 Runtime Debugging

Using the job object : If the workflow terminates with an error, access the Reason property of the JobStateInfo property. If there are errors, access the Error collection.
Execution tracing : Review the workflow’s Progress output to trace its execution.

$j = Invoke-TestWorkflow -AsJob
$j.ChildJobs[0].Progress

Advanced diagnosis : Use the PSDiagnostics module.

Enable-PSWSManCombinedTrace
Invoke-TestWorkflow
Disable-PSWSManCombinedTrace
$r = Get-WinEvent -Path $pshome\Traces\PSTrace.etl -Oldest
$r | Where-Object ProviderName -eq Microsoft-Windows-PowerShell | Foreach-Object Message

5.3 Performance Counters

Use the Get - Counter cmdlet to view performance counters related to PowerShell workflows.

Get-Counter -ListSet "PowerShell Workflow" | Foreach Paths
Get-Counter "\PowerShell Workflow(*)\# of running workflow jobs"

6. Using PowerShell Activities in a Traditional Windows Workflow Application

6.1 Problem

You have a traditional Windows Workflow Foundation application and want to use PowerShell’s cmdlets as activities.

6.2 Solution

Add a reference to Microsoft.PowerShell.Workflow.ServiceCore and the appropriate Microsoft.PowerShell.Activities assembly, and then invoke the PowerShell activity like any other Windows Workflow Foundation activity.

6.3 PowerShell Activity Assemblies

Microsoft.PowerShell.Activities
Microsoft.PowerShell.Core.Activities
Microsoft.PowerShell.Diagnostics.Activities
Microsoft.PowerShell.Management.Activities
Microsoft.PowerShell.Security.Activities
Microsoft.WSMan.Management.Activities
Microsoft.PowerShell.Workflow.ServiceCore

6.4 Finding the Full Path of an Assembly in the GAC

$assembly = [Reflection.Assembly]::LoadWithPartialName("Microsoft.PowerShell.Management.Activities")
$assembly.Location
$assembly.Location | clip

6.5 Code Generation

You can use the Microsoft.PowerShell.Activities.ActivityGenerator class to generate code for exposing a command as an activity.

[Microsoft.PowerShell.Activities.ActivityGenerator]::GenerateFromName("Get-Process", "MyCompany.MyProduct.Activities")

7. Transactions in PowerShell

7.1 Introduction

Transactions in PowerShell provide four main guarantees:
- Isolation : Commands inside the transaction do not impact the system for non - participating observers.
- Atomicity : Either all changes in a transaction take effect or none do.
- Consistency : Errors during a transaction are corrected to maintain system consistency.
- Durability : Once a transaction is completed, changes are permanent.

7.2 Starting a Transaction

To start a transaction, use the Start - Transaction cmdlet. To use a cmdlet that supports transactions, specify the -UseTransaction parameter.

Set-Location HKCU:
Start-Transaction
mkdir TempKey -UseTransaction
New-Item TempKey\TempKey2 -UseTransaction

The following mermaid flowchart shows the process of a workflow requiring human intervention:

graph TD;
    A[Start Workflow] --> B{Error Detected?};
    B -- Yes --> C[Send Email Notification];
    C --> D[Suspend Workflow];
    D --> E[Administrator Provides Input];
    E --> F[Resume Workflow];
    F --> G[Use Input to Recover];
    B -- No --> H[Continue Workflow];

In summary, PowerShell workflows and transactions offer powerful capabilities for system management. Workflows can handle complex tasks with efficiency, and transactions ensure data integrity and system consistency. By following the techniques and practices described above, you can effectively develop, debug, and manage PowerShell workflows and transactions.

8. Comparing Workflow Techniques

8.1 Table of Workflow Feature Comparison

Feature	Method	Advantages	Disadvantages
Changing Default Values	`Set-PSWorkflowData`	Allows dynamic modification of default values within a workflow	Changes are permanent for the remainder of the workflow, may require saving and restoring original values
Human Intervention	`Suspend-Workflow` and email	Enables long - running workflows to pause and wait for human input	Requires proper security measures for input retrieval, additional administrative steps
Adding XAML	`Invoke-Expression -Language XAML`	Allows direct inclusion of XAML in a workflow	Error messages from the Windows Workflow Foundation engine can be obscure, less error - detection support from PowerShell
Referencing Custom Activities	`#requires -Assembly`	Enables use of custom activities from Windows Workflow Foundation	Different ways of including DLLs may cause confusion, need to handle generic activities properly
Debugging	Trace statements, Progress output, ETW	Can diagnose workflow behavior at different stages	Advanced diagnosis using ETW requires additional steps and tools
Using in Traditional Workflow Apps	Referencing PowerShell activity assemblies	Allows use of PowerShell cmdlets in traditional Windows Workflow Foundation applications	Need to find full assembly paths for Visual Studio Workflow Designer

8.2 Flowchart for Debugging a Workflow

graph TD;
    A[Start Debugging] --> B{Authoring - Time?};
    B -- Yes --> C[Use Trace Statements];
    C --> D[Check Variable Values and Execution Branches];
    B -- No --> E{Runtime?};
    E -- Yes --> F{Error Occurred?};
    F -- Yes --> G[Check JobStateInfo.Reason and Error Collection];
    F -- No --> H[Review Progress Output];
    E -- No --> I[Advanced Diagnosis with ETW];
    I --> J[Enable and Disable Tracing];
    J --> K[Get WinEvents from PSTrace.etl];
    K --> L[Filter and Analyze Messages];

9. Best Practices for PowerShell Workflows and Transactions

9.1 Workflow Best Practices

Use Checkpoints : Incorporate Checkpoint - Workflow statements at appropriate places in long - running workflows. This allows the workflow to resume from a known state in case of interruption.

workflow LongRunningWorkflow
{
    Checkpoint-Workflow
    # Long - running operations
    Checkpoint-Workflow
}

Limit Custom Activity Use : Only use custom activities when necessary. PowerShell activities can handle most common tasks, and custom activities may introduce complexity.
Secure Input Retrieval : When a workflow requires human input, ensure that the input mechanism is secure. Use proper access controls on files or other communication channels.

9.2 Transaction Best Practices

Be Explicit with -UseTransaction : Always specify the -UseTransaction parameter when using a cmdlet that supports transactions. This ensures that the cmdlet participates in the transaction as intended.
Test Transactions : Before applying transactions in a production environment, thoroughly test them in a development or test environment. This helps identify and fix any issues related to transaction isolation, atomicity, consistency, and durability.

10. Real - World Use Cases

10.1 System Configuration Management

PowerShell workflows can be used to manage system configurations across multiple servers. For example, a workflow can be created to install software, configure services, and update settings on a group of servers simultaneously.

workflow ServerConfigurationWorkflow
{
    param($ServerList)
    foreach - parallel ($server in $ServerList)
    {
        InlineScript
        {
            # Install software on the server
            Install - Software - Server $USING:server
            # Configure services
            Configure - Services - Server $USING:server
        } - PSComputername $server
    }
}

10.2 Database Operations

Transactions in PowerShell can be used to perform complex database operations. For instance, a money transfer between two bank accounts can be implemented as a transaction to ensure data integrity.

Start-Transaction
try
{
    # Subtract money from account 1
    Update - AccountBalance - AccountId 1 - Amount - 100 - UseTransaction
    # Add money to account 2
    Update - AccountBalance - AccountId 2 - Amount 100 - UseTransaction
    Complete - Transaction
}
catch
{
    Undo - Transaction
}

11. Future Considerations

11.1 Potential Improvements in Workflow Tools

In the future, we may see more advanced debugging tools for PowerShell workflows. These tools could provide better interactive debugging capabilities, similar to those available for PowerShell scripts.

11.2 Expansion of Transaction Support

PowerShell may expand transaction support to more providers and cmdlets. This would allow for even more comprehensive system management using transactions.

In conclusion, PowerShell workflows and transactions are essential components for efficient and reliable system management. By understanding the various techniques, best practices, and real - world use cases, you can leverage these features to build robust and scalable solutions. Whether you are a system administrator or a developer, mastering PowerShell workflows and transactions will enhance your ability to manage complex systems effectively.