You can do that by passing these properties as job parameters (those are best passed as non-identifying job parameters in this case) and late-bind them in your reader at runtime. Here is an example:

@Bean
@StepScope
public ItemReader<String[]> itemReader(
        @Value("#{jobParameters['fileName']}") String fileName,
        @Value("#{jobParameters['columnNames']}") String columnNames
        ) {
    return new FlatFileItemReaderBuilder<String[]>()
            .name("hacReader")
            //put file here
            .resource(new FileSystemResource(fileName))
            .lineMapper(new DefaultLineMapper<String[]>() {{
                setLineTokenizer(new DelimitedLineTokenizer() {{
                    //put column names here
                    setNames(columnNames.split(","));
                }});
            }})
            .build();
}

With this setup, the reader will be dynamically configured with the fileName and columnNames specified as job parameters:

JobParameters jobParameters = new JobParametersBuilder()
            .addString("fileName", "/path/to/input/file")
            .addString("columnNames", "column1,column2,column5")
            .toJobParameters();

Hope this helps.

Spring Batch provides java based configuration for the building of jobs via java code instead of XML. By using the provided builders, you can dynamically construct jobs as you need. I'd strongly suggest using this method instead of wiring a ChunkOrientedTasklet by hand since there is quite a bit going on in that particular Tasklet.

The best place to get started with Spring Batch's java configuration is in the Spring Batch guide: http://spring.io/guides/gs/batch-processing/. It's a 15 minute walk through on getting started with Spring Batch using tools like Spring Boot and java configuration.

Parse in job parameters from the command line and then create and populate JobParameters.

public JobParameters getJobParameters() {
    JobParametersBuilder jobParametersBuilder = new JobParametersBuilder();
    jobParametersBuilder.addString("dest", <dest_from_cmd_line);
    jobParametersBuilder.addDate("date", <date_from_cmd_line>);
    return jobParametersBuilder.toJobParameters();
}

Pass them to your job via JobLauncher -

JobLauncher jobLauncher = context.getBean(JobLauncher.class);
JobExecution jobExecution = jobLauncher.run(job, jobParameters);

Now you can access them using code like -

@Bean 
@StepScope
public Resource destFile(@Value("#{jobParameters[dest]}") String dest) {
    return new FileSystemResource(dest);
}

Or in a @Configuration class that is configuring Spring Batch Job artifacts like - ItemReader, ItemWriter, etc...

@Bean
@StepScope
public JdbcCursorItemReader<MyPojo> reader(@Value("#{jobParameters}") Map jobParameters) {
    return new MyReaderHelper.getReader(jobParameters);
}

There are various questions.

1. To disable starting all jobs automatically on startup just configure this Spring Boot property:

spring.batch.job.enabled=false # Do not execute all Spring Batch jobs in the context on startup.

2. You would run job like this:

java -Dspring.batch.job.names=prepareTeaJob -jar target/0910-job-parameters-cli-0.0.2-SNAPSHOT.jar sugarAmount="no sugar"

sugar amount there is Job parameter. Full example belonging to this listing is hosted in my Github Repository here. BTW, there are much more examples covering these various Spring Batch topics if you are learning Spring Batch.

3. Not sure what you are referring to as "ApplicationReadyEvent". AFAIK job should be executed after the Spring context it fully initialized.

Add the following property to your properties or yaml config to prevent automatic execution of jobs

spring.batch.job.enabled=false