InfoSphere Master Data Management Reference Data Management Hub Version 10 Release 0. User s Guide GI

Size: px
Start display at page:

Download "InfoSphere Master Data Management Reference Data Management Hub Version 10 Release 0. User s Guide GI"

Transcription

1 InfoSphere Master Data Management Reference Data Management Hub Version 10 Release 0 User s Guide GI

2

3 InfoSphere Master Data Management Reference Data Management Hub Version 10 Release 0 User s Guide GI

4 Note Before using this information and the product that it supports, read the information in Notices and trademarks on page 85. Edition Notice This edition applies to version 10.0 of IBM InfoSphere Master Data Management Server and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 2011, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents Chapter 1. Managing reference data... 1 InfoSphere MDM Reference Data Management Hub Overview Components of the InfoSphere MDM Reference Data Management Hub solution The InfoSphere MDM Reference Data Management Hub server The InfoSphere MDM Reference Data Management Hub user interface Chapter 2. Defining data sets and mappings with reference data types.. 7 Overview Business keys Creating reference data types for sets Adding reference data type properties Editing or deleting properties for reference data types Creating compound key data types Data validation for property types Reference data set data types Creating reference data types for mappings Adding reference data type properties Editing or deleting properties for mapping data types Editing reference data types Copying reference data types Deleting reference data types Chapter 3. Managing reference data with reference data sets Overview Reference data set versions The lifecycle of reference data sets Reference data set translation Reference value management Working with reference data sets Creating reference data sets Creating reference data set versions Changing reference data sets Copying reference data sets Deleting reference data sets or data reference set versions Comparing reference data sets Organize sets using folders Using folders Creating folders Moving reference data sets into folders Deleting folders Working with reference values Creating reference values Changing reference values Deleting reference values Importing reference values from a CSV or XML file Exporting reference values to a CSV or XML file 31 Finding reference values with the advanced filter 32 Adding translations to reference values Reference data set hierarchies Tree-style hierarchies Level-based hierarchies Reference data set subscriptions Creating Subscriptions Editing subscriptions Deleting subscriptions Reference data set history Chapter 4. Relating associated data across reference data sets About data set mappings Creating mappings Mapping reference values Editing mappings Deleting mappings Deleting mappings of reference values Importing mappings Creating a CSV file for importing mappings.. 46 Importing mapped values into mappings Exporting mappings to a CSV or XML file Chapter 5. Configuring data providers and consumers Creating managed systems Editing or deleting managed systems Setting the owner About importing reference data from managed systems About exporting reference data to managed systems 51 Chapter 6. Exporting data from the command line Overview of batch export Batch export command parameter options Running batch export Batch export results Appendix. Data and configuration reference Reference data set properties Reference value properties Reference data type properties Custom reference data type properties Schemas for XML import Reference data XML schema Structural hierarchy XML schema Adjacency list XML schema Data types XML schema Mapping set XML schema Mapping properties Copyright IBM Corp. 2011, 2012 iii

6 Validation rules Lifecycles and states Language names for translation import Legal Statement Index Contacting IBM Notices and trademarks iv User s Guide

7 Chapter 1. Managing reference data The InfoSphere MDM Reference Data Management Hub is an application for centralized stewardship and management of enterprise reference data. After you install and configure the InfoSphere MDM Reference Data Management Hub, you perform the following tasks: v v v v v Define the different reference data sets that will be managed within the InfoSphere MDM Reference Data Management Hub. Import data in CSV or XML format into the sets, or create entries manually by using the InfoSphere MDM Reference Data Management Hub user interface. Define any hierarchies over the reference data. Create mappings and relationships between related reference data sets. Publish or export reference data. InfoSphere MDM Reference Data Management Hub Overview The IBM InfoSphere Master Data Management Reference Data Management Hub solution provides a single point of management and governance for enterprise reference data. The InfoSphere MDM Reference Data Management Hub has been designed from the ground up to provide a robust solution for centralized management, stewardship, and distribution of enterprise reference data. It supports defining and managing reference data as an enterprise standard. It also supports maintaining mappings between the different application specific representations of reference data used within the enterprise. The InfoSphere MDM Reference Data Management Hub supports formal governance of reference data, putting management of the reference data in the hands of the business users, reducing the burden on IT, and improving the overall quality of data used across the organization. The InfoSphere MDM Reference Data Management Hub is built on the proven IBM InfoSphere Master Data Management platform. It has been implemented as a new master data domain with its own data model, services and stewardship user interface for managing enterprise reference data. Designed for business users, the intuitive user interface and flexible data model ensure a quick implementation and minimize the need for IT involvement on an ongoing basis. Key functions of the InfoSphere MDM Reference Data Management Hub include: v Role based user interface with security and access control v Management of reference data sets and values v Management of mappings between reference data sets v Import and export of reference data by using CSV and XML format v Versioning support for reference data sets and maps v Change process controlled through configurable life cycle management v Hierarchy management over sets of reference data Copyright IBM Corp. 2011,

8 The InfoSphere MDM Reference Data Management Hub also integrates with and complements IBM Business Glossary and the broader portfolio of IBM Information Management products. Some examples of drivers for managing reference data include: v Banking: EU countries have adopted different versions of the European NACE industry classification code set as their national standard. Banks with operations in multiple countries must support the individual national NACE code sets of each country at the local level, and reconcile the differences across countries at the corporate level. The InfoSphere MDM Reference Data Management Hub enables you to manage the different versions of the NACE codes from a central point. It simplifies creation of mappings between the different versions and supports reconciling values across the different set versions. v Banking: Banks face the dual challenge of distributing reference data changes to downstream applications and assessing what applications are impacted by a reference data change. InfoSphere MDM Reference Data Management Hub provides a subscription model that makes it possible to assess what applications are impacted by a particular reference data set change. v Healthcare: The U.S. government mandated that healthcare payers and providers must use ICD-10 codes for diagnoses and procedures by October The challenge the healthcare industry faces is the lack of a one-to-one relationship between the ICD-9 and ICD-10 codes. The InfoSphere MDM Reference Data Management Hubsupports central management of the ICD standards and mappings and the definition of company-specific mapping schemes. v Cross Industry: Loading data into a data warehouse or a master data management hub typically requires reconciling reference data from multiple sources. The InfoSphere MDM Reference Data Management Hub supports publishing reference data map files for batch and load jobs to support warehouse or InfoSphere MDM hub data load. What is reference data? Reference data is any data that is used to categorize other data within the enterprise. Reference data is commonly stored in the form of code tables or lookup tables, such as country codes, state codes, and gender codes. Reference data is used within every enterprise application, from back-end systems through front-end commerce applications to the data warehouse. Business users recognize reference data as code choices within the pick-lists of their business application user interfaces. Reference data code tables are often implemented in the database as relatively simple structures with a key column containing a code value and a description column. Some code tables, such as NACE, have a small number of values (in the tens or hundreds). Others, such as healthcare ICD-10 codes, have larger numbers of values (in the tens of thousands). They can be flat lists or have a hierarchical code structure. A hierarchy can be defined over the values within the code table, or a hierarchy can be defined where each level is a code table in its own right. The structural simplicity and static nature of code tables belies the cost and difficulty of managing code tables at the enterprise level. The problems with code tables include the sheer number of code tables used within and across enterprise applications. Each application often has its own representation and set of values for code sets defining the same thing. When integrating data across applications, it's necessary to translate between the different code table representations in order to categorize data in a consistent way. Mapping between the different 2 User s Guide

9 representations and keeping track of changes across all the different code table variations on an ongoing basis can be a major challenge. Many enterprises struggle with this challenge using spreadsheets and other error-prone manual processes to record and manage changes to reference data sets and their relationships to each other. The lack of change management, audit controls and security is often a compliance risk, and as reference data is used to drive key business processes and application logic - errors in the reference data can have a major business impact. Mismatches in reference data can have a major impact on data quality, can affect the integrity of BI reports, and is a common source of system integration failure. The new InfoSphere MDM Reference Data Management Hub provides enterprises with a robust master data management solution for centralized management, stewardship, and distribution of reference data within the enterprise. Components of the InfoSphere MDM Reference Data Management Hub solution The InfoSphere MDM Reference Data Management Hub consists of the Reference Data Management Hub server and the Reference Data Management Hub user interface. Figure 1. The IBM Reference Data Management architecture The InfoSphere MDM Reference Data Management Hub server The InfoSphere MDM Reference Data Management Hub server component is the server and repository for managing and storing reference data. It has been implemented as a new master data management domain on the proven IBM InfoSphere MDM platform. The InfoSphere MDM Reference Data Management Hub uses an underlying domain model designed for managing reference data. The hub takes advantage of base InfoSphere MDM Custom Domain Hub platform frameworks and services for security, business rules, data quality processes, events and notifications, audit, and history. Chapter 1. Managing reference data 3

10 4 User s Guide Reference data maintenance services support creation, maintenance, and search of reference data sets and the reference data values within those sets. Import and distribution services support import and export of reference data in multiple formats. Transcoding services support the mapping and transformation of data from one application representation to another. The InfoSphere MDM Reference Data Management Hub user interface The InfoSphere MDM Reference Data Management Hub user interface was designed specifically for managing reference data. It was developed using the latest web technologies for a more appealing user experience and assumes business users rather than technical users as the primary audience. The user interface is a role based UI with out-of-the-box security, versioning, and review and approval lifecycle management built in. New types of reference data can be defined directly with the user interface without requiring any code development. Using the InfoSphere MDM Reference Data Management Hub user interface, you can define canonical reference data sets and maintain the values within those sets and the mappings between reference data sets. You can also search, view, create, update, delete, and import reference data values. After you log in to the user interface, you see tabs across the top of the display area. Reference Data Sets On this tab, you manage the reference data sets that contain your reference data. You can create new sets, edit existing sets, delete unwanted sets, and manage versions of the reference data sets and set hierarchies. You also provide the reference values for the sets, translation values for them. Mappings On this tab, you manage the mappings between reference data sets. Maps define the relationships between reference data sets and the reference data values within those sets, to relate associated data in multiple reference data sets. Managed Systems Managed systems are references to external systems which represent the suppliers and consumers of the reference data defined. On this tab, you specify all relevant properties of the managed system to enable communication with the managed system by InfoSphere MDM Reference Data Management Hub and integrated applications. Administration On this tab, you manage the data types that are used by mappings and reference data sets. Custom Page On this tab, you can provide your users custom functions that you define by using HTML, javascript, or Java. The IBM InfoSphere MDM Reference Data Management Hub Transaction Reference provides information about the transactions used to interface with the InfoSphere MDM Reference Data Management Hub. In the upper-right portion of the screen are the following functions:

11 Role From this list, you can choose the role for which your user name was configured. Some users have a single role, and other users can choose from multiple roles. Users who were assigned to the RDMRole_All group can select the All option, which gives access to all functions of the combined roles. Help From this menu, you can access the online help (this information center) or the customer support portal. About Clicking this link opens a dialog to display information about this product. Log Out Clicking this link logs you out of the application. Chapter 1. Managing reference data 5

12 6 User s Guide

13 Chapter 2. Defining data sets and mappings with reference data types Every reference data set and mapping is associated with a reference data type, which defines the properties of the data set or mapping. About this task These procedures require a role with access to the Administration tab. For information about configuring user roles, see the installation and configuration instructions. Overview Every reference data set (data table) or mapping created within InfoSphere MDM Reference Data Management Hub has a default set of properties. These reference data set and mapping properties are defined by using reference data types. Every data set and mapping is associated with a data type definition. The InfoSphere MDM Reference Data Management Hub system comes with two basic data types, Default Reference Data Type and Default Mapping Type, which can be used to define a simple reference data set or mapping. You can create reference data types with additional properties to define more complex reference data sets or mappings. Properties that are defined in a reference data type can be applied at the reference data set level, or at the value level for sets and mappings. At the value level, properties apply to all the rows of data in a data table or to all value mappings. Reference data types have a data type property, which designates whether the reference data type is used to create reference data sets or mappings. After the reference data type is saved, its data type cannot be changed. Business keys You can create reference data types with compound keys. You can specify up to four properties plus the Code as constituent key parts of a unique reference data value key. Business keys apply only to reference data set data types; mapping set data types do not use business keys. The business key feature is enabled for a reference data type in the Administration menu. Checking the business key check box for a reference data type is one way to ensure that the code for a reference data set is unique. Note: Name is also a required field for each reference value but is not used in determining uniqueness of the compound key. InfoSphere MDM Reference Data Management Hub supports up to five properties within a compound key for a set, where Key 1 is always the set Code. The other four properties must have the Key property enabled within the reference data type definition. Copyright IBM Corp. 2011,

14 Compound keys allow records with the same code to be saved, if the combined key is unique. The uniqueness check is done against the full key defined for the type. If the overall compound key is unique, the record can be stored. Importing values into a reference data set defined as having a compound key is the same as importing values into any other set. The same rules hold for the manual case: the key values cannot be null and the overall combination of keys + code must be unique for each value. The business key check box and compound key definition can be applied for a reference data set with existing values if the values conform to the rules defined for the keys. InfoSphere MDM Reference Data Management Hub checks for data integrity when you change compound key settings for a reference data set type and does not allow actions that would create duplicate entries in the database where uniqueness is required. In InfoSphere MDM Reference Data Management Hub, uniqueness is not enforced for the Code property unless the business key option is selected. Uniqueness is not enforced to support effective date-centric use cases that require multiple entries for the same code with different effective dates. Note: For most reference data types, the business key is recommended. If you receive the error message The data consistency check failed. Update not allowed for Property Type used as Compound Key., edit the reference values to ensure uniqueness across all properties that make up the compound key before enabling the business key on the reference data type. Related tasks: Creating compound key data types on page 11 You create special reference data types for supporting compound keys. Compound key reference data types are like other reference data types except that they have one or more key properties. Adding reference data type properties on page 9 You add custom properties to a reference data type to define the columns that are available to any reference data set that uses the reference data type. Importing reference values from a CSV or XML file on page 30 If you have reference data stored in a comma-separated values (CSV) or Extensible Markup Language (XML) file, you can easily import it into a reference data set. Creating reference data types for sets To define the properties and structure of reference data sets, you create reference data types that use the Reference Data Set data type property. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task This procedure requires a role with access to the Administration tab. For information about configuring user roles, see the installation and configuration instructions. 8 User s Guide

