Migrate HSM policy data using API-based migration

Use the Migration functionality to migrate hierarchical storage management (HSM) migration policy data from a primary tier to a secondary or tertiary tier using API-based migration. This method tightly couples third-party HSM storage systems with Teamcenter. Pending migration file sets are routed through API (user exit) calls to your HSM storage system. The API calls perform the actual migration and commit the changes to the database. Note HSM API-based migration requires tight integration with your third-party HSM system. Procedure Open the Volume Management view. From the Policies tree, select an HSM policy. Click the Migration tab. The policy name and description display at the top of the Migration pane. Verify that the selected policy is an HSM migration policy. The Migration Volumes section displays the tier from which the data is being migrated, and the tier to which it is being migrated. In the Function Options section, click Migration. At the bottom of the pane, click Mark For Migration. Any files defined by the selected migration policy that meet the migration criteria are added to a pending migration request and displayed in the Pending Migration Requests section. Manage the pending migration requests in the list using any of the buttons to the right of the Pending Migration Requests section. Select the pending file request to be migrated and click the Migrate button to the right of the Pending Migration Requests section. The Migration dialog box appears. Select Use Tightly Coupled (API Based) HSM Migration and click OK. Click Yes when the following message appears to indicate you are using a third-party HSM storage system: Copy Has the 3rd party file migration tool been integrated and configured with Teamcenter? The selected data is migrated. A progress indicator displays the migration progress as the APIs perform the file migration and the changes are committed to the database. Note If an error occurs, the current file is rolled back; files from the migration set which have already migrated without error are stored to the database. If you rectify the error and re-select the same pending file set for migration, the second iteration of the migration begins from the current file. After the migration completes, a Migration successful message appears. Click OK.