By Candace Taylor, Marketing Coordinator for PerformanceG2
 
Do you know the current health of your organization’s Cognos environment? Is your Cognos system mature, up-to-date and conforms to industry standards? Is your Cognos platform efficient and organized? Do you want to be dedicated to making sure your Cognos system is healthy?

While organizations focus on utilizing Cognos software to its fullest through training and best practices, it is also important to think about your Cognos system’s overall health to ensure that the architecture is stable, logical, clean and fully-functional.

Through PerformanceG2’s complimentary Cognos Health Check service, your system is assessed by certified technical specialists who know what they are doing, know what they are looking for and can provide recommendations on how you can get your system cleaned up. They do this by reviewing the overall system and architecture through a validation process, scan the content store for corruption, check for broken reports and inconsistencies, identify broken links and run a variety of other diagnostics to offer a full-view, and grade of the health of your Cognos platform.

To take advantage of our Cognos Health Check service, call us at (877) 742-4276 or email us at info@performanceg2.com and see how you can get started.
 


 
 
 
Contact the Blogger

 
By Craig Harding, Consultant for PerformanceG2
 

Better performance will be realized by using parameters and prompts within Model Query Subjects, filter objects or stand alone calculations. This will allow for better SQL generation than inserting them within the SQL of a Datasource Query Subject.

These recommendations lead to better SQL generation, which in turn, leads to better performance.

Nearly any prompting can be done in a Model Query Subject:
[Product dimension].[Product line].[PRODUCT_LINE_CODE] =
#prompt(‘Product Line Code’, ‘integer’, ‘1’)#

Same with Calculations:
Case [Product dimension].[Product line].[PRODUCT_LINE_CODE]
When #prompt(‘Target Product Line Code’, ‘integer’, ‘1’)# then 1
Else 0
End

The added benefit of placing prompts in a stand alone calculation is that if the report author does not use the calculation, then the prompt is no longer needed. There is no need to add this case statement to the Base SQL.

When using calculations and filter objects in Model Query Subjects or as stand alone objects, the Datasource Query Subjects can be left untouched. This means the SQL remains minimized and eliminates the need to fetch metadata.

 
 
Contact the Blogger

 
Kirk Wiseman, VP of Training for PerformanceG2
 
In Cognos 8.4, it is now possible to use existing IBM Cognos 8 packages and reports as a data source in Cognos Transformer. This has made building data sources that much easier since any Cognos 8 report can be leveraged in Transformer, improving development time and ensuring that the data is all coming from the same underlying data source.

When using IBM Cognos 8.4 as a data source for Transformer, use the following guidelines to achieve efficient cube build times:

• If filtering and/or calculations are required, use Cognos 8 reports as the data source
• Create separate data sources in Transformer for each required dimension as well as for measures
• Include foreign keys found in fact tables to transformer modelers
• Avoid unnecessary local data processing on IBM Cognos 8 servers

 
Use IBM Cognos 8 Reports when Filters and/or Calculations are Required

While you can request that the IBM Cognos Framework Manager modeler include certain filters and calculations in an IBM Cognos 8 package, this requires extra maintenance on the Framework Manager modeler’s part. Instead, Transformer modelers can use list reports that incorporate filters/prompts and calculations as needed. If prompts are used in the report, Transformer modelers can control which filters are applied when the PowerCubes are built.

Regardless of whether the work is done in the Framework Manager model or in a report, the net gain remains the same; where supported, processing will be pushed to the database and the load on Transformer will be reduced. If filters/prompts are used, then Transformer will deal with a reduced record set, thereby decreasing build times.

Using reports allows for a greater degree of control to meet requirements and removes the need for additional development support.
 
Create Separate Queries in Transformer
When using a package as a data source in Transformer, individual queries should be created based on the data sources for the cube; one for each required dimension and one or more for the measures depending on how many underlying fact tables there are and what the business need is.

When using a report as a data source, either use separate list reports, again, one for each dimension and one or more for the measures, or create separate list report queries in one report. Then in Transformer, a query is created for each of the separate list reports or separate list queries within a single report.
 
