Schedule an Entry/Report Based on an Occurrence/Trigger

As part of setting up trigger-based scheduling, you must schedule an entry based on an occurrence.

Trigger-based schedule is activated if the user firing the trigger has:

read and traverse permissions for the schedule entry

traverse permissions for all ancestors of the schedule entry

access to IBM Cognos Administration

Steps
Click the schedule button next to the entry you want to schedule.

Under Frequency, click the By Trigger tab.

In Trigger name, type the name of the trigger occurrence.

Note: The trigger name that you enter may be provided to you by your administrator or developer. If not, you must inform your administrator or developer of the trigger name that you use.

The default start date is "now", and the default end date is "forever", which means the trigger schedule runs when the trigger is fired (either from trigger.bat or from an SDK application). If you enter a valid start and end date, the trigger schedule can only be fired between those dates.

Click OK.


Set Up a Trigger Occurrence on a Server

As part of setting up trigger-based report scheduling , you must set up the trigger occurrence on a server. You link the external occurrence, such as a database refresh or an email, with a trigger on the server that causes the entry to run. You must also specify the name of the occurrence.

Trigger occurrences can also be set up by an SDK developer using the IBM Cognos 8 software development kit (SDK). For more information, see the The IBM Cognos 8 SDK Developer Guide.

Scripts
Using the Windows script named trigger.bat or the shell script named trigger.sh, you can trigger one or more schedules to run on the server.

The script syntax follows where URL is the IBM Cognos 8 server URL, username is a valid username in the specified namespace, password is the password for the username, namespace is the namespace for the username, and triggerlist is a comma separated list of trigger names:

trigger.bat URL [username password namespace]
triggerlist
For example, if users want to schedule a report based on a database refresh and want to schedule a second report based on receipt of an email, your custom trigger command line may look similar to this:

trigger.bat http://localhost:9300/p2pd/servlet/dispatch username
password namespace databaserefreshtriggername,emailtriggername
Steps
If you are setting up a trigger occurrence on a server other than an IBM Cognos 8 server, complete the following tasks:

Ensure that the server has a supported version of either a Java Runtime Environment or a Java Development Kit.

Copy the following files from c8_location/webapps/p2pd/WEB-INF/lib on an IBM Cognos 8 server to the location on the server where you are setting up the trigger occurrence:

activation.jar

axis.jar

axisCrnpClient.jar

commons-discovery.jar

commons-logging.jar

jaxrpc.jar

saaj.jar

mail.jar

xml-apis.jar

xercesImpl.jar


Copy the following files from c8_location/webapps/EventTrigger on an IBM Cognos 8 server, to the location on the server where you are setting up the trigger occurrence:

trigger.bat

trigger.sh

trigger.class (a Java utility that can run on any IBM Cognos-supported platform)


Ensure that the command line runs when the external occurrence, such as a database refresh or email, occurs.

The mechanism that you use to invoke your custom trigger command depends on the application that you are working with, such as a database system or an email application. For information, see the documentation for your application.

Inform users that they can now schedule entries based on the trigger occurrence.

If a user scheduled an entry based on the occurrence, when the user clicks the schedule button for a report view, occurrence information replaces frequency information on the Schedule page.

If a user scheduled an entry based on the occurrence, when the user clicks the schedule button for a report view, occurrence information replaces frequency information on the Schedule page.

After the script runs, the trigger method returns an integer value representing the number of schedules that were run. The following integers represent errors:

-1 is a usage error, such as invalid parameter or syntax

-2 is a communication problem with IBM Cognos 8 server

Why is TM1 in limelight?

Only product in market that can be used for “OLAP Analysis” & “Planning” using “Multiple cubes” stored “in-Memory” .
Earlier, TM1 was available in 32bit technology. Limitation is 2 GB RAM. Targeted at solutions having limited data.
With introduction of 64 bit Technology, the available RAM is upto 1TB. This enabled TM1 to target solutions that handle large amount of data.
Sparcity removing algorithm.
Post Cognos Acquisition, TM1 is on long term road map of IBM.

Learning and sharing: CAFE (Cognos Analysis for Excel) Basic

Learning and sharing: CAFE (Cognos Analysis for Excel) Basic: "Just wanted to share a video about the integration of Cognos8 with Excel."

Business intelligence for all Cognos 10

Cognos 10 BI

IBM Cognos BI provides users with many options to access information. Each
option uses common functions and interfaces. Executives can take IBM Cognos
Active reports offline to keep working while out of the office. Information
consumers and executives can access reports, charts, and other business
intelligence objects using dashboards from IBM Cognos Business Insight. IBM
Cognos Advanced Business Users and Professional Report Authors can use
IBM Cognos Business Insight Advanced to create new IBM Cognos BI objects
and to analyze information from any source and from new perspectives. Users
familiar with office productivity tools can use IBM Cognos Analysis for MS Excel
to blend the power of IBM Cognos BI information with the personal workspace of
Excel. Users on the go can use IBM Cognos Mobile to stay connected to their
IBM Cognos BI information.

Stay connected I am going to expalin each feature in details ......

IBM Cognos 10 Redbook link and new features detail...

Face The Truth: IBM Cognos 10 Redbook link and new features detail...: "IBM Cognos 10 RedBook Link to the Book http://www.redbooks.ibm.com/redbooks/pdfs/sg247912.pdf Some of the Feature I like: New dynamic qu..."

IBM Cognos 10 Redbook link and new features details

IBM Cognos 10 RedBook
Link to the Book
http://www.redbooks.ibm.com/redbooks/pdfs/sg247912.pdf


Some of the Feature I like:

New dynamic query capability. Optimized caching, in-memory calculations, 3x faster query

