Installing and Configuring Oracle® Hyperion Financial Close Management 11.1.2.4.000 in a Multi Node Environment

In the folder to which you unzipped the utility, navigate to the rcuHome\bin folder and run rcu.bat.

1. On the Welcome screen, click Next.

   

2. On the Create Repository screen, select Create, and then click Next.

   

3. On the Database Connection Details screen, enter the database connection details, you wish to configure SOA. Be sure to enter user with DBA or SYSDBA privileges and select SYSDBA as the role. Click Next to continue.

   Example for Oracle Database:

   

   Example for MS SQLServer Database:

   

4. At the prerequisites confirmation prompt, click OK. If a warning prompt regarding the character set is displayed, click Ignore.

   

5. On the Select Components screen, in Create a new Prefix, enter a prefix for the schema tables.

   In the Component list: Under SOA and BPM Infrastructure, select SOA Infrastructure and click Next.

   You will see that, User Messaging Service under SOA and BPM Infrastructure and Metadata Services under AS Common Schemas get selected automatically when you selected SOA Infrastructure.

   

6. At the prerequisites confirmation prompt, click OK.

   

7. On the Schema Passwords screen, select Use the same password for all schemas, enter a password, and click Next.

   

8. On the Map Tablespace screen, leave the default tablespace names and click Next.

9. The following screen is shown for Oracle

   

10. At the confirmation prompt, click OK.

11. This screen is shown for Oracle.

    

12. At the completion prompt, click OK.

13. This screen is shown for Oracle.

    

14. On the Summary screen, click Create. This may take a while.

    

15. On the Completion Summary screen, click Close.

    

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. SOA Suite has to be installed on both Machine A and Machine B.

1. Open Command prompt and Navigate to the Disk1 folder under SOA Suite installation directory and provide following command.

   Setup.exe -jreLoc <jre location>

   

2. On the Welcome screen, click Next.

   

3. Select Skip Software Updates and click Next.

   

4. On the Prerequisites screen, click Next.

   

5. 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.

   Please ensure to modify the Middleware Home that is defaulted.

   

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

   

7. On the Installation Summary screen, click Install.

   

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

   

9. On the Installation Complete screen, click Finish.

   

Apply SOA patch 17014142 (on both the machines)

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 (on both the machines)

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.

After installing SOA Suite and running the Repository Creation Utility, you configure SOA Suite and create a WebLogic domain. You later extend this WebLogic domain for Financial Close Management.

1. Select Start, then Programs, then Oracle SOA 11g - Home1, and then Configure Application Server.
   (You can also start it with config.cmd. For example: C:\Oracle\Middleware\Oracle_SOA1\common\bin\config.cmd).

2. Select Create a new WebLogic domain, and click Next.

   

3. On the Select Domain Source screen, select Generate a domain configured automatically to support the following products, then select Oracle SOA Suite, Oracle Enterprise Manager, Oracle WSM Policy Manager, Oracle JRF Webservices Asynchronous Services, and Oracle JRF, and click Next.
   You will see that, Oracle WSM Policy Manager and Oracle JRF get selected automatically when you selected Oracle SOA Suite.

   

4. On the Specify Domain Name and Location screen, enter a domain name and accept the default locations, and click Next.
   You must use the same domain name when you configure the EPM components. In this example, the domain name is base_domain.

   

5. On the Configure User Name and Password screen, enter a user name and password for the WebLogic domain administrator, and click Next.
   You use this domain administrator name and password for the EPM components as well. In this example, the domain administrator name is weblogic.

   

6. On the WebLogic Domain Startup Mode screen, change the mode to Production Mode if the default is Development Mode. Then select the Jrockit location, and click Next.

   

7. On the Configure JDBC Component Schema screen, select each component schema and provide the database connection information, using the prefix and schema password that you entered in the Repository Creation Utility. When finished, click Next.

   Example for Oracle Database:

   

   Example for MS SQLServer Database:

   

8. On the Test Component Schemas screen, verify that the connections to your data sources are successful, and click Next.

   

