If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

Monitor & Log Service

Started by CognosPolzovatel, 26 Nov 2007 02:33:51 PM

Previous topic - Next topic

CognosPolzovatel

Greetings:

Could someone please explain the functionality/purpose of the Monitor Service, Log Service and the Report Service? What are you using these services for? If these services are running in the background, where can one locate the generated output? 

MFGF

Hi,

In a nutshell:
The monitor service is used to monitor requests coming in from the dispatcher and route them to the requisite service to handle them (report service, batch report service, request service etc)

The log service is used to handle any logging requests to file/database/event log etc.  This covers production of both log messaging and audit messaging from the Cognos 8 server.  The output produced is sent to whichever logging resources are configured in the Cognos Configuration utlility, and the logging levels are determined via settings in the Server Administration utility in Cognos Connection.

The report service is used to process requests to execute reports interactively through the web browser session (ie run now and wait for the output to be rendered).  This is distinct from the batch report service, which is used to handle requests to execute reports in the background (ie run now but render the output and save it into the content store instead of displaying the results immediately in the browser).

Hope that helps,

MF.
Meep!

CognosPolzovatel

Hello MF:

Thanks for the overview of what the Monitor, Log, and Report service accomplish. I am researching what Cognos provides for Cognos usage monitoring/statistics. It looks like the log service can be used for this type of auditing. I shall also research the Audit package, as suggested in an earlier post.

Thanks for your help.

MFGF

Hi,

You're correct - the log service is used in generating usage information (among other things).  If your logging destination is configured as a database, then it's generally referred to as Auditing, although the reality is that the same service is responsible for producing the information, regardless of its destination.

Regards,

MF.
Meep!