WO2019223178A1 - Cross-platform task scheduling method and system, computer device, and storage medium - Google Patents

Abstract

The present application relates to a cross-platform task scheduling method and system, a computer device, and a storage medium. The method comprises: configuring parameter information for task scheduling and storing same into a scheduling platform database; deploying an execution template and using same to convert an SSH in a scheduling platform server into an SSH in an ORACLE ODI or ESSBASE server for executing task scheduling; and grabbing task information serving a scheduling condition and the parameter information, splicing same into an executable scheduling task, and using the SSH in the ORACLE ODI or ESSBASE server to execute the scheduling task for carrying out cross-platform task scheduling. According to the method, a complete dependent flow and data processing flow can be formed for different types of tasks in the whole project, thereby significantly saving the development manpower on which scheduling and cross-platform tools rely, and making it convenient for the operation & maintenance staff to perform batch operations and task monitoring on the whole data flow.

Description

Cross-platform task scheduling method, system, computer equipment and storage medium

This application claims the priority of a Chinese patent application filed on May 21, 2018 with the Chinese Patent Office, application number 201810487527.X, and the invention name "Cross-platform task scheduling method, system, computer equipment and storage medium", all of which The contents are incorporated herein by reference.

Technical field

The present application relates to the technical field of task scheduling, and in particular, to a cross-platform task scheduling method, system, computer device, and storage medium.

Background technique

ORACLE ODI (Oracle Data Integrator) is a data integration tool of Oracle. It is a data extraction / data conversion tool designed using the concept of E-LT. ESSBASE is a multi-dimensional database of BI software hyperion. Unlike a relational database in the usual sense, ESSBASE divides data into "blocks", and each data defines a different dimension. There is only one scheduling method and device based on HIVE tasks, which involves the scheduling methods of ORACLE ODI and ESSBASE. Although this method is the ORACLE ODI scheduling method, this method still has many disadvantages, which are as follows:

1. The existing tools in the industry only implement the scheduling methods of ORACLE ODI or ESSBASE separately. There is no special tool sufficient to implement the cross-platform, cross-tool scheduling methods of ORACLE ODI and ESSBASE tasks.

2. The existing scheduling methods that implement Oracle ODI or ESSBASE cannot achieve dependence on existing big data SQOOP tasks and HIVE tasks;

3. Existing scheduling methods that implement Oracle ODI or ESSBASE cannot form a complete data processing flow that is intuitive and easy to deploy and manage.

Summary of the Invention

Based on this, it is necessary to provide cross-platform task scheduling methods for a series of problems such as the inability to implement ODILE or ESSBASE task scheduling and the formation of an intuitive, easy-to-deploy complete data processing flow. Systems, computer equipment, and storage media.

A cross-platform task scheduling method includes:

S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database;

S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server;

S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling.

Based on the same technical concept, this application also provides a cross-platform task scheduling system, including:

The configuration unit is configured to configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in a scheduling platform database;

The deployment unit is configured to use the Oracle ODI or ESSBASE execution template to deploy the Oracle ODI or ESSBASE execution template to convert the SSH in the scheduling platform server to the Oracle ODI or ESSBASE server to execute the Oracle ODI or ESSBASE server. Task scheduling

The execution unit is configured to capture task information serving ORACLE or ODI or ESSBASE scheduling conditions and stitch the parameter information into executable ODI or ODI or ESSBASE scheduling tasks, and execute ORACLE or ODI using SSH in ORACLE or ESSBASE server Or ESSBASE scheduling tasks, cross-platform task scheduling.

Based on the same technical concept, the present application also provides a computer device including a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processing causes the processing. The processor performs the following steps:

S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database;

S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server;

S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling.

Based on the same technical concept, the present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the following steps:

S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database;

S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server;

S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling.

