Installing and Configuring Oracle® Hyperion Financial Close Management 11.1.2.2.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 aMS 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.2.000
Oracle Hyperion Foundation Services Release 11.1.2.2.000
Oracle Hyperion Financial Close Management Release 11.1.2.2.000
Oracle SOA Suite 11g (11.1.1.6.0)
Oracle Repository Creation Utility 11g(11.1.1.6.0)
Oracle Data Integrator 11g (11.1.1.6.0)

Navigate to the installation folder for the Hyperion 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. Under Financial Close Management, select the components you want to install (Financial Close Management Web Application,
Account Reconciliation Management Web Application, or both).

d. Under FDM select ERP Integrator

e. Click Next.

Note: This example is for installing Foundation Services, Financial Close Manager, Account Reconciliation Manager, and ERPI only.
If you are installing other EPM products in distributed environment then you must install all of them to Machine A where
WebLogic Admin server will be running because it is required that 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,
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.

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 (in this example, the user name is fcm):

Example for MS SQl Server database (in this example, the user name is fcm and the database name is HSSdb):

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

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.
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 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.
• Expand FDM and select all the components.
• Expand Financial Close and select Deploy to application server and Configure Database
  for both Financial Close Management and Account Reconciliation.
  Do not select Deploy to SOA.
• Select Configure Content Management System location only if you are
  using a content management system.

Click Next.

Select Perform first-time configuration of database, enter the connection details for the
Financial Close Management, EPRI Integrator and Account Reconciliation database,
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.

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.
  
  
  

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.

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

Expand Financial Close, then Financial Close Management and select Deploy to SOA.
Also within Financial Close, expand Account Reconciliation and select Deploy to SOA,
Deploy to SOA for ERPI and click Next.

Ensure that none of the options under Hyperion Foundation are selected.

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 Foundation Services,
and then EPM System Configurator.

Accept the defaults and click Next.

Expand Hyperion Foundation and select only Configure Web Server.  Make sure both
FDM and Financial Close are not selected.  Click Next.

Accept the default Configure Web Server settings, 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 “Next” to navigate to the MSAD User Configuration Tab and enter 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_29\bin\

where C:\Oracle\Middleware\jdk160_29\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.

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 on Lock & Edit.

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 pools for the EDNLocalTxDataSource,
financialclose_datasource, and accountreconciliation_datasource services 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 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 ERP Integrator on Machine B, start the Hyperion ERP Integrator - 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 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) .

f. 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 on “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:

For Oracle, log in to SQLPlus as sys user and run the following:

a. Create user DEV_ODI_REPO identified by welcome1, default tablespace users, temporary tablespace temp;

b. Grant connect, resource to DEV_ODI_REPO;

For SQL Server, log in to Microsoft SQL Server Management Studio as sa user and do the following:

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

b. On New Database screen, enter the Database name you want to create for ODI Master repository. Owner is <default>.
Click OK to create the database.

c. A new database is created under the Database folder.

Open a command prompt window and navigate to <ODI Installation folder>\Disk1 and run the following command:
setup -jreLoc <jdk path>

where –jreLoc value is your JDK location

In this example, the jdk path is c:\Oracle\Middleware\jdk160_29.

At the Welcome page, click Next.

Select Skip Software Updates, and click Next.

Select ODI Studio, ODI SDK, and Standalone Installation, and click Next.

On the Prerequisite Checks screen, click Next.

On the Installation location screen, accept the default or click browse to navigate to the desired location, and click Next.

On the Repository Configuration screen, select Skip Repository Configuration and click Next.

On the Agent Details screen, enter ERPI_AGENT and 20910 and click Next.

