Postprocessing Native Data Translation

Oracle JCA Adapter for FilesFTP 4-45 XSD files are required for translation. If you want to define a new schema or convert an existing data type definition DTD or COBOL Copybook, then select Define Schema for Native Format . This starts the Native Format Builder wizard. This wizard guides you through the creation of a native schema file from file formats such as comma-separated value CSV, fixed-length, DTD, and COBOL Copybook. After the native schema file is created, the Messages page is displayed, with the Schema File URL and Schema Element fields filled in. For more information, see Section 6.1, Creating Native Schema Files with the Native Format Builder Wizard.

4.3.1.7 Inbound Service

When you finish configuring the Oracle File Adapter, a JCA file is generated for the inbound service. The file is named after the service name you specified on the Service Name page of the Adapter Configuration Wizard. You can rerun the wizard later to change your operation definitions. The ActivationSpec parameter holds the inbound configuration information. The ActivationSpec and a set of inbound Oracle File Adapter properties are part of the inbound JCA file. Table 4–5 lists the properties of a sample inbound JCA file. The ActivationSpec property values are specified in the Adapter Configuration Wizard during design time and, as shown in Table 4–5 . The inbound Oracle File Adapter uses the following configuration properties: ■ PollingFrequency ■ MinimumAge ■ PhysicalDirectory ■ LogicalDirectory ■ PublishSize ■ PhysicalArchiveDirectory ■ LogicalArchiveDirectory ■ IncludeFiles Note: Ensure that the schema you specify includes a namespace. If your schema does not have a namespace, then an error message is displayed. Table 4–5 Sample JCA Properties for Inbound Service Property Sample Value UseHeaders true PhysicalDirectory tmpopaquein Recursive true DeleteFile false IncludeFiles .\.xml PollingFrequency 1 MinimumAge 4-46 Oracle Fusion Middleware Users Guide for Technology Adapters ■ ExcludeFiles ■ UseHeaders ■ ListSorter ■ ThreadCount ■ Recursive ■ MaxRaiseSize For a description of these configuration properties, see Appendix A of this book.

4.3.1.8 Inbound Headers

Apart from the payload, Oracle File Adapter publishes the following header metadata, from the inbound service, as shown in Figure 4–24 : ■ jca.file.FileName: file name ■ jca.file.Directory: directory name ■ jca.file.Batch: a unique name for a batch in case of debatching ■ jca.file.BatchIndex: the batch index for each message within the batch for debatching ■ jca.file.Size: the file size ■ jca.file.LastModifiedTime: the last modified time for the file Figure 4–24 The Invoke Dialog

4.3.2 Oracle File Adapter Write File Concepts

In the outbound direction, the Oracle File Adapter receives messages from the service engine and writes the messages to a file in a file system. This section provides an overview of the outbound file writing capabilities of the Oracle File Adapter. You use the Adapter Configuration Wizard to configure the Oracle File Adapter for use with a BPEL process or a Mediator Service. This creates an outbound WSDL and a JCA file pair. This section includes the following topics: