Cisco Cisco Process Orchestrator 3.0 User Guide

Adapters are one of the extensibility mechanisms in the Process Orchestrator platform, and are only 
written by members of the Process Orchestrator product development team. The development team uses 
adapters to extend Process Orchestrator functionality to integrate with devices, environments, 
applications, or tools without undergoing core modification. 

Automation packs are the primary means of extending integrations in the field. Automation packs are 
prepackaged collections of process definitions, target types, variables, categories, targets, target groups, 
and other configurations needed to define a set of automated IT processes. Automation packs allow:

Cisco or its partners to ship best practice automation to customers. 

Customers to get productive quickly, and to shift automation across systems, such as from a 
development system to a test system to production. 

Customers to export their own processes and share with each other in the community.

The backup of process definitions and other product configuration.

Automation packs:

Can be exported from one Process Orchestrator system and imported into another. 

Can ship separately from product releases.

Are versioned and dependencies are recorded. Versions and dependencies are checked during import 
to ensure that the system will work after the import. For example, if your personal automation pack 
calls a process in “Sample Document A” automation pack v1.3, then you cannot import your 
automation pack into a system that has installed “Sample Document A” v1.2.

http://www.amqp.org/

).