Blog Post

Boomi Atomsphere API:

• This Boomi AtomSphere API is one of the standard connectors provided by the Boomi
• The Boomi AtomSphere API connector enables you to perform the object-based operations and actions exposed in the AtomSphere API
• The Boomi AtomSphere API connector is designed to connect seamlessly with Boomi Integration
• Deploying a Boomi AtomSphere API connector does not affect your license count. You can deploy this connector unlimited times across Atoms and Environments

Actions of Boomi AtomSphere API:

The Boomi AtomSphere API has different actions, i.e.

1. Get
2. Query
3. Create
4. Update
5. Delete
6. Execute

Objects of Boomi AtomSphere API:

Boomi AtomSphere API has multiple objects. Some of the Objects are

Deployed Package

• Packaged Component
• Process Schedules
• Process Schedule status
• Environment Extensions
• Trading Partner Component
• Trading Partner Processing Group
• Environment
• Environment Atom Attachment ……………

Getting Started – Logging into the Boomi Platform

Step-1: Enter your Email Address and Password to log in to your Boomi Account

Step 2: Enter the Authorization code

Step 3: Click on Integration Service to create our process

Step 4: Click on the Create New option, then we can see the process canvas where we can build our process

Step 5: Once we click on the create a new option, we have to select the process component and it will show the below image.

Step 6: Here we can build our process

Process for migration of deployed process from one environment to another:

• The Above image shows the entire process i.e. how to Migrate the deployed processes from one environment to another using this Boomi Atom Sphere API connector.
• The following Alphabets specify the steps, that we have used to achieve the entire functionality
• The Below steps define the entire information related to every shape

Step A: Configure Boomi Atom sphere API connector

Whenever we take any connector, we have to configure 2 components

1. Connection
2. Operation

• Along with these 2 options, we have to specify an action, which we are going to perform
• Here, this Atom sphere API connector fetches the currently deployed processes in a specific environment.
• To fetch current deployments in an Environment, we have to select the action as a Query, and in operation, we have to import one object i.e. Deployed Package object.
• This Object will help you to fetch the deployments in a specific environment, to do that, we have to provide Environment ID and “Active” value as “True”

Configure Connection Component:

Once CLICK on the + icon of the Connection Component we can see the below image

To establish connectivity with this Boomi Atom Sphere API connection component, the following steps are required:

• we have to provide the Account ID in the WSDL URL path along with the default URL
• Select Authentication type i.e. either API token or Password.
• Based on the Authentication type we have to provide the required details
• If the Authentication type is an API token, then we have to generate an API token at the account level and pass it in the API token place
• If the Authentication type is the password, we have to provide the Boomi user Account password
• In place of a username, we have to provide the Boomi Account username

Configure Operation Component

Once We CLICK on the + symbol of the operation component we have to follow the below steps

Finally, The Operation Component looks like this,

• Whenever we open the operation component of Boomi Atom Sphere, for the first time we have to import the required object.
• Because this Boomi Atom Sphere API consists of multiple objects based on the Actions
• In this process, we have to import the Deployed Package Object.
• Once we import the deployed package object, it will create a response profile.
• In filters, we have to add to expressions i.e. Environment ID and Active
• The values of this, Environment ID, and Active values should be passed in parameters of the Boomi Atom sphere API connector (the below image shows how to pass the values in parameters).

Step B: Configure Boomi Atom sphere API connector

• Drag and drop another Boomi Atom sphere API connector to the process canvas

• Configure the connector with the same connection component which we made earlier

Because of the Connection, we can reuse it. If the connector is the same we can use the same connection component multiple times. It will help to reduce the connection licensing (licenses will be consumed based on the unique connection).

• Select the action as CREATE
• Click on the + icon to configure the Operation component

These are the steps to follow to configure the Operation Component

Once we follow all the steps, The Operation component looks like the below image.

Step C: Configure Map Shape

• Drag and drop the map shape onto the Process canvas
• Once we drag and drop the map shape, just click on the + icon, then we have to configure the map component

The Map component looks like the below IMAGE.

Select the profile type and add the profile

In the SOURCE of the map component, we have to select the Response profile of the 1st Boomi Atom Sphere API connector.

The Profile Type is XML, because the Boomi Atom Sphere API provides XML profiles only

• Select the profile type and add the profile
• In the SOURCE of the map component, we have to select the Response profile of the 1st Boomi Atom Sphere API connector.
• The Profile Type is XML because the Boomi Atom Sphere API provides XML profiles only

Once we add the Source and Target profiles in the Map component, The Map component looks like the below IMAGE

• Whenever we try to migrate the Deployed processes from one ENV to another, we need Deployment ID, Component ID, and Environment Id
• In this process, the Deployment ID and Component ID come from source profiles, and the Environment ID has to be provided as a Static value
• Finally click on Save and Close

Once we execute the Process in Test mode, the processes that are deployed in one environment will be migrated to Another environment.

There are the processes deployed in the Source Environment

After the process is executed successfully, The Processes migrated from the Source Environment (Naveen’s_Test Environment) to the Target Environment (kazimiraz Test Environment)