Changing CloverETL Server "server properties"

Support questions related to CloverETL Server

starsailor
Posts: 31
Joined: Tue Jun 04, 2013 9:05 pm

Changing CloverETL Server "server properties"

Postby starsailor » Wed Feb 04, 2015 12:38 am

I need to change my CloverETL Server v3.5.1 server properties, specifically to change the SMTP configuration. My server is running under Apache Tomcat.

I don't see a way to do this in the Server Console GUI, so I'm assuming I need to change the server properties using one of the methods document in "Chap. 19 Configuration", like editing the config file. Right? Is there another way to change the server configuration while it's running?

Assuming I edit the config file and restart the CloverETL WEB-APP using normal Tomcat procedures, what happens to jobs or graphs that were executing when I restarted the CloverETL server? Can you explain this in terms of processes and threads?

slechtaj
Posts: 192
Joined: Wed Aug 15, 2012 8:18 am

Re: Changing CloverETL Server "server properties"

Postby slechtaj » Wed Feb 04, 2015 1:40 pm

Hi starsailor,

In order to change Server SMTP configuration, you need restart the Server. If you are afraid of failing running job, you might suspend the Server at first and wait for all jobs to be finished. Then you can restart the Server, change configuration and start it again. If you decided to do so, make sure you click "Suspend" button instead of "Suspend at once" since the second option would kill all currently running jobs.

In case you want make sure no planned execution will be skipped, you may simply check "Fire misfired event as soon as possible" checkbox in your Scheduled task.

Hope this helps.
Jan Slechta
CloverCARE Support
CloverETL | Rapid Data Integration

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

How to speed up communication with CloverCARE support

starsailor
Posts: 31
Joined: Tue Jun 04, 2013 9:05 pm

Re: Changing CloverETL Server "server properties"

Postby starsailor » Thu Feb 05, 2015 12:28 am

Hi Jan,

Your instruction worked fine. Thanks.


cron