The above-mentioned cross-platform task scheduling method, system, computer equipment and storage medium, by setting a parameter template table and a parameter routing table in a scheduling platform database, and configuring ORACLE ODI or ESSBASE for task scheduling according to the parameter template table and parameter routing table. Parameter information, and store the parameter information in the scheduling platform database; set up a database table in the scheduling platform database, use the scheduling platform server to read SSH account information, help SSH log in to the scheduling platform server, and install python on the scheduling platform Program, use it to write ORACLE ODI or ESSBASE execution modules, and then deploy ORACLE ODI or ESSBASE execution templates, and then use it to convert SSH in the scheduling platform server to SSH in ORACLE ODI or ESSBASE server to execute ORACLE ODI or ESSBASE server Task scheduling; the scheduling platform server continuously polls the scheduling platform configuration library through ORACLE ODI or ESSBASE execution modules, grabs task information that serves ORACLE ODI or ESSBASE scheduling conditions, and obtains ORACLE ODI or ESSBASE scheduling conditions from the scheduling platform database of Parameter information. The Oracle ODI or ESSBASE execution module will stitch the task information and parameter information into executable Oracle ODI or ESSBASE scheduling tasks. Use ORACLE ODI or SSH in the ESSBASE server to execute Oracle ODI or ESSBASE scheduling tasks to make the entire project Various types of tasks can form a complete dependency flow and data processing flow, which greatly saves the development manpower on scheduling and cross-platform tool dependency, which greatly facilitates the operation and maintenance personnel's batch operation and task monitoring of the entire data flow.

BRIEF DESCRIPTION OF THE DRAWINGS

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the detailed description of the preferred embodiments below. The drawings are only for the purpose of illustrating preferred embodiments and are not to be considered as limiting the present application.

1 is a flowchart of a cross-platform task scheduling method according to an embodiment of the present application;

2 is a flowchart of configuring parameter information in an embodiment of the present application;

3 is a flowchart of a deployment execution module according to an embodiment of the present application;

4 is a flowchart of performing a scheduling task in an embodiment of the present application;

5 is a schematic diagram of a cross-platform task scheduling system according to an embodiment of the present application;

6 is a schematic diagram of configuration parameter information in an embodiment of the present application;

7 is a schematic diagram of a deployment execution module in an embodiment of the present application;

FIG. 8 is a schematic diagram of performing a scheduling task in an embodiment of the present application.

Detailed ways

In order to make the purpose, technical solution, and advantages of the present application clearer, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the application, and are not used to limit the application.

It will be understood by those skilled in the art that the singular forms "a", "an", "the" and "the" may include plural forms unless specifically stated otherwise. It should be further understood that the wording "including" used in the specification of the present application refers to the presence of the described features, integers, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, Integers, steps, operations, elements, components, and / or groups thereof.

As shown in FIG. 1, this application provides a cross-platform task scheduling method, including:

Step S1: Configure the parameter information of Oracle ODI or ESSBASE for task scheduling, and store the parameter information in the database of the scheduling platform; Step S2: Deploy the Oracle ODI or ESSBASE execution template and use the Oracle ODI or ESSBASE execution template to transfer the information in the scheduling platform server. SSH is converted into Oracle or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server; Step S3: Capture task information and parameter information serving ORACLE ODI or ESSBASE scheduling conditions and stitch them into executable ODI ODI Or ESSBASE scheduling tasks, and use Oracle ODI or SSH in the ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks to perform cross-platform task scheduling.

The scheduling platform in this embodiment may select ZooKeeper. ZooKeeper is an open and open source distributed application coordination service. It is an open source implementation of Google's Chubby and an important component of Hadoop and Hbase. ZooKeeper is a software that provides consistent services for distributed applications. The functions it can provide include configuration maintenance, domain name services, distributed synchronization, and group services. It can implement key services that are complex and error-prone, and will be easy to use. The interface and efficient and stable system are provided to users. Set the scheduling platform database on the ZooKeeper scheduling platform, save the configuration information of ORACLE ODI or ESSBASE, deploy ORACLE ODI or ESSBASE execution modules, and convert SSH to provide a stable operating environment for scheduling ORACLE ODI or ESSBASE tasks using SSH.

In this embodiment, an Oracle database may be used as the scheduling platform database. Oracle database is currently the world's leading relational database relational system. Its system is portable, easy to use, and powerful. It is suitable for various large, medium, small, and microcomputer environments. Storing the completed ODI or ODI or ESSBASE parameter information in the Oracle database can ensure the stability of ORACLE ODI or ESSBASE parameter information, and can adapt to the storage of parameter information of different reserves. When using the ORACLE ODI or ESSBASE execution module for grabbing, it can quickly locate the required ODILE or ESSBASE parameter information.

The scheduling platform server in this embodiment may select a Linux server. The Linux server is a network server using the Linux system for business processing applications, such as network and system management, database management, and Web services. It is a server with high performance and open source. The Linux server has excellent system stability and security. Because it uses a multi-user operating system, it has good flexibility and scalability. It can accommodate resources well regardless of the processor or machine architecture. The software on the Linux server is free, so the Linux server can save costs in application development. Most user services can be developed more freely with Linux systems.

The ORACLE ODI or ESSBASE task scheduling method enables various types of tasks in the entire project to form a complete dependency flow and data processing flow, which greatly saves the development manpower in scheduling and cross-platform tool dependency, which greatly facilitates operation. Maintenance personnel monitor the batch operations and tasks of the entire data flow.

FIG. 2 is a flowchart of configuring parameter information according to an embodiment of the present application. As shown in FIG. 2, in step S1, parameter information of ODILE or ESSBASE for task scheduling is configured through a parameter template table and a parameter routing table. This embodiment Step S1 may include S101-S103:

Step S101: Set the Oracle database on the scheduling platform, and set the parameter template table and parameter routing table of ODILE or ESSBASE in the parameter routing table. The parameter routing table is based on the historical record stored in the Oracle database, and one parameter corresponds to one record. The generated form; as shown in Table 1 below, when generating the parameter template table, according to the historical records of parameters such as task name, date, and time type stored in the Oracle database, a parameter template table is generated by using one parameter corresponding to one record;

Table 1

The parameter routing table includes how many parameter items each parameter has and a path for obtaining information under each parameter item, and the parameter routing table is shown in Table 2 below;

Table 2

Step S102: Select the number of parameters and parameter names required by the Oracle ODI or ESSBASE task when scheduling, and configure according to the parameter routing table to obtain the parameter item corresponding to the parameter name; for example, the parameter name is "date ", Then in the parameter template table shown in Table 1 above," date "is positioned as the parameter item" inc_time ";

Step S103: Configure the parameter information under the parameter item according to the parameter routing table; for example, the parameter item is "inc_time", and according to the parameter routing table shown in Table 2 above, it can be known according to "inc_time" "Inc_time" contains two item categories, "inc_start" and "inc_end".

The foregoing configuration of ORACLE ODI or ESSBASE parameter information provides preparation conditions for splicing into executable ODI OESS or ESSBASE scheduling tasks.

FIG. 3 is a flowchart of deploying an execution module according to an embodiment of the present application. As shown in FIG. 3, in step S2, read the SSH account information, log in to SSH to the scheduling platform server, and use the python program on the scheduling platform to use It compiles Oracle ODI or ESSBASE execution modules, deploys ORACLE ODI or ESSBASE execution modules, and then uses the ORACLE ODI or ESSBASE execution modules to convert SSH in the scheduling platform into ORACLE ODI or ESSBASE servers. In this implementation, step S2 may include S201-S203;

Step S201: setting a database table in the database of the scheduling platform, where the database table stores SSH account information, and the scheduling platform server reads the SSH account information from the database table to help SSH login to the scheduling platform server;

In one embodiment, the SSH account information includes ORACLE ODI or ESSBASE server IP information, user information, and password information. The database table is shown in Table 3 below:

Server_name Varchar2 (100) server nickname Server_ip Varchar2 (100) Server IP Server_user Varchar2 (100) user Server_pwd Varchar2 (64) password

table 3

