My team and I talking and we may want to consider job classes as being the way to provide support teams.
I can see few advantages to using job class:
#1 Job Class is not tied to security, and is available as filter criteria (meaning you can isolate to apps, groups, departments etc...Tidal keeps your filters in mind so if you only want to see a certain set of jobs that works (support, dev ops, app development, those that care about x App etc.)
#2 Job events can be associated with jobs and could be a way to server multiple needs for varying groups (each can have their own defines alerts, etc). They can also be applied before or after individual jobs events
#3 if you add a job class at a high level … all Child Jobs/Groups inherit class so it natually add new jobs in that group/s to any filters, etc
This document explains the logic to develop Tidal Enterprise
Orchestrator workflow to automate the process of creating vCenter
Resource Pool* vSphere Power CLI must be installed either on the TEO
server or vCenter* vMA can also be used to achieve the same...
IntorductionCisco Process Orcehstrator (CPO) ships with the webservices
adapter that can be used to make Web Service API call to REST or SOAP
based applications. Before a sample workflow to make SOAP API calls
using CPO, lets understand some of the fundam...