Configuring Cognos 8 to send out report output via email

To send out report output via email from report server (run -> advanced options -> Delivery ->send the report via email for the report), we need to configure the mail server. Please see below for the steps to follow, in this context.
  1. Open up Cognos Configuration UI via Start -> Programs -> Cognos 8 -> Cognos Configuration
  2. Select 'Data Access' -> 'Notification' from the 'Explorer' panel
  3. In the 'Notification - Component Properties' panel, make the following changes:
    1. set the value for 'SMTP mail server' (something like smtp.ca..com:25 for eg)
    2. select the value for 'Account and password'
      1. Edit the value by selecting the pen symbol next to the value cell;
      2. clear the default values in the 'User ID' and 'Password', 'Confirm password' text fields in the pop up window 'Value - Account and password'.
      3. Select OK

    3. select the value for 'Default sender'.
      1. enter your email address
      2. The value entered in this field MUST be a valid email address.


  4. Save the changes made in Cognos configuration
  5. Restart Cognos by selecting the restart button
You can now choose the 'send the report via email' option as the run time option for any report, and enter your valid email address to receive the report output via email.

IMP Note: Report output will be send on behalf of the report owner, if the owner is default then report ouput will be send using default email mentioned in steps#3

Please note that an incorrect configuration of notification component can lead to memory leaks ( leading to java out of memory error)in Cognos 8 server, in 8.1.2 MR2.

Comments

Post a Comment

Popular posts from this blog

How can you extract all user information from Cognos Access Manager Namespace Report Utility and create Cognos Report out of it?

The AM_NamespaceReport Utility allows you to extract the namespace to an XML file. 1. Use the AM_NamespaceReport Utility to extract all users from the namespace to an XML file. am_namespacereport -h > -p > -r > -n > -D > -w > -f all -o > e.g am_namespacereport -h cognoscamsevr -p 4004 -r o=cognos.com –n devcam -D admin -w admin -f all -o c:\temp\usrlst.xml 2. This will extract all user information to an XML file 3. Import the xml file into XLS spread sheet 4. Create ODBC connection using the ms-excel spread sheet driver 5. Create Data Source Connection and proceed creating FM Model & Publish 6. Create Report using Report Studio. 7. Save & Share the report The Access Manager Administration Guide (Appendix A) contains further information on this functionality.
Read more

RSV-VAL-0032 expression is not valid. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'.

Image
Problem: RSV-VAL-0032 The following expression is not valid: [AdjRowsReturned] = 0. If the item exists in a query but is not referenced in the layout, add it to a property list. CRX-API-0005 An error ocurred at or near the position '0'. The variable named '[AdjRowsReturned]' is invalid Resolution: You might have used the calculated data item in the variable, which needs to be added in the page properties. - Click on the page and go to properties. Make sure you see 'page' on the top of the properties. - Click on properties icon under data section, you'll get pop up icon - Check mark the data item which is used for variable calc. You are good to go.Find the snapshot. .
Read more

BME-EX-0047 Unable to read preferences for the requested interface..

Issue When opening or creating a Framework Manager project the following error message is shown. Additionally, when attempting to create or open a report based on a package is made in Report Studio or Query Studio, the same error message is shown. Error BME-EX-0047 Unable to read preferences for the requested interface. Please use another repository and/or ProjectAccess Interface. Resolving the problem This happens due to a corrupt bmt.ini file in <Install Location>/c8/configuration directory. This issue can be resolved by extracting bmt.ini from last known good backup or even from installation files.
Read more