In order to bring you the best possible user experience, this site uses Javascript. If you are seeing this message, it is likely that the Javascript option in your browser is disabled. For optimal viewing of this site, please ensure that Javascript is enabled for your browser.
Login  |   Cloud ERP  |   Home  |   qad.com



  •     QAD Glossary

  • QAD QXtend 1.8.4
    QXtend Inbound
    QXI Server Version: 1.8.4
    Date: September 2013
    QAD Enterprise Applications Compatibility: eB SP4 through current release
    Supported Progress Releases: Progress 9.1E, OpenEdge 10.0B, 10.1A, 10.1B, 10.1C, 10.2A, 10.2B, 11.1, 11.2
    Supported Java Version: Java 1.6 or higher
    QAD QXtend Documentation: User Guide: QAD QXtend (70-3190-1.8.4) and Installation Guide: QAD QXtend (78-0952-1.8.4)
    New and Changed Features
    1
    Configuration Data Transfer Enhancements
    Transferring QXI receiver APIs is supported in this release.
    Configuration data can be imported into a target system with different configuration names (for example, receiver name) by using a mapping file.
    Wildcard matching is enhanced to support multiple patterns.
    The template of the descriptor file can be generated for export.
    A report in text format is generated after a successful export/import. The report shows the detailed process results and warning messages.
    When running configuration bundle scripts, the system first checks whether the JAVA_HOME is set correctly.
    2
    Network Security Enhancements
    UIAPI connection pools support SSH connection using public/private key pairs.
    SIAPI and FinAPI connection pools support connection to SSL-enabled AppServers.
    QXtend installer is enhanced to support SSH connection with public/private key pairs for UIAPI Connection Pool.
    3
    A new method is available for developers to use QDoc SAX Writer to create a QDoc with session ID credentials.
    4
    More QDocs are available, including more than 150 easy on boarding QDocs for QAD SE and QAD EE and 21 new CRM APIs.
    5
    A new session context parameter decimalSeparator is available. QXtend replaces the decimal separators in decimal string values with dots (.) before processing the QDoc. It is used for QDocs that have decimal values that do not use a dot as the decimal separator; for example, in European number format.
    Fixes
     
    Fix Description
    Internal ID
    Issue Affected Versions
    If dbman is used and the adminserver is not using the default port, the QXtend Installer can now install and start QXODB correctly.
    QXT-1512
    1.7.2+
    Configuration bundle scripts now check the action type and bundle ID specified in the descriptor file before further processing.
    QXT-1485
    1.8.3
    In this release, users do not need to manually add stty -icanon and stty ixoff to the connection scripts or the QXI server startup scripts. The system adds them automatically.
    QXT-1479
    1.7+
    Excelerator running on Windows system with language setting that does not use a dot as the decimal separator can now work with QXtend correctly. The fix works together with Excelerator 1.3 or higher versions.
    QXT-1475
    1.7+
    Previously, QXtend 1.8.3 installer failed to compile QXtend Adapter against QAD 2013 SE. Now this issue has been fixed.
    QXT-1465
    1.8.3
    Previously, during QXtend upgrade, Migrate Queue Configuration step reported an error when there was no queue defined. Now this issue has been fixed.
    QXT-1464
    1.8.3
    Configuration bundle scripts can now run normally when the paths include spaces.
    QXT-1459
    1.8.3
    The issues about the QDocs enterCycleCountResults and maintainUsers have been fixed for Excelerator use.
    QXT-1431
    QXT-1487
    1.7+
    Previously, when a qdocSummary.log file was created for a new day, the header was missing. In this release, the header is displayed correctly.
    QXT-1421
    1.8+
    Start-timestamps and Finish-timestamps in qdocInfo.log are now consistent with the timestamps in other logs. Previously, the same start-timestamp could differ slightly in different logs.
    QXT-1420
    1.7+
    When QXtend installer is deploying QXI/QXO servlet, it no longer checks Progress DLC so that it does not produce any issue when Tomcat is not on the same server as Progress.
    QXT-1413
    1.8.3
    Inbound can now show the correct error message when the receiver name is not correct in a QDoc.
    QXT-1379
    1.8.3
    The misleading field “Database Language” in the installer has been changed to a boolean field called “Database UTF.”
    QXT-1378
    1.7+
    QXtend can now return QDoc response when character “^” is in data values in the response. Previously, this character caused ArrayIndexOutOfBoundsException.
    QXT-1376
    1.7+
    When QXtend is installed through QDT, Connection Method (SSH/Telnet) and Connection Port can now be configured correctly for UIAPI.
    QXT-1363
    1.8.3
    When installing QXtend 1.8.3 against QAD EE versions before 2011 EE, the adapter compile reported errors. This issue has been fixed.
    QXT-1360
    1.8.3
    The configuration bundle files can now be imported into Inbound or Outbound running on Windows servers.
    QXT-1354
    1.8.3
    QXtend Outbound
    QXO Server Version: 1.8.4
    Date: September 2013
    QAD Enterprise Applications Compatibility: eB SP4 through current release
    Supported Progress Releases: OpenEdge 10.2B, 11.1, 11.2
    Supported Java Version: Java 1.6 or higher
    QAD QXtend Documentation: User Guide: QAD QXtend (70-3190-1.8.4) and Installation Guide: QAD QXtend (78-0952-1.8.4)
    New and Changed Features
    1
    Configuration Data Transfer
    More configuration components are supported in this release. They are:
    QXO BO registrations with message publishers
    QXO subscriber profiles
    QXO source application event type
    Configuration data can be imported into a target system with different configuration names (for example, source application name, message publisher name, or subscriber name) by using a mapping file.
    Wildcard matching is enhanced to support multiple patterns.
    The template of the descriptor file can be generated for export.
    A report in text format is generated after a successful export/import. The report shows the detailed process results and warning messages.
    When running configuration bundle scripts, the system first checks whether the JAVA_HOME is set correctly.
    2
    Message archiving is enhanced to free more qxodb database space.
    Fixes
     
    Fix Description
    Internal ID
    Issue Affected Versions
    Previously, special characters were allowed in the BO names and the profile names, but they may cause issues in data publish, export/import, or query deployment. Now, only alphanumeric characters, dash, and underscore are allowed in BO names and profile names. The BOs and profiles having other special characters in the names cannot be saved.
    QXT-1547
    1.7+
    The subscriber message resend issue has been fixed and a message in PEND status cannot be resent.
    QXT-1455
    1.7+
    The BO creation issue in QXtend 1.8.3 has been fixed.
    QXT-1430
    1.8.3
    “Logical Name” is corrected to “ID Name” on the Databases page of Source Application Configuration.
    QXT-1429
    1.8.1+
    Resending subscriber message now works as expected when there are multiple subscriber profiles. The system resends the subscriber message to only the subscribers it belongs to.
    QXT-1428
    1.7+
    The issue that domain could not be added to source application configuration in QXtend 1.8.3 has been fixed.
    QXT-1427
    1.8.3
    In Outbound validate configuration, the logic to check whether QXO is enabled in the source application now runs correctly for early MFG/PRO versions that do not have domains.
    QXT-1381
    1.7+
    Event Service now allows an event to be processed up to ten minutes without showing a DEAD status.
    QXT-1380
    1.7+
    The subscriber message for the “Delete” operation can now be sent out when the subscriber profile listens to the operation. Previously, it was not sent out when the subscriber profile listened to “Delete” and did not listen to “Modify.”
    QXT-1340
    1.8+
    The Archive service can now process all the raw messages and the subscriber messages that meet the criteria.
    QXT-834
    1.7+
    Known Issue
    QXtend 1.8.4 has not passed the certification test against Oracle database with OE 11.1 and 11.2 because of issues with OpenEdge. Contact QAD Support for details.