Specifying Inbound Physical or Logical Directory Paths in SOA Composite Archiving Successfully Processed Files

Oracle JCA Adapter for FilesFTP 4-37 endpoint-activation operation=Read activation-spec className=oracle.tip.adapter.file.inbound.FileActivationSpec property name=UseHeaders value=false property name=LogicalDirectory value=InputFileDir property name=Recursive value=true property name=DeleteFile value=true property name=IncludeFiles value=.\.txt property name=PollingFrequency value=10 property name=MinimumAge value=0 property name=OpaqueSchema value=false activation-spec endpoint-activation adapter-config In the composite.xml file, you then provide the physical parameter values in this case, the directory path of the corresponding logical ActivationSpec or InteractionSpec. This resolves the mapping between the logical directory name and actual physical directory name. service name=FlatStructureIn interface.wsdl interface=http:xmlns.oracle.compcbpeladapterfileFlatStructureInwsdl.inter faceRead_ptt binding.jca config=FlatStructureIn_file.jca property name= InputFileDir type=xs:string many=false source= override=may homeuserinputDirproperty binding.jca service

4.3.1.2.2 Archiving Successfully Processed Files

This option enables you to specify a directory in which to place successfully processed files. You can also specify the archive directory as a logical name. In this case, you must follow the logical-to-physical mappings described in Section 4.3.1.2.1, Specifying Inbound Physical or Logical Directory Paths in SOA Composite.

4.3.1.2.3 Deleting Files After Retrieval

This option enables you to specify whether to delete files after a successful retrieval. If this check box is not selected, processed files remain in the inbound directory but are ignored. Only files with modification dates more recent than the last processed file are retrieved. If you place another file in the inbound directory with the same name as a file that has been processed but the modification date remains the same, then that file is not retrieved.

4.3.1.3 File Matching and Batch Processing

The File Filtering page of the Adapter Configuration Wizard shown in Figure 4–21 enables you to specify details about the files to retrieve or ignore. The Oracle File Adapter acts as a file listener in the inbound direction. The Oracle File Adapter polls the specified directory on a local or remote file system and looks for files that match specified naming criteria. 4-38 Oracle Fusion Middleware Users Guide for Technology Adapters Figure 4–21 The Adapter Configuration Wizard-File Filtering Page The following sections describe the file filtering information to specify: ■ Section 4.3.1.3.1, Specifying a Naming Pattern ■ Section 4.3.1.3.2, Including and Excluding Files ■ Section 4.3.1.3.4, Debatching Multiple Inbound Messages

4.3.1.3.1 Specifying a Naming Pattern

Specify the naming convention that the Oracle File Adapter uses to poll for inbound files. You can also specify the naming convention for files you do not want to process. Two naming conventions are available for selection. The Oracle File Adapter matches the files that appear in the inbound directory. ■ File wildcards po.txt Retrieves all files that start with po and end with .txt. This convention conforms to Windows operating system standards. ■ Regular expressions po.\.txt Retrieves all files that start with po and end with .txt. This convention conforms to Java Development Kit JDK regular expression regex constructs.