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

Ensure Windows Firewall is turned off - see Appendix A: Turning Off Windows Firewall

Ensure IPv6 Network is properly working if this feature in enabled on your machines – see Appendix B: IPv6 Network.

Have access (with sysdba privileges) to an Oracle 11g ( 11.1.0.7 or higher) or a MS SQL Server 2005/2008 database.

Have access (with administrative rights) to an external authentication provider, such as Oracle Internet Directory, Microsoft Active Directory, or SunOne.

Have access to the installation files for the following software:
Oracle Hyperion Enterprise Performance Management System Installer Release 11.1.2.3.000
Oracle Hyperion Foundation Services Release 11.1.2.3.000
Oracle Hyperion Financial Close Management Release 11.1.2.3.000
Oracle SOA Suite 11g (11.1.1.7.0)
Oracle Repository Creation Utility 11g(11.1.1.7.0)
Oracle Data Integrator 11g (11.1.1.6.0)
Patch 16709748

Navigate to the installation folder for the EPM software and run installtool.cmd.

Note: Throughout this tutorial, for Linux version of commands, see Appendix E: Linux Commands.

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:

a. Deselect Check All.

b. Under Foundation Services select Foundation Components.

c. Select Financial Close Management.

d. Select FDM Enterprise Edition (Oracle Database client 32-bit under Foundation Services and ADM Driver
under Financial Management will be auto-selected).

e. Click Next.

Note: This example is for installing Foundation Services, Financial Close Manager, Account Reconciliation Manager, and FDM Enterprise Edition only.
If you are installing other EPM products in adistributed environment then you must install all of them to Machine A where
WebLogic Admin server will be running because it is required that the machine which hosts WebLogic Admin server should have
all the binary files for every products configured in distributed environment.

On the Confirmation screen, click Next.

On the Summary screen, click Finish.

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

On the Welcome screen, click Next

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

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 SQL database:

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

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

In the Component list, under SOA and BPMA 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.

At the prerequisites confirmation prompt, click OK.

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

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

Note: The example below is for Oracle.

At the confirmation prompt, click OK.

Note: The example below is Oracle.

At the completion prompt, click OK.

Note: The example below is Oracle.

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

On the Completion Summary screen, click Close.

Open Command prompt and Navigate to the Disk1 folder under SOA Suite installation directory and provide 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 default Middleware Home location if needed.

On the Application Server screen, verify that the 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.

Select Start, then Programs, then Oracle SOA 11g - Home1, and then Configure Application Server.

Note: You can also start it using config.cmd. For example: c:\Oracle\Middleware\Oracle_SOA1\common\bin\config.cmd).

Select Create a new WebLogic domain, and click Next.

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.

On the Specify Domain Name and Location screen, enter a domain name, 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.

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.

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.

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 SQl Server database:

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

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

On the Configuration Summary screen, click Create.

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

From the Windows Start menu, select Programs, then Oracle EPM System,
and then EPM System Configurator(all instances).

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

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 SQl Server 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

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 Enterprie Edition and Financial Close Management. Click Next.

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

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 create when you configure SOA.
Domain Name: Use the existing domain that was created when you configured SOA. The default
domain name is base_domain.

Note: If there is a warning about password validation, click OK.

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

Accept the default Configure Web Server settings, and click Next.

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

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

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

When the configuration is complete, click Finish.

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.

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.

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

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

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

Example for Oracle database:

Example for MS SQl Server database:

Make the following selections:

• Expand Hyperion Foundation and ensure that only Configure Oracle Configuration manager
  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.
• Expand Financial Close Managment and select Deploy to application server and Configure Database
  for both Close Manager and Reconciliation Manager.
  Do not select Deploy to SOA and Deploy to SOA for FDM EE.
• Financial Management’s Configure DCOM is required for FDM EE and it should be selected by default
• Select Configure Content Management System location only if you are
  using a content management system.

Click Next.

You will see the connection details for the
Financial Close Management, FDMEE and Reconciliation Manager databases. Verify the information, and click Next.

Example for Oracle Database:

Example for MS SQL Server Database:

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

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

Enter the local user credential (the local administrator user you are currently logged on as on Machine B) and click Next.

Provide the necessary information if you want to be informed of security updates by email,
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 you will see this screen, otherwise skip to the next section.

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

When the configuration is complete, click Finish.

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

On machine B, from the Windows Start menu, select Programs, then Oracle EPM System,
then EPM System Configurator(all instances).

Note: You can also start it with configtool.bat. For example:
c:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat.

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

Expand Financial Close Management, then Close Manager, and select Deploy to SOA.
Expand Financial Close Management, expand Account Reconciliation, and select Deploy to SOA
and Deploy to SOA for FDM EE, verify that none of the options under Hyperion Foundation are selected,
and click Next.

On the Deploy to SOA screen, click Next.

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

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 .

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

Accept the defaults and click Next.

Expand Hyperion Foundation and select only Configure Web Server.  Make sure both
FDM Enterprise 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), and click Next.

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

When the configuration is complete, click Finish.

WebLogic Admin server must be running before you start manual configuration tasks.

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

