Tag Archives: CloverETL OEM

DataMotion: CloverETL’s Newest OEM Partner

Leave a reply

CloverETL offers a choice. This has been part of our philosophy since day one. Flexibility. Scalability. Robustness. These principles are fundamental to us—and also what set us apart in the market. With these strengths at the forefront of our offering, our mission is simple: to craft a tailored approach for customers looking for that “just right” ETL/Data Integration relationship. This just makes sense to us. So with this firm belief, we continue look for new ways to make great things happen for our customers.

Our OEM strategy is no different. As described in an earlier blog, CloverETL works as OEM in three ways: OEM Partner, OEM Embedded, and OEM Embedded White Label.

For us, the ability for customers to shape and style a unique OEM relationship with us really transforms the OEM conversation. When a partnership is involved, it’s a serious marriage—one in which we work closely together, count on each other, and move forward towards success. A strong OEM relationship comes not only when two product offerings sync well, but when the companies’ goals do too. This is what we strive for because after all, an OEM partner’s success is, in a sense, ours too.

The OEM Partner

In certain cases, a company may just need a little something extra. This is a great way we two companies can shine individually—together. Naturally, this is what we call the partner approach.

OEM Partner companies use CloverETL alongside their offer to provide an integrated package to their end-user clients. And this is great not only for our customers, but also for their clients, who gain access to the Clover community through both our resources and licensing of CloverETL. We support these indirect customers—users who come to CloverETL through our OEM. We welcome them; they are the in-laws, so to speak. Helping our partners means making sure that their clients get exactly what they need to move forward with projects too. Here is where our flexible architecture is a plus: our dev team can work on our ETL offering, while their team can offer the right support to their users who are implementing it. This partnership means we work together to bring the right solutions to the right customers.

CloverETL and DataMotion

Let’s take a look at a real life partner of ours—a really exciting and interesting case. DataMotion, a company that offers software, consulting, development and implementation services of CRM, Direct Marketing and Data Quality solutions in Brazil, fits under this partner umbrella well.

Before they found Javlin, “DataMotion was a frustated user of SQLServer SSIS. So, we were searching for a new, powerful and accessible ETL solution,” said Ricardo Rego, Managing Partner of DataMotion.

He continues, “In the middle of last year, we started to look at the market for a new data integration flagship technology. We were performing due diligence in readiness for start-up. Part of this planning phase included selecting a software vendor that could support the delivery of professional service engagements and help the business grow using a common integration platform. Our decision went to Javlin and CloverETL.”

With them, CloverETL works as a critical software component together with their growing suite of data solutions. As business in Brazil propels forward, especially in the data-heavy verticals of healthcare, retail, and finance, companies are looking to harness the business value from their data assets. For this, they turn to DataMotion with CloverETL for support. “With CloverETL, DataMotion will be able to provide a solid rock data management and integration services to all SME in Brazil and Latin America. This is a special momentum where the Brazilian economy is growing very fast and the enterprise commitment combined with the quality of the information is critical and mandatory to the success of businesses,” said Rego.

As we have seen working with a diverse mix of partner relationships, this approach is definitely something special: it works like a “power couple” to provide real value to data clients.

When Two Become One: CloverETL OEM Embedded White Labeling

Leave a reply

In our previous post, we reviewed the three approaches to CloverETL OEM—Here, I’ll discuss the more technical aspects of CloverETL OEM Embedded White Labeling.

OEM White Labeling – What it Takes

When partners needs white labeling, they are mostly considering the seamless integration of the ETL piece with their application. They have to manage things like version control of their application (making sure it works with Clover), the look and feel of the GUI, and a good sense of automation, for example. The Clover team works with the partner to architect this and can do so quickly.

Partners needing this option receive CloverETL Integration documentation to guide them through the process of achieving stable, effective white labeling. Both the CloverETL Designer and CloverETL Server can also be white labeled as part of a company strategy.

Which steps does white labeling consist of in Designer and Server?

CloverETL Designer

