How to Load a Patch Stream

Last updated on July 7, 2021.

Last Reviewed and Approved on PENDING REVIEW

Introduction

This document provides step-by-step instructions for loading a patch stream into RPS.

Prerequites

User must have permissions to the CDN folder.
User must be part of the ContentCreators Active Directory group.
Patches must have been previously created. Please visit How to Create an RPS Patch for detailed instructions.

Note

Users may see "patch" and "package" used interchangeably in the log outputs during this process.

How to Create a Patch Stream Using PowerShell Cmdlets

Note

If patches have already been copied to the node, proceed to step 3.

On an external media device (e.g. USB thumb drive), create a new directory.
Zip patch files and and move them to the newly created directory.
Log into the node where you will be creating the patch stream.
Open a PowerShell window as an Administrator.
Change your directory to the RPS ContentStore using the following command:
```
cd C:\ContentStore
```
Import the RPS API module using the following command:
```
Import-Module C:\ContentStore\Modules\Rps-Api
```

Use the New-RpsPatchStream cmdlet to create the patch stream. There are two required parameters and two optional parameters for use with the New-RPSPatchStream cmdlet:

The following parameters are required:

Parameter Name	Type	Description
Name	string	Names the new patch stream (max length = 255). The name can be arbitrary and is valid only to the user.
Path	string	Specifies current location of patches (e.g. on the external media)

The following parameters are optional:

Parameter Name	Type	Description
PatchExtensions	List of String	Used to list file extensions of patches that will be searched for in the location specified in the Path parameter. The files must be valid ZIP archives.
Recurse	Switch	Used to search all sub-directories of path parameter for patches.

The following is an example of how these parameters can be used with the New-RPSPatchStream cmdlet to create a patch stream:

New-RpsPatchStream -Name MyPatchStream1 -Path E:\Patches -PatchExtensions ".zip"

In this example, the user has created a patch stream named "MyPatchStream1" containing patches from the E:\Patches\ directory.

The following actions will occur once the New-RPSPatchStream command has been successfully executed:

a. A patch stream item will be added to the Configuration Management Database (CMDB).

b. The patches will be added to the CMDB, one for each patch found in the location specified by the path parameter.

c. The patches will be copied into the CDN directory, enabling them to be replicated across the CDN.

Note
The initial state of a patch stream is "Pending" and therefore no assignments between patches and targets will be made.

d. The patch stream will be approved via PowerShell or the Web UI. For more information on how to approve and reject patch streams, please visit How to Approve and Reject Patch Streams.