9. On the Select Optional Configuration screen, leave the default settings and click Next.

   

10. On the Configuration Summary screen, click Create.

    

11. On the Creating Domain screen, when the process is complete, click Done.

    

1. 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).

2. Accept the defaults, and click Next.

   

3. Select Perform first -time configuration of Shared Services database, enter the database connection details for the Shared Service database, and click Next. This might take several minutes.

   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;
   • Service Name or SID:  FCMdb
   • User Name: fcm
   • Password: welcome1

   

4. Expand Hyperion Foundation and accept the default options. Make sure to select Deploy to Application Server and Configure Web Server if not selected. Deselect the top-level nodes of FDM Enterprise Edition & Financial Close Management. Click Next.

   

5. Select Create Windows Services for configured components, Enter Email Configuration details and click Next.

   

6. Select Deploy Java 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 configuration)

   

7. If there is a warning about password validation, press OK.

   

8. Uncheck the deploy the Java web applications to a single managed Server and accept the default application server deployment settings, and click Next.

   

9. Accept the default Configure Web server settings, and click Next.

   

10. In the Password and Re-type Password text boxes, enter a password, and click Next.

    

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

    

12. When the configuration is complete, click Finish.

    

1. Ensure that admin server is running on Machine A before running 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 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.

2. From the Windows Start menu, select Programs, then Oracle EPM System, then Foundation Services, and then EPM System Configurator.
   (You can also start it with configtool.bat. For example: C:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat).

3. Accept the defaults and click Next.

   

4. Enter the database connection details for the Shared Service database.
   Ensure Connect to a previously configured Shared Service database is chosen.
   The credentials should be same as entered when configuring Shared Services on Machine A

   Example for Oracle Database:

   

   Example for MS SQLServer Database:

   

5. Expand Hyperion Foundation and ensure that only Configure Common Settings and Configure Database are selected and grayed out. Deselect any items that were selected by default.

   Expand FDM Enterprise Edition and select Configure Database and Deploy to Application Server.

   Select Financial Management if not selected.

   Expand Financial Close Management and 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.

   

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

   Example for Oracle Database:

   

   Example for MS SQLServer Database:

   

7. 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.

   

8. Ensure that Deploy the Java web applications to a single managed Server is unchecked and grayed out. Accept the default application server deployment settings, and click Next.

   

9. If earlier you chose to integrate Oracle Enterprise Content Management with your Financial Close Management application you will see this screen, otherwise skip to the next section.

   

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

    

11. When the configuration is complete, click Finish.

    

1. Ensure that both Admin and SOA server are running on Machine A before running 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, 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).
   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 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 few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt box.

2. After configuring EPM products, you need to run the EPM System Configurator again to deploy to SOA.

   On Machine B, from the Windows Start menu, select Programs, then Oracle EPM System, and then EPM System Configurator.
   (You can also start it with configtool.bat. For example: C:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat).

3. Select EPM Oracle instance to which this configuration would be applied, and click Next.

   

4. Ensure that none of the options under Hyperion Foundation are selected.
   Expand Financial Close Management and select Deploy to SOA and click Next

   

5. On the Confirmation screen, click Next to launch the configuration.

   

6. When the configuration is complete, click Finish.

   

Before reconfiguring the Web server, shutdown both Admin and SOA 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.
• 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.

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

2. Accept the defaults and click Next.

   

3. Uncheck “Check All” option.

4. Expand Hyperion Foundation and select only Configure Web Server.  Click Next.

   

5. Accept the default Configure Web Server settings. Ensure ‘Set the logical web address for the web applications to this web server’ is selected. Select it if not already selected, click Next.

   

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

   

7. When the configuration is complete, click Finish.

   

Start the Admin Server before you start with the instructions.

1. 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 startWebLogic.cmd. For example: C:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd).
2. 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 communicate with an external authentication provider, such as Oracle Internet Directory or Microsoft Active Directory, you must configure WebLogic. You must configure Shared Services to use the same external authentication provider. For more information on configuring Shared Services, see the Oracle Enterprise Performance Management System User and Role Security Guide.