The dispatch platform server reads according to the information shown in Table 3 above, reads the corresponding dispatch platform server name according to "Server_name", reads the IP information of the dispatch platform server, account based on "Server_ip", "Server_user" and "Server_pwd". Information and password information.

Step S202: Install a python program on the scheduling platform, and use the python program to write an Oracle ODI or ESSBASE execution module. After SSH logging in to the scheduling platform server, upload the ORACLE ODI or ESSBASE execution module program to the scheduling platform server using SSH Secure Shell. To complete the deployment of the Oracle ODI or ESSBASE execution module;

The python program in this embodiment is free software. The source code and interpreter CPython follow the CPL protocol, and its syntax is concise and clear. Python has a rich and powerful library that can easily link various modules (especially C / C ++) made in other languages. Install a Python program on the scheduling platform. You can use this program to quickly and easily write ORACLE ODI or ESSBASE execution modules.

Step S203: Use ORACLE ODI or ESSBASE execution module to convert SSH logged in to the scheduling platform server into ORACLE ODI or ESSBASE server.

In this embodiment, the Oracle ODI or ESSBASE execution module inherits the base class of the scheduling platform to implement functions such as Oracle ODI or ESSBASE task execution, abnormal return, log recording, error log extraction, and number of recorded logs. At the same time, it can implement scheduling The SSH in the platform server is converted into OSSH in Oracle ODI or ESSBASE server to achieve the connection between ORACLE ODI and ESSBASE scheduling tasks.

In the above, the SSH in the scheduling platform server is converted into the SSH in ORACLE ODI or ESSBASE server, and an execution component is provided for the next step of ORACLE ODI or ESSBASE task scheduling.

FIG. 4 is a flowchart of executing a scheduling task according to an embodiment of the present application. As shown in FIG. 4, in step S3, the executable ODI or ESSBASE scheduling task is spliced and executed by using ORACLE or SSH in the ESSBASE server. ORACLE, ODI or ESSBASE scheduling task. In this embodiment, step S3 includes S301-S303;

Step S301: Fill in a deployment document of a scheduled ORACLE or ESSBASE task schedule on a scheduling platform.

Step S302: Import the deployment document into a web interface through a scheduling platform, and store information in the imported deployment document into a scheduling platform configuration library.

The deployment document in this embodiment is filled with an EXCEL-type deployment document, and records information such as the server name, program path, scheduling time, and scheduling frequency corresponding to the Oracle ODI or ESSBASE task. After filling in the deployment document, you can import it to the web interface and import it as a web page.

Step S303: The scheduling platform server continuously polls the scheduling platform configuration library through the Oracle ODI or ESSBASE execution module, grabs task information serving the scheduling conditions of ORACLE ODI or ESSBASE, and obtains from the database of the scheduling platform that meets the ODI or ESSBASE scheduling conditions. For parameter information, the Oracle ODI or ESSBASE execution module will stitch the task information and parameter information into executable Oracle ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in the ESSBASE server to perform Oracle ODI or ESSBASE scheduling tasks.

The above calls ORACLE ODI or SSH in the ESSBASE server to execute ORACLE ODI or ESSBASE scheduling tasks to achieve cross-platform task scheduling of ORACLE ODI and ESSBASE tasks.

Based on the same technical concept, the embodiment of the present application also provides a cross-platform task scheduling system, as shown in FIG. 5, including: a configuration unit, configured to configure ORACLE ODI or ESSBASE parameter information for task scheduling, and parameter information Stored in the scheduling platform database; the deployment unit is set to deploy ORACLE ODI or ESSBASE execution templates and use it to convert SSH in the scheduling platform server to SSH in ORACLE ODI or ESSBASE server to perform tasks in ORACLE ODI or ESSBASE server Scheduling; execution unit, which is set to capture task information and parameter information that serve the scheduling conditions of Oracle ODI or ESSBASE and stitch them into executable Oracle ODI or ESSBASE scheduling tasks, and execute ORACLE ODI or ESSBASE by using ORACLE or SSH in the ESSBASE server Schedule tasks and perform cross-platform task scheduling.

