B.

A report specification is executed via Query service which directly queries via RDBMS
adapter, and caches then waits for the result and generates the report output.

B.

Create a datasource connection to the logging database.

Before you can create audit reports or use the sample audit reports that come with IBM
Cognos software, you must set up audit reporting.

D.

Traversing to view child entries

Users must have at least traverse permissions for the parent entries of the entries they
want to access. The parent entries include container objects such as folders, packages,
groups, roles, and namespaces.
References:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos
.ug_cra.doc/c_accesspermissions.html

C.

Configure dispatchers together with the content stores.

If your installation includes more than one dispatcher, you can specify the proportion of
requests that each dispatcher handles by changing their processing capacity. This is
commonly referred to as load balancing. You typically set the capacity for a dispatcher
based on the CPU speed of the computer where it is installed.
References:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.1/com.ibm.swg.ba.cognos
.crn_arch.10.2.1.doc/c_arch_dispatcher.html

C.

Create and run a Content Archival task for the folder “AP”. Create and run a Content
Removal task and set the options of Run history to 12 Months and Output versions to 30
days.

Administrators use the retention rule update task to specify the number of reports, queries,
analyses, and document objects to keep in the content store. You can specify how long to
keep the history and output versions in the content store. Anything that is older than the
date you specify is deleted from the content store.
Run this task only after creating and running the content archival task. If you run it before,
content that was not marked for archival is permanently deleted from the content store.
References:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_10.2.1/com.ibm.swg.ba.cognos
.ug_cra.10.2.1.doc/t_creat_retent_rl.html

B.

Add external namespaces to the Cognos namespace manually.

In the Cognos Analytics user interface, authentication providers are represented by
namespaces.
Cognos Analytics supports the following types of authentication providers:
Authentication providers are configured in IBM Cognos Configuration, under the Security >
Authentication category. After the provider namespace is added there, and the IBM Cognos
service is restarted, the namespace name is displayed in Manage > Accounts, and users
can log on to Cognos Analytics using that namespace.
References:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos
.ag_manage.doc/c_ca_external_namespaces.html

B.

ContentManageService: Request: Number of failed requests

Figure: A detailed view showing the status of individual system metrics for a service

References:
https://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/pa
ge589.html

B.

userCapabilities

The userCapabilities cookie, with the Session temporary type, contains all capabilities and
the signature for the current user.