Expose Fact Table Foreign Keys in the Package
Typically, foreign keys found in the tact table are not presented in the fact query subjects in a Cognos 8 FM model. Either they are not included in the model query subject, or they are hidden form the user. For most ad hoc query users or report authors, they provide little benefit and can cause confusion. To prevent confusion to the larger authoring audience, security can be used to expose the keys to a select group of authors only. For example, only Transformer modelers. In certain cases such as with Tranformer modelers, there is a clear benefit to exposing the foreign keys to the users. It will be more efficient to create a measures data source in Transformer that takes its keys from the actually fact table, rather than from its related dimension tables. In this way, the query will go against one table in the data source, rather than several. The database may rewrite the query to be more efficient before executing it, but a a general rule of thumb, the cleaner the SQL Cognos submits to the database, the more likely an efficient query will be run at the database layer which takes advantage of database optimization.
 
Avoid Unnecessary Local Data Processing on IBM Cognos 8 Servers
Certain query scenarios may require data processing on IBM Cognos 8 servers. In some of these cases, performance is not an issue and may even be required to produce a result set where a database vendor does not support the query. However, there are cases where local processing can adversely affect query performance and in turn, affect PowerCube build times. A typical example of this is when a function that is not supported by the database vendor is used in a calculation. This will cause a retrieval of the entire data set from the database and then perform the calculation locally on the Cognos 8 servers. To rectify the situation, use an equivalent function that is supported by the database vendor.

To see if local processing is occurring for a slow performing query, there are a couple of troubleshooting techniques. One is to look at the Cognos SQL generated for the query and compare it to the Native SQL. This can be done in Framework Manager or in Report Studio. Actions being performed in the Cognos SQL and not in the Native SQL indicate that processing is done locally. Another technique is to set query processing to Database Only. In Framework Manager this setting is found in the properties of the Data Source objects and is called Query Processing. In Report Studio, the setting is found in the properties of the query and is called Processing. When the setting is set to Database Only, an error will be generated in cases where the query can not be fully pushed to the database. The error will typically identify the offending time preventing the push to the database.

NOTE: This is based upon the IBM Best Practices Document which can be found at: http://www.ibm.com/developerworks/data/library/cognos/modeling/transformer/page512.html?ca=drs-
 
 
Contact the Blogger

 
By Sanjeev Datta, Senior Consultant for PerformanceG2
 
 
I always find interest in situations where, as a full-service CPM organization specializing in BI, we make an instant difference to our clients by significantly improving their profitability and performance, while at the same time, helping them cut costs and go green.

A few weeks ago, one of our clients approached us with a situation where invoice reports that went our to their customers who bought products via a Web site, were eating up their budgeted office supplies allocations more than they had expected. In a way, this was good news as sales figures were up, however the sales numbers would look more attractive if internal costs were down too.

One solution that we proposed to our client to meet this challenge was to create invoice reports in IBM Cognos Report Studio and distribute them via an automated nightly email process rather than a daily chore of printing out invoices and analyzing and calculating shipments, which can be time consuming and cumbersome tasks, especially for invoices going to global clientele.

PerformanceG2 took upon the challenge of creating this highly customized and extremely detailed invoice report in Report Studio version 8.4. With the use of singletons, which are data items that can be placed anywhere on the pixel perfect Web based reporting tool, and with the use of blocks, tables and various conditional statements to customize the report to include business rules for specialized groups of customers (e.g., domestic versus international, currency conversions, changing address lines, etc.), we delivered to our client The Invoice Report.

Report delivery was decided to go out in PDF format as an email attachment. For this, we used a feature in Report Studio known as “bursting”. The burst feature is used to run a report and divide the output based on a burst key, in this case, unique invoice numbers, which then generate multiple outputs inclusive of security features for each of these invoices. Therefore, this one developed report was to generate thousands of invoices per month and email them out to their respective customers daily, eliminating human errors and postal delivery delays all while significantly reducing printing costs, paper and my favorite: terminating the extremely time consuming task of folding these paper invoices and carefully placing them into envelopes. In addition, in the event a scheduled job halts, or is not completed in the specified time, an alert is sent out to the concerned owners who can take appropriate actions to rectify any inconsistencies before they reach the far end.

In the end, the challenge was met, the project was a success, and the project is now in production to our client’s and their customers’ satisfaction. With the use of Cognos Event Studio, and some creative green thinking, we have handed ownership of this project to our client.

 
 
 
Contact the Blogger

 
By Candace Taylor, Marketing Coordinator for PerformanceG2
 