Note: You can also start it with startWebLogic.cmd. For example: c:\Oracle\Middleware\user_projects\domains\base_domain\bin\startWebLogic.cmd.

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

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

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

Click on Lock & Edit.

In the Domain Structure area, click Security Realms.

Click myrealm.

Select the Providers tab.

Click New.

Configure your authentication provider.

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

Click OK.

In the Authentication Providers list, click MSAD.

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

Make sure you provide SAMAccountName as User Name Attribute and in
User From Name Filter for MSAD instead of cn.

Click Save.

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

Select the Providers tab.

In the Authentication Providers list, click MSAD.

In the Control Flag list, select Sufficient.

Click Save.

Click  Activate Changes.

Click Logout.

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

Note: You can also stop it with stopWebLogic.cmd.
For example: c:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd.

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.

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

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

Log in as admin.

Click on Administration and Select Configure User Directories.

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

Enter the following in the Server information Tab:

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

Click Nex” to navigate to the MSAD User Configuration Tab and enter the user information.

Click Next to navigate to the MSAD Group Configuration Tab and enter group information.

Click Save and Logout.

Restart the FoundationServices0 Managed Server.

At a command prompt on the 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.

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

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

Enter your Weblogic administrator name and password to log in.

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

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

In the Keystore section, click Configure.

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

Click OK.

Note: The keystore (default-keystore.jks) and the cwallet.sso files must be copied to Machine B after configuring the keystore above. Copy these files to the <domain>/config/fmwconfig folder, where <domain> is the domain you created using the SOA configuration tool.

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.

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.

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.

In the Domain Structure area, expand Services and select DataSources.

In the Datasources table, delete EDNDataSource and EDNLocalTxDataSource.

Click  Activate Changes.

Click Logout.

On Machine A (the Oracle HTTP Server box), make a 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.

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

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:

Restart the OHS instance. You can restart it from Window services, for example: “Oracle Process Manager (ohsInstance3193331783)”

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.

In the Domain Structure area, expand Services, and click on Datasources.

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

In the Name list, click EDNDataSource.

Select the Connection Pool tab.

In the Maximum Capacity text box, enter 150.

Click Save.

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

Repeat steps 3 to 6 to increase the connection pool 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

In the Domain Structure area, expand Environment and select Servers.

In the server list, click ERPIntegrator0.

Select the Tuning tab.

In the Stuck Thread Max Time textbox, enter 6000.

Click Save.

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

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

Click  Activate Changes.

Click Logout.

Stop Foundation Services from windows services.

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

To stop the SOA managed server,press and hold Ctrl + C in the command window where WebLogic Admin server
has been started. When prompted, type 'Y' and hit the enter key to terminate the batch job.

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

You see the list of servers to be started:

Note: Wait until each server status changes to the RUNNING state before you go to next server in the sequence.
Refresh the page to get the server 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.

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 the Oracle HTTP server, enter the following command at a command prompt:
c:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\bin\opmnctl.bat startall

To start FDM Enterprise Editions Integrator on Machine B, start the Oracle Hyperion FDM Enterprise Edition -Jave Web Application service from Windows Services.

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

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.

Note: You can also start it with startFinancialClose.bat. For example:
c:\Oracle\Middleware\user_projects\epmsystem1\bin\startFinancialClose.bat.

The EPM validator tool can be launched by running (double- clicking) the following .bat script:
%EPM_ORACLE_INSTANCE%\bin\validate.bat

Example: c:\Oracle\Middleware\user_projects\epmsystem1\bin\validate.bat

