Object Migration export tips
You can use these tips to better understand the Object Migration export process.
| Object Migration area | Tip |
| Messages panel | Check the Messages panel for the status of the Object Migration process. |
| Navigation panel | When you click Objects in
the Navigation panel, the Objects panel
displays everything in the package. When you select one of the object types, the Objects panel displays everything in the package about that Object Type; for example, business objects might display triBuilding, triProperty, or triProposedSite. |
| Navigation panel hierarchy | To help the existing hierarchy load faster when
you reopen an existing Object Migration package, all folders in the Navigation panel
are initially closed. You do not need to expand the nodes to see the objects. When the hierarchy is loaded, click any folder name and view its objects in the Objects panel. |
| Object Migration page | The layout properties for the Object Migration panels are saved as cookies in your browser. If you sign on to another computer, you inherit the properties set up by the user of that computer. One way to reset the layout to the as-delivered default is to click Reset. |
| Record Data | If you are searching for Record Data, you must select a module. If you see a message, Nothing found, it is likely because a module is not selected. The Record Data display shows to which business object the Record Data belongs. Use the Record Data object type only for moving setup data, templates, and other items that are imported once and used as a template thereafter. Object Migration is not meant to move data from one environment to another, including data in work task templates and user message records. For supported tools that move data from one environment to another, see Integrating data with external applications |
| Dictionary Record Data | Use the Globalization Manager instead of Object
Migration to export and import Dictionary (triDictionaryEntry) record
data. If you choose to use Object Migration, make sure to remove existing Dictionary records from the target environment before you import the package that contains your Dictionary records. The Dictionary record name is mapped from a control number. The control number sequence in the source environment might not match the sequence in the target environment; therefore, duplicate records might occur on import. |
| Group overrides | In Navigation Builder, you can set a group override
to hide navigation items in navigation collections from users in a
security group that you designate. You can also set a navigation item
to contain a specific target for a security group. Group overrides are exported as part of the navigation collections with which they are associated. In previous releases, group overrides are exported with their associated security groups. |
| Security groups | Security group members are not included in the export process. |
| User Activity | Do not allow users to access the IBM TRIRIGA environment while you are processing Object Migration packages. User activity might result in data corruption or locked tables. |
| Workflows | When you search for workflows, the results include
all workflows regardless of their status. If a workflow is under revision,
the last published or retired version is exported. When you add retired workflows to the Object Migration package and import them to another environment, the workflows are automatically retired in the target system. |