Version 4.2  |   Version 4.1.1  |   Version 4.1  |   Version 4.0.3  |   Version 4.0.2  |   Version 4.0.1  |   Version 4.0  |   Version 2.6  |   Version 2.1  |   Version 2.0  |  


Connector for Oracle 4.2

Release Notes: July 2017

What are the new features of this release?

  • Added support for non-clustered Microsoft Windows Server 2016.
  • Added the ability for the Connector Console to automatically update when printer lists are modified on any
  • configured Loftware Print Servers.
  • Added the ability to treat non-group values for the _FORMAT attribute as labels.
  • Added the ability to test with large XML files.
  • Added the ability to register a listener without a filter.
  • Added additional feedback when errors are encountered while running “Discover All LPS Servers”.
  • JRE 1.8 is now packaged with Loftware Connector Products, which results in providing separate installation
  • packages for 32 and 64-bit Operating Systems.

What are the new features of this release?

  • Corrected issues with Repair functionality incorrectly reporting on status of XDK java classes and failing to install the Console service
  • Corrected a defect that prevented labels with fixed text fields only from printing via the Connector
  • Corrected issues running service.bat if both JAVA_HOME and JRE_HOME are set
  • Method type of “literal” is now disallowed when configuring a Default Data Lookup filter
  • Corrected an error with Format Substitution not working after a Default Data Lookup in a filter chain
  • We no longer automatically remove an existing INV_SYNC_PRINT_REQUEST during install
  • Corrected issues with a failed import rendering the Connector useless
  • Corrected a loadjava call by surrounding the JDBC_URL with double quotes

Connector for Oracle 4.1

Release Notes: December 2014

Note: The Loftware Universal Connector version 4.1 requires the Loftware Print Server Premier Edition version 10.0.1 or higher.

What are the new features of this release?

  • Added support for non-clustered Windows Server 2012 R2
  • Added the ability to Import and Export Business Rules and configuration to the local client. This allows for easy migration between different Connector instances
  • Enhanced flexibility for Business Rules that allows labels to be printed unless a certain condition occurs (“Execute Unless”). This expands the existing “Execute When” logic, which allows a label to be printed when specified conditions are met
  • Added the ability to fail a print job on a database error
  • Added Network Proxy Support for load balanced environments
  • Improved JDBC Driver Handling, providing easy connectivity to additional external data sources
  • Support for Oracle 12c and Java 1.8
  • Changed “Filter” terminology to “Rules”

What fixes are available in this release?

  • Improved Business Rules load times
  • Fixed issue where the Connector was holding onto an invalid socket connection
  • Additional error handling and logging improvements

What issues are known about this release?

  • LPS commands within incoming XML files must be in all UPPERCASE.
  • Label Groups cannot be deleted if they are currently associated with a Rule Chain or another label.
  • Loftware recommends you disable console persistence across restarts.
  • When triggering a filter that queries either an SQL Server 2005 or 2008 R2 database, an AccessControlException is thrown, indicating that "...listen, resolve permissions have not been granted to user LOFTWARE". This can occur when a JDBC URL string has a named instance, and the optional port address is left off. To fix this issue, either fully qualify the connection with the port information, or remove the named instance.

Connector for Oracle 4.1.1

Release Notes: October 2016

Note: The purpose of this release is to provide an update about a change in behavior introduced in the Loftware Connector for Oracle version 4.1.

What issues are known about this release?

Data Lookup filters that use the Extended Rule Connection URL from the Settings page will fail after upgrading to the Loftware Connector for Oracle version 4.1. Before or after upgrading, you must remove the Extended Rule Connection URL from the Connector Console Settings page, and add it to the Data Source URL in each of your filters.

Connector for Oracle 4.1

Release Notes: December 2014

Note: The Loftware Universal Connector version 4.1 requires the Loftware Print Server Premier Edition version 10.0.1 or higher.

What are the new features of this release?

  • Added support for non-clustered Windows Server 2012 R2
  • Added the ability to Import and Export Business Rules and configuration to the local client. This allows for easy migration between different Connector instances
  • Enhanced flexibility for Business Rules that allows labels to be printed unless a certain condition occurs (“Execute Unless”). This expands the existing “Execute When” logic, which allows a label to be printed when specified conditions are met
  • Added the ability to fail a print job on a database error
  • Added Network Proxy Support for load balanced environments
  • Improved JDBC Driver Handling, providing easy connectivity to additional external data sources
  • Support for Oracle 12c and Java 1.8
  • Changed “Filter” terminology to “Rules”

What fixes are available in this release?

  • Improved Business Rules load times
  • Fixed issue where the Connector was holding onto an invalid socket connection
  • Additional error handling and logging improvements

What issues are known about this release?

  • LPS commands within incoming XML files must be in all UPPERCASE.
  • Label Groups cannot be deleted if they are currently associated with a Rule Chain or another label.
  • Loftware recommends you disable console persistence across restarts.
  • When triggering a filter that queries either an SQL Server 2005 or 2008 R2 database, an AccessControlException is thrown, indicating that "...listen, resolve permissions have not been granted to user LOFTWARE". This can occur when a JDBC URL string has a named instance, and the optional port address is left off. To fix this issue, either fully qualify the connection with the port information, or remove the named instance.

Connector for Oracle Version 4.0.3

Release Notes: December 2013

Note: The Loftware Universal Connector version 4.0.3 requires the Loftware Print Server Premier Edition version 10.0.1 or higher.