On the Security Updates screen, clear the (I wish to receive security updates… checkbox and click Next

Click Yes on the warning screen

On the Installation Summary screen, click Install

On the Configuration Progress screen, click Next.

On the Installation Completed screen, click Finish.

To start ODI Studio, select Start, then Program Files, then Oracle, then Oracle Data Integrator, then Oracle ODI Studio.
Note: Launching ODI for first time may ask for migration of previous settings. You can ignore it and select No.

Select File, and then New.

Select Master Repository Import Wizard from New Gallery and Click “OK”.

The Master Repository Import Wizard comes up with empty fields for you to fill in.

On the Master Repository Import Wizard screen:

For Oracle Database

a. Enter the database connection details for ODI Schema you created.

- For JDBC Driver, select oracle.jdbc.OracleDriver

- For JDBC URL, use the following option; jdbc:oracle:thin:@<host>:<port>:<SID>

Example: jdbc:oracle:thin:@demoserverDB.example.com:1521:orcl

- For DBA User/DBA Password, use sys user and password

b. Enter 500 for New Repository ID (it is required to enter 500)

c. Enter the masterrep folder for Export Path. The masterrep folder can be found from the EPM installation location for ERPI such as “<EPM_ORACLE_HOME>/products/FinancialDataQuality/odi/11.1.2.2.00/masterrep”) 

d. Be sure to test the connection with the “Test Connection” button.

e. To start importing the master repository, click Finish.

For SQL Server Database

- For JDBC Driver, weblogic.jdbc.sqlserver.SQLServerDriver

- For JDBC URL, use the following option:
jdbc:weblogic:sqlserver://<host>:<port>;SelectMethod=cursor;databaseName=<ODIDatabase>; integratedSecurity=false

Example: jdbc:weblogic:sqlserver://demoserverDB.example.com:1433;SelectMethod=cursor;
databaseName=DEV_ODI_REPO;integratedSecurity=false

– For User/Password and DBA User/DBA Password, use sa user and password

b Enter 500 for New Repository ID (it is required to enter 500).

c. Enter the masterrep folder for Export Path. The masterrep folder can be found from the EPM installation location for ERPI such as “<EPM_ORACLE_HOME>/products/FinancialDataQuality/odi/11.1.2.2.00/masterrep”) 

d. Be sure to test connection with “Test Connection” button.

e. Otto start importing the master repository, click Finish.

Select File,and then New

On the New Gallery screen, select Create a New ODI Repository Login and click OK.

On the Repository Connection Information screen:

a. Enter the Login Name (e.g. Master Repository).

b. Enter the User and Password (User is SUPERVISOR and Password is SUNOPSIS). It is case sensitive.

c. Enter the Database Connection information.

d. Select the Master Repository Only option.

e. Test the DB connection with the Test button.

f. Click OK.

Example for Oracle:

Example for MS SQL Server:
URL sample: jdbc:weblogic:sqlserver://demoserverDB.example.com:1433;SelectMethod=cursor;databaseName=DEV_ODI_REPO;
integratedSecurity=false

Click the Connect To Repository link.

Log in to ODI Studio with the Master Repository login (SUPERVISOR / SUNOPSIS).

On ODI Studio, select the Topology tab and expand Repositories panel.

Right-click on Work Repositories and click on New Work Repository.

On the Create Work Repository wizard screen perform these steps:

a. Enter DB connection information (values are auto populated) and validate the connection with “Test Connection” button.

b. Click Next.

Example for Oracle:

Example for MS SQl Server:

Note that databaseName is your ODI database  in JDBC Url.

JDBC URL sample;
jdbc:weblogic:sqlserver://demoserverDB.example.com:1433;SelectMethod=cursor;databaseName=DEV_ODI_REPO;integratedSecurity=false

On the Specify ODI Work Repository Properties screen:

a. Enter 501 for Id (it is required to enter 501)

b. Enter WORKREP for Name (WORKREP is the recommended name).

c. Don’t enter anything for Password.

d. Click Finish

When ODI asks whether to create a login for work repository, click Yes and create it with name WORKREP (WORKREP is the recommended name)..

Log off from Master repository (select ODI, then Disconnect  “Master Repository”).

Click the Connect To Repository link

Log in to ODI Studio with WORKREP (SUPERVISOR/SUNOPSIS).

Go to the Topology tab and click on Import.

On the Import Selection screen, select “Import the Work Repository” and click OK;

On the Import work repository screen perform these steps:

a. Select the Import Mode as Synonym Mode Insert_Update option

b. Select the Import from a Folder option

c. Enter the workrep folder ( The workrep folder can be found from EPM installation location for ERPI, for example “<EPM_ORACLE_HOME>/products/FinancialDataQuality/odi/11.1.2.2.00/workrep”).

