Batch Application Naming Rules

1. Batch Job Processing Model

Below is the basic type of batch job processing model.

Figure 1. Batch Job Processing Model

2. Batch Application

BXM divides the application units for batch based on different management entities and units that can minimize function calls between applications. Applications are created through the 'Bxm Application' menu in Studio.

Batch Application Naming Rules
Classification	Description
Composition	L1 code + L2 code + L3 code + Batch
Example of Application	BxmDftSmpBatch
Basic Rules	Application names must follow the following notation rules: The first character of the system code and application code must be uppercase. The remaining characters must be lowercase. Application names must not be duplicated and must be unique across all businesses. Use Batch as the suffix.

3. Job

A Job is the logical unit of a batch business processing process, consists of multiple Steps, and becomes the execution unit of batch business. The name of a Job is written as follows.

Job Naming Rules
Classification	Description
Composition	J + L3 code + Unique identification ID
Example	JSmpAccountTaxSum JSmpTotalProc
Basic Rules	Job names must follow the following notation rules: The first character of each word must be uppercase. The remaining characters must be lowercase. They are defined with one character 'J' indicating batch, a 3-character L3 code, and a unique identification ID.
Example	`<job id="JSmpAccountTaxSum" restartable="true"> ... </job>`

4. Step

A Step is the minimum execution business unit of a batch. One Job has 1 to N Steps, and Steps are executed sequentially. When Steps are not executed sequentially but processed in Parallel Processing, use Split, which is a type of Step. The names of Steps and Splits are written as follows.

Classification Description

Classification	Description
Composition	JOB ID + 1-digit step serial number + 2-digit split serial number If there are only Steps, the numbers increase in the order of 100, 200.
Example	JSmpAccountTaxSum100 JSmpAccountTaxSum101
Basic Rules	1-digit step serial number: Assign sequential serial numbers (1,2,3…) to the main Steps of the batch job. 2-digit split serial number If the main Step is not split, it is fixed as "00". If it is split, assign sequential serial numbers (01,02…).
Example	Single Step `<job id="JSmpAccountTaxSum" restartable="true"> <step id="JSmpAccountTaxSum100"> ... ... </step> </job>` Multiple Steps `<job id="JSmpAccountTaxSum" restartable="true"> <step id="JSmpAccountTaxSum100" next="JSmpAccountTaxSum200"> ... ... </step> </job>` Split `<job id="JSmpAccountTaxSum" restartable="true"> <step id="JSmpAccountTaxSum100" next="JSmpAccountTaxSum200"> <flow> <step id="JSmpAccountTaxSum101"> ... ... </step> </flow> <flow> <step id="JSmpAccountTaxSum102"> ... ... </step> </flow> </step> <step id="JSmpAccountTaxSum200"> ... ... </step> </job>`

Composition

JOB ID + 1-digit step serial number + 2-digit split serial number

If there are only Steps, the numbers increase in the order of 100, 200.

Example

JSmpAccountTaxSum100

JSmpAccountTaxSum101

Basic Rules

1-digit step serial number: Assign sequential serial numbers (1,2,3…) to the main Steps of the batch job.
2-digit split serial number
- If the main Step is not split, it is fixed as "00".
- If it is split, assign sequential serial numbers (01,02…).

Example

Single Step

<job id="JSmpAccountTaxSum" restartable="true">
    <step id="JSmpAccountTaxSum100">
    ... ...
    </step>
</job>

Multiple Steps

<job id="JSmpAccountTaxSum" restartable="true">
    <step id="JSmpAccountTaxSum100" next="JSmpAccountTaxSum200">
    ... ...
    </step>
</job>

Split

<job id="JSmpAccountTaxSum" restartable="true">
    <step id="JSmpAccountTaxSum100" next="JSmpAccountTaxSum200">
        <flow>
            <step id="JSmpAccountTaxSum101">
                ... ...
            </step>
        </flow>
        <flow>
            <step id="JSmpAccountTaxSum102">
                ... ...
            </step>
        </flow>
    </step>
    <step id="JSmpAccountTaxSum200">
        ... ...
    </step>
</job>

5. Job Configuration File

The name of the file that sets the configuration of a Job is written as follows.

Job Configuration File Rules
Classification	Description
Composition	JOB ID + .xml
Example	JSmpAccountTaxSum.xml JSmpTotalProc.xml
Basic Rules	Create it in the META-INF/jobs folder of the project. Use xml as the file extension. One Configuration file contains one JOB.