Информационное Руководство для Cisco Cisco Tidal Enterprise Adapter for Oracle Database
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
© 2013 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public
Page 4 of 9
“These days, you cannot underestimate the importance of an intuitive user interface,” says Ramesh Nagalingam,
Cisco IT manager. “With our current system, clients cannot simply jump in and use the software to start building
and scheduling workflows. In order to connect to a database, for example, you have to script a sequence, which
can take twice as long as using a Cisco TES adapter. With Cisco TES, you do not have to rewrite scripts every
time you want to add a new job to the workflow, either. Anytime scripting is involved, there is a greater margin for
error.”
Recently, Sudheer Keshav had to coordinate four teams—database administration, system administration, the
client team, and IT—across different time zones to set up a new job in Job Scheduler 1. It took about a week to
organize the process. With Cisco TES, he says, it would have taken less than a day and involved only two teams.
“With the existing scheduler, it could take up to four days to onboard a new job, compared to a half hour with
Cisco TES. We anticipate a much higher level of client satisfaction with Cisco TES based on the time savings
alone.”
Thousands of jobs are maintained by the client application teams, so the migration to Cisco TES will take several
quarters. Prakash Hemchand, lead engineer for enterprise job scheduling services, estimates that the jobs for Job
Scheduler 1 began transitioning at the rate of about 70 to 80 a week, but that number has grown quickly as word
spreads. “Most people are excited to move to something new. They hear that other teams are finding the new
technology faster and easier to use, and they want the same benefits,” says Hemchand.
The IT organization identifies opportunities for the transition, usually when an application team needs to make a
change in their production environment. The process involves an analysis of the outcomes using Job Scheduler 1
compared to the outcomes with Cisco TES. “We want to show clients the value that they will get, so that they are
excited about moving to the new platform” says Hemchand. “We follow a service engagement process for all new
projects.” Clients provide a lot of detailed input. IT provides the best practices, FAQs, and training for the clients.
Eventually, onboarding to Cisco TES will become more streamlined because scheduler accounts and access will
be executed as a service request through the Cisco Prime Service Catalog, a self-service portal.
Replacing Job Scheduler 2
Cisco IT used Job Scheduler 2 to schedule Business Object/Business Analyzer and SAP-related jobs. Over 75
percent of the jobs scheduled with the existing scheduler were for the supply chain organization. “If those jobs do
not run, Cisco does not produce and ship products,” says Keith Abass, Cisco IT analyst.
This migration involved moving six client teams and several thousand production jobs to Cisco TES. Because of
the focused scope of this application set, the transition to Cisco TES was achieved relatively quickly, within a
couple quarters.
“With the existing scheduler, it could take up to four days to onboard a
new job, compared to a half hour with Cisco TES. We anticipate a
much higher level of client satisfaction with Cisco TES based on the
time savings alone.”
new job, compared to a half hour with Cisco TES. We anticipate a
much higher level of client satisfaction with Cisco TES based on the
time savings alone.”
— Sudheer Keshav, IT Engineer