Creating Financial Close Management 11.1.2.3 Server Clusters

Overview

    Purpose

    This tutorial covers adding additional Oracle Hyperion Financial Close Management (FCM) servers to a multi-node environment.

    Time to Complete

    Approximately 4 hours

    Introduction

    This tutorial covers adding additional Oracle Hyperion Financial Close Management (FCM) servers to a multi-node environment. This tutorial assumes that FCM 11.1.2.3 has been installed and configured in a multi-node environment following the instructions in the Installing and Configuring Financial Close Management 11.1.2.3 in a Multinode Environment tutorial.

    Scenario

    This tutorial assumes the following installation topology:

    • Machine A will be hosting Admin Server, SOA Server, and Foundation Services.
    • Machine B will be hosting Financial Close Management (FinancialClose0), FDMEE, and Oracle Data Integrator
    • Machine C will be hosting Financial Close Management (FinancialClose1)
    This example uses the standard default oracle home path, domain name and FCM cluster name. Please replace with the appropriate domain name, cluster name, and paths that are used in your configuration, if they are different from the defaults.

    Before starting this tutorial, you should:

    • Verify that that FCM tasks/reconciliations are NOT in a running state. In case of tasks/reconciliations in a running state, you should change the schedule status to Closed and the period status to Locked. These can successfully be reopened after the process is complete. Note that locked schedules cannot be reopened.
    • Stop all servers in the following order: SOA Managed Server (machine A), ERPI Managed Server (machine B), FCM Managed Server (machine B), Foundation Server (machine A), and Admin Server (machine A)

Installing EPM Components on Machine C

    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 New installation, and click Next.

    On the Product Selection screen, perform these steps

    1. Clear Uncheck All.
    2. Under Foundation Services, select Foundation Components.
    3. Select Financial Close Management.
    4. Select FDM Enterprise Edition (Note that Oracle Database Client 32-bit and Financial Management ADM Driver will be auto-selected).
    5. Click Next.

    Note: This example is for installing Foundation Services, Financial Close Manager, Account Reconciliation Manager, and FDM Enterprise Edition only.

    On the Confirmation screen, click Next.

    On the Summary screen, click Finish.

Installing SOA Suite on Machine C

When you install SOA Suite, select the same Middleware Home directory that you specified for installing EPM Components. The Middleware Home directory contains the WebLogic installation, which is required for installing SOA Suite.

    Open a command prompt, navigate to the Disk1 folder under SOA Suite installation directory, and enter the following command:

    Setup.exe -jreLoc <jre location>

    On the Welcome screen, click Next,

    Select Skip Software Updates, and click Next.

    On the Prerequisites screen, click Next.

    On the Specify Installation Location screen, verify that the Middleware Home directory is the directory that you selected when you installed the EPM Components, and click Next.

    Be sure to modify the Middleware Home that is defaulted.

    On the Application Server screen, verify that WebLogic Server is selected, and click Next.

    On the Installation Summary screen, click Install.

    On the Installation Progress screen, when the Installation Successful message is displayed, click Next.

    On the Installation Complete screen, click Finish.

Configuring EPM on Machine C

