Skip to main content

Configuring service jobs for Interpret and Transfer instances

Article # 3041445 - Page views: 48


Configure service jobs for Interpret and Transfer instances run as services

Use this procedure to configure service jobs as one of the steps to automate Interpret and Transfer.

The settings for service configurations are very flexible. Consequently, they must be configured carefully and tested to ensure jobs run correctly. For example, if two conditions, configured for the same service job, negate each other, the job may not run at all, or if service jobs with different conditions are set up in the wrong order, some jobs may never run resulting in invoices that cannot be processed.

Service jobs are configured two ways:

  • Multiple service jobs are created at the same time for multiple job descriptions.
  • A single service job is inserted in a specific place in the list of service jobs for an Interpret or Transfer instance.
Create service jobs for multiple job descriptions at the same time

Use the following procedure to create multiple service jobs at the same time. This is handy if you want to use the same advanced options for multiple services.

  1. In Manager, click the Service configurations object bar, right-click an Interpret or Transfer instance, and click Add job(s).  
  2. In the Job descriptions box, select one or more job descriptions for which you want to configure service jobs.
  3. In the Service job name box, specify a unique name. A separate service job is created for each job description selected in step two. The name of each service job includes the name of the job description and the name you specify resulting in service jobs with names in the format <job description name>_<unique name specified>. If the Service job name box is left empty, the name is in the format <job description name>_integer+1. Three job descriptions are selected in step two called InternalFax, and Collector, and they are in that order.
    • If the unique name specified in the Service job name box is ITRP1, the resulting service jobs receive the following names:
      • Internal_ITRP1
      • Fax_ITRP1
    • If the Service job name box is left empty, the resulting service jobs receive the following names:
      • Internal_1
      • Fax_2
      • COLLECTOR_3
  4. If desired, specify the time span, during which the job is run, under Run options > Time limits.  If nothing is specified here, the job always runs in the order it is found in the list. Note that if the times specified here conflict with time limits specified for the instance, the times for the instance override these.
  5. If desired, specify the length of time the job is idle before closing under Job control settings > Idle time between jobs. This can be useful when there is no information to process and the starting and stopping of jobs puts a strain on the CPU in connection with the application or database server.
  6. If desired, specify the amount of memory the job is allowed to use before the job is stopped and the next job is started under Job control settings > Memory limit.
  7. If desired, specify the maximum number of batches or invoices that are processed before stopping the job and starting the next one under Job control settings > Invoice/batch limit. This can be used to ensure that subsequent jobs in the list are processed. If nothing is specified here, the job runs until there are no additional invoices or batches to process.
  8. If desired, click Advanced conditions, right-click the area underneath, click Add condition, and configure advanced conditions to customize how and when service jobs are controlled. Note that this is not available by default. To enable it, the AdvancedJobCondition flag must be set to 1 in the [InvoiceServices] section of eilocal.ini. See INI file help for more information.
  9. If desired, specify No. of times to skip job after crash to configure how many times the job is to be skipped if it crashes. This can be helpful to keep production going if this job crashes. If you specify four here, for example, it means that if the job crashes at some point, it will not be run again until the fifth time it can be picked up.
  10. Click Enable to put the service jobs into use. If you do not want to do this for all service jobs created using the above procedure, this can also be done later separately for each job by right-clicking the resulting job in the list and clicking Enable.
    •  - Service jobs with this icon are enabled.
    •  - Service jobs with this icon are not enabled. They are skipped in the list if the instance is used in production.

 Note: Ensure both the instance and the service jobs it contains are configured correctly before enabling them.
  11. Click OK. As many service jobs are created under the current instance as job descriptions were selected in step two above.
Insert a single service job in a specific place in the list of jobs for an Interpret or Transfer instance

The procedure is the same as is described above for multiple service jobs except for starting the process. Right-click a job beneath which you want to insert another job, and then click Insert job below. In this case, only one job description can be selected from the Job description drop-down list, and the Service job name must be specified to be able to continue.

Change the order in which service jobs are run

Jobs run in the order they are listed from top to bottom under the Interpret or Transfer instance to which they belong. How and when they run also depends on the conditions that have been specified, if any.

Drag jobs up or down in the list to change the run order.

Enable or disable a service job for an Interpret or Transfer instance

Right-click a service job, and then click Enable or Disable depending on whether or not you want the job to run for the instance to which it belongs.

Note that to use a service job, the instance it belongs to must be enabled as well.

Delete individual service jobs

On the Service configurations object bar under the Interpret or Transfer instance to which it belongs, click the service job you want to delete and press Delete on the keyboard or right-click the instance and then click Delete.  


Level of Complexity 



Applies to  

Product Version Build Environment Hardware
Invoices 6      
  • Was this article helpful?