Skip to main content

Introduction to Scheduler

Hubble® is an integrated suite of performance management apps. It offers reporting, analytics and planning in a single, real-time solution that fully understands your ERP. Hubble is built on a simple idea – that things should be easy. Hubble integrates your critical business systems so end users at all levels of the organization have access to live data – extraordinarily fast. With this type of visibility, everyone can easily understand, manage and predict the business. Redundant processes disappear, and a high- performance business can emerge.

Scheduler is a tool that allows users to define distribution lists, define Hubble reports to be run at a scheduled time, automatically run reports according to their predefined schedules, and distribute the reports via email in PDF and/or Microsoft Excel® format.

Scheduler is a standalone application that installs on a server. The application allows authorized Scheduler users to define schedules and distribution lists for automatically running and delivering the reports.

Getting Started

Prerequisite

Microsoft .NET must be installed prior to Scheduler. Please see the Minimum Technical Requirements for Desktop Reporting; the same .NET requirements specified for Desktop Reporting also apply to Scheduler.

ERP Versions

Scheduler works with JD Edwards Enterprise One, JD Edwards World and Oracle ERP Systems. It is important to know that with JDE World, the associated Profile in the Administrator application must use option 4 in the World Security Options (login with Hubble user and password is authenticated by the Object Repository). If this is not the option currently being used with your World Profile, you would need to set up a separate World Profile to be used with scheduled reports so that it is set this way. (The reason for this requirement is that all the other World Security Options rely on the user entering their JDE password at the time the report is scheduled to be run, which does not work with the concept of reports running automatically.)

Licensing

Scheduler Administrators

Scheduler Administrators, the users who manage the Schedules and Distribution Lists, need the Scheduler license (SCH). Scheduler Administrators are able to log into the Scheduler Application in order to create, view, edit and delete all Schedules and Distribution Lists that they have defined. If the Scheduler Administrator is NOT in the Administrator group in Administrator, the user will also need to be given the Users and Group Administration Capability in order to manage the Recipient Users:

Repository Administrators (those in the Administrator group within Administrator) are also able to log into the Scheduler Application in order to manage the schedules and distribution lists in the system.

Run as Users

For each scheduled task, an individual user will be defined as the ‘run as user’ so that the inquiry is run using this user’s ERP credentials. To run a scheduled inquiry, the ‘run as user’ must be someone who can open that inquiry in an application. More specifically, the ‘run as user’ must have one of the following:

  • A license assignment for the same module as the inquiry being scheduled as well as the Reporting License

  • An Viewer (CON) License

  • A Reconciler License when the inquiry belongs to the Reconciliation Module

Recipient Users

The ‘recipient users’ are the users on the report distribution lists who only receive an email with the report output. They must be added as ‘recipient users’ in the Scheduler Application or the standard Administrator Application. They do not need to have a license assigned to them.

Standard Users

Standard Hubble users can be added to report distribution lists.

Installing Scheduler

Scheduler is a standalone application that installs on a server and has an additional component, Scheduler Service. Scheduler must be installed in the same folder as the standard Hubble release with which it is being used.

After the installation, you see that 5 files have been added to the install path for the Scheduler application:


If you install Scheduler on a client PC as well as a server, it is important to note that the service component is not needed on the client PC as the service on the server will run the jobs. So it is critical that you permanently deactivate the service on the client PC. For detailed information on how to do this, see the section on Windows Services on page 10.

Only one Scheduler Service should be active (started) per Hubble Object Repository. This is why it must be deactivated on the client PC if it is active on a server.

Also it is important to note that the active Scheduler Service should be located in close proximity within the network to the repository database.

In version 2012.2 and above, Scheduler is available on a 64-bit platform.

Administration Setup

The items below must be done in Administrator prior to running Scheduler.

Profile

We recommend setting up a Scheduler profile and using this for all the Scheduled jobs. If at some point you want to point to different data, you can do this within the same profile rather than changing all the scheduled jobs.

Permissions

‘Run as users’ must have read permissions for the profile and connection that are being used for their scheduled reports.

Save Repository Selection File

If this is a new install of a Hubble, save the repository selection file in the new install path, or set up a connection to a remote repository selection file. Refer to the Administrator & Configuration Guide for further details of repository files and how to set them up.

The Scheduler Application must also point to this repository selection file; this can be done once you launch Scheduler.

Verify that the RepositorySelection.xml file is located in the correct location path and is viewable for the Administrator starting the Windows Service.

Licensing

Licenses must be assigned in License Assignments. All non-administrator users who will be managing the scheduled reports must be assigned a Scheduler, or SCH, license. Also the “run as users” must have the appropriate license assignment to be able to open the scheduled inquiry in Hubble.

User Setup Required

Recipient Users

Users who will be receiving scheduled reports via email are not required to have a license for a specific module or Viewer; however they must be named as ‘recipient users’ in the Scheduler Application or in the standard Administrator Application.

To set up recipient users, right-click on Users and Groups and select Manage Recipient Users:


In the Manage Recipient Users dialog, recipient users can be added, edited, and deleted completely. To add a user, type the requested information into the field. Once a user is added, you can edit the information by clicking in the field and changing it as needed. To delete a user, highlight the entire row and select Delete on your keyboard.


Fields in the Manage Recipient Users dialog:

  • First Name - either this or the Surname must be specified.

  • Surname- either this or the First Name must be specified.

  • Username – Hubble generates the username if one is not specified; also if the user is already a standard licensed Hubble user, the username cannot be edited.

  • Email Address – must have a valid email address.

  • Company - optional; this information only seen in this dialog.

  • Notes – optional; this information only seen in this dialog.

Notes:

  • For organizational purposes, recipient users can be moved out of the Recipient Users Group under Users and Groups but they will still be manageable via the Manage Recipient Users command.

  • This information in the Manage Recipient Users dialog can be managed in Microsoft Excel and then pasted into this dialog using the Paste Button in the bottom left corner. Pasting will append this list, not replace it. If you want to replace the list that is already in the dialog, you must delete the users in the dialog first and then paste the new list from Excel.

  • Recipient users are identified by a different icon in Users and Groups.

  • A recipient user cannot be turned into an Hubble user. If the situation arises where the user type needs to change, you need to delete the recipient user and create the Hubble user by using the standard process. All scheduled tasks that contain that previously defined recipient user will still function and deliver an email to the now Hubble user.

Once the recipient users have been set up in the group, you can view them in the Group Definition dialog (accessed by right-clicking on the group and selecting Edit) as well as by focusing on the group in the left panel and viewing them in the right panel. Both of these methods are shown below:

in the Group Definition dialog, the email field is for future use, so this should remain blank. Optionally, you can provide a description for this group.

Under the Administrators group, you will see a user, Scheduler Service. This user is only used by the Scheduler Service to log into the Repository. This username is used to log Scheduler Services activities under a distinct username. This user cannot be deleted or moved.

Email Address Set in User Definition

A valid email address must be defined for all email recipients as well as those who will be scheduling reports (the latter for test email purposes). The email address for Recipient Users is done in the Manage Recipient Users dialog. Email addresses for standard Hubble Users are set in the User Definition for each individual user. To access this, expand Users and Groups. Right-click on the specific user and choose Edit to launch the User Definition dialog: