Configuring the DataView Scheduler

Configure the DataView Scheduler to schedule the creation of consolidated views, that is, views that are made up of one or more individual tables or charts. In addition, you can schedule these consolidated views to be sent by email, with delivery notification and error information. You can also upload consolidated reports to an FTP server to be accessed by internal users.

Before you begin

Important: For security reasons, consider not using the Tivoli® Netcool® Performance Manager server to allow FTP download to external users.
Note: If scheduled reports are to be used where multiple DataView servers are associated with the same database, the same content must be installed on each DataView server.

About this task

To configure the Scheduler:

Procedure

  1. Select System Configuration > Network Performance > Performance Management.
  2. Select the Scheduler tab.
  3. Enter a valid address for the Host Email Address.
  4. Change the default values of the other parameters as necessary, by using the table for guidance.
    Option Description
    Internal Scheduler Password The Scheduler cannot run until you change the internal password from the one set at installation time. The Internal Scheduler Password must match the password of the Dashboard Application Services Hub user tnpmScheduler.

    You must restart the Jazz for Service Management application server for your changes to take effect.

    Report Format Select a report format type for the Scheduler task. By default, the report format type is PDF.
    Note: You can also change the report format type when scheduling a report.
    Email User Name If the email host server requires SMTP authentication, you must enter a valid user name and password to log in to the email server and relay email messages beyond the network domain.
    Email Password If the email host server requires SMTP authentication, you must enter a valid user name and password to log in to the email server and relay email messages beyond the network domain.
    Host Email Server A valid email host server must be provided in order for the Scheduler to start. The Scheduler delegates all email to this email host server for distribution. If configured, email content can include consolidated report documents, FTP notifications, and error messages. An example of an email host reference is mail4.kafka.com.
    Administrator Email Account Email address of the Scheduler system administrator. All system error and task completion notifications are sent to this system administrator email account.
    NFS Base Directory A directory where finished report files are placed for storage. Consider using a directory that is accessible to all Scheduler servers. The full directory format is base FTP directory/report owner/report name.zip.
    For example, given the following parameter values:
    • NFS base directory: /opt/my_sched_reports
    • Scheduled report user: user123
    • Scheduled report task: thruput
    • Type of report: Daily

    the name of the scheduled report is: /opt/my_sched_reports/user123/RO_user123_thruput_DAILY.zip

    Note:
    • The NFS Base Directory must exist and must be writable by pvuser (the UNIX user running DataView).
    • You must ensure that the NFS mount is working properly before the Scheduler attempts to write files to the remote machine.
    • The Scheduler does not require NFS to operate. Files can also be written to the local DataView machine.
    FTP Base Directory The directory where an FTP server can provide access to completed report files. A directory that is accessible to all Scheduler servers is suggested. The full directory format is base FTP directory/report owner/report name.zip.
    For example, given the following parameter values:
    • FTP base directory: /opt/my_sched_reports
    • Scheduled report user: user123
    • Scheduled report task: thruput
    • Type of report: Daily

    the name of the scheduled report is: /opt/my_sched_reports/user123/RO_user123_thruput_DAILY.zip

    Note:
    • The FTP Base Directory must exist and must be writable by pvuser (the UNIX user running DataView).
    • You must ensure that the NFS mount is working properly before the Scheduler attempts to write files to the remote machine.
    • The Scheduler does not require NFS to operate. Files can also be written to the local DataView machine.
    FTP Link Information The link prefix to which a file name is appended to create a complete FTP file link specification that points to a consolidated report file in the FTP file directory structure. Example: ftp://ftp_server_name where ftp_server_name is the name of the FTP server that contains the scheduled reports for the user.
    Email Notification File Enter the full path name of a file containing text to be included in the body of the email message sent to the recipient of a consolidated report. This file allows you to configure custom text to be included in the notification message. If the field is not populated, a default message is sent by the scheduler. The default text includes basic information about extracting the reports from the compressed file and how to open the document containing the reports.
    Off-Peak Start Time Time at which the Scheduler starts running report tasks at a higher priority. Typically set for night when fewer portal users access the server. Default value at initialization is 00:00:00 GMT.
    Off-Peak End Time Time at which the Scheduler switches back to running report tasks at a lower priority to avoid competing with portal requests. Default value at initialization is 00:00:00GMT. If both start and end off-peak times are default values, the Scheduler threads remain as low-priority threads.
    Period Completion Time Time of day until which the Scheduler waits before processing a scheduled task. Waiting until this time ensures that late data resides in the database at the time the report is run.
    Maximum Run Once Tasks Maximum combined number of `run once' tasks that can be started by all report owners at one time. Because run once tasks are not scheduled, they do not comply with the "off peak" policy. Keep the maximum as low as possible to prevent system overload.
    Maximum Off-Peak Processes Maximum number of report tasks that can run concurrently in the off-peak time period.
    Maximum Peak Processes Maximum number of report tasks that can run concurrently in the peak time period.
    Wait Late Data Days Number of days the Scheduler waits before running a report task to ensure that late data resides in the database. A task is assigned by a Scheduler when the current time is within 24 hours of its next run time. In addition, the Wait Late Data Days plus the Period Completion Time are factored in.
  5. Click Save.