Job Server vs. Process Server

Overview

As with Costpoint's client/server's Process server, the job server in Costpoint web is used to combine function parameters from report, computation, and posting applications into a single job that can be submitted to a user-defined queue for running on the Job server at a scheduled date and time.  

Most of the web's Job server screens are similar in design and function to client/server's Process server screens, with the following exceptions:

Workstations

Server and Queue Relationship in Client/Server

1) Can have multiple Process servers.

2) Each Process server can only service one queue.

3) Each queue can be serviced by one or more Process servers.

  S1    S2    S3      S4

     \    |      /          |

       Queue1       Queue2

Server and Queue Relationship in Costpoint Web

1) There is usually one application server.

2) The application server contains threads to run jobs in queues.

3) Each queue can be serviced by more than one thread.

4) Jobs in a non-sequential queue will run simultaneously on different threads.

5) Jobs in a sequential queue will run sequentially (one job after the other).

          Application Server

       /     |       \           |

   T1      T2      T3       T4

      \      |       /           |   

         Queue1           Queue2

  (Non-Sequential)   (Sequential)

Recurring Timeframe Selections

Database Tables

Due to different requirements and structure, the Job server in Costpoint web uses different database tables than the Process server in Costpoint client/server.  

Using Job Server

Costpoint Administrator Steps

1.  Create Job Queues  

Create job queues for jobs to run.  Use the Job Queues screen (Administration\Maintain\Job Management) to manage all job queues, since it provides information on the status of each queue and its specific jobs.

Note:  Normally, only the Costpoint system administrator has rights to this screen (since this screen can modify all jobs within all queues).

 

Note:  When a queue is first created, it is not active.  You can set a queue to an active state in the Start/Stop Job Server screen (Administration\Transactions\Job Management) or Update Job Queue List Status screen (Administration\Transactions\Job Management).  Only jobs in active queues are run in the Job server.
 

 

2.  Start/Stop Job Server

To ensure that a queue is active, select the Active for Server checkbox for that queue in the Start/Stop Job Server screen (Administration\Transactions\Job Management).   

Click on the "Start" pushbutton to start the Job server polling. Use the "Stop" pushbutton to stop the Job server from polling. You can use the Shutdown Time and Restart Time fields to stop the Job Server from polling during a specified timeframe.  Use the "Reset" pushbutton to bring the Job server down completely, and detach the queues from the Job server until it is started again (which means that all queues will be inactive when the Job server starts again).

Note:  The system will not recognize a new queue that is created while the Job server is running unless you perform one of the following actions:

  • Stop (or reset) the Job server and restart it.  [Clicking on the "Start" pushbutton updates the JOB_QUEUE_LIST table with information from the Job Queue List child table subtask, and then starts the Job server.]

  • Click on the "Update" button in the Start/Stop Job Server screen (Administration\Transactions\Job Management) or Update Job Queue List Status screen (Administration\Transactions\Job Management). You must select the Active for Server checkbox to make the Queue active.

Submitting a Job to Job Server

1.  Save Screen Parameters

In a process or report application, create and save the screen parameters to be used in Job server.

2.  Create Job Groups (Optional)

Create a Job Group in the Job Groups screen (Administration\Maintain\Job Management) if you want to organize your jobs into groups (e.g., Accounting, Payroll, etc.).  

Note:  Job Groups are for organizational purposes only and have no effect on the execution of a job.  Job Groups are used in the Job Report to print out job definitions for a specific group or to print out all job definitions grouped by a job or job group.

3.  Create Jobs

Create jobs in the Jobs screen (Administration\Maintain\Job Management), specifying name, description, job group (optional), how you want the job to behave if an application task fails, and comments.  In the Application Parameters subtask, you must also enter one or more application tasks that you want to execute in this job, including the parameter and process or report.

4.  Submit Job to Queue

Use Query to search for a desired job.  Select when you want the job to be run and whether you want the job to be run on a recurring basis.  Then enter the queue (manually or use Lookup) that you want the job to be submitted to.  Click on the "Submit to Queue" pushbutton to send the job to the specified queue.

Report and Maintenance Steps

1.  Print Job Report

Print this report from the Job Report screen (Administration\Review\Job Management) to review the jobs in your system and the Costpoint applications and parameter IDs that have been associated with them.

2.  View the Job Status  

Use the Monitor Job Status screen (Administration\Transactions\Job Management) to view the status and related information for all the specific jobs within a queue.

3.  Change Queue Active/Inactive Status  

Use the Update Job Queue List Status screen (Administration\Transactions\Job Management) to make a queue active or inactive on the Job server and to allow new queues to be recognized when the Job server is already running.

4.  Print/Purge Job History

Use the Print/Purge Job History screen (Administration\Review\Job Management) to print or purge the history of jobs that have been previously executed on the Job server.

Top of Page