Boomi Integration Best Practice Part 2

Continuing on my previous post Boomi Best Practice. In following post we will talk about SAP Connector of Boomi.

SAP Connector

To implement a connection to your SAP account from Dell Boomi AtomSphere, you need to copy SAP JCo drivers to the folder where atom is installed. Follow this link for the list of drivers to be copied:

http://help.boomi.com/atomsphere/GUID-38961E54-DF4A-4DCB-940D-FCD5B5B6F1DE.html

• .       Use Naming Convention

 Always use standard naming convention for integration processes. Naming convention can be like” INT-001 Account Updates from SAP”. While creating  process for Sandbox append “SANDBOX” keyword as prefix with name of process and for production process use “PROD” as prefix.

•     Main Listner for IDOC Integration     

      Create a common Listner in order to listen all IDOC integrations. Create a single “Listen” action.

1     Use “Route” component and attach all sub processes which are using IDOC to listen data from SAP.

      Note:
     Whenever changes are need to be deployed on atom, always deploy actual process and IDOC main Listner.

•     Data Filter on the basis of Identifier

      To filter IDOC segment on the basis of identifiers use “identifier instance”.

         1. First you have to add a qualifier in the IDOC XML profile

2. After adding qualifier, add identifier instance. Click on blue triangle sign you will have option to add identifier.

3. After clicking identifier instance you have to choose your previously added qualifier. You can also identify on the basis of occurrence.

Note: You cannot put identifier on both parent and child node.

Boomi Atom Management Best Practice

The following post will guide you about some best practice we can use in Dell Boomi integration.

Atom Management

Boomi Atom Memory

By default memory for Atom is 512 MB. Memory size usually depends on data volume and available memory in your Server (Atom Machine) atom memory should be aligned with the configuration of server where atom is installed.

You can update memory size by editing file Name atom.vmoptions from Boomi Atmosphere\bin by converting it to txt extension then update it size and change it extension back. You can refer to below link

http://help.boomi.com/atomsphere/GUID-9DA4BA58-0D7F-40A7-815C-965DE636B8B3.html

Boomi Atom Management

1. Boomi Atom Logs can be downloaded to debug the issues with the connections and execution of processes.

2. In case of Integration with SAP, Boomi Atom should be restarted every time a new field is added to the RFC/IDoc.

3. Boomi Atom logs deletion should be set for a particular period of time to avoid load on the server where atom is installed.

4. Set Atom Encoding to UTF-8 to avoid special characters issues in data. 

SALESFORCE CONNECTOR

• Use one connection for every Connector and then re-use it.

• Use external ID to update/Create records avoids more API call. As we normally face issue when calling system multiple times which increase API calls. 

• Enable archiving and specify directory to debug which records are processed. 

Disk Connector

• The format of the file should be aligned with data, for example, if data has long text area fields then it is better to use tab delimited file as long text area fields could contain commas in the data. 
• Name of error files should be consistent. 
• “*” should be used instead of Hard-coding Directory in the Disk Connection, so that multiple paths can be specified using one connection. 

• If using disk connection as the start shape then use “Parameter” to define directory.

• Set properties should be used when setting parameters of the Disk Connection and Operation.

• This should be taken into consideration that whenever we are using “*” in Disk Connection and using properties to set its value then extensions would not apply. 
• File extension should also be specified in File Name.

Stay tuned, I will follow up this very shortly with more Boomi connectors best practices.