Skip to main content

Purpose and How to Read This Specification

intra-mart Accel Platform is built by bundling each individual feature into a unit called a module. To enable developers to assemble, with their own hands, this unit that forms the very foundation of the platform. That is the purpose of this specification.

A module is not merely a collection of code and resources. By placing code and resources into the designated predefined directories, tools can automatically convert a module project into a module. Furthermore, a module project must have module metadata that defines the module's own identification information and dependency information. This specification presents these conventions from two perspectives.

  • Project structure: Describes the resource layout, metadata, dependencies, and build procedure of the project used to produce a module. Covered in Module Project Structure.
  • File formats: Specifies each constituent element of the module metadata (module.xml) and the various Maven definition files. Covered in File Formats.

This specification does not re-explain the concept of modules themselves or the benefits of using modules. Also, before you begin creating a module, the development environment must already be set up. These topics are covered in the following documents.

The Mechanism for Creating a WAR​

To run Accel Platform, you must first create the configuration information through the IM-Juggling tool and then create a WAR file. From a DevOps and CI/CD perspective, you make use of a mechanism for creating the WAR file dynamically. The mechanism for manipulating IM-Juggling configuration information is covered in Manipulating IM-Juggling Configurations.