• The "Common Services" allows general access to the system like sign-on and browsing through all of the files and folders.
• The "Intelligence Service" could also be called the publishing service used for publishing queries and jobs and is used when jobs are running.
• The "Data Access Service" allows you to process queries.

We restart the Hyperion Server every night at 7:30 PM. If you have a job in the scheduler that was previously set to run after a triggered event or timed event, after the restart at 7:30PM, it will most likely start running.

In the current environment we can only run 3 jobs every 10 minutes. All jobs that start after a triggered event MUST start after 12:01 am.

We run 2 web servers for MyReports. On occasion one or the other seems to hang up, it may be because of the activity on one web server is due to a very complicated query and returning a lot of results from more than one person. If the logon to MyReports seems to hang - like beyond the normal 15 seconds, just close the window, and click on the MyReports link again, it should automatically send you to the next Web server. Then send us a SD Request via email so we can have the Web group check the web server.

Always remember we are all in the Hyperion web environment together and many of the jobs in the scheduler are based on a Data Warehouse area refresh, some of which take most of the night loading. As the tables, and subsequently the load gets larger, the refresh takes longer and pushes the hyperion scheduler jobs into the day when day-to-day clients are running queries. We will sometimes need to work with you to get your queries moved to different time slots if need be or process them differently. Just one way of doing that is to consolidate some of the queries that seem to take a few seconds to run into one query document. There are other ways; we can work with you to accomplish this.

Make sure if you send email from the scheduler, you enter your contact information so the people know to whom to reply. We receive a lot of emails that people just reply to sender (which is the server software, and they are just deleted).

Don't copy/paste text into the email subject, email to/cc/bcc list, or additional message areas. Sometimes the hard-coded characters that you can't see such as carriage returns and tabs are in the text that you copy and they can sometimes cause an error. You can sometimes see this when the error message is "invalid number of job parameters".

Keep your event names, schedule names, job names down in size to less than 60 characters, when you start adding all of these together and then append the date/timestamp to the filename you will get an error message that is vague and mis-leading and may not even save the output.

Also, stay away from any "special" characters in schedule names, job names, and event names. Some of the combinations with certain special characters have a particular meaning when developing web pages, so it is best to stay away from all of them and stick to straight alpha-numeric characters. The only true safe character to use is an Underscore. It seems to be safe using space also, although when saving output or queries, you will sometimes see a %20 in replace of the space when on the web.

Sending attachments to listservs via the scheduler seems to cause the attachment to be embedded within the email there-by making the attachment useless.

There seems to be an issue when running very large results sets and trying to "Save Document" back to the web. If you need this large set of results we can work with you to see what else can be done. Things like this have brought down the server in the past.

Replacing Jobs
In most cases, just delete the old job and everything that goes with it. It is best just to start from scratch. Even a simple thing as changing the name of a section can and will cause an issue.

Manage Events
The list sorting is messed up - basically it is sorted by the index that is built on the underlying tables so when you list your events, it is sorted, just not in a very useful manner. This has been identified as a bug to Hyperion.

When creating events, please put your user_ID in as identification of the name of the event so we can see who "owns" the event. The GUI screens are not sorted and don't display the name of the owner.

Manage Jobs
While there is no sorting button, if you go to Browse and make sure your sort is set to "by Name" the sorting will be alphanumeric, otherwise, you are not sure what the sort is, it may actually be by date.

Consolidated Job Status List
If you haven't used this, the best thing to do is "Save as default" then click "apply". After that, when you go in to use it, you will be taken directly to the list of jobs. The PDF should have more abouit this. But this is the best place to see a list of all of the jobs in the scheduler.

• What has run: Look at the consolidated Job Status List, this shows what has run, best to sort descending by Last Run Date.
• What is left to run: if it is based on a Time Schedule, it will be shown in the Job Status List. If it based on the triggered event, you can not see what should run in the Job Status List. We are trying to get a query available to help, but it will only show what jobs are based on the event. It will not show when it will run.