For many years, Cognos Enterprise Planning has been made the market choice for budgeting and forecasting – providing users with a powerful alternative to spreadsheet-based financial modeling. However, the core of the EP application was built more than a decade ago, and lacks the scalability and flexibility necessary to deal effectively with the increasing volumes of financial data that are now common in most organizations. The result is that EP is often difficult to change and costly to manage.   

Cognos TM1 is designed to fix many of the current EP challenges. The time is now to make your Cognos EP to TM1 conversion, and with IBM’s limited time offer of an EP license trade-in promotion, you can receive a TM1 Contributor license for every EP Contributor license you currently own, making the process easier and cost-efficient for your organization.
 

 
Why convert to Cognos TM1? Here are just some reason why your organization should make the move:

1. TM1 allows for a more scalable solution which provides for easier handling of increased volumes of data, unlike its predecessors
2. TM1 functions in real-time, providing on-demand updates and forecasting capabilities
3. TM1 incorporates the breadth of Cognos 8 Studios for optimal reporting capabilities
4. TM1’s cutting edge financial analysis and reporting capabilities is backed by its powerful database engine that delivers comprehensive views of your organization’s financial picture
5. Migrating Cognos EP to TM1 could never be easier and more cost-efficient with IBM’s limited time conversion offer

Read more about the TM1 Advantage, TM1’s new features and how you can start your EP to TM1 migration by downloading our EP to TM1 Fact Sheet. Learn more about how you can save and get started with your migration, also get all of your questions about the process answered - connect with one of our TM1 experts today by emailing us at info@performanceg2.com or call 877.742.4276.
 
Contact the Blogger

 
By Candace Taylor, Marketing Coordinator for PerformanceG2
 
Are you a Business Intelligence Admin looking for more transparency in your BI environment? This awesome app by Motio, MotioPI FREEware for IBM Cognos, allows you to investigate your BI environment’s components, users, content, report details, schedules, dependencies and more. It is the perfect tool to become familiar with a new environment, identify constraints, monitor usage behavior and ensure that your IBM Cognos BI environment is aligned with your resources and infrastructure for optimal performance.

The best part about this app, is that it is a free tool, designed with IBM Cognos BI admins in mind. Watch this short MotioPI demo to learn more about the app and what it can do. Or to start using the free tool, click here to download it.
 

Motio and PerformanceG2, together provide complete and comprehensive solutions and products for organizations to achieve maximum return on their BI and Financial Planning investments. For more information on the Motio and PerformanceG2 partnership, visit performanceg2.com/about/partners/
 
 
And if you are interested in learning how PerformanceG2 can help meet your needs with BI solutions, email us at info@performanceg2.com or call 877.742.4272. Or for complete access to BI, CPM and Cognos industry news, updates and tips and techniques, follow us on Twitter, become a fan on Facebook, watch our YouTube Videos or connect with us on LinkedIn.
 
 
Contact the Blogger

 
Kirk Wiseman, VP of Training for PerformanceG2
 
For many organizations, TM1 is a critical application that must be maintained as a 24×7 enterprise application. In these cases, it is not acceptable to shutdown the TM1 server to perform a backup. TM1 provides organizations the ability to maintain 24×7 uptime, and also perform regular backups of the data directory. Several changes will need to be made to the default settings of the TM1 server configuration file (tm1s.cfg) in order to perform a live backup successfully.

The advantages of this method include ease of administration, 24×7 system uptime and automation which can be created within TM1 using Turbo Integrator and Chores. The disadvantages of this method include initial configuration that must be performed, and the possibility of lost data between “saves” if the data directory files become corrupt.

The following steps must be performed in order to run backups from a live TM1 server:

1) Modify the default TM1 server configuration file (tm1s.cfg)

• Point the log files to a location other than the data directory by inserting the “LoggingDirectory” parameter in the configuration file. By default, TM1 writes log files to the data directory. Since these files will be open and active while the TM1 server is running, any attempt to back them up will result in a file sharing violation and may cause a backup process to fail.
• Verify that the “AuditLogOn” parameter is set to ‘F’. This is the default setting, however if the “AuditLogOn” parameter is set to ‘T’, then as in the case above with the transaction logs, open and active files will be in the data directory. Attempting a backup will cause a file sharing violation which may result in a backup failure.

