Reference
Job Execution Services
This topic lists the Windows services that APM uses for job execution, and the job type each service handles. You can start or stop the Windows service based on your requirement. You can configure the MaxConcurrencyPerTenant value in the appsettings.global.json file.
| Service Name | Supported Job Types | Output in Job Monitoring Dashboard | MaxConcurrencyPerTenant |
|---|---|---|---|
| Meridium Job Executor | Export Untranslated Strings | The exported translation excel file can be downloaded | NA |
| LDAP sync | NA | 5 | |
| Export | The exported zip file can be downloaded | NA | |
| Import | NA | NA | |
| Meridium.Service.Search | Global Search Rebuild | NA | NA |
| MIExecution Service | Risk Based Inspection | NA | 5 |
| Inspection Management | NA | 5 | |
| Integrity Mobile | NA | NA | |
| Thickness Monitoring | NA | 5 | |
| Meridium.Service.AsiExecution | ASI Package | NA | 5 |
| Meridium.Service.AsmExecution | ASM Strategy | NA | 5 |
| ASM Template | NA | 5 | |
| ASM Export | The exported zip file can be downloaded | 1 | |
| Meridium.Service.AsmImpExecution | ASM Overview | NA | 1 |
| ASM Implementation | NA | 1 | |
| Recommendation | NA | 10 | |
| Meridium.Service.AsmSysExecution | System Strategy | NA | 10 |
| Meridium.Service.RcmAcaExecution | ACA Overview | NA | 1 |
| ACA Analysis | NA | 5 | |
| RCM FMEA | NA | 5 | |
| RCM FMEA Export | The exported zip file can be downloaded | 1 | |
| ACA Export | The exported zip file can be downloaded | 1 | |
| Meridium.Service.ReliabilityExecution | RCA Email Alert | Short job description. For example:
| NA |
| Meridium GAA Wind Event Import Service | Event Import Job | The log file can be downloaded | 16 |
| Report Generation Job | The log file can be downloaded | 16 | |
| Meridium.Service.GAA | Bulk Generation Job | The log file can be downloaded | 5 |
| Import Job | The log file can be downloaded | 5 | |
| Meridium.Service.eLog | Recommendation Alert Job | The log file can be downloaded | 16 |
Schedule Statuses
The Job Monitoring Dashboard page shows the status of the various jobs that are scheduled in the APM system.
The Job Monitoring Dashboard page contains the following sections:
- In Progress: When a job is running, it appears in the In Progress section. On completion of the scheduled run process, the result is either Successful or Failed.Note: At any given time, only five scheduled jobs will be running. The other jobs will be in queue.
- Successful: If the scheduled job completes without any errors, the job appears in the Successful section.
- Failed: If the scheduled job fails due to an error occurs, the job appears in the Failed section. This section also displays the error details.Note: If a job stops due to server failure or shut down, then the schedule status is displayed as Failed.
- Cancelled: If the scheduled job is cancelled by the user, the job appears in the Cancelled section.
Family Field Descriptions
The following table lists the fields that are available in the In Progress, Successful, Failed , and Cancelled sections of the Job Monitoring Dashboard page.
| Fields | Type | Description | Behavior and Usage |
|---|---|---|---|
| Cancelled | Date | The time at which the scheduled job was cancelled. | The filed is automatically populated based on the time when the job was cancelled. You can sort the cancelled jobs in ascending or descending order based on the time at which it was cancelled. |
| Reason for Cancellation | Text | The reason specified when cancelling the job. | The filed is automatically populated based on the input provided as the reason for cancellation while cancelling the job. |
| Description | Text | The description that you have provided for the scheduled job. | The filed is populated automatically based on the description that you have provided for the job. Tip: It is recommended that you provide the name of the job for which you are scheduling an operation. |
| Download Log | N/A | The log for the jobs that are completed. | You can select the download button ( ) to download the log file for the scheduled jobs that are completed and are in a Successful, Failed, or Cancelled state. |
| Error Details | Text | The details of the error. | This field appears in the Failed section and is automatically populated. |
| Next Execution | Date | The time at which the next occurence of the job is scheduled. | This field appears in the Successful and Failed sections and is automatically populated. You can sort the scheduled jobs in ascending or descending order based on the next occurence time. |
| Percent Complete | Number | The percentage completion of the scheduled job. | This field appears in the In progress section and is automatically populated. |
| Runtime (Seconds) | Number | The time taken for the completion of a scheduled job. | This field appears in the Successful section and is automatically populated. |
| Started | Date | The time at which the schedule process started. | The fiels is automatically populated based on the schedule defined for the job. You can sort the scheduled jobs in ascending or descending order based on the start time. |
| Type | Text | The type of job that is scheduled. | The fiels is automatically populated based on the schedule that you have defined for job. For example, if you have scheduled a KPI to be updated at a particular time period via the Schedule, Alerts and Privileges section, then the In Progress section displays the type as KPI. |
Examples
This topic contains some scenarios that will help you understand the scheduling interval.
Scenario 1: Run a weekly job
This example explains how to schedule a weekly job. For this example, let us consider the following requirements for the weekly job:
- The first instance of the job must run on 21st December 2020 at 10:30 PM PST (UTC -08:00).
- After the first instance, the job must run every two weeks on Mondays and Wednesdays.
- The scheduled job must stop after 10 occurrences.
To schedule a job as per these requirements, you must configure the following options in the Edit Schedule window:
- In the Repeat Interval box, select Weekly.
- In the Next Occurrence section, in the Repeat Every box, enter 2.
- In the Repeat On box, select the check boxes corresponding to Monday and Wednesday.
- In the Start Date box, specify the first instance of the job using the clock option. In this case, the start date must be 12/21/20 10:30 PM.
- In the End Repeat section, select After, and then specify 10 in the box.
- In the Timezone box, set the Time Zone to (UTC-08:00) Pacific Time (US & Canada).
- Verify the Summary section.
- Select Save.
The job is scheduled to run on 21st December 2020 at 10:30 PM PST, and then occurs every 2 weeks on Monday and Wednesday, and ends after 10 occurrences.
Scenario 2: Run a monthly job
This example explains how to schedule a monthly job. For this example, let us consider the following requirements for the monthly job:
- The job must run on the first Monday of every month.
- The first job must run on 1st March 2021 at 9:00 AM PST (UTC -08:00).
- There is no end date specified for the job.
To schedule a job as per these requirements, you must configure the following options in the Edit Schedule window:
- In the Repeat Interval box, select Monthly.
- In the Next Occurrence section, select the third radio button so that you can specify a month, week, and day for the scheduled job.
- Specify the following details:
- Repeat Every: 1 Month(s) of
- First Week
- On Monday
- In the Start Date box, specify the first instance of the job using the clock option. In this case, the start date must be 03/01/21 9:00 AM.
- In the End Repeat section, select Never.
- In the Timezone box, set the Time Zone to (UTC-08:00) Pacific Time (US & Canada).
- Verify the Summary section.
- Select Save.
The job is scheduled to run on 1st March 2021 at 9:00 AM PST, and then occurs on the first Monday of every month.
Scenario 3: Run a yearly job
This example explains how to schedule a yearly job. For this example, let us consider the following requirements for the monthly job:
- The job must run on the last Friday of every year.
- The first job must run on 31st December 2021 at 9:00 AM PST (UTC -08:00).
- The schedule job must stop after 5 years.
To schedule a job as per these requirements, you must configure the following options in the Edit Schedule window:
- In the Repeat Interval box, select Yearly.
- In the Next Occurrence section, select the third radio button to specify a year, month, week, and day for the scheduled job.
- Specify the following details:
- Repeat Every: 1 Year(s) on
- December on
- Last Week
- On Friday
- In the Start Date box, specify the first instance of the job using the clock option. In this case, the start date must be 12/31/21 9:00 AM.
- In the End Repeat section, select After, and then specify 5.
- In the Timezone box, set the Time Zone to (UTC-08:00) Pacific Time (US & Canada).
- Verify the Summary section.
- Select Save.
The job is scheduled to run on 31st December 2021 at 9:00 AM PST, and then occur on the last Friday of every year.