While Spring Batch saves all the monitoring and job information to the database, let's understand each of the administration components of Spring Batch, how they interact with each other, and their configurations.
The database saves job-related information and acts as a source to monitor the job execution information.
A database can be configured using the following syntax:
<bean id="dataSource" class="org.apache.commons.dbcp.BasicDataSource"> <property name="driverClassName" value="${batch.jdbc.driver}"/> <property name="url" value="${batch.jdbc.url}"/> <property name="username" value="${batch.jdbc.user}"/> <property name="password" value="${batch.jdbc.password}"/> </bean> <bean id="transactionManager" class="org.springframework.jdbc.datasource.DataSourceTransactionManager" lazy-init="true"> <property name="dataSource" ref="dataSource"/> </bean>
The values of driverClassName
, url
, username
, and password...