WebLogic Admin Server must be running on Machine A before you run 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, where <domain> is the WebLogic domain you created with the SOA configuration tool.

    (You can also start it with the 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 a few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt window.

    From the Windows Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator.

    (You can also start the configuration tool by using configtool.bat. For example: C:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat)

    Accept the defaults and click Next.

    Enter the database connection details for the Shared Service database. Verify that Connect to a previously configured Shared Service database is chosen. You should use the same credentials as you entered when you configured Shared Services on Machine A.

    Example for Oracle database:

    Example for MS SQL Server database:

    Perform the following steps to select the components to configure:

    1. Expand Hyperion Foundation and verify that only Configure Oracle Configuration Manager and Configure Database are selected and grayed out. Deselect any items that were selected by default.
    2. Expand Financial Close Management and select Deploy to application server for both Close Manager and Reconciliation Manager. Do not select Configure Database, Deploy to SOA, or Deploy to SOA for FDMEE. Select Configure Content Management System location only if you are using a content management system.
    3. Click Next.

    Select Deploy Java web applications to an existing domain, enter the information for the WebLogic domain that you created when you configured SOA on Machine A, and click Next.

    Note: The details will be populated by default.

    Verify that "Deploy web application to single managed Server" is unchecked and grayed out. Select the FinancialClose and AccountReconciliation check boxes if they are not selected by default, and click Next.

    if you want to be informed of security updates by email, provide the necessary information; otherwise click Next and answer Yes at the confirmation prompt.

    If earlier you chose to integrate Oracle Enterprise Content Management with your Financial Close Management application, specify a location; otherwise click Next.

    Review your selections, and click Next to launch the configuration process.

    When the configuration is complete, click Finish.

    This process creates the clustered Financial Close Management server.

Applying Patch 16709748 to Machine C

    Download ADF patch 16709748 and copy it to machine C.

    Shut down all the servers that are running.

    To apply the patch, follow the instructions given in the patch readme file.

Reconfiguring the Web Server and Logic Web Address on Machine A

You must reconfigure the web server and logical web address on machine A, where Foundation Services is configured. Before reconfiguring the web server, you must shut down WebLogic Admin Server.

    To stop the WebLogic Admin Server perform these steps:

    1. Press and hold Ctrl + C in the command window where WebLogic Admin server has been started.
    2. When prompted to terminate the batch job, type 'Y' and hit the enter key.

    From the Windows Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator.

    Accept the defaults and click Next.

    Expand Hyperion Foundation and select Configure Web Server and Configure Logical Address for Web applications. Make sure both FDM Fusion Edition and Financial Close are not selected. Click Next.

    Accept the default Configure Web Server settings. Verify that Set the logical web address for the web applications to this web server is selected (select it if it is not already selected). Click Next.

    Select the Set the logical web address for all the web applications to: option and click Next.

    Review your selections, and click Next to launch the configuration process.

    When the configuration is complete, click Finish.

Copying Keystore Files from Machine A to Machine C

    Follow the procedure below to copy the keystore files from machine A to machine C.

    • Copy the keystore file, default-keystore.jks, and the cwallet..sso file from the source folder on machine A to the destination folder on machine C:

    The source folder on machine A is:
    C:\Oracle\Middleware\user_projects\domains\<domain>\config\fmwconfig
    where <domain> is the domain you created using the SOA Configuration tool.

    The destination folder on machine C is:
    C:\Oracle\Middleware\user_projects\domains\<domain>\config\fmwconfig
    where <domain> is the domain you created using the SOA Configuration tool.

Performing Post-Installation Manual Configuration Tasks

    After completing the above installation and configuration tasks, you must perform the following manual configuration tasks:
    • Configure the async queue for a new node
    • Update the soa_infra schema
    • Update the LLR table (MS SQL Server only)

    Configuring the Async Queue for a New Node

      Shut down both FinancialClose0 and FinancialClose1 servers. (Shut down only these servers. WebLogic Admin Server should be running.)

      Start WebLogic Admin Console: select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, and then Admin Server Console.

      Log on using the WebLogic administrator name and password that you specified for the domain.

      Click Lock & Edit.

      Under Domain Structure, expand Services.

      Under Services, expand Messaging.

      Select JMS Modules, and in the JMS Modules list, delete JRFWSAsyncJmsModule_FinancialClose.

      Select JMS Servers and in the JMS Servers List, delete JRFWSAsyncJmsServer_FinancialClose0_auto_1.

      Select Persistent Stores and in the Persistent Stores list, delete JRFWSAsyncFileStore_FinancialClose0_auto_1.

      Click Activate Changes.

      On Machine A (where admin server is running), open a command prompt, change the directory to C:\Oracle\Middleware\oracle_common\webservices\bin, and run the following command:
      C:\Oracle\Middleware\wlserver_10.3\common\bin\wlst jrfws-async-createUDDs.py --domain_home C:\Oracle\Middleware\user_projects\domains\base_domain --cluster FinancialClose

      On machine B (where FinancialClose0 is running), go to <domain_home> (e.g. C:\Oracle\Middleware\user_projects\domains\base_domain) and create a blank directory with the following name
      JRFWSAsyncFileStore_auto_1

      On machine C (where FinancialClose1 is running), go to <domain_home> (e.g. C:\Oracle\Middleware\user_projects\domains\base_domain) and create a blank directory with the following name:
      JRFWSAsyncFileStore_auto_2

      On Machine C, perform the following steps to modify the file setdomainEnv.cmd in the <domain_home>/bin directory (e.g. C:\Oracle\Middleware\user_projects\domains\base_domain\bin) for notifications:

      1. Add ‘set SOA_ORACLE_HOME=C:\Oracle\Middleware\Oracle_SOA1’ after set SUN_JAVA_HOME=
      2. Modify ‘set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true' to:
        ‘set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -Dsoa.oracle.home=%SOA_ORACLE_HOME% -Dem.oracle.home=C:\Oracle\Middleware\oracle_common -Djava.awt.headless=true’
        (You just need to add the -Dsoa.oracle.home=%SOA_ORACLE_HOME% variable)

      In WebLogic Admin Console, start the FCM nodes ( FinancialClose0 and FinancialClose1) one after the other. Wait unitl both FCM nodes have finished starting.

      Verify the JMS async queue configurations and their targets:

      1. Go to WebLogic Admin Console
      2. Verify the created modules, servers and stores are targeted to FCM managed servers or cluster wherever applicable by navigating to Domain Structure > Services > JMS Modules, JMS Servers and Domain Structure > Persistent stores.
      3. Verify FCM and ARM deployment status to be Active (both from weblogic console and em console).

       

    Updating the soa_infra Schema

      Connect to soa_infra schema using SQL Developer and run the following query:

      For Oracle Databases:
      UPDATE WFTASKDISPLAY SET httpport = <LWA Port> , httpsport=0, hostname = <LWA Host> WHERE URI like '/workflow/%';

      Note: Use the logical web address host and port that you specified during logical web address configuration,
      where <LWA Port> is replaced by the logical web address port (default 19000), and
      where <LWA Host> is replaced by the logical web address host name(default Machine A)

      For MS SQL Server Databases:
      UPDATE your_sql_db.DEV_SOAINFRA.WFTaskDisplay SET your_sql_db.DEV_SOAINFRA.WFTaskDisplay.httpPort = <LWA Port>, your_sql_db.DEV_SOAINFRA.WFTaskDisplay.httpsPort=0, your_sql_db.DEV_SOAINFRA.WFTaskDisplay.hostName = <LWA Host> WHERE your_sql_db.DEV_SOAINFRA.WFTaskDisplay.uri like '/workflow/%';

      where ‘your_sql_db’ is replaced by SQL DB name
      where ‘DEV_’ is replaced by the prefix name used when creating via RCU
      Note: Use the logical web address host and port that you specified during logical web address configuration,
      where <LWA Port> is replaced by the logical web address port (default 19000), and
      where <LWA Host> is replaced by the logical web address host name(default Machine A).
      Refer to the screen shot below for details.

    Updating the LLR Table (MS SQL Server Only)

      Launch MS SQL Management Studio

      Click New Query in the upper left and choose FCM database from the drop-down list just below it.

      Run the following scripts to update the LLR tables:

      DECLARE @alterquery as varchar(2000)
      -- Get the Table created for LLR Transaction
      DECLARE c1 cursor LOCAL FOR
      SELECT
      o.name
      FROM dbo.sysobjects AS o
      WHERE o.name like 'WL_LLR%'

      DECLARE @TEMP_TABLE_NAME VARCHAR (1000)
      OPEN c1
      FETCH NEXT FROM c1 INTO
      @TEMP_TABLE_NAME
      WHILE (@@FETCH_STATUS = 0)

      BEGIN

      PRINT @TEMP_TABLE_NAME

      -- Modify each LLR Table and alter column RECORDSTR width to 4000.
      SET @alterquery = 'ALTER TABLE ' + @TEMP_TABLE_NAME +' ALTER COLUMN RECORDSTR nvarchar(4000)'

      exec (@alterquery )

      FETCH NEXT FROM c1 INTO
      @TEMP_TABLE_NAME
      END
      CLOSE c1
      DEALLOCATE c1
      GO

       

Restarting the Servers

    You must start the servers required for Financial Close Management in the proper order.
    Note: Wait until each server status changes to RUNNING before you starting the next server in the sequence. Refresh the page to get the server status.

    Start the servers in the following order.

    1. WebLogic Admin Server (Machine A)
    2. Foundation Services managed server (Machine A)
    3. Oracle Process Manager(Machine A)
    4. Optional: Managed servers for integration products (for example: FDM Enterprise Edition, Financial Management or Financial Reporting) (Machine B)
    5. SOA managed server (Machine A)
    6. Financial Close Management Managed server (Machine B)
    7. Financial Close Management Managed server (Machine C)

Running the Validation Tool to Verify Your Configuration

    You can use the validation tool to verify your EPM, Close Manager, and Account Reconciliation Manager configurations.

    Running the Validation Tool to verify EPM configuration on Machine A

      To run the EPM System Diagnostics tool, double-click the validate.bat file:
      %EPM_ORACLE_INSTANCE%\bin\validate.bat.

      For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat

      A new browser window is launched that displays the Oracle EPM System Diagnostics page with the status of all EPM components.

      In the Oracle EPM System Diagnostics page, verify that all components have a status of PASSED.

      To run the EPM Deployment Topology report, at a command prompt, enter the following command:
      %EPM_ORACLE_INSTANCE%\bin\epmsys_registry.bat report deployment

      For example: C:\Oracle\Middleware\user_projects\epmsystem1\bin\epmsys_registry.bat report deployment

      A new browser window is launched that displays the EPM Deployment Topology Report.

      Scroll to the bottom of the report and verify that 0 items failed.

    Running the Validation Tool to Verify Close Manager Configuration on Machine B

      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 the FinancialClose0 managed server is configured, and
      where <FCMPORT> is the Listening port of the FinancialClose0 Managed Server in the WebLogic console.

      Log on to Close Manager with Shared Services administrator credentials.

      To validate the Close Manager configuration, click the Validate Financial Close Manager Configuration button.

      After validation, the configuration information will be displayed in a tabular form. A checkmark in the status columns indicates Pass, an X indicates Fail. In case of a Fail status, the Next Steps column suggests corrective actions. See the table beneath the graphic for a list of all validation items.


      Admin Server

      Host
      Port
      Status (running/shutdown)

      Foundation Server

      Host
      Port
      Status
      DataSources targeted

      FCM Managed Server

      Host
      Port
      Status
      DataSources targeted

      SOA Server

      Host
      Port
      Status
      DataSources targeted

      FCM Web application

      Version:
      Status:
      DB Type

      Authentication 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  JMS

      OWSM 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.
      Warnings can be ignored.

      To validate a test schedule, in the bottom half of the page, click Validate Test Schedule.

      This test generates a test Main Orchestration Process, deploys it to SOA Server, and starts a test task. The status for each task is displayed in a table. Should there be any errors, the possible cause of the error and suggested corrective action displays in the last column. If you are running this test, make sure the user logged into the Diagnostic tool is a user that is also present in Hyperion Shared Services.
      Note: The button to run this test is enabled only if all the required configuration from the above table is in place, displaying a checkmark instead of an x.

      After validation, the configuration information is displayed in a tabular form. A checkmark in the status columns indicates Pass, an X indicates Fail. In case of a Fail status, the Next Steps column suggest corrective actions. See the table beneath the graphic for additional information on the validation items.


      SOA Composite Deployment

      Tells if the composite deployment to soa server is successful.

      Business Event

      Tells if the business event 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 properly.

    Running the Validation Tool to Verify Account Reconciliation Manager Configuration on Machine B

      From a Web browser, open the following URL:
      http://<FCMHOST>:<FCMPORT>>/arm/faces/oracle/apps/epm/arm/ui/page/common/ARMValidation.jspx

      where <FCMHOST> is the name of the machine where the FinancialClose0 managed server is configured, and
      where <FCMPORT> is the Listening port of the FinancialClose0 Managed Server in the WebLogic console.

      Log on to Close Manager with Shared Services administrator credentials.

      To validate the close manager configuration, click the Validate Account Reconciliation Manager Configuration button.

      After validation, the configuration information will be displayed in a tabular form. A checkmark in the status columns indicates Pass, an x indicates Fail. In case of a Fail status, the Next Steps column suggests corrective actions. See the table beneath the graphic for a list of all validation items.


      Admin Server

      Host
      Port
      Status (running/shutdown)

      Foundation Server

      Host
      Port
      Status
      DataSources targeted

      FCM Managed Server

      Host
      Port
      Status
      DataSources targeted

      SOA Server

      Host
      Port
      Status
      DataSources targeted

      ARM Web Application

      Version:
      Status:
      DB Type

      Authentication 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  JMS

      OWSM 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.
      Warnings can be ignored.

Summary

     

    In this tutorial, you have learned how to:

    • Add additional Financial Close Management (FCM) servers to a multi-node environment.
    • Perform post-Installation manual configuration tasks.
    • Run the validation tool to verify your configuration.

    Credits

    • Lead Curriculum Developer: Mark Mitsock
    • Other Contributors: Raghava Ravindranath, Ron Reiley

To navigate this Oracle by Example tutorial, note the following:

Hide Header Buttons:
Click the title to hide the buttons in the header. To show the buttons again, click the title again.
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.