You need an incrementer for this as usual.

<bean id="simpleIncrementer"
class="org.springframework.batch.core.launch.support.RunIdIncrementer"/>
<job id="myJob" incrementer="simpleIncrementer">
</job>

The trick for this incrementer to work with CommandLineJobRunner is adding the -next parameter when running the task.

-next: (optional) to start the next in a sequence according to the JobParametersIncrementer in the Job

Something like this:

java –jar myjob.jar jobs/myjob.xml myjob -next

I have an example which is to capture an exit code from spring batch called from Shell script.

JOB_RET=$?.

Hope it helps.

    #!/bin/bash
#
#  Launch Spring Batch
#
#Get the absolute path to the folder containing the folder this script is located in
BIN_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
HOME_DIR=$(dirname $BIN_DIR)
BATCH_HOME=$HOME_DIR
RUN_ID=$(date +"%Y-%m-%d %H:%M:%S")
LOG4J_CONF=file:$HOME_DIR/config/log4j.xml

function show_help {
    echo "usage:  $BASH_SOURCE -o <options> -d <month> -y <year>"
    echo "             where command is one of the following: "
    echo "                   options                    - Options (such as autoLogin|autoLogOut)."
    echo "                   month                      - Enter a month as Job param."
    echo "                   year                       - Enter a year as Job param."
    exit 1
}

# Read command line options
OPTIND=1         # Reset in case getopts has been used previously in the shell.
while getopts "ho:d:y:" opt; do
    case "$opt" in
    h)
        show_help
        exit 0
        ;;
    d)  options=$OPTARG
        ;;
    s)  month=$OPTARG
        ;;
    o)  year=$OPTARG
        ;;
    esac
done

JOB_PARAMS="options=$options month=$month year=$year"

#Run the job
$JAVA_HOME -cp "$(echo $HOME_DIR/lib/*.jar | tr ' ' ':') \
        -Djava.security.properties==$JAVA_SECURITY_FILE \
        -Dlog4j.configuration=$LOG4J_CONF \
        -DBATCH_HOME=$HOME_DIR -d64 \
               org.springframework.batch.core.launch.support.CommandLineJobRunner batch-jobs.xml <job-name> run.id="$RUN_ID" ${JOB_PARAMS} > $HOME_DIR/logs/stdout.log 2>&1

JOB_RET=$?
echo "Job returns $JOB_RET" >> $HOME_DIR/logs/stdout.log
exit $JOB_RET

https://bigzidane.wordpress.com/2016/06/26/launch-spring-batch-job-from-shell-script-sh/

If you are already using SpringApplication from Spring Boot, why not finish the job and use @EnableAutoConfiguration as well, and also the Maven plugin (see for example this guide)? That way you will get something working pretty quickly and you can always add your own features later.

However, any command executed by ssh cannot be executed in the background permanently

But you can do this via service/systemctl

[Unit]
Description=xxxx
After=network.target syslog.target

[Service]
Type=simple
Restart=always
ExecStart=/usr/local/jdk/bin/java -jar /opt/xxx.jar --spring.profiles.active=prod
ExecStop=/uss/bin/kill -9 $MAINPID
ExecReload=/uss/bin/kill -9 $MAINPID && /usr/local/jdk/bin/java -jar /opt/xxx.jar --spring.profiles.active=prod

[Install]
WantedBy=multi-user.target

But now I need to pass some job parameters also. How can I do that?

You can pass job parameters as key/value pairs:

java -jar mySpringBootApplication.jar -DJOB_NAME=myJob param1=value1 param2=value2

You can find more details in the Batch Applications -> Running from the Command Line section of the reference documentation.