Copy as Performance Management Architect When Source Application Exists at Target

  To copy an application:

1. From the Shared Services console, navigate to the LCM Artifacts List and select Export to File System.

2. Using the LCM Migration Wizard, select the options and export the file to the file system. The Migration Definition XML with all selected artifacts is extracted to the specified file system.

3. Import the Migration Definition file from the file system to the appropriate application, selecting the Merge or Replace Artifacts option (applicable only for dimensions).

   The Merge option allows any artifacts that exist in the target destination, but not in the source, to be included in the target application.

   The Replace option creates the target application as a copy of the source but may affect other applications on the target Performance Management Architect system that use those shared dimensions.

4. After the Import process ends successfully, the Target application is updated with the artifacts from the Source application. You can now start the copy application process.

5. Ensure that the Source and Destination Financial Management servers are not running.

6. Navigate to the directory where the Copy Application utility is installed and double-click HFMCopyApplication.exe.

   Note:

   The default location is the Server directory of your Financial Management installation.

7. At the Welcome screen, click Next.

8. Click to locate the Source database connection file for the application that you want to copy and click Next.

   After successful validation of the Source database connection, the utility displays the Source applications (Classic and Performance Management Architect).

9. From the list of applications, select an application to copy and click Next.

10. At the prompt “This is an EPM Architect application. Do you want to convert it to a Classic Administration application?”, click No.

11. A warning message is displayed, advising that prior to copying the application, you must perform an LCM migration of the artifacts related to the application. Perform an action:

    • If you have not performed the LCM migration, click No and complete that procedure first.

    • If you have performed the LCM migration, click Yes to continue.

12. Click to locate the destination database connection file (UDL) and click Next.

13. From the application list, select the application to which you want to copy or enter a new application name and click Next.

14. On the Options panel, select options and click Next.

    • Copy Application Data to copy data from the source application to the destination application. This generates an identical copy of the source application.

    • Copy Audit Data to copy task and data audit data from the source application to the destination application.

    • Copy Cluster Settings to copy cluster information from the source application to the destination application.

    • Overwrite Existing Application (if it exists) to overwrite an application of the same name as the destination application.

      • Drop All application tables prior to copy

      • Only drop tables that are being copied

    • Optional: Click Advanced Options for additional options.

    1. Modify these values as required:

       • Use Client-side Cursor or Use Server-Side Cursor

       • Use SQL Binding

       • Use default thread count or Use custom thread count

       • Log SQL errors

       • Number of task retries

    2. Click OK to close the Advanced Options box.

15. Confirm the settings and click Next.

16. When the copy process completes, click OK.

17. To view a task detail in Completed tasks or Failed tasks (if any), double-click the task or select the task and click the question mark (?) icon.

18. Click Close.

19. Click Finish to exit, or View Log File to view the log file and see errors that occurred during the copy operation.

    Note:

    An improperly sized Oracle instance can cause the utility to fail to copy all table rows. If the error log displays an Oracle issue, or table rows are missing, you may need to increase the size of the REDO logs.

20. Log in to the target Performance Management Architect Application Library.

21. The newly updated application has a status of “Out of Sync with deployed application.” Redeploy the application.