CloverETL code deployment

Support questions related to CloverETL Server

SnigdhaSahoo
Posts: 2
Joined: Fri Mar 14, 2014 11:22 am

CloverETL code deployment

Postby SnigdhaSahoo » Fri Mar 14, 2014 11:36 am

Hi All,
I am new to cloverETL. I have worked in SSIS before. I have a confusion about code deployment in cloverETL from dev environment to other environments like QA or Production. Is it Export/Import that does the deployment? Any document or any link to any example which describes the deployment process thoroughly? As SSIS has its own way for deployment.

Hoping for an early reply.

Regards,
Snigdha

kubosj
Posts: 372
Joined: Thu Jan 12, 2012 9:10 am

Re: CloverETL code deployment

Postby kubosj » Tue Mar 18, 2014 3:51 pm

Dear Snigdha,

Yes, export from Designer is one possibility. Also, because our projects/sandboxes are plain directories you can use VCS systems like git, cvs, svn, ... for deploy.

Also please see viewtopic.php?f=4&t=6750
Jaroslav Kubos
CloverCARE Support
CloverETL | Rapid Data Integration

Visit us online at http://www.cloveretl.com

martin_stangler
Posts: 4
Joined: Thu May 21, 2015 12:28 pm

Re: CloverETL code deployment

Postby martin_stangler » Fri Jan 15, 2016 1:19 pm

export/import approach is generally not very good. It is not very common to use exported project as-is with no customization) in enterprise environments

There are many problems to solve:
- environment specific artifacts (such as specific urls, credentials, ssh keys, ...)
- import/update/delete of schedules/services
- different jndi context format on tomcat (dev) and for example weblogic (other environments)

In my case shell script only installation is a must - use of designer is forbidden on some envs, server console is forbidden during installation.

I wrote my own installer shell script suite to call multiple methods of simple http api and web-dav using curl. Some task such as backup existing sandbox before push changes use web service api

There are many features missing in server api. I miss CRUD methods for schedules, launch services, users, ...