Have access with sysdba privileges to an Oracle 11g ( 11.1.0.7) database.

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

Have access to the installation files for the following software:

• Oracle Hyperion Enterprise Performance Management System Installer Release 11.1.2
• Oracle Hyperion Foundation Services Release 11.1.2
• Oracle Hyperion Financial Close Management Release 11.1.2
• Oracle SOA Suite 11g (11.1.1.2)
• Oracle Repository Creation Utility 11g(11.1.1.2.1)
• Fusion Middleware Patch 9538640
  
• Fusion Middleware Patch 9201797
  
• Fusion Middleware Patch 9050722

Navigate to the installation folder for the Hyperion software and click installtool.cmd.

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 Product Selection screen, select Foundation Services and Financial Close, and click Next.

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 click rcu.bat.

On the Welcome screen, click Next.

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

On the Database Connection Details screen, enter the database connection details. Be sure to select SYSDBA as the role.

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, select Metadata Services, SOA Infrastructure, and User Messaging Service, and click Next.

At the prerequisites confirmation prompt, click OK.

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

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

At the confirmation prompt, click OK.

At the completion prompt, click OK.

On the Summary screen, click Create.

On the Completion Summary screen, click Close.

Navigate to the Disk1 folder in the SOA Suite installation directory, and click Setup.exe.

At the JRE/JDK location prompt, enter c:\oracle\middleware\jdk160_11\jre. The default location for the Java run-time environment is c:\oracle\middleware\JDK160_11\JRE.

The default location for the JRE is c:\oracle\middleware\JDK160_11\JRE.

On the Welcome screen, 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.

On the Installation Summary screen, click Install. During the installation process, you may be prompted to browse to the Disk2 and the Disk3 folders to continue the installation.

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.

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.

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

On the Configure User Name and Password screen, enter a user name and password for the WebLogic domain administrator. 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, select Production 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, using the schema password that you entered in the Repository Creation Utility. When finished, click Next.

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.

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 domain you created in the SOA configuration tool.

Enter the Web Logic admin user name and password when prompted.

To start the SOA managed server, enter the following command at a DOS prompt:
c:\oracle\middleware\user_projects\domains\<domain>\bin\startmanagedweblogic.cmd soa_server1,
where <domain> is the domain you created in the SOA configuration tool.

Enter the Web Logic admin user name and password when prompted.

In Windows explorer, create a directory named security as a subdirectory of c:\oracle\middleware\user_projects\domains\<domain>\servers\AdminServer,
where <domain> is the domain you created in the SOA configuration tool.

In a text editor such as Notepad, create a file named boot.properties with the following content:

username=<Web Logic admin user>
password=<Web Logic admin password>

where <Web Logic admin user> is the admin user for Web Logic and <Web Logic admin password> is the password.

Save boot.properites in c:\oracle\middleware\user_projects\domains\<domain>\servers\AdminServer\security,
where <domain> is the domain you created in the SOA configuration tool.

In Windows explorer, create a directory named security as a subdirectory of c:\oracle\middleware\user_projects\domains\<domain>\servers\soa_server1.

In a text editor such as Notepad, create a file named boot.properties with the following content:

username=<Web Logic admin user>
password=<Web Logic admin password>

where <Web Logic admin user> is the admin user for Web Logic and <Web Logic admin password> is the password.

Save boot.properties in c:\oracle\middleware\user_projects\domains\<domain>\servers\soa_server1\security.

To stopt the WebLogic Admin Server, select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, and then Stop Admin Server, where <domain> is the domain you created in the SOA configuration tool.

To stop the SOA managed server, enter the following command at a DOS prompt:
c:\oracle\middleware\user_projects\domains\<domain>\bin\stopmanagedweblogic.cmd soa_server1,
where <domain> is the domain you created in the SOA configuration tool.

Download and follow the instructions for Installing the following patches, which are available from My Oracle Support at http://metalink.oracle.com.:

• 9538640 - PS1 CUMULATIVE MLR2 (RT) BASED
  JDEVADF_11.1.1.2.PS1_GENERIC_100329.1609.5562
  
• 9201797 - APPS-BLK: MOVE WORKLIST LINK TO BOTTOM OF EMAIL NOTIFICATION
  
• 10225883 - MERGE REQUEST ON TOP OF 11.1.1.2.0 FOR BUGS 9050722 9541100
  

Note: For Patch 9201797 and 10225883, set ORACLE_HOME to ../ Oracle/Middleware/Oracle_SOA1. For Patch 9538640, set ORACLE_HOME to ../ Oracle/Middleware/oracle_common.

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

Select all available options under Hyperion Foundation, then select all tasks under Financial Close Management except Deploy to SOA, and click Next.

Enter the database connection details for the Shared Service database.

Select Create Windows Services for configured components, and click Next.

Select Perform 1st-time configuration of database, enter the connection details for the Financial Close Management database, and click Next.

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

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.

