title: Does jobRepository have to use the same transaction manager as the JdbcBatchItemWriter?
body: <p>I am developing a Spring Batch enterprise application. The objective of the application is to write records to a table in a legacy database from the company I work for. That database is really big boy that stores business and customer information in huge number of schemas and tables with hundreds of millions of records, there are also hundreds of applications that connect to it: ERPs, CRMS, internal applications, .com.</p>
  
  <p>Because of that, I cannot create the job metadata tables needed by the jobRepository as I cannot create new tables in that legacy database. But at the same time I need to be able to monitor the jobs so I want jobRepository to point to another datasource.</p>
  
  <p>Should I just create another transaction manager and use it in the jobRepository? I am using tasklet steps with chunk tasks and JdbcBatchItemWriter</p>