Skip to main content
Omnitracs Knowledge Base

Integration Toolkit Release Notes (v2.0)

What's New for v2.0?

In Brief 

The operation, functionality, interfaces and components of the Integration Toolkit remain largely unchanged in this latest version . Those familiar with earlier versions of the toolkit will easily adapt to version 2.0. The main changes for version 2.0 are centered on formalizing the Integration Toolkit as a versioned, distributable software product.

The following sections describe specific areas where the product was enhanced.

Product Consolidation

  • A consolidated toolkit source code base was created, incorporating changes from the field, and is now versioned and buildable via source code management system.
  • The single toolkit source code base supports build targets for i5/OS v5r4 through v6r1.
  • The toolkit incorporates a single set of the latest IBM CTC components, which are designed to support i5/OS v5r4 through v6r1. 
  • Bug reports, changes requests, and field modifications to non-customizable (non-stub) components will follow standard practices currently in place for customer-hosted iSeries Omni products (ie. QTRACS/400, etc).

Distribution and Installation

  • Toolkit distributions (CDs) for supported i5/OS targets may be requested on behalf of the customer via the standard SAE product request form
  • Automated, menu-driven installation is now supported via the Application Software Distribution Utility (ASDU).
  • An automated upgrade path from the non-versioned instances of the toolkit currently in the field to v2.0 is not supported. Earlier versions of the Integration Toolkit must be upgraded to v2.0 through a series of manual and automated upgrade steps.

Product Enhancements 

  • Online, wiki-based documentation has been throughly re-worked and updated for Integration Toolkit v2.0
  • The product has been extensively unit, integration and installation tested for i5/OS targets v5r4 through v6r1
  • Technical enhancements include:
    • Exportable TSTRANDS ESS data structure copy member replaces IITRANDS as IITRAN table overlay structures for subset of supported ESS transaction types
    • New hub utility to export customer macro template definitions and ESS static data tables and structures (TSTRANDS) for customer/Portal synchronization
    • Replacement of obsolete IBM XT1 XML parser with custom XML parser for converting ESS XML transactions to fixed format equivalents (IICVTXML)
    • Incorporation of field-developed (IIUTILS) enhancements supporting memory-based response buffer processing and ASCII compatible string operations
    • Support for field-developed trailer web service wrappers:









  • Was this article helpful?