The following instructions show an example of how to configure MSAD as the authentication provider.

1. Connect to Weblogic Console http://host:7001/console where host is the name of the Machine.

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

3. Click on Lock & Edit.

   

4. In the Domain Structure area, click Security Realms.

   

5. Click myrealm.

   

6. Select the Providers tab.

   

7. Click New.

   

8. Configure your authentication provider:

   For Microsoft Active Directory, in the Name text box enter MSAD, and select ActiveDirectoryAuthenticator from the Type list.

   

9. Click OK.

10. In the Authentication Providers list, click MSAD.

    

11. Select the Provider Specific tab. Enter the principal user name and credentials, and modify any other settings as required for your provider.

    

12. Ensure to provide SAMAccountName as User Name Attribute  and in User From Name Filter for MSAD instead of cn.

    

13. Click Save. 

14. In the Domain Structure area, click Security Realms, and then myrealm.

15. Select the Providers tab.

16. In the Authentication Providers list, click MSAD.

17. In the Control Flag list, select Sufficient.

    

18. Click Save.

19. Click  Activate Changes.

    

20. Click Logout.

21. Select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, and then Stop Admin Server.
    (You can also stop it with stopWebLogic.cmd. For example: C:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd).

22. Select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, 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.

1. Start Foundation Services and Oracle Process Manager (OHS) from windows Services of Machine A.

   

   

2. Connect to Shared Service Console http://host:port/interop/index.jsp where host is the name of the Machine and port is Listen port of FoundationServices0 managed Server in weblogic console.

3. Login as admin.

4. Click on Administration and Select Configure User Directories.

   

5. Click New and choose the Directory Type as MSAD and click Next.

   

6. Enter the following in Server information Tab.

   • Host
   • Port
   • Base DN
   • User DN
   • Credential

   

7. Click “Next” to navigate to MSAD User Configuration Tab and enter user information.

   

8. Click “Next” to navigate to MSAD Group Configuration Tab and enter group information.

   

9. Click Save and Logout.

10. Restart the FoundationServices0 Managed Server.

You must set up the Keystore for message protection and configure the Credential Store Provider. The Financial Close Management client and the Oracle Hyperion Financial Management Web service use the following policies:

• wss11_saml_token_with_message_protection_client_policy
• wss11_saml_token_with_message_protection_service_policy

1. At a Command Prompt (on machine where WebLogic Admin Server is running (Machine A)), enter the following command to add the JDK to the path:
   set PATH=%PATH%;C:\Oracle\Middleware\jdk160_35\bin\ 
   (where C:\Oracle\Middleware\jdk160_35\bin has to be your JDK path).
   The JDK must be included in the path in order to run the Java keystore utility.

2. Use the Oracle keystore utility to create a keystore on the Weblogic Admin server hosting your EPM System domain by navigating to c:\oracle\middleware\user_projects\domains\<domain>\config\fmwconfig (where <domain> is the WebLogic domain you created with SOA configuration tool), and enter the following command:

   keytool -genkey -keyalg RSA -alias orakey -keypass welcome1 -keystore default-keystore.jks -storepass welcome1 -validity 3600

   

   This command creates a keystore with the name default-keystore.jks if it does not already exist and adds a new private key entry with alias 'orakey' and password welcome1 to it. You will be prompted for additional information regarding your authentication provider.

   You can change the alias, password, and domain name as needed in the command.

3. Enter the following URL to start Oracle Enterprise Manager, replacing <host> with your host name: http://<host>:7001/em.

4. Enter your Weblogic administrator name and password to login.

5. In the navigation pane, expand WebLogic Domain, and then select the WebLogic domain you created in the SOA configuration tool.

   

6. Click on WebLogic Domain, then Security, and then Security Provider Configuration.

   

7. In the Keystore section, click Configure.

   

