(1902) DataTiering Settings Tab

To access Settings of a specific DataProvider you can choose the Settings button, as shown on the figure below. To access the general settings click on the Settings tab.

Under DP Settings you can either change the general setting for all DataProviders by clicking Display or you can change the settings for one DataProvider by entering its name.

SETTINGS

Setting element	Description
Group ID	Name of the Group ID for mass processing of DataProviders. For better processing should a Group ID contain DataProviders that have a common characteristic.	Group ID is a global setting and may be changed only for all DataProviders. The Group ID is set to the value "Default". You can edit the name of the default Group ID by clicking Edit. The name should contain maximum 10 characters.
Read VP : ON-THE-FLY replication of navigation attributes	When reading offloaded data through a query with navigation attributes, this feature creates a master data table replica of this navigation attributes (if it is not created yet) and performs a join with this table on the external storage.	Click on Edit and enter 'X' to switch on the On-The-Fly replication or enter ' ' to switch it off.
Source storage	Name of the storage from which data is offloaded.	Source storage is a global setting and may be changed only for all DataProviders. You can change the default source storage by clicking Edit.
Target storage	Name of the storage to which data is offloaded.	Target storage is a global setting and may be changed only for all DataProviders. You can change the default target storage by clicking Edit.
Selectivity field for DP	Name of the field for partitioning. If the value of this setting isn't empty, partitioning will be based on the entered field name, otherwise partitioning analysis will run as usually.	You can change the selectivity field by clicking Edit. We recommend to use a field name that has many distinct values (has a higher granularity), for example a document number.
Max BG jobs for subrequest processing	Maximum number of background jobs for parallel processing. Relevant only when parallel processing is enabled. Please note that by parallel processing, the system creates first a job for offloading, and after that it creates other jobs for the subrequests.	You can edit the maximum number of background jobs by clicking Edit. Please consider your system settings and set an appropriate value.
Fetch package size	Maximum number of records in one package fetched from the source storage.	By clicking Edit you can change the maximum number of records in one package. The recommended minimum value is 100 000 rows.
Package volume for subrequest	Maximum size of a subrequest. Relevant only when parallel processing is enabled.	By clicking Edit you can change the maximum size of one subrequest. The recommended value is between 500-1000 MB.
Minimum offloaded rows	Minimum number of offloaded rows for offloading process. If the parameter isn't high enough, it may influence the storage performance (too many partitions are created). Also, the offloading condition should be defined as lower or equal to this parameter. In the case number of offloaded rows is less than the parameter Minimum offloaded rows a confirmation message appears.	By clicking Edit you can change the minimum number of offloaded rows. The recommended value is 100 000 rows.
Enable PiT recovery for Hadoop	Allows the Point-in-Time recovery for Hadoop target storage.	You can enable this feature by clicking Edit.
Enable PiT recovery for HANA	Allows the Point-in-Time recovery of HANA primary database.	You can enable this feature by clicking Edit.
Binary storage for HANA PiT recovery	Name of the binary storage used to store data for Point-in-Time recovery for HANA. Please note that once the binary storage is set for the specific DataProvider, it should not be changed.	You can edit the name of the binary storage by clicking Edit.

For more information how to transport settings to another system please see the chapter (1902) Transport of DataProviders and Settings to Other Systems.

Storage Management

Storage Management provides an interface for connecting to secondary databases / storages.

Following operations are available:

New – creates new storage
Edit – changes existing storage
Delete – deletes storage
Check – checks whether specified storage is running

For more information on how to configure Storage Management, please ask for a separate Storage Management for Hadoop documentation.

Transport Settings

It is possible to transport the definition of the DataProvider and its' settings to another system directly from DataTiering.

For more information check (1902) Transport of DataProviders and Settings to Other Systems.

W3 Settings

This button will show up only if Writer 3.0 is installed on the system. When clicked, you will be redirected to writer specific settings.