15 Procedure 1. Click the Administration tab. 2. Click New. 3. Enter a Name for this reference data type. 4. For the Data type, select Reference Data Sets. 5. Optional: To use a validation rule for the Code property of each reference value, enter the Code validation rule. Validation rules ensure that the data matches a format you specify with regular expressions. For an introduction to validation rules, see Validation rules on page Optional: To add custom properties, see Adding reference data type properties. 7. To save the new reference data type and its custom properties, click Save. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Creating level-based hierarchies on page 38 You create a level-based hierarchy to link reference data sets together by their reference values. Related reference: Reference data type properties on page 60 Every reference data type has a default set of properties that define the base structure of reference data sets. Adding reference data type properties You add custom properties to a reference data type to define the columns that are available to any reference data set that uses the reference data type. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task Perform these steps for each property you want to create. Procedure 1. Click the Administration tab. 2. Select the reference data type to which you want to add properties. 3. To add reference value properties, click the Value Level tab. Properties at the value level are available for each reference value in the set. a. Click New. The Data Type Property dialog opens. b. In the Data Type Property dialog, enter the Name for this property. The name you supply is displayed as an additional field on the Properties tab for each reference value in reference data sets that use this reference data type. c. Optional: Enter values for the remaining fields. For information about the custom property fields, see Custom reference data type properties on page 61. Chapter 2. Defining data sets and mappings with reference data types 9

16 10 User s Guide Note: The Key property requires that Enable business key is enabled on the reference data type. d. Click OK. 4. To add reference set properties, click the Set Level tab. Properties at the set level apply to the entire reference data set. a. Click New. The Data Type Property dialog opens. b. In the Data Type Property dialog, enter the Name for this property. The name you supply is displayed as an additional field on the Set Properties tab for reference data sets that use this reference data type. c. Optional: Enter values for the remaining fields. For information about the custom property fields, see Custom reference data type properties on page 61. d. Click OK. 5. To save the reference data type and its custom properties, click Save. Related concepts: Business keys on page 7 You can create reference data types with compound keys. You can specify up to four properties plus the Code as constituent key parts of a unique reference data value key. Business keys apply only to reference data set data types; mapping set data types do not use business keys. Related tasks: Creating level-based hierarchies on page 38 You create a level-based hierarchy to link reference data sets together by their reference values. Related reference: Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Editing or deleting properties for reference data types You can change or delete the custom properties for a reference data type. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task When the reference data type is in use by a reference data set, you can add new properties, delete unused properties or change whether a value-level property in use is unique. You cannot change the data type for a property that is being used. Procedure 1. Click the Administration tab. 2. Select the reference data type whose properties you want to edit or delete. 3. Click the Value Level tab to edit or delete custom value-level properties. 4. Click the Set Level tab to edit or delete custom set-level properties. This tab applies to reference data set data types only. 5. Select a property and click Edit or Delete. 6. If you are deleting a property, click Delete to confirm you want to delete it.

17 7. If you are editing the property, make the necessary changes. 8. To save changes to the reference data type, click Save. Related reference: Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Creating compound key data types You create special reference data types for supporting compound keys. Compound key reference data types are like other reference data types except that they have one or more key properties. Procedure 1. Click the Administration tab. 2. Click New to create a reference data type. 3. Type the name for the new reference data type. 4. Choose Reference Data Set Type as the Type. 5. Enable the Enable business key option. 6. Add Value Level properties. a. Click New. The Data Type Property dialog opens. b. Enable the Key option to indicate that this property is a key. The Required check box is automatically enabled and cannot be disabled. c. To close the Data Type Property dialog, click OK. 7. To save the new reference data type and its properties, click Save. Related concepts: Business keys on page 7 You can create reference data types with compound keys. You can specify up to four properties plus the Code as constituent key parts of a unique reference data value key. Business keys apply only to reference data set data types; mapping set data types do not use business keys. Data validation for property types Validation rules check that supplied data is in a valid format, such as two letters followed by three digits. These rules are defined through the use of regular expressions, a simple and powerful language. Validation rules can be used when defining reference data types. The Code validation rule field validates the Code field that is entered for the values in a set. For example, if your reference data set is for states or provinces, and you want the code to be a two-letter abbreviation that uses only capital letters, the code validation rule is [A-Z]{2}. You can also use validation rules in the Validation rule field when defining the settings for a string data type of a custom property. A rule is considered matched if the text that is being checked fits the constraints imposed by the rule you defined. More information about data validation rules can be found in Validation rules on page 76. Detailed tutorials on regular expressions are outside the scope of this document. Example 1 code format Chapter 2. Defining data sets and mappings with reference data types 11