8. In the Keystore Path text box, enter the path name for the keystore you created, and enter the keystore password in the password fields. In the Signature Key and Encryption key text boxes, enter the alias and password for the signature and encryption keys.

   It should be noted that the "Keystore Path" requested by EM is relative to "C:\Oracle\Middleware\user_projects\domains\<domain>\config\fmwconfig" so it should be ./default-keystore.jks.

   

9. Click OK.

After you install and configure SOA, you delete the EDNDataSource and EDNLocalTxDataSource data sources.

1. If the WebLogic Admin server is not already running, select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, 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.

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

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

4. Click on Lock & Edit.

   

5. In the Domain Structure area, expand Services and select Data Sources.

   

6. In the Data Sources table, delete EDNDataSource and EDNLocalTxDataSource.

7. Click  Activate Changes.

   

8. Click Logout.

If FCM is configured on different machine from Oracle HTTP Server (which is true for this document case) then you have to do the following steps to manually configure mod_wl_ohs.conf for SOA and WebLogic Admin servers.

1. On the Machine A (Oracle HTTP Server box), make copy of the autogenerated  mod_wl_ohs.conf file under  EPM_ORACLE_INSTANCE/httpConfig/autogenerated/soa/ folder and rename it to mod_wl_soa_ohs.conf.

2. Open the copied mod_wl_soa_ohs.conf in a text editor and replace soa_server_host:soa_server_port and admin_server_host:admin_server_port with the actual values for the SOA host and port and WebLogic Admin server host and port.

   For example change the following section:
   <LocationMatch ^/soa-infra>
   SetHandler weblogic-handler
   WeblogicCluster soa_server_host:soa_server_port
   WLProxySSL ON
   WLProxySSLPassThrough ON
   </LocationMatch>
   ……
   ……
   <LocationMatch ^/console>
   SetHandler weblogic-handler
   WeblogicCluster admin_server_host:admin_server_port
   </LocationMatch>

   to this:

   <LocationMatch ^/soa-infra>
   SetHandler weblogic-handler
   WeblogicCluster demoserverA:8001
   WLProxySSL ON
   WLProxySSLPassThrough ON
   </LocationMatch>
   ……
   ……
   <LocationMatch ^/console>
   SetHandler weblogic-handler
   WeblogicCluster demoserverA:7001
   </LocationMatch>

   Do the same change for all the places where soa_server_host:soa_server_port and admin_server_host:admin_server_port are presented.

3. Copy the modified mod_wl_soa_ohs.conf to EPM_ORACLE_INSTANCE/httpConfig/ohs/config/OHS/ohs_component folder.

4. Open httpd.conf under EPM_ORACLE_INSTANCE/httpConfig/ohs/config/OHS/ohs_component folder in a text editor and add the following line inside of <VirtualHost> tag: Include “conf/mod_wl_soa_ohs.conf”.

   Example:
   <VirtualHost *:19000>
   include "conf/mod_wl_ohs.conf"
   Include "conf/epm_online_help.conf"
   Include "conf/epm_rewrite_rules.conf"
   Include "conf/epm.conf"
   Include "conf/mod_wl_soa_ohs.conf"
   </VirtualHost>

5. Restart OHS instance. You can restart it from Window services such as “Oracle Process Manager (ohsInstance3193331783)”.

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

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

3. Click on Lock & Edit.

   

4. In the Domain Structure area, expand Services and then click on Data Sources.

   Note: For SQL Server Only
   Skip  “Raising the Maximums for Connection Pools” for the deleted data sources (i.e. for EDNDataSource and EDNLocalTxDataSource).

5. In the Name list, click EDNDataSource.

   

6. Select the Connection Pool tab.

7. In the Maximum Capacity text box, enter 150.

   

8. Click Save.

9. In the Domain Structure area, click Data Sources to return to the list of data sources.

10. Repeat steps to increase the connection pools for the EDNLocalTxDataSource to 150.

    If you receive resource errors specific to any of the following data sources, use the above procedure  to increase their connection pools:

    • mds-owm
    • mds-soa
    • EPMSystemRegistry
    • OraSDPMDataSource
    • SOADataSource
    • SOALocalTxDataSource

