Home
IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
Lotus® Connectors
Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
Lotus® Connectors and Connectivity Guide
Chapter 11 Lotus® Connector for Text
This chapter provides information about the Lotus® Connector for Text, including descriptions of the fields in the connection document.
Connector for Text terminology
The following table lists IBM® Lotus Enterprise Integrator® (LEI) terms and the corresponding terms used by the Lotus® Connector for Text.

IBM Domino Designer Basic User Guide and Reference
Basic product usage information and programming language reference information.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Domino® Designer templates
  The templates described in the following table are available with Domino® Designer and are specifically intended for use by application developers.
- Importing to and exporting from views
- Developing applications using MAPI
  Domino® Designer Release 6 and later supports the messaging application program interface (MAPI), which allows mail integration between Domino and a MAPI-compliant messaging application, such as Microsoft™ Outlook, Microsoft Office applications, or user-written C++ programs.
- Features to avoid using in Web applications
  Developers creating applications specifically for the Web, or for the dual purpose of serving Notes® and Web clients, should review the following tables for features that are not supported on the Web.
- URL commands for Web applications
  You have a variety of options for programming a Web site. You can directly manipulate objects such as documents or views in an application using Domino® URL commands. Adding Domino URL commands as HTML in forms gives users shortcuts for navigating databases and performing other tasks quickly.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Composite Applications - Design and Management
  Composite applications are a key element in a service-oriented architecture (SOA) and contextual collaboration strategy. The ability to create and edit composite applications lets you easily integrate different types of components and technologies.
- DB2® Access views
  Domino® Designer includes two types of design elements to assist you in managing data contained in DB2® enabled Notes® databases:
- Programming Overview and User Interface
  This section contains general guidelines and examples that show where to use Java, LotusScript, and the formula language.
- Formula Language
  This section documents the formula language.
- LotusScript® Language
  Welcome to the LotusScript® Language section of Domino® Designer Help.
- LotusScript/COM/OLE Classes
- Java/CORBA Classes
  This section documents the Java/CORBA classes.
- Lotus® Connectors
  Lotus® Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
  - Lotus® Connectors and Connectivity Guide
    - Chapter 1 DCTEST and CONTEST
      This chapter provides information about DCTEST and CONTEST. These programs test system and application connectivity to external data sources.
    - Chapter 2 Connectivity
      This chapter provides instructions and information for setting up and testing connectivity to the following database systems:
    - Chapter 3 Introduction to Lotus® Connectors
      This chapter provides introductory information about each of the supplied IBM® Lotus® connectors.
    - Chapter 4 Lotus® Connector for Notes®
      This chapter provides information about the Lotus® Connector for Notes®, including descriptions of the fields in the connection document.
    - Chapter 5 Lotus® Connector for DB2®
      This chapter provides information about the Lotus® Connector for DB2®, including descriptions of the fields in the connection document.
    - Chapter 6 Lotus® Connector for File System
      This chapter provides information about the Lotus® Connector for File System, including descriptions of the fields in the connection document.
    - Lotus® Connector for ODBC
      For complete information on the Lotus® Connector for ODBC, refer to the documentation on the Notes® Domino® Application Development wiki.
    - Chapter 8 Lotus® Connector for Oracle
      This chapter provides information about the Lotus® Connector for Oracle, including descriptions of the fields in the connection document.
    - Chapter 9 Lotus® Connector for OLE DB
      This chapter provides information about the Lotus® Connector for OLE DB, including descriptions of the fields in the connection document.
    - Chapter 10 Lotus® Connector for Sybase
      This chapter provides information about the Lotus® Connector for Sybase, including descriptions of the fields in the connection document.
    - Chapter 11 Lotus® Connector for Text
      This chapter provides information about the Lotus® Connector for Text, including descriptions of the fields in the connection document.
      - Introduction to the Lotus® Connector for Text
        This chapter provides information about the Lotus® Connector for Text. The Lotus Connector for Text can be used with Lotus Enterprise Integrator® for Domino® (LEI), and Lotus Connector LotusScript® Extensions (LC LSX).
      - Connector for Text terminology
        The following table lists IBM® Lotus Enterprise Integrator® (LEI) terms and the corresponding terms used by the Lotus® Connector for Text.
      - Supported characteristics of the Connector for text
        The following list captures supported characteristics of the Lotus® Connector for Text.
      - Field Options and Text Information Definition Syntax
        When specifying information in the ZMerge Field Specifications and Source and Target Options sections of the connection document, you will need to be familiar with the field and format information described here.
      - Defining Source Files
        This section provides examples showing how to define test and binary files that are organized in several different ways: single line, multiple line, fixed length fields, and floating field format.
      - Text Input Files Using Multiple Lines per Record
        The Text connection can also read input records from multiple contiguous lines of text. A multiple line per record format requires that you specify an input record delimiter (a unique character or string of characters) to denote the end of one input record and the beginning of the next input record. Specify the input record delimiter in the Text connection. The record delimiter string can be up to 256 characters long. Usually the input record delimiter is a single character such as a form feed (\f) character or a paragraph symbol (¶).
      - Binary Input Files Using Fixed Length Records
        Data in binary files can only be organized as fixed length records. All records contain the same amount of data (number of bytes). With binary files, a record consists of one or more fields of a given fixed length. You specify the fixed size of input binary data records with the record delimiter specification in the Text Connection. Binary input files most closely resemble the text fixed field format. As with the text fixed field format, fields within binary files must exist at the same location and have the same length in every input record.
      - Defining Target Files
        Output records can be single or multiple line text. You can generate multiple lines by designating carriage returns or line feeds as UNTIL strings.
      - Using Field Options
        You can use field options to describe the location of fields in both fixed and variable records and also to format the data. As described previously, include the desired field option following the field entry.
      - Text Connection Document for LEI
        The Text connection document defines the location and format of the text data. Text connections are defined as source or destination processing options, specifying the location and format of the data in its destination. The format and basic methodologies are the same for each specification.
      - Fields in the LEI Connection Document - 6
        This section describes the connection document fields.
      - Lotus® Connector for Text Data Types
        The following tables show the correspondences of Lotus® Connector for Text data types to IBM® Lotus Enterprise Integrator® (LEI) data types for various types of activity.
    - Chapter 12 Metaconnectors for LEI
      This chapter provides an introduction to LEI Metaconnectors and contains information for creating and using the different types of Metaconnectors.
  - LSX for Lotus® Connectors
    LotusScrip Extensions for Lotus® Connectors (LC LSX) enhances the power of Notes® by extending its scripting to data outside of Notes through the use of Lotus Connectors. The programming model is independent of the individual connector. This eliminates the need to learn each individual system, while at the same time allowing experienced users to access the individual features of a specific system.
  - Accessing external databases through LS:DO
    LS:DO has been in maintenance mode since R5. Developers are advised not to use it. Developers should use the Lotus® Connector LSX for (LCLSX) when accessing external data sources.
- Javadoc™ for Domino® Designer related APIs
  As part of providing additional Java™ reference documentation, Domino® Designer ships with a help plugin that contains Javadoc™ for additional Domino Designer related APIs.
- Accessibility and keyboard shortcuts
  Accessibility features assist users who have a disability, such as restricted mobility or limited vision, to use information technology content successfully.

Connector for Text terminology

The following table lists IBM® Lotus Enterprise Integrator® (LEI) terms and the corresponding terms used by the Lotus® Connector for Text.


LEI	Lotus® Connector for Text
Server	(Not applicable)
Database	File name
Metadata	Replacement substrings
Index	(Not applicable)
Field	Field, as defined in the information description (ZID) area
Record	Record, as defined by record delimiter or record length