Developing OTDs for Communication Adapters

Overview of the Batch OTDs

An OTD contains a set of rules that define an object. The object encodes data as it travels through OTDs which are used as the basis for creating Collaboration Definitions for a Project.

Each OTD acts as a template with a unique set of features of the adapter. The Batch Adapter OTD template is not customizable and cannot be edited.

The four parts of an OTD are:

A high-level view of the OTD folder structure shows methods and attributes you can use in creating Business Rules that invoke FTP, secure FTP, batch record, or local file data exchange.

Types of Batch Adapter OTDs

The figure shows the specialized OTDs available with the adapter.

Table 1–1 Batch Adapter OTDs

OTD Name

Description

BatchFTP 

Provides FTP access to remote systems. 

BatchFTPOverSSL 

Provides secure data transfer using FTP over SSL. 

BatchSCP 

Provides secure data transfer using Secure Copy Protocol with Secure Shell (SSH) as an underlying protocol. 

BatchSFTP 

Provides secure data transfer using SSH File Transfer Protocol or SFTP protocol. 

BatchLocalFile 

Provides easy access to local file systems. 

BatchRecord 

Allows the adapter to parse or create (or both) payloads of records in specified formats. 

BatchInbound 

Polls for input file, renames the file to a GUID, and triggers the Business Process or Collaboration. 

This chapter describes each of these OTDs and how to use them with the adapter.

OTD Functions

OTDs provide the following functions:

All OTDs must be configured and administered using NetBeans IDE. Any client components relevant to these OTDs have their own requirements. See the client system’s documentation for details.

For the BatchFTP, BatchLocalFile, and BatchRecord OTDs, only those nodes for which there is a corresponding section in the Environment or Connectivity Map properties (From the Properties Editor) are implemented on the OTD. The remaining nodes are not implemented and are reserved for potential future use.

For the BatchFTP, BatchLocalFile, and BatchRecord OTDs, only those configuration parameters which appear in the Environment or Connectivity Map properties (From the Properties Editor) are supported for use on the OTD. The remaining configuration parameters are not implemented, and are reserved for potential future use. Even though an implemented configuration parameter might be accessed and used from a non-implemented node, such use is not recommended.