11. Click  Activate Changes.

    

12. Click Logout.

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

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

3. Click on Lock & Edit.

4. In the Domain Structure area, expand Environment and then click on Servers.

   

5. In the Servers list, click ErpIntegrator0.

   

6. Select the Tuning tab.

7. In the Stuck Thread Max Time text box, enter 6000.

   

8. Click Save.

9. In the Domain Structure area, click Servers to return to the list of servers.

10. Repeat steps to increase the Stuck Thread Max Time for the soa_server1 and FinancialClose0.

11. Click  Activate Changes.

    

12. Click Logout.

13. Stop Foundation Services from Windows Services.

14. To stop the WebLogic Admin Server:

• Press and hold Ctrl + C in the command window where WebLogic Admin server has been started. Type 'Y' and hit the enter key when prompted to terminate the batch job.

15. To stop the SOA managed server:

• Press and hold Ctrl + C in the command window where   SOA managed server has been started. Type 'Y' and hit the enter key when prompted to terminate the batch job.

1. Launch the validator tool from a web browser using this 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.

   

2. 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):

   1. Log on to WebLogic admin console (http://localhost:7001/console)
   2. Click on Lock & Edit

   

   3. Go to Domain Structure area and click Security Realms

      

   4. Click on myrealm link.

      

   5. Go to Users and Groups tab and click New under the Users tab.

   

   6. Enter admin for Name field and enter admin user’s password for Password/Confirm Password fields (or simply enter welcome1 for the password)

   

   7. Click OK
   8. Click  Activate Changes

   

3. After successfully logging on the following screen is displayed.

   

4. To validate the close manager configuration, click on “Validate Close Manager Configuration” button.

   

5. 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:

6. Validate 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.

1. 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.

   

2. Log on with Shared Services administrator credentials.

3. After successful logging in the following screen is displayed.

   

4. To validate the account reconciliation manager configuration, click on the Validate Account Reconciliation Manager Configuration button.

   

5. 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 targeted
   FCM Managed Server	Host Port Status DataSources targeted
   SOA Server	Host Port Status DataSources targeted
   ACCOUNTRECONCILIATION Web Application	Version: Status: DB Type
   FINANCIALCLOSETAXOPCOMMON Web Application	Version: Status: DB Type
   EPM-FCM-LIBRARIES library	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. Warning can be ignored.

6. Validating Test Scheduler

   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 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)

You must create databases in SQL Server and run the Repository Creation Utility before you install and configure SOA Suite.

1. Install SQL Server and log on to Microsoft SQL Server Management Studio with sa user;

2. Create a login with the db_owner role.

   1. Go to the Object Explorer window. Navigate to the Security folder and right click on Login, then click on New Logins.

      

   2. In the General tab, select SQL Server authentication, enter the Login Name, password and Confirm password..

      

3. Select the Server Roles tab and select the dbcreator and sysadmin Server roles.

   

4. Click OK to create the user.

5. Create two databases: one for SOA, and another for Financial Close Management and HSS. Set the login created earlier as the owner of the two databases.

   1. Right click on Database and select “New Database…”

      

   2. Enter the Database name and Owner.

      

   3. Click OK to create the database.

6. Modify the properties of the database for SOA by using the following commands:

   1. Click on New Query in the upper left and choose master database from the dropdown just below it.
   2. Enter the below commands and replace <database name> with the SOA Database.
      ALTER database <database name> SET READ_COMMITTED_SNAPSHOT ON
      ALTER database <database name> COLLATE SQL_Latin1_General_CP1_CS_AS

   3. Click on the ‘Execute’ button to run the commands.

   

7. Modify the properties of the database for Financial Close Management by using the following command:
   ALTER database <database name> SET ALLOW_SNAPSHOT_ISOLATION ON

You must Enable XA transactions for SQL Server in both SQL Server and at the operating system level. You should perform these procedures before you install and configure SOA Suite.

1. Copy instjdbc.sql from C:\Oracle\Middleware\wlserver_10.3\server\lib into:

   C:\Program Files\Microsoft SQL Server\MSSQL10.<INSTANCE_NAME>\MSSQL\Binn for SQL Server 2008. 

