webMethods.io Embed - Integration Patterns

Author: Bharath.Meka@softwareag.com     

1. Introduction

This article describes the different types of embed integration patterns White labeling, Integrations Embedded, Connectivity Embedded.

   1.1 Audience

       It is assumed that readers of this article understand integration strategies such as Saas (Software as a service) and iPass (Integration Platform as a Service) and are familiar with the products of the SoftwareAG Integration Suite webMethods.

2. Why you need to offer integrations to your customers

There are many good reasons to build out a range of integrations inside your SaaS platform.

  • Customers demand an integrated stack
  • Create customer “bonding”
  • Become the Single Source of Truth

    Once you have created a set of native integrations around your SaaS platform, the next question is how you will embed them in your own UI, and how you will present them to your customers.

3. Levels of embedded integrations

There are several ways you can embed native integrations into your platform.

   3.1 White-label Integration Hub

          The simplest solution is to leverage an iPaaS platform to build a set of native integrations and bundle them in a white-label Integration Hub.

In this embedding scenario, give your customers the power of the iPass platform with the look and feel of their site.

  • Customize the branding, colors, user onboarding, as well as recommended integrations
  • Visualize customer insights by creating the admin dashboard.
  • Platform having the capability of SSO is an added advantage.

3.2 Integrations Embedded Pattern

To provide your customers with a seamless experience, you can embed the Integration Hub into your SaaS platform using an iframe with SSO (single-sign-on).

Here is an example of embedding the White Label Integration Platform, which was created in webMethods.io Embed.

You can include a “My integrations” link inside your platform, which opens your white-labeled Hub in an iframe or popup. Inside the URL you can add SSO information (including a secure hash and timestamp) so that the user is automatically logged in, inside the Hub. You can also use oAuth2 for the SSO flow.

Note: Customers have to create an account in the Integration Hub before they can activate integrations. As part of the setup, they will also have to add credentials to your platform, by entering e.g. an API key or by using OAuth.

3.3 Connectivity Embed Pattern

The IoT industry is one of the most exciting emerging industries in the past decade. That said, it’s still in its early stages, one of the primary issues with the IoT industry as it is today is in the way that connectivity is handled.

The importance of embedded connectivity

Providing IoT users with embedded connectivity solutions helps to demystify the IoT industry, makes implementing the technology faster and smoother, and allows businesses to fully reap the rewards of this exciting technology faster and smoother, and allows businesses to fully reap the rewards of this exciting tech.

key reasons :

1) True digitization

Being able to test the connectivity of your products before they are shipped reduces potential risks and offers IoT customers a better product. It also reduces costs and saves time

2) Consumer ready products

It adds a new dimensionality to Plug and Play without requiring customers to add extra processes (or needing particular technical expertise) to connect their products, which costs them time and money

3) Improved security

Choosing to embed connectivity into your devices before they’re shipped also allows you to control what kind of connectivity options the devices will be capable of. This way, you know that your IoT products will be on the most secure networks possible, improving device security across the board

                      Figure: Source - Onomondo https://www.onomondo.com/