Data Orchestration Engine Background Jobs 

You can schedule the following background jobs in the Data Orchestration Engine (DOE):

Statistics

Purpose

If you want to aggregate synchronization and message statistics at regular intervals, you can schedule this job. However, before you schedule this job, you must first enable the aggregation of statistics by configuring the relevant parameters.

Optional or Mandatory

This job is optional and can be scheduled based on your requirements.

Frequency

You can configure the statistics to be aggregated daily, weekly, or monthly. Therefore, the job can be scheduled for a daily, weekly, or monthly run based on the value you have configured.

We recommend that you schedule the job for a daily run.

Delta Generation

Purpose

You need to identify the runtime objects that need to be regenerated as a result of changes to the associated generators. You can identify the changed generators either manually or by scheduling a job. To manually identify the changed generators, is a time-consuming task. However, when you schedule a job, the information about all the changed generators is sent to the Admin inbox.

Optional or Mandatory

This job is optional and you can be scheduled based on your requirements.

Frequency

You need to check for changed generators when new transports reach the system. Therefore, we recommend that you schedule the job based on the frequency of transports. In addition, you can schedule this job after you apply notes in the system as generators can change as part of corrections in notes.

Message Store and Log Reorganization

Purpose

The logs and traces associated with the client devices, DOE, and other connected systems are stored in the log and trace tables. In addition, the messages sent by client devices to be processed by the DOE are stored in message store tables. If these tables are not cleaned up at regular intervals, the size of these tables can increase significantly.

Optional or Mandatory

This job is mandatory to ensure that the system cleans up the entries in the log and message store tables up at regular intervals.

Frequency

The frequency of the job depends on the number of activities that are performed in the DOE.

We recommend that you schedule this job once a week. However, you can increase or decrease the frequency based on your requirements. You can also archive the logs and messages if required.

Generic Sync

Purpose

Generic sync applications can work in two modes, synchronous and asynchronous. For synchronous applications, the DOE receives the request from the client, calls the back-end system immediately, and sends the response (success or failure) to the client. These requests are not stored in the DOE for later processing. For asynchronous applications, the DOE stores these requests and sends a confirmation about the receipt to the client. These stored requests are later processed by the DOE when this job is executed.

Optional or Mandatory

This job is mandatory if the synchronization mode of the application is asynchronous.

Frequency

Since the response to the stored requests is sent to the client only when the job is executed, the frequency of the job is based on when you want the responses to be sent. Therefore, if the responses must be sent once in a day, then you must schedule the job on daily basis.

Delta Load

Purpose

This job allows you to trigger the delta download from the back-end system at regular intervals. The delta download ensures that the DOE is updated with the data from the back-end system at regular intervals.

Optional or Mandatory

This job is optional.

Frequency

You can specify a frequency for this job based on your requirements. For example, if you want the DOE to be updated with the data from the back-end system every day, then you can schedule this job for a daily execution.

Back-end Push

Purpose

In case of back-end triggered replication, when a user modifies the data in the back-end system, the back end sends the instance keys to the DOE. This job allows you to store these keys in a DOE table. These keys are processed when the job is executed. This job primarily allows you to improve performance by using semantic compression. In this case, if an instance is repeatedly modified in the back end within a short period of time, only one instance is stored for all the modifications.

Optional or Mandatory

This job is optional and you can schedule it based on your requirements.

Frequency

We recommend that you schedule the job for short durations, for example, every 10 minutes.

Message Restart

Purpose

This job identifies the messages from the message store that have failed processing and are marked for automatic restart. Automatic restart refers to some error code that is registered in the DOE. For example, INV_TASK is an error code that is sent by the key mapping service during message processing. If you want to automatically restart messages that fail due to this error code, then you can configure this code. To do this, you need to maintain the relevant entries in the SMMW_AUTO_STATUS table.

Optional or Mandatory

This job is optional.

During message processing, if some errors occur repeatedly and if these errors can be resolved by restarting the message, then you can configure such error codes for automatic restart. As a result, when this job is executed, the report searches for messages with the error codes configured for automatic restart and triggers the restart for such messages. If errors are resolved, then the state of such messages changes to consistent.

If you have to manually resolve errors before reprocessing messages, then you must not configure such error codes for automatic restart.

Frequency

The frequency of the job depends on the type of error codes you configure for automatic restart. For example, you can configure error code XYZ, which indicates system downtime, for automatic restart. In this case, when the system is up, these messages can be reprocessed automatically.

Alert Reorganization

Purpose

The DOE receives various alerts triggered by the client devices, back-end systems, or other systems that are connected to it. These alerts are stored in the alert store tables. If these tables are not cleaned up at regular intervals, the size of these tables can increase significantly.

Optional or Mandatory

This job is mandatory to ensure that the system cleans up the table entries at regular intervals.

Frequency

The frequency of the job depends on the number of alerts the DOE receives.

We recommend that you schedule this job once a week. However, you can increase or decrease the frequency based on your requirements. You can also archive the alerts if required.

Extract Job

Purpose

This job extracts data for a data object based on the frequency you specify. This data is then transferred to the relevant devices when they connect to the DOE to synchronize data.

Optional or Mandatory

This job is optional because in addition to the scheduling the extract, you can also trigger the extract by using any of the following methods:

Manual

You need to manually trigger the extract for the relevant devices by using the NetWeaver Mobile administrator

Extract on device connect

In this case, the extract is triggered only when the device connects to the DOE to synchronize data

Configuring the data object for synchronous extract

The extract is triggered when the data at the instance level changes.

Download request

For backward compatibility applications, the download request ensures that the data is extracted from the DOE to the mobile clients. This request is sent by the mobile clients to the DOE during each synchronization cycle.

Frequency

You can define the frequency of this job based on your requirements.

System Message

Purpose

This job ensures that all the system messages for which the lifetime has expired are deleted from the consolidated data store. You can schedule this job during the setup of DOE.

Optional or Mandatory

This job is mandatory.

Frequency

We recommend that you schedule this as an hourly job.

LDQ Flush

Purpose

The size of the LDQ tables increases constantly because the table entries are not purged automatically even if the queue entries have been read by the relevant receivers. This can have an impact on the performance of the system because the response time for synchronization and portal components increases. Therefore, you must purge the entries in the LDQ tables at regular intervals.

Optional or mandatory

This job is mandatory.

Frequency

You must define the frequency of this job based on the data load in these queues.

We recommend that you schedule this job when the load on the DOE is less.