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 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 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