d. Click OK

When asked for your confirmation, click “Yes” (You need to repeat the confirmation several times for different IDs).

When the Import report screen is shown, scroll to bottom of the screen, verify that nothing is present under Not Imported Objects,
and click Close.

If you're not already logged in to ODI Studio as WORKREP (SUPERVISOR/SUNOPSIS) do so now.

Go to Topology tab and expand the Physical Architecture panel

Expand the desired folder such as Oracle (It has Physical servers for ARM, ERPI, EBS, and Peoplesoft)

(For SQLServer, there are ARM and ERPI Physical servers. EBS and Peoplesoft are only supported under Oracle)

Double-click to open the desired server (e.g. ARM_DATA_SERVER).

For Oracle, on the Definition screen, enter the user with DBA privileges for your ARM schema.

Click the JDBC tab on the left side of the ARM_DATA_SERVER window, and enter the JDBC Driver and URL.
To test the connection, above the Definition tab, click Test Connection.

Example for Oracle

JDBC URL sample:; jdbc:oracle:thin:@demoserverDB.example.com:1521:orcl

Example for MS SQL Server - the databaseName is for the FCM database.

JDBC URL sample:
jdbc:weblogic:sqlserver://demoserverDB.example.com:1433;SelectMethod=cursor;databaseName=arm;integratedSecurity=false

When you are asked to save and continue then click OK.

Choose No Agent to test the connection (note that you haven’t configured ODI Agent yet) and click Test.

Expand the desired server (ARM_DATA_SERVER):

For Oracle, double click to open Physical schema (ARM_DATA_SERVER.Schema)

For MS SQl Server,double-click to open Physical schema (ARM_DATA_SERVER_MSSQL.Database.Owner).

On the Definition screen:

For Oracle:

Select the physical schema (for example, the FCM schema created from the EPM Configurator) for Schema(Schema)
and Schema(Work Schema).

For SQLServer:

Select Database (e.g. FCM database created from EPM Configurator) and Owner (e.g. dbo).

To save the changes you made to the Physical schema, click Save.

Repeat the same steps you did for ARM_DATA_SERVER for ERPI_DATA_SERVER and other Physical servers as needed.

Example for EBS and Peoplesoft DB connections:

• Create EBS_Data_Server (apps/apps)

      JDBC Driver: oracle.jdbc.OracleDriver
      JDBC URL: jdbc:oracle:thin:@demoserver:1573:fz5mq206

• Create PeopleSoft_Data_Server (emdbo/emdbo)

      JDBC Driver: oracle.jdbc.OracleDriver
      JDBC URL: jdbc:oracle:thin:@demoserver:1521:ep900sba

Expand the Contexts panel from the Topology tab and double click on Global context (Note that you need to use Global;
not ARMCONTEXT).

Select the Schemas tab.

Note: By default, the Global context has a map for all predefined schema,
but you need to choose the physical schema that you configured.

Choose a Physical schema you have configured from the Physical Schemas pull down menu .

For example;
ARM_TGT should map to ARM_DATA_SERVER.<Your ARM schema name>
AIF_TGT should map to ERPI_DATA_SERVER.<Your ERPI schema name>
AIF_FILE should map to ERPI_FILE_SERVER.#AIF_FILE_PROJECT.p_file_path

If you need to use an EBS source then EBS_APPS should map to 
                      EBS_DATA_SERVER.<your EBS schema name>

Click Save if any changes were made.

Note: The last value selected from pull down menu is not saved so change the selection to
some other schema and make sure all the selections are saved correctly.

Set the following parameters in the odiparms.bat under the
“<Oracle_Home>\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin” folder:

Oracle Example:

set ODI_MASTER_DRIVER=oracle.jdbc.OracleDriver

set ODI_MASTER_URL=jdbc:oracle:thin:@demoserverDB.example.com:1521:orcl   (add your ODI master repository URL)

set ODI_MASTER_USER=DEV_ODI_REPO   (add your ODI master schema username)

set ODI_MASTER_ENCODED_PASS=aYyHdZSEixcjzk2RGMi.iy (to get the encrypted password, see the instructions below)

