1 Release Notes

This document contains the Oracle Enterprise Data Quality for Product Data Endeca Connector Release Notes for various releases of the product.

Endeca Connector Changes from 11g (11.1.1.6.0) to 11g (11.1.1.6.1)

• Added an example project to illustrate how the Endeca Connector can be implemented.

Endeca Connector Changes from 5.6 to 11g (11.1.1.6)

• Rebranded the application from DL Foundry to PDQ-Endeca Connector.

• Changed the prefix of all pass throughs from SCS to PDQ.

• Changed the package structure of the Java Manipulator Adapter and the Discovery Classes. This is only visible when you are configuring the Java Manipulator in the Endeca Developers Studio.

• Merged the two library files, edqp-addin.jar and edqp-adapter.jar into a single file for both PDQ discovery and the run-time adapter, opdq-connector-endeca.jar.

• Added a new run-time library for the adapter named opdq-core.jar.

DL Foundry Changes from 5.5.03.02 to 5.6

• The following pass thru parameters have been removed:

  CLIENT_CODE and HA_LB_ENABLED (in SilvercreekAdapter)

  CHECK_VERSION (in Discovery add-ins)

• The version and copyright information has been updated.

• Updated the Windows installation process.

• Changed default for VersionEndecaFiles from true to false (for new core-step add-ins).

• Build Version 5.6.02 -Added the ability to rename Dimensions.xml and pipeline.epx in the add-in parameters,

• Build Version 5.6.03 - Ignore scs_props.xml if the project is not discovering properties.

DL Foundry Changes from 5.5 to 5.5.03.02

• The description of the Attributes. in the AddInTransformParameters configuration file, is updated.

• Verification to avoid adding conflicting precedence rules is introduced. This ensures that you cannot add a child that is already a parent.

  It allows multiple levels of precedence rules to be created entirely within the data lens and fixes the problem where manually created precedence rules could break the DL Foundry-created precedence rules.

• Support for the Dimension advanced option Multi Select is introduced.

• The case of the Pipeline.epx file and the Dimensions.xml file to match the lower-case used in Linux is corrected.

• Converted the Dimension Ids from int data type to long to match the Endeca data type for Dimensions.

• Modified the way versioning operates by creating a versioning transform step, rather than separately versioning during each step of the discovery/delete add-in processing.

• The Endeca Developers Studio is removed from the project paths.

• Code was refactored for Oracle (the Java packages and renaming classes were restructured).

• Removed the installation procedure on Windows.

DL Foundry Changes from 5.1 to 5.5

The following are enhancements for increased robustness, failover, reliability and round-robin server support.

• The Host and Port Adapter pass thru parameters have been replaced with the _SERVER_1 required and the _SERVER_2, and _SERVER_3 optional parameters.

  • This adds support for multiple Oracle DataLens Servers to be pinged (a DataLens servlet ping) in a round-robin fashion to determine which server to run the Add-In jobs and the Adapter jobs.

• DL Foundry SilvercreekAdapter now retries the current chunk if the Oracle DataLens Server fails during Forge processing so that the Forge job will not fail.

  • Using the same server parameters as the round-robin code for Oracle DataLens Servers, the SilvercreekAdapter will catch if a Forge chunk (DSA job) fails during job submittal (sending the data to the server) or during job results retrieval and retry the chunk of data on another Oracle DataLens Server if there is a problem.

  • The SilvercreekAdapter fail-over happens (and the data chunk is resubmitted) when one of the following occurs:

    • Connection Exception

    • Out Of Memory error

    • DSA job Fault

• Changed the project versioning to have a separate XFM Add-In that is added to the start of a DL Foundry discovery job. The individual versioning flags for the separate Add-Ins are no longer supported.

DL Foundry Changes from 5.0.2 to 5.1

• DL Foundry Adapter - The pass thru, DSA_OUTPUT_STEP, is introduced. It names the output step if there are more than one output steps in a DSA Map (for instance routing exceptions).

• DL Foundry Add-In - Optional support for Endeca external dimensions file is added as follows:

  • SCS-generated Dimensions will not conflict with dimensions in this file. The following parameter in the Endeca.DiscoverDimensions Add-In is introduced:

    Endeca.ExternalDimensionsFile

  • SCS-generated Precedence rules can use the Dimension names in the external file as a source when creating new precedence rules. The following parameter in the Endeca.DiscoverPrecedence Add-In is introduced:

    Endeca.ExternalDimensionsFile

• DL Foundry Add-In - Optional support for generating precedence rules on a data lens by data lens basis is added as follows:

  • The following parameters in the Endeca.DiscoverPrecedence Add-Ins are introduced:

    SCS.ServerName

    SCS.ServerPort

    SCS.DataLens

    SCS.Standardization

• DL Foundry Add-In - Optional support for precedence rule generation for Dimensions not generated by the DL Foundry if they are in the list of attributes for the specific data lens is added.

  SCS.GenerateRulesForAllAttributes

• DL Foundry Add-In - The Endeca.CleanupDimensions TMap Add-In Transform is introduced. It is added to the end of DSA maps performing the DL Foundry discovery to clean up the cached data that is shared by all the Endeca Add-Ins with information on the dimensions from the Endeca Developer Studio project.

• The REPLACE_UNDERSCORES_ONLY parameter is introduced to support respecting the case of attribute aliases, while still replacing underscores with spaces. This is a required pass thru parameter for the DL Foundry Adapter.

• The USE__PREFIX parameter is introduced to toggle off the use of the ”.” prefix in the Prop/Dim mapping table in Endeca. This is a required pass thru parameter for the DL Foundry Adapter.

• Five Add-In Transform parameters (including SCS.ServerName, SCS.ServerPort, SCS.DSAMap) have been consolidated in the SilvercreekAdapter pass thru parameters where they are shared, simplifying configuration.

DL Foundry Changes from 5.0 to 5.0.2

This version of DL Foundry only supports Oracle Product Data Quality 5.0.2 because it uses TMap Add-In parameters introduced in the 5.0.2 release.

• Any DL Foundry discovery process will throw an exception if an error is encountered and the job will terminate. This makes it very easy for you to check the status of these jobs without needing to examine the log files.

  In the 5.0 release, errors in any of the DL Foundry discovery processes were written to the Log file, but the Job would complete successfully.

• The DL Foundry discovery processes are now completely integrated with the TMap Add-In Transformations.

  Support for the DL Foundry DSA Add-In Outputters is discontinued.

• The DL Foundry configuration files are now stored only on the Oracle DataLens Administration Server in the Data Repository. These files are stored in C:\SilverCreek\Server\data\shared\common\config (formerly in C:\Program Files\Apache Software Foundation\Tomcat 5.5\webapps\silvercreek\config). This is a general 5.0.2 server change to the way all Add-In functions are used on the server.

  The configuration file has changed from AddInOutputParameters.xml to AddInTransformParameters.xml.

• The DL Foundry library has changed from Custom.jar to Addin.jar.

  The requirement to move the DTD files into the XML pipeline directory has been removed.

• The following parameters have been removed from the Dimension Delete, Property Delete, Precedent Discover, and Precedent Delete:

  • Server Name

  • Server Port

  • DSA name

  • DL Standardization