Rules and Guidelines for Business 360 FEP Connector
Consider the following rules and guidelines when you use a Business 360 FEP 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.
•After you create a mapping to ingress data to a dynamic field definitions attribute, create another mapping to ingress relationships. When you relate records, they inherit the dynamic field definitions.
•To add new records, update field values, and delete field values in a nested field group, ensure that you map the source primary key of the records.
•To delete field group entries in record sections, ensure that you map the field group ID of the records.
•You can't use the delete operation to delete all the root field values of a record.
•To update field values in record sections, ensure that you map all the field values of that particular section.
• 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:
•If you want to run the Secure Agent through a proxy server, configure the following JVM options in the Secure Agent:
1In Administrator, click Runtime Environments.
2Click the Secure Agent that you want to run through a proxy server.
3Click Edit.
4In the System Configuration Details section, select the type as DTM for the Cloud Data Integration Server service.
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=<username>.
JVMOption5
Required if you set JVMOption4 to -Dhttps.proxyUser=<username>. Set to -Dhttps.proxyPassword=<password>.
Note: You can set either https or http for the preceding options. If you do not set the required JVM options, the mapping fails.
6To enable or disable the mongo TCP proxy support for the Business 360 FEP Connector, configure the custom configuration details for JVMOption6 listed in the table below:
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 value 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.
7Click Save.
8Restart the Secure Agent.
• When you run an ingress job to import records, the wait time during the Extract step might increase based on the volume of records.
To reduce the wait time during the Extract step, configure the following JVM options in the Secure Agent:
1In Administrator, click Runtime Environments.
2On the Runtime Environments page, click the Secure Agent that you want to run through a proxy server.
3Click Edit.
4In the System Configuration Details section, select the service as Data Integration Server and then select the type as DTM.
aEdit the following JVMOptions:
JVMOptions
Value
JVMOption1
-XX:-UseGCOverheadLimit
JVMOption2
-Xms8192m
JVMOption3
-Xmx8192m.
Additionally, to reduce the wait time, increase the batch count of records sent to the Mongo. To increase the batch count, add the MDM_MONGO_BULK_REQUEST_COUNT=1000 property to the mdm.Connector.properties file in the following directory: