Cisco Cisco Tidal Enterprise Adapter for zLinux Hoja De Datos
©2016
Cisco
and/or
its
affiliates.
All
rights
reserved.
This
document
is
Cisco
Public.
Cisco Workload Automation Schedule Integration – One of the key strengths of the adapter is that the
messaging integration approach is made available for scheduling designs via Cisco Workload Automation job
definition screens. This extends standardization of operations across the full range of environments under Cisco
Workload Automation management, giving IT operations staff a robust and sophisticated tool with which to
incorporate messaging-based processes into the enterprise. In addition, as with other Cisco Workload
Automation adapters, the Adapter for JMS jobs can be executed through granular calendar, ad hoc, and on
demand scheduling techniques, bringing message-driven topologies into the enterprise scheduling framework
for the first time.
Accelerated Automation – Cisco Workload Automation Adapter for JMS can drive IT-wide process automation
by giving IT operations staff the tools to orchestrate enterprise-wide job schedules and event-driven activities
from a portable, browser-based single pane of glass. The adapter also allows IT operations staff to accelerate
the delivery of service level agreements (SLAs) by making all scheduling activities more efficient and by
accelerating the ability to respond to business changes.
Cisco Workload Automation Adapter for JMS consolidates message-based scheduling automation with other
distributed processes, making it easier to comply with enterprise IT policies and standard operational processes.
Integrated security management features support required credentials authorization when implementing JMS
connections, enforcing process adherence to IT security rules as well. To add flexibility to Cisco Workload
Automation, the adapter can be used as a full-featured scheduling alternative to Cisco Workload Automation for
Web Services in distributed message-driven environments—particularly where adding a web services layer or
integrating into a SOA-based framework is not otherwise required.