Hi,
I am using cloveretl engine with sqlserver's own jdbc driver.
In the target environment I have to use windows authentication - integratedSecurity.
The user that starts that can start the etl is different form the user that has access to the database.
To achive windows authentication for the db user, I use windows command: runas.
runas /env /user:domain\user "..\bin\clover.bat graph\mygraph.grf"
It is running fine, except for the watchdog output does not show processed records.
The etl process reads and writes the data that is expected, I just don't have visual feedback from it.
When running without 'runas' all works fine - unfortunately I cannot use that in the target environment.
Any ideas what can cause the watchdog to display 0 records during the run?
Thank you,
Csaba
I am using cloveretl engine with sqlserver's own jdbc driver.
In the target environment I have to use windows authentication - integratedSecurity.
The user that starts that can start the etl is different form the user that has access to the database.
To achive windows authentication for the db user, I use windows command: runas.
runas /env /user:domain\user "..\bin\clover.bat graph\mygraph.grf"
It is running fine, except for the watchdog output does not show processed records.
The etl process reads and writes the data that is expected, I just don't have visual feedback from it.
When running without 'runas' all works fine - unfortunately I cannot use that in the target environment.
Any ideas what can cause the watchdog to display 0 records during the run?
Thank you,
Csaba
-
I am not specialist for Windows shell, nonetheless I guess that the given command "..\bin\clover.bat graph\mygraph.grf" is run in different shell instance than the actual one. The probably easiest way is to simply redirect the stdout to an file:
runas /env /user:domain\user "..\bin\clover.bat graph\mygraph.grf > clover.log"
Equivalent solution could be done by log4j configuration:
runas /env /user:domain\user "..\bin\clover.bat graph\mygraph.grf -logcfg mylog4j.properties"
and refactor the build-in log4j.properties with a file appender or whatever you want.
Please sign in to leave a comment.
Comments 1