Directories/Maintenance

The directory structure for the installed product is as follows:

• .\ (VersaLex home) – Contains VersaLex executable files (VersaLex.exe, VersaLexc.exe) and other program files. If the Java Runtime Environment (JRE) terminates unexpectedly, trace or heap files may be created here. Archive or copy files may also accumulate in this directory.
  • .license\ – Contains product license files. Automatically created and updated when the product is registered or when a permanent license is acquired.
  • home\ – Default location used by file or directory chooser dialogs when no other default folder applies.
  • logs\ – Contains system XML logs (VersaLex.xml), system debug files (VersaLex.dbg), and other log output. Logging and retention behavior are configurable.
    • archive\ – Archived system XML log files. Storage location is configurable.
    • olddbg\ – Archived system debug files. Retention period is three days and cannot be changed.
  • inbox\ – Default parent directory for incoming payload files. The default system inbox can be configured.
  • outbox\ – Default parent directory for outgoing payload files. The default system outbox can be configured.
    • test\ – Files used for testing with the Cleo Test Server.
  • receivedbox\ – System defaults to no receivedbox. A default receivedbox can be configured.
    • archive\ – Archived receivedbox ZIP files.
  • sentbox\ – System defaults to no sentbox. A default sentbox can be configured.
    • archive\ – Archived sentbox ZIP files.
  • rejectbox\ – Default directory for rejected outgoing files. The default rejectbox can be configured.
  • AS2\ – AS2 protocol directories.
    • data\ – Message ID and filename history. The retention period can be changed in the AS2 service AS2 tab.
    • mdn\ – Message disposition notification (MDN) directories.
      • received\ – Received MDNs. Received MDNs are always retained. You can control the storage location. See MDN Storage Folder in the Local Listener AS2 Service reference.
        • archived\ – Archived MDN ZIP files. Archive properties can be configured. See Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
      • sent\ – Sent MDNs. You can control the storage location. See MDN Storage Folder in the Local Listener AS2 Service reference. For Cleo VLTrader and Cleo Harmony, sent receipts are always saved. For Cleo LexiCom, sent receipts can be configured. See Save Sent Receipt in Specifying Local Listener advanced properties.
        • archived\ – Archived MDN ZIP files. Archive properties can be configured. See Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
    • received\ – Copies of raw incoming messages. You control whether these messages are saved. See Store Raw Received Message in Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
    • sent\ – Copies of raw outgoing messages. You control whether these messages are saved per trading partner. See Store Raw Sent Message in AS2 Host: Advanced Tab. Archive or copy files accumulate in this directory.
    • restart\ – Partial incoming messages. You can change this storage location. See Restarts Temp Folder in the Local Listener AS2 Service reference.
    • unsent\ – Copies of outgoing messages waiting for an asynchronous MDN.
  • AS3\ – AS3 protocol directories.
    • data\ – Message ID history. You can control the retention period for this directory. See Retain Message ID History in the Local Listener AS3 Service reference.
    • mdn\ – Message disposition notification (MDN) directories.
      • received\ – Received MDNs. Received MDNs are always retained, but you can control the storage location. See MDN Storage Folder in the Local Listener AS3 Service reference.
        • archived\ – Archived MDN ZIP files. Archive properties can be configured. See Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
      • sent\ – Sent MDNs. You can control the storage location. See MDN Storage Folder in the Local Listener AS3 Service reference. For Cleo VLTrader and Cleo Harmony, sent receipts are always saved. For Cleo LexiCom, sent receipts can be configured. See Save Sent Receipt in Specifying Local Listener advanced properties.
        • archived\ – Archived MDN ZIP files. Archive properties can be configured. See Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
    • received\ – Copies of raw incoming messages. You control whether these messages are saved. See Store Raw Received Message in Specifying Local Listener advanced properties. Archive or copy files accumulate in this directory.
    • sent\ – Copies of raw outgoing messages. You control whether these messages are saved per trading partner. See Store Raw Sent Message in the AS3 Host Advanced tab. Archive or copy files accumulate in this directory.
    • unsent\ – Copies of outgoing messages waiting for an asynchronous MDN.
  • AS4\ – AS4 protocol directories.
    • data\ – Message ID history. Retention can be changed through the PMode.ReceptionAwareness.DuplicateDetection.MaxWindow setting.
    • ping\ – Payloads received as part of a Test Service PING operation.
      • receipt\ – Receipts generated by PING operations.
        • received\ – Receipts received during PING operations.
        • sent\ – Receipts sent during PING operations.
    • receipt\ – AS4 receipt directories.
      • received\ – Received receipts. Received receipts are always retained. You can control the storage location.
        • archive\ – Archived received receipts. These include receipt files and associated INF files. Archive properties can be configured.
      • sent\ – Sent receipts. Sent receipts are always retained. You can control the storage location.
        • archive\ – Archived sent receipts. Archive properties can be configured.
      • schemas\ – Schemas used by AS4 for XML schema validation.
      • sent+received\ – Copies of raw incoming and outgoing requests and responses for both client-side and server-side operations. Raw message storage can be configured. Files in this directory are not archived and should generally not be retained to conserve disk space.
      • unsent\ – Transient copies of outgoing User Messages waiting for synchronous or asynchronous responses. Files are deleted once transfers complete, and associated INF files move to receipt\received\.
