C.

IBM Cognos implementation, capacity, infrastructure

Conduct an architecture review to assess the physical architecture and software
installation.
References: ftp://public.dhe.ibm.com/software/pdf/dk/serviceshop/
IBM_Cognos_BI_Health_Check_Service_FINAL_10-21-11.pdf

A.

Set load balancing to cluster compatible.

If your IBM Cognos servers operate within a load balancing infrastructure, you can turn off
the weighted round robin format of load balancing for the dispatcher. Otherwise, load
balancing may be duplicated by the cluster and by IBM Cognos software, which can
degrade performance.
You can set the dispatcher property named loadBalancingMode either to
weightedRoundRobin or clusterCompatible.
References: IBM Cognos Administration Version 10.1.0, Administration and Security
Guide, page 163

D.

On the Connection tab of the datasource properties, ensure that the ‘Allow web-based
modeling’ check box is selected.

Problem(Abstract): Datasource connections not listed in Data server by default
Symptom: We can see the datasource in the Admin console but not in the list of data
servers.
Cause: This is default behavior.
Resolving the problem
Go to the Administrative Console -> Configuration -> Set properties -> Connections tab.
On the bottom, you will see "Data source capabilities"
Inside that, check the box which says "Allow web-based modeling"
Once you check this, the datasource would be present as data server.
References: http://www-01.ibm.com/support/docview.wss?uid=swg21978718

C.

An advanced routing has to be configured in Cognos Administration audit requests from
application tiers routed to Content Manager server.

If a request should be subject to Advanced Routing, then the client which send the request
is responsible for calling CM to evaluate Routing Rules and put the Server Group
Information into the request passed to a Dispatcher.
References:
https://www.ibm.com/developerworks/data/library/cognos/infrastructure/cognos_specific/pa
ge510.html

B.

In IBM Cognos Configuration under IBM Cognos Services/IBM Cognos select Query
Service and select operation Clear Cache.

To avoid using outdated data that might be stored in the cache, you can clear the cache.
You might want to clear the cache manually if your data source metadata changes
infrequently or if you want to clear the cache in between automatically scheduled cache
clearing. When you clear the cache using the following steps, it clears everything in the
cache.
Steps
1. Start IBM Cognos Connection.
2. In the upper-right corner, click Launch, IBM Cognos Administration.
3. On the Configuration tab, click Query Service Caching.
4. Select the server groups for cache clearing.
5. Click Clear cache.The status of the Clear cache command is displayed.If a cache is
being used by one or more pending reports or queries, it is internally flagged as “stale” by
this command and is automatically cleared as soon as this usage completes.
6. Click Close.
References: IBM Cognos Administration Version 10.1.0, Administration and Security
Guide, page 253

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.

At least one signon available to the users through permissions.

You add signons to data source connections so that users do not have to enter database
credentials when they run reports.
References:
https://www.ibm.com/support/knowledgecenter/en/SSEP7J_11.0.0/com.ibm.swg.ba.cognos.ug_cra.doc/c_datasources.html

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.