Upgrading Oracle® Hyperion Financial Close Management 11.1.2.3.000 to 11.1.2.4.000 (Single-node set up)
Overview
Purpose
This tutorial covers upgradation of Financial Close Management from 11.1.2.3.000 to 11.1.2.4.000.
Time to Complete
Approximately 6 hours.
Introduction
In this tutorial, you upgrade the components installed for Financial Close Management PS3.
Prerequisites
Before starting this tutorial, you should:
- Have Financial Close Management PS3 installed & properly working
- Have access (with sysdba privileges) to an Oracle 11g ( 11.1.0.7 or higher) database or MS SQLServer 2008
- Oracle Hyperion Enterprise Performance Management System Installer Release 11.1.2.4.000
- Oracle Hyperion Foundation Services Release 11.1.2.4.000
- Oracle Hyperion Financial Close Management Release 11.1.2.4.000
- Have access to below SOA patches:
- 17014142
- 17440113 - download patch for SOA version 11.1.1.7.1
Upgrade Sequence
- Install PS4
- Configure EPM
- Validation and Starting FCM
- 17014142
- 17440113 - download patch for SOA version 11.1.1.7.1
Installing EPM Components
To install the EPM components, you run the Oracle Hyperion Enterprise Performance Management System Installer. Foundation Services and Financial Close Management are required components. If it is not already present, WebLogic is installed as part of the Foundation Services installation. You configure EPM components after you install and configure the SOA Suite.
- Navigate to the installation folder for the EPM software and run installtool.cmd.
-
Select a language, and click OK.
On the Welcome screen, click Next.
On the Destination screen, select the location for the Middleware Home directory, and click Next. The default directory is c:\oracle\middleware.
-
On the Installation Type screen, select Apply maintenance release and click Next.
On the Product Selection screen, select Foundation Components under Foundation Services, Financial Close Management, FDM Enterprise Edition, (“Oracle Database Client-32 bit”, “Oracle Database Client-64 bit” under Foundation Services & Financial Management SDK under Financial Management will be auto-selected) and click Next.
On the Confirmation screen, click Next.
On the Summary screen, click Finish.
Apply SOA patch 17014142
NOTE: This patch upgrades SOA to level 11.1.1.7.1
To apply the patch follow instructions given in the readme file of the patch.
Apply SOA patch 17440113
NOTE: This patch fixes a SOA bug. Please make sure that you downloaded patch for SOA version 11.1.1.7.1
To apply the patch follow instructions given in the readme file of the patch.
Configuring EPM Components
The database schemas for the EPM components are created during the configuration process.
During the configuration process you must provide valid Oracle/ MS SQLServer database user names and passwords under which to create the schemas. You perform the Deploy to SOA configuration task after you restart WebLogic Server.
Configuring Foundation Services, Financial Close Management and FDMEE
-
From the Windows Start menu, select Programs, EPM System Configurator (all instances).
(You can also start it with configtool.bat. For example: C:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat). -
Accept the defaults, and click Next.
-
Accept the default options under Hyperion Foundation and Financial Management. For any products under Financial Close Management and FDM Enterprise Edition, select Deploy to application server and Configure Database. Do not select Deploy to SOA. Select Configure Content Management System location only if you are using a content management system. Click Next.
-
Accept the default options for Shared Services and Registry Database. Connect to previously configured Shared Services database is selected by default and DB details are fetched from the PS3 installation.
Example for Oracle Database:
- Server: Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
- Port: 1521;
- Service Name or SID: The database service name that you must use is available in C:\app\<user>\product\11.2.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora;
- User Name: fcm
- Password: welcome1
Example for MS SQLServer Database:
- Server:Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
- Port: 1433;
- Database Name : FCMdb
- User Name: fcm
- Password: welcome1
-
You will see the database connection details that were provided in Shared Services database connection details screen. Verify the connection details for the Financial Close Management and FDM Enterprise Edition database, and click Next.
Example for Oracle Database:
Example for MS SQLServer Database:
Select Deploy web applications to an existing domain, enter the information for the WebLogic domain that you created when you configured SOA, and click Next.
Administrator User/Password: use the WebLogic administrator username and password created from SOA configurator.
Domain Name: base_domain (use the existing domain that was created from SOA configurator)
Make sure the option ‘Deploy the Java web applications to single managed Server’ is unchecked and accept the default application server deployment settings, and click Next.
-
Under Configure WebServer, select Oracle HTTP Server and click Next.
-
If you want to integrate Oracle Enterprise Content Management with your Financial Close Management application, enter the URL for Oracle Enterprise Content Management, and click Next.
Review your selections, and click Next to launch the configuration.
When the configuration is complete, click Finish.
Deploying to SOA
After configuring EPM products, you need to run the EPM System Configurator again to deploy to SOA.
-
Ensure that both Admin and SOA server are running before you start the EPM configurator
To start the WebLogic Admin Server, select Start, then Programs, then Oracle WebLogic,then User Projects, then <domain>, and then Start Admin Server for Weblogic Server Domain, where <domain is the WebLogic domain you created with the SOA configuration tool.
(You can also start it with startWebLogic.cmd. For example: C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd)
Enter the Web Logic admin user name and password if prompted.
The process will take few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt box.To start the SOA managed server, enter the following command at a Command Prompt:
c:\oracle\middleware\user_projects\domains\<domain>\bin\startManagedWeblogic.cmd soa_server1,
where <domain> is the WebLogic domain you created with the SOA configuration tool.
When prompted, enter the Web Logic admin user name and password.
The process will take a few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt box. -
From the Windows Start menu, select Programs, then Oracle EPM System, and then EPM System Configurator (all instances).
(You can also start it with configtool.bat. For example: C:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat). -
Select EPM Oracle instance to which this configuration would be applied, and click Next.
-
Expand Financial Close Management select Deploy to SOA and click Next.
Ensure that none of the options under Hyperion Foundation are selected.
-
On the Confirmation screen, click Next to launch the configuration.
-
When the configuration is complete, click Finish.
Starting the Servers
You must start the servers required for Financial Close Management in the following order:
- WebLogic Admin Server
- Foundation Services managed server
- SOA managed server
- Financial Close Management Managed server
Note: Wait until each server status changes to RUNNING state to go to next server in the sequence.
Refresh the page to get the server started status.
To start the WebLogic Admin server, select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, and then Start Admin Server.
Note: You can also start it with startWebLogic.cmd. For example; C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd).
When prompted, enter the WebLogic admin user name and password.
The process will take a few minutes and is complete when you see '<Server started in RUNNING mode>' in the command prompt box.-
To start Foundation Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then Foundation Services, and then Start Foundation Services.
Note: You can also start it with startFoundationServices.bat. For example C:\Oracle\Middleware\user_projects\epmsystem1\bin\startFoundationServices.bat). To start Financial Close Management Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then Financial Close, then Start FinancialClose.
Note: (You can also start it with startFinancialClose.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\startFinancialClose.bat).To start the SOA managed server , enter the following command at a command prompt:
c:\oracle\middleware\user_projects\domains\<domain>\bin\startManagedWeblogic.cmd soa_server1
where <domain> is the domain you created using the SOA configuration utility.
When prompted, enter the WebLogic admin user name and password.
The process will take a few minutes and is complete when you see '<Server started in RUNNING mode>' in the command prompt box.
Running the Validation Tool to Verify Close Manager and Account Reconciliation Manager Configuration
Perform the procedures below to validate the configuration.
Validating Close Manager Configuration
-
From a Web browser, open the following URL : http://<FCMHOST>:<FCMPORT>/fcc/faces/oracle/apps/epm/fcc/ui/page/FCCValidation.jspx.
- Where FCMHOST is the name of the machine where FinancialClose0 managed server is configured.
- Where FCMPORT is the Listening port of FinancialClose0 managed Server in the WebLogic console.
-
Log on to Close Manager with Shared Services administrator credentials.
Note:
If an external provider is configured, the login can also be done with a user from the external provider. But if there are issues with external provider configuration, the login may not succeed. In such cases, you can log on with any seeded user (seeded both on WLS and HSS native directory) and run the tool to identify issues with external provider configuration.
Example to seed “admin” user (who is the default administrator in Shared Services) in WebLogic (this way, you can use the admin user to login to the validator): After successfully logging on the following screen is displayed.
-
To validate the close manager configuration, click on “Validate Close Manager Configuration” button.

