Incremental application migrations
Updated: 2009-04-30
You can continue to make changes to your business models on your source system after the initial application migration is completed. If you make changes and have tested them to your satisfaction, then you can import these incremental changes to the destination system.
The incremental migration process is similar to that used for first-time migration. Start by exporting from the source system by using the same steps as in first-time application migration. However, with incremental migration, you must lock the destination systems application before you start the import to the destination system. After the import is complete, make certain to unlock the application.
Note
You must be a member of both the global administrator role and the modeler role to execute the migration command. While only the global administrator role is necessary to lock the application and take it offline, the actual incremental migration must be performed by a user who is a member of both the global administrator and application modeler roles.
Important considerations
When you perform an incremental migration, the migration process tries to make the destination system exactly match the source system. Any changes made in the destination system to the migrated information, such as metadata or rules, will be overwritten by subsequent migrations from the source system.
Any matching security roles or form templates will be overwritten with the definition from the source system. However, any new roles or form templates created in the destination system are preserved.
Other information that is migrated is a full synchronization. For example, if a dimension was created in the destination system and then a migration import is performed, that dimension will be removed. The final list of dimensions will exactly match the source system's dimensions.
Procedures
Migrate incremental applications
Perform the usual migration export from the source system by using Planning Command Utility as described in Export the Planning application.
A member of the global administrator role of the target system must use the Planning Administration Console to change the target application status to Async-Offline and then to the Lock status. The target application must be in the locked state to prevent concurrent submissions by other modelers.
At the command prompt, type:
run ppscmd.exe migrate /import /server http://webservices_server_name:portnumber <destination_folder> \ <application_label> .xml
From Planning Administration Console, change the status of the application to Online. This is done by a global administrator.
Download this book
This topic is included in the following downloadable book for easier reading and printing:
See the full list of available books at Downloadable content for PerformancePoint Planning Server.