If you want to integrate Oracle Content Management with your Financial Close Management application, enter the URL for Oracle Content Management, 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.

To start the SOA managed server, enter the following command at a DOS 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.

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

.

Expand Financial Close, select Deploy to SOA, 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.

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

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 WebLogic Server Administration Console, under Domain Structure, click Deployments.

In the Deployments area, click Install.

In the Current Location field, browse to c:\Oracle\Middleware\EPMSystem11R1\products\FinancialClose\AppServer\InstallableApps\common.

Select FCCAlertNotification.ear, and click Next.

Select Install this deployment as an application, and click Next.

Under Available targets for FCCAlertNotification, select soa_server1, and click Next.

Do not target the notification EAR files to any servers other than soa_server1.

On the Optional Settings screen, under Source accessibility, select Copy this application onto every target for me, and click Next.

Click Finish.

Repeat steps 6 to 11 to install FCCNotification.ear and FCCTaskNotification.ear.

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

In the Domain Structure area, select Services, then JDBC, and then DataSources.

Click New.

In the Name text box, enter EDNLocalTxSource, and in the JNDI Name text box enter jdbc/EDNLocalTxSource.

In the Database Driver list, select Oracle's Driver (Thin) for Service Connections, and click Next.

On the Transaction Options screen, clear the Supports Global Transactions check box, and click Next.

Enter your database connection information for the soa_infra schema (you created this schema earlier in the Repository Creation Utility), and click Next.

Click Test Connection, and when the connection is verified, click Next.

In the Cluster area, select Financial Close, and click Finish.

In the Data Source list, click New.

In the Name text box enter EDNSource, and in the JNDI Name text box, enter jdbc/EDNSource.

In the Database Driver list, select Oracle's Driver (Thin XA) for Service Connections, and click Next.

On the Transaction Options screen, leave the default settings, and click Next.

Enter your database connection information for the soa_infra schema (you created this schema earlier in the Repository Creation Utility), and click Next.

Click Test Connection, and when the connection is verified, click Next.

In the Clusters area, select Financial Close, then click Finish..

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

In the Domain Structure area, select Services, then JDBC, and then DataSources.

Click finacialclose_datasource.

Select the Targets tab.

Select soa_server1, and click Save.

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

Expand Environment, and then Servers.

Click soa_server1.

In the Listen Address text box, enter the host name for the SOA server, and click Save.

Expand Environment, then Machines, and click Local Machine..

Select the Node Manager tab.

In the Listen Address text box, enter the host name for the SOA server, and click Save.

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

In the Domains Structure area, click Security Realms.

Click myrealm.

Select the Providers tab..

Click New.

For Oracle Internet Directory, in the Name text box enter OID, and select Oracle Internet Directory Authenticator from the Type list.For Oracle Active Directory, in the Name text box enter MSAD, and select ActiveDirectoryAuthenticator from the Type list.

Click OK.

In the Authentication Providers list, click OID or MSAD.

Select the Provider Specific tab.

Enter the principal user and credentials, and modify any other settings as required for the provider.

Click Save.

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

Select the Providers tab.

Click Reorder.

Move OID or MSAD to the second position in the list (after DefaultAuthenticator).

Click OK.

In the Authentication Providers list, click OID or MSAD.

In the Control Flag list, select Sufficient.

Click Save.

Click Logout.

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

Navigate to the folder c:\oracle\middleware\user_projects\<domain>\<domain>\config\fmwconfig.

Create a backup of the jps-config.xml file.

Open the jps-config.xml file in a text editor.

Add an entry for the service instance provider to the serviceinstances tag, replacing the text in italics with the information for your provider

For Oracle Internet Directory:

<serviceInstance provider="idstore.ldap.provider" name="idstore.OID">
<property value="yourSubscriberName" name="subscriber.name"/>
<property value="OID" name="idstore.type"/>
<property value="username:password" name="cleartext.ldap.credentials"/>
<property value="ldap://hostname:port" name="ldap.url"/>
<property value="uid" name="username.attr"/>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>User Base DN</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>Group Base DN</value>
</values>
</extendedProperty>
</serviceInstance>

For Active Directory:

<serviceInstance provider="idstore.ldap.provider" name="idstore.AD">
<property value="yourSubscriberName" name="subscriber.name"/>
<property value="ACTIVE_DIRECTORY" name="idstore.type"/>
<property value="username:password" name="cleartext.ldap.credentials"/>
<property value="ldap://hostname:port" name="ldap.url"/>
<property value="cn" name="username.attr"/>
<extendedProperty>
<name>user.search.bases</name>
<values>
<value>User Base DN</value>
</values>
</extendedProperty>
<extendedProperty>
<name>group.search.bases</name>
<values>
<value>Group Base DN</value>
</values>
</extendedProperty>
</serviceInstance>

Add a reference to your newly defined service instance to the <jpsContext name="default"> tag, as in the following example:

