EDI XML Outbound File System Adapter Configuration

The EDI XML Outbound File System adapter extracts files from the file system to be used by the predefined EDI Translation business processes. By default, this File System adapter is not scheduled to perform automatic file collection.

Note: At a minimum you must edit User Parameter 1, User Parameter 2, User Parameter 3, User Parameter 4, and User Parameter 5 with the appropriate information so that the predefined business process recognizes that you are sending XML data.

This adapter collects files from the following directory:

install_dir/edioutbound/collect_xml

This adapter extracts files to the following directory:

install_dir/edioutbound/extract

The following table describes the default configuration of the EDI XML Outbound File System adapter:

Field	Description
Name	EDI XML Outbound File System adapter
Description	File System adapter
Group	None – No group is selected. This is the group associated with the adapter.
Collection folder	install_dir/edioutbound/collect_xml Where: The name of the folder on the same computer where the system is installed and where it collects (picks up) files as part of a business process. The deleteAfterCollect parameter in the GPM defaults to Yes. If you do not change the default value to No, any files collected are deleted from the Collection Folder. The File System adapter does not copy the files it collects for processing. The collectionFolder parameter is read-only in the GPM. However, you can override this parameter using BPML.
Filename filter	None. Since there is no specified filename filter, if there are multiple files in the collection folder, one of the following occurs: If the adapter is configured to start a business process, it processes all files placed in the collection folder. If the adapter is within a business process, it collects only the first file in the collection folder. If you modify this option using the File System adapter configuration, you cannot override the value using the GPM filter parameter. However, you can override this parameter using BPML.
Collect files from subfolders within and including the collection folder?	Yes – Collects files in the specified folder (install_dir/edioutbound/collect_xml) and all subfolders. This parameter is read-only in the GPM.
Use the absolute file path name for the document name?	Yes – The absolute file path name is kept with the document in the business process. Choose this value if your business process requires the path information to precede the file name. An absolute path is a path that points to the same location regardless of the working directory or combined paths. It is usually written in reference to a root directory. For example, c:\dir1\subdir1\somefile.txt (Windows) and /home/dir1/subdir1/somefile.txt (UNIX) are examples of absolute paths to the file somefile.txt. This parameter is read-only in the GPM.
Start a business process once files are collected?	Yes – Starts the EDIOutboundBootstrap business process. This parameter is read-only in the GPM.
Business Process	EDIOutboundBootstrap This is the name of the business process that is invoked.
Document storage type	System Default Defines how the document will be stored in the system.
Obscure File Contents?	No – File contents will not be obscured. Specifies whether to obscure the file contents when collecting. Does not work with “attachFile” or “importFile.” If you specify this parameter using the configuration, you cannot override this value using the GPM Obscure option. However, you can override this parameter using BPML.
User Parameter 1	Specify the XMLEnvelopeStandard (X12, EDIFACT, TRADACOMS, CII, ACH, or VDA), which notifies the EDIOutboundBootstrap business process that it is extracting XML data. This parameter is passed to the bootstrapped workflow and placed in process data as UserParm1.
User Parameter 2	Specify the XMLRootTag, the string that represents the subdocument root tag (for example, Root). This parameter is passed to the bootstrapped workflow and placed in process data as UserParm2.
User Parameter 3	Specify the XMLSenderIDPath, the XPATH string for the Sender ID element tag (for example, /Root/Sender). This parameter is passed to the bootstrapped workflow and placed in process data as UserParm3.
User Parameter 4	Specify the XMLReceiverIDPath, the XPATH string for the Receiver ID element tag (for example, /Root/Receiver). This parameter is passed to the bootstrapped workflow and placed in process data as UserParm4.
User Parameter 5	Specify the XMLAccepterLookupAliasPath, the XPATH string for the AccepterLookupAlias element tag (for example, /Root/Alias). This parameter is passed to the bootstrapped workflow and placed in process data as UserParm5.
Run As User	admin This parameter allows someone who doesn't have rights to a specific business process to run it. If you select Admin as the user ID, you will inherit Administrative rights (for this run of the business process only), and enable the scheduled run.
Use 24 Hour Clock Display	Not selected.
Schedule	Do not use schedule.
Extraction folder	install_dir/edioutbound/extract The name of the folder or subfolder on the same computer where the system is installed and where it extracts (writes) data from the primary document as part of a business process. This parameter is read-only in the GPM.
Unobscure File Contents?	No – File contents will not be unobscured. Whether to unobscure the file contents when extracting. Does not work with “exportFile.” This parameter is read-only in the GPM.
Filenaming convention	Use the original file name as the extracted file name – Keeps the names of the files. If the primary document has no document name, the adapter will use a default filename in the form of nodename_yyyyMMddHHmmssSSS.dat. This parameter is read-only in the GPM.