Boomi File-System Implementation

Simple File-System state-management with Boomi

To start with the considerations we need a directory in which we store the state files. It is even better to have several (sub) directories to manage different states.

I recommend to use a shared directory to store states. However, for testing "no directory" is good enough ("No directory" with Disk v2 connector means: relative to Boomi Atom Directory).

A file-name represents to id of a state.

Boomi Solution

We use the Disk v2 connector and we keep all state-management processes (incl. required components) in the StateManager folder. There will be two independent subProcesses, called though a Route: subPr.saveState and subPr.readState:

Boomi Repository

States

A State is represented by j.State profile (see State-Management in general) and states are serialized and stored in files.

{
  "id" : "character",
  "key" : "character",
  "context" : "character",
  "userId" : "character",
  "userState" : "number"	/* # */,
  "userInfo" : "character",
  "payloadType" : "character",
  "payload" : "character"
}