Tidal Enterprise Orchestrator: Starting Processes

Available Languages

Updated:July 26, 2011
Document ID:113146

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document provides information to help understand the two ways to start processes in Tidal Enterprise Orchestrator (TEO), either via triggers or Ad-Hoc.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the Tidal Enterprise Orchestrator 2.1 or later.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

How to Start Processes

TEO is an event driven product.

Ad-Hoc

TEO can be started Ad-Hoc if you right click on any process and select Start Process. This is a one time run and can be seen in the operations tab, pending the process has archival selected in the options tab. The started by field shows who started the process.

Triggers

TEO can also be started via triggers. These triggers include SAP CCMS alerts, Cisco UCS Faults, Inbound Emails, Remedy Incident changes, SAP Server Down, SCOM 2007 Alerts, SNMP Traps, Internal TEO Variables being updated, Windows Events, VMWare Events, Schedules (run off of calendars), and create/expiration/changes in an internal TEO Task. TEO Tasks include alerts, incidents, approval request, guided operations, input requests, and reviews.

What is the difference?

The major difference between these two processes is human interaction and one time running. Trigger-based processes can run one time or many times, depending on the way a trigger is configured. In order to properly set up the triggers or learn more about them, consult the TEO documentation or contact Technical Support.

Related Information

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products