Data Mediation › Configure the Repository Agent › Profile XML File Format

Profile XML File Format

To generate a profile from an external source, use the format in the sample profile XML file. This file resides in the USM_HOME\repagent\data\samples folder.

The profile XML file used by the repository agent to create a Data Mediation profile contains two sections:

Profile section

Contains information about the data mediation profile. Only one profile section can exist for each XML file.

• profile_name - the profile name (mandatory).
• profile_type - the profile type where 0=reference, 1=metric (default is 0).
• import_format - the format of the data source where 0=delimiter-separated file, 1=fixed length file (default is 0).
• field_separator - the delimiter between fields in the usage file. Valid values are either the character itself or the ASCII numeric value for the following characters: ampersand (&), asterisk (*), at sign (@), comma (,), dollar sign ($), exclamation mark (!), percent (%), period (.), pipe (|) or space ( ). In addition, the ASCII numeric value for a tab may be used.

Field section

Contains information about each column of the data file. You can use this section to create the fields in the Data Mediation profile. Each XML file can contain many field sections.

• field_name - database table column name (mandatory)
• display_name - display name of the field
• mandatory - mandatory status
  • 0 - neither server nor client mandatory
  • 1 - server mandatory
  • 2 - client mandatory
  • 3 - both client and server mandatory
• data_type - data type
  • 0 - string
  • 1 - integer
  • 2 - float
  • 3 - date
  • 4 - decimal
  • 5 - double
  • 6 - binary

    Note: A data type of “double” is converted to “float” during import.

• data_length - the length of this field
• data_format - the format of date data (only if data_type =3).

  A slash (/) can be replaced by a dash (-) in the formats shown below. The separator between the date and time portion can be a slash (/), dash (-) or space. Upper or lower case letters can be used. For example, YYYY-MM-DD hh24:mi:ss is a valid format.

  • MM/DD/YY
  • MM/DD/YYYY
  • MM/DD/YYYY HH:MI:SS
  • MM/DD/YYYY HH24:MI:SS
  • MM/DD/YYYY HH:MI:SS.MSS
  • MM/DD/YYYY HH24:MI:SS.MSS
  • DD/MM/YY
  • DD/MM/YYYY
  • DD/MM/YYYY HH:MI:SS
  • DD/MM/YYYY HH24:MI:SS
  • DD/MM/YYYY HH:MI:SS.MSS
  • DD/MM/YYYY HH24:MI:SS.MSS
  • YY/MM/DD
  • YYYY/MM/DD
  • YYYY/MM/DD HH:MI:SS
  • YYYY/MM/DD HH24:MI:SS
  • YYYY/MM/DD HH:MI:SS.MSS
  • YYYY/MM/DD HH24:MI:SS.MSS
• default_value - the value for this field. The Catalog system uses this value, not the input record.
• start_position - if import_format=1 (fixed length file), start_position is the starting position of the field in each record, starting at 1. If import_format=0 (delimiter-separated file), it is the field position starting with 1.

  For example:

  • For a fixed length file, a record contains “abc001” and this field is the numeric portion. Therefore, the start_position is 3, and the end_position is 6.
  • For a delimiter-separated file, a record contains “abc,001” and this field is the numeric portion. Therefore, the start_position is 2, because this field is the second field. Also, the end_position is blank.
• end_position - required only when import_format=1. It is the ending position of a field in each record.
• status - status of the field (default is 1)
  • 0 - system (cannot delete)
  • 1 - active
  • 2 - inactive