JSR 352 TCK Execution (using RI against TCK Distribution ZIP)

Batch processing is a pervasive workload pattern, expressed by a distinct application organization and execution model. It is found across virtually every industry, applied to such tasks as statement generation, bank postings, risk evaluation, credit score calculation, inventory management, portfolio optimization, and on and on. Nearly any bulk processing task from any business sector is a candidate for batch processing. Batch processing is typified by bulk-oriented, non-interactive, background execution. Frequently long- running, it may be data or computationally intensive, execute sequentially or in parallel, and may be initiated through various invocation models, including ad hoc, scheduled, and on-demand. Batch applications have common requirements, including logging, checkpointing, and parallelization. Batch workloads have common requirements, especially operational control, which allow for initiation of, and interaction with, batch instances; such interactions include stop and restart.

License

License

Categories

Categories

Jakarta Batch Jakarta EE Jakarta EE Supporting Technologies
GroupId

GroupId

com.ibm.jbatch.tck
ArtifactId

ArtifactId

com.ibm.jbatch.tck.dist.exec
Last Version

Last Version

1.1-b03
Release Date

Release Date

Type

Type

pom
Description

Description

JSR 352 TCK Execution (using RI against TCK Distribution ZIP)
Batch processing is a pervasive workload pattern, expressed by a distinct application organization and execution model. It is found across virtually every industry, applied to such tasks as statement generation, bank postings, risk evaluation, credit score calculation, inventory management, portfolio optimization, and on and on. Nearly any bulk processing task from any business sector is a candidate for batch processing. Batch processing is typified by bulk-oriented, non-interactive, background execution. Frequently long- running, it may be data or computationally intensive, execute sequentially or in parallel, and may be initiated through various invocation models, including ad hoc, scheduled, and on-demand. Batch applications have common requirements, including logging, checkpointing, and parallelization. Batch workloads have common requirements, especially operational control, which allow for initiation of, and interaction with, batch instances; such interactions include stop and restart.

Download com.ibm.jbatch.tck.dist.exec

How to add to project

<!-- https://jarcasting.com/artifacts/com.ibm.jbatch.tck/com.ibm.jbatch.tck.dist.exec/ -->
<dependency>
    <groupId>com.ibm.jbatch.tck</groupId>
    <artifactId>com.ibm.jbatch.tck.dist.exec</artifactId>
    <version>1.1-b03</version>
    <type>pom</type>
</dependency>
// https://jarcasting.com/artifacts/com.ibm.jbatch.tck/com.ibm.jbatch.tck.dist.exec/
implementation 'com.ibm.jbatch.tck:com.ibm.jbatch.tck.dist.exec:1.1-b03'
// https://jarcasting.com/artifacts/com.ibm.jbatch.tck/com.ibm.jbatch.tck.dist.exec/
implementation ("com.ibm.jbatch.tck:com.ibm.jbatch.tck.dist.exec:1.1-b03")
'com.ibm.jbatch.tck:com.ibm.jbatch.tck.dist.exec:pom:1.1-b03'
<dependency org="com.ibm.jbatch.tck" name="com.ibm.jbatch.tck.dist.exec" rev="1.1-b03">
  <artifact name="com.ibm.jbatch.tck.dist.exec" type="pom" />
</dependency>
@Grapes(
@Grab(group='com.ibm.jbatch.tck', module='com.ibm.jbatch.tck.dist.exec', version='1.1-b03')
)
libraryDependencies += "com.ibm.jbatch.tck" % "com.ibm.jbatch.tck.dist.exec" % "1.1-b03"
[com.ibm.jbatch.tck/com.ibm.jbatch.tck.dist.exec "1.1-b03"]

Dependencies

There are no dependencies for this project. It is a standalone project that does not depend on any other jars.

Project Modules

There are no modules declared in this project.
com.ibm.jbatch.tck

Versions

Version
1.1-b03
1.1-b02
1.1-b01
1.0.1-noRelease
1.0.1-beta2
1.0.1-beta1