Руководство Пользователя для Cisco Cisco Workload Automation 6.3
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
7
Cisco Systems, Inc.
www.cisco.com
1
Introducing the
Cognos Adapter
This chapter provides an overview of the Cognos Adapter and its requirements:
Overview
The Cisco Workload Automation (CWA) Adapter for Cognos is an API-level integration solution. This solution hides
implementation details in screens that connect to Cognos instances and define Cognos tasks as part of CWA job
definitions. It accesses the Cognos Business Intelligence content store using the Cognos Content Manager Service. As
a platform independent solution, the adapter can run on any platform where the CWA master runs.
implementation details in screens that connect to Cognos instances and define Cognos tasks as part of CWA job
definitions. It accesses the Cognos Business Intelligence content store using the Cognos Content Manager Service. As
a platform independent solution, the adapter can run on any platform where the CWA master runs.
The Cognos adapter enforces Cognos security by authenticating with Cognos through associations between CWA
runtime users and Cognos namespaces, users, and roles. Creating a Cognos job from CWA is highly secure, but as
simple as creating any other job.
runtime users and Cognos namespaces, users, and roles. Creating a Cognos job from CWA is highly secure, but as
simple as creating any other job.
A job definition refers to report and query data that is retrieved from the Cognos content store including format, print,
save, and email disposition options as well as parameter value overrides that can refer to Scheduling variables. Based
on defined scheduling criteria, the Enterprise Adapter submits a Cognos task to run either directly through the Cognos
Batch Report Service or indirectly as an event that tracks background processes and history from the Cognos Monitor
Service. Once the task has been submitted, the Adapter monitors the process until it is completed. The Adapter returns
the final completion status (used to control downstream jobs) as well as details associated with the run to the console.
In addition, the Adapter lets users cancel, abort or rerun tasks from CWA, a feature that provides significantly more
control over the environment than afforded by scripting or other non-integrated scheduling solutions.
save, and email disposition options as well as parameter value overrides that can refer to Scheduling variables. Based
on defined scheduling criteria, the Enterprise Adapter submits a Cognos task to run either directly through the Cognos
Batch Report Service or indirectly as an event that tracks background processes and history from the Cognos Monitor
Service. Once the task has been submitted, the Adapter monitors the process until it is completed. The Adapter returns
the final completion status (used to control downstream jobs) as well as details associated with the run to the console.
In addition, the Adapter lets users cancel, abort or rerun tasks from CWA, a feature that provides significantly more
control over the environment than afforded by scripting or other non-integrated scheduling solutions.
The Cognos adapter is event-based. It launches processes based on defined calendars and schedules and uses
asynchronous callbacks for monitoring—enabling users to see status changes in real time and to control those processes
as they execute. This capability reduces production processing time windows, because the Adapter does not need to
wait for a polling interval to pass before reacting to the completion of a Cognos task.
asynchronous callbacks for monitoring—enabling users to see status changes in real time and to control those processes
as they execute. This capability reduces production processing time windows, because the Adapter does not need to
wait for a polling interval to pass before reacting to the completion of a Cognos task.
Prerequisites
If Cognos is configured to use SSL for external communication (HTTPS), you must complete the following steps as
described in detail in
described in detail in
.
Obtain security certificates for all target servers
Export security certificates for all target servers to a local directory
Import security certificates for all target servers into a Java keystore