Cisco Cisco Tidal Enterprise Adapters for Agentless Scheduling Data Sheet
Data Sheet
© 2010 Cisco and/or its affiliates. All rights reserv ed. This document is Cisco Public Information.
Page 2 of 3
Where Agentless Scheduling Makes Sense
Using Cisco Tidal adapters for agentless scheduling makes sense for targets that have critical performance controls,
w here the execution of an external agent may cause process degradation and job failures, or w here strict change
management controls ―lock dow n‖ a target image, preventing attempts to install and execute softw are on that
management controls ―lock dow n‖ a target image, preventing attempts to install and execute softw are on that
machine.
Highly secured environments may also restrict administration or scheduling access to specific machines. In addition,
as more data centers embrace virtualized and cloud computing environments, agentless job management may be the
only w ay to connect to and interconnect these decoupled resources.
Those types of environments and business needs are w ell served by agentless scheduling.
Features and Benefits
Cisco Tidal ag
entless scheduling capabilities extend an organization’s reach to remote Windows machines, as w ell
as Linux, UNIX, and any other SSH-enabled environments, reducing the time and effort required to schedule jobs that
run across these environments. For agentless scheduling in Window s environments, the specific adapter to order is
named Cisco Tidal Enterpr ise Remote Job Adapter for Window s. For agentless scheduling in SSH environments, the
specific adapter to order is named Cisco Tidal Enter prise Adapter for SSH.
Agentless Scheduling for Windows Environments
– Each job to be run by Enterpr ise Remote Job Adapter for
Window s is predefined w ithin the Enterprise Scheduler w eb interface. A secured proxy machine, acting as a job
scheduling agent, makes the necessary netw ork connections to the target Window s machines using the WMI. The
ad
scheduling agent, makes the necessary netw ork connections to the target Window s machines using the WMI. The
ad
apter then launches, populates, and runs each job us ing the target machines ’ Windows Task Scheduler.
Each job supplied through the adapter is discrete and encapsulated and can be run on a scheduled, change-based
(e.g., w atched resource) or on demand instance. Job definitions run by the target machines’ Task Scheduler services
(e.g., w atched resource) or on demand instance. Job definitions run by the target machines’ Task Scheduler services
are never saved on the target machines. They are automatically removed, preserving the security, performance, a nd
image integrity of the target machine.
Every point in the job runtime process is monitored and can be acted upon by IT operations staff. If the adapter finds
that the target is unreachable due to netw ork, machine, service, or authentication failures, Enterprise Scheduler can
be configured to alert IT managers to issues as they happen
—often acting in conjunction w ith its ability to execute
auto-recovery steps.
And as remote jobs are run on a scheduled or event-driven basis, they can be monitored in Enterpr ise Scheduler,
using the job details screen. Job output is equivalent to the data captured in the task manager log, w hich is delivered
back to Enterprise Scheduler. Exit codes are also available.
Agentless Scheduling for Linux, UNIX, or Other SSH En viro nments
– Agentless job scheduling for Linux, UNIX,
or any SSH- enabled environment is defined and managed using Enterprise Adapter for SSH. Enterpr ise Scheduler
can make direct calls to a target machine using the adapter w ithout the need for a proxy. Security management is
achieved through the use of defined runtime users as w ith all other adapters for Enterprise Scheduler.
can make direct calls to a target machine using the adapter w ithout the need for a proxy. Security management is
achieved through the use of defined runtime users as w ith all other adapters for Enterprise Scheduler.
As in the case of any other job schedules, SSH jobs are defined using Enterprise Scheduler. Once a connection to a
target has been defined, established, and user/machine credentials verified, job instances are supplied automatically
to the target, and the agentless job instance is then run on the target machine.
As scheduled or event-based jobs are run, they can be monitored like any other type of job defined in Enterprise
Scheduler. Standard output information is captured and delivered back to the Master by the adapter for real-time job
monitoring. Exit codes are also available.
Runtim e Control
– These adapters for agentless scheduling provide the follow ing runtime job control capabilities to
users. These capabilities are important, because they reduce the effort and time required to manage schedules and
job execution. Users can:
●
Hold a job instance w aiting to run