Cisco Cisco Workload Automation 6.3 Guia Da Instalação
17
Installation Overview
CWA Components
CWA Cache Database
The database where the Client Manager stores the job scheduling objects and cache data. CWA supports Microsoft SQL
Server and Oracle (see
Server and Oracle (see
for specific versions). Windows platforms can use either Microsoft SQL Server
or Oracle; Unix platforms must use Oracle. The database software must be installed on the Master server machine prior
to installation of the CWA Master. The default CWA Cache database name is “TESCache”.
to installation of the CWA Master. The default CWA Cache database name is “TESCache”.
Master (or Primary Master)
The Master is the primary CWA component that conducts all scheduling tasks. You can have one or more Masters in your
network. The Master can be installed on either the Windows platform or the Unix platform. The basic functionality of CWA
remains the same regardless of the platform of the Master.
network. The Master can be installed on either the Windows platform or the Unix platform. The basic functionality of CWA
remains the same regardless of the platform of the Master.
Each Master computer must supply a unique port number to which Client Managers connect. This port number ensures
that communication between the Client Manager and Master is clear.
that communication between the Client Manager and Master is clear.
Client Manager
The Client Manager allows the Master to achieve higher performance and scalability. The purpose of the Client Manager
is to service requests from user initiated activities, such as through the CWA Web Client, CWA Transporter and from other
external sources that utilize the Command Line Interface (CLI) or published CWA Web services. The Client Manager
allows the Master to focus more capacity on core scheduling needs related to job execution and job compilations, while
the Client Manager addresses demands from activities such as users viewing/configuring scheduling data and output.
The Client Manager constantly syncs the information from the Master database into its own TESCache database that it
then uses to provide all CWA Web Client users with current information. Multiple Client Managers connected to the same
Master can be deployed to address additional performance needs.
is to service requests from user initiated activities, such as through the CWA Web Client, CWA Transporter and from other
external sources that utilize the Command Line Interface (CLI) or published CWA Web services. The Client Manager
allows the Master to focus more capacity on core scheduling needs related to job execution and job compilations, while
the Client Manager addresses demands from activities such as users viewing/configuring scheduling data and output.
The Client Manager constantly syncs the information from the Master database into its own TESCache database that it
then uses to provide all CWA Web Client users with current information. Multiple Client Managers connected to the same
Master can be deployed to address additional performance needs.
The Client Manager is required if you want to use the CWA Web Client, the Transporter, the Command Line Interface
(CLI), REST, or mobile applications. The Client Manager is not required if you are only using the Java Client.
(CLI), REST, or mobile applications. The Client Manager is not required if you are only using the Java Client.
CWA Web Client
The CWA Web Client is the main user interface for managing CWA jobs, scheduling, connections, configuration, and so
on. The CWA Web Client connects to the Client Manager using a browser.
on. The CWA Web Client connects to the Client Manager using a browser.
You can use both the CWA Web Client and the CWA Java Client with the same Master.
CWA Java Client
The CWA Java Client is a standalone application that provides the same user interface as the CWA Web Client to manage
CWA jobs, scheduling, connections, configuration, and so on. However, the Java Client connects directly to the CWA
Master and not through the Client Manager. You can run the Java Client as an application, or you can launch it using a
browser.
CWA jobs, scheduling, connections, configuration, and so on. However, the Java Client connects directly to the CWA
Master and not through the Client Manager. You can run the Java Client as an application, or you can launch it using a
browser.
The CWA Java Client is typically more responsive than the CWA Web Client because it is connected directly to the
Master. However, this increases the RAM used by the Master process as the Master is now doing the work instead
offloading it to the Client Manager.
Master. However, this increases the RAM used by the Master process as the Master is now doing the work instead
offloading it to the Client Manager.
You can use both the CWA Java Client and the CWA Web Client with the same Master. Note that an environment
exclusively using the CWA Java Client will not be able to utilize features that require the Client Manager like the
Transporter, Command Line Interface, and the WebService API.
exclusively using the CWA Java Client will not be able to utilize features that require the Client Manager like the
Transporter, Command Line Interface, and the WebService API.