For Importing Objects
Table 16-3 Details and Descriptions of the Tags and their Attributes
| Tag Name | Attribute | Description |
|---|---|---|
| USERID |
Specify the user ID of the OFSAAI user who will be running the migration utility. Ensure that the user is mapped to the specific target 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 where objects need to be imported. The information domain name should be provided in capital letters. |
|
| FOLDER |
Specify the Code of the folder /segment to which you need to import objects. This field is optional. The folder value should be provided in capital letters. Note: This is the default target folder if object specific TargetFolder is not provided. However, if both FOLDER and TargetFolder are not specified, then source folder available in the exported dump file will be considered as target folder. For behavior in this release, see Limitations section. |
|
| MODE | Set the Mode of the operation as IMPORT. | |
| FILE | Specify the name of the file to be imported, which is present under $FIC_HOME/utility/Migration/metadata/restore folder. | |
| IMPORTALL |
Y indicates that all exported objects in the .DMP file (dump) will be imported (regardless of any specific OBJECT entries in the OBJECTMIGRATION.XML file). Example: <IMPORTALL TARGETFOLDER="BASEG">Y</IMPORTALL> N indicates that only objects explicitly specified in the OBJECTMIGRATION.XML file will be imported (provided they are already exported and available in the dump file). Note: When migrating Sandbox, IMPORTALL should be N. |
|
| FAILONERROR |
Specify whether to fail operation on any error. Y - Stops the import process if there is any error. N - Continues with the next object in the import process even if there is an error. |
|
| OVERWRITE |
Specify whether to overwrite any existing metadata. Y - Overwrites metadata even if the metadata already exists. N - Will not overwrite the object if it already exists and continue migrating the next object. |
|
| RETAIN_IDS |
Specify whether to retain the source AMHM objects after migration. Y – To retain the Source AMHM objects’ System IDs. N – Not to retain the Source AMHM objects’ System IDs. If ‘Y' is selected, different scenarios and the behaviors are as follows: Object and ID does not exist in Target- the object is created in target environment with same ID as that in source. Object exists in Target with different ID- object is migrated and the ID in the target is retained. ID already exists in Target with different object- then the object is migrated to target environment and a new ID is generated. Same object and ID exists in Target- In this case, the behavior depends on the OVERWRITE flag. |
|
| 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 importing all objects of that Type. For example: <OBJECTS> <OBJECT Code="*" Type="112" /> </OBJECTS> To import multiple objects of a particular metadata type, multiple entries with each metadata code should be made in the OBJECTMIGRATION.XML file. For example, if you want to import 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> Note: Specify only those Codes that are present in the exported dump file. To import 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>. |
| Type |
Specify the Type ID of the required metadata objects to be imported. Refer to the Objects Supported for Command Line Migration section. Note: You need to specify only those Types, which are present in the exported dump file. |
|
| 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> |
|
| OBJECTS | TargetFolder |
Specify an optional attribute TargetFolder in <OBJECTS> tag to import objects to a specific folder. Objects can be migrated individually or in groups. Example: <OBJECTS TargetFolder="FSGBSEG"> <OBJECT Code="200143" Type="14"/> </OBJECTS> <OBJECTS TargetFolder="BASEG"> <OBJECT Code="M0001NW" Type="101"/> <OBJECT Code="H0002CRP" Type="103"/> </OBJECTS> Note the following: If you have not specified the TargetFolder, the objects will be imported to the folder specified in FOLDER tag. If you have not provided the default FOLDER value also, then the source folder value in the dump file will be taken as target folder. For Catalog Publish object, the TargetFolder is mandatory. For behavior in this release, see Limitations section. |