Application Ingestion and Replication

Back Next

Configure an Oracle Fusion Cloud source

Define source properties for the source that you selected on the

Source

page.

Under

Source Properties

, configure the basic properties:

Property	Description
Load Type	Type of load operation that you want the application ingestion and replication task to perform. You can select one of the following load types for the task: Initial Load : Loads data read at a specific point in time from the source application to the target in a batch operation. You can perform an initial load to materialize a target to which incremental change data will be sent. Incremental Load : Propagates source data changes to a target continuously or until the job is stopped or ends. The job propagates the changes that have occurred since the last time the job ran or from a specific start point for the first job run. Initial and Incremental Load : Performs an initial load of point-in-time data to the target and then automatically switches to propagating incremental data changes made to the same source objects on a continuous basis.
Oracle Fusion Replication Approach	Select one of the following replication approaches Select REST to extract data from various applications of Oracle Fusion such as ERP, SCM, HCM, Sales, and Services, and transfer data to the target. Select BICC (Business Intelligence Cloud Connector) to extract bulk data from the source to the target.
Oracle Fusion Application	Select the application from which you want to replicate data.

Under

Source Objects

, select the source objects from which you want to replicate data. Use one or both of the following methods:

On the

Selected Objects

tab, individually select the check box for each source object you want to include. Clear the check box for any objects you do not want to include. To select all objects, select the

Object

check box at the top.

The

Field

count for an object shows the total number of fields in the object.

If you select the objects you want to include, all the selected and unselected objects are displayed by default. To view the selected objects only, use the filter next to the object selection count and change the view from

All

Selected

To find objects or fields, you can type all or part of a name in the Find
box and click

. This value is case-sensitive. If you type the beginning of a name only, a wildcard isn't required to represent the remainder. For example, CDC, CD, and CD* return the same results. However, if the search string is within the name, include the wildcard * at the beginning. For example, *CDC returns objects and fields that include CDC anywhere in their names. To narrow the search to only object names or field names, select

Object Name

Fields

in the drop-down list adjacent to the Find
box.

On the

Selection Rules

tab, you can create inclusion and exclusion rules for objects.

To add an object rule, click the plus (+) sign in the upper right corner. In the

Type

field, select

Include

Exclude

as the rule type. Then enter a string, with or without wildcards, as the condition.

Tips:

You can copy an existing object rule to use as a starting point for creating another rule. Click the copy icon at the right end of the row.

You can edit an object rule directly in its row by clicking the

Type

Match Condition

value.

To view the objects and fields that match a single rule, click

View Objects

in the row for the rule. For an Include rule, it shows the objects to be included. For an Exclude rule, it shows the objects to be excluded.

When you define a condition in a rule, use the following guidelines:

The task wizard is case sensitive. Enter the object names or masks in the case with which they were defined.

A mask can contain one or more wildcards. Supported wildcards are: an asterisk (*), which represents one or more characters, and a question mark (?), which represents a single character. A wildcard can occur multiple times in a mask value and can occur anywhere in the value.

Delimiters such as quotation marks or brackets are not allowed, even if the source uses them.

If an object name includes special characters such as a backslash (\), asterisk(*), dollar sign ($), caret (^), or question mark (?), escape each special character with a backslash (\) when you enter the rule.

If you define multiple object rules, they're processed in the order in which they're listed (top to bottom). Be sure to define them in the correct order of processing. For example, if an object rule specifies "Exclude CDC" followed by "Include C", all objects with names beginning with "C" are selected, including the CDC objects.

You can both manually select source objects and define selection rules. If you first manually select objects on the

Selected Objects

tab, rules are generated and displayed for those selections on the

Selection Rules

tab. Similarly, if you first define rules, any objects selected by those rules are displayed as selected on the

Selected Objects

tab.

To configure advanced source properties, toggle on

Show Advanced Options

at the top of the page. Advanced source properties are optional or have default values. Complete the following optional advanced properties as needed:

Property	Description
List Objects by Rule Type	Generate and download a list of the source objects that match the object selection criteria. If you used rule-based object selection, you can select the type of selection rules to use. Options are: Include Rules Only Exclude Rules Only Include And Exclude Rules Select the Include Fields check box to include fields in the list, regardless of which object selection method you used. Click the Download icon to download the list.
Include Child Objects	Get the child object data of an object using an Oracle Fusion Cloud source. This applies only for the REST replication approach and for all load types only when the target is Google Big Query.
Initial Start Point for Incremental Load	For incremental load jobs, customize the position in the source logs from which the application ingestion and replication job starts reading change records the first time it runs. You must specify the date and time in the time zone configured for the Oracle Fusion Cloud instance.
CDC Interval	For incremental load and combined initial and incremental load jobs, specify the time interval in which the application ingestion and replication job runs to retrieve the change records for incremental load. The default interval is 5 minutes.
Fetch Size	Enter the number of records that the application ingestion and replication job associated with the task reads at a time from the source. The default value is 50000.
Enable chunking	Select this checkbox to chunk data during the extraction process in an application ingestion and replication task. Chunking applies to initial load tasks, and in the initial portion in combined initial and incremental load tasks that use the BICC replication approach. Chunking is not applicable for CDC tasks. Options are: None . Extracts data as a whole without dividing it into chunks. Default is None. By Primary Key . Select this option to chunk data based on a numeric primay key. This option requires that your datastore contains a single numeric primary key column without Null values. By Creation Date. Select this option to divide data into chunks at intervals defined by the number of days for date range extraction. This option requires selection of the `Is Creation Date` option in the BICC Console for a column or columns in the column list, which represent the creation date.
Number of Rows	If you select the By Primary Key chunking option, specify the number of rows to chunk extracts. Enter a positive integer. Make sure that the combination of total rows and chunk size results in no more than 250 chunks. For example, if you have 2500 rows with a chunk size of 10, it results in 250 chunks, which is the maximum chunks allowed.
Number of Days	If you select the By Creation Date chunking option, enter the number of days to set the interval for data extraction. For example, if you specify 365 days, the data is divided into segments that each cover a 365-day period, starting from the initial date. To prevent performance issues, consider specifying a larger number of days for the interval.

Under

Custom Properties

, you can specify one or more custom properties that Informatica provides to improve performance or to meet your special requirements. To add a property, click the + icon to add a row. In the

Property Name

field, select a property and then enter a property value, or select the

Custom

option and manuallly enter both the property name and value.

The following table describes the properties that are available, depending on the load type:

Property	Description
Read Event Batch Size	The number of payload events written in batch to the internal event queue during CDC processing. When the event queue is implemented as an internal ring buffer, this value is the number of payload events that the reader writes to a single internal buffer slot. A batch size that's too small might increase contention between threads. A larger batch size can provide for more parallelism but consume more memory.
Reader Helper Thread Count	The number of reader helper threads used during CDC processing to convert change data into a canonical format that can be passed to the target. Default value is 3. You can enter a larger value to allow more threads to be available for performing conversion processing in parallel.
Custom	Select this option to manually enter the name of a property and its value. Use this option to enter properties that Informatica Global Customer Support or a technical staff member has provided to you for a special case. Available for any supported load type.

Custom properties are intended to address performance or special processing needs. A property name can contain only alphanumeric characters and the following special characters: periods (.), hyphens (-), and underscores (_).