Special uses for Life Cycle Management (LCM)
In my previous post, I showed how to use LCM to back up or copy an entire planning application environment. Here I’ll expand on that subject a bit by showing some other uses you may find handy. This is by no means meant to be an exhaustive collection – just a few suggestions you may find useful and which may provoke ideas for other uses.
Copy single dimension from one app to another
This can be done for any dimension, including the standard planning dimensions. Here, to expand on the subject we are also going to export from the “Organization” dim in one planning app & import to the “Entity” dim in another.
Click thru the next screen to this one.
Since we need to change the dimension name, we must export to files, not directly to the other app.
Then click thru the remaining screens to execute the migration.
After the export finishes, go to the \Hyperion\Common\Import_export directory. Under the Username@Directory folder find the files you exported.
In the “info” directory, edit “listing.xml” changing all instances of “Organization” to “Entity”.
Now find the XML file for the dimension to be migrated with name change.
Rename to the target dimension name.
Now edit the file to change “Organization” to “Entity”.
In Shared Services->Application Groups->File System, open the extract and select the (newly renamed) Entity dimension.
...and click thru the remaining screens to execute the migration.
In Shared Services select the artifacts to be backed up and define migration.
We need to back it up to files so type in a folder name...
...and click thru the remaining screens until you get here.
Now, instead of clicking the Execute button, click “Save Migration Definition."
You will get this screen...
Shared Services wants to save “MigrationDefinition.xml” where you tell it to.
You can name the file any name you want (I suggest using naming conventions to differentiate the operation being saved) and anywhere you want.
After saving the file you will get this...
...click “Close” and the backup definition will be saved.
Now look in the Automation folder where the xml file was saved.
The file has everything Shared Services needs to run the backup from the command line utility except the USERID and PASSWORD.
Edit in TextPad or other text editor and type in a Userid and password.
After running the job the password is automatically encrypted.
You should channel the output to a log file so you will have a record of success or failure. The following message is an excerpt from that log which, in turn, lists the detailed log location & name and whether the process was a success or failure and it will also tell exactly where any failure occurred in the process.
I hope I’ve shown you enough to get you started using LCM. It can certainly be a valuable tool, whether you want to do one-time tasks or perform lights-out operations such as regular backups. The important thing to remember is to test it and see what, if any, problems you will have and either fix those or work around them.