Deployment Channels serve as a virtual queuing system for updates that helps prevent constant disruptions to end-users. Rather than deploying updates at once upon release, OneSite Patch adds updates to the Deployment Channel queues and releases the patches at a scheduled installation time. This approach combines process terminations, notifications, and device reboots into a single cycle, reducing the impact and disruption to users.
Deployment Channel Processes are responsible for deploying patches to Business Units, and specifying the deployment schedule. When a patch is ready for deployment, it is queued and held until the next scheduled execution. At that point, the Deployment Channel Process activates, processes all queued patches, and deploys them to the appropriate Business Units.
Configuration options include classifying different patches and adding them to various Deployment Channels based on a desired execution schedule. For example, you can add critical updates to a Daily channel that deploys critical patches within 24 hours and add less critical updates to a monthly channel which deploys all queued updates on a chosen date every month. The scheduling and frequency are completely customizable. OneSite Patch includes multiple, preconfigured Deployment Channels. Administrators can modify existing configurations or create new Deployment Channels.
Channel Merging Rules use a designated Target Channel and a defined Merging Duration to govern the merge of patch deployments from multiple Deployment Channels. The purpose of this merger is to prevent multiple channels from executing at the same time. So, when a daily channel overlaps a weekly channel once per week and the weekly channel overlaps the monthly channel once every four or five weeks, Channel Merging Rules prevent multiple channels from executing at the same time.
You can create several Channel Merging Rules for a Deployment Channel to cover multiple potential scheduling issues. The Deployment Channel evaluates the rules according to the hierarchy, so place higher priority rules before lower priority rules in the Channel Merging Rule dialog. The Deployment Channel evaluates each rule and when one rule matches, evaluation stops. Then, all submitted patches in this Deployment Channel merge with the target channel specified.
Settings in a Deployment Channel template allow you to create a deployment that meets the needs of your organization. Deployment Channels require some settings, such as a designated channel process and a Deployment Wave, and several optional configurations, including Approvals, Notifications and Content Prestaging.
-
Hover over or select Deployment Channels in the left navigation menu of the Adaptiva OneSite Patch Dashboard, and then select Deployment Channels. This opens the table of existing Deployment Channel templates.
-
Create a New Folder for Objects in the Deployment Channels Menu.
-
Select to view the available templates.
-
Select the Name of an existing Deployment Channel template to open it.
-
Save the template with a new Name:
-
Move the new template to the folder you created, either now or when you complete your changes.
To add Deployment Process Settings to a Deployment Channel template:
Open a Deployment Channel template, and then scroll down to Deployment Process Settings in an open Deployment Channel template.
This opens the Deployment Process workspace.
-
Select + Add Schedules from the Deployment Process Settings workspace of an open Deployment Channel template.
-
Select one or more Schedule Names from the Add Schedules table, and then click Add Schedules on the lower-left corner of the dialog.
-
Select Save on the upper left to save your changes:
-
Select + Add Schedules from the Deployment Process Settings workspace of an open Deployment Channel template.
-
Select Show All to see the available processes, and the select the Process to use for this Deployment Channel.
-
Select Add Deployment Channel Process on the bottom left to return to the template.
Deployment Control settings in a Deployment Channel template allow you to choose whether to use this Deployment Channel to deploy patches to all approved Business Units or to add a Deployment Wave and restrict deployment to authorized Business Units only. For more information about Deployment Waves, see Deployment Waves.
To configure Deployment Control:
Open a Deployment Channel template, and then scroll down to the Deployment Control workspace.
The Deployment Control setting defaults to disabled, which allows deployment of patches using this Deployment Channel to all Business Units.
To enable Deployment Control:
-
Select the Restrict Patches to Deployment Wave toggle to enable using a Deployment Wave to manage deployments in this Deployment Channel.
-
Select Browse next to Add Deployment Wave.
-
Select a Deployment Wave, and then click on the bottom left of the dialog. To create a new Deployment Wave, see Open and Save a Deployment Wave Template.
-
Select Save on the upper left to save your changes:
Approval Chains define and manage the approvals required before the Deployment Channel deploys patches to Business Units. Including an Approval Chain in a Deployment Channel template requires selecting an existing Approval Chain and saving it in the Deployment Channel template. For more information about Approval Chains, see Using Approval Chains.
Add an Approval Chain to the Deployment Channel to request approval before deploying patches to Business Units. For more information about Approval Chains, see Using Approval Chains.
-
In a open Deployment Channel template scroll down to the Approval Chain workspace.
-
Select Browse next to Add Approval Chain. This opens the table of existing Approval Chains.
-
Select an Approval chain, and then click to return to the Deployment Channel template.
Notification settings in the Deployment Channel template include adding a Notification Chain and and Patch Notification Bots, as well as creating Notification Settings and Channel Merging Rules.
Notification Chain settings exist in the object templates for Patching Strategies, Deployment Channels, and Business Units.
-
Expand the Notifications box in an open object template to show the available configuration options.
-
Select Browse next to Notification Chain. This opens the Notifications Chain dialog.
-
Select Show All to see the available templates.
-
Select a Notification Chain from the table. To edit or create Notification Chains, see .
-
Continue editing the Notification settings or click to return to the template.
These values must match the corresponding values defined in the Notification Bots. Otherwise, the Notification Cycle does not send a notification.
Execution Schedules control when and how often a Notification Cycle sends notifications. Choose schedules based on when and how often receiving parties require notification.
-
Select + Create Notification Setting from the Notifications workspace of a object template.
-
Select +Add Schedules to display the Create Notification Setting dialog.
-
Select one or more Schedule Names from the Add Schedules table, and then click Add Schedules on the lower-left corner of the dialog.
-
Continue editing the notification settings or click to return to the template.
When enabled, sends notifications to the Roles shown in the Notification Chain associated with the Patching Strategy or Deployment Channel template. Defaults to disabled.
-
In the + Create Notification Setting dialog in the Patching Strategy or Deployment Channel template, decide whether to enable notifications:
-
Select the Notify Patching Strategy Chains toggle to enable or disable (default) whether the notification cycle sends notifications to the chains included in the strategy.
-
Select the Notify Business Unit Chains toggle to enable or disable (default) whether the notification cycle sends notifications to Business Unit chains included in the strategy.
-
-
Continue editing the Notifications settings or click to return to the template.
This setting names the Notification Cycle that processes the Notifications for the Patching Strategy or Deployment Channel. Notification Cycle workflows are customized for specific uses. Adaptiva does not provide sample Notification Cycle templates. These templates exist only if you create them for your environment.
Important
Contact Adaptiva Customer Support for assistance with Notification Cycle templates.
-
Select + Create Notification Setting from the Notifications box in the object template.
This opens the Create Notification Setting dialog.
-
Select Browse on the Add Workflow line. This opens the list of available workflows in OneSite.
-
Select your custom workflow from the list, and then click Add Workflow on the lower-left corner of the dialog.
-
Continue editing the Notification settings or click to return to the template.
Specifies the maximum length of time that the Notification Cycle Workflow runs before timing out. If set to all zeros (default) the workflow may run indefinitely. Choose this setting with care. If the notification times out before sending all notifications, the next cycle triggers the notifications again.
-
Select + Create Notification Setting the Notification box of the object template.
-
Next to Time Limit, set the Hours, Minutes, or Seconds that the Notification Cycle will run, or leave the setting default at 0 for each item to allow the workflow to run indefinitely.
-
Continue editing the Notification settings or click to return to the template.
Both Patching Strategies and Deployment Channel templates have an option to Add Patch Notification Bots.
-
Select + Add Patch Notification Bots from the Notifications box in the object template.
This opens the Add Patch Notification Bots dialog.
-
Select Show All to list all available Patch Notification Bots or click any Filtered by: folder to see the Bots associated with that filter.
-
Choose one or more Notification Bots to set requirements for this template. To create more Notification Bots, see Creating Notification Bots.
-
Select Add Patch Notification Bots on the bottom left of the dialog to return to the starting template settings for Notifications.
Channel Merging Rules merge patch deployments from multiple Deployment Channels when deployment schedules from two or more channels overlap. Settings here include adding a Deployment Channel to serve as a Target Channel and setting the timing for Merge Duration. See Understanding Channel Merging Rules for more information.
-
Select Browse next to Add Deployment Channel, and then select a Deployment Channel.
-
Select + Create Channel Merging Rule from the Notification box of a Deployment Channel template.
-
Select Add Deployment Channel at the bottom left to return to the Channel Merging Rule template.
-
Set the Merging Duration to the number of hours, minutes, or seconds before this Deployment Channel executes.
The Content Prestaging feature enables OneSite Patch to provide deployment content to devices ahead of the scheduled deployment, either pushing content to a location or allowing a client to pull content. Prestaging content makes the content available on the device locally when the deployment time arrives. This reduces the deployment time and minimizes the chances of missing service windows or having devices going offline before a content download finishes.
Use this procedure to add or change Content Prestaging Settings in Patching Strategy, Business Unit, or Deployment Channel templates.
-
Expand the Notifications box in an open object template, and then scroll down to the Content Prestaging Settings.
-
Expand the Content Prestaging Settings box to view the available settings.
Client Content Pull defaults to Not Enabled. To enable pull settings, complete the following steps in the Content Prestaging Settings of a Patching Strategy, Business Unit, or Deployment Channel template:
-
Select the arrow to the right of Client Content Pull to expand the menu of available options.
-
Select the option you need for the object template you are using. For definitions of push options, see Defining Content Prestaging Settings.
-
Select Save on the upper left to save your changes:
Server Content Push defaults to Not Enabled. To enable push settings, complete the following steps in the Content Prestaging Settings of a Patching Strategy, Business Unit, or Deployment Channel template, complete the following steps:
-
Select the arrow to the right of Server Content Push to expand the menu of available options.
-
Select the option you need for the object template you are using. For definitions of push options, see Defining Content Prestaging Settings.
-
Select Save on the upper left to save your changes:
Customer Extension Data is an advanced feature of OneSite Patch. The Customer Extension Data fields allow advanced users to specify different key/value pairs for use in customized Patching Strategies, Deployment Chains, or Business Units when necessary to achieve different results.
Customer Extension Data fields relate directly to fields in a customized template. If you do not have customized templates with key/value pairs you can modify, you do not need to configure or use this feature.
If you want to create customized templates that use key/value pairs for some settings, contact Adaptiva Customer Support.
Deployment channel processes collect patch approvals, and then execute according to the schedule defined in the Deployment Channel. The logic in the Channel Process defines how to roll out patches to Business Units (one at a time or following the deployment waves, and so on).
If you want to create your own Channel Processes, enter a support ticket, and request help from Adaptiva Customer Support. Customer Support will help you understand the nuances of Channel Processes and assist with creating templates that support your requirements.
Comments
0 comments
Article is closed for comments.