Rules and Guidelines for Business 360 Connector

• •When you create a taskflow, ensure that you add the mapping tasks of both the root field and the child field group. For more information about creating a taskflow, see Creating a taskflow.
• •When input files of ingress jobs contain duplicate records with identical source primary keys, the jobs randomly select and import one of the duplicate records. Filter the data in the input files to remove duplicate values before loading it to the target. For more information about filtering data, see Data filters.
• • When you write data to the Business 360 data store, the Business 360 Connector sends 100 records in one batch.
To increase the batch count, add the MDM_MONGO_BULK_REQUEST_COUNT=<Bulk count> property to the mdmConnector.properties file in the following directory:
<Secure Agent Installation Directory>/apps/Data_Integration_Server/conf/mdmConnector.properties
Before you increase the count of records, ensure that you have enough Java heap size.
• •When you run an ingress or export job, a new user is created in the data store. By default, the wait time to add a user is 60 seconds.
To customize the wait time, add the MDM_MONGO_CONN_WAIT=<Time in milliseconds> property to the mdmConnector.properties file in the following directory:
<Secure Agent Installation Directory>/apps/Data_Integration_Server/conf/mdmConnector.properties
Note: A shorter wait time might result in a timeout error.
• • To prevent an ingress or egress job from running indefinitely because of network latency or disruptions during the extract step, use the SOCKET_HANDSHAKE_TIMEOUT=<Time in milliseconds> property. By default, the wait time is set to 60 seconds.
To customize the wait time, add the SOCKET_HANDSHAKE_TIMEOUT=<Time in milliseconds> property to the mdmConnector.properties file in the following directory:
<Secure Agent Installation Directory>/apps/Data_Integration_Server/conf/mdmConnector.properties
• •If you want to run the Secure Agent through a proxy server, configure the following JVM options in the Secure Agent:
1. 1In Administrator, click Runtime Environments.
2. 2Click the Secure Agent that you want to run through a proxy server.
3. 3Click Edit.
4. 4In the System Configuration Details section, select the type as DTM for the Cloud Data Integration Server service.
5. 5Edit the following properties:

JVMOptions	Value
JVMOption1	Set to -Dhttps.proxySet=true
JVMOption2	Required if you set JVMOption1 to -Dhttps.proxySet=true. Set to -Dhttps.proxyHost=<hostname>.
JVMOption3	Required if you set JVMOption1 to -Dhttps.proxySet=true. Set to -Dhttps.proxyPort=<port>.
JVMOption4	Optional. If you have user credentials configured for the proxy server, set to -Dhttps.proxyUser=<user name>.
JVMOption5	Required if you set JVMOption4 to -Dhttps.proxyUser=<user name>. Set to -Dhttps.proxyPassword=<password>.

Note: You can set https or http for the preceding options. If you don't set the required JVM options, the mapping fails.
6. 6To enable or disable the Mongo TCP proxy support for the Business 360 Connector, configure the custom configuration details for JVMOption6.
The following table describes the custom configuration details for JVMOption6:

Custom Configuration Details	Value
Service	Data Integration Server
Type	DTM
Name	JVMOption6
Value	- To enable the proxy support for Mongo connections, set the value to -Db360.datastore.useProxy=true. - To disable the proxy support for Mongo connections, set the value to -Db360.datastore.useProxy=false. Note: The values true or false is not case sensitive.

Note: To disable the proxy support for Mongo connections, you can set the value to -Db360.datastore.useProxy=false or don't configure the JVMOption6.
7. 7Click Save.
8. 8Restart the Secure Agent.