Cognos 8 -- Keys to Data Governance Success - Teamwork and an Iterative Approach

http://www.b-eye-network.com/view/6421

 

Here’s an interesting article to read on Data Governance if you have some spare time.

“Data governance practices are essential for managing data as an asset. These practices establish repeatable, measurable business processes and manageable policies for improving data quality. Data governance helps companies meet regulatory compliance mandates while improving revenue opportunities and customer and partner relationships through the power of higher quality information...

http://www.b-eye-network.com/view/6421 “

 

 

 

 

Cognos 8 -- Keys to Data Governance Success - Teamwork and an Iterative Approach

http://www.b-eye-network.com/view/6421

 

Here’s an interesting article to read on Data Governance if you have some spare time.

“Data governance practices are essential for managing data as an asset. These practices establish repeatable, measurable business processes and manageable policies for improving data quality. Data governance helps companies meet regulatory compliance mandates while improving revenue opportunities and customer and partner relationships through the power of higher quality information...

http://www.b-eye-network.com/view/6421 “

 

 

 

 

Cognos 8 SDK -- count of objects in content store

If your Cognos 8 SDK application requires that you determine the number of objects that are contained within the content store then you need to use the query method for the Content Manager Service.

private int CSObjectCount = 0;

public void countContentStoreObjects(String objectSearchPath)
{
PropEnum props [] = new PropEnum[]{PropEnum.searchPath,PropEnum.defaultName};

try
{
SearchPathMultipleObject srchPath = new SearchPathMultipleObject(objectSearchPath);
BaseClass bc [] = new BaseClass[]{};
bc = cmService.query(srchPath,props, new Sort[]{},new QueryOptions());

if (bc != null)
CSObjectCount = bc.length;
}
catch(java.rmi.RemoteException remoteEx)
{
System.out.println("ERROR Exception - querying:\n" + remoteEx);
return;
}
}

Cognos 8 SDK -- count of objects in content store

If your Cognos 8 SDK application requires that you determine the number of objects that are contained within the content store then you need to use the query method for the Content Manager Service.

private int CSObjectCount = 0;

public void countContentStoreObjects(String objectSearchPath)
{
PropEnum props [] = new PropEnum[]{PropEnum.searchPath,PropEnum.defaultName};

try
{
SearchPathMultipleObject srchPath = new SearchPathMultipleObject(objectSearchPath);
BaseClass bc [] = new BaseClass[]{};
bc = cmService.query(srchPath,props, new Sort[]{},new QueryOptions());

if (bc != null)
CSObjectCount = bc.length;
}
catch(java.rmi.RemoteException remoteEx)
{
System.out.println("ERROR Exception - querying:\n" + remoteEx);
return;
}
}

Cognos 8 Tuning -- Report Service Queue timeout limit

Queue timeout limit for the report service (seconds)

 

Default Value:  240 seconds

Recommended Value: 300 seconds

 

This setting is used to determine the length of time in seconds in which a request will be queued in a Cognos dispatcher before being terminated. If the queue timeout limit is exceeded, an error will be returned indicating that a process “… was not available within the configured time limit”.

 

A request will reside with the dispatcher until an appropriate high/low affinity connection becomes available.  This setting can be used to troubleshoot an environment that is

perceived to be queuing requests even though system resources appear underutilized. To help determine this, change the setting to a small value (e.g. 5 seconds) and monitor the system for an error page indication.