For Orchestrated Integration Trigger Connections

The following pages describe how to configure a File Adapter trigger connection in an orchestrated integration.

Basic Information Page

You can enter a name and description on the Basic Info page of each trigger and invoke adapter in your integration.

Element Description

What do you want to call your endpoint?

Provide a meaningful name so that others can understand the responsibilities of this connection. You can include English alphabetic characters, numbers, underscores, and dashes in the name. You cannot include the following:
  • Blank spaces (for example, My Inbound Connection)

  • Special characters (for example,  #;83& or righ(t)now4)

  • Multibyte characters

What does this endpoint do?

Enter an optional description of the connection’s responsibilities. For example: This connection receives an inbound request to synchronize account information with the cloud application.

Do you want to specify the structure for the contents of the file?

Select Yes to define a schema format for the transfer files. Select No if a schema is not required and you want to send opaque files (for example, a GIF or PNG file).

Which of the following choices would be used to describe the structure of the file contents?

Create a new schema with a CSV file or select an existing schema from your local system.
  • Sample delimited document (e.g. CSV)

  • XML schema (XSD) document

  • Sample XML document (Single on No Namespace)

  • Sample JSON document

Trigger Configure File Read Page

Enter the File Adapter trigger file read configuration values for your integration.

Element Description

Specify an Input Directory

Specifies the directory path for file reading.

Specify a File Name Pattern

Specifies the input file naming pattern.

Specify the Rejection Directory

Specify the directory in which to place rejected files.

Read Files Recursively Select to read subdirectory files recursively.

Maximum Files

Specifies the number of files to be processed in a single poll operation.

Polling Frequency

Specifies the polling operation frequency.

Processing Delay

Specifies the polling operation frequency delay.

Delete Files After Successful Reading

When selected, files are deleted after they are successfully read.

Ignore File Not Found Error in Delete

When selected, any file not found errors are ignored during file polling, and polling continues.

File Contents - Definition Page

Enter the format definition parameters.

The fields that display on the Format Contents - Definition page are determined by your selection on the Schema page:

Note:

  • If configuring the adapter in the trigger (inbound) direction, schema selection is not supported. If you select Yes to define a schema for the endpoint on the Basic Info page, nothing prevents you from uploading a schema on the Format Contents - Definition page. However, this schema is not used. You must select No on the Basic Info page to transfer files as an attachment.

  • The adapter can only be configured as an invoke connection in an orchestrated integration.

Creating a New Schema from a CSV File

Element Description

Select the Delimited Data File

Select the delimited comma-separated value (CSV) file from which to create the schema file. The content of the file is then displayed at the bottom of the page.

Enter the Record Name

Enter the record name. This becomes the parent element in the created schema file for the record names selected as column headers from the CSV file.

Enter the Recordset Name

Enter the recordset name. This becomes the root element of the created schema file.

Select the Field Delimiter

Select one of the following supported file delimiter options:

  • Single space

  • Comma

  • Semicolon

  • Tab

  • Pipe (for example, Name|City|Country)

Character Set

Select a character set. The selected value will be used as the encoding format while reading the sample data file.

This field is used for character encoding during file transfer. If data sent to the adapter is in a specific encoding format, then select that same encoding format in the adapter. Otherwise, there may be some character loss in the final written file. This also corrupts the file. For example, if a REST Adapter is using UTF-8 encoding and the adapter is configured with the ASCII character set, this may corrupt the file. If you select the same UTF-8 encoding in the adapter, the problem is resolved.

Optionally Enclosed By

This value causes occurrences of the selected delimiter to be ignored during processing. For example, when processing the following record:

Fred,"2 Old Street, Old Town,Manchester",20-08-1954,0161-499-1718

If the selected Field Delimiter is “,” and the Optionally Enclosed By value is quot; (), then the value 2 Old Street, Old Town,Manchester is treated as a single record column.

If Optionally Enclosed By is used, the character must not be part of any field. Therefore, the following is invalid:
  • a,b",c (In this scenario, " is part of the second field)
  • a,"b,c",d (In this scenario, the second field is created using Optionally Enclosed By ('"'). However, it has ',' as content for the second field value.)

Terminated By

Displays by default the first row of the selected CSV file as the column headers. Select the option to terminate the end of a line.

  • ${eol}
  • \n
  • \r\n
  • \r

Detach

Select to edit the CSV file in a separate window.

Use First Row as Column Headers Select to use the first row as the column headers.

Mark All As Optional

Select to mark elements as optional in the schema file. By default, all elements are mandatory. You can also select the data type (for example, string, byte, integer, and so on) to use for each column in the table and mark specific elements as optional. While this option enables you to select all elements as optional, you must have at least one mandatory element to validate this page. This checkbox provides a convenient method to select the majority of elements as optional.

Select an existing XML schema or schema archive from the file system

The schema archive can have a single top level schema with nested input and include elements containing absolute or relative paths.

Element Description

Select File

Select the existing schema file to use.

Selected File Name

Displays the selected schema file name.

Select the Schema Element

Select the schema element. This field is displayed after the schema file is selected. The element name is treated as the root element in the uploaded schema file.

Provide a sample XML document from the file system

The XML document should contain no namespaces or only a single namespace.

Element Description

Select File

Select the existing XML document to use.

Selected File Name

Displays the selected schema file name.

Select the Schema Element

Select the schema element. This field is displayed after the schema file is selected. The element name is treated as the root element in the uploaded schema file.

Provide a sample JSON document from the file system

Element Description

Select File

Select the existing JSON file to use.

Selected File Name

Displays the selected file name.

Select the Schema Element

Select the schema element. This field is displayed after the schema file is selected. The element name is treated as the root element in the uploaded schema file.

Summary Page

You can review the specified adapter configuration values on the Summary page.

Element Description

Summary

Displays a summary of the configuration values you defined on previous pages of the wizard.

The information that is displayed can vary by adapter. For some adapters, the selected business objects and operation name are displayed. For adapters for which a generated XSD file is provided, click the XSD link to view a read-only version of the file.

To return to a previous page to update any values, click the appropriate tab in the left panel or click Back.

To cancel your configuration details, click Cancel.