CU-Data R11 Upgrade
Upgrading CU-Data(Cognos) QA instance from R6 to R10 on Tuesday, 5/14/2018
Professional authors with experience developing reports with IBM Cognos BI v10 in either Report Studio or Cognos Workspace Advanced
CU-Data User Session "How to" Video
IBM Cognos Analytics Videos
Recently we have started migrated ETL from DataStage to ODI and took eRA ETL to Live in November 2017, as the part of the new ETL tool we have updated all the table names. Please find the attached crosswalk file for old and new tables.
This course provides an overview of CU-Data system and its various components (Report, Dashboard, Etc..). In this 2- day instructor-led training we cover in-depth basic developer CU-Data training, step by step on how to build a report, prompt and other related functionality. The training will run from about 9 am – 4 pm Thursday and 9 am – 12 pm Friday, with the afternoon of Friday reserved for workshop. CU DATA (Cognos Analytics Version 11) - The CU Data User Interface is a modern and sleek User Interface (UI) that provides a graduated User Experience based on the needs of the individual user. This modern purpose- built User Interface provides a highly intuitive User experience which greatly promotes User adoption. The only CU provides Analytics tools that provide managed self-service done in a cognitive way. Whether Users are looking for Personal Data Discovery, or to leverage their full enterprise data platform for analysis. Let’s take a few hours to familiarize ourselves with the User Interface so we can take CU Data for a test drive!!
You can schedule entries based on an occurrence, such as a database refresh or an email. The occurrence acts as a trigger, causing the entry to run. For example, you may want to run a report every time a database is refreshed. Trigger-based scheduling may be used to run entries automatically based on an occurrence. It may also be used to limit when users can run entries. For example, in a warehouse environment where the database is refreshed only once a week, there is no need to run reports more frequently. You can choose to schedule the report based on the database refresh so that the report runs only once a week. Trigger-based scheduling applies only to the entry, not to any entry view associated with it. For example, if trigger-based scheduling applies to a report, it does not apply to report views associated with the report. However, you can schedule a report view using a trigger.
Automation for DS jobs to ODI mapping conversions using tools/Groovy/Stagekillaz
Understanding where to install the ODI Standalone agent Top Ten Best practices in ODI ODI performance guide