I'm seeing a bunch of files from various dates in \application\BusinessConnect\working\tibcobc_temp and tibcobc_shared. What are those files and is it safe to remove them? As an example:

working\tibcobc_temp\tibcobc_edi_cache_store_Batching-sib2b01-pd-Interior-Server

working\tibcobc_temp\tibcobc_edi_cache_store_LargeFile-sib2b01-pd-Interior-Server

working\tibcobc_temp\tibcobc_edi_cache_store_Sync-sib2b01-pd-Interior-Server

working\tibcobc_temp\tibcobc_edi_file_system_sib2b01-pd-Interior-Server-2

I'm seeing a large number of files with various timestamps the in \application\BusinessConnect\working\tibcobc_temp and tibcobc_shared directories. What are those files and is it safe to remove them?

EDI 6.x

EDI makes extensive use of local temp and shared temp directories. The temp directory is used for processing large files, for streaming and preprocessing EDI data (as well as batching process). It internally caches it for each run. The files that have transactional data are controlled by the internal caching mechanism which rolls over into the file system. When the engines are brought down, these directories are cleaned up and recreated when the engines are restared.

We have made 4 partitions (1 for Batching, 1 Sync, 1 for LargeFile and 1 for Generic).  These subdirectories are in local temporary location defined in the deployment. Folder name starts tibcobc_edi_cache_store_<Batching|Sync|LargeFile|Generic>-<instanceName> and there is a file with one prefix starting Batching|Sync|LargeFile|Generic>_edi_cache_seg_<guid>.data.  

These files are not persistent between engine runs, but only for the duration the engines are running. So, working/tibcobc_temp/ tibcobc_edi_cache_store_Generic* can be safely removed after the engines
are stopped.

These files can be zero length in certain cases when the rollover from memory to disk is not needed. There is a default threshold beyond which some files with .data would have transactional data. The threshold is per data file and is removed once the message is processed. These files are also controlled by the caching mechanism and are considered as partitions internally.

When the engine is running, it is not safe to remove the files. There is one file per partition (partition is interchange, group, txn, segments, elements etc) and these are written to disk if the threshold is exceeded.

In some cases, these files are may not deleted from the temp directory as part of normal engine housekeeping.  In this case, you can manually delete these files which are old enough (i.e. with a timestamp over one day old).