CloverETL Designer branding is based on showing the product name, splash screen, welcome screen, etcetera inside the Eclipse environment. Applications embedding or extending CloverETL Designer can use the same branding elements to visually customize the product. Features available via branding:

  • Product naming and description: These are visible in multiple places inside Eclipse (however, not all occurrences can be changed.)
  • Default configuration: Eclipse configuration options can be changed according to users’ needs, e.g. whether a splash screen should be shown at start-up.
  • Splash screen: The initial image shown at start-up and the progress bar can be customized.
  • Welcome screen: An introduction screen shown to users on the application’s first run; it can contain useful links to documentation, examples etc.

CloverETL Server

CloverETL Server is mentioned in multiple messages, web GUI images, directory names, etc. Following steps described in the integration documentation (available to OEM partners), you can get rid of all CloverETL occurrences. White labeling Server thus involves:

  • Replacing images, logos plus related work on graphics
  • Editing a couple of properties stored in server configuration files
  • Tuning the resulting application

CloverETL OEM Advantage: ETL As You Like It

Leave a reply

Shakespeare didn’t know the first thing about OEM, or Original Equipment Manufacturers, but he did have quite a grasp on relationships. That being said, we’re here to put what Will preached back into the data world, channeling his penchant for the complexity of true relationships, with our OEM Program. Introducing, “ETL As You Like It: A True OEM Partnership.”

What is a CloverETL OEM Partnership?

Well, it really is a relationship, isn’t it? When CloverETL aligns with a company, we bring together not just our unique products, but also our tested dev teams, solutions, and ideas. It’s actually like a marriage—with joys and delights, compromise and adjustment. We’ve been active in OEM Partnerships for a while now and think it’s a great way for Clover to flourish in all sorts of challenges.

Today, CloverETL is at the core of many data service platforms as a vital data integration piece. As an OEM to many customers’ larger offerings – be it with IBM’s MDM offer, Good Data’s BI platform, or Mulesoft’s ESB service – Clover, with its flexibility, lends itself to match any OEM business strategy. It’s just a matter of deciding which OEM approach works best. CloverETL can work on a “partner basis” (side by side as a toolset), be embedded as a data integration piece, or even be embedded and white labeled.

Let’s take a look at what OEM programs are available for Clover today.

Partner Approach

Some companies use CloverETL alongside their offer to provide an integrated commercial package to their end-user clients. These clients can then have access to the Clover community through our forum to gain knowledge about the best use practice of CloverETL. Often, companies are replacing just the ETL bit because it is either hand-coded or just too cumbersome.

The data services companies that choose this option tend to need a lower volume of licenses. Another reason might also be to simply add a stronger ETL product to an application or service without the need to fully embed Clover. In a sense, the partner approach works like a “power couple” to run compelling applications that provide value to data clients.

Embedded OEM

Many businesses prefer the embedded OEM approach for CloverETL because they only have to manage one offering for their development teams. To embed means that as they make changes and improvements to their application, Clover and its team can adapt with a company’s growth in an evolving market. We offer this option in higher volume scenarios on a per unit basis, or even on an enterprise (one time fee) basis as the case allows.

For example, there are literally hundreds of Clover users for IBM’s Initiate MDM offer; the company, a partner since 2007, even produced a CloverETL user guide to help their clients learn and use Clover more effectively.

You can check out this IBM WorkBench document at: http://publib.boulder.ibm.com/infocenter/initiate/v9r5/topic/com.ibm.initiatepdfs.doc/topics/i46wecug.pdf

Embedded OEM – White Labeling

Lately, we are seeing a trend from customers asking for a white labeled ETL/data integration piece for their service offer. This is part of an interesting strategy where service providers simply want to present their offer with a focus on the application or the power of the company brand. IT and data professionals know that the ETL is there, cranking through and organizing data, but a white label strategy puts the ETL behind the scenes for a complete, branded look: Voila! The service just works, it seems. White labeling has the same licensing strategy as embedded-only OEM approach.

—

In all, David Pavlis, Javlin’s President put it best: “What’s great about Clover is that we want to work with you, and you can rely on us. We can adapt alongside your offering or become part of it, fully integrated. What we do know is that, in every case, we can support a lifetime partnership–adapting, improving, and aligning to where our customers and their clients are going.”

And there you have it, as you like us.

—

Interested in the technical nuances of OEM? Our OEM blog series will continue, detailing each approach reviewed today, so check back soon.