Cisco Cisco Process Orchestrator 3.0 Guida Utente

Automation packs are collections of configuration definitions of process definitions, target types, 
variables, categories, target groups, and other system elements needed to define a set of automated IT 
processes (see 

). The out-of-the-box automation 

definitions in automation packs allow customers to get productive quickly (see 

). 

Automation packs allow users with the appropriate rights to export their own processes and share them 
with other customers in the community. Automation pack authors have control over how end users can 
override their automation definitions. The purpose of this control is to improve the ease of:

Consuming future upgrades. Customers naturally expect that some amount of work is involved in 
upgrades. During an upgrade, all properties customized by users will be preserved. If a workflow is 
customized, it will be preserved. Process Orchestrator does not merge workflows. If any part of the 
workflow has been customized, all of the workflow will be left intact (no updates will be made to a 
customized workflow).

Consuming patches and hotfixes for content. Customers do not expect these to be difficult or 
dangerous to consume. 

An automation pack is a single file (package) that contains:

Configuration (processes, categories, knowledge base articles, and so on)

An optional custom configuration user interface that presents a wizard used to configure essential 
elements of the automation pack. For example, a configuration UI for SAP performance 
management might ask the user importing the automation pack to define the SAP systems that 
Process Orchestrator will manage and provide credentials to reach those systems.

Report Definition files. These files are extracted into a directory during automation pack import, and 

can then be imported by the customer into their chosen reporting system

External management system configuration files such as those to define alerts in a health monitoring 
application such as Microsoft System Center Operations Manager or HP OpenView SPI Modules.

Binaries that the customer installs in an external system that the automation pack might require. For 
example, in Cisco Intelligent Automation for Cloud, Process Orchestrator provides the elements that 
can be imported into Cloud Portal to order cloud services.