1. Lifecycle Management Guide
  2. Using the Lifecycle Management Utility
  3. Using the Lifecycle Management Utility
  4. Command-line Arguments

Command-line Arguments

[-b]: Specifies the Base Path

The [-b] argument instructs the Lifecycle Management Utility to use the base path relative to where the file system path is set (the file system is the location where all exports and imports are stored).

utility.bat c:/lcm/lcmdefinition.xml [-b path]

The path that is specified can be absolute or relative to the current working directory (it can also include " . " and " .. " relative to an absolute path). If no base path is specified, it uses the directory location of the MDF file (which is not necessarily the directory where the utility exists).

The following are some examples:

utility.bat c:\import_export\HPFullApplicationSuite\Import.xml

utility.bat c:\import.xml -b c:\Oracle\Middleware\user_projects\epmsystem1\import_export\HPFullApplicationSuite

Note:

If the specified path does not exist, Oracle Hyperion Enterprise Performance Management System Lifecycle Management will display an error.

Following are some examples that specify an MDF file residing inside exported content:

utility.bat c:\Oracle\Middleware\user_projects\epmsystem1\import_export\SS1.zip\Export.xml

utility.bat c:\Oracle\Middleware\user_projects\epmsystem1\import_export\SS1.zip\HSS-Shared Services\Import.xml

[-ls]: Lists EPM System Contents

The [-ls] argument lists the artifacts in a migration defined by a migration definition file. It lists the artifacts of both the source and the target system. In an export MDF, for example, the source is the Oracle Enterprise Performance Management System application and the target is the file system.

utility.bat importMDF.xml -ls

utility.bat exportMDF.xml -ls

The resulting output is two files; one for the source and one for the destination:

  • <mdf name>_application name.txt

  • <mdf name>_file system folder name.txt

You can compare the output using a third-party, file-compare utility. This helps to determine the success of the migration.

Output file details:

  • Artifact names

  • Artifact types

  • Path

  • Summary of the content summary

    Sample content summary:

    CONNECTION NAME = AppConnection2
CONNECTION TYPE = Application

APPLICATION RESOURCE DETAILS - 
APPLICATION ID - 1111
PRODUCT NAME - Hyperion Shared Services
PRODUCT CODE - HUB
PRODUCT VERSION - 11.x.x.x
PROJECT NAME - Foundation

TOTAL ARTIFACT: 48
Aggregated Roles  	1     (artifact count by type)
Assigned Roles    	15
Groups            	1
Process Definition	15
Taskflow ACL      	15
Users             	1

The output files are created in the same path as the MDF file and replace any existing files with the same names. You can specify a path for the output files as follows:

utility.sh c:\importMDF.xml -ls -p c:\compare\

For MDF files with multiple tasks, different sets of list structures are created for each task, and the files are prefixed with the task number:

  • <mdf name>_application name_<tasknumber>.txt

  • <mdf name>_file system folder name_<tasknumber>.txt

-ls -ms lists the artifacts which were modified since the last exported time. ls -lmu "username" lists all the artifacts modified by the user in the exported content.

[-ls -ms]: Lists Artifacts Modified Since the Last Exported Time

The [-ls -ms] argument lists artifacts that have been modified in the system since the last migration defined by a migration definition file. These artifacts are listed in Oracle Hyperion Shared Services Console.

For an export MDF file (source = application, target = file system content), [-ls -ms] lists the artifacts whose last modified dates are different in the application from the dates of the artifacts in the file system content.

For an import MDF ( source = file system content, target = application), [-ls -ms] lists the artifacts whose last modified dates are different in the file system from the dates of the artifacts in the application.

Note:

If the modified date for an artifact is not available, the artifact is listed.

utility.bat c:\exportMDF.xml -ls -ms

Output Format in Console:

Artifact Type Artifact Last Modified Date

[-ls -lmu username]: Lists Artifacts Modified by a User in the Exported Content

The [-ls -lmu] argument lists the artifacts modified by a specific user.

For an export MDF file (source = application , target = file system content), the utility matches the modified by name with the artifacts in the file system listing.

For an import MDF ( source = file system content, target = application), the Lifecycle Management Utility matches the modified by name with the artifacts in the product listing.

utility.bat c:\exportMDF.xml -ls -lmu "user"

Output Format in Console:

Artifact Type Artifact Modified By

Note:

If you do not specify a user name, an error is displayed. The user name must be enclosed in quotation marks.