Cisco Cisco Process Orchestrator 3.1 User Guide
13-1
Cisco Process Orchestrator 3.1 User Guide
C H A P T E R
13
Using Adapters
The topics in this chapter describe the adapters available for Cisco Process Orchestrator, any special
information about installing and configuring the adapters, and the activities provided by each adapter.
You can use these adapters in a workflow.
information about installing and configuring the adapters, and the activities provided by each adapter.
You can use these adapters in a workflow.
Many of the Process Orchestrator tasks that are required to run an activity are common to all or most
adapters. For example:
adapters. For example:
Configuring Adapters
For specific information about installing and configuring an adapter, see the topics in this chapter. For
general information about adapters, see
general information about adapters, see
.
Creating Targets
Before you can create or run processes in your Process Orchestrator environment, you must create the
targets on which the processes will run. Targets define specific environments where certain processes,
activities, or triggers will run.
targets on which the processes will run. Targets define specific environments where certain processes,
activities, or triggers will run.
You can define a target once and then reuse it in multiple processes. To define a target, see
Creating Runtime User Accounts
When creating targets, a runtime user account must be specified to be used to connect to the target. The runtime user account stores the information about the user security context for the target.
You can create the runtime user accounts during the process of creating the targets or prior to creating the targets. To create a runtime user account, see
Creating Triggers
Triggers are events and conditions in the system that determine how or when the process will be
executed. Using a trigger, for example, you can subscribe to an existing queue and fire an event trigger
based on the message that is generated. See
executed. Using a trigger, for example, you can subscribe to an existing queue and fire an event trigger
based on the message that is generated. See