Bursting a Report Using SDK and Save the Output to the Local File System

When the report runs with the burst option, multiple outputs are being created in a single run. The Java code for this technique – will extract all of the outputs and store them in a local file system in HTML format.You can also change the option to extract just the latest output version of the report outputs.
For this example, we will be using the "GO Sales and Retailers" sample database to create the report with the burst key.
Follow these steps to complete the technique:
Create a new report in Report Studio. Set the Burst Options and execute at least once. Do not delete the report outputs.
Modify the value of the endpoint variable if you are not using the default gateway:
String endpoint = "http://localhost/crn/cgi-bin/cognos.cgi";
Modify the savePath variable to where the output will be saved:

String savePath = "C:\\temp\\";

Modify the reportName variable to the report that will run:

String reportName = "Banded Report";
Modify the latestVersion variable to true if you want to retrieve the latest version of the report outputs; otherwise, set it to false to retrieve all versions of the report outputs:
boolean latestVersion = true;
Modify the username, password, and namespaceID variables to the correct login information:
String userName = "nameSpaceID";
String passWord = "userName";
String nameSpaceID = "passWord";
Compile and execute the script. Information about the Cognos ReportNet Java Toolkit can be found in Chapter 1 of the ReportNet SDK Getting Started Guide, under the ReportNet Java Toolkit section.
Check from your save path to see if the report outputs are being generated.

What is SOX ?

SOX - Sarbanes-Oxley

The Sarbanes-Oxley Act of 2002 protects investors by improving the accuracy and reliability of corporate disclosures made pursuant to the securities laws. One of the most significant provisions within Sarbanes-Oxley are the criminal and civil penalties that place executive management and the board of directors in the “hot seat.” Specifically, under Section 404 of the Sarbanes-Oxley Act, executives need to certify and demonstrate that they have established and are maintaining an adequate internal control structure and procedures for financial reporting.

Objectives to meet Sarbanes-Oxley compliance
Sarbanes-Oxley requires a new level of corporate governance and accountability. As a result, the vital role security information and event management (SIEM) plays in establishing and maintaining internal controls have never been greater. Companies must institute log monitoring and vulnerability assessments as a critical part of their IT internal control systems. Both domestic and international publicly-traded companies must comply with Sarbanes-Oxley. If you are a covered entity you must have methods to maintain audit trails and to log possible altering of electronic records. Network Intelligence has mapped best practices and reports to help organizations comply with audits under Sarbanes-Oxley Section 404.

For more details check http://www.network-intelligence.com/solutions/compliance/regulations/sarbanesoxley.asp

Redirecting from Contributor Application Help

Sometimes it is desirable to redirect users to other web-resources, when they click on the help button for a given cube.
For example:
- Place a instruction on a sales forecast cube telling users to click help to view a report showing previous years sales.
- Link to a Capex model that may feed the expenses model so that users can review input that has been feed in using admin or system links.

This allows the administrator the ability to use a web-authoring tool, such as MS FrontPage, to create a central company-themed site for documentation and easily link to it, rather than re-creating pages each time. Also, this
provided the added benefit of reducing the model size, as none of the help text needs to be included in the model definition.

Steps

1. Go to any Contributor Application --> Development --> Configuration --> Contributor Help Text
2. For each cube for which you wish to provide a help link that redirects to another page, enter the following tag in the Detailed Cube Help:
<meta http-equiv="refresh" content="0; URL=http://webserver/site/page.htm">

This meta tag is instructing the browser to refresh the page. The “content=” tag tells the browser how long to wait (in seconds) before refreshing the page. To redirect immediately, without the user noticing anything, leave this
value at 0.
The “URL=tag” tells the browser where you want to redirect to. If you have a specific page in mind (like a report, for example) you can cut and paste the URL into this location

For more details on various HTML Tags check the following website: -
http://www.w3schools.com/

Publish Failure Error in Cognos Planning 7.3 and 8.1

Error Message: -
Publish fails with bulk load error and no .out file is present. Installing Oracle Client and executing sqlldr.exe is successful.
Unable to Bulk Load the data.
BulkLoad Execution returned 1.Output file (C:\DOCUME~1\cognos\Local Settings\Temp\CBE61F5133084ED8AEFA2C22B10E00A9et_forecast__machiE282F3CBD61140398D4F0873872C1B1C{6B5305F0-D569-4B3D-8E0B-DB818AF5F6A9}.out)

Solution:
If you are using Windows 2003, there may be an issue with using the Disable8dot3 setting.

Look at the error message as displayed above or open the .cmd file in a text editor. If the path contains a space such as "c:\docume~1\cognos\local settings\temp" SQL*Loader will fail with a syntax error, even though the path is enclosed in quotes.

Set your temp directory to a path that contains no spaces such as c:\temp. Modify the temp settings for the user account assigned to the COM+ component to point to a path with no spaces in Environment Variables, then set this path in Configuration Manager under Cognos Planning>Shared. Apply your configuration, then stop and start services

For more details check Cognos support site http://support.cognos.com/kb-app/knowledgebase?document_search_show_document=1&document_id=1012528&version_id=1