Prerequisites for data ingress

1. 1In Administrator, create a source connection to read data from source and a Business 360 connection to write to the Business 360 assets. For more information about creating connections, see Configuring a connection in the Administrator help.
2. 2In Administrator, specify a Secure Agent that is up and running as the runtime environment to run a mapping task. For more information about Secure Agent, see Runtime environments in the Administrator help.
3. 3Create a mapping in one of the following ways:
• - Manual mapping. In Cloud Data Integration, create a mapping with the source connection as the source transformation and the Business 360 connection as the target transformation. Manually map the fields between the source and target transformations. For more information about manually creating a mapping, see Mapping configuration in the Data Integration help.
• - Automapping. Start the mapping creation process from a business entity in Business 360 Console. In Cloud Data Integration, the business entity becomes the target for the mapping. After you select a source, Cloud Data Integration automatically maps the fields between the source and the target.
4. Ensure that you create an in-out parameter jobInstanceId in the Parameters panel.
Note: The name of the in-out parameter is case sensitive.
5. 4In Cloud Data Integration, create a mapping task by selecting the runtime environment and adding the mapping that you create. For more information about configuring a mapping task, see Defining a mapping task in the Data Integration help.
6. 5In Cloud Data Integration, create the required taskflows. Publish the taskflows to use in your ingress job. For more information about creating taskflows, see Taskflows in the Data Integration help.
Note: Ensure that you don't add a Command Task step to the taskflows that you create. If the taskflows contain the Command Task step, the ingress jobs fail.
7. 6Consider the data source for the ingress jobs because not all the connectors available in Informatica Intelligent Cloud Services can be used in the mapping for ingress jobs.
For example, you can't use the Databricks Delta connector with custom queries in an ingress mapping for MDM SaaS. Before you define an ingress job, identify the source systems and validate the connectivity.
8. 7Validate the connectivity with the MongoDB Atlas instance and the Business 360 Connector.
9. 8To load a multibyte data set, meet the following requirements:
• - Define JVM options in the Secure Agent.
For more information, see Rules and Guidelines for Business 360 FEP Connector.
• - Ensure that the sourcePkey field name contains only alphanumeric characters and the following special characters without exceeding 255 characters:
~!/'={}|:@#$^&*()-_+,<>?`
For more information about loading a multibyte data set with ingress, see the
Multibyte characters not loading properly with Ingress when using Business 360 connector Knowledge article.

Rules and guidelines for importing data

• • Identify the differences between the Business 360 Connector and the Business 360 FEP Connector.
For more information about the differences between the Business 360 and Business 360 FEP Connectors, see the FAQ: Difference between Business 360 connector & Business 360 FEP connector Knowledge article.
• •When you ingress a large volume of data, use the chunking strategy to load a maximum of 25 to 50 million records per ingress job. To optimize the load time and help with the recovery time in case of any job failures, logically divide large source data into multiple jobs.
• •Use Business 360 FEP Connector instead of Business 360 Connector for parallel execution and enhanced performance.
• •In Data Integration, create separate mappings for hierarchy instances, root relationships, and relationships. Add each mapping to its own mapping task, and then add all the mapping tasks to a common taskflow.
• •Ensure that the primary key of each relationship in a hierarchy is unique.
• •If you want to add, update, upsert, or delete field values of records in a single mapping, ensure that you add separate target transformations for each operation in Data Integration
• •When you specify the delete operation for the root section in Data Integration, ingress jobs deletes entire records irrespective of the operation that you specify for field groups.
• •If you specify the update operation to update field values of existing records, the load step rejects records with field values that are identical to the field values of existing records.

Automapping source and target transformations

1From the Explore page, open a business entity
2Click Actions, and then click Automapping.
The Automapping page appears in Cloud Data Integration.
3In Business 360 Console, on the Sources tab of the Choose sources and targets page, click Add Sources.
4 Select the packages and sources along with their objects.
You can select multiple objects. Use the Find field to search for the objects if required.
5Click Add.
The selected sources and their objects appear on the Sources tab.
6Optionally, verify the target business entity.
Note that the target is predefined and you can't configure it.
7Click Create Mapping.
The mapping appears in the mapping canvas. Save and validate the mapping.
You can configure the mapping to add one or more supported transformations.