FIG. 6 is a schematic diagram of configuration parameter information according to an embodiment of the present application. As shown in FIG. 6, the configuration unit includes a setting module configured to set an Oracle database on a scheduling platform and set a parameter template table of ORACLE ODI or ESSBASE therein. And parameter routing table. The parameter routing table is a table generated by using a parameter corresponding to a record according to the historical records stored in the Oracle database. The parameter routing table contains how many parameter items each parameter has and how many The path for obtaining information under each parameter; the parameter acquisition module is set to the number of parameters and parameter names required by the selected ODILE or ESSBASE task for scheduling, and is configured according to the parameter routing table to obtain the parameters corresponding to the parameter name Item; a configuration parameter information module configured to configure parameter information under the parameter item according to a parameter routing table.

FIG. 7 is a schematic diagram of a deployment execution module according to an embodiment of the present application. As shown in FIG. 7, the execution module includes a login module configured to set a database table in a scheduling platform database. The database table stores SSH account information. Read the SSH account information in the database table to help SSH login to the scheduling platform server; deploy the execution module, set to install a python program on the scheduling platform, and use the python program to write ORACLE ODI or ESSBASE execution modules, and SSH to log in to the scheduling platform server Then upload the ORACLE ODI or ESSBASE execution module program to the scheduling platform server using SSH Secure Shell to complete the deployment of the ODILE or ESSBASE execution module; the conversion module is set to use ORACLE ODI or ESSBASE execution module to log in to the dispatch platform server SSH into ODI or ODI or ESSBASE server.

FIG. 8 is a schematic diagram of executing a scheduling task according to an embodiment of the present application. As shown in FIG. 8, it includes: a filling module configured to fill in a deployment file of a predetermined format type ORACLE ODI or ESSBASE task scheduling on a scheduling platform; import and save Module, set to import the deployment document to the web interface through the dispatch platform, and store the information in the imported deployment document to the dispatch platform configuration library; execute the dispatch task module, set to the dispatch platform server to execute the module via ORACLE ODI or ESSBASE Constantly poll the scheduling platform configuration library, grab the task information that serves the ODI or ESSBASE scheduling conditions, and obtain parameter information that meets the ODILE or ESSBASE scheduling conditions from the scheduling platform database. The ORACLE ODI or ESSBASE execution module will The task information and parameter information are spliced into executable Oracle ODI or ESSBASE scheduling tasks, and Oracle ODI or SSH in the ESSBASE server is used to perform ORACLE ODI or ESSBASE scheduling tasks.

In one embodiment, the scheduling platform adopts a distributed application coordination service ZooKeeper, a scheduling platform database is preset on ZooKeeper, and parameter information of ORACLE ODI or ESSBASE is stored.

Based on the same technical concept, this application proposes a computer device. The computer device includes a memory, a processor, and computer-readable instructions stored on the memory and executable on the processor. The processor implements the computer-readable instructions to implement the foregoing. Steps in the cross-platform task scheduling method in each embodiment.

Based on the same technical concept, the present application also provides a storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps in the foregoing embodiments. Steps in a platform task scheduling method.

A person of ordinary skill in the art can understand that all or part of the processes in the methods of the foregoing embodiments can be implemented by using a computer program to instruct related hardware. The computer program can be stored in a computer-readable storage medium. When executed, the processes of the embodiments of the methods described above may be included. The storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disc, a read-only memory (ROM), or a random access memory (Random Access Memory, RAM).

The technical features of the embodiments described above can be arbitrarily combined. In order to simplify the description, all possible combinations of the technical features in the above embodiments have not been described. However, as long as there is no contradiction in the combination of these technical features, It should be considered as the scope described in this specification.

The above-mentioned embodiments only express several implementation manners of the present application, and their descriptions are more specific and detailed, but they should not be construed as limiting the patent scope of the present application. It should be noted that, for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of this application patent shall be subject to the appended claims.

