[/map {"- map/map "}) [/map/title {"- topic/title "}) Configuring (title] [/map/topicref {"- map/topicref "}) [/map/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuring the IKM SQL to Endeca Server (navtitle][/map/topicref/topicmeta/linktext {"- map/linktext "}) Configuring the IKM SQL to Endeca Server (linktext][/map/topicref/topicmeta/shortdesc {"- map/shortdesc "}) The following procedures describe how to configure and run the IKM SQL to Endeca Server in ODI.次の手順を順番どおりに実行してください。After you complete the procedures, you can run an ODI Interface that integrates data into an Endeca Server. (shortdesc] (topicmeta][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Importing the Endeca Server technology into ODI (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Importing the Endeca Server technology into ODI (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You use ODI Studio to import the Endeca Server technology into ODI. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Adding flexfield definitions (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Adding flexfield definitions (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) You must add flexfield definitions to ODI to define Endeca Server fields.As a convenience, the IKM SQL to Endeca Server provides a command line utility, named metadata-import, to create the flexfields into ODI.The metadata-import utility requires a few configuration settings for SDK, Java, and driver locations. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating an Endeca Server data server (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating an Endeca Server data server (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Next, you create an Endeca Server data server. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating a physical schema (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating a physical schema (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you have created an Endeca Server technology, you create a physical schema to associate with it. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating a logical schema (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating a logical schema (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) After you have created an Endeca Server, you create a logical schema to associate with it. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating a model (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating a model (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Next, you create a model. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating a datastore (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating a datastore (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Next, you create a datastore. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Modifying column settings in a datastore (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Modifying column settings in a datastore (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Once you have created a datastore and its columns, you can assign Endeca properties to each column in the datastore.Endecaフレックスフィールド・プロパティによって、各列値にEndeca検索設定が構成されます。たとえば、Endecaプロパティによって、列の値がテキスト検索可能か、値検索可能か、単一割当てか、複数割当てかなどが定義されます。The definition of each Endeca property is documented in the "Property Description Record (PDR)" topic of the Oracle Endeca Server Developer's Guide. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Importing the knowledge module (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Importing the knowledge module (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) In this procedure, you import the knowledge module contained in the <install path>\ikm_sql_to_endeca_server\3.1.0\ikm directory.This module is project dependent and cannot be imported until you first create and configure a project. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Creating an interface (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Creating an interface (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) Next, you create an interface. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Configuration reference for the IKM SQL to Endeca Server (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Configuration reference for the IKM SQL to Endeca Server (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) When you open the Target component for the IKM SQL to Endeca Server, you find configuration options in the Options area of the Target Area - Property Inspector dialog.These options are described below. (shortdesc] (topicmeta] (topicref][/map/topicref/topicref {"- map/topicref "}) [/map/topicref/topicref/topicmeta {"- map/topicmeta "}) [/map/topicref/topicref/topicmeta/navtitle {"- topic/navtitle "}) Mapping source data types to Endeca Server data types (navtitle][/map/topicref/topicref/topicmeta/linktext {"- map/linktext "}) Mapping source data types to Endeca Server data types (linktext][/map/topicref/topicref/topicmeta/shortdesc {"- map/shortdesc "}) When the knowledge module writes source data to an Endeca Server target, it is possible to encounter errors if data types do not map correctly between the database source and the Endeca Server target. (shortdesc] (topicmeta] (topicref] (topicref] (map]