This tutorial covers upgrading prior versions of Financial Management applications to version 184.108.40.206.0
Approximately 1 hour
This tutorial covers the following topics:
|Upgrading Applications by using the Schema Upgrade Utility|
|Upgrading Applications in Performance Management Architect|
Click icon to show all screenshots
Note: Alternatively, you can click an individual icon (or image) associated with each step to view (or hide) the screenshot associated with that step.
This tutorial covers upgrading prior versions of Financial Management applications to version 220.127.116.11.0. If you want to use applications from prior releases you must upgrade the applications by using the HFM Schema Upgrade utility. If the application is a classic application, you can upgrade it to Performance Management Architect as well.
Your company has upgraded Financial Management to version 18.104.22.168.0, and wants to continue to use its existing applications, which were built in version 9.3.1. You are to upgrade the applications to the current version. Your company uses Performance Management Architect to manage its applications, so the applications must be upgraded in Performance Management Architect as well.
Before starting this tutorial, you should:
Have installed and configured version 22.214.171.124.0 of Financial Management and Performance Management Architect
Have backed up your relational database
Have backed up your Financial Management applications
Have created a Financial Management project to which you want to migrate applications
Know the Shared Services URL and the user name and password of a Shared Services administrator
|6.||Have created a Financial Management application (Apex is used for this tutorial.)|
The Schema Upgrade utility is installed in the Server directory when you install Financial Management, and it runs on the application server. It converts database tables that do not meet the current release specifications. The converted tables account for changes in metadata, data types, and other changes that optimize or enhance Financial Management. It also migrates security users and their roles from the prior release to Shared Services.
When you run the utility, based on your settings, the Schema Upgrade utility sequentially upgrades one application at a time. If it is determined that security needs to be migrated, the migration utility is started on the first instance and used for subsequent applications. It converts the tables and migrates the users from your Financial Management application to Shared Services for all applications.
When you use the Schema Upgrade utility, all applications for the current database are upgraded simultaneously, and the upgrading options apply to all applications. You cannot upgrade only one application.
Navigate to the Financial Management installation directory, and locate the Server directory.
Double-click HFM Schema Upgrade.exe.
The Schema Upgrade Utility starts in a new window.
In the Schema Upgrade Utility window, click Connect.
A list of applications that are available to be upgraded is displayed.
Under Error Handling, select an option:
Under Logging Options, perform the following actions:
a. Select an option:
b. In the Log File Name box, enter an upgrade error log name in a directory of your choosing.
Review the system warning that all applications will be converted, and click Yes to continue.
In the User Migration dialog box, enter the following information to provision the application and click OK:
When the upgrade process is completed, click OK.
Optional: To view the error log after upgrading, perform the following actions:
a. Click View Log.
b. Review the error log, and click X to close it.
Click Close to close the Schema Upgrade Utility.
After converting applications by using the Schema Upgrade utility, you run the Application Upgrade for Performance Management Architect. Classic applications can be upgraded to Performance Management Architect.
If you are not using Performance Management Architect, you work with applications by using Classic Application Administration. If you upgrade an application created in Classic Application Administration to Performance Management Architect, you can no longer work with that application in Classic Application Administration.
Log on to Workspace with username trnadmin and password hyperion.
Select Navigate > Administer > Application Upgrade.
Review the Welcome page, and click Next.
Review the Application Summary information and click Next.
The Application Summary page displays the applications which the user can upgrade (this information is provided from the Shared Services server. If an application cannot be upgraded, an explanation is provided.)
On the Application Selection page, select the applications that you want to upgrade, click the right arrow to add them to the Application to Upgrade list, and click Next.
Review the Upgrade Summary, and click Finish to execute the upgrade.
Review the Application Upgrade task in the Job Console and verify that it was completed successfully.
Select Navigate > Administer > Application Library.
Confirm that the upgraded application is displayed in Performance Management Architect.
Select Navigate > Administer > Dimension Library.
Confirm that the dimensions for the upgraded application were added to Performance Management Architect.
Select Navigate > Applications > Consolidation > APEX to open the application.
Confirm that the application opens successfully in Workspace.
You have successfully upgraded an application!
In this tutorial, you learned how to:
|Upgrade an application by using the Schema Upgrade Utility|
|Upgrade an application in Performance Management Architect|
To learn more about Financial Management, refer to additional OBEs.
More Middleware Downloads