This article describes the directories within local Atoms, Molecules, and Private Atom Cloud runtimes and is provided as an informational reference for administrators.
- Whenever available you should always make configuration changes and access data and execution history through the AtomSphere user interface to ensure data integrity.
- Unless specifically instructed to do so, note that modifying files in the local directories may result in the runtime becoming corrupted and non-operational.
- Unless specifically documented, note that file names, data formats, and the directory structure itself are not guaranteed and may change without notice.
|Directory||Description||Important for Support?||Notable Contents||Life Span of Contents||How Created||Potentially contains customer data?|
|<root>||Runtime installation root||Not typically||Permanent||Upon install||No|
Installation artifacts. Define JRE location used by Atom.
|accounts||Cloud only. List of tenant subdirectories for multi-tenant cloud runtimes. Each tenant has its own copy of data, execution history, process configuration, etc. directories.||Yes||Permanent||Upon account attachment||Yes (subdirectories)|
|accounts-deleted||Cloud only. Names of recently deleted cloud account attachments.||No||Purged periodically||Upon deleting account attachments||No|
|as2-mdn||Staging area for AS2 asynchronous MDN messages.||No||Momentary (Atom consumes immediately)||Upon AS2 process execution with asynchronous MDNs enabled||Yes (MDNs)|
|bin||Atom runtime executables and JVM configuration files.||Yes||Permanent||Upon install||No|
|component||Transient component XML metadata for components that have been test mode-executed or deployed to the Atom.||No||Permanent||Upon test mode executions or deployment||Yes (encrypted passwords)|
Additional Atom application configuration files.
Only contains connectors required by processes that have executed on this Atom. New connectors are downloaded automatically during first use.
|Yes||Permanent||Upon first execution requiring given connector||No|
Property files containing the next values for custom counters and trading partners.
Counter values should be modified through the Atom Management UI.
|Not typically||Permanent||Upon first use of a counter parameter or trading partner||No|
Actual document data files used during execution and subsequent document data viewer.
Do not modify. Uploaded via UI. Subject to Purge schedule.
|Not typically||Atom Purge Schedule||Upon every execution||Yes|
|doc||Start menu links to documentation. Windows install only||No||Permanent||Upon install||No|
Temp directory for Document Cache component.
Do not modify. Typically empty except during executions.
|No||Single execution||Upon execution that uses a document cache||Yes (temporarily)|
Additional runtime library files.
Do not modify.
Process execution artifacts including Process and Document logs.
Do not modify. Subject to Purge schedule.
|Not typically||Atom Purge Schedule||Upon every execution||Yes (execution/history)|
|jre (optional)||Contains a local copy of the Java runtime if you have the installer or upgrader install or update its own copy of Java.||Permanent||Upon install (optional)||No|
Core runtime libraries.
Do not modify.
|Not typically||Permanent||Upon install||No|
Daily container logs, HTTP server logs, local user logs.
Subject to Purge schedule. Important for operational runtime monitoring.
|Yes||Atom Purge Schedule||Daily while Atom is running||No|
Staging area for messages exchanged with the platform.
Messages include Atom status, execution metadata, test mode results, UI-requested info, etc.
|Not typically||Momentary (Atom consumes immediately)||Continuously; upon every execution||No|
Cache for OAuth 2.0 tokens.
|Not typically||Permanent||Upon token generation||Yes (tokens)|
|plugins||Additional configuration and deployment artifacts for optional functionality such as the shared web server, API components, MDM universes, etc.||No||Permanent||Upon deployment of certain functionality||No|
|process||List of processes attached/deployed to this Atom.||Not typically||Permanent||Upon process attachment/deployment||No|
|processes||Deployment Version versions of Component XMLs for processes and their dependent components. Used exclusively for deployed-process executions.||Not typically||Permanent||Upon process attachment/deployment||Yes (encrypted passwords)|
|queue||Persisted Atom Queue contents. Does not contain actual document data, instead contains pointers to document data residing in data directory.||Not typically||Atom Purge Schedule (but not Purge Immediately)||Upon first execution using Atom Queue connector||Yes (for Low Latency executions)|
|resources||Non-process deployed components (e.g. certificates, process routes).||Not typically||Permanent||Upon deployment||No|
|settings||Extension values for deployed processes.||Not typically||Permanent||Upon Atom/Environment extension configuration||Yes (encrypted passwords)|
|settings-test||Extension values for test-mode processes.||Not typically||Permanent||Upon configuring test mode extensions||Yes (encrypted passwords)|
|tmp||Temporary files for the Atom, including process execution artifacts.||No||Atom Purge Schedule||Upon every execution||Yes|
|tmpdata||Temporary files for process executions when "Purge Immediately" is enabled.||No||Single execution||Upon every execution||Yes (but purged immediately)|
|update||Temporary space for applying Atom executable updates.||No||Temporary (during update only)||Upon Atom executable updates||No|
Contains additional libraries (jars) for some types of connectors, custom scripts, etc.
Must create manually. Can contain subdirectories.
|Yes||Permanent||Created manually when needed for connector libraries/drivers, custom scripting libraries||No|
|work||Working copies of the core and connector libraries to be loaded into memory at runtime as well as some history execution artifacts including AS2 communications and Find Changes.||Not typically|
/as2 is subject to Atom Purge Schedule
|Upon Atom start, process execution||Yes|