Claims (20)

A cross-platform task scheduling method includes: S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database; S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server; S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling. The cross-platform task scheduling method according to claim 1, wherein the step S1 comprises: S101: Set up an Oracle database on the scheduling platform, and set therein a parameter template table and a parameter routing table of ODILE or ESSBASE. The parameter routing table is based on the historical records stored in the Oracle database, and one parameter corresponds to one. A form generated by recording, the parameter routing table includes how many parameter items each parameter has and a path for obtaining information under each parameter item; S102: Select a parameter name required by the Oracle ODI or ESSBASE task when scheduling, and configure according to the parameter routing table to obtain a parameter item corresponding to the parameter name; S103: Configure parameter information under the parameter item according to the parameter routing table. The cross-platform task scheduling method according to claim 1, wherein the step S2 comprises: S201: A database table is set in the database of the scheduling platform, the database table stores SSH account information, and the scheduling platform server reads the SSH account information from the database table to help SSH login to the scheduling platform server; S202: Install a python program on the scheduling platform, and use the python program to write an Oracle ODI or ESSBASE execution module. After logging in to the scheduling platform server via SSH, upload the ORACLE ODI or ESSBASE execution module program to the scheduling platform server using SSH Secure Shell. To complete the deployment of the Oracle ODI or ESSBASE execution module; S203: Use ORACLE ODI or ESSBASE execution module to convert SSH logged in to the scheduling platform server into ORACLE ODI or ESSBASE server. The cross-platform task scheduling method according to claim 1, wherein the step S3 comprises: S301: Fill in the deployment document of the ODILE or ESSBASE task scheduling preset type on the scheduling platform; S302: Import the deployment document into a web interface through a scheduling platform, and store information in the imported deployment document into a scheduling platform configuration library; S303: The scheduling platform server continuously polls the scheduling platform configuration library through the Oracle ODI or ESSBASE execution module, grabs the task information that serves the scheduling conditions of ORACLE ODI or ESSBASE, and obtains parameters that meet the ODILE or ESSBASE scheduling conditions from the database of the scheduling platform Information, the Oracle ODI or ESSBASE execution module will stitch the task information and parameter information into executable Oracle ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in the ESSBASE server to execute ORACLE ODI or ESSBASE scheduling tasks. The cross-platform task scheduling method according to claim 1, wherein the scheduling platform uses a distributed application coordination service ZooKeeper, presets the scheduling platform database on the ZooKeeper, and stores parameters of ORACLE ODI or ESSBASE information. A cross-platform task scheduling system includes: The configuration unit is configured to configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in a scheduling platform database; The deployment unit is configured to use the Oracle ODI or ESSBASE execution template to deploy the Oracle ODI or ESSBASE execution template to convert the SSH in the scheduling platform server to the Oracle ODI or ESSBASE server to execute the Oracle ODI or ESSBASE server. Task scheduling The execution unit is configured to capture task information serving ORACLE or ODI or ESSBASE scheduling conditions and stitch the parameter information into executable ODILE or ESSBASE scheduling tasks, and execute ORACLE ODI using ORACLE or SSH in the ESSBASE server. Or ESSBASE scheduling tasks, cross-platform task scheduling. The cross-platform task scheduling system according to claim 6, wherein the configuration unit includes a setting module, a parameter acquisition module, and a configuration parameter information module; The setting module is configured to set an Oracle database on a scheduling platform, and set therein a parameter template table and a parameter routing table of ORACLE ODI or ESSBASE, and the parameter routing table is based on a historical record stored in the Oracle database, A table generated by using a parameter corresponding to a record, the parameter routing table includes how many parameter items each parameter has and a path for obtaining information under each parameter item; The parameter obtaining module is set to a parameter name required by the selected Oracle ODI or ESSBASE task when scheduling, and is configured according to the parameter routing table to obtain a parameter item corresponding to the parameter name; The configuration parameter information module is configured to configure parameter information under the parameter item according to the parameter routing table. The cross-platform task scheduling system according to claim 6, wherein the deployment unit comprises a login module, a deployment execution module module, and a conversion module; The login module is configured to set a database table in a database of the scheduling platform, where the database table stores SSH account information, and the scheduling platform server reads the SSH account information from the database table to help SSH login to the scheduling platform server ; The deployment execution module is configured to install a python program on a dispatch platform and use the python program to write an Oracle ODI or ESSBASE execution module. After SSH logging in to the dispatch platform server, use SSH Secure Shell to run the ORACLE ODI or ESSBASE execution module program. Upload to the scheduling platform server to complete the deployment of ORACLE ODI or ESSBASE execution modules; The conversion module is configured to use Oracle ODI or ESSBASE execution module to convert SSH logged in to the scheduling platform server into ORACLE ODI or ESSBASE server. The cross-platform task scheduling system according to claim 6, wherein the execution unit includes a filling module, an import saving module, and an execution scheduling task module; The filling module is configured to fill in a deployment document of a predetermined format type ORACLE ODI or ESSBASE task scheduling on a scheduling platform; The import and save module is configured to import the deployment document to a web interface through a scheduling platform, and store information in the imported deployment document into a scheduling platform configuration library; The execution scheduling task module is configured to schedule the platform server to continuously poll the scheduling platform configuration library through the Oracle ODI or ESSBASE execution module, grab the task information serving the scheduling conditions of Oracle ODI or ESSBASE, and obtain the ORACLE from the database of the scheduling platform. ODI or ESSBASE scheduling parameter information. ORACLE ODI or ESSBASE execution module will stitch the task information and parameter information into executable ODILE or ESSBASE scheduling tasks. Use ORACLE ODI or SSH in ESSBASE server to execute ORACLE ODI or ESSBASE. Scheduling tasks. The cross-platform task scheduling system according to claim 6, wherein the scheduling platform adopts a distributed application coordination service ZooKeeper, presets the scheduling platform database on the ZooKeeper, and stores parameters of ORACLE ODI or ESSBASE information. A computer device includes a memory and a processor. The memory stores computer-readable instructions. When the computer-readable instructions are executed by the processor, the processor causes the processor to perform the foregoing steps: S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database; S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server; S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling. The computer device according to claim 11, wherein the step S1 causes the processor to perform the above steps: S101: Set up an Oracle database on the scheduling platform, and set therein a parameter template table and a parameter routing table of ODILE or ESSBASE. The parameter routing table is based on the historical records stored in the Oracle database, and one parameter corresponds to one. A form generated by recording, the parameter routing table includes how many parameter items each parameter has and a path for obtaining information under each parameter item; S102: Select a parameter name required by the Oracle ODI or ESSBASE task when scheduling, and configure according to the parameter routing table to obtain a parameter item corresponding to the parameter name; S103: Configure parameter information under the parameter item according to the parameter routing table. The computer device according to claim 11, wherein the step S2 causes the processor to perform the above steps: S201: A database table is set in the database of the scheduling platform, the database table stores SSH account information, and the scheduling platform server reads the SSH account information from the database table to help SSH login to the scheduling platform server; S202: Install a python program on the scheduling platform, and use the python program to write an Oracle ODI or ESSBASE execution module. After SSH login to the scheduling platform server, upload the ORACLE ODI or ESSBASE execution module program to the scheduling platform server using SSH Secure Shell To complete the deployment of the Oracle ODI or ESSBASE execution module; S203: Use ORACLE ODI or ESSBASE execution module to convert SSH logged in to the scheduling platform server into ORACLE ODI or ESSBASE server. The computer device according to claim 11, wherein the step S3 causes the processor to perform the above steps: S301: Fill in the deployment document of the ODILE or ESSBASE task scheduling preset type on the scheduling platform; S302: Import the deployment document into a web interface through a scheduling platform, and store information in the imported deployment document into a scheduling platform configuration library; S303: The scheduling platform server continuously polls the scheduling platform configuration library through the Oracle ODI or ESSBASE execution module, grabs the task information that serves the scheduling conditions of ORACLE ODI or ESSBASE, and obtains parameters that meet the scheduling conditions of ORACLE ODI or ESSBASE from the database of the scheduling platform. Information, the Oracle ODI or ESSBASE execution module will stitch the task information and parameter information into executable Oracle ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in the ESSBASE server to execute ORACLE ODI or ESSBASE scheduling tasks. The computer device according to claim 11, wherein the scheduling platform adopts a distributed application coordination service ZooKeeper, and further causes the processor to perform the above steps: The scheduling platform database is preset on the ZooKeeper, and parameter information of ORACLE ODI or ESSBASE is stored. A storage medium storing computer-readable instructions. When the computer-readable instructions are executed by one or more processors, the one or more processors execute the above steps: S1: configure ORACLE ODI or ESSBASE parameter information for task scheduling, and store the parameter information in the scheduling platform database; S2: After deploying the ODI or ODI or ESSBASE execution template, use the ODI or ODI or ESSBASE execution template to convert SSH in the scheduling platform server to ORACLE or ODI or ESSBASE server to perform task scheduling in ORACLE ODI or ESSBASE server; S3: Capture task information serving ORACLE ODI or ESSBASE scheduling conditions and the parameter information to splice into executable ODI ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in ESSBASE server to perform ORACLE ODI or ESSBASE scheduling tasks, Perform cross-platform task scheduling. The storage medium according to claim 16, wherein the step S1 causes one or more processors to perform the above steps: S101: Set up an Oracle database on the scheduling platform, and set therein a parameter template table and a parameter routing table of ODILE or ESSBASE. The parameter routing table is based on the historical records stored in the Oracle database, and one parameter corresponds to one. A form generated by recording, the parameter routing table includes how many parameter items each parameter has and a path for obtaining information under each parameter item; S102: Select a parameter name required by the Oracle ODI or ESSBASE task when scheduling, and configure according to the parameter routing table to obtain a parameter item corresponding to the parameter name; S103: Configure parameter information under the parameter item according to the parameter routing table. The storage medium according to claim 16, wherein the step S2 causes one or more processors to perform the above steps: S201: A database table is set in the database of the scheduling platform, the database table stores SSH account information, and the scheduling platform server reads the SSH account information from the database table to help SSH login to the scheduling platform server; S202: Install a python program on the scheduling platform, and use the python program to write an Oracle ODI or ESSBASE execution module. After SSH login to the scheduling platform server, upload the ORACLE ODI or ESSBASE execution module program to the scheduling platform server using SSH Secure Shell To complete the deployment of the Oracle ODI or ESSBASE execution module; S203: Use ORACLE ODI or ESSBASE execution module to convert SSH logged in to the scheduling platform server into ORACLE ODI or ESSBASE server. The storage medium according to claim 16, wherein the step S3 causes one or more processors to perform the above steps: S301: Fill in the deployment document of the ODILE or ESSBASE task scheduling preset type on the scheduling platform; S302: Import the deployment document into a web interface through a scheduling platform, and store information in the imported deployment document into a scheduling platform configuration library; S303: The scheduling platform server continuously polls the scheduling platform configuration library through the Oracle ODI or ESSBASE execution module, grabs the task information that serves the scheduling conditions of ORACLE ODI or ESSBASE, and obtains parameters that meet the ODILE or ESSBASE scheduling conditions from the database of the scheduling platform Information, the Oracle ODI or ESSBASE execution module will stitch the task information and parameter information into executable Oracle ODI or ESSBASE scheduling tasks, and use ORACLE ODI or SSH in the ESSBASE server to execute ORACLE ODI or ESSBASE scheduling tasks. The storage medium according to claim 16, wherein the scheduling platform adopts a distributed application coordination service ZooKeeper, and further causes one or more processors to perform the above steps: The scheduling platform database is preset on the ZooKeeper, and parameter information of ORACLE ODI or ESSBASE is stored.

Images