Outbound Operation Oracle File Adapter Write File Concepts

4-48 Oracle Fusion Middleware Users Guide for Technology Adapters element name=opaqueElement type=base64Binary schema schema targetNamespace=http:xmlns.oracle.compcbpeladapterfile xmlns=http:www.w3.org2001XMLSchema attributeFormDefault=qualified element name=OutboundFileHeaderType complexType sequence element name=filename type=string element name=directory type=string sequence complexType element schema wsdl:types wsdl:message name=Write_msg wsdl:part name=opaque element=opaque:opaqueElement wsdl:message wsdl:message name=Output_msg wsdl:part name=body element=FILEAPP:OutboundFileHeaderType wsdl:message wsdl:portType name=Write_ptt wsdl:operation name=Write wsdl:input message=tns:Write_msg wsdl:output message=tns:Output_msg wsdl:operation wsdl:portType wsdl:definitions You can select the Update Output Header checkbox in edit mode, and the output message header schema will be removed from the adapter WSDL.

4.3.2.2 Outbound File Directory Creation

For the outbound operation, you can specify the outbound directory, outbound file naming convention to use, and, if necessary, the batch file conventions to use. The File Configuration page of the Adapter Configuration Wizard shown in Figure 4–26 enables you to specify the directory for outgoing files and the outbound file naming convention. Oracle JCA Adapter for FilesFTP 4-49 Figure 4–26 The Adapter Configuration Wizard-Parameters for Outgoing Files The following sections describe the file configuration information to specify: ■ Section 4.3.2.2.1, Specifying Outbound Physical or Logical Directory Paths in Oracle BPEL PM ■ Section 4.3.2.2.4, Specifying the Outbound File Naming Convention ■ Section 4.3.2.2.5, Specifying a Dynamic Outbound File Name ■ Section 4.3.2.2.6, Batching Multiple Outbound Messages

4.3.2.2.1 Specifying Outbound Physical or Logical Directory Paths in Oracle BPEL PM

You can specify outbound directory names as physical or logical paths. Physical paths are values such as c:\outputDir. If you specify logical parameters, then the generated JCA file looks as follows for the logical outbound directory name OutputFileDir. ?xml version=1.0 encoding=UTF-8? adapter-config name=FlatStructureOut adapter=File Adapter xmlns=http:platform.integration.oracleblocksadapterfwmetadata connection-factory location=eisFileAdapter adapterRef= endpoint-interaction operation=Write interaction-spec className=oracle.tip.adapter.file.outbound.FileInteractionSpec property name=LogicalDirectory value=OutputFileDir property name=FileNamingConvention value=yyMMddHHmmssSS_SEQ_ yyyyMMdd_SEQ.out.SEQ property name=Append value=false property name=NumberMessages value=1 property name=OpaqueSchema value=false interaction-spec endpoint-interaction adapter-config