• 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 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.
