Data replication configuration options
If an app supports data replication functionality, review the following configuration options to ensure the data replication settings best meet the requirements of your environment.
Middle-tier data replication options
Data replication imports data from a Host (such as an ERP service like JD Edwards or Oracle E-Business Suite) and saves it in one or more middle-tier databases on the server. When configuring data replication for your environment, consider applying the following configuration options. These settings are edited in the Data Replication Agent. For more information, refer to About Data Replication Agent.
| Action | Details |
|---|---|
| Edit data records that are replicated from the Host to the middle-tier databases | Depending on the requirements of your environment, you may want to replicate additional or fewer data records with each event. Data replication is typically configured to replicate the majority of records in a Host database. |
| Edit frequency of scheduled data replication events | You can edit the number of replication events that are set to occur each day. Often, saving too many partial data replication records at once can slow down the app solution. For example, a price increase across all items could result in a high number of records, which could slow down replication from the middle-tier database to the device database. |
| Edit the length of time to retrieve records in the middle-tier databases | You can edit the SQL database query to only retrieve and retain records created in the specified time limit. For example, if you want the data replication agent to retrieve only JDE service orders for the most recent 180 days, you can edit the SQL database query in the first action item to only bring in orders created in the past 180 days. |
| Edit the method for disposing records that are automatically removed | You can determine the disposal method for any records that have remained in the database longer than the set number of days. For example, the records can be marked as "deleted" but not actually removed, or the records can be permanently deleted from the middle-tier database. |
| Edit AIM behavior | If any AIM sessions are scheduled for your app solution, you can configure the AIM sessions to improve efficiency. |
Device data replication options
Device data replication imports data from a middle-tier database on the server to the device database on the platform where you operate your app. When configuring device data replication for your platform, consider applying the following configuration options. These options are modified using device data replication rules, which are written in a SQL query format. For more information, refer to Add a device data replication rule.
| Action | Details |
|---|---|
| Configure the tables to replicate to the device | You can use check boxes to select the tables for the device to replicate. |
| Configure the data records to replicate to the device | You can write a WHERE clause in a SQL query that modifies the data records to replicate with each device data replication event. Note that the WHERE clause only allows you to download the filtered data from the middle-tier database. For example, the following SQL query downloads the user configuration element for LOCATION1 to the device database. LOCATION1 = @
@ = GetConfigElement("LOCATION1")
|
Loading...
There was a problem loading this topic