After validation, the configuration information will be displayed in a tabular form. See the following table for more information on the results.
Below is the list of things that will be displayed in a tabular form:
Admin Server
Host
Port
Status (running/shutdown)a (Green)/r (red)
Messages describing the steps to fix in case of r (red)
Foundation Server
Host
Port
Status
DataSources targetedFCM Managed Server
Host
Port
Status
DataSources targetedSOA Server
Host
Port
Status
DataSources targetedFinancialClose Web application
Version:
Status:
DB TypeFinancialCloseTaxOpCommon Web application
Version:
Status:
DB TypeEPM-FCM-LIBRARIES library
Version:
Status:
DB TypeAuthentication Providers
Provider configured/ not
Control Flag (Sufficient/Not)External Authenticators
Lists the Authentication Providers
SOA Composites
Check whether SOA composites Active/Not
Foreign JNDI
EDN JMS (in case of sql server)
SOA JMSOWSM KeyStore
Lists the external Identity store configuration. The tool only lists the values used for the configuration. It is the responsibility of the customer to make sure that the entered values are correct.
Warning can be ignored.
-
Validating the test schedule:
The second half of the page has a utility that will generate a test Main Orchestration Process, deploys it to soa server and start a test task. The status for each task is displayed in a table below it and should there be any errors – the possible cause of the error and the way to fix it will be displayed in the last column.
If you are running this part, make sure the user logged into the Diagnostic tool with a user that is also present in HSS.
Click on Validate Test Scheduler.
Note: The button to run this test is enabled only if all the required configuration from the above table is in
place; marked with check marks instead of X.
After validation, the configuration information is displayed in a tabular form:
Below is the list of things that is displayed in a tabular form:
SOA Composite Deployment
Tells if the composite deployment to soa server is successful.
a (Green)/r (red)
Messages describing the steps to fix in case of r (red)
Business Event
Tells if the business event if fired successfully.
Composite Instance
Tells if the business event is able to start a Task correctly or not.
FCM Basic Task
Tells if the basic task is started and successfully set to Running Status.
Humanworkflow
The above task is submitted internally to confirm if Humanworkflow is working fine.
Validating Account Reconciliation Manager Configuration
-
Launch the validator tool from a web browser using this URL:
http://<FCMHOST>:<FCMPORT>/arm/faces/oracle/apps/epm/arm/ui/page/common/ARMValidation.jspx
- Where FCMHOST is the name of the machine where FinancialClose0 managed server is configured.
- Where FCMPORT is Listening port of FinancialClose0 managed Server in the WebLogic console.
-
Log on with Shared Services administrator credentials.
-
After successful logging in the following screen is displayed.
-
To validate the account reconciliation manager configuration, click on the Validate Account Reconciliation Manager Configuration button.
-
After validation, the configuration information is displayed in a tabular form. See the following table for more information on the results.
Below is the list of things that will be displayed in a tabular form:
Admin Server
Host
Port
Status (running/shutdown)a (Green)/r (red)
Messages describing the steps to fix in case of r (red)
Foundation Server
Host
Port
Status
DataSources targetedFCM Managed Server
Host
Port
Status
DataSources targetedSOA Server
Host
Port
Status
DataSources targetedACCOUNTRECONCILIATION Web Application
Version:
Status:
DB TypeFINANCIALCLOSETAXOPCOMMON Web Application
Version:
Status:
DB TypeEPM-FCM-LIBRARIES library
Version:
Status:
DB TypeAuthentication Providers
Provider configured/ not
Control Flag (Sufficient/Not)External Authenticators
Lists the Authentication Providers
SOA Composites
Check whether SOA composites Active/Not
Foreign JNDI
EDN JMS (in case of sql server)
SOA JMSOWSM KeyStore
Lists the external Identity store configuration. The tool only lists the values used for the configuration. It is the responsibility of the customer to make sure that the entered values are correct.
Warning can be ignored.
-
Validating the test schedule:
The second half of the page has a utility that will generate a test Main Orchestration Process, deploys it to soa server and start a test task. The status for each task is displayed in a table below it and should there be any errors – the possible cause of the error and the way to fix it will be displayed in the last column.
If you are running this part, make sure the user logged into the Diagnostic tool with a user that is also present in HSS.
Click on Validate Test Scheduler.
Note: The button to run this test is enabled only if all the required configuration from the above table is in
place – marked with a check marks instead of an X.
After validation, the configuration information is displayed in a tabular form:
Below is the list of things that is displayed in a tabular form:
Scheduler for Period |
Tells if the scheduler for period started successfully. |
a (Green)/r (red) |
Messages describing the steps to fix in case of r (red) |
Appendix A: Linux Commands
To launch the EPM System installer: Execute
/installTool.shTo launch the SOA Installer: Execute
./runInstaller –jreLoc /oracle/middleware/jdk160_35To launch the SOA Configurator: Run
/oracle_soa1/common/bin/config.sh To launch the EPM System Configurator: Run
/common/config/version_number/configtool.sh To start weblogic server: Run
/user_projects/domains/ /bin/startWebLogic.sh To start SOA server : Execute
/user_projects/domains/ /bin/startManagedWebLogic.sh soa_server1 To start Foundation Services: Run
/user_projects/epmsystem1/bin/startFoundationServices.sh To start OHS: Run
/user_projects/epmsystem1/bin/startOHS.sh To stop Foundation Services: Run
/user_projects/epmsystem1/bin/stopFoundationServices.sh -
To launch FDMEE: Run
/user_projects/epmsystem1/bin/startErpIntegrator.sh To start Financial Close Services: Run
/user_projects/epmsystem1/bin/startFinancialClose.sh To stop Financial Close Services: Run
/user_projects/epmsystem1/bin/stopFinancialClose.sh To start epmsystem Services: Run
/user_projects/epmsystem1/bin/start.sh To stop epmsystem Services: Run
/user_projects/epmsystem1/bin/stop.sh - If loading the properties and running the py from the wlsConfigMDS.sh does not succeed, you may load the properties and execute the py script from wls.
Example:
wls:/offline>loadProperties('/scratch/Oracle/Middleware/EPMSystem11R1/products/FinancialDataQuality/bin/wls-infra.properties')
wls:/offline>execfile('/scratch/Oracle/Middleware/EPMSystem11R1/products/FinancialDataQuality/bin/wlsConfigMDS.py')
Appendix E: Stopping and Restarting the Servers
Stopping the Servers
-
To stop the WebLogic Admin Server:
- Press and hold Ctrl + C in the command window where WebLogic Admin server has been started.
- When prompted to terminate the batch job, type 'Y' and hit the enter key (You can also stop it with stopWebLogic.cmd. For example: C:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd).
-
To stop the SOA managed server:
- Press and hold Ctrl + C in the command window where SOA managed server has been started.
- When prompted to terminate the batch job, type 'Y' and hit the enter key.
Stop Foundation Services from windows Services.
- To stop Financial Close Management Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then Financial Close, then Stop Financial Close. (You can also stop it with stopFinancialClose.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\stopFinancialClose.bat)
- To stop FDMEE Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then FDM Enterprise Edition, and then Stop ERPIntegrator. (You can also stop it with stopErpIntegrator.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\stopErpIntegrator.bat)
Starting the Servers
You must start the servers required for Financial Close Management in the following order:
- WebLogic Admin Server
- Foundation Services managed server
- Optional: Managed servers for integration products (for example: FDM Enterprise Edition, Financial Management or Financial Reporting)
- SOA managed server
- Financial Close Management managed server
Note: Wait until each server status changes to RUNNING state to go to next server in the sequence. Refresh the page to get the server started status.
-
To start the WebLogic Admin server, select Start, then Programs, then Oracle WebLogic, then User Projects, then
, and then Start Admin Server. (You can also start it with startWebLogic.cmd. For example: C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd).
When prompted, enter the Web Logic admin user name and password.
The process will take few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt box. -
To start Foundation Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then Foundation Services, and then Start FoundationServices.
(You can also start it with startFoundationServices.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\startFoundationServices.bat)
-
To start FDMEE Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then FDM Enterprise Edition, and then Start ERPIntegrator.
(You can also start it with startErpIntegrator.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\startErpIntegrator.bat)
-
To start the SOA managed server, enter the following command at a Command Prompt: c:\oracle\middleware\user_projects\domains\
\bin\startmanagedweblogic.cmd soa_server1 where <domain> is the domain you created using the SOA configuration utility.
When prompted, enter the Web Logic admin user name and password.
The process will take few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt box. -
To start Financial Close Management Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then Financial Close, then Start FinancialClose.
(You can also start it with startFinancialClose.bat. For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\startFinancialClose.bat)
Summary
In this tutorial, you have learned how to:
- Upgrade the components installed for Financial Close Management 11.1.2.3.000.
- Install and Configure EPM Components for Financial Close Management.
- Performing post-installation manual configuration tasks.
Resources
Credits
- Lead Curriculum Developer: Syed Khairulla
- Other Contributors: Mark Mitsock
To navigate this Oracle by Example tutorial, note the following:
- Topic List:
- Click a topic to navigate to that section.
- Expand All Topics:
- Click the button to show or hide the details for the sections. By default, all topics are collapsed.
- Hide All Images:
- Click the button to show or hide the screenshots. By default, all images are displayed.
- Print:
- Click the button to print the content. The content that is currently displayed or hidden is printed.
To navigate to a particular section in this tutorial, select the topic from the list.