• autoroute\ – Default directory for outgoing payload files to be automatically processed based on routing rules. This directory applies to Cleo VLTrader and Cleo Harmony systems only. You can configure the Autoroute Directory settings.
• autorun\ – Default directory for command files to be automatically processed. The Autorun directory can be changed through system options.
• backup\ – Versioned incremental patch backup files. Archive or copy files accumulate in this directory.
• BI\ – Business intelligence resource folder for dashboards and system monitoring. This directory applies to Cleo VLTrader and Cleo Harmony systems only.
• certs\ – Certificate storage for secure transfers.
  • pending\ – Trusted and pending X.509 certificate authority (CA) files used for secure communications. Certificates can be managed directly in this directory, though the Certificate Manager is the preferred method.
• conf\ – Product configuration files. These files are managed through various Configure and Tools menu options.
  • unsynced\ – Synchronized configuration changes that have not yet been applied.
• data\ – Certificate and private key storage for secure transfers, including X.509 user certificates, OpenPGP keys, and SSH keys. These files are managed using the Certificate Manager.
• jre\ – Java Runtime Environment used by VersaLex.
• lib\ – Core product library files.
  • api\ – Embedded custom API libraries. Custom classes can be specified through system options.
  • ext\ – Add-on third-party libraries, such as database drivers.
  • help\ – Product help library files.
  • ws\ – Web service client runtime libraries.
• local\root\ – Default FTP, HTTP, and SSH FTP server root directory. This directory applies to Cleo VLTrader and Cleo Harmony systems only.
• lostandfound\ – Incoming payload files for unknown trading relationships. You can control how unknown partner messages are handled through advanced system properties. Archive or copy files accumulate in this directory.
• resource\ – Installer resource files.
• temp\ – VersaLex non-persistent work area.
• thirdparty\ – Information about third-party software included with the product.
• translators\ – Subdirectories containing files used by EDI translators. See integration generation documentation for details.
• hosts\ – Active host XML files. These files are created when you activate a pre-configured host.
  • pre-configured\ – Pre-configured host XML files.
    • archive\ – Archived pre-configured hosts, including pre-release, beta, or backup hosts. This directory may be empty.
    • custom\ – Custom pre-configured hosts. See /hc/en-us/articles/360033982494Creating a custom pre-configured host.
  • support\ – Active support host XML files used for communicating with the Cleo website.
    • pre-configured\ – Pre-configured support host XML files.
  • unsynced\ – Synchronized host configuration changes that have not yet been applied.
• EBICS\ – EBICS protocol directories.
  • ack\ – Acknowledgment (receipt) directories.
    • sent\ – Acknowledgments sent.
      • archive\ – Archived acknowledgment ZIP files. Archive properties can be configured. Archive or copy files accumulate in this directory.
  • schemas_2_4\ – EBICS version 2.4 schema files.
  • schemas_2_5\ – EBICS version 2.5 schema files.
  • sent+received\ – Copies of raw incoming requests and outgoing responses. Storage of raw messages can be configured per host. Archive or copy files accumulate in this directory.
  • unsent\ – Transient copies of outgoing XML documents.
• ebXML\ – ebMS protocol directories.
  • ack\ – Acknowledgment (receipt) directories.
    • received\ – Acknowledgments received. Received ACKs are always retained. You can control where received acknowledgments are stored. Archive or copy files accumulate in this directory.
      • archive\ – Archived acknowledgment ZIP files. Archive properties can be configured.
    • sent\ – Acknowledgments sent. You can control where sent acknowledgments are stored. For Cleo VLTrader and Cleo Harmony, sent receipts are always saved. For Cleo LexiCom, sent receipts can be configured.
      • archive\ – Archived acknowledgment ZIP files. Archive properties can be configured.
  • data\ – Message ID history. You can control how long this data is retained.
  • schemas\ – ebMS schema files.
  • sent+received\ – Copies of raw incoming and outgoing messages. You can control whether raw messages are stored for received messages and per trading partner for sent messages. Archive or copy files accumulate in this directory.
  • unsent\ – Copies of outgoing messages waiting for asynchronous acknowledgment.