Cognos admins can export all system metrics to a RDBMS and then analyze with Business Insight(new Dashboard tool integrated in COgnos 10).

The UI works very well and looks very well thought out.

Allows end user to manage their own login credentials reducing the load on IT.

we should more intensively use upgrade manager

Improved content manager performance through caching and faster olap in memory caching

New external data wizard for Cognos10 Report Studio. A feature that supports and encourages agile development

No more messy javascript to modify prompt object text - they are now modifiable properties in cognos10 (this is the best)

http://ow.ly/i/4UH1




Go! Search looks to be included in #Cognos10.

Cognos 10 -Bussiness Insight

Business Insight provides an integrated business intelligence experience for business users. This webbased tool allows you to use IBM Cognos content to build sophisticated interactive dashboards that facilitate collaborative decision making. These dashboards can include traditional business intelligence assets, along with Real Time Monitoring information, TM1 Websheets and CubeViews, as well as external data.

To Add Connection to LDAP sever:

• Right click on ‘Directory Server’ and say ‘Add connection’.
• A pop-up will appear as shown in the snapshot below.
• Add the following details in the pop-up
Add host: Cognos url
Port : 389
Base DN : o=organization.com

The connection is added.

Now we see the ‘Default’ namespace under the Directory Server.

Under the default namespace we see

• User
• Root User Class
• Application Server
• Data Source

To make LAE :

Right click on the namespace and say ‘Export to .LAE’

Scheduling Reports

Scheduling Reports
You can schedule reports to run at a time that is convenient for you, such as during off hours when demands on the system are low.
You can schedule reports individually or in a group by using a job. You can schedule reports to run by minute, hourly, daily, weekly, monthly, or yearly.
Only one schedule can be associated with each report or job. If you require multiple schedules for the same report, you can create report views and then create a schedule for each report view. Jobs have their own schedules, and these schedules are independent from report schedules.
After you create a schedule, the report or job runs at the time and date specified. You can then manage the properties of your schedules.
Prompts in Scheduled Reports
If a report that contains prompts is scheduled, you must save the prompt values or specify default values to ensure that values exist when the report runs according to the schedule.
In a job, you can specify prompt values for job steps. When a report runs as part of a job, the prompt values saved in the job definition are used instead of the values saved with the report. If no values are specified in the job definition, ReportNet uses the values saved in the report.
SCHEDULE A REPORT
You schedule a report to run it at a later time or at a recurring date and time.
If you no longer need a schedule, you can delete it. You can also disable it without losing any of the scheduling details. You can then enable the schedule at a later time.
ReportNet keeps history information and report outputs each time a report runs according to a schedule. You can specify how many occurrences to keep or for how long to keep them. For example, you can keep the history and report outputs for the ten latest occurrences or for schedules that ran in the last two months. Use the report history to see the times at which the reports ran and whether the reports ran successfully.
To schedule a report or report view, you must have read, write, execute, and traverse permissions for it. You also require the following access permissions to any data sources used by the report.
• dataSource - Execute and Traverse
• dataSourceConnection - Execute and Traverse
(With only Execute access, you are prompted to log on to the database.)
• dataSourceSignon - Execute

Schedule Multiple Reports at Once

You can set the same schedule for multiple reports by creating a job. A job identifies a collection of reports, report views, and other jobs that are scheduled together and share the same schedule settings. When a scheduled job runs, all the reports in the job run.

Jobs contain job steps, which are references to individual reports, jobs, and report views. You can specify whether to run the steps all at once or in sequence.

When the steps are run all at once, all the steps are submitted at the same time. The job is successful when all the steps run successfully. If a step fails, the other steps in the job are unaffected and still run, and the job has a Failed status.

When the steps are run in sequence, you can specify the order in which the steps run. A step is submitted only after the preceding step runs successfully.

The individual reports, jobs, and report views in steps can also have individual schedules.

To schedule a report or report view, you must have read, write, execute, and traverse permissions for it. You also require the following access permissions to all data sources used by the report.

• dataSource - Execute and Traverse
• dataSourceConnection - Execute and Traverse

(With only Execute access, you are prompted to log on to the database.)

• dataSourceSignon - Execute

Schedule a Report Based on an Event

You can schedule a report based on an event, such as a database refresh. You specify an event to act as a trigger. When that event occurs the report runs.

This functionality is also available through Event studio.

Start Query Studio in Preview Mode

You can configure Query Studio to start in preview mode. Users can then create or modify reports without retrieving actual data from the database. Instead, simulated data is shown.

If you later upgrade IBM Cognos 8, you must reapply this configuration.
Steps

1. Using IBM Cognos Configuration, stop IBM Cognos 8.
2. Rename the c8_location\templates\ps\async\system.xml.sample file to
system.xml.
Tip: To restore the regular mode, rename the
c8_location\templates\ps\async\system.xml file to system.xml.sample.

3. Using IBM Cognos Configuration, start IBM Cognos 8.

Unsupported IBM Cognos 8 Formatting

About 30% of the formatting functions available in IBM Cognos 8 are not supported in Microsoft Excel. In particular, Excel does not allow changing locale-dependent formatting attributes, such as the following:

Decimal Separator

Exponential Symbol

Group Separator

Monetary Decimal Separator

AM String

Day Name

Day Short Name

Decimal Delimiter Symbol

Month Name

Month Short Name

PM String

In addition, Excel does not support the following:

Format Width

International Currency Symbol

List Separator

Percent Symbol (Excel does not support percent symbols for charts)

Multiplier

Overline Text Format

PerMill Symbol

Plus Sign

Scale (Excel has a different scaling formula than IBM Cognos 8)

Calendar (Excel does not allow changing the calendar)

Era Name

First Day Of Week

Show Era