EPMExportAll (EPM_CloneExport.bat) is a new Oracle EPM (Hyperion) 184.108.40.206 Lifecycle Management (LCM) command-line utility that exports all LCM-enabled artifacts to the file system. It is very similar, in use and function, to the Lifecycle Management Utility (utility.bat), with a few subtle, yet key differences:
- Unlike the Lifecycle Management Utility (utility.bat), the EPMExportAll utility does not utilize a Migration Definition File to specify which artifacts you want to export. Rather, the EPMExportAll utility grabs all LCM-enabled artifacts by default – whether you want them or not – without specifying a Migration Definition File
- Although the EPMExportAll utility does not use a Migration Definition File, it does require a properties file as input. The properties file does not come installed, so it must be created and named “input.properties” The input.properties file then needs to be populated with the EPM username and password, to be used by the EPMExportAll utility, each time it runs
- The EPMExportAll utility does not accept any command-line arguments. The Lifecycle Management Utility accepts some command-line arguments that can be used to list information or to specify a base path
- While the EPMExportAll utility grabs all LCM-enabled artifacts, it will not grab any artifacts that are not LCM-enabled (e.g., Application Groups ? Foundation ? Deployment Metadata ? Shared Services Registry). The Lifecycle Management Utility (utility.bat) will allow you to select these artifacts
The EPMExportAll utility is executed by running a file called “epm_cloneexport.bat.” This file should be on the Foundation Server, in the Middleware_Home/user_projects/epmsystem1/bin directory (the file may be on a different server and directory, depending on how the installation was done). Here are instructions on how this utility works:
1. Once you’ve located the epm_cloneexport.bat file (in the same directory that the epm_cloneexport.bat file is in), create a blank file and name it input.properties. Open the input.properties file and add the following two lines where mylcmusername and mylcmpassword are the Shared Services credentials for the account that you want the utility to use (Important tip: The password in the input.properties file will be overwritten with an encrypted password during the first run of the utility)
2. Save and close the input.properties file.
3. From a command line, cd to the directory that contains the epm_cloneexport.bat file, and run the following command:
4. When completed, you should see a message that says: “Migration Status: Success.”
5. Exit the command window.
6. In Shared Services, under “File System,” you should now see a folder called EPM_CloneExport. This folder should contain all of the LCM-enabled artifacts.
7. If you go back and open the input.properties file, it should now display the encrypted password (Important tip: At the time that this was written, there appeared to be a potential bug with this utility, whereby the utility created a sort of ad-hoc MDF file, named epmexportall.xml, and put it in the default File System location, alongside the EPM_CloneExport folder. This file contained the unencrypted version of the password from the input.properties file. The file is generated every time the utility is run. We currently have a ticket open with Oracle to see if this is a bug. In the meantime, as a work-around, I am running the utility in a script and having the script delete the epmexportall.xml file after the epm_cloneexport.bat completes):
Author: Ivan Agudelo, Performance Architects