【文章內(nèi)容簡介】 d Port 屬性設(shè)置 ：Remote System：選擇遠(yuǎn)程系統(tǒng)Map: 選擇在 Syndicator 中定義的 MapProcessing Type: 選擇自動還是手動。Processing Interval：僅僅 Processing Type 設(shè)置為 Automatic 時(shí)設(shè)置此參數(shù)。這個(gè)參數(shù)是指自動處理的間隔時(shí)間，可以理解為后臺作業(yè)多久執(zhí)行一次。Xml Schemas 管理 管理 Repostiory 需要用到的 xml Schema 文件。Xml Schema 是指Repository 與遠(yuǎn)程系統(tǒng)進(jìn)行數(shù)據(jù)交換的格式文件。schema 文件從客戶端上傳，保存在 MDM 服務(wù)器中。在 port 管理時(shí)需要用到 xml schmeas 文件。 Repository 其它操作Repository 可以進(jìn)行驗(yàn)證，驗(yàn)證包含檢查和修復(fù)二個(gè)功能。 操作如圖所示: 當(dāng) Repository 無法 Loading 的時(shí)候可以通過 Verify Repository 來查看和檢 江蘇省電力公司信息化登高項(xiàng)目 MDM 培訓(xùn)手冊第 32 頁 共 85 頁查 Repository 是否包含錯(cuò)誤。通過 Check 可以查看錯(cuò)誤，追蹤問題并解決。某些錯(cuò)誤可以通過 Repair 功能來進(jìn)行修復(fù)。　　　Repository 復(fù)制功能操作如圖所示: 江蘇省電力公司信息化登高項(xiàng)目 MDM 培訓(xùn)手冊第 33 頁 共 85 頁Repository 屬性設(shè)置是設(shè)置 Repository 的多語言以及運(yùn)行端口，每個(gè)Repository 需要設(shè)置不同的 port,如果設(shè)置相同則會導(dǎo)致 Repository 無法加載。如圖所示:Repository 多語言設(shè)置步驟如下: 江蘇省電力公司信息化登高項(xiàng)目 MDM 培訓(xùn)手冊第 34 頁 共 85 頁Repository 的詳細(xì)設(shè)置界面如下： Repository Modelling　Repository 建模主要利用 MDM 交付的表類型、字段類型來進(jìn)行模型構(gòu)建工作。一個(gè) Repository 必須由一個(gè)或一個(gè)以上的主表(main table).　一個(gè)主表包含某個(gè)業(yè)務(wù)對象的主要信息，例如產(chǎn)品、物料、客戶等等。Repository 默認(rèn)的主表名稱是 Product，可以進(jìn)行修改。主表之間可以共享數(shù)據(jù)，比如供應(yīng)商和客戶可以共享國家這個(gè)表。MDM 表類型可以參考下圖:MDM Data Table TypesTable Type Description Main and subtables Main A main table is a flat table containing the primary information about a business object. For example, an MDM repository of product information would include an individual record for each product and an individual field for each piece of information that applies to all products, such as SKU, product name, manufacturer, and price. New MDM repositories include a main table named Products. Flat A flat table has the standard, rectangular SQL structure consisting of records and fields (rows and columns). A main table in an MDM repository typically contains some fields whose possible data values are limited and can therefore be selected from a list, rather than entered manually. For example, a Country field would naturally have a limited set of possible values. These values can 江蘇省電力公司信息化登高項(xiàng)目 MDM 培訓(xùn)手冊第 35 頁 共 85 頁be stored as records in a separate, flat subtable associated with a Country lookup field in a main table. New MDM repositories do not include any flat tables. Hierarchy A hierarchy table anizes information in a hierarchy, where each record is related to a parent record (even if the only parent is the root) and may also be related to sibling records and/or child records. The main table in an MDM repository typically contains some fields whose data may be hierarchical in nature. For example, a Manufacturer field may need to acmodate division and subdivision information for manufacturers. This hierarchical information is stored in a separate, hierarchy subtable associated with the Manufacturer lookup field in the main table. Note that a hierarchy table is useful even when it is flat (. only leaf nodes below the root), because it stores the ordered sequence of sibling records, allowing you to override the unordered sequence of values in a flat table and instead put the values in a fixed order. New MDM repositories include the following hierarchy tables: a default taxonomy table, the Masks table, and the Families table. Table Type Description Taxonomy1 Predefined. A taxonomy is the classification scheme that defines the categories and subcategories that apply to a collection of records. Categorizing records enables you to isolate subsets of records for various anizing, searching, editing and publishing purposes. A taxonomy table in MDM stores a hierarchy of categories and subcategories and also supports attributes, “subfields” that apply to particular categories rather than to the entire collection of records. MDM supports multiple simultaneous taxonomies. New MDM repositories include a single taxonomy table named Categories. Qualified Flat Subtable. A qualified table in MDM stores a set of lookup records, and also supports qualifiers, “subfields” that apply not to the qualified table record by itself, but rather to each association of a qualified table record with a main table record. MDM supports multiple simultaneous qualified tables. Qualified tables can be used to support product applications and applicationbased search, and also to store any large set of subtable records that contain fields whose values are different for each main table record, such as multiple prices for different quantities, divisions, regions, or trading partners, crossreference part numbers, and 江蘇省電力公司信息化登高項(xiàng)目 MDM 培訓(xùn)手冊第 36 頁 共 85 頁additional distributor/supplier/customerspecific information for different distributors, suppliers, or customers. New MDM repositories do not include any qualified flat tables. Object tables Images A single table named Images. Stores image files, where each image is stored as a record in the table. Sounds A single table named Sounds. Stores sound files, where each sound file is stored as a record in the table. Videos A single table named Videos. Stores video files, where each video file is stored as a record in the table. Binary Objects A single table named Binary Objects. Stores other binary object files, where each binary object file is stored as a record in the table. Text Blocks A single table named Text Blocks. Stores blocks of text, where each text block is stored as a record in the table. Copy Blocks A single table named Copy Blocks. Stores blocks of text interpreted as copy, where each text block is stored as a record in the table. Text HTMLs A single table named Text HTMLs. Stores blocks of text interpreted as HTML, where each text block is stored as a record in the table. PDFs A single table named PDFs. Stores PDF files, where each PDF is stored as a record in the table. Special tablesImage Variants A single table named Image Variants. Used to define t