• OFTP\ – Odette FTP (OFTP) protocol directories.
  • data\ – Message ID history. You can control how long this data is retained.
  • eerp\ – End-to-end response (EERP) directories.
    • received\ – Received EERPs and NERPs. Received responses are always retained. You can control where received responses are stored.
      • archive\ – Archived EERP ZIP files. Archive properties can be configured. Archive or copy files accumulate in this directory.
    • sent\ – Sent EERPs. You can control whether sent responses are saved and where they are stored.
      • archive\ – Archived EERP ZIP files. Archive properties can be configured. Archive or copy files accumulate in this directory.
  • received\ – Copies of raw incoming messages. You control whether raw messages are saved.
  • sent\ – Copies of raw outgoing messages. You control whether raw messages are saved per trading partner.
  • restart\ – Partial incoming messages. You can change the storage location for these files.
  • unsent\ – Copies of outgoing messages waiting for an EERP.
• RNIF\ – RosettaNet Implementation Framework protocol directories.
  • ack\ – Acknowledgment (receipt) directories.
    • received\ – Acknowledgments received. Received ACKs are always retained. You can control where received responses are stored.
      • archive\ – Archived acknowledgment ZIP files. Archive properties can be configured.
    • sent\ – Acknowledgments sent. You can configure whether sent responses are stored and where they are stored.
      • archive\ – Archived acknowledgment ZIP files. Archive properties can be configured.
  • data\ – PIP instance and message ID history. You can control how long this data is retained.
  • DTDs\ – PIP content validation DTD files shipped with the product or imported.
  • pips\ – Pre-defined PIPs shipped with the product.
  • schemas\ – PIP content validation schema files shipped with the product or imported.
  • sent+received\ – Copies of raw incoming and outgoing messages. You can control whether raw received messages are stored and whether raw sent messages are stored per trading partner. Archive or copy files accumulate in this directory.
  • unsent\ – Copies of outgoing messages waiting for asynchronous acknowledgment.
• SMTP\ – SMTP protocol directories.
  • data\ – Message ID history. The retention period can be changed in the SMTP Service settings. You can control how long this data is retained.
  • dsn\ – Delivery status notification (DSN) directories.
    • received\ – Received DSNs. Received DSNs are always retained. You can control where received DSNs are stored.
      • archive\ – Archived DSN ZIP files. Archive properties can be configured. Archive or copy files accumulate in this directory.
    • sent\ – Sent DSNs. You can configure whether sent receipts are stored and where they are stored.
      • archive\ – Archived DSN ZIP files. Archive properties can be configured. Archive or copy files accumulate in this directory.
  • received\ – Copies of raw incoming messages. You can control whether raw received messages are stored. Archive or copy files accumulate in this directory.
  • sent\ – Copies of raw outgoing messages. You can configure whether raw sent messages are stored per trading partner. Archive or copy files accumulate in this directory.
  • unsent\ – Copies of outgoing messages waiting for a delivery status notification (DSN).
• HTTP\ – HTTP client protocol directories.
  • sent\ – Copies of raw outgoing messages. You can configure whether raw sent messages are stored per trading partner. Archive or copy files accumulate in this directory.
• WS\ – Web service protocol directories.
  • conf\ – Apache AXIS configuration and web service security files.
  • received\ – Copies of raw incoming web service messages. You can control whether raw received messages are stored.
  • sent\ – Copies of raw outgoing web service messages. You can configure whether raw sent messages are stored per trading partner.
• webserver\
  • VLPortal\ – Web portal documents, images, HTML pages, and language-specific property files. This directory applies to Cleo VLTrader and Cleo Harmony systems only. Files can be imported through web page and web portal build functions.
    • doc\ – Web portal document files.
    • img\ – Web portal image files.
    • html\ – Web portal HTML page files.
    • internationalization\ – Language-specific property files used by the web portal.

File accumulation and cleanup considerations

VersaLex does not automatically delete files in certain directories. Over time, files may accumulate in these locations, particularly if debugging or message retention options are enabled.

After troubleshooting is complete, disable any options that cause files to be retained longer than necessary.

Common examples include:

• Heap or diagnostic files created in the VersaLex home directory (.\)
• Raw AS2 received files stored under AS2\received\
• Debug files (*.dbg) written to subdirectories under logs\

Removing unused directories

VersaLex does not remove non‑empty inbound or outbound directories when a host or mailbox is renamed or deleted. This is intentional, as the same directories may be referenced by other trading relationships or external applications.

If you are confident that a directory is no longer in use, you may remove it manually.

Before doing so, verify that:

• The directory is not referenced by any active hosts or mailboxes
• No integrations or external processes depend on the files in that location

Manual cleanup should be performed with care, particularly in production environments.