• Section Widget

  • Recent Articles

    jsiwila

    Processing Records Rejected by a Read File Operator

    This is a companion article to Processing Rejected Records. That deals with records rejected by the Read Excel operator and applies to Read operators in other expressor Extensions and to the Read Custom operator.

    Parsing records rejected by the Read File operator is simpler than parsing records from Read Excel and related operators. The Read File operator retains the sequence of fields and attributes when it writes them to the RecordData field of the Reject Record Schema. Because of that, it is not necessary for the Read File operator to write header records to describe the field and attribute sequence. That greatly simplifies the datascript required to parse the RecordData field and reconstruct the rejected records.

    As explained in the Processing Rejected Records article, when a Read operator... read more
    jsiwila 05-14-2012, 03:33 PM
    jlifter

    expressor tutorials

    In this section you will find a collection of older tutorials that demonstrate the features of expressor Studio and the entire expressor Data Integration Platform. Though... read more
    jlifter 05-08-2012, 04:08 PM
    jsiwila

    Release Notes - expressor 3.6.0, 3.6.1, 3.6.2, 3.6.3, and 3.6.4

    expressor 3.6.4 fixes four bugs, three in Studio (STU-4728, STU-4730, and STU-4744) and one having to do with reading Informix databases from dataflows running on Linux (PRO-2634). See the resolved issues section below for a description of each of the fixed bugs.

    Also, see STU-4729in the known issues section below. STU-4729 describes an issue encountered when upgrading artifacts in a Repository Workspace.

    Note that the Informix ODBC drivers shipped with expressor software do not support Unicode on Linux.

    expressor 3.6.3 fixes three bug in Studio: one covering memory leaks, another dealing with binding to the Oracle NUMBER data type, and the third corrects unnecessary rounding when converting a double precision value to decimal. See STU-4641, STU-4625, and PRO-2622 under resolved issues below. Also see STU-4657 in the known issues section immediately following for a workaround to a problem dealing with NUMBER... read more
    jsiwila 05-08-2012, 09:02 AM
    jsiwila

    Processing Rejected Records

    When records produce errors because they violate constraints set on Composite Type
    attributes or other reasons, the operator that encounters the error can handle them
    by skipping them, aborting the dataflow, or rejecting the offending records. In some
    cases, it is sufficient to simply send rejected records to a Write File operator
    and examine the records in the output file. If the intent is, however, to correct
    or otherwise use those records, examining each error and changing the data could
    be very cumbersome. The more efficient approach would be to reprocess the records
    as they come out the reject port.

    Records rejected by input operators such as Read File, Read Table, and Read Excel are structured into the following fields:

    RejectType
    RecordNumber
    RecordData
    RejectReason
    RejectMessage

    The record data as it was constituted before being rejected is contained in the RecordData field. To process that data, it must first be reconstructed from the rejected record format. Several factors affect the reconstruction. The order of the record data fields can be different from the order represented in the original Schema, and some of the records emitted from the reject port do not contain record data. For example, RejectType 1 errors are constraint violations, but before they are emitted, a RejectType 4 record is emitted. The RejectType 4 record contains the record data field order for the subsequent RejectType 1 errors in its RecordData field. The RejectTypes are fully explained in the Using the Reject Port section of the Read Custom operator topic in the product documentation.

    Note: All non-input operators that have a reject port emit rejected records with the existing attributes of the record, that is, they do not restructure the records the way input operators do. Reprocessing records rejected by non-input operators do not have to be reconstructed
    ... read more
    jsiwila 05-07-2012, 10:00 AM

  • Install the expressor Standard Edition

    by
    jlifter
    Published on 07-20-2011 10:56 AM
    The expressor Standard Edition consists of three components:

    1. expressor Repository, the centralized version control system that enables team development and an easy mechanism to install expressor applications onto remote computer
    2. expressor Data Processing Engine, used to run completed applications from a command window or through integration with a scheduler application
    3. expressor Studio, the graphical environment in which applications are developed and tested

    For developers, the expressor Community Edition, which includes expressor Studio with a no term development license, is a suitable platform for learning and developing and running applications. expressor Studio deployed as the Community Edition may be integrated into a Standard Edition deployment through a no cost licensing procedure once Standard Edition has been purchased.
    When you run the expressor Standard Edition installer you have multiple options:

    • You could install one component: the engine, the repository, or Studio.
    • You could install multiple components: the engine and repository, or Studio and repository.

    After installation, you must obtain a license key for the engine or repository before these components may be used.
    The Standard Edition installer is a typical wizard driven Windows process.

    1. Download the installer .exe from the expressor software Web site.
    2. As the installer runs, it checks your computer for the required prerequisites and, if necessary, downloads and installs these prerequisites.
    3. Next the installer download and runs the .msi executable, which performs the actual expressor installation.
    4. After accepting the license agreement, the Custom Setup window will open. Use this window to select the components you wish to install.
    5. To install just the repository:
      Expand the drop down menu adjacent to the expressor Engine listing and select the option that prevents installation of this component.

      Neither the engine nor Studio will be installed.
      In the next window, enter the credentials for an account with the authority to use the repository. You will need to provide these credentials in order to connect to the repository from Studio. Additional accounts may be added; see the product documentation.

      You may also change the directory in which the repository’s data will be stored.
    6. To install the engine and repository, expand the drop down menu adjacent to the expressor Studio listing and select the option that prevents installation of this component.

    7. And to install just the engine, disable installation of both Studio and repository.

    If you need to completely remove all expressor 3 components from the computer, use the standard uninstall functional of the Control Panel. To remove one component while leaving another, rerun the installer and select the Modify option from the Program Maintenance window.
Follow us
 
copyright  |  privacy  |  contact  |  terms of use  |  sitemap
 
Style & Customization by Boston Web Developer
Gravatar as Default Avatar by 1e2.it

SEO by vBSEO 3.6.0