Document Migration via REST API
Update the on-premise server as shown in the below table.
Table 20-79 On-Premise Actions and Commands
| Action | Command |
|---|---|
|
Configure/ Add metadata in AAI_DOC_MIGN_UTIL_REG in CONFIGschema. This table holds application specific configuration details suchas APP ID, Migration Start Time, End Time (ie., Run window),Batch Size (ie., no of records to be picked at a time), numberof threads (ie., how many parallel threads to be spawn), etc,. |
cd$FICDB/bin/ ./docmigrncloudutil.shADD <appId> <infodom> <mign_start_time><mign_end_time> <n_batch_size> <n_threads> ./docmigrncloudutil.shEDIT <appId> <infodom> <mign_start_time><mign_end_time> <n_batch_size> <n_threads> |
| Configure Bearer Token metadata in AAI_DOC_MIGN_PROPERTIESinCONFIGschema |
cd$FICDB/bin/ ./docmigrncloudutil.shPROPMAINT BEARERTOKEN <BEARER_TOKEN_VALUE> <appId> <infodom> |
| Configure Case Status |
cd$FICDB/bin/ ./docmigrncloudutil.shPROPMAINT CASESTATUS <CASE_TOKEN_VALUE> <appId> <infodom> |
| Trigger the Migration Process |
cd$FICDB/bin/ ./docmigrncloudutil.shSTART <appId> <infodom> |
|
Optional: Disable the Migration Process |
cd$FICDB/bin/ ./docmigrncloudutil.shDISABLE <appId> <infodom> |
|
Optional: Enable the Migration Process |
cd$FICDB/bin/ ./docmigrncloudutil.shENABLE <appId> <infodom> |