What are the new features of this release?

  • Support for IE versions 9, 10, and 11.
  • Support for Non-Clustered Windows Server 2012
  • Support for Windows 8
  • Support for customizable "Job Listener" to identify and intercept specific print jobs that have been processed through a filter, before they are allowed to continue to LPS for printing.

What fixes are available in this release?

  • Java Connector API has been updated to accept a label name in any upper or lower case.
  • XML parser has been updated to not require a CR at the end of jobs in stacked XML files.

What issues are known about this release?

  • High volumes of jobs across a large number of scan folders can result in jobs being stacked in the Processing folder.
  • LPS commands within incoming XML files must be in all UPPERCASE.
  • Label Groups cannot be deleted if they are currently associated with a Filter Chain or another label.
  • Loftware recommends you disable console persistence across restarts.

Connector for Oracle 4.0.2

Release Notes: February 2012

Note: The Loftware Connector for Oracle 4.0 requires Loftware Printer Server Premier Edition version 10.0.

What fixes are available in this release?

  • With Oracle 8 and above, when you change the filters from “Legacy” to “New” the memory state inside the database JVM is maintained as “legacy.” LPS now correctly handles the “New” business rules in the Oracle instance.
  • When an Instance Expansion filter executes in a Filter Chain, during group expansion the connector communicates with LPS to determine if the label exists. When Connector 4.0 is executing Filter Chains, the Connector is not appending the LPS_PRINTER_TYPE (if in use) to the label when communicating with LPS. LPS checks the root labels directory and if the label does not exist LPS will report an error back to Connector.


Connector for Oracle 4.0.1

Release Notes: December 2011

What fixes are available in this release?

  • In version 3.0.2.1 of the Loftware Connector for Oracle, installation errors were logged in the lwloadjava.log. This logging has been restored in this release.
  • Instance Expansion Rules are now functioning correctly and are providing error messages. Job XML assembly now reacts properly with legacy parsers used by the Oracle Connector.
  • Verbose Logging trace files are now operational. The trace files are now in the following location: <install_dir>\<user>\rdbms\<sid>\<sid>\trace.

Connector for Oracle 4.0

Release Notes: November 2011

Note: The Loftware Connector for Oracle 4.0 requires Loftware Printer Server Premier Edition version 10.0.

What are the new features of this release?

  • Updated the look and feel of the Connector Console user interface.
  • Added support for Windows Server 2008 and Server 2008 R2.
  • Added the ability to import and export Loftware Oracle Connector configuration information to an XML file.
  • Added support for JDBC compliant databases.
  • Added the ability to turn on or off individual filters without deleting them from the Filter Manager in the console.
  • Add Save As Capability to Connector Filters.
  • Allow Filter triggers in the console to be based on incoming xml data.
  • Added ability to turn off XSLT transforms using the SkipXSLTransforms property in the LPSConnector.property file.
  • The XML created by the Connector Instance Expansion filter can be modified so that labels can be sent to multiple printers.
  • Improved error handling and logging in the Connector Console for Oracle.
  • Allow over-writing data values on Print Attribute Substitution.

What fixes are available in this release?

  • The Default Servers check box on the LPS Servers page now remains selected when Show/Hide Printers is selected.
  • Print Attribute Substitution Filter is able to modify the literal _QUANTITY if _QUANTITY exists and a value has been assigned.
  • You can now delete an LPS Server in the Loftware Oracle Connector if the LPS server cannot be reached by the server name.
  • Replace forward slashes (/) in printer model names to a space.
  • When in the Modify Filter view, clicking the browser Back button no longer produces an error.
  • Settings in the Connector Console do not update to the File Drop Service until the service restarts.
  • LPSTemplate.setData(string,string) now truncates data if the data string being passed is too long.

Connector for Oracle 2.6

Release Notes: April 2006

Enhanced Console Interface:

  • Filter and label group definitions allow for notes/comments to be added and modified.
  • Filters can be given more descriptive names/aliases. These names appear in configured filter list for easy filter identification.
  • Lists can be sorted on selected columns for filters, labels, and printers.
  • Label groups are now defined from the Manage Labels section, along with labels and label types.
  • Text box sizes have been increased to make more field data viewable.

Java Version 5 Support:  The Connector and the Console can now operate in Java SDK Version 5 environment.


Connector for Oracle 2.1

Release Notes: September 2004

Internal Engine reengineered for a five fold increase in performance when processing large XML request files. Refined and improved install, admin tools, documentation, and utilities.


Connector for Oracle 2.0

Release Notes: 2003

The latest version of the Loftware Connector is designed to run with Loftware Print Server Enterprise Edition. Much like Version 1.0, Loftware Connector Version 2.0 is a high-capacity program that offers tremendous speed and reliability. The Connector is a connectivity module that bridges Loftware's Enterprise bar code printing technology and the Loftware Print Server to applications such as Oracle©. The Connector v2.0 also features a new smart filtering capability, eliminating the need for complicated and costly programming tasks that are sometimes required to meet specialized label printing needs, quickly allowing application developers and integrators to connect Oracle applications and systems to corporate back-end bar code label printing systems. Users administrating Oracle applications find that The Loftware Connector has a familiar interface, is easy to use, and eliminates the need for unreliable data transfer and connection methods. The Loftware Connector is a fully tested and highly maintained solution. The Loftware Enterprise Print Server allows for Loftware Connector v2.0 integration capabilities. Please note that the Loftware Connector is sold separately from the Loftware Print Server.