BOX Manager
A Buildable Object eXchange (BOX) is a file package consisting of a collection of related system configuration files. Through the IDE, a BOX is transferred from one system root to another. Every BOX has a manifest file to record its content, the time of creation, the version, and descriptive notes.
BOX also provides the ability to share configuration resources between system sites on several hosts.
A BOX can include these objects:
- Thread/destination and its process definition
- Database schemas
- Tcl procs
- Java UPoCs
- PDLs
- Variants of message format
- EO configurations
- Xlate and XSLT
- Lookup tables
A BOX can also include these on the physical file level:
- NetConfig and thread/process notes files
- Database schema files and corresponding database configuration
- Tcl script files
- Java UPoC class files
- PDL files
- Format files: FRL, VRL, HRL, LDL, XML, HL7, X12, and other HMD variant files
- EO configuration files
- Translation configuration files, XSLT files, Lookup table files
An audit trail is created when creating, importing, exporting, deploying, and creating a site for a BOX. This trail is viewed from the Audit Log Viewer.
If your Java classes are packaged to a jar file, then you can add this file to the BOX using the GUI. Its original folder structure is remembered in the BOX manifest.xml file during BOX creation.