Ankit Goyal, Deepak Ramchandani, Rishabh Baj

Date- Jul 24, 2015

2015 Appirio, Inc. - Confidential

Click here for reference content Outline example
Course Objective

At the end of this course you will be able to:

Get idea of Boomi Architecture and Boomi Features

Manage Basic Setup for Boomi

Boomi Terminology

Use Basic Shapes

Create Process

Deploy and Schedule Processes

Get Reporting of Process

What is Covered in this Course
Introduction

Why choose Boomi?

Boomi Architecture

Start Playing with Boomi

Boomi Terminology

Getting familiar with Basic Shapes

Creating the first process

Deploying and Scheduling

Process Reporting

2
Introduction
Rather than retrofitting older technologies, Boomi AtomSphere developed a single instance, multi-
tenant platform to optimize the new integration paradigms used in SaaS, PaaS, and cloud
computing environments.
For companies seeking ease of use and accelerated time to value in addressing application
integration, Boomi AtomSphere leads the iPaaS vendor landscaperegardless of company size,
industry or geography.
Dell Boomi AtomSphere can give customers the power to start using new cloud and SaaS
applications, and connect them to existing applications. AtomSphere Spring 11, the newest version
of Dell Boomis cloud integration technology, includes new capabilities for middleware
connectivity, large-scale data management and migration, and anywhere integration monitoring.
The new features simplify the move to cloud computing through easy integration with existing
enterprise IT environments.

3
Why ?
Boomi provides many features as:
True Multi-Tenancy
The Dell Boomi AtomSphere platform was designed and implemented from the ground up to be an
elastic, multi-tenant, hosted platform. It is not a retro-fit of a traditional software solution where
multi-tenancy is achieved via multiple installation instances.

Enterprise Performance
AtomSphere can simultaneously handle the smallest integration requirements with the demands of
very complex integrations. For the most demanding integration requirements and those that affect
business-critical processes, AtomSphere offers functionality that improves testing, deployment and
scalability:

4
 Why ?
Environments AtomSphere offers separate, dedicated environments for advanced testing.
Molecules An enterprise-grade version of Boomis patented Atom technology can be deployed
across multiple physical servers to enhance load balancing and deliver high-availability for mission-
critical integration processes.
Scalability AtomSpheres innovative and mature single-instance, multi-tenant platform meets the
scalability and performance requirements demanded by mission-critical integration processes.
Parallel Processing AtomSphere allows processes and parts of processes to execute in parallel to
help speed up "slow" or "complex" integration flows.
Message Queuing AtomSphere includes native message queuing as part of the core platform,
eliminating the need for a standalone message queuing solution.
Advanced Workflow AtomSphere supports complex process orchestration, lowering development
times and improving team efficiency for larger integration projects.
Advanced User Security AtomSphere includes the ability to assign access to Boomi resources
based on user and account-group profiles.

Source: Placeholder for notes, etc. 12 pt..

5
Why ?
Security
For any SaaS or cloud computing application, security requires careful scrutiny. At Boomi, we are
keenly aware that our platform manages the integration of business-critical information and processes.
To meet global security requirements, Boomi AtomSphere provides a multi-layered security model
built on patented technology.
Network and Facilities Infrastructure Security
The Boomi infrastructure has received a number of global security certifications and compliance
verifications. Certifications include ISO 27001:2005, Level 1 Payment Card Industry (PCI) Service
Provider, SSAE16 Type II SOC1, SOC2 (Security and Availability Only), and SOC3, Safe Harbor,
and CDSA Content Protection and Security.
Application and Platform Security
The Boomi Atom resides on your network, in our data center on premises or in the cloud, hosted by
Dell Boom or a third party. During deployment, the data center verifies and authenticates the Atom
and all of its contents before activation.

6
Architecture

7
Architecture:
AtomSphere: Dell Boomi AtomSphere integration Platform as a Service (iPaaS) enables
customers to integrate any combination of cloud and on premise applications without software,
appliances or coding. As an iPaaS, AtomSphere supports real-time integration and elastically
scales to meet high-volume needs in mobile, batch (ETL) and EDI environments.
Dell Boomi AtomSphere is a 100 percent native cloud, multi-tenant platform that supports
application integration for anything, anytime, anywhere, including:
cloud to cloud / SaaS to SaaS (software-as-a-service) / cloud to on premise /
on premise to on premise / B2B integration
Atom: The Dell Boomi Atom is a lightweight, dynamic runtime engine. Once your integration
processes have been deployed to your Atom, the Atom contains all the components required to
execute your processes from end to end, including connectors, transformation rules, decision
handling and processing logic. Inside Atom:
One or more integration process.
All components needed to execute from end to end
Connectors, map, error handling etc.
A micro sized business rules engine.
8
Start Page:

9
Access and Setups

Buy License
Add users/Groups
Manage rights of
User and Groups
Manage Alerts
Track records in
processes

10
Set up and Install Atom

Save setup
on cloud or
local
system

Install setup and

Atom can be
seen running in
Management
Tab under Atom
Management

11
Boomi Terminology
Components : Reusable configuration objects used in processes. Components are reusable and include
certificates, connections, connector operations, cross reference tables, document caches, maps, map functions,
processes, process properties, profiles, queues, trading partners and web services.

Document : A document is a set of data that goes through a process. A document can be a single record, a group
of records

Process: Processes are the central components in AtomSphere. It represents a single type of data to integrate
between two or more systems. They are comprised of a series of steps (represented in the UI by shapes) that
specify the business logic and transformation requirements.

