Home
HCL Domino Designer User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
Connectors
Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
Connectors and Connectivity Guide
Chapter 11 Connector for Text
This chapter provides information about the Connector for Text, including descriptions of the fields in the connection document.
Supported characteristics of the Connector for text
The following list captures supported characteristics of the Connector for Text.

HCL Domino Designer User Guide and Reference
This guide provides information on using HCL Domino Designer and programming language reference information.
- What's new in Domino Designer 14.5?
  The following features are new for developers in HCL Domino® Designer 14.5.
- What's new in Nomad Designer?
  HCL Nomad for web browsers v1.0.10 introduces the capability to design Notes databases. For more information, see HCL Nomad for web browsers User Documentation, Nomad web Designer.
- 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.
- Application Design
  Welcome to the Application Design section of Domino® Designer Help.
- Application Management
  Welcome to the Application Management section of Domino® Designer Help.
- Domino® Query Language
  Domino® Query Language (DQL) is a facility running on a Domino server that provides a terse, shorthand syntax for finding documents. It supports a wide variety and complexity of search terms. It leverages existing design elements, avoiding the need to write detailed code to access them. DQL consolidates all methods in Domino for searching document contents.
- 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.
- Connectors
  Connectors provide native access to a wide variety of DBMS products, ODBC, the platform File system, Enterprise Resource Planning systems, and Transaction Processing systems.
  - 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 Connectors
      This chapter provides introductory information about each of the supplied HCL Connectors.
    - Chapter 4 Connector for Notes®
      This chapter provides information about the Connector for Notes®, including descriptions of the fields in the connection document.
    - Chapter 5 Connector for DB2®
      This chapter provides information about the Connector for DB2®, including descriptions of the fields in the connection document.
    - Chapter 6 Connector for File System
      This chapter provides information about the Connector for File System, including descriptions of the fields in the connection document.
    - Chapter 7 Connector for ODBC
      This chapter provides information about the Connector for ODBC, including descriptions of the fields in the connection document.
    - Chapter 8 Connector for Oracle
      This chapter provides information about the Connector for Oracle, including descriptions of the fields in the connection document.
    - Chapter 9 Connector for OLE DB
      This chapter provides information about the Connector for OLE DB, including descriptions of the fields in the connection document.
    - Chapter 10 Connector for Sybase
      This chapter provides information about the Connector for Sybase, including descriptions of the fields in the connection document.
    - Chapter 11 Connector for Text
      This chapter provides information about the Connector for Text, including descriptions of the fields in the connection document.
      - Introduction to the Connector for Text
        This chapter provides information about the Connector for Text. The Connector for Text can be used with HCL Enterprise Integrator (HEI) for Domino® (HEI), and Connector LotusScript® Extensions (LC LSX).
      - Connector for Text terminology
        The following table lists HCL Enterprise Integrator (HEI) terms and the corresponding terms used by the Connector for Text.
      - Supported characteristics of the Connector for text
        The following list captures supported characteristics of the 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 HEI
        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 HEI Connection Document - 6
        This section describes the connection document fields.
      - Connector for Text Data Types
        The following tables show the correspondences of Connector for Text data types to HCL Enterprise Integrator (HEI) data types for various types of activity.
    - Chapter 12 Metaconnectors for HEI
      This chapter provides an introduction to HEI Metaconnectors and contains information for creating and using the different types of Metaconnectors.
  - LSX for Connectors
    LotusScript® Extensions for Connectors (LC LSX) enhances the power of Notes® by extending its scripting to data outside of Notes through the use of 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
    Developers are advised not to use LS:DO. Developers should use the 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.

Supported characteristics of the Connector for text

The following list captures supported characteristics of the Connector for Text.

For a definition of the terms used in this section, see "Supported Connector Characteristics -- List of Terms" in Chapter 3 of this manual. If you are accessing the Connector using LotusScript®, see the Connector LotusScript® Extensions Guide for more information.

Writeback support -- N/A
Writeback index -- N/A
Statement syntax -- N/A -- use ZID file instead
Condition syntax -- N/A
Array transfer -- None
Actions supported -- Clear, Reset, Truncate
Catalog types -- None
Create types -- None
Drop types -- None

All connections have a set of properties with values that can be assigned and retrieved. See the Connector LotusScript® Extensions Guide for a list of supported properties for each Connector. Also see the "Common Connector Properties" and "LCConnection Properties" sections in the LCConnection Class chapter of that same manual.

When using long file names, include the file name as is (with any embedded spaces). Do not put quotation marks around the file name, since the quotation marks will be considered part of the file name.