This launches a new browser window with the validation status for each EPM component (all components should have a pass status, as in the following example:

To run an EPM status report, launch the following bat script:
%EPM_ORACLE_INSTANCE%\bin\epmsys_registry.bat report deployment

This produces a new browser window with the following report:

Scroll to the end of the report and you should all passed and 0 failed.

Launch the validator tool using the following the URL from a web browser:
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 in to Close Manager with Shared Services administrator credentials.

Note: If an external provider is configured, the log in can also be done with a user from the external provider.
But if there are issues with external provider configuration, the log in may not succeed. In such cases, you can
log in 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 an “admin” user (who is default administrator in Shared Services) in WebLogic (this way, you can use the admin user
to log in to the validator):

a. Log in to WebLogic admin console (http://localhost:7001/console.

b. Click Lock and Edit.

c. Go to the Domain Structure area and click Security Realms.

d. Click the myrealm link.

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

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

g. Click OK.

h. Click Activate Changes.

After successfully logging in the following screen is displayed.

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

After validation, the configuration information is displayed in a tabular form.
See the table below for more information on the results.

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 is a user that is also present in HSS.

To run validate the test schedule, click Validate Test Schedule.

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 will be displayed in a tabular form, Below is a list of the information displayed.

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 to Close Manager with Shared Services administrator credentials.

 

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

After validation, the configuration information is displayed in a tabular form. See the table below for more information on the results.

Below is the information that is displayed:

Copy the downloaded patch to <MIDDLEWARE_HOME>oracle_common\OPatch directory.

Shut down all the servers if any are running.

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

Edit the wls-ARM.properties file (Machine B).

a. Go to the machine where ERPI is installed (Machine B).

b. Go to directory <EPM_ORACLE_HOME>/products/FinancialDataQuality/bin

c. Modify the wls-ARM.properties file as following:

For WebLogic Admin server connection:

• userName=adminUserName      (Replace adminUserName with your WebLogic admin user)
• passWord=adminPassword        (Replace adminPassword with your WebLogic admin password)
• adminServerURL=t3://localhost:7001    (Replace localhost:7001 with your WebLogic admin server host and port on Machine A)

Run the wlsConfigARM.bat file (on machine B):

a. Open a command prompt.

b. Change the directory to <EPM_ORACLE_HOME>/products/FinancialDataQuality/bin.

c. Run wlsConfigARM.bat file and verfiy that the script runs successfully.

Restart the FDMEE service (machine B) and WebLogic Admin server (machine A)..
Note: You should start the FDMEE service from Windows Services.

Select Start, then Administrative Tools, and then Windows Firewall with Advanced Security and click on Properties.

Turn the firewall off on the Domain, Private, and Public tabs.

Verify that the IPsec tab is set as follows.

Run "ipconfig /all" from a command prompt on Machine A:

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

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.

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.

From Local Area Connection Properties, deselect IPv6:

a. From the Start menu, right click on Network and click on Properties.

b. From the Network and Sharing Center screen, click on Local Area Connection.

From Local Area Connection Properties, deselect IPv6

From a 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 that Teredo is still using IPv6:

To disable devices using IPv6 do the following:

a. From the Start menu, select Administrative Tools, then Computer Management.

b. Go to Device Manager.

c. Click "Show hidden devices" from the View menu

d. Expand Network adapters.

e. Right-click on Teredo Tunneling Pseudo-Interface (or any other device that is using IPv6) and disable it

Run “ipconfig /all” again from a 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.

To open the SQLPlus window, select Start, then All Programs, then Oracle - OraDb 11g_home1,
then Application Development, and then SQL Plus.

Log in to SQLPlus as sys user and run the following:

create user fcm identified by welcome1;

grant RESOURCE,CONNECT,CREATE SESSION,CREATE VIEW to fcm;

Install SQL Server and log in to Microsoft SQL Server Management Studio as sa user.

Create a log in with the db owner role:

a. Go to the Object Explorer window and right-click on the Logins folder under the Security folder.

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

Select the Server roles tab, and then select the dbcreator and sysadmin Server roles.

Click OK to create the user.

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

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

b. Enter the database name and owner.

c. Click OK to create the database.

Modify the properties of the database for SOAdb:

a. Click on the ‘New Query’ button in the upper left and choose ‘master’ database from the drop-down just below it.

ALTER database <database name> SET READ_COMMITTED_SNAPSHOT ON
ALTER database <database name> COLLATE SQL_Latin1_General_CP1_CS_AS

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

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

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

c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn for SQL Server 2005

or

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

Copy one of the following:
sqljdbc.dll(for 32 bit OS)
or 64sqljdbc.dll (for 64 bit OS Titanium based)
or x64sqljdbc.dll(for 64 bit OS Intel based)
from c:\Oracle\Middleware\wlserver_10.3\server\lib into
c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn for SQL Server 2005
c:\Program Files\Microsoft SQL Server\MSSQL10.<INSTANCE_NAME>\MSSQL\Binn for SQL Server 2008.

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

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\90\Tools\Binn\ for SQL Server 2005 and
c:\Program Files\Microsoft SQL Server\100\Tools\Binn\ for SQL Server 2008.

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

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.

For Windows 2008:

a. Select Start, then Programs, then Administrative Tools, then Component Services,
and  Computers,  and expand My Computer, and then Distributed Transaction Coordinator

b. Right Click Local  DTC and select Properties

c. Select the Security Tab and then select Enable XA Transactions

d. Click OK

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

For Windows 2003:

a. Select Start, then Programs, then Administrative Tools, then Component Services, and then Computers.

b Right click on My Computer and select Properties.

c. Select the MSDTC tab and click Security Configuration.

d. Select Enable XA Transactions

e. Click OK

Restart SQL Server (MSSQLSERVER) from Windows Services.

To stop the WebLogic Admin Server (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).

To stop the SOA Managed Server (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.

Stop Hyperion Foundation Services - Managed Server (Machine A) from the Services window.

To stop Financial Close Managment server (Machine B), select Start, then Programs, then Oracle EPM System, then epmsystem1, then Financial Close, then Stop Financial Close.

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)

To start the WebLogic Admin server on Machine A, 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.

If 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 on Machine A, 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 FDMEE Services on Machine B, select Start, then Programs, then Oracle EPM System, then epmsystem1, then FDM Enterprise Edition, and then Start ERPIntegrator.

Note: 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 on Machine A, 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.

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.

Note: You can also start it with startFinancialClose.bat. For example:
c:\Oracle\Middleware\user_projects\epmsystem1\bin\startFinancialClose.bat.