2. Copy one of the following:

   sqljdbc.dll(for 32 bit OS)
   64sqljdbc.dll (for 64 bit OS Titanium based)
   x64sqljdbc.dll(for 64 bit OS Intel based)
   from C:\Oracle\Middleware\wlserver_10.3\server\lib into
   C:\Program Files\Microsoft SQL Server\MSSQL10.<INSTANCE_NAME>\MSSQL\Binn for SQL Server 2008.

3. After copying the file, rename the 64sqljdbc.dll or x64sqljdbc.dll to sqljdbc.dll.

4. Run the following command from the command prompt:

   SQLCMD.EXE -S <SERVER NAME> -U SA -P SA_PASSWORD -i “C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\instjdbc.sql” -o log.txt

   SQLCMD.EXE is located at C:\Program Files\Microsoft SQL Server\100\Tools\Binn\ for SQLServer 2008.

   In the above command "SERVER NAME" is the server name used to connect SQLServer using SQL Server Studio.

   Example for SQL Server 2008:

   

5. Look for the messages creating JDBC XA procedures and instxa.sql completed successfully in the log. If the messages are present then the SQL ran fine and you can ignore any other messages in the log.

   

6. For Windows 2008:

   1. Select Start, then Programs, then Administrative Tools, then Component Services, and Computers,  and expand My Computer and Distributed Transaction Coordinator.
   2. Right Click Local  DTC and select Properties
   3. Select the Security Tab, and then select Enable XA Transactions.
   4. Click OK.

   

   Note: Click OK through the warning dialogs about service restarting.

7. For Windows 2003:

   1. Select Start, then Programs, then Administrative Tools, then Component Services, and then Computers.
   2. Right click on My Computer and select Properties.

      

   3. Select the MSDTC tab and click Security Configuration.

      

   4. Select Enable XA Transactions
   5. Click OK

   

8. Restart SQL Server (MSSQLSERVER) from Windows Services.

   

1. Run ipconfig /all from Command Prompt on Machine A.

   

2. If there is any device using IPv6 such as the following example then you need to test IPv6 connection from other remote machine.

   

3. From Machine B ping Machine A from a Command Prompt as follows:
   ping -6 <Machine A> where <Machine A> is the name or IP Address of Machine A.

   

4. If ping returns Ping request could not find host <Machine A> then your network doesn't support IPv6 and you must turn off IPv6 before you start EPM installation.

   

1. From Local Area Connection Properties, unchecked IPv6:
   1. From the Start menu, right click on Network and click on Properties.
   2. From Network and Sharing Center screen, click on Local Area Connection.

   

2. From Local Area Connection Properties, deselect IPv6.

   

3. From Command Prompt, run ipconfig /all and check if there is no process using IPv6 (this check has to done every time you restart the machine).

   For example the following illustrates Teredo is still using IPv6.

   

4. To disable devices using IPv6 do the following:

   1. From the Start menu, click Administrative Tools, and then Computer Management
   2. Go to Device Manager
   3. Form View menu, click Show hidden devices
   4. Expand Network adapters
   5. Right click on Teredo Tunneling Pseudo-Interface (or any other device that is using IPv6) and disable it

      

5. Run ipconfig /all again from the Command Prompt to make sure there are no longer any devices using IPv6. If you find more then repeat above steps to turn it off until there is no device using IPv6.

1. To stop the WebLogic Admin Server on Machine A:

   • 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).

2. To stop the SOA managed server on Machine A:

   • 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.

3. Stop Foundation Services from windows Services on Machine A.

4. To stop Financial Close Management Services on Machine B, 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).
5. To stop FDMEE Services on Machine B, 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)

You must start the servers required for Financial Close Management in the following order:

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

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.

1. 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.

2. 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)

3. To start FDMEE Services on Machine B, 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)

4. To start the SOA managed server on Machine A, 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.

5. To start Financial Close Management Services on Machine B, 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)