MicroStrategy Objects Migration (V 9.2.1)

Introduction:

  • MicroStrategy Objects Migration is the Process to migrate or to move objects from one environment to the other environment.
  • For example: The objects developed in the Dev environment will be moved to Testing environment to test and validate the reports/dashboards.
  • Typically the migration will be from Dev to UAT to Production.
  • This will be applicable only after the initialization of project in UAT and Production (i.e. base MD is already uploaded once).
  • In the whole process you will be moving a “.mmp” file of Signed-Off Objects provided to another environment.
  • The activity of MicroStrategy Objects migration can be carried out by using two ways:
    1. Command Line with a simple command using MAImport.
    2. Command Line with a simple command using ProjectMerge.

(Note: The above mentioned ways are applicable wherever we only have OEM license).

 

Import Package through MAImport:

Steps:

1. Paste the “.mmp” file of Signed-Off Objects to be migrated in one of the folders of to UAT or Production Machine.

2. Go to the Directory on Command Line- C:\Program Files (x86)\MicroStrategy as pasted below on UAT or Production Machine.

Note: Assumed MicroStrategy is installed in Program Files (x86). If not, root to the directory where MicroStrategy being installed.

12

 

 

 

 

 

 

3. Now execute the below pasted Command with the proper input Parameters.

MAImportPackage -n  Project Source Name   -u  administrator user name    -p  password -f  “Path of the .mmp file located on Production machine to be moved to Production” –j Project Name

4. Below pasted is an example assuming the fixes.mmp file to be moved to production is present in the location: C:\ProductionPackages9092014\fixes.mmp on Production Machine.

Then the Command to be executed to move the Package “fixes.mmp” will result into

Command: MAImportPackage -n  testserver   -u  administrator -p  xxxxx –f “C:\ProductionPackages9092014\fixes.mmp” –j testproject

The Screenshot is pasted below:

123

5. After typing the Command above in the Command Line Press Enter on the Keyboard,once the Command completes successfully you can exit the window.

1234

6. The MicroStrategy Objects are moved successfully.

7. Since in OEM licence we do not have project access in desktop, so restart MicroStrategy Intelligence server in Services.msc for schema changes to affect.

12345

123456

8. The MicroStrategy Objects Migration is completed.

Note: In this process we cannot generate the Undo Package of the package which we moved from Dev to UAT or Production.

 

Import Package through Project Merge:

Steps:

1. Paste the “.mmp” file of Signed-Off Objects to be migrated and Import.xml in one of the folders of UAT or Production Machine. (Please the the attachment for Import.xml)

2. Edit “Import.xml” and Change the details like (where ever mentioned “<>” in the document for the place holder)

  1.  Server IP,
  2. Project ,
  3. Admin user usually administrator in our case,
  4. Path where the package is available along with package name

3. Now, go to the Directory on Command Line- C:\Program Files (x86)\MicroStrategy as pasted below on UAT or Production Machine.

Note: Assumed MicroStrategy is installed in Program Files (x86). If not, root to the directory where MicroStrategy being installed.

12

 

 

 

 

 

 

4. Now execute the below pasted Command with the proper input Parameters.

ProjectMerge -f “Path of the .xml file located on Production machine to be moved to Production” -sp  “Password of the project source”

5. Below pasted is an example assuming the fixes.mmp file to be moved to production is present in the location: C:\ProductionPackages9092014\fixes.mmp on Production Machine and the C:\ProductionPackages9092014\Import.xml

Then the Command to be executed to move the Package “fixes.mmp” will result into

Command: ProjectMerge –f  “C:\ProductionPackages9092014\Import.xml ” –sp “xxxxxxxx” –SU

The Screenshot is pasted below:

1234567

6. After typing the Command above in the Command Line Press Enter on the Keyboard.

7. A pop up comes with Success message. The MicroStrategy Objects are moved successfully.

12345678

8. Since in OEM licence we do not have project access in desktop, so restart MicroStrategy Intelligence server in Services.msc for schema changes to affect.

12345

123456

9. The MicroStrategy Objects Migration is completed.

Note: In this process we can generate the Undo Package of the package which we moved from Dev to UAT or Production. 

(5 Posts)

My name is Dhanush Nallamothu, and I enjoy meeting new people and finding new ways in key situations. I am dedicated, outgoing, and a responsible team player. People find me to be an upbeat, self-motivated team player with good communication skills. I consider myself a good public speaker, and I have a good sense of humour too.

One thought on “MicroStrategy Objects Migration (V 9.2.1)

  1. Manish Singh

    Hi Guys

    I have about 8 years of experience as SAP BODS administrator and I have been given additional responsibility as MicroStrategy admin. I want to get myself certified in that , but could not find much information on the same. Is there a particular training I need to attend which could help me in getting certified. Any help in this regard would help.

    Thank you
    Manish Singh

Comments are closed.