EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB14912: How to execute a Project Merge from the command line in MicroStrategy 9.x


Stefan Zepeda

Salesforce Solutions Architect • Strategy


This technical article describes project merge command line execution in MicroStrategy 9.x

A Project Merge routine can be launched from the Microsoft Windows command prompt. Users can also run several sessions of the Project Merge Wizard with the same source project.
The settings for this routine must be saved in an XML file which can easily be created using the Project Merge Wizard. Once created, the XML file servers as the input parameter to the command.
A sample command using this syntax is provided below. The command assumes that 'test' is the password for all of the project source and database connections. The login IDs used with these passwords are stored in the XML file created by the Project Merge Wizard. The sample command would resemble the image below:
 

ka02R000000kX55QAE_0EM440000002FL8.jpeg


projectmerge -fc:\temp\merge.xml -sptest -dptest -smptest -dmptest -MD -SU

 

The path to the XML file cannot contain spaces. For example, c:\program files\xml\merge.xml is invalid. The short name of directories can be used, for example c:\progra~1\xml\merge.xml, or the entire path can be placed in double quotes, for example "c:program files\xml\merge.xml".
 
To run multiple sessions of the Project Merge Wizard with the same source project, users must make the following changes to the XML file:
 
Under OMSettingsOnOff, add the following:
 
<SkipProjectMergeSourceLockingSkipProjectMergeDestConfigLocking/>
NOTE: Make sure that the Project Merge log file names are different in each XML file. Also make sure to note that this will not work or take affect if configuration objects are being brought over with the merge such as Database Instances.
 
All command line parameters are described below:
 

  • -f[] - Specifies the path and file name, but note that it is without spaces of the XML file to use. Users must have already created the file using the Project Merge Wizard. Example: -fc:\files\merge.xml
  • -sp[] - Password for Source Project Source. The login ID to be used is stored in the XML file. Example: sptest
  • -dp[] - Password for Destination Project Source. The login ID to be used is stored in the XML file. Example: dptest
  • -smp[] - Password for Source metadata. The login ID to be used is stored in the XML file. Example: -smtest
  • -dmp[] - Password for Destination metadata. The login ID to be used is stored in the XML file. Example: -dmtest
  • -sup - Suppress progress windows. This is useful for running a project merge in the background, and the windows displaying status of merge do not appear.
  • -MD - Forces metadata update of Destination metadata if it is older than the Source metadata. Project Merge will not execute unless Destination Metadata is more recent.
  • -SU - Updates the schema of the Destination project after the Project Merge is completed.
  • -h - Displays help and explanations for all of the above parameters.

Comment

0 comments

Details

Knowledge Article

Published:

April 10, 2017

Last Updated:

April 10, 2017