Have access with sysdba privileges to an Oracle 11g ( 11.1.0.7 or higher) 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.1
• Oracle Hyperion Foundation Services Release 11.1.2.1
• Oracle Hyperion Financial Close Management Release 11.1.2.1
• Oracle SOA Suite 11g (11.1.1.4)
• Oracle Repository Creation Utility 11g(11.1.1.2.1)
• Fusion Middleware Patch 11063511
• Fusion Middleware Patch 11864201
  

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

Select a language, and click Next.

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 Choose components individually, and click Next.

On the Product Selection screen, select Foundation Components and Financial Close Management Web Application, 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 then 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 the location of the JRE. The default location is c:\oracle\middleware\jdk160_21\jre.

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.

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.

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 information, 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.properties 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 stop 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 is available from My Oracle Support at http://metalink.oracle.com.:

• 11063511 - SPORADIC MISSING OF SUBJECT IN BUSINESS EVENT HEADER.
• 11864201 - PSE FOR MLR BUG 11864201 ON TOP OF 11.1.1.4.0 (PSE #536496)
  

Note: Before applying the patches, shut down SOA server and all other manager servers. For patch 11063511, set the ORACLE_HOME environment variable to c:\Oracle\Middleware\oracle_soa1. For patch 11864201, set ORACLE_HOME to c:\Oracle\Middleware\oracle_common.

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

Select Create a new EPM Oracle instance, 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.

Accept the default options under Hyperion Foundation. For Financial Close, select Deploy to application server and Configure Database. Do not select Deploy to SOA. Select Configure Content Management System location only if you are using a content management system. Click Next.

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

Select Perform first-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, 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 Enterprise Content Management with your Financial Close Management application, enter the URL for Oracle Enterprise 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.

.

Select Modify an existing Oracle EPM instance, and click Next.

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.

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.

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 table, click wsm-pm.

Select the Targets tab.

Select wsm-pm, and click Change Targets.

In the Clusters Area, select Foundation Services, and click Yes.

In the Target Assignments table, verify that Foundations Services is added to Current Targets for wsm-pm.

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

In the Domain Sources table, click mds-owsm and select the Targets tab.

In the Clusters Area, select Foundation Services, 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 Domain Structure area, click Security Realms.

Click myrealm.

Select the Providers tab..

Click New.

Configure you authentication provider:

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

Click OK.

In the Authentication Providers list, click OID, MSAD, or SunOne.

Select the Provider Specific tab.

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

Click Save.

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

Select the Providers tab.

In the Authentication Providers list, click OID, MSAD, or SunOne.

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.

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.

In the Driver-Specific Configuration section, 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.

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

set PATH=%PATH%;C:\Oracle\Middleware\jdk160_21\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 enter 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 administrator name and password to login.

In the navigation pane, expand 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 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.

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 files to the <domain>/config/fmwconfig folder, where <domain> is the domain you created using the SOA configuration tool.

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

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

Click More SOA Infra Advanced Configuration Properties.

In the Attributes list, click EdnJmsMode.

In the Value list, select True, and click Apply.

This setting does not take effect until SOA Server is restarted.

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.

Click myrealm.

Select the Providers tab..

Click New.

In the Name tex box enter OAMIdentityAsserter, and in the Type list, select OAMIdentityAsserter.

Click OK.

In the Authentication Providers list, click Reorder.

Order the authentication providers as follows:

MSAD, OID, or SunOne (depending which you are using)
OAM IdentityAsserter
Default Authenticator
Default IdentityAsserter .

Click OK.

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.

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

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

In the Domain Structure area, expand Services, then JTA.

In the Timeout Seconds text box, replace the default value of 30 with 300.

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 Financial Close Management Services, select Start, then Programs, then Oracle EPM System, then Financial Close, then Start FinancialClose.

Install SQL Server

Create three databases: one for SOA, one for Financial Close Management, and one for Shared Services.

Create a user with the db_owner role and make the user the owner of the three databases.

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

ALTER database <database name> SET READ_COMMITTED_SNAPSHOT ON

ALTER database <database name> COLLATE SQL_Latin1_General_CP1_CS_AS

Modify the properties of the database for Financial Close Management by using the following command:

ALTER database <database name> SET ALLOW_SNAPSHOT_ISOLATION ON

Run the Repository Creation Utitlity to create the SOA-INFRA schemas for the SOA database.

Copy instjdbc.sql and 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 wlserver_10.3\server\lib into C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Inn for SQL Server 2005 or C:\Program Files\Microsoft SQL Server\MSSQL10.<INSTANCE_NAME>\MSSQL\Binn for SQL Server 2008.

Rename the 64sqljdbc.dll or x64sqljdbc.dll to sqljdbc.dll after copying.

Run the following command from the command prompt:

SQLCMD.EXE -S "DB_HOST\INSTANCENAME" -U SA -P SA_PASSWORD -i instjdbc.sql -o LOG_FILE

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

Note: In the above command "DB_HOST\INSTANCENAME" is the server name used to connect SQLServer 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

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

Right My Computer and select Properties.

Select the MSDTC tab and click Security Configuration.

Select Enable XA Tansactions.

Click OK.

Install and configure SOA Suite.

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.

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

In the Datasource table, delete EDNDataSource and EDNLocalTxDataSource.