18 Rule: The Code for any entered value must be two letters followed by three digits. Validation Rule: [A-Za-z]{2}[\d]{3} [ The beginning of a rule for matching a single character. A-Za-z Match any characters in the range of A-z (uppercase and lowercase letters). ] The end of the rule for matching a character. {2} The previous section must match two consecutive characters. [\d] A short way of saying [0-9]. {3} The previous section must match three consecutive characters. Example 2 alphanumeric code Rrule: Any combination of numbers and letters, with a length of at least 1. Validation Rule: [A-Za-z0-9]+ [A-Za-z0-9]+ Match any alphanumeric character. + Match the previous section at least once, with no upper limit. Example 3 part number Rule: A six to eight-digit number, optionally followed by a hyphen and another five-digit number. Validation Rule: [\d]{6,8}(-[\d]{5})? [\d]{6,8} Match six to eight digits in a row. ( Begin a new section. - Literally match the - character. [\d]{5} Match five digits in a row. ) End the section began by the previous (.? The previous section does not have to be matched, but cannot match more than once. (The section is optional.) Example 4 address Here is a simple example of an address validation. Rule: An alphanumeric handle followed by symbol, followed by the domain name. Validation Rule: \b[a-za-z0-9._%+-]+@[a-za-z0-9.-]+\.[a-z]{2,4}\b \b The beginning of a word boundary. 12 User s Guide

19 [A-Za-z0-9._%+-] Match any combination of uppercase and lowercase letters, digits, and the period, underscore, percent sign, plus sign, or minus sign characters. The next character must be an at sign [A-Za-z0-9.-] Match any combination of uppercase and lowercase letters, digits, and the period or minus sign characters. +\. Literally match the period character. [A-Za-z]{2,4} Thenext2-4characters must be letters. \b The end of a word boundary. Related reference: Validation rules on page 76 Validation rules ensure that the data matches a format you specify with regular expressions. They can be imposed on the Code property for a reference value, and on string data types in a custom property. The syntax used is based on the Java regular expression syntax. InfoSphere MDM Reference Data Management Hub matches only when the entire input string explicitly matches. Reference data set data types When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value. The current version of a set is one that meets all of these conditions: v The state is in an approved state for the lifecycle process or state machine. v The effective date is the current date or earlier. v The expiration date is after the current date. If more than one version meets these conditions, the most recent version is considered the current version. Note: The effective date and expiration date for individual reference values are not relevant to the definition of a current version. Example You create a reference data set called Countries, which contains reference values for country names. The State for the Countries data set is Approved. Its Effective date was last month, and its Expiration date is next year. Next, you create a reference data type called Branches, which includes a Value Level property called Country. The data type for the Country property is Reference Data Set, and its Related set is the Countries reference set. Chapter 2. Defining data sets and mappings with reference data types 13

20 14 User s Guide When you create a reference data set called Branches, basing it on the Branches reference data type, the Country property is populated with the values from the Countries data set.

21 Note: The Country property is populated with the values from the Countries data set only if the Countries data set has a current version (that is, the set meets the three conditions listed above). Related concepts: Level-based hierarchies on page 37 InfoSphere MDM Reference Data Management Hub supports level based hierarchies across multiple sets, where each level of the hierarchy is associated with a different reference data set. Related tasks: Creating level-based hierarchies on page 38 You create a level-based hierarchy to link reference data sets together by their reference values. Related reference: Lifecycles and states on page 77 Every reference data set and mapping has a state that corresponds to its lifecycle process. The lifecycle is used by the data administrators to control the versions of reference data sets and mappings that are in use. Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Creating reference data types for mappings To define the properties and structure of mappings, you create reference data types that use the Mapping Set data type property. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. For information about reference data type properties, see Reference data type properties on page 60. About this task This procedure requires a role with access to the Administration tab. For information about configuring user roles, see the installation and configuration instructions. Procedure 1. Click the Administration tab. 2. Click New. 3. Enter a Name for the reference data type. 4. Optional: Enter a Description. 5. For the Data type, select Mapping Set. 6. Optional: To add custom properties for the value mappings, see Adding reference data type properties on page To save the new reference data type and its custom properties, click Save. Chapter 2. Defining data sets and mappings with reference data types 15

22 Related reference: Reference data type properties on page 60 Every reference data type has a default set of properties that define the base structure of reference data sets. Adding reference data type properties You add properties to a reference data type to define the columns that are available to any mapping that uses the reference data type. Before you begin Log into InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task Perform these steps for each property you want to add. Procedure 1. Click the Administration tab. 2. Select the reference data type to which you want to add properties. 3. To add value properties, click the Value Mapping Properties tab. These properties are available for each mapping. a. Click New. The Data Type Property dialog opens. b. In the Data Type Property dialog, enter the Name for this property. The name you supply is displayed as a custom property field for each value mapping in maps that use this reference data type. c. For the Type, select the appropriate data type. d. Optional: Enter values for the remaining fields. e. Click OK. 4. To save the reference data type and its custom properties, click Save. Related reference: Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Editing or deleting properties for mapping data types You can change or delete the custom properties for a mapping data type. Before you begin Log into InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task When the data type is in use by a mapping, you can add new properties, delete unused properties or change whether a value-level property in use is unique. You cannot change the data type for a property that is being used. 16 User s Guide

23 Procedure Editing reference data types 1. Click the Administration tab. 2. Select the reference data type whose properties you want to edit or delete. 3. Select a property and click Edit or Delete. 4. If you are deleting a property, click Delete to confirm you want to delete it. 5. To save changes to the reference data type, click Save. Related reference: Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. You edit a reference data type when you need to change its properties. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. About this task The data type property cannot be changed. Procedure 1. Click the Administration tab. 2. Select the reference data type you want to change. 3. Change the properties as needed. 4. To save the changes to the reference data type and its custom properties, click Save. Related reference: Reference data type properties on page 60 Every reference data type has a default set of properties that define the base structure of reference data sets. Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Copying reference data types You copy a reference data type to easily create a similar one. All values and custom properties are also copied. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. Procedure 1. Click the Administration tab. 2. Select the reference data type you want to copy. 3. Click Copy Data Type. Chapter 2. Defining data sets and mappings with reference data types 17

24 4. At the prompt, enter the Name for the new data type. 5. Click OK. The copy is created. 6. Edit the copied reference data type as needed. Related reference: Reference data type properties on page 60 Every reference data type has a default set of properties that define the base structure of reference data sets. Custom reference data type properties on page 61 When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Deleting reference data types You can delete unwanted reference data types by using the Administration option. Reference data types that are used to define an existing reference data set or mapping cannot be deleted. Before you begin Log in to InfoSphere MDM Reference Data Management Hub and select a role that permits access to the Administration tab. Procedure 1. Click the Administration tab. 2. Select the reference data type you want to delete. 3. Click Delete. 4. At the prompt, confirm you want to delete the reference data type by clicking Delete. 18 User s Guide

25 Chapter 3. Managing reference data with reference data sets Overview You define reference data sets to manage reference data. An example of a reference data set is "Countries," which is used to list the countries in which customers reside or business partners operate. You store the data values for each property in the reference data set. Before you begin Create a data type upon which to base the data set. See Creating reference data types for sets on page 8. Procedure 1. Create the reference data set. See Creating reference data sets on page Create one or more reference values for the data set. See Creating reference values on page Optional: Create translations for each reference value. See Adding translations to reference values on page Optional: Create a hierarchy for the data set. See Reference data set hierarchies on page 35. What to do next Create mappings between data sets and their reference values. See Chapter 4, Relating associated data across reference data sets, on page 43. Reference data sets are at the heart of the system and are used to manage and contain reference data. Every reference data set is associated with a Reference Data Type, which defines the properties of the data set. When a reference data set is created, it is automatically given a version number, starting with 1. You can change the version number to another value, numeric, or alphabetic. When you create new versions, you can give them any label to indicate the version number. Each reference data set has at least one version. All versions of a data set are grouped together. For ease of management, reference data sets can also be grouped in folders. The InfoSphere MDM Reference Data Management Hub user interface uses a drag hierarchy widget to visualize and manipulate the reference data set folder hierarchy, and the reference data sets within them. Folders and the reference data sets they contain, or individual reference data sets, can be dragged and dropped from one folder to another. Each reference value has properties which contain values. The reference value properties are defined as part of the reference data type upon which the reference data set is based. Copyright IBM Corp. 2011,

26 Reference data set versions Reference data sets support versions. Versions are used to provide a structured approval process for changes to reference data before those changes become active. Data stewards can also create a copy of a reference data set as a new version of the original, preserving a set before changes are made. In the event the changes are unwanted, the later version can be deleted to restore the preserved version. Related tasks: Creating reference data set versions on page 22 You create a version of a reference data set when you want to change its properties or its reference values without affecting the existing versions. Using folders on page 27 You use the Folder View within the Reference Data Sets tab to view and create folders for organizing your reference data sets. The lifecycle of reference data sets A set of lifecycle states is defined for a reference data set and mappings, and transition rules determine what the valid state transitions are. The set of lifecycle states and allowable transitions from one state to another can be defined and changed to support different review and approval process flows. The valid state values and transitions are described in Lifecycles and states on page 77. Reference data set translation Reference data sets can have multiple language translations for each reference value in the set. The translations of a particular reference value can be provided manually on the Translations tab in the Set Values view. Alternatively, the translations can be imported from a comma-separated values (CSV) file. For more information about importing data value translations, see Importing translated reference values on page 33. Reference value management Reference data sets contain rows of data values, which might be only a few rows or large data sets. Data set size is unlimited by InfoSphere MDM Reference Data Management Hub, but it is normally fewer than 100,000 rows. The data can be managed by the graphical user interface, InfoSphere MDM Reference Data Management Hub data imports, or updates applied by using the batch processor or web services. 20 User s Guide

27 Related tasks: Working with reference values on page 28 Each row in the data set can contain multiple properties, as defined by the data set type, and support a number of different languages. In addition, data values can participate in both mapping and hierarchy associations. Using the graphical user interface, you create, edit and delete the values contained in a data set. You can reduce the number of visible data rows by using the filter option to select a subset of the data. Working with reference data sets After you create reference data sets, you create reference values for those sets. You can edit and delete sets or reference values, although some properties, such as the lifecycle or reference data type, become read-only after the data set is initially saved. Creating reference data sets You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Before you begin Create the reference data type on which to base this reference data set. Procedure 1. Click the Reference Data Sets tab. 2. Click New Set. The New Set dialog opens. Note: Sets created with the New Set button are created at the root level, as indicated by the value None for the Parent Folder field. 3. Alternatively, you can right-click a folder in the Folder View and select New > Set to create a set in the selected folder. The Parent Folder field on the New Set dialog shows the selected folder. 4. Enter details for the new reference data set, providing a value for all mandatory fields. 5. Select values for the optional properties as needed. 6. Click OK. 7. To save the set, click Save. What to do next Create reference values. See Creating reference values on page 28. Chapter 3. Managing reference data with reference data sets 21

28 Related concepts: Tree-style hierarchies on page 35 Reference data set hierarchies within InfoSphere MDM Reference Data Management Hub are tree-style hierarchy structures created over the values within a reference data set. You access the hierarchies by using the Set Hierarchies view. Related tasks: Setting the owner on page 50 You set the owner of an object to designate the user groups that can edit it. Creating reference data types for sets on page 8 To define the properties and structure of reference data sets, you create reference data types that use the Reference Data Set data type property. Using folders on page 27 You use the Folder View within the Reference Data Sets tab to view and create folders for organizing your reference data sets. Creating reference data set versions You create a version of a reference data set when you want to change its properties or its reference values without affecting the existing versions. Creating reference values on page 28 You create reference values to add rows to a reference data set. Importing reference values from a CSV or XML file on page 30 If you have reference data stored in a comma-separated values (CSV) or Extensible Markup Language (XML) file, you can easily import it into a reference data set. Creating mappings on page 43 You create mappings as the first step in associating data between reference data sets. You create mappings from a specific version of a source set to a specific version of a target set. Related reference: Reference data set properties on page 59 Every reference data set has a default set of properties in addition to any custom properties that are created in the reference data type. Creating reference data set versions You create a version of a reference data set when you want to change its properties or its reference values without affecting the existing versions. Before you begin Click the Reference Data Sets tab and choose the reference data set to work with. Procedure 1. Select the version you want to work with. 2. Right-click the version on which you want to base the new version and select New > Version from the menu. The New Set Version dialog opens. 3. Provide a value for the New version field. 4. Select a copy option. Values and hierarchies The new version inherits all of the reference values and hierarchies from the base version, and the properties of the set. Values and hierarchies is the default option. 22 User s Guide

29 Values only The new version inherits only the reference values from the base version and the properties of the set. Nothing The new version is created with no reference values or hierarchies. It inherits only the properties of the set. This option is useful when you intend to import reference values from an external source. 5. Click Create. Related concepts: Reference data set versions on page 20 Reference data sets support versions. Versions are used to provide a structured approval process for changes to reference data before those changes become active. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Importing reference values from a CSV or XML file on page 30 If you have reference data stored in a comma-separated values (CSV) or Extensible Markup Language (XML) file, you can easily import it into a reference data set. Changing reference data sets You change a reference data set when you want to edit its properties. Fields that cannot be changed are disabled. Set properties are defined on the Set Level tab for the reference data type. Before you begin On the Reference Data Sets tab, choose the reference data set to work with. Procedure 1. If the reference data set has more than one version, select the version whose properties you want to change. 2. From the View menu, select Set Properties. 3. Edit the fields as needed. 4. To save your changes, click Save. Related tasks: Setting the owner on page 50 You set the owner of an object to designate the user groups that can edit it. Changing reference values on page 29 You change reference values when you want to edit existing rows within a data set. Related reference: Reference data set properties on page 59 Every reference data set has a default set of properties in addition to any custom properties that are created in the reference data type. Copying reference data sets You copy reference data sets when you want to create a reference data set with properties similar to an existing one. Chapter 3. Managing reference data with reference data sets 23

30 Before you begin On the Reference Data Sets tab, choose the reference data set to work with. Procedure 1. Right-click the reference data set version you want to copy and select Copy to set. 2. Name the new reference data set. 3. Click Copy. Deleting reference data sets or data reference set versions You delete reference data sets versions you no longer want. Deleting the only version of a set also deletes the set. Reference data sets cannot be deleted if they are referenced by other sets or mappings. Before you begin Open the Reference Data Sets tab. Procedure 1. Select the reference data set version you want to delete. Note: Reference data sets cannot exist without at least one version. If you delete the only version, the set itself is also deleted. 2. Click Delete. Note: Whether reference data sets can be deleted depends on the lifecycle state and the security configurations. 3. Confirm that you want to delete the version. Related tasks: Deleting reference values on page 30 You delete reference values when you do not want to use them any longer. Data deletion is always handled by a soft deletion mechanism. Data is never physically deleted from the InfoSphere MDM Reference Data Management Hub database on a delete action. Related reference: Lifecycles and states on page 77 Every reference data set and mapping has a state that corresponds to its lifecycle process. The lifecycle is used by the data administrators to control the versions of reference data sets and mappings that are in use. Comparing reference data sets As part of reviewing a reference data set, you might want to know what changed between different versions. You can also compare two different sets. You can compare sets or set versions to see additions, deletions and differences in the values and properties. Before you begin Click the Reference Data Sets tab and select the reference data set you want to work with. 24 User s Guide

31 Procedure 1. Select the second set or set versions you want to compare by holding the Control key (Microsoft Windows) or Command key (Mac OS) and clicking the set. 2. Right-click and select Compare from the menu. 3. Review the comparison in the Comparison Report dialog. 4. To export the results of the comparison to a CSV file, click Export > CSV > Set Values to export the set differences or Export > CSV > Set Properties to export the set properties differences. 5. When you are finished, click OK to close the dialog. Comparison Report dialog The Comparison Report dialog shows the differences between two reference data sets or versions of a reference data set. Comparing Set The name of the set that is being compared. If two different sets are being compared, only the first set that you clicked is shown here. Comparing Versions The version numbers and states for the versions that are being compared. The actual version label is displayed. For example, if you compare versions 1A and 5B of a set, the values 1A and 5B are displayed in this section and in the Values Changes section. Properties Changes The property name for the set property that was changed. If the set properties are identical between the two versions, this section is blank. Values Changes This grid displays the reference value name, property name, and the value for each version where there is a difference. When all properties of a reference value are identical between the two versions, the reference value is not listed. When a reference value exists in one version but not in the other, the reference value was added to a version or removed from a version. Note: The Operation column describes the difference between the two versions and not necessarily the action that was taken by the user. Version comparison example Comparing sets or set versions shows you the differences in set properties and reference values between two reference data sets for versions. In this example, Medical Codes versions 1 and 3 were selected for comparison. Medical Codes Version 1 has three reference values: Value Value Name Ear irrigation Outpatient Visit, Moderate Outpatient Visit, Moderate Medical Codes Version 3 has four reference values: Value Value Name Ear irrigation Chapter 3. Managing reference data with reference data sets 25

32 Value Value Name Outpatient Visit, Low Outpatient Visit, Moderate PHP03 Osseopatite Supplement Organize sets using folders To compare the versions, select Medical Codes (1) and Medical Codes (3) in the Reference Data Set list, and then select Compare. A report is generated, showing the differences in set properties and reference values between the two versions. One value (PHP03) was added and one value was changed (99212). You use folders as an aid for organizing and navigating your reference data sets. You can give the folders meaningful names that suit the context of your work environment, such as named for the project they belong to, the person who created them or a date. Folders can also contain child folders to further help organize your reference data sets. The folders are listed in alphabetical order. If you scroll down the Folder View, any reference data sets that are outside of a folder are listed after the folders. 26 User s Guide

33 Using folders You use the Folder View within the Reference Data Sets tab to view and create folders for organizing your reference data sets. Before you begin Open the Reference Data Sets tab. Procedure 1. If needed, click the Folder View tab. 2. To view the contents of a folder, click the + symbol beside the folder name. The folder expands to show the contents of the folder. 3. To view the versions of a reference data set, click the + symbol beside the reference data set name. Related concepts: Reference data set versions on page 20 Reference data sets support versions. Versions are used to provide a structured approval process for changes to reference data before those changes become active. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Creating folders You create folders to organize reference data sets. Each folder can contain one or more folders or reference data sets or both. Procedure 1. Click the Reference Data Sets tab. 2. If the Folder View is not active, click the Folder View tab. 3. Choose one of the following methods to create a folder: v To create a folder at the root level, click New Folder. v To create a child folder for an existing folder, right-click a folder and select New > Child Folder. v To create a sibling folder to an existing folder, right-click a folder and select New > Sibling Folder. Sibling folders are at the same level as the folder from which they are created. 4. In the Create a Folder dialogue, type the name of the new folder. 5. To save the new folder, click OK. Moving reference data sets into folders You move reference data set into folders when you want to organize or group them by a particular category. Examples of common folder organization are date, user s name or product. Before you begin On the Reference Data Sets tab, open the Folder View and choose the reference data set to move. Chapter 3. Managing reference data with reference data sets 27

34 Procedure 1. Optional: If you want to move a reference data set into a child folder, expand the parent folder by clicking the + symbol beside the folder name. 2. Drag the reference data set and drop it into the new folder. As you drag the reference data set, a moveable box indicates whether the reference data set can be dropped at the location of the cursor. A red bar indicates it cannot be dropped at the current location. A green bar indicates it can be dropped at the current location. Deleting folders You delete folders when you no longer want them. Reference data sets and child folders that were in the deleted folder are moved to the root level. Before you begin On the Reference Data Sets tab, open the Folder View and choose the folder to delete. Procedure 1. Right-click the folder you want to delete. 2. Select Delete. 3. Confirm that you want to delete the folder. Working with reference values Each row in the data set can contain multiple properties, as defined by the data set type, and support a number of different languages. In addition, data values can participate in both mapping and hierarchy associations. Using the graphical user interface, you create, edit and delete the values contained in a data set. You can reduce the number of visible data rows by using the filter option to select a subset of the data. Related concepts: Reference value management on page 20 Reference data sets contain rows of data values, which might be only a few rows or large data sets. Data set size is unlimited by InfoSphere MDM Reference Data Management Hub, but it is normally fewer than 100,000 rows. The data can be managed by the graphical user interface, InfoSphere MDM Reference Data Management Hub data imports, or updates applied by using the batch processor or web services. Creating reference values You create reference values to add rows to a reference data set. 28 User s Guide

35 Before you begin On the Reference Data Sets tab, open the Reference Sets List. Procedure 1. Select a reference data set to which you want to add a value. 2. From the View menu, select Set Values. 3. Enter values for the required fields. Required fields are indicated by an asterisk beside the field name. Other visual cues might also be given. 4. Optional: Enter values for the optional fields as needed. 5. Click Save. 6. Confirm that you want to save the changes. Related concepts: Tree-style hierarchies on page 35 Reference data set hierarchies within InfoSphere MDM Reference Data Management Hub are tree-style hierarchy structures created over the values within a reference data set. You access the hierarchies by using the Set Hierarchies view. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Related reference: Reference value properties on page 60 Every reference data set reference value has a default set of properties in addition to any custom properties that are created in the reference data type. Changing reference values You change reference values when you want to edit existing rows within a data set. Before you begin On the Reference Data Sets tab, open the Reference Sets List. Procedure 1. Select the reference data set and version you want to update. 2. From the View menu, select Set Values. 3. Select the reference value you want to update. 4. On the Properties tab, update the values for one or more properties. 5. To save the changes, click Save. If you do not want to save the changes you made, click Discard. Note: You can change the properties of multiple reference values before saving. Chapter 3. Managing reference data with reference data sets 29

36 Related tasks: Changing reference data sets on page 23 You change a reference data set when you want to edit its properties. Fields that cannot be changed are disabled. Set properties are defined on the Set Level tab for the reference data type. Related reference: Reference value properties on page 60 Every reference data set reference value has a default set of properties in addition to any custom properties that are created in the reference data type. Deleting reference values You delete reference values when you do not want to use them any longer. Data deletion is always handled by a soft deletion mechanism. Data is never physically deleted from the InfoSphere MDM Reference Data Management Hub database on a delete action. Before you begin 1. On the Reference Data Sets tab, open the Reference Sets List. 2. Remove any relationships before attempting to delete a reference value. Procedure 1. Select a reference data set that has reference values you want to delete. 2. From the View menu, select Set Values. 3. Select the reference value to be deleted. 4. Click Delete. Note: Be sure that you click the Delete button that is located within the Reference Value pane. Clicking the Delete button that is in the Reference Sets List pane deletes the reference data set. 5. Confirm that you want to delete the value. Related tasks: Deleting reference data sets or data reference set versions on page 24 You delete reference data sets versions you no longer want. Deleting the only version of a set also deletes the set. Reference data sets cannot be deleted if they are referenced by other sets or mappings. Importing reference values from a CSV or XML file If you have reference data stored in a comma-separated values (CSV) or Extensible Markup Language (XML) file, you can easily import it into a reference data set. Before you begin Make sure that the import file conforms to the appropriate schema. For information, see Schemas for XML import on page 65. About this task When importing values for a set that has a compound key, be sure that the import file contains values that map to each of the custom key properties. 30 User s Guide

37 Procedure 1. Create a reference data set or data set version into which you want to import data. 2. Right-click the reference data set version and select Import from the menu. The Import wizard opens. 3. Choose whether the file you want to import is a CSV or XML file. 4. If you chose CSV as the file format, indicate the separator used in the file. In most cases, CSV files use commas to separate fields, but your file might use a different character. 5. Indicate the wanted date and date/time format. 6. Click Browse and select the file to import. 7. Click Next. 8. For each property in the reference data set, specify the corresponding column from the file. Choose NONE if you do not want to import values for a property. Required keys and required properties must be mapped to columns in the file. Note: You can import rows for a data set that has a compound key formed by using the values from another set. In this case, be sure the additional properties that form the key are included in the import file. 9. On the Preview File tab, review the properties to be imported. Click Back to make any needed corrections to the import mapping at this time. 10. Click Next. 11. Click Finish to begin importing the data. Related concepts: Business keys on page 7 You can create reference data types with compound keys. You can specify up to four properties plus the Code as constituent key parts of a unique reference data value key. Business keys apply only to reference data set data types; mapping set data types do not use business keys. Related tasks: Importing translated reference values on page 33 You can import translated reference values from a comma-separated values (CSV) file. If the reference data set already contains values for the default language, those values are updated during the import. Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Creating reference data set versions on page 22 You create a version of a reference data set when you want to change its properties or its reference values without affecting the existing versions. Related reference: Schemas for XML import on page 65 To import reference data sets, mappings, hierarchies, and reference data types, your XML file must conform to the published schema. Exporting reference values to a CSV or XML file You can export data values to a comma-separated values (CSV) format or Extensible Markup Language (XML) file for import to another data set or use in an Chapter 3. Managing reference data with reference data sets 31

38 external system. You can also define or use export formats when exporting reference values. Export formats save the selected attributes when exporting reference data sets. Before you begin Click the Reference Data Sets tab and choose the reference data set to work with. Procedure 1. Right-click the version you want to export, and choose Export from the menu. The Export wizard opens. 2. Optional: If any export formats were previously saved, you can select one to use. If needed, you can delete unwanted export formats at this time. 3. Click Next. 4. Choose whether to export the data in CSV or XML format. 5. Optional: Make any needed adjustments to the date, time formats, or the time offset. 6. If you chose CSV as the file format, indicate the separator to be used in the file. In most cases, CSV files use commas to separate fields, but you might need a different character. 7. Click Next. 8. Choose the reference data set properties to be included in the export file by highlighting a property in the Available properties list and moving it to the Selected properties list. 9. Choose the reference value properties to be included in the export file by highlighting a property in the Available properties list and moving it to the Selected properties list. The Code and Name properties must be exported. 10. If you want the translated reference values included in the export file, enable Export the value translations. 11. Click Next. 12. If you want to change the name of a property as it is displayed in the export file, click the property name in the Exported Name column and edit it. 13. Click Next. 14. If you want to save the export attributes you chose: v Click Save and overwrite to overwrite an export format you chose in step 2. v Click Save as and provide a name for the new export format. 15. Click Next. 16. If your export is successful, you can download the file to save the exported file, or open it in a browser or file editor. 17. To exit the wizard, click Done. Finding reference values with the advanced filter When a reference data set has many reference values, the advanced filter can help you find the values you want by narrowing the list by specific properties. Before you begin Click the Reference Data Sets tab and choose the reference data set to work with. 32 User s Guide

39 Procedure 1. To open the Advanced Filter dialog, click the filter icon next to the filter text box. 2. Select Advanced Filter... from the menu. The Advanced Filter dialog opens. 3. The Enable advanced filter option is checked by default. If necessary, check this option. 4. Select a property from the Property list. The default and custom value level properties for the set are listed. 5. Select a condition from the list. The conditions vary depending on the data type of the property you selected. 6. Provide a value on which you want to filter the reference values. 7. To add more filter conditions, click the plus (+) icon. 8. To remove a filter condition, click the minus (-) icon. 9. To clear all filter conditions, click Clear All. 10. To apply the filter and continue adding conditions, click Apply. 11. To apply the filter and close the dialog, click OK. 12. To remove an advanced filter, click the filter icon and select Remove All Filters. 13. To apply an advanced filter configured previously, click the filter icon and select Apply. Adding translations to reference values You create translations for a reference value when you want to make the values available in other languages. Before you begin Click the Reference Data Sets tab and choose the reference data set to work with. Procedure 1. Select the version to which you want to add a translation. 2. From the View menu, select Set Values. 3. Select a reference value. 4. Click the Translations tab. 5. Click New. 6. Choose the Language for the translation. 7. In the Translation field, enter the translated text. 8. Optional: Add the Description. 9. Click OK. 10. To save the set with the new translations, click Save. Importing translated reference values You can import translated reference values from a comma-separated values (CSV) file. If the reference data set already contains values for the default language, those values are updated during the import. Chapter 3. Managing reference data with reference data sets 33

40 Before you begin Ensure that non-translated values for each reference value were added to the reference data set before attempting to import translated values. Procedure 1. Create a CSV file that contains the translated values. For information about creating the CSV file, see Creating a CSV file for importing reference value translations. 2. Use the Import utility to specify the CSV file. 3. On the Map File Columns tab under Translations, indicate the columns in the CSV file you want to use for the Language and Value. 4. Step through the rest of the wizard and click Finish. Related tasks: Creating a CSV file for importing reference value translations You import translations of reference values at the same time you import a reference set. To import translations, you must structure the CSV file in a way that the import utility can parse it. Importing reference values from a CSV or XML file on page 30 If you have reference data stored in a comma-separated values (CSV) or Extensible Markup Language (XML) file, you can easily import it into a reference data set. Creating a CSV file for importing reference value translations: You import translations of reference values at the same time you import a reference set. To import translations, you must structure the CSV file in a way that the import utility can parse it. Procedure 1. On the first line of the CSV file, define all of the columns for the file which are to be linked to the various attributes of the reference data set. When importing translated values, you must have at least four columns for each reference value: Code, Name, Language, and Translated Value. 2. Add other wanted columns to import values for custom properties defined by the data set type. 3. On the subsequent lines, add the necessary data for each value. The Language and Translated Value can be null, but Code and Name are required for each row. Code,Name,Language,Translated Value BLUE,Blue,Français,Bleu BLUE,Blue,Deutsch,Blau LTBLUE,Light Blue,, RED,Red,Français,Rouge RED,Red,Deutsch,Rot 34 User s Guide

41 GREEN,Green,Français,Vert GREEN,Green,Deutsch,Grün YELLOW,Yellow,Français,Jeune YELLOW,Yellow,Deutsch,Gelb Note: If the language name in the CSV file does not match any existing language in InfoSphere MDM Reference Data Management Hub, it is not added to the reference value translation table. 4. Save the file with UTF-8 encoding. Related tasks: Importing translated reference values on page 33 You can import translated reference values from a comma-separated values (CSV) file. If the reference data set already contains values for the default language, those values are updated during the import. Reference data set hierarchies The InfoSphere MDM Reference Data Management Hub console supports the creation of two different types of hierarchies over reference data: value hierarchies and tree hierarchies. v v Value hierarchies are defined as relationships between reference data sets defined in the data reference type. Tree hierarchies are defined in the Set Hierarchies view. Tree-style hierarchies Reference data set hierarchies within InfoSphere MDM Reference Data Management Hub are tree-style hierarchy structures created over the values within a reference data set. You access the hierarchies by using the Set Hierarchies view. Actions available from the Set Hierarchies view include: v Save or discard changes to a hierarchy v Select the hierarchy to work on by selecting Set Hierarchies from the View menu. v Create a new empty or pre-populated hierarchy over the values in a reference data set, as described in Creating tree-style hierarchies. v Import a hierarchy definition from a comma-separated values (CSV) file, as described in Importing set hierarchies. A hierarchy structure can be defined between the elements of a set in a CSV file and imported over a set of reference data values. When dealing with hierarchies over a large set of values it is easier to define the hierarchy externally, and create a CSV file to import the hierarchy into InfoSphere MDM Reference Data Management Hub. v Copy a hierarchy v Delete a hierarchy v Refresh the list of hierarchies Note: Each reference value can exist only once within a hierarchy. Chapter 3. Managing reference data with reference data sets 35

42 Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Creating reference values on page 28 You create reference values to add rows to a reference data set. Creating tree-style hierarchies You create tree-style set hierarchies to organize the data within a set. Before you begin On the Reference Data Sets tab, open the Reference Sets List. Procedure 1. Select the reference data set and version you want to work with. 2. From the View menu, choose Set Hierarchies. 3. Click New in the Set Hierarchy panel. The Add a Hierarchy dialog opens. 4. Enter a name for the hierarchy. 5. Select Empty if you want to begin with an empty hierarchy. In empty hierarchies, only the root node is populated. You build the hierarchy one element at a time. Select Pre-Populated if you want to start with a hierarchy that is pre-populated with all the set elements one level under the root. With both options, you can create a hierarchy by dragging and dropping nodes and values. Note: For large sets, it is easier to build a set from the Empty setting. The hierarchy manipulation response is faster when dealing with a small set of unexpanded nodes. When a new empty hierarchy is created, all the reference data set values are initially displayed in the Values section of the user interface. You can highlight one or more values at a time, and then drag them to the hierarchies section of the user interface. 6. Alternatively, you can import a hierarchy if you have a CSV file defining the parent and child nodes. For information about importing hierarchies, see Importing set hierarchies. 7. To remove values from a hierarchy, right-click a value in the hierarchy and select Remove. The selected value is moved to the Values not in hierarchies section. It is not possible to drag or remove entire branch structures in the hierarchy. To remove a higher level node, you must remove all of the children first, starting at the lowest level and working up. 8. To save the hierarchy structure, click Save. Importing set hierarchies A hierarchy structure can be defined between the elements of a set in a comma-separated values (CSV) file and imported over a set of reference data values. When dealing with hierarchies over a large set of values, it is usually easier to create the hierarchy externally within a CSV file and to import the hierarchy into InfoSphere MDM Reference Data Management Hub. Before you begin Create or open the spreadsheet file in which to specify the CSV values to import. 36 User s Guide

43 Procedure 1. For the highest level hierarchy nodes, specify root as the parent. 2. For each row of the CSV file, create two entries: v The code for the parent value. v The code for the child value within the hierarchy. For example, a hierarchy CSV file might have the following entries: Parent.Code,Child.Code root,a A,01 A,01.1 A,01.11 A,01.2 A,01.21 A,01.3 A,02 A,02.01 A,02.02 root,b B,05 B,05.01 root,c C,CA C,CB CA,10 CA, Save the file in CSV format. 4. Click the Reference Data Sets tab. 5. Select the reference data set and version you want to work with. 6. From the View menu, select Set Hierarchies. 7. Click Import. The wizard steps you through the process of naming the new hierarchy and selecting a hierarchy file to upload. Values within the set but not specified within the hierarchy import file are displayed in the Values not in the hierarchy section after the import is completed. Note: Importing into an existing hierarchy is not currently supported. Level-based hierarchies InfoSphere MDM Reference Data Management Hub supports level based hierarchies across multiple sets, where each level of the hierarchy is associated with a different reference data set. An example of such a level-based hierarchy would be city/state/country where city, state, and country are each reference data sets. It is both valuable and meaningful to manage the relationships between the values across the sets. Reference data sets can be linked together by using the reference data set property type. The values from one reference data set can be surfaced as a look-up table within the value properties of a related reference data set. For example, a State reference data set has a property for Country, and this property is of type reference data set. State and country become linked by using the Country reference data set as a lookup table within State values. This linkage creates a value-based hierarchy. The first step in supporting a level-based hierarchy is to create the appropriate reference data set types. The parent s type is designated as a property in the child set. Chapter 3. Managing reference data with reference data sets 37

44 In this example, a user created three reference data set types. The Country data set type is the parent type and has no additional properties. Name Country Type Reference Data Set The user defined a reference data set by using this data type and named it Country. The user then created the State data set type with a property called Country. The Country property is a Reference Data Set type, and the source for the property values is the Country data set. Name State Type Reference Data Set Property 1 Name Country Type Reference Data Set Related Set Country We created another reference data set and named it State. The State set is based on the State data type. When we added values to the State set, we were required to select a Country. Related concepts: Reference data set data types on page 13 When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value. Creating level-based hierarchies You create a level-based hierarchy to link reference data sets together by their reference values. Procedure 1. Select a reference data set to serve as the look-up set. Note: The look-up data set must have a current version. Ensure the three conditions stated in Reference data set data types on page 13 are met, and the data set has all the reference values that you need. 2. Create a reference data type of data type Reference Data Set. 3. Create a value-level property of type Reference Data Set and choose the set designated in step 1 as the Related set. 4. Create a reference data set based on the new reference data type you created in step User s Guide

45 5. Add reference values to the new data set. For the property created in step 3, choose one of the values in the look-up data set. Related concepts: Reference data set data types on page 13 When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value. Related tasks: Creating reference data types for sets on page 8 To define the properties and structure of reference data sets, you create reference data types that use the Reference Data Set data type property. Adding reference data type properties on page 9 You add custom properties to a reference data type to define the columns that are available to any reference data set that uses the reference data type. Reference data set subscriptions Subscriptions form part of the definition of the data distribution model within InfoSphere MDM Reference Data Management Hub. A subscription is an association made between a reference data set and a managed system and this association essentially indicates who the publishers and consumers of the said reference data set are. Hence, it is possible for a reference data set to have many subscriptions, as you have a single publisher and many consumers. Subscriptions are useful when performing import or export operations for the associated reference data set. Your lab services department creates the custom integration see you need to utilize subscriptions. The process for creating these custom integrations is outside the scope of this documentation. Related tasks: Chapter 5, Configuring data providers and consumers, on page 49 You use the managed systems feature to configure the integration with applications and other entities that provide data to InfoSphere MDM Reference Data Management Hub or that subscribe to data exports from InfoSphere MDM Reference Data Management Hub. Creating Subscriptions You create subscriptions to schedule updates to and from the managed systems that provide or consume the reference data. Before you begin Click the Reference Data Sets tab and select a reference data set to work with. Procedure 1. From the View menu, select Set Properties. 2. Click the Subscriptions tab. 3. To create a subscription, click New. A Subscription properties dialog opens where you can define your subscription. 4. Enter values for each property as needed. 5. To close the subscription properties dialog, click OK. Chapter 3. Managing reference data with reference data sets 39

46 6. To save the set with the new subscription, click Save. Related tasks: Creating managed systems on page 49 You create a managed system when you want to configure an entity that provides data to a reference data set or consumes data from a reference data set. Editing subscriptions You edit subscriptions to change the scheduled updates to and from the managed systems that provide or consume the reference data. Before you begin Click the Reference Data Sets tab and choose a reference data set to work with. Procedure 1. From the View menu, select Set Properties. 2. Click the Subscription tab. 3. Select the subscription you want to edit or view from the list. 4. Click Edit. The Subscription Properties dialog opens, where you can refine the subscription. 5. If you want to remove external system activity updates for the selected subscription, click Clear Activity. 6. To close the Subscription Properties dialog, click OK. 7. To save the set with the subscription changes, click Save. To restore the subscription properties to their previous values, click Discard. Deleting subscriptions You delete subscriptions when you no longer want to use them. Before you begin On the Reference Data Sets tab, open the Reference Sets List. Procedure Reference data set history 1. Select a reference data set to work with. 2. From the View menu, select Set Properties. 3. Click the Subscriptions tab. 4. Select the unwanted subscription from the list. 5. Click Delete. The subscription is removed from the list. 6. To save the set with the deleted subscription, click Save. To restore the deleted subscription, click Discard. History data is maintained within the InfoSphere MDM Reference Data Management Hub but cannot be viewed through the InfoSphere MDM Reference Data Management Hub user interface. This function relies on the underlying InfoSphere MDM Custom Domain Hub platform, which records database activity in the history tables managed in the 40 User s Guide

47 InfoSphere MDM Custom Domain Hub database. This data can be retrieved through use of customized database SQL calls. In addition, all InfoSphere MDM Reference Data Management Hub data that is deleted through the user interface is not physically deleted from the InfoSphere MDM Reference Data Management Hub database, but is marked as logically deleted. (This process is often called a soft delete.) Deleted data is not returned through the InfoSphere MDM Reference Data Management Hub inquiry services or user interface, but can be retrieved, for audit purposes, from the InfoSphere MDM Reference Data Management Hub database. Chapter 3. Managing reference data with reference data sets 41

48 42 User s Guide

49 Chapter 4. Relating associated data across reference data sets About data set mappings Creating mappings Mappings can be defined between two reference data sets, and the reference values within those sets, to relate associated data. For example, NACE is the European standard for industry codes, and NAICS is the North American standard. You can map a reference data set that contains NACE codes to one that contains NAICS codes. The mappings browser is where you perform the primary management tasks for mapping sets. With the mappings browser, you create, read, update, and delete a mapping between two reference data sets and map reference values in those data sets. Each mapping has its own metadata, including version and lifecycle state. For instance, the version for a mapping is unrelated to the version of the sets that are being mapped. You can easily locate a map by filtering for the source or target set associated with the map. You create mappings as the first step in associating data between reference data sets. You create mappings from a specific version of a source set to a specific version of a target set. Before you begin Create a reference data set to designate as the source, and another reference data set to designate as the target. Procedure 1. Click the Mappings tab. The mapping browser opens to display any existing mapping sets. 2. Click New. The Create Mapping dialog opens. 3. Select a Source set and Version from an existing reference data set. You can start typing the set name in the field to filter by name. 4. Select a Target set and Version from an existing reference data set. You can start typing the set name in the field to filter by name. 5. Enter a Name for the mapping set. 6. Type the Version designation for this mapping set. 7. Select a Type for the mapping set. The type corresponds to existing reference data types. 8. Optional: Provide values for the remaining fields as needed. 9. Click OK. The mapping properties tab opens, displaying the properties of the mapping. The tab name corresponds to the mapping name you chose earlier. Copyright IBM Corp. 2011,

50 What to do next Mapping reference values Editing mappings See Mapping reference values or Importing mappings on page 45. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Setting the owner on page 50 You set the owner of an object to designate the user groups that can edit it. Mapping reference values You create value mappings as the second step in associating data between reference data sets. You map reference values to associate the reference values in one set with reference values in another set. Related reference: Mapping properties on page 75 Every mapping has a default set of properties that govern its behavior. You create value mappings as the second step in associating data between reference data sets. You map reference values to associate the reference values in one set with reference values in another set. Before you begin Create a mapping to associate two reference data sets. Procedure 1. Click the Mappings tab. 2. Select an existing mapping set and click Edit. 3. In the Value Mappings group box, click New. A new pane opens, where you create manual mappings between reference data values. 4. In the Source Values column, select a source value. 5. In the Target Values column, select the corresponding target value. 6. Click Create Mapping. 7. In the Create Value Mapping dialog, choose the custom properties for this mapping. The properties vary depending on the data type of the mapping. 8. To create a mapping between the two values, click OK. 9. Repeat this process until the wanted values are mapped. 10. When finished, click Save. Related tasks: Creating mappings on page 43 You create mappings as the first step in associating data between reference data sets. You create mappings from a specific version of a source set to a specific version of a target set. You edit mappings when you want to change how data sets or their values are mapped. 44 User s Guide

51 Deleting mappings Procedure 1. Click the Mapping tab. 2. Select an existing mapping set that has reference data values mapped. 3. Click Edit. The mapping opens in a new tab. 4. Make the necessary changes. 5. To change the version of one or both reference data sets in the mapping: a. Click Change Versions. The Change Source and Target Versions dialog opens. b. Select the source or target version to use. c. Click OK. 6. To save your changes, click Save. Related tasks: Setting the owner on page 50 You set the owner of an object to designate the user groups that can edit it. Related reference: Mapping properties on page 75 Every mapping has a default set of properties that govern its behavior. You delete a mapping when you no longer want to associate one reference data set with another. Procedure 1. Click the Mappings tab. 2. Select the mapping you want to delete. 3. Click Delete. 4. Click Delete to confirm you want to delete the mapping. Deleting mappings of reference values Importing mappings You delete a value mapping when you no longer want to associate the value from one data set with a value from another data set. Procedure 1. Click the Mappings tab. 2. Select the mapping in which the unwanted reference data values are referenced. 3. Click Edit at the top of the Mapping Browser. 4. Select the value mapping to be deleted. 5. Click Delete under the Value Mappings section. 6. Click OK to confirm you want to delete the value mapping. Mappings can be defined between reference data sets and the reference data values within those sets to relate associated data in multiple reference data sets. Chapter 4. Relating associated data across reference data sets 45

52 About this task The Import Mappings feature is used to import mappings between reference data values into mapping sets by using a comma-separated values (CSV) file. The import feature can import all data required for a mapping set, including parameters such as custom properties and values for a mapping set of a certain reference data type. Creating a CSV file for importing mappings The following steps describe the correct format for a comma-separated values (CSV) file in order to use it to import mappings. Procedure 1. On the first line of the CSV file, define all of the columns for the file which are later linked to various attributes of the mapping set. There must be a minimum of two columns, which must be linked to the Source Code and Target Code attributes. You can add additional columns to be linked to custom properties defined by the type of the mapping set. 2. On the subsequent lines, define values and properties to be mapped following the order indicated in the columns of the first line. 3. Continue adding to the file until all values are accounted for or all the wanted mappings are defined. For example, when mapping NACE codes to NAICS codes, the CSV file might look like the following: Source.Code, Target.Code 97.00, , , , , , , , , , , , Save the file with UTF-8 encoding. Importing mapped values into mappings You import data from comma-separated values (CSV) files into a mapping to relate associated data in two reference data sets. Before you begin 1. Create a CSV file as described in Creating a CSV file. 2. Create a mapping set as described in Creating mappings on page 43. Procedure 1. Click the Mappings tab and select the mapping you want to work with. 2. Right-click the mapping and select Import... The Import Mappings wizard opens. 3. On the Choose Import File tab, browse for a CSV file to import. 4. Choose the separator used in the file. In most cases, CSV files use commas to separate fields, but your file might use a different character. 5. Indicate the wanted date and date/time format. 46 User s Guide

53 6. Click Next. 7. On the Map File Columns tab, choose the CSV column for each property in the set. The Code property must be mapped. 8. Click Next. 9. On the Preview File tab, review the mappings selected. Click the Errors Found tab, if present, to review any errors found. Make any needed corrections to the mapping at this time. 10. Click Finish to begin importing the data. Note: Any values that were previously mapped in the current mapping are not imported. Exporting mappings to a CSV or XML file You can export mappings to comma-separated values (CSV) or extensible markup language (XML) file for import into other mappings. Procedure 1. Click the Mappings tab. The mapping browser opens to display any existing mapping sets. 2. Find the mapping you want to export. 3. To export to CSV format, right-click the mapping and choose Export > CSV from the menu. A dialog opens, giving you the option of opening the file or saving it. 4. To export to XML format, right-click the mapping you want to export and choose Export > XML from the menu. A dialog opens, giving you the option of opening the file or saving it. Results The export file contains the source and target Code field values for each mapped entry, along with other properties defined for the particular mapping type in the chosen format. Chapter 4. Relating associated data across reference data sets 47

54 48 User s Guide

55 Chapter 5. Configuring data providers and consumers You use the managed systems feature to configure the integration with applications and other entities that provide data to InfoSphere MDM Reference Data Management Hub or that subscribe to data exports from InfoSphere MDM Reference Data Management Hub. About this task Creating managed systems Managed systems are references to external systems which represent the suppliers and consumers of the reference data defined within InfoSphere MDM Reference Data Management Hub. You can set properties for the managed system to enable InfoSphere MDM Reference Data Management Hub and integrated applications to communicate with the managed system. Managed systems are associated with reference data by subscribing to a specific reference data set. Facilities are also provided to configure the managed system to import or export reference data definitions directly from or to the external system. Each managed system can have custom properties that assist your external integration services personnel in providing reference data to external systems. Integrating managed systems requires custom code, which is outside the scope of this documentation. Related concepts: Reference data set subscriptions on page 39 Subscriptions form part of the definition of the data distribution model within InfoSphere MDM Reference Data Management Hub. You create a managed system when you want to configure an entity that provides data to a reference data set or consumes data from a reference data set. Procedure 1. Click the Managed Systems tab, and then click New. 2. Define the properties for your new managed system. 3. To add system properties, click New on the System Properties tab. a. In the Property Source dialog, enter the Property Name and Value. b. Click OK. 4. To save the managed system and its properties, click Save. Copyright IBM Corp. 2011,

56 Related tasks: Creating Subscriptions on page 39 You create subscriptions to schedule updates to and from the managed systems that provide or consume the reference data. Editing or deleting managed systems Setting the owner You edit managed systems when you want to add, edit, or delete the properties used by the external integration services personnel to import or export reference data to or from external systems. You delete managed systems when they are no longer used. Procedure 1. Select the managed system you want to edit from the list of managed systems. The details and associated properties of the selected managed system are displayed. 2. You can change the definitions or properties as follows: a. To add a custom property, click New on the System Properties tab. b. To delete an existing custom property, select the property and click Delete on the System Properties tab. c. To change the Owner settings click Manage Owners and follow the instructions in Setting the owner. 3. To save the changes to the managed system, click Save. To revert changes, click Discard. 4. To delete an unwanted managed system, click Delete above the list of managed systems. You set the owner of an object to designate the user groups that can edit it. Procedure 1. With the object selected, click Manage Owners. The Manage Owner dialog opens. A list of available owner groups is presented with the current settings preselected. 2. Use Add, Remove, Add All, and Remove All to move an owner group to the Available or Selected list box as needed. Members of the owner groups shown in the Selected list box have edit capabilities for the object. 3. Click OK to close the Manage Owner dialog. 4. Save the object as usual. 50 User s Guide

57 Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Changing reference data sets on page 23 You change a reference data set when you want to edit its properties. Fields that cannot be changed are disabled. Set properties are defined on the Set Level tab for the reference data type. Creating mappings on page 43 You create mappings as the first step in associating data between reference data sets. You create mappings from a specific version of a source set to a specific version of a target set. Editing mappings on page 44 You edit mappings when you want to change how data sets or their values are mapped. About importing reference data from managed systems You can use managed systems to import reference data directly into the InfoSphere MDM Reference Data Management Hub repository. Each managed system can have custom properties that assist the lab services personnel in consuming data from internal systems. This requires custom code, which is outside the scope of this document. About exporting reference data to managed systems You can use managed systems to export reference data sets directly to the external system defined by the managed system. Each managed system can have custom properties that assist the lab services personnel in providing reference data to external systems. This requires custom code, which is outside the scope of this document. Chapter 5. Configuring data providers and consumers 51

58 52 User s Guide

59 Chapter 6. Exporting data from the command line With the batch export capability, you can export data from the InfoSphere MDM Reference Data Management Hub without needing to use the graphical user interface. Before you begin Overview of batch export Configure the batch export property file. See "Configuring batch export" in the IBM InfoSphere MDM Reference Data Management Hub Installation Guide. The batch export function can be installed and run from any supported system that has access to the InfoSphere MDM Reference Data Management Hub. The hub can be on the same physical system that is used to perform the export, or it can be on a remote system. Batch export fully supports exporting the following entities: v Data values v Data types v Translation v Mapping v Hierarchies Batch export can produce CSV- or XML-formatted output. The formatted output is compatible with the CSV and XML import and export functions accessible with the user interface. The resource definition and control for batch export is handled with a properties file and command-line options. You use the properties file and command-line options to specify the type and name of the resource that is exported. A log file is created that contains the result of the export and statistics on the number of rows exported. Batch export command parameter options You specify the command-line options when you run the batch export command. The general format of the options for the parameters is: <option>=value where option is one of the following, in lowercase. v rds v rdt (or allrdt) v map v hier v version v state Copyright IBM Corp. 2011,

60 v prop Important: Options on the command line are separated by blank spaces (not commas). Note: If the value includes a space (blank) character, then the value string must be wrapped in double quotation marks ("). For example, rds="my Set". If the value includes a double quotation mark ("), then it must be escaped with a back slash (\) character. For example rds="my \"Quoted\" Set". It is suggested that special characters are not used in data set names. The following tables list the parameters that apply to batch export by type. Reference data set rds Name of the reference data set that is targeted for export. This parameter is required. For example, rds=mydataset version Identifies the version of the data set. This parameter is required. For example, version=3 state Defines the state of the data set. This parameter is required. For example, state=approved prop Path of the properties file. This parameter is optional. For example, prop=c:\projects\batchclient\ RDMBatchExportClient.properties The following is an example of the command parameters for exporting a reference data set. rds=mydataset version=3 state=approved prop=c:\batchclient\rdmbatchexportclient.properties Map map Name of the reference map that is targeted for export. This parameter is required. For example, map=mymap version Identifies the version of the mapping. This parameter is required. For example, version=3 state Defines the state of the mapping. This parameter is required. For example, state=approved prop Path of the properties file. This parameter is optional. For example, prop=c:\projects\batchclient\ RDMBatchExportClient.properties The following is an example of the command parameters for exporting a Map. map=mymap version=3 state=approved prop=c:\batchclient\rdmbatchexportclient.properties 54 User s Guide

61 Hierarchy Hierarchy export also requires the rds parameter. hier Name of the Hierarchy that is targeted for export. This parameter is required. For example, hier=myhierarchy version Identifies the version of the Hierarchy. This parameter is required. For example, version=1 state Defines the state of the Hierarchy. This parameter is required. For example, state=approved prop Path of the properties file. This parameter is optional. For example, prop=c:\projects\batchclient\ RDMBatchExportClient.properties The following is an example of the command parameters for exporting a hierarchy. rds=mydataset hier=myhierarchy version=1 state=approved prop=c:\batchclient\ RDMBatchExportClient.properties Data type rdt Running batch export Exports a single data type. For example, rdt=countrydatatype allrdt Exports all the data types on the server. The value you assign is used to create the.csv,.xml and.log files. For example, allrdt=alldatatypes Related concepts: Batch export results on page 56 The data file and related log file are directed to a subdirectory, depending upon the type of entity that is exported. Related tasks: Running batch export With the batch export capability, you can export data from the InfoSphere MDM Reference Data Management Hub without needing to use the graphical user interface. With the batch export capability, you can export data from the InfoSphere MDM Reference Data Management Hub without needing to use the graphical user interface. Before you begin Configure the batch export property file. See "Configuring batch export" in the IBM InfoSphere MDM Reference Data Management Hub Installation Guide. Before running the batch export utility program, you need: v The name of the data set, data type, map, or hierarchy that is to be exported and the associated version and state information. Chapter 6. Exporting data from the command line 55

62 v The name of the batch export properties file and the path to the file. Procedure 1. Open a command window and change to the directory that was used to install the batch export utility programs. If you copied the RunBatchExport.bat or RunBatchExportClient.sh file to a different directory, then change to that directory. 2. Run the batch export program in the command window, along with the necessary command-line options. v For Microsoft Windows operating systems, the file name is RunBatchExport.bat. v For UNIX operating systems, the file name is RunBatchExportClient.sh. For information about the command-line options for the batch export, see Batch export command parameter options on page Change to the output directory specified in the properties file and view the results. Related reference: Batch export command parameter options on page 53 You specify the command-line options when you run the batch export command. Batch export results The data file and related log file are directed to a subdirectory, depending upon the type of entity that is exported. v v v v Data set information is written to the sets subdirectory Map information is written to the maps subdirectory Hierarchy information is written to the hierarchies subdirectory Data types are written to the Data Types subdirectory For data sets, hierarchies and maps, the output file name is constructed from the resource name, state, and version number. It is appended with a suffix to denote the type of file. For example, exporting version 2 of a data-set MyTest in draft state results in creating a file named MyTest_DRAFT_2.suffix, where suffix is CSV or XML, depending upon the type of export that was requested. For data types, the output file name is constructed from the data type name provided for the rdt parameter, or the value for the allrdt parameter if it was used. It is appended with a suffix to denote the type of file. For example, exporting all data types using the parameter allrdt=alldatatypes results in a file named AllDataTypes.suffix, where suffix is CSV or XML, depending upon the type of export that was requested. Log file contents A log file is created for every request to record the results of the export. If the log file exists, the results are appended to the file, otherwise a new log file is created. A log file entry contains the following information: v Time stamp that shows the time that the export started v The command-line arguments v The options specified in the Properties file v Result of the request, which contains: The path and name of the file that contains the exported data 56 User s Guide

63 The number of rows of data that were exported The log file name follows the same pattern as the data files and is constructed from three pieces of information, which are Resource name, State and Version number, and appended with a suffix of log to denote a log file. For example, exporting Version 2 of a data-set MyTest in Draft state results in creating a log file named: MyTest_DRAFT_2.log. A sample log file contains information similar to this example: [06/10/11 17:59] NEW SESSION STARTED Command line arguments: version = 1 rds = Names_and_Country state = Draft Properties from file: date_format = yyyy-mm-dd max_translations = 10 export_wrapper = " hierarchy_export = list request_lang = 100 requester_name = somename user = tabs timestamp_format = yyyy-mm-dd T HH:mm:ssz target_dir = C:\output\ provider_url = localhost:9082 page_size = 250 export_separator =, format = xml password = ************ requestid = SUCCESS! - Your data has been exported to "C:\output\sets \Names_and_Country_Draft_1.xml". Number of rows exported = 7. Debug Log If the debug option is enabled by setting the debug property value to true, trace information for the data flows between the batch export client and InfoSphere MDM Reference Data Management Hub is recorded in the debug log file. The debug log file is written to the same subdirectory as the normal output files for an export and uses the file name debug.log. Differences between batch export and export from the user interface Generally, batch export and the UI export produce the same results. When exporting to a CSV file, however, there is a difference in how translations are handled. Batch export optimizes its handling of translations. For each entry defined in a data set, batch export exports its data in a single row, including all the associated translations. Entries with multiple translations are handled differently to the UI export, which writes a row for every translation value. Chapter 6. Exporting data from the command line 57

64 For data sets that have a single translation value for data values, the results are compatible, although the column headings in the CSV file are different. The actual number of columns in the file that are reserved for translation values depends on the setting of the max_translations option. Related reference: Batch export command parameter options on page 53 You specify the command-line options when you run the batch export command. 58 User s Guide

65 Appendix. Data and configuration reference Reference data set properties When creating objects in InfoSphere MDM Reference Data Management Hub, refer to the data reference topics for descriptions of the fields. Other reference material, such as descriptions of the properties files, can also be found in this reference. Every reference data set has a default set of properties in addition to any custom properties that are created in the reference data type. The default properties for each reference data set include: Name The name of the reference data set. This property is required. Description A description of the reference data set. This property is optional. Owner The groups that have permissions to access the set. This property is required. Version The version of the reference data set. You can use any value to indicate the version. This property is required and must be unique across the versions of a set. Lifecycle process The lifecycle used by the reference data set. The lifecycle is used by the data administrators to control the versions of reference data sets that are in use. This property is required. For information about lifecycles and states, see Lifecycles and states on page 77. State The current state of the reference data set within the configured lifecycle process. This property is required for all lifecycle processes except Active Editable. Type The reference data type from which the set was created. Reference data types are created on the Administration tab. Review date The date the set is to be reviewed. This property is optional. Effective date The date the set becomes effective. This property is optional. Expiration date The date the set expires. This property is optional. Last update user The last user who updated the set. This information is supplied by the system and is read-only. Last update date The date the set was last updated. This information is supplied by the system and is read-only. Mappings The mappings in which this reference data set is a source or a target set. Copyright IBM Corp. 2011,

66 Subscriptions The relationship between the reference data set and the managed system that represents the publisher or consumer of the reference data set. Subscriptions are optional. Related tasks: Creating reference data sets on page 21 You create reference data sets as the first step in defining your reference data. Each reference data set is based on a reference data type. Changing reference data sets on page 23 You change a reference data set when you want to edit its properties. Fields that cannot be changed are disabled. Set properties are defined on the Set Level tab for the reference data type. Reference value properties Every reference data set reference value has a default set of properties in addition to any custom properties that are created in the reference data type. The default properties for each reference value are: Name The name of the set value. The Name must be unique within the set and is required. Description A description of the reference data set. This property is optional. Code A key for the value. The Code must be unique within the set and is required. Review date The date the set is to be reviewed. This property is optional. Effective date The date the set becomes effective. This property is optional. Expiration date The date the set expires. This property is optional. Sort order The order in which the value appears within the set. This property is optional. Valid values are integers 0 to Leaving the sort order blank gives the value the lowest possible sort priority. Zero is the highest sort priority. Related tasks: Creating reference values on page 28 You create reference values to add rows to a reference data set. Changing reference values on page 29 You change reference values when you want to edit existing rows within a data set. Reference data type properties Every reference data type has a default set of properties that define the base structure of reference data sets. Name The name of the reference data type. This property is required. Description A description of the reference data type. This property is optional. 60 User s Guide

67 Code validation rule The validation rule applied to the Code property for each reference value in the reference data sets with this reference data type. This property is optional for reference data types of type Reference Data Set, and disabled for reference data types of type Mapping Set. Enable business key Enabling this option makes the reference data type a compound key data set type. Compound key reference data types are like other reference data types except that they have one or more key properties. These properties require unique reference values in the sets that are based on this reference data type. The default value is true (enabled). This property is disabled for reference data types of type Mapping Set. Data type Indicates whether the reference data type is for sets or mappings. Reference data sets are based on a reference data type of type Reference Data Set. Mappings are based on a reference data type of type Mapping Set. After the reference data type is saved, this property cannot be changed. This property is required. Related tasks: Creating reference data types for sets on page 8 To define the properties and structure of reference data sets, you create reference data types that use the Reference Data Set data type property. Creating reference data types for mappings on page 15 To define the properties and structure of mappings, you create reference data types that use the Mapping Set data type property. Editing reference data types on page 17 You edit a reference data type when you need to change its properties. Copying reference data types on page 17 You copy a reference data type to easily create a similar one. All values and custom properties are also copied. Custom reference data type properties When you create a reference data type, you can add custom properties, each of which has a set of standard attributes and data type-specific attributes. Standard Attributes Name The name of the custom property. This field is required. Description The description of the custom property. This field is optional. When supplied, this description is provided as the hint text for the property in the data sets or mappings that are based on this data type. Type Any custom properties for the set must also be assigned a data type. The available data types align with the data type for the property s column in the database. String Any character data. The contents of the string can be limited by applying a data expression to validate the content. Text One or more strings, which can contain multiple lines. Integer A whole number in the range -9,000,000,000,000,000 to +9,000,000,000,000,000 Appendix. Data and configuration reference 61

68 Decimal A decimal number in the range, -9,000,000,000,000,000 to +9,000,000,000,000,000 Date A valid date, containing day, month, and year. TimeStamp A two-part value that consists of a valid date and valid time of day. Reference Data Set An existing reference data set. You use this data type when creating a level-based hierarchy. For more information about this data type, see Reference data set data types on page 13. Boolean A value that represents true or false. URL A universal resource locator (URL) string. Values entered into properties of type URL must be properly formed URLs. Important: You must use %20 in place of each space in a URL. For example, instead of typing page.html, type Unique For value-level properties, indicates whether the supplied value must be unique for the set. The default is disabled. Required Indicates whether the property is required. The default is disabled, but Required is automatically enabled if the Key field is enabled. Key Indicates whether the reference value property is a key. The default is disabled. Data type settings The fields in the Data type settings section of the properties dialog vary depending on the data type of the property. Validation rule The validation rule for Strings. This field is optional. For information about validation rules, see Data validation for property types on page 11. Default value The default value for the property in new sets or reference values. This field is optional. Length The maximum length of the value for properties of type String or Text. This field is optional. Related set The specific reference data set for properties of type Reference Data Set. This field is required for properties of type Reference Data Set. 62 User s Guide

69 Related concepts: Reference data set data types on page 13 When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value. Related tasks: Adding reference data type properties on page 9 You add custom properties to a reference data type to define the columns that are available to any reference data set that uses the reference data type. Editing or deleting properties for reference data types on page 10 You can change or delete the custom properties for a reference data type. Adding reference data type properties on page 16 You add properties to a reference data type to define the columns that are available to any mapping that uses the reference data type. Editing or deleting properties for mapping data types on page 16 You can change or delete the custom properties for a mapping data type. Editing reference data types on page 17 You edit a reference data type when you need to change its properties. Copying reference data types on page 17 You copy a reference data type to easily create a similar one. All values and custom properties are also copied. Reference data set data types When you create a data type property of type Reference Data Set that points to a data set in the system, the options available must be from a current version of that set. A current version of the set is required to fill that property in a reference value. The current version of a set is one that meets all of these conditions: v The state is in an approved state for the lifecycle process or state machine. v The effective date is the current date or earlier. v The expiration date is after the current date. If more than one version meets these conditions, the most recent version is considered the current version. Note: The effective date and expiration date for individual reference values are not relevant to the definition of a current version. Example You create a reference data set called Countries, which contains reference values for country names. The State for the Countries data set is Approved. Its Effective date was last month, and its Expiration date is next year. Next, you create a reference data type called Branches, which includes a Value Level property called Country. The data type for the Country property is Reference Data Set, and its Related set is the Countries reference set. Appendix. Data and configuration reference 63

70 64 User s Guide When you create a reference data set called Branches, basing it on the Branches reference data type, the Country property is populated with the values from the Countries data set.

Teamcenter 11.1 Systems Engineering and Requirements Management

Teamcenter 11.1 Systems Engineering and Requirements Management SIEMENS Teamcenter 11.1 Systems Engineering and Requirements Management Systems Architect/ Requirements Management Project Administrator's Manual REQ00002 U REQ00002 U Project Administrator's Manual 3

More information

Contents About This Guide... 5 About Notifications... 5 Managing User Accounts... 6 Managing Companies Managing Password Policies...

Contents About This Guide... 5 About Notifications... 5 Managing User Accounts... 6 Managing Companies Managing Password Policies... Cloud Services Identity Management Administration Guide Version 17 July 2017 Contents About This Guide... 5 About Notifications... 5 Managing User Accounts... 6 About the User Administration Table...

More information

IBM InfoSphere Information Server Version 8 Release 7. Reporting Guide SC

IBM InfoSphere Information Server Version 8 Release 7. Reporting Guide SC IBM InfoSphere Server Version 8 Release 7 Reporting Guide SC19-3472-00 IBM InfoSphere Server Version 8 Release 7 Reporting Guide SC19-3472-00 Note Before using this information and the product that it

More information

IBM. Administration Guide. IBM Emptoris Contract Management SaaS

IBM. Administration Guide. IBM Emptoris Contract Management SaaS IBM Emptoris Contract Management IBM Administration Guide 10.1.2 SaaS IBM Emptoris Contract Management IBM Administration Guide 10.1.2 SaaS ii IBM Emptoris Contract Management: Administration Guide Copyright

More information

IBM Security Identity Manager Version Planning Topics IBM

IBM Security Identity Manager Version Planning Topics IBM IBM Security Identity Manager Version 7.0.1 Planning Topics IBM IBM Security Identity Manager Version 7.0.1 Planning Topics IBM ii IBM Security Identity Manager Version 7.0.1: Planning Topics Table of

More information

Guide to Managing Common Metadata

Guide to Managing Common Metadata IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01 IBM InfoSphere Information Serer Version 11 Release 3 Guide to Managing Common Metadata SC19-4297-01

More information

Community Edition. Web User Interface 3.X. User Guide

Community Edition. Web User Interface 3.X. User Guide Community Edition Talend MDM Web User Interface 3.X User Guide Version 3.2_a Adapted for Talend MDM Web User Interface 3.2 Web Interface User Guide release. Copyright This documentation is provided under

More information

Information Catalog Center Administration Guide

Information Catalog Center Administration Guide IBM DB2 Warehouse Manager Information Catalog Center Administration Guide Version 8 SC27-1125-00 IBM DB2 Warehouse Manager Information Catalog Center Administration Guide Version 8 SC27-1125-00 Before

More information

IBM InfoSphere Master Data Management Version 11 Release 5. Overview IBM SC

IBM InfoSphere Master Data Management Version 11 Release 5. Overview IBM SC IBM InfoSphere Master Data Management Version 11 Release 5 Overview IBM SC27-6718-01 IBM InfoSphere Master Data Management Version 11 Release 5 Overview IBM SC27-6718-01 Note Before using this information

More information

About the P6 EPPM Importing and Exporting Guide

About the P6 EPPM Importing and Exporting Guide P6 EPPM Importing and Exporting Guide October 2018 Contents About the P6 EPPM Importing and Exporting Guide Scope This guide contains information about import and export formats and the process of importing

More information

2 The IBM Data Governance Unified Process

2 The IBM Data Governance Unified Process 2 The IBM Data Governance Unified Process The benefits of a commitment to a comprehensive enterprise Data Governance initiative are many and varied, and so are the challenges to achieving strong Data Governance.

More information

STEP Data Governance: At a Glance

STEP Data Governance: At a Glance STEP Data Governance: At a Glance Master data is the heart of business optimization and refers to organizational data, such as product, asset, location, supplier and customer information. Companies today

More information

IBM FileNet Business Process Framework Version 4.1. Explorer Handbook GC

IBM FileNet Business Process Framework Version 4.1. Explorer Handbook GC IBM FileNet Business Process Framework Version 4.1 Explorer Handbook GC31-5515-06 IBM FileNet Business Process Framework Version 4.1 Explorer Handbook GC31-5515-06 Note Before using this information and

More information

Composer Guide for JavaScript Development

Composer Guide for JavaScript Development IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development GI13-2630-00 IBM Initiate Master Data Service Version 10 Release 0 Composer Guide for JavaScript Development

More information

IBM InfoSphere MDM Inspector User's Guide

IBM InfoSphere MDM Inspector User's Guide IBM InfoSphere Master Data Management Version 11 Release 0 IBM InfoSphere MDM Inspector User's Guide GI13-2653-00 IBM InfoSphere Master Data Management Version 11 Release 0 IBM InfoSphere MDM Inspector

More information

ER/Studio Enterprise Portal User Guide

ER/Studio Enterprise Portal User Guide ER/Studio Enterprise Portal 1.1.1 User Guide Copyright 1994-2009 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights

More information

IBM Atlas Policy Distribution Administrators Guide: IER Connector. for IBM Atlas Suite v6

IBM Atlas Policy Distribution Administrators Guide: IER Connector. for IBM Atlas Suite v6 IBM Atlas Policy Distribution Administrators Guide: IER Connector for IBM Atlas Suite v6 IBM Atlas Policy Distribution: IER Connector This edition applies to version 6.0 of IBM Atlas Suite (product numbers

More information

Talend Open Studio for MDM Web User Interface. User Guide 5.6.2

Talend Open Studio for MDM Web User Interface. User Guide 5.6.2 Talend Open Studio for MDM Web User Interface User Guide 5.6.2 Talend Open Studio for MDM Web User Interface Adapted for v5.6.2. Supersedes previous releases. Publication date: May 12, 2015 Copyleft This

More information

IBM Atlas Suite Developers Guide: Reporting Views. for IBM Atlas Suite v6

IBM Atlas Suite Developers Guide: Reporting Views. for IBM Atlas Suite v6 IBM Atlas Suite Developers Guide: Reporting Views for IBM Atlas Suite v6 IBM Atlas Suite Developers Guide: Reporting Views This edition applies to version 6.0 of IBM Atlas Suite (product numbers 5725-D75,

More information

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide

IBM Proventia Management SiteProtector Policies and Responses Configuration Guide IBM Internet Security Systems IBM Proventia Management SiteProtector Policies and Responses Configuration Guide Version2.0,ServicePack8.1 Note Before using this information and the product it supports,

More information

CyberSource Business Center

CyberSource Business Center CyberSource Business Center CS3-609-06-16-09 Copyright 2009 Harris Connect, LLC. all rights reserved. Reproduction in any form without the express written consent of Harris Connect, LLC. is strictly prohibited

More information

Web logs (blogs. blogs) Feed support BLOGS) WEB LOGS (BLOGS

Web logs (blogs. blogs) Feed support BLOGS) WEB LOGS (BLOGS Web logs (blogs blogs) You can create your own personal Web logs (blogs) using IBM Lotus Notes. Using the blog template (dominoblog.ntf), you create a blog application, such as myblog.nsf, which you can

More information

Vendor: IBM. Exam Code: 000-M86. Exam Name: IBM MDM PIM Technical Sales Mastery Test v1. Version: Demo

Vendor: IBM. Exam Code: 000-M86. Exam Name: IBM MDM PIM Technical Sales Mastery Test v1. Version: Demo Vendor: IBM Exam Code: 000-M86 Exam Name: IBM MDM PIM Technical Sales Mastery Test v1 Version: Demo QUESTION NO: 1 Which of the following does NOT describe Master data? A. Transactional Data and Application-unique

More information

Batch Versions Guide Release 9.2

Batch Versions Guide Release 9.2 [1]JD Edwards EnterpriseOne Tools Batch Versions Guide Release 9.2 E53572-01 October 2015 Describes how to create and process versions of report templates. JD Edwards EnterpriseOne Tools Batch Versions

More information

IBM InfoSphere Master Data Management Version 11 Release 5. IBM InfoSphere MDM Inspector User's Guide IBM SC

IBM InfoSphere Master Data Management Version 11 Release 5. IBM InfoSphere MDM Inspector User's Guide IBM SC IBM InfoSphere Master Data Management Version 11 Release 5 IBM InfoSphere MDM Inspector User's Guide IBM SC27-6720-01 IBM InfoSphere Master Data Management Version 11 Release 5 IBM InfoSphere MDM Inspector

More information

ER/Studio Enterprise Portal User Guide

ER/Studio Enterprise Portal User Guide ER/Studio Enterprise Portal 1.0.3 User Guide Copyright 1994-2009 Embarcadero Technologies, Inc. Embarcadero Technologies, Inc. 100 California Street, 12th Floor San Francisco, CA 94111 U.S.A. All rights

More information

IBM Optim. Edit User Manual. Version7Release3

IBM Optim. Edit User Manual. Version7Release3 IBM Optim Edit User Manual Version7Release3 IBM Optim Edit User Manual Version7Release3 Note Before using this information and the product it supports, read the information in Notices on page 79. Version

More information

IBM Leads Version 9 Release 1 October 25, User Guide

IBM Leads Version 9 Release 1 October 25, User Guide IBM Leads Version 9 Release 1 October 25, 2013 User Guide Note Before using this information and the product it supports, read the information in Notices on page 35. This edition applies to version 9,

More information

Luncheon Webinar Series June 3rd, Deep Dive MetaData Workbench Sponsored By:

Luncheon Webinar Series June 3rd, Deep Dive MetaData Workbench Sponsored By: Luncheon Webinar Series June 3rd, 2010 Deep Dive MetaData Workbench Sponsored By: 1 Deep Dive MetaData Workbench Questions and suggestions regarding presentation topics? - send to editor@dsxchange.com

More information

SAS Web Report Studio 3.1

SAS Web Report Studio 3.1 SAS Web Report Studio 3.1 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2006. SAS Web Report Studio 3.1: User s Guide. Cary, NC: SAS

More information

User Guide. Kronodoc Kronodoc Oy. Intelligent methods for process improvement and project execution

User Guide. Kronodoc Kronodoc Oy. Intelligent methods for process improvement and project execution User Guide Kronodoc 3.0 Intelligent methods for process improvement and project execution 2003 Kronodoc Oy 2 Table of Contents 1 User Guide 5 2 Information Structure in Kronodoc 6 3 Entering and Exiting

More information

IBM Records Manager Version 8.5. Designing a DoD Compliant Solution

IBM Records Manager Version 8.5. Designing a DoD Compliant Solution IBM Records Manager Version 8.5 Designing a DoD 5015.02 Compliant Solution IBM Records Manager Version 8.5 Designing a DoD 5015.02 Compliant Solution Note Before using this information and the product

More information

EMC Documentum My Documentum Desktop (Windows)

EMC Documentum My Documentum Desktop (Windows) EMC Documentum My Documentum Desktop (Windows) Version 7.2 User Guide EMC Corporation Corporate Headquarters: Hopkinton, MA 017489103 15084351000 www.emc.com Legal Notice Copyright 2003 2015 EMC Corporation.

More information

Enterprise Architect. User Guide Series. Model Exchange

Enterprise Architect. User Guide Series. Model Exchange Enterprise Architect User Guide Series Model Exchange How to transfer data between projects? In Sparx Systems Enterprise Architect you can move data between projects using Data Transfer of models to file

More information

Microsoft Windows SharePoint Services

Microsoft Windows SharePoint Services Microsoft Windows SharePoint Services SITE ADMIN USER TRAINING 1 Introduction What is Microsoft Windows SharePoint Services? Windows SharePoint Services (referred to generically as SharePoint) is a tool

More information

CounterACT Reports Plugin

CounterACT Reports Plugin CounterACT Reports Plugin Version 4.1.8 and Above Table of Contents About the Reports Plugin... 3 Requirements... 3 Supported Browsers... 3 Accessing the Reports Portal... 5 Saving Reports and Creating

More information

Version Installation and User Guide

Version Installation and User Guide IBM Cognos 8 Business Intelligence Map Manager Version 8.4.1 Installation and User Guide Product Information This document applies to IBM Cognos 8 Version 8.4.1 and may also apply to subsequent releases.

More information

ZENworks Reporting System Reference. January 2017

ZENworks Reporting System Reference. January 2017 ZENworks Reporting System Reference January 2017 Legal Notices For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights, patent

More information

CA ERwin Data Modeler

CA ERwin Data Modeler CA ERwin Data Modeler Implementation Guide Service Pack 9.5.2 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to only and is subject

More information

EMC Documentum Quality and Manufacturing

EMC Documentum Quality and Manufacturing EMC Documentum Quality and Manufacturing Version 4.0 User Guide EMC Corporation Corporate Headquarters Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Legal Notice Copyright 2012-2016 EMC Corporation.

More information

Nortel Quality Monitoring User Import Guide

Nortel Quality Monitoring User Import Guide NN44480-104 Nortel Quality Monitoring User Import Guide Product release 6.5 and 7.0 Standard 01.04 November 2009 Nortel Quality Monitoring User Import Guide Publication number: NN44480-104 Product release:

More information

Oracle Revenue Management and Billing. File Upload Interface (FUI) - User Guide. Version Revision 1.1

Oracle Revenue Management and Billing. File Upload Interface (FUI) - User Guide. Version Revision 1.1 Oracle Revenue Management and Billing Version 2.6.0.1.0 File Upload Interface (FUI) - User Guide Revision 1.1 E97081-01 May, 2018 Oracle Revenue Management and Billing File Upload Interface (FUI) - User

More information

Content Modeling for Administrators

Content Modeling for Administrators Content Modeling for Administrators Getting Started Guide ImageNow Version: 6.7.x Written by: Product Documentation, R&D Date: September 2016 2014 Perceptive Software. All rights reserved CaptureNow, ImageNow,

More information

IBM. Bulk Load Utilities Guide. IBM Emptoris Contract Management SaaS

IBM. Bulk Load Utilities Guide. IBM Emptoris Contract Management SaaS IBM Emptoris Contract Management IBM Bulk Load Utilities Guide 10.1.2 SaaS IBM Emptoris Contract Management IBM Bulk Load Utilities Guide 10.1.2 SaaS ii IBM Emptoris Contract Management: Bulk Load Utilities

More information

Oracle Cloud Using the File Adapter. Release 17.4

Oracle Cloud Using the File Adapter. Release 17.4 Oracle Cloud Using the File Adapter Release 17.4 E71397-08 October 2017 Oracle Cloud Using the File Adapter, Release 17.4 E71397-08 Copyright 2016, 2017, Oracle and/or its affiliates. All rights reserved.

More information

IBM Initiate Inspector Version 10 Release 0. User's Guide GI

IBM Initiate Inspector Version 10 Release 0. User's Guide GI IBM Initiate Inspector Version 10 Release 0 User's Guide GI13-2604-00 IBM Initiate Inspector Version 10 Release 0 User's Guide GI13-2604-00 Note Before using this information and the product that it supports,

More information

Data Express 4.0. Data Subset Extraction

Data Express 4.0. Data Subset Extraction Data Express 4.0 Data Subset Extraction Micro Focus The Lawn 22-30 Old Bath Road Newbury, Berkshire RG14 1QN UK http://www.microfocus.com Copyright Micro Focus 2009-2014. All rights reserved. MICRO FOCUS,

More information

ForeScout CounterACT. Configuration Guide. Version 5.0

ForeScout CounterACT. Configuration Guide. Version 5.0 ForeScout CounterACT Core Extensions Module: Reports Plugin Version 5.0 Table of Contents About the Reports Plugin... 3 Requirements... 3 Supported Browsers... 3 Verify That the Plugin Is Running... 5

More information

Oracle Financial Services Governance, Risk, and Compliance Workflow Manager User Guide. Release February 2016 E

Oracle Financial Services Governance, Risk, and Compliance Workflow Manager User Guide. Release February 2016 E Oracle Financial Services Governance, Risk, and Compliance Workflow Manager User Guide Release 8.0.2.0.0 February 2016 E65393-01 Oracle Financial Services Governance, Risk, and Compliance Workflow Manager

More information

Getting Started With TPM

Getting Started With TPM Getting Started With TPM About TPM The Oracle Textura Payment Management system (TPM) is an Internet-based construction progress claim submission solution. With the TPM system: Progress claims and supporting

More information

IBM. Database Database overview. IBM i 7.1

IBM. Database Database overview. IBM i 7.1 IBM IBM i Database Database overview 7.1 IBM IBM i Database Database overview 7.1 Note Before using this information and the product it supports, read the information in Notices, on page 39. This edition

More information

ECM Extensions xcp 2.2 xcelerator Abstract

ECM Extensions xcp 2.2 xcelerator Abstract ECM Extensions xcp 2.2 xcelerator Abstract These release notes outline how to install and use the ECM Extensions xcelerator. October 2015 Version 1.0 Copyright 2015 EMC Corporation. All Rights Reserved.

More information

Managing Load Plans in OTBI Enterprise for HCM Cloud Service

Managing Load Plans in OTBI Enterprise for HCM Cloud Service Managing Load Plans in OTBI Enterprise for HCM Cloud Service Copyright 2014, Oracle and/or its affiliates. All rights reserved. 1 Objective After completing this lesson, you should be able to use Configuration

More information

Fusion Product Hub Training Data Governance: Business Rules and Impact Analysis. July 2014

Fusion Product Hub Training Data Governance: Business Rules and Impact Analysis. July 2014 Fusion Product Hub Training Data Governance: Business Rules and Impact Analysis July 2014 Copyright 2014 Oracle and/or its affiliates. All rights reserved. Oracle Confidential Internal/Restricted/Highly

More information

IBM Atlas Suite Users Guide: Data Source Definition. for IBM Atlas Suite v6.0

IBM Atlas Suite Users Guide: Data Source Definition. for IBM Atlas Suite v6.0 IBM Atlas Suite Users Guide: Data Source Definition for IBM Atlas Suite v6.0 IBM Atlas Suite Users Guide: Data Source Definition This edition applies to version 6.0 of IBM Atlas Suite (product numbers

More information

Telelogic Directory Server Product Manual Release 4.3

Telelogic Directory Server Product Manual Release 4.3 Telelogic Directory Server Product Manual Release 4.3 Before using this information, be sure to read the general information under Appendix E, Notices on page 106. This edition applies to VERSION 4.3,

More information

Features and Benefits

Features and Benefits AutoCAD 2005 Features and s AutoCAD 2005 software provides powerhouse productivity tools that help you create single drawings as productively as possible, as well as new features for the efficient creation,

More information

SAS Universal Viewer 1.3

SAS Universal Viewer 1.3 SAS Universal Viewer 1.3 User's Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2012. SAS Universal Viewer 1.3: User's Guide. Cary, NC: SAS

More information

Style Report Enterprise Edition

Style Report Enterprise Edition INTRODUCTION Style Report Enterprise Edition Welcome to Style Report Enterprise Edition! Style Report is a report design and interactive analysis package that allows you to explore, analyze, monitor, report,

More information

What s New in BID2WIN Service Pack 4

What s New in BID2WIN Service Pack 4 What s New in BID2WIN Service Pack 4 BID2WIN Software, Inc. Published: August, 2006 Abstract BID2WIN 2005 Service Pack 4 includes many exciting new features that add more power and flexibility to BID2WIN,

More information

Content Sharing and Reuse in PTC Integrity Lifecycle Manager

Content Sharing and Reuse in PTC Integrity Lifecycle Manager Content Sharing and Reuse in PTC Integrity Lifecycle Manager Author: Scott Milton 1 P age Table of Contents 1. Abstract... 3 2. Introduction... 4 3. Document Model... 5 3.1. Reference Modes... 6 4. Reusing

More information

IBM Security Identity Manager Version Glossary IBM

IBM Security Identity Manager Version Glossary IBM IBM Security Identity Manager Version 7.0.1.3 Glossary IBM IBM Security Identity Manager Version 7.0.1.3 Glossary IBM ii IBM Security Identity Manager Version 7.0.1.3: Glossary Table of contents Glossary..............

More information

Veritas NetBackup OpsCenter Reporting Guide. Release 8.0

Veritas NetBackup OpsCenter Reporting Guide. Release 8.0 Veritas NetBackup OpsCenter Reporting Guide Release 8.0 Veritas NetBackup OpsCenter Reporting Guide Legal Notice Copyright 2016 Veritas Technologies LLC. All rights reserved. Veritas and the Veritas Logo

More information

SAS Clinical Data Integration 2.6

SAS Clinical Data Integration 2.6 SAS Clinical Data Integration 2.6 User s Guide SAS Documentation The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2015. SAS Clinical Data Integration 2.6: User's Guide.

More information

Copyright 2010, Oracle. All rights reserved.

Copyright 2010, Oracle. All rights reserved. Agenda Interactive Dashboards Master-Detail Linking New Prompt Controls Pivot Table Interactions Enhanced Dashboard Builder Analysis Editor Overview Working with the analysis editor step by step Praxisteil

More information

IBM i Version 7.2. Database Database overview IBM

IBM i Version 7.2. Database Database overview IBM IBM i Version 7.2 Database Database overview IBM IBM i Version 7.2 Database Database overview IBM Note Before using this information and the product it supports, read the information in Notices on page

More information

ZENworks 2017 Audit Management Reference. December 2016

ZENworks 2017 Audit Management Reference. December 2016 ZENworks 2017 Audit Management Reference December 2016 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S. Government rights,

More information

IBM Security Identity Manager Version Administration Topics

IBM Security Identity Manager Version Administration Topics IBM Security Identity Manager Version 6.0.0.5 Administration Topics IBM Security Identity Manager Version 6.0.0.5 Administration Topics ii IBM Security Identity Manager Version 6.0.0.5: Administration

More information

DataFlux Web Studio 2.5. Installation and Configuration Guide

DataFlux Web Studio 2.5. Installation and Configuration Guide DataFlux Web Studio 2.5 Installation and Configuration Guide The correct bibliographic citation for this manual is as follows: SAS Institute Inc. 2014. DataFlux Web Studio 2.5: Installation and Configuration

More information

ZENworks 11 Support Pack 4 Endpoint Security Utilities Reference. October 2016

ZENworks 11 Support Pack 4 Endpoint Security Utilities Reference. October 2016 ZENworks 11 Support Pack 4 Endpoint Security Utilities Reference October 2016 Legal Notice For information about legal notices, trademarks, disclaimers, warranties, export and other use restrictions, U.S.

More information

IBM. Mailbox. Sterling B2B Integrator. Version 5.2

IBM. Mailbox. Sterling B2B Integrator. Version 5.2 Sterling B2B Integrator IBM Version 5.2 Sterling B2B Integrator IBM Version 5.2 Note Before using this information and the product it supports, read the information in Notices on page 37. Copyright This

More information

DeltaV Continuous Historian

DeltaV Continuous Historian Frequently Asked Questions Data Analysis Integrated Configuration Scalable Flexible Architecture Contents 1. Introduction 1.1. What is the DeltaV Continuous Historian? 5 1.2. What features are available

More information

EMC Documentum Forms Builder

EMC Documentum Forms Builder EMC Documentum Forms Builder Version 6 User Guide P/N 300-005-243 EMC Corporation Corporate Headquarters: Hopkinton, MA 01748-9103 1-508-435-1000 www.emc.com Copyright 1994-2007 EMC Corporation. All rights

More information

EDQ Product Data Extensions Essentials

EDQ Product Data Extensions Essentials EDQ Product Data Extensions Essentials January, 2015 Contents Part 1 Product Data and EDQ s Product Data Extensions: a Conceptual Overview Part 2 Create a Data Lens Using the Knowledge Studio Part 3 Develop

More information

Veeva Network 18R1.2 Early Release Notes

Veeva Network 18R1.2 Early Release Notes June 2018 Contents About these Release Notes... 4 Browser requirements... 4 What's new... 4 Introduction... 6 Network Customer Master... 6 Widgets... 7 Profile widget... 7 How does it work?... 7 Integration

More information

Oracle Agile Product Lifecycle Management for Process

Oracle Agile Product Lifecycle Management for Process Oracle Agile Product Lifecycle Management for Process Document Reference Library User Guide Release 6.1.1.5 E57817-01 November 2014 Oracle Agile Product Lifecycle Management for Process Document Reference

More information

Enterprise Architect. User Guide Series. Model Exchange. Author: Sparx Systems. Date: 26/07/2018. Version: 1.0 CREATED WITH

Enterprise Architect. User Guide Series. Model Exchange. Author: Sparx Systems. Date: 26/07/2018. Version: 1.0 CREATED WITH Enterprise Architect User Guide Series Model Exchange Author: Sparx Systems Date: 26/07/2018 Version: 1.0 CREATED WITH Table of Contents Model Exchange 3 Copy Packages Between Projects 4 XMI Import and

More information

Specification Manager

Specification Manager Enterprise Architect User Guide Series Specification Manager Author: Sparx Systems Date: 30/06/2017 Version: 1.0 CREATED WITH Table of Contents The Specification Manager 3 Specification Manager - Overview

More information

APPENDIX 4 Migrating from QMF to SAS/ ASSIST Software. Each of these steps can be executed independently.

APPENDIX 4 Migrating from QMF to SAS/ ASSIST Software. Each of these steps can be executed independently. 255 APPENDIX 4 Migrating from QMF to SAS/ ASSIST Software Introduction 255 Generating a QMF Export Procedure 255 Exporting Queries from QMF 257 Importing QMF Queries into Query and Reporting 257 Alternate

More information

IBM. IBM Tivoli OMEGAMON XE for WebSphere MQ. Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. Tivoli. Version 3.7.

IBM. IBM Tivoli OMEGAMON XE for WebSphere MQ. Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration. Tivoli. Version 3.7. Tivoli IBM Tivoli OMEGAMON XE for WebSphere MQ IBM Version 3.7.0 Using IBM Tivoli OMEGAMON XE for WebSphere MQ Configuration SC31-6889-00 12 1 2 Tivoli IBM Tivoli OMEGAMON XE for WebSphere MQ IBM Version

More information

Oracle. SCM Cloud Implementing Product Management. Release 13 (update 18B)

Oracle. SCM Cloud Implementing Product Management. Release 13 (update 18B) Oracle SCM Cloud Release 13 (update 18B) Release 13 (update 18B) Part Number E94178-02 Copyright 2011-2018, Oracle and/or its affiliates. All rights reserved. Authors: Lisa Brown, Venkat Karthik, Mark

More information

econtracts for Tier1 partners COURSE CODE: COE01

econtracts for Tier1 partners COURSE CODE: COE01 econtracts for Tier1 partners COURSE CODE: COE01 April 2017 Introduction Welcome to the econtracts for Partners course. This course provides a brief overview of what the Zebra econtracts Portal is used

More information

BMC Remedy IT Service Management Data Management Administrator s Guide

BMC Remedy IT Service Management Data Management Administrator s Guide BMC Remedy IT Service Management 7.5.00 Data Management Administrator s Guide January 2009 www.bmc.com Contacting BMC Software You can access the BMC Software website at http://www.bmc.com. From this website,

More information

Document Reference Library User Guide

Document Reference Library User Guide Prodika Product Lifecycle Management Document Reference Library User Guide Release 5.1 Part Number: TPPR-0049-5.1A Make sure you check for updates to this manual at the Oracle Documentation Web site Oracle

More information

PRINCIPLES AND FUNCTIONAL REQUIREMENTS

PRINCIPLES AND FUNCTIONAL REQUIREMENTS INTERNATIONAL COUNCIL ON ARCHIVES PRINCIPLES AND FUNCTIONAL REQUIREMENTS FOR RECORDS IN ELECTRONIC OFFICE ENVIRONMENTS RECORDKEEPING REQUIREMENTS FOR BUSINESS SYSTEMS THAT DO NOT MANAGE RECORDS OCTOBER

More information

Teamcenter NX Remote Manager Guide. Publication Number PLM00123 G

Teamcenter NX Remote Manager Guide. Publication Number PLM00123 G Teamcenter 10.1 NX Remote Manager Guide Publication Number PLM00123 G Proprietary and restricted rights notice This software and related documentation are proprietary to Siemens Product Lifecycle Management

More information

Creating Industry Models Change Documents in IDA. IBM Industry Models

Creating Industry Models Change Documents in IDA. IBM Industry Models Creating Industry Models Change Documents in IDA IBM Industry Models November 2014 Contents Identifying Changes to Models... 1 Preparing and Running BIRT Reports for the IDA Logical Data Models Change

More information

Tivoli Management Solution for Microsoft SQL. Statistics Builder. Version 1.1

Tivoli Management Solution for Microsoft SQL. Statistics Builder. Version 1.1 Tivoli Management Solution for Microsoft SQL Statistics Builder Version 1.1 Tivoli Management Solution for Microsoft SQL Statistics Builder Version 1.1 Tivoli Management Solution for Microsoft SQL Copyright

More information

Solution Explorer Guide Release 9.2

Solution Explorer Guide Release 9.2 [1]JD Edwards EnterpriseOne Tools Solution Explorer Guide Release 9.2 E53539-01 October 2015 Describes the Solution Explorer application and discusses the menu design, menu filter, and task launch modes.

More information

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide

IBM Endpoint Manager Version 9.0. Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide IBM Endpoint Manager Version 9.0 Software Distribution User's Guide Note Before using this information and the product it supports,

More information

Oracle Cloud Using the Microsoft Adapter. Release 17.3

Oracle Cloud Using the Microsoft  Adapter. Release 17.3 Oracle Cloud Using the Microsoft Email Adapter Release 17.3 E70297-10 December 2017 Oracle Cloud Using the Microsoft Email Adapter, Release 17.3 E70297-10 Copyright 2016, 2017, Oracle and/or its affiliates.

More information

Creating and Maintaining Vocabularies

Creating and Maintaining Vocabularies CHAPTER 7 This information is intended for the one or more business administrators, who are responsible for creating and maintaining the Pulse and Restricted Vocabularies. These topics describe the Pulse

More information

Data Import Guide DBA Software Inc.

Data Import Guide DBA Software Inc. Contents 3 Table of Contents 1 Introduction 4 2 Data Import Instructions 5 3 Data Import - Customers 10 4 Data Import - Customer Contacts 16 5 Data Import - Delivery Addresses 19 6 Data Import - Suppliers

More information

Oracle Agile Product Lifecycle Management for Process Content Synchronization and Syndication User Guide Release E

Oracle Agile Product Lifecycle Management for Process Content Synchronization and Syndication User Guide Release E Oracle Agile Product Lifecycle Management for Process Content Synchronization and Syndication User Guide Release 6.1.0.1 E27853-01 March 2012 Oracle Agile Product Lifecycle Management for Process Content

More information

Speaker Notes. IBM Software Group Rational software. Exporting records from ClearQuest

Speaker Notes. IBM Software Group Rational software. Exporting records from ClearQuest Speaker Notes IBM Software Group Rational software IBM Rational ClearQuest Exporting records from ClearQuest Updated October 23, 2007 This presentation will cover exporting records from IBM Rational ClearQuest.

More information

Software Requirements Specification. for WAVED. Version 3.0. Prepared By:

Software Requirements Specification. for WAVED. Version 3.0. Prepared By: Software Requirements Specification for WAVED Version 3.0 Prepared By: Sean Bluestein, Kristian Calhoun, Keith Horrocks, Steven Nguyen, Hannah Pinkos Advisor: Kurt Schmidt Stakeholder: Climate Central

More information

CA ERwin Data Modeler

CA ERwin Data Modeler CA ERwin Data Modeler Implementation Guide Release 9.5.0 This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the Documentation

More information

COGNOS (R) 8 COGNOS CONNECTION USER GUIDE USER GUIDE THE NEXT LEVEL OF PERFORMANCE TM. Cognos Connection User Guide

COGNOS (R) 8 COGNOS CONNECTION USER GUIDE USER GUIDE THE NEXT LEVEL OF PERFORMANCE TM. Cognos Connection User Guide COGNOS (R) 8 COGNOS CONNECTION USER GUIDE Cognos Connection User Guide USER GUIDE THE NEXT LEVEL OF PERFORMANCE TM Product Information This document applies to Cognos (R) 8 Version 8.1.2 MR2 and may also

More information

Improving Data Governance in Your Organization. Faire Co Regional Manger, Information Management Software, ASEAN

Improving Data Governance in Your Organization. Faire Co Regional Manger, Information Management Software, ASEAN Improving Data Governance in Your Organization Faire Co Regional Manger, Information Management Software, ASEAN Topics The Innovation Imperative and Innovating with Information What Is Data Governance?

More information

DreamTeam Suite User Guide

DreamTeam Suite User Guide DreamTeam Suite User Guide Product Usage and Best Practices Guide By Adam Buxbaum September 20, 2011 Table of Contents Introduction... 4 Project Manager... 6 Creating Projects... 9 Project Import/Export...

More information