set ODI_SECU_WORK_REP=WORKREP    ( your work repository name)

set ODI_ADDITIONAL_CLASSPATH=%ODI_HOME%\..\..\oracledi.sdk\lib\*

MS SQL Server Example:

set ODI_MASTER_DRIVER=weblogic.jdbc.sqlserver.SQLServerDriver

set ODI_MASTER_URL=jdbc:weblogic:sqlserver://demoserverDB.example.com:1433;SelectMethod=cursor;databaseName=DEV_ODI_REPO;integratedSecurity=false   (add your ODI master repository URL. Note that databaseName is for your ODI database)

set ODI_MASTER_USER=sa   ( sa user)

set ODI_MASTER_ENCODED_PASS=aYyHdZSEixcjzk2RGMi.iy (to get the encrypted password, see the instructions below)

set ODI_SECU_WORK_REP=WORKREP    ( your work repository name)

Save and close the odiparms.bat file.

It is required to get an encrypted password for ODI_MASTER_ENCODED_PASS in odiparms.bat:

a. In <Oracle_Home>\product\11.1.1\Oracle_ODI_1\oracledi\agent\bin run encode.bat from
a command prompt with a parameter; e.g. encode welcome1 (where welcome1 is ODI schema password).

b. Copy the encrypted password output and add it to value of ODI_MASTER_ENCODED_PASS in odiparms.bat

In the same directory run agent_ERPI_AGENT.bat to start ODI Agent. Look for the following message: “Agent ERPI_AGENT started."

Edit the wls-infra.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-infra.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)

For MDS schema information (You should have already setup your MDS schema from RCU configuration step):

• databaseType=ORACLE/MSSQL  (Choose database type for your MDS schema: ORACLE or MSSQL)
• hostName=dbHostName                  (Replace dbHostName with host name for your MDS schema)
• port=dbPortNumber                        (Replace dbPortNumber with port number for your MDS schema)
• schemarUserName=dbUserName    (Replace dbUserName with username for your MDS schema, E.g. DEV_MDS)
• schemaPassword=dbUserPassword (Replace dbUserPassword with password for your MDS schema)
• dbName= dbService                          (Replace dbService  with SID/DBName for your MDS schema)
• partitionName=erpi_adfConn            (Don’t need to change it)

Note: If you are not sure, then you can get above information from the mds_owsm datasource from the WebLogic
Admin console (under Services, then Data Sources, then mds_owsm, and then Connection Pool screen.

For Account Reconciliation Manager configuration:

• dataLoadServiceWSDL=http://localhost:8700/ARM-DataModel-context-root/DataloadAMService?wsdl         (change localhost:8700 with your ARM server host and port) 
• clientSecPolicyForARM stays the same.

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

a.Open a command prompt.

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

c. Run wlsConfigMds.bat file and ensure that the script runs successfully

Restart the Hyperion ERP Integrator-Web Application service.
Note: You should start the ERPI service from Windows Services.

Check the status of ERPI server:

Log in to WebLogic admin console (http://<host>:7001/console
where <host> is the machine name for where WebLogic admin server is running) and go to the Domain Structure area,
click Environment, and then Servers.You should wait until ErpIntegrator server status is changed to RUNNING.

Run the wlsConfigOWSM.bat file (Machine B):

From the same command prompt, run wlsConfigOWSM.bat file and ensure that the script runs successfully

Restart ERPI Service and Admin Server.

Note: You should start the ERPI service from Windows Services.

Check the status of ERPI server:

Log in to WebLogic admin console (http://<host>:7001/console
where <host> is the machine name for where WebLogic admin server is running) and go to the Domain Structure area,
click Environment, and then Servers.You should wait until ErpIntegrator server status is changed to RUNNING.

To set Log On As for the ERPI service, right click on the service and click on Properties.

On Log On screen, select This account and provide username and password and click OK

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 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 three databases: one for SOA, one for Financial Close Management, and one for Shared Services.
Set the login created earlier as the owner of the three 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 - Manager Server (Machine A) from the Services window.

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

Stop the Hyperion ERP Integration - Web Application (Machine B) service in the Services window.

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

To start ERP Integrator on Machine B, start the Hyperion ERP Integrator - 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 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.