File system transport configuration
When you specify inbound and outbound file system application directories, the system creates subdirectories for its own use. The system must have permissions to create the subdirectories. Do not delete these subdirectories or copy files to them or retrieve files from them.
File system deliveries with metadata
Use the file system with message metadata transport when you want a community to produce MMDs to the file system on inbound deliveries. You configured this transport the same way you configure as the basic file system transport. See the following topics for additional information about using MMDs:
Configure the file system settings page
- Directory name – Enter the path to a directory on the trading engine server file system. If the directory does not exist, the system creates it.
- Preserve original filenames (application delivery only) – Select this option if you want original file names to be preserved when Activator delivers messages. This field applies to delivery exchanges only.
- For binary messages, we recommend that you preserve original file names. Otherwise, Activator assigns a unique file name that does not readily identify the contents of the file. Preserving original file names also allows your back-end application to process binary messages based on their file names.
- Overwrite duplicate filenames – This option is available when you select to preserve original file names. If duplicate file names are detected, Activator overwrites the existing file.
- Sequentially number duplicate filenames – This option is available when you select to preserve original file names. If duplicate file names are detected, Activator appends a number to the new file. For most transports, the appended number is consecutively numbered. For FTP and SFTP, however, the appended number is hexadecimal and looks like this:
filename_c4.
- Generate unique filenames (application delivery only) – Select this option to have the system provide a unique file name instead of using the original name. This field applies to community integration delivery exchanges and partner delivery exchanges only.
- When selected, files are given arbitrary names. The names always have less than 30 characters and often have less than 20 characters.
- Appended to the file name is a hex representation of a monotonically increasing file name counter that is maintained in the database and guaranteed to be unique. In addition, if the original file name had an extension, the same extension is appended to the unique name the system generates.
- The following are examples of unique file names generated by the system, one with the original file extension and one without:
-
dabeed45_4cb.edi
z47e4120_4ce
Exchange name page
- Name – Enter a name to identify the delivery exchange. This is the name that will be displayed in the interface.