Tag Archives: boomi atom

Wedid: Boomi Atom Installation and Processes Transfer


Customer has been using the Boomi Atom Cloud to run their integration processes and would like to shift to an on-premise atom to have better control over the atom configuration.

Customer would have difficulty transferring all the processes into the new production environment as well when the on-premise atom is available.


  • Installed a 64-bit on-premise atom hosted in Linux server
  • Assisted in transferring existing processes into the new production environment
  • Updated the environment extension as well as redefine the integration schedule
Purpose Install on-premise atom and transfer the existing integration process to ensure all processes utilises the on-premise atom instead
Tool Boomi
Complexity Low


Boomi: SAP Integration Tips

This guide is not to help you to build a brilliant integration, but it gives you an important head start if you are integrating to SAP by using the Boomi SAP Connector.


  1. Before the installation, please make sure that you have installed the Java JDK (not JRE) in the server although Boomi Atom installer will download the Java JRE into the Atom installation directory (e.g, C:/Boomi Atomsphere/Atom – WDCi Atom/jre) if you do not have one in the server. Unfortunately, the Java JRE is not sufficient to run the SAP connector.
  2. You need to create a JAVA_HOME environment variable to point to the Java JDK directory and also include the JAVA_HOME/bin into the global path environment variable.
  3. After the installation, you will need to download the additional SAP library from the official site (service.sap.com/connectors > SAP Java Connector > Tools & Services) and extract the content into the <Boomi atom installation folder>/userlib/sapjco folder (e.g, C:/Boomi Atomsphere/Atom – WDCi Atom/userlib/sapjco).
  4. Once the above is done, please restart the Atom service in order for the changes to take effect.

Notes: If you would like to use SAP IDoc Listener (for real time integration), Boomi SAP connector requires a database (for tracking purpose) and you will need to download the required JDBC driver and place in the userlib/ folder.

Operation Profile

After importing the operation, please make sure that the date data type field has the correct date format in both Request and Response profile. The format used by the connector is:

  • Date = yyyy-MM-dd
  • Time = HH:mm:ss

Failing to configure the date in the Request profile would cause the connector to always returns all data from SAP.

Get Operation

Mostly, you will query the data by using last updated date time. The date/time format for the query operation is:

  • Date = yyyy-MM-dd (this is different from the format being used in SAP BAPI Tester, dd.MM.yyyy)
  • Time = HH:mm:ss

Send Operation

If you are sending information to SAP via a BAPI operation, it is best to double check with the SAP developer to see if they require Boomi SAP Connector to send “Commit Transaction” as part of the BAPI call. If yes, please make sure that the “Commit Transaction” option is checked in the SAP operation.

Boomi: What JVM version Atom is using?

If you have multiple JVMs in the same machine and wonder which one Boomi Atom is using? Easy, you can check this out easily from the Boomi AtomSphere via Manage > (Atom Name) > Atom Startup Properties. For example:



If you have access to the Atom installation folder, you can also go to <Atom_Installation_Path>\.install4j\inst_jre.cfg to find out the actual path.

Boomi: Keeping Track Of Cloud Usage

Boomi provides the facility to deploy any cloud-based integration processes to dedicated hosted atom known as the atom cloud. The usage limit allowed within this facility is 1 GB of volume for every month. Exceeding the appointed limit will cause additional charges to be incurred. The volume is based on the formula: ((inbound connector data + outbound Connector data) / 2).

The transparency to view the historical/current usage within your account is provided. Proceed to <logged in account> > Setup > Licensing > Cloud Usage Tab in order to view your account usage. The following is a sample display of the usage limit report:

Salesforce Real Time Integration with Boomi: Prerequisite

If you are interested to set this up, check out the list below:

  • License. SOA framework is required. It’s included in Boomi Enterprise license and can be added as an add-on in Professional license.
  • Atom installation. The Boomi Atom is installed in a machine that has internet connection.
  • Windows security setup. If you are using Windows, make sure that the Atom executable is not blocked and the port is open. For example: 9090.
  • Network setup. Configure your router/firewall to redirect package to the server that hosts the Atom.
  • Configure the Shared Web Server Setting in AtomSphere to get your Atom ready for port 9090.
  • Has basic knowledge in Salesforce to setup the Outbound Message workflow.

Once you have built the process in Boomi, you are all set to go!

Boomi Integration : Shared Web Server Settings – Security

In every Atom in Boomi, you can find this Shared Web Server Settings
The setting here will affect how Atom accepts inbound package. In this blog, we are going to share with you about the security setting:

Atom supports Basic Authentication. When a client performs an API call to your Atom, before acquiring the data, they will need to pass this security layer first. For example: If you want to get the WSDL file from Atom, you will need to use:

  • Boomi AccountID as the Username
  • Token (see picture above) as the Password

This Token is unique and please keep it secure. You can always re-generate this token if it is compromised.

Boomi: Defining Last Run Date & Last Successful Run Date

We talked about possible ways to change the Last Run Date & Last Successful Run Date via the Atom Management. When deployed process has been run, the properties are automatically populated and hence you may proceed to make the changes prior to next run.

Is there a way to manually add this in advance prior to first running the deployed process? This is possible by manually defining the com.boomi.execution.lastrun or com.boomi.execution.lastsuccessfulrun perperty name followed by the date/time in timestamp converted format (up to miliseconds). For example:

Which it then automatically convert the property value to a proper date/time picker.

Save the property and voila!