Background Job Repository for Automated ERP Maintenance
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current software delivery approaches for ERP systems require sophisticated scheduling of background jobs, which can be manual and dependent on subjective factors, leading to inefficiencies and incompatibility with customized software platforms, especially in multi-tenant systems where each tenant may have unique requirements.
Innovation Solution
A background job repository is implemented to store templates with metadata specifying the purpose, triggering information, and prerequisite features for background jobs, allowing for automated scheduling and maintenance, ensuring that only necessary jobs are executed in the customized software platform, and enabling updates and modifications based on changes in tenant-specific configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If background jobs are scheduled manually based on administrator experience and guidelines, then scheduling flexibility is maintained, but scheduling efficiency and consistency deteriorate
Solution Approach 1:
The system automatically determines which background jobs should be scheduled by comparing the current tenant-specific configuration against the job template repository, eliminating the need for manual administrator intervention while maintaining appropriate scheduling decisions
Solution Approach 2:
The system uses configuration parameters and metadata from job templates to automatically determine scheduling requirements, transforming manual experience-based decisions into automated parameter-driven decisions
2Reliability
If all background job templates are applied to every tenant, then comprehensive maintenance is ensured, but system complexity and resource consumption increase
Solution Approach 1:
Each tenant receives a customized subset of background jobs based on their specific configuration and requirements, rather than applying a uniform set to all tenants. The system evaluates each job template's prerequisite features against the tenant's actual configuration to determine local applicability
Solution Approach 2:
The background job repository is segmented into multiple templates with different prerequisite features and tenant applicability criteria. The system divides the overall maintenance task into individual job templates that can be selectively applied to different tenants based on their specific needs
3Adaptability or versatility
If manual scheduling approaches are used, then adaptability to individual tenant needs is possible, but time consumption and operational overhead increase
Solution Approach 1:
Job templates are pre-configured with metadata including prerequisite features, triggering information, and tenant applicability criteria. This preliminary preparation enables automated matching and scheduling without requiring time-consuming manual analysis for each tenant
Solution Approach 2:
The system automatically monitors tenant configurations and determines which background jobs should be scheduled by comparing current state against job template requirements, providing adaptive scheduling without manual intervention
Data Source
AI summary
Aspects of the current subject matter can provide a background job repository that stores a background job template specifying a background job comprising a maintenance task that affects a customized software platform. The background job template can also include metadata defining a purpose of the background job, triggering information indicating when the background job should be executed, and a prerequisite feature of the customized software platform that indicates a need for the background job in the customized software platform. A previous set of background jobs that run in the customized software platform can be updated to a current set by comparing the previous set with the background job template and including the background job in the current set of background jobs when the customized software platform includes the prerequisite feature.