Cisco Cisco Process Orchestrator 3.0 Guida Utente
1-9
Cisco Process Orchestrator User Guide
OL-30196-01
Chapter 1 Understanding Service-Oriented Orchestration and the Cisco Process Orchestrator
Service Definition Examples
Now, using Service-Oriented Orchestration:
1.
An external team provides an automation pack that defines a TelePresence target type, with:
–
Relationships defined for terminal, SNMP, and web service target types
–
Properties such as a phone number or escort name
–
Process actions for TelePresence systems
2.
The automation pack can add properties such as a location property to the built-in network device
target type.
target type.
3.
The customer installs the automation pack and configures TelePresence service instances by calling
a constructor process called Create.
a constructor process called Create.
4.
The process not only creates the TelePresence target, but also creates the terminal, SNMP, and web
service targets as well as the relationships that unify them into the model.
service targets as well as the relationships that unify them into the model.
5.
The end user can browse the target views or operations views and filter for targets with the
TelePresence type. When they select a type, they can see:
TelePresence type. When they select a type, they can see:
–
All of the available user-startable actions (processes).
–
All automation running against the TelePresence system. These results are filterable by a time
range or by a specific process.
range or by a specific process.
6.
When the end user runs a process action, internally the workflow traverses the relationship to find
the SSH, etc. target required by the action. The user sees this and other automation running against
the TelePresence system.
the SSH, etc. target required by the action. The user sees this and other automation running against
the TelePresence system.