When the IFS Aurena Native Client Framework module (FNDMOB) is installed a number of background processes are created.These include Database Tasks, Database Processes and Aurena Naive specific Batch Queues.
The following database tasks are included in IFS Cloud to manage Aurena Native Apps data.
|Aurena Native Batch Schedule||Runs the Batch Synchronization process. The default schedule will be set to run every 15 minutes. The schedule for this database task must be equal to or more frequent to the quickest interval defined in Synchronization Rules.|
|Aurena Native Daily Statistics||Captures statistics for synchronized entity times and volumes per Application that are shown on a Aurena Native App Status lobby page.|
|Aurena Native Schedule for reprocess failed transactions||Reprocesses all Failed Transactions for the App/Version. Suggested reprocess cycle is once per day at 00:00.|
|Aurena Native Scheduled Activation||Processes any Scheduled Activations for the App/Version. Suggested cycle is daily at 00:00|
|Clean Up Aurena Native Deleted Failed Transactions||Removes Deleted Failed Transactions that are older than x days and any records relating to removed Apps/Devices. Suggested number of days is 30.|
|Clean Up Aurena Native Device Locations||Removes Device Locations that are older than x days and any records relating to removed Apps/Devices. Suggested number of days is 30.|
|Clean Up Aurena Native Entity Sync Data||Removes Synchronization Data and Out Messages for records relating to removed Apps/Devices or Apps/Devices in the state Disabled or failed to successfully activate and are older than x days. Suggested number of days is 7.|
|Clean Up Aurena Native Faulty Device Records||Clear All faulty device records, device records which are Disabled an do not have an installed app device. Suggested cycle is every 04:00 hour.|
|Clean Up Aurena Native Ignored Failed Transactions||Removes Ignored Failed Transactions that are older than x days and any records relating to removed Apps/Devices. Suggested number of days is 30.|
|Clean Up Aurena Native Interrupted Sync Tasks||Removes Synchronization Tasks that are in the state of Posted or Executing and are more than x day(s) old. Suggested number of days is 1.|
|Clean Up Aurena Native Logs||Removes Logs that are older than x days. Suggested number of days is 100.
Note: depending on your system's transaction volumes, you might need to set this to a lower value.
Note: if Extended Logging is enabled, this needs to be set to a lower value.
|Clean Up Aurena Native Sync Tasks||Removes Synchronization Tasks and Push Queue records that are older than x days and any records relating to removed Apps/Devices. Suggested number of days is 7.|
|Clean up Aurena Native Sync Traces||Removes Synchronization Traces that are older than x days and any records relating to removed Apps/Devices. Suggested number of days is 7.|
|Clean Up Aurena Native Synchronization Service Stat Records||Removes Synchronization Service Stat Records that are older than x days. Suggested cycle is weekly on Sundays at 00:00.|
|Clean Up Aurena Native Transaction Log Data||Removes older Aurena Native Transaction Log Data based on transaction SCN (System Change Number). Suggested cycle is daily at 00:00.
Note: SCN is database wide number that keeps incrementing on each commit. Backend keeps track of the SCN each Device/App/User was last initialized/synced.
If there are transactions in the log that happened after this number we cannot delete them no matter how old they are until they are synced to the device or get invalidated.
|Clean Up Notify Me Notifications||Clean Up Aurena Notify Me notifications that are older than x days on any device. Suggested Number of days is 30.|
All Tasks are enabled by default on enabling the Application.
The Task "Aurena Native Batch Schedule" will be processed by the Aurena Native Batch Queue.
Database Processes are used in the Push and Grouped Push Synchronization Rule delivery methods.
Delivery Method - Push¶
A database process is used to process the Push Queue. This process checks if there are any Push Queue records that are ready to be executed. If there are Push Queue records to be executed this process creates a Synchronization Task which in terns submits them into a background job. This process is managed in the System Parameters screen. The name of this process is Mobile_Db_Process_SYS.Push_Data__.
Delivery Method - Grouped Push¶
A database process is used to process the Grouped Push Transaction Queue. This process checks if there are any Grouped Push Transaction Queue records that are ready to be executed. If there are Grouped Push Transaction Queue records to be executed this process will publish the Grouped Push data changes to the filtered Aurena Native users. The name of this process is Mobile_Db_Process_SYS.Grouped_Push_Data__.
Aurena Native Batch Queue¶
The Aurena Native Queue handles the Batch Synchronization and Scheduled Activation. The number of processes that are allocated to this Queue will affect the number of Background Jobs that are created when processing Synchronization Tasks.