Changes In Oracle Endeca Integrator with OEID 3.0

Integrator is a separate installation from the OEID Discovery install.  However it’s a simple installation and the tool itself is not very different.  There are a couple new components: “Delete Records” and “Modify Records”.  “Reset Data Store” was renamed “Reset Data Domain”.  “Add/Update Records” was renamed to “Merge Records”.

The Merge Records component now includes a property called “Disable Updates”, which will fail the process if any attempt is made to update an existing record in the data domain.

Any calls to the OES web services should update the version number from 1 to 2.  For example:

2.3:         xmlns:config-service=”http://www.endeca.com/MDEX/config/services/types/1/0”

3.0:         xmlns:config-service=”http://www.endeca.com/MDEX/config/services/types/2/0″

(or)

2.3:         http://www.endeca.com/MDEX/config/services/config/1

3.0:         http://www.endeca.com/MDEX/config/services/config/2

CAS is now IAS (Integrator Acquisition System), any CAS components will need their properties to be updated.  IAS identifies support for only Windows 2008.

Any existing components with references to Data Store Names in their properties will need to be updated to use the Data Domain Name.  There is also a property called “Endeca Server Context Root” that you’ll need to specify for quite a few OEID components.  The default value should be “endeca-server”

Default value of the IsSingleAssign property (mdex-property_IsSingleAssign) changed from false to true.  This should become part of your PDR settings.  None of the standard property defaults have changed.  Note however from 2.3 to 3.0 there is now a property for “mdex-property_Language” to define the charset for that attribute.

There are also some additional xml properties that can be defined on attributes with OEID 3.0:

  1. system-eid_isDimension
  2. system-eid_available_aggregations
  3. system-eid_default_aggregation
  4. system-eid_description
  5. system-eid_formatSettings

The GettingStarted project provides some templates for how these can be leveraged to set the attributes up for use in Studio.  They’re optional, but provide a nice way to ensure the data is ready for business users to work with.  Definitely recommend basing future projects on their structure.

There are no apparent changes to the data types that can be specified.

Advertisements
This entry was posted in Endeca and tagged , , , , , , , , . Bookmark the permalink.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s