<jpsContext name="default">
<serviceInstanceRef ref="credstore" />
<serviceInstanceRef ref="keystore" />
<serviceInstanceRef ref="policystore.xml" />
<serviceInstanceRef ref="audit" />
<serviceInstanceRef ref="idstore.OID" />
</jpsContext>

Save the file.

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

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

.

When prompted, enter the WebLogic administrator ID and password.

Expand User Messaging Service.

Right-click usermessagingdriver-email(soa_server1) and select Email Driver Properties.

Enter the information for you email server, and select Clear Text for the password type.

Click Apply.

In the left panel, expand the SOA folder, right-click soa-infra (soa-server1), click SOA Administration,
and select Workflow Notification Properties.

In the Notification Mode list, select Email.

In the Email:From Address text box, enter a valid e-mail address.

Click Apply.

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

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

Stop all managed servers that are running(all Web applications that you deployed, including
Foundation Services, Financial Close Management, and any other managed servers in the domain).

Make a backup copy of setDomainEnv.cmd, which is in the BIN folder of the WebLogic domain folder that you created.
In a distributed environment, perform this step on each machine.

Open setDomainEnv.cmd in a text editor and add the following entries after the LONG_DOMAIN_HOME environment variable. Insert a
blank line between the existing section and the new content. Update the locations to point to the appropriate path on your machine, replacing <domain> with the domain you created with the SOA configuration tool.:
set EPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1
set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1

For example:

set LONG_DOMAIN_HOME=C:\Oracle\Middleware\user_projects\domains\<domain>

set EPM_ORACLE_HOME=C:\Oracle\Middleware\EPMSystem11R1

set EPM_ORACLE_INSTANCE=C:\Oracle\Middleware\user_projects\epmsystem1

• Be sure to insert a blank line before and after the added text.
• Be sure there are no trailing spaces at the end of each line of added text.
• Also include a blank line between the entries for EPM_ORACLE_HOME and EPM_ORACLE_INSTANCE.

In setDomainEnv.cmd, after the last instance that sets POST_CLASSPATH, add epm.jar to the POST_CLASSPATH as follows:
set POST_CLASSPATH=%POST_CLASSPATH%;%EPM_ORACLE_HOME%\common\jlib\11.1.2.0\epm.jar

Save and close setDomainEnv.cmd.

Copy EPMIdentityAsserter.jar from EPM_ORACLE_HOME/common/SharedServices/
11.1.2.0/lib to MIDDLEWARE_HOME/wl_server10.3/server/lib/mbeantypes.

In a distributed environment, perform this step on each machine.

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

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

In the Domain Structure area, click Security Realms.

Click myrealm.

Select the Providers tab.

Click New.

Enter EPMAsserter in the Name text box, and select EPMIdentityAsserter from the Type list.

Click OK.

Reorder the providers list so that EPMAsserter is in the third position.

In the providers list, click Default Authenticator.

In the Control Flag list, select Sufficient.

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

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

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

In the Domain Structure area, click Security Realms.

From the Available Realms list, click myrealm.

Select the Roles and Policies tab.

In the Available Role list, expand Global Roles, and click Roles.

Click New.

Enter valid_users for the role name.

Click OK.

In the Global Roles list, click valid_users.

In the Role Conditions area, click Add Conditions.

In Predicate List, select Allow access to everyone.

Click Finish, and then Save

At a dos prompt, enter the following command to add the JDK to the path:

set PATH=%PATH%;C:\Oracle\Middleware\jdk160_11\bin\

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

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

.

Enter your Weblogic adminstrator name and password to login.

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

Select WebLogic Domain, then Security, and then Security Provider Configuration.

In the Keystore section at the bottom of the page, click Configure.

In the Keystore Path text box, enter the path and name for the keystore you created.

In the Signature Key and Encryption key text boxes, enter an alias and password for the signature and encryption keys.

Click OK.

For a distributed environment, the keystore (default-keystore.jks) and the cwallet.sso files must be copied to each Web application server within the environment. Copy these file to the <domain>/config/fmwconfig folder, where <domain> is the domain you created using the SOA configuration tool.

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

In the Domain Structure area, expand Environment, then Services, then JDBC, and then Datasources.

In the Name list, click EDNSource.

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 EDNLocalTxSource and financialclose_datasource services to 150.

In the Name list, click SOADataSource.

Select the Transaction tab.

Select Set XA Transaction Timeout and verify that the XA Transaction Timeout value is 0.

Click Save.

To start the WebLogic Admin server, select Start, then Programs, then Oracle WebLogic, then User Projects, then <domain>, and then Start Admin Server.

To start Foundation Services, select Start, then Programs, then Oracle EPM System, then Foundation Services, and then Start FoundationServices.

To start the Oracle HTTP server, select Start, then Programs, then Oracle Web Tier Instance, and then Start Oracle HTTP server.

To start the SOA managed server, enter the following command at a DOS 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.

To start Foundation Services, select Start, then Programs, then Oracle EPM System, then Financial Close, then Start FinancialClose.