1. Analytical Application Infrastructure User Guide
  2. Command Line Utilities
  3. Command Line Utility to Migrate Objects
  4. Migrating Objects Using OBJECTMIGRATION.xml File
  5. For Exporting Objects

For Exporting Objects

Table 16-2 Details and Descriptions of the Tags and their AttributesTag NameAttributeDescription

Tag Name Attribute Description
USERID

Specify the user ID of the OFSAAI user who will be running the migration utility. Ensure the user is mapped to the specific source Information Domain / Segment.

The user id should be provided in capital letters.

Note: The User ID or Service accounts are “SMS Auth Only” in case of SSO and LDAP configured setups.
LOCALE Set this as en_US.
INFODOM

Specify the Information Domain from where objects need to be exported.

The information domain name should be provided in capital letters.
FOLDER Not Applicable, only used for importing.
MODE Set the mode of the operation as EXPORT.
FILE Specify the name of the dump file which will be created under $FIC_HOME/utility/Migration/metadata/archive folder as a .DMP file.
FAILONERROR Not Applicable, only used for importing.
OVERWRITE Not Applicable, only used for importing.
RETAIN_IDS Not Applicable, only used for importing.
MIGRATION_CODE

Enter the unique migration code to identify the status of the migration process.

For example: 8860
OBJECT Code

Specify the object Code which should be a unique identifier of the definition according to the Type of the object in the Information Domain. Code should be either system generated or user defined unique code. See the Objects Supported for Command Line Migration section to know for a particular object whether it is user defined or system generated.

Note: Object Code is case sensitive.

You can specify the Code value as wildcard “*” if you are migrating all objects of that Type.

For example, to export all Rules from RRF:

<OBJECTS>

<OBJECT Code="*" Type="112" />

</OBJECTS>

To export multiple objects of a particular object type, multiple entries with each object code should be made in the OBJECTMIGRATION.xml file.

For example, if you want to export three different rules, the entries should be made as given below:

<OBJECTS>

<OBJECT Code="Rule Code_1" Type="112" />

<OBJECT Code="Rule Code_2" Type="112" />

<OBJECT Code="Rule Code_3" Type="112" />

</OBJECTS>

To export ETL objects, the format is Data Mapping Code followed by Type=”122”.

For example,

<OBJECT Code="FCTPRODUCT" Type="122" />

Note: Only the latest version will be archived and it will be restored as new version.

To export Enterprise Modeling Objects which supports versioning, the version of the object should be a part of the Code attribute.

<OBJECTS>

<OBJECT Code="ModelID_Version" Type="1305" />

</OBJECTS>

Additionally, if you want to include or exclude a few of the dependent objects, you can set the depType as exclude or include.

<OBJECTS>

<OBJECT Code="BP_Code_1" Type="105”>

<OBJECT Code="Dataset_Code_1" depType="include" Type="104"/>

<OBJECT Code="Measure_Code_1" depType="exclude" Type="101"/>

</OBJECT>

</OBJECTS>
Object Type Specify the Type ID of the required metadata objects to be exported. Refer to the Objects Supported for Command Line Migration section.
SubType

SubType is available for Filters and AMHM hierarchy only. This is a mandatory field.

For filters, SubType indicates the type of the filter. For hierarchies, this indicates the Dimension ID.

See the table for filter SubTypes.

Example: For Group Filter,

<OBJECTS>

<OBJECT Code=”200265" Type="1" SubType=”21”/>

</OBJECTS>
  1. After you have updated the files with required information in the source environment, navigate to $FIC_HOME/utility/Migration/bin path and execute ObjectMigration.sh. The dump file will be created.
  2. Once executed, you can view the related log files from the $FIC_HOME/utility/Migration/logs location.