2) The administrator must perform, or must set up automation to perform, a “Save Data All” command. This command should be executed immediately prior to backing up the TM1 server. This command takes all changed data in RAM and saves it to the TM1 data directory files, where it is then able to be captured in the back up process.

3) Backup all files in the TM1 data directory

• Create a batch file called tm1back.bat that has the following script: “C:\program files\winzip\winzip32.exe” -a -p -r c:\backup\tm1backup.zip “C:\<tm1data folder>\*.*”

4) This process can easily be automated through the use of Turbo Integrator calling the batch file and scheduling the Turbo Integrator job via the TM1 Chores.

• Expand the TM1 sever and click on “Processes”;
• Click on the “Advanced” tab;
• Click on the “Epilog” tab;
• Below the “#****End: Generated Statements****” line, type the following:
  SaveDataAll;
  ExecuteCommand(‘C:\<folder where you saved the batch file>\TM1backup.bat’,0);
• Click on the “Save” icon or choose from the menu, “File” > “Save As…”
• Enter a name for the process, for example Backup
• Next, click on the “Schedule” tab;
• Check the box “Schedule this process as a chore named:”;
• Enter a name for the new Chore, for example Backup Chore
• Choose a start date and a frequency and then click “Save”

There you have it – a scheduled backup procedure that will create a backup of your TM1 server without having to shutdown the server!
 
Contact the Blogger

 
By Craig Harding, Consultant for PerformanceG2
 

To try this, build a real simple list report and add staff name and revenue.

Add a value prompt to the report page. Name the parameter sort, and click ‘finish’. Add two static choices through the properties pane of the value prompt. For the first static choice, display value will be ascending with a use value of 1. For the second static choice, set the display value to descending, and the use value to -1.
 

 

You must add a default selection in order to avoid being prompted on report load. This can be done through the properties of the prompt. I put a value of 1 in the default selections for ascending.

Also, set the auto submit property to yes.

Add a data item to the query. The expression should read [Revenue]*?sort? (no need to type this, drag and drop from the insert-able objects pane). Name the data item sortkey and set the presort property to ascending.

Return to page one and select the list. The properties property of the list must have the sortkey checked.
 

 
Run the report to test.
 

 

 
 
Contact the Blogger

 
Kirk Wiseman, VP of Training for PerformanceG2
 
This month’s IBM Cognos Supportlink newsletter has a great article on how to do “on the fly” language translation using Cognos 8 Report Studio and Google’s language API. As we know, Cognos 8 is a multilingual reporting tool that can automatically switch languages based on a user locale. However, this requires storing all the different language variations within the client’s database. Using the Google API allows the client to have a translation applied automatically without having to store the data locally. To read the full article, click here.
 

 
PerformanceG2 is an advanced business partner of IBM, and IBM Cognos Software. For more information on our Cognos offerings, click here.
 
 
Contact the Blogger

 
Kirk Wiseman, VP of Training for PerformanceG2
 
Often with large text items, the Select and Search prompt display areas are not wide enough to display the data. Here’s a way to make the display areas dynamically re-size to meet the demands of the wider data:

1. Locate and backup the file ..\c8\webcontent\prompting\properties.js located on the Cognos 8 gateway component.

2. Set the SYSTEMPROPERTY_CSEARCH_AUTO_RESIZE_RESULT_LIST to true.

See below:
————————————————————————–
// Copyright (C) 2008 Cognos ULC, an IBM Company. All rightsreserved.
// Cognos (R) is a trademark of Cognos ULC, (formerly CognosIncorporated).
/* Use this file to override flags in the prompt controls. */
/*
Use the following flag to disable search request when the user press Enter in the search input box.
This is a workaround to prevent searches when users use japanese IME input control.
*/
var Search_DisableEnterKeyAutoSubmit = false;
var SYSTEMPROPERTY_CSEARCH_AUTO_RESIZE_RESULT_LIST = true;
var SYSTEMPROPERTY_CREATE_CUSTOM_SCRIPTS_REFS = true;
var SYSTEMPROPERTY_CUSTOM_SCRIPTS_OVERRIDE_FORM_SUBMIT = false;
var SYSTEMPROPERTY_REORDER_DROPDOWN_VALUES_IN_RANGES = false;
—————————————————————————-
The Select and Search prompt control display areas are variable width and therefore wide information is no longer cut off.

 
Contact the Blogger