Connector : Connectors get data into and send data out of processes. They are actually comprised of two
components:
i. Connection : The connection represents the "endpoint" and contains the physical connection details.
ii. Operation : The operation represents a specific action to perform against that connection, such as a database
SELECT query, an FTP etc.
12
Boomi Terminology
Map: Maps allow data to be transformed from one format to another or specifically, from one profile to
another.

Profile: Profiles define the structure or layout of the data to be processed. They are used when reading from or
writing to a given format. Profiles can be of the following types:
i. Database
ii. EDI
iii. Flat File
iv. XML
v. JSON

Shape : Process shapes are the steps linked together to form the business logic for a process.Shapes can perform
execution tasks like document splitting and data transformation, or logic tasks like decision and routing.

13
Getting familiar with Basic Shapes
Branch: The Branch shape is used when you have several actions that you want to execute in sequence. Each branch consists of a
separate path that is executed in sequential order.

Data Process: The Data Process shape provides a number of options for manipulating document data within a process, from splitting
and combining documents to zipping and unzipping data.

Decision: The Decision shape routes documents based on a true/false comparison of two values. Those values can be anything from
field values in the current document (profile elements), static values, results of a database or even an application query, and more.

Process Call: The Process Call shape allows you to execute another process from within a process. When the subprocess is called,
the Start shape of the subprocess is invoked to get data. The subprocess call is considered a separate, distinct process execution

Route: The Route shape can conditionally send documents down a different execution path based on the value of some field.

Stop: The Stop shape provides the ability to terminate the data flow down a process path. The Stop shape represents a successful
conclusion and therefore does not generate an error message. If your process requires the path to end with an error, use an Exception
shape instead.

14
Getting familiar with Basic Shapes
Add to Cache: The Add to Cache shape is used to add documents to a document cache so that they can be used in a process or
subprocess. The Add to Cache shape references a Document Cache component, which describes how the cache is defined..

Business Rules: The Business Rules shape works with the profile structure of a document and allows you to check multiple
"business rules" to determine if a document should be accepted or rejected. This shape is similar to the Cleanse shape, but it is
content-driven rather than structural, meaning that you can perform advanced logic and validations against parent/child field data
rather than analyze field lengths and data types.

Cleanse: The Cleanse shape enables you to validate document field values and either repair or reject the document before further
processing. It is often helpful to use a Cleanse shape before a Map shape, so that invalid values can be corrected before potentially
causing errors while mapping..

Connector: Connector shapes are used to get data into and send data out of a process. Every process has one "get" connector (i.e.,
the Start shape) and typically has one or more "send" connectors. The Connector shape uses a combination of predefined connection
and operation components to establish where and how to get or send data.

15
Getting familiar with Basic Shapes
Find Changes: The Find Changes shape provides a way for a process to track changes made to a document and to send the
document results down an Add, Update or Delete path. This is most useful for large data sets or mainframe files where a full capture
of the data always needs to be retrieved from the source system.

Try/Catch: The Try/Catch shape captures document-level errors for one or more documents that fail during an execution. The
Try/Catch shape must be placed before the main processing shapes in your process. The Try/Catch shape sends documents down the
"Try" path to be processed. Documents that fail are caught and are sent down the "Catch" path.

Set Properties: The Set Properties shape allows you to set values for various document and process property connector properties.
These properties can be used to set outbound connector attributes such as file name or email subject, or store certain values in
memory to facilitate the integration. The property values can be comprised of static and/or dynamic values.

Return Document: The Return Documents shape is placed at the end of a document path and returns the documents to the calling
source point, which is one of the following:
The parent process
A web service client application

16
Example
SFDC Account to NetSuite Customer Integration
(This will walk through some of the Boomi functionalities and will provide an overview of the platform.)

17
Deploying Components
There are two key steps to perform when deploying a new component to an Atom:

Attach one or more Atoms to the component An Atom is a runtime engine on which processes run and
web services are hosted. You must attach one or more Atoms to your component so that it can be executed
or accept requests.

Deploy the latest version of the component You must select the version of the component that you want
to execute or accept requests on the Atom. You can do this before or after the component is attached to an
Atom.

Steps:
i. Go to DEPLOY tab
ii. Select the process to be deployed from the left hand side
iii. Select the Environment to be attached
iv. Click Save and Deploy

18
Scheduling
After you build and deploy a process, you can schedule it to run automatically at set times.
Process schedules can be added on the Atom Management page. To add and edit process schedules
on the Atom Management page you need the Scheduling and Atom Management privileges.

Go to Manage > Atom Management.

Select the Atom, Molecule or Cloud from the list on the left.
On the Deployed Processes tab, locate the process, click its blue arrow icon and select Edit
Schedules.
The Scheduling dialog opens with the Execution tab selected.
Click Add.
Choose a Type: Minute, Hour, Day or Advanced.
The rest of the selections change depending on the type.

19
Read less, practise more:
1. Export Account, Contacts from SFDC to CSV
2. Migrate data from one SFDC org to another for Account, Contacts
3. Load Opportunity Products from one SFDC org to another.
4. 2-way integrate Account from one SFDC org to another.

20
Useful Links:

Reference Guide:
http://help.boomi.com/atomsphere/GUID-BA83DB8E-D487-4C8A-8EA3-BB95B186CE05.html

Training Video Library:

http://training.boomi.com/display/TDASH/Training+Video+Library

Useful Assets:
Getting Started
Naming Convention
Exception Handler
SFDC Account Integration
SFDC-NetSuite Integration

21
Thanks !

22