Job Scheduler

kuju

Hi,

Does anyone has an idea why Microsoft didn't implemented its Job scheduler in an application server?

If i understand the functionality of the job scheduler well you have to leave a session where the "Job scheduler management" form has to remain open

K.

fl

Basicaly, there is almost no difference between an application server and a job sheduler. They run both codeunits or reports you want.

Difference is that:

Job scheduler needs a session just like any other navision client (so uses 1 license). In that session there is a form running with a timer inside so that all the jobs (reports, dataports or codeunits) or run at the right time.

Application server runs as a service on the pc or server. This means you even don't need to login in windows. The service wil automatically start as soon as the pc /server boots. But a applicationserver uses no GUI (grafical interface). You have to look in the log for remarks and in the services to see if the service is still running. The application server does not use a standard user license but needs an application server license.

The reason they are not implemented in each other is that a service should'nt have a GUI.

Arhontis

Hi,

NAS is just like the job scheduler... You can implement anything you want that doesn't need a UI with NAS.

Job scheduler needs UI to work, but you can create a NAS and use the code (i.e. from form 6094) to run the objects you have setup in job scheduler without using the form...

kuju

Arthonis, Fl,

Thnx for the reply!
I was aware of the difference between the client and the nas but in my opinion a job scheduler is a task especially for the NAS:
- Automatically start/stop of service
- Restart in case of errors (technical/functional)
- Load on "middle" tier component (dedicated NAS server)
With the 'Navision Timer 1.0'.Timer' error catching and logging can be simply done in a log form.

We developped a job scheduler a few years ago (before it was available from MS) with the NAS functionality.

I can imagine that in most operational environments this is a pc standing in a corner where nobody is watching it.

I was just wondering why MS chooses to use an open session?

K.

nunomaia

Microsoft for the PT version and supplied several enhancements, one of them is to run job scheduler from NAS.

themave

Job scheduler can be run by an end user who licenses it for a few hundred bucks.

NAS, has to have a codeunit modified to run items, and end users can't modify codeunits without a very expensive application designer granule at a cost of around $8000.

So, if end user wants to run NAS jobs, he has to pay his solution center everytime he wants to change something.

DenSter

Not if you implement it like the job scheduler, with a setup for jobs and such, and have the actual scheduler process look in that setup for what to run at which times.

themave

DenSter wrote:

Not if you implement it like the job scheduler, with a setup for jobs and such, and have the actual scheduler process look in that setup for what to run at which times.

Interesting, so what do I need to ask my solution center to do to set up the separate job schedule for NAS?

I would rather have NAS do the function of the job schedular, now I start a client on the server and start the schedular from that client, since the server never shuts off, the client is always running, which is fine. but it does use a client license.

Luc_VanDyck

themave wrote:

I would rather have NAS do the function of the job schedular, now I start a client on the server and start the schedular from that client, since the server never shuts off, the client is always running, which is fine. but it does use a client license.

The NAS also uses a Navision session, so you wan't cut on user sessions. It's just more convenient as it's running as a service and you don't have to manually login to Navision whenever the server is rebooted.

Waldo

May I?

http://www.ifacto.be/default.aspx?page=nasscheduler_eng
or
http://www.mibuso.com/pdinfo.asp?FileID=77

DenSter

themave wrote:

DenSter wrote:

Not if you implement it like the job scheduler, with a setup for jobs and such, and have the actual scheduler process look in that setup for what to run at which times.

Interesting, so what do I need to ask my solution center to do to set up the separate job schedule for NAS?

I would rather have NAS do the function of the job schedular, now I start a client on the server and start the schedular from that client, since the server never shuts off, the client is always running, which is fine. but it does use a client license.

It's not something you can just set up, it is custom development, although not very complicated. It's been done by many people, probably with slight changes. Check out Waldo's solution and if it is what you want I am sure you could purchase it.

Oh and the standard license comes with one instance of NAS included, so if you are not using NAS at the moment, you should only have to make sure you have the new/purchased objects added to the license. Otherwise, you need to purchase another instance of NAS to accommodate the scheduler.

Waldo

Indeed.

If you want one NAS-based job scheduler per company, it's quite easy to do (after some custom development).

If you want one job scheduler for all companies ... it's quite complicated, but do-able...