Installing and Configuring Oracle® Hyperion Financial Close Management 11.1.2.3.000 With SOA Clustering

Ensure that the IPv6 Network is properly working if this feature is enabled on your machines – see Appendix D: IPv6 Network.

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

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

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

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

Log on to sqlplus as a user with sysdba privileges. For example:
sqlplus "/ as sysdba"

Grant select on sys.dba_pending_transactions to soaha_soainfra.

Grant force any transaction to soaha_soainfra.

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

Note: Throughout this tutorial, for Linux versions of command, consult Appendix D: Linux Commands.

Select a language, and click OK.

On the Welcome screen, click Next.

On the Destination screen, select the location for the Middleware Home directory, and click Next.
The default directory is c:\oracle\middleware.

On the Installation Type screen, select New installation, and click Next.

On the Product Selection screen:

a. Deselect Check All.

b. Under Foundation Services select Foundation Components.

c. Select Financial Close Management.

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

e. Click Next.

On the Confirmation screen, click Next.

On the Summary screen, click Finish.

Open a command prompt and navigate to the Disk1 folder under the SOA Suite installation directory and enter the following command.
Setup.exe -jreLoc c:\Oracle\Middleware\jdk160_35 (if your JRE location is different than the example, replace with your 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 configuration using config.cmd, or for Linux ./config.sh. 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 then select Oracle Enterprise Manager, Oracle WSM Policy Manager 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:
Host Name: Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
DBMS/Service: The database service name that you must use is available in c:\app\<user>\product\11.2.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
Port: 1521
Schema password: Password for all schemas that you entered in the Repository Creation Utility.

Example for MS SQl Server database:
Host Name: Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
DBMS/Service: SOAdb
Port: 1433
Schema password: Password for all schemas that you entered in the Repository Creation Utility.

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

In the Select Optional Configuration screen, select Administration Server; Managed Servers, Clusters, and Machines; and Deployments and Services.

On the Configure the Administration Server screen, enter the following values:

• Name: Admin Server
• Listen Address: All local addresses
• Listen Port: 7001
• SSL Listen Port: N/A
• SSL Enabled: Unchecked

On the Configured Manage Servers screen, click Add to define the two servers below, and then click Next.

• Name: WLS_WSM1
• Listen Address: SOAHOST1.example.com
• Listen Port: 7001
• SSL Listen Port: N/A
• SSL Enabled: Unchecked

• Name:WLS_WSM2
• Listen Address: SOAHOST2.example.com
• Listen Port: 7001
• SSL Listen Port: N/A
• SSL Enabled: Unchecked

On the Configure Clusters screen, click Add to enter the cluster details below, and then click Next.

• Name: WSM-PM_Cluster
• Cluster Messaging Mode: unicast
• Multicast Address: n/a
• Multicast Port: n/a
• Cluster Address: Leave blank

In the Assign Servers to Clusters screen, assign both WLS_WSM1 and.WLS_WSM2 to the WSM_PM cluster, and then click Next.

On the Configure Machines screen, click Add to the machines below, and then click Next.

• Name: SOAHOST1; Node Manager Listen Address: SOAHOST1.example.com
• Name: SOAHOST1; Node Manager Listen Address: SOAHOST2.example.com
• Name: ADMINHOST; Node Manager Listen Address: localhost

In the Assign Servers to Machines screen, make the assignments below, and then click Next.

1. Assign WLS_WSM1 to SOAHOST1.
2. Assign WLS_WSM2 to SOAHOST2.
3. Assign ADMINSERVER to ADMINHOST.

On the Target Deployments to Clusters or Servers screen, perform the following:

1. In the Target list select WSM_PM Cluster, and on the right select wsm=pm and oracle.wsm.seedpolicies.
2. In the Target list select AdminServer, and on the right de-select wsm=pm and oracle.wsm.seedpolicies.
3. Verify that, with the exception of wsm-pm and oracle.wsm.seedpolicies, all other application and seedpolicies are targeted only to Admin Server libraries.

On the Target Deployments to Clusters or Servers screen, in the Target list select AdminServer, and in the right de-select wsm=pm and oracle.wsm.seedpolicies.Verify that, with the exception of wsm-pm and oracle.wsm.seedpolicies, all other application and seedpolicies are targeted only to Admin Server libraries, and then click Next.

On the Target Services to Clusters or Servers screen, perform these steps to make sure the JOC-Shutdown and JOC-Startup services are targeted to the WSM-PM_Cluster and are not targeted to Admin Server:

1. On the left select WSM_PM_Cluster, and then on the right select JOC-Shutdown and JOC-Startup.
2. On the left select Admin Server, and then on the right de-select JOC-Shutdown and JOC-Startup.
3. Verify that mds-owsm is targeted to both Admin Server and WSM-PM_Cluster.
4. Verify that all remaining services are targeted to the Admin Server.
5. Click Next.

On the Configuration Summary screen, click Create.

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

Navigate to ORACLE_COMMON_HOME/common/bin directory.

The default location for windows is c:/Oracle/Middleware/oracle_common.
The default location for linux is $HOME/Oracle/Middleware/ oracle_common.

Run setNMProps to set the StartScriptEnabled property to 'true' before starting Node Manager.

For Windows: setNMProps.cmd
For Linux: SOAHOST1> ./setNMProps.sh

A message displays saying that the required properties file was copied.

Navigate to the WEBLOGIC_HOME/common/bin directory.

The default location for Windows is c:/Oracle/Middleware/wlsserver_10.3/server/bin
The default location for Linux is $HOME/Oracle/Middleware/ /wlsserver_10.3/server/bin

Run startNodeManager script to Start Node Manager:

For Windows:startNodeManager.cmd
For Linux: SOAHOST1> ./startNodeManager

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 the server 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 the command prompt box.

In a browser, go to http://SOAHOST1VHN0:7001/console.

Log in as the administrator.

Verify that the WLS_WSM1 and WLS_WSM2 managed servers are listed.

Verify that the WSM-PM_Cluster cluster is listed.

Verify that you can access Oracle Enterprise Manager at http://SOAHOST1VHN0:7001/em.

Log in to EM Console with the username and password.

Log in to Oracle Enterprise Manager Fusion Middleware Control with the username and password.

On the navigation tree on the left, expand Farm_<domain_name>, WebLogic Domain, and then <domain_name>, and select WSM_PM_Cluster.

Click Apply JRF Template on the right.

Wait for the confirmation message to appear on the screen.
This message should confirm that the JRF Template has been successfully applied to the WSM-PM_Cluster cluster.

Log in to Oracle WebLogic Server Administration Console and click Lock and Edit.

Expand the Environment node in the Domain Structure window.

Click Servers. The Summary of Servers page is displayed.

Select AdminServer(admin) in the Names column of the table. The Settings page for AdminServer(admin) appear.

Click the SSL tab.

Click Advanced.

Set Hostname Verification to None.

Click Save.

Repeat the above steps for the WLS_WSM1 and WLS_WSM2 servers.

Save and activate the changes.

Restart the Administration and WLS_WSM1 servers.

Start the WLS_WSM1 managed server using the Oracle WebLogic Server Administration Console as follows:

1. Expand the Environment node in the Domain Structure window.
2. Choose Servers. The Summary of Servers page appears.
3. Click the Control tab.
4. Select WLS_WSM1 and then click Start.

Verify that the server status is reported as "Running" in the Admin Console, then access http://SOAHOST1:7010/wsm-pm.

Click Validate Policy Manager. A list of policies and assertion templates available in the data store appear.
Note: The configuration is incorrect if no policies or assertion templates appear.

Navigate to the ORACLE_COMMON_HOME/common/bin directory.

The default for location for < ORACLE_COMMON_HOME> is c:/Oracle/Middleware/oracle_common.
The default location for < ORACLE_COMMON_HOME> on Linux is $HOME/Oracle/Middleware/ oracle_common.

Run the pack command on SOAHOST1 to create a template pack as follows:
For Windows: pack -managed=true -domain= MIDDLEWARE_HOME \user_projects\domains\<domainName> -template=c:\<domainTemplate>.jar -template_name=<domain Template Name>
For Linux: SOAHOST1> ./pack.sh -managed=true -domain=<MIDDLEWARE_HOME>/user_projects/domains/domain_name -template=<domainTemplate>.jar -template_name=<domain Template Name>

The default for <MIDDLEWARE_HOME> for Windows is c:/Oracle/Middleware.
The default for <MIDDLEWARE_HOME> for Linux is $HOME/Oracle/Middleware.

Copy the template file created on SOAHOST1 to ORACLE_COMMON_HOME/common/bin on SOAHOST2.

Login to the SOAHOST2 machine.

Navigate to the ORACLE_COMMON_HOME/common/bin directory.

Run the unpack command on SOAHOST2 to unpack the propagated template:
For Windows: unpack -domain=MIDDLEWARE_HOME/user_projects/domains/<domain_name> -overwrite_domain=true -template=<domainTemplate>.jar
For Linux: SOAHOST2> ./unpack.sh -domain=MIDDLEWARE_HOME/user_projects/domains/<domain_name> -template==<domainTemplate>.jar

Navigate to ORACLE_COMMON_HOME/common/bin directory.

The default location for windows is c:/Oracle/Middleware/oracle_common.
The default location for linux is $HOME/Oracle/Middleware/ oracle_common.

Run setNMProps to set the StartScriptEnabled property to 'true' before starting Node Manager.

For Windows: setNMProps.cmd
For Linux: SOAHOST1> ./setNMProps.sh

A message displays saying that the required properties file was copied.

Navigate to the WEBLOGIC_HOME/common/bin directory.

The default location for Windows is c:/Oracle/Middleware/wlsserver_10.3/server/bin
The default location for Linux is $HOME/Oracle/Middleware/ /wlsserver_10.3/server/bin

Run startNodeManager script to Start Node Manager:

For Windows:startNodeManager.cmd
For Linux: SOAHOST1> ./startNodeManager

Start the WLS_WSM2 managed server using the Oracle WebLogic Server Administration Console as follows:

1. Expand the Environment node in the Domain Structure window.
2. Choose Servers. The Summary of Servers page appears.
3. Click the Control tab.
4. Select WLS_WSM2 and then click Start.

Verify that the server status is reported as "Running" in the Admin Console, then access http://SOAHOST2:7010/wsm-pm.

Click Validate Policy Manager. A list of policies and assertion templates available in the data store appear.
Note: The configuration is incorrect if no policies or assertion templates appear.

Connect to the Administration Server using the command-line Oracle WebLogic Scripting Tool (WLST) on SOAHOST1.

For Windows: c:\Oracle\Middleware\Oracle_SOA1\common\bin\wlst.cmd
For Linux: SOAHOST1> cd ORACLE_SOA_HOME/common/bin/wlst.sh

Type connect(), and enter the WebLogic admin user name and password when prompted.

After connecting to the Administration Server using wlst, start the script using the execfile command:
wls:/mydomain/serverConfig>execfile('MIDDLEWARE_HOME/oracle_common/bin/configure-joc.py')
where MIDDLEWARE_HOME is the location of you Middleware home directory.

for example:

execfile('c:\Oracle/Middleware/oracle_common/bin/configure-joc.py')

Configure JOC for all the managed servers for a given cluster. Enter 'y' when the script prompts whether you want to specify a cluster name, and also specify the cluster name and discover port, when prompted. This discovers all the managed servers for the given cluster and configures the JOC. The discover port is common for the entire JOC configuration across the cluster. For example:
Do you want to specify a cluster name (y/n) <y>
Enter Cluster Name : wsm-pm_cluster
Enter Discover Port : 9991

Here is a walk-through for using configure-joc.py for HA environments:

execfile('MW_HOME/oracle_common/bin/configure-joc.py')
.
Enter Hostnames (for example host1,host2) : SOAHOST1.example.com, SOAHOST2.example.com
.
Do you want to specify a cluster name (y/n) <y>y
.
Enter Cluster Name : wsm-pm_cluster
.
Enter Discover Port : 9991
.
Enter Distribute Mode (true|false) <true> : true
.
Do you want to exclude any server(s) from JOC configuration (y/n) <n> n

Restart the managed servers, WLS_WSM1 and WLS_WSM2.

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.
(You can also stop it with stopWebLogic.cmd. For example: c:\Oracle\Middleware\user_projects\domains\base_domain\bin\stopWebLogic.cmd).

Navigate to the <ORACLE_SOA_HOME>/common/bin directory. (It is recommended that all database instances should running.)

The default location for < ORACLE_SOA_HOME> for Windows is c:/Oracle/Middleware/ Oracle_SOA1.
The default location for < ORACLE_SOA_HOME> for Linux is $HOME/Oracle/Middleware/ Oracle_SOA1.

Start the Configuration Wizard.

For Windows: Config.cmd
For Linux: SOAHOST1>./config.sh

On the Welcome screen, select Extend an existing WebLogic domain, then click Next.

In the WebLogic Domain Directory screen, select the WebLogic domain directory (MIDDLEWARE_HOME/user_projects/domains/<<domain_name>>), then click Next.

The default location for MIDDLEWARE_HOME for Windows isc:/Oracle/Middleware
The default location for MIDDLEWARE_HOME for Linux is$HOME/Oracle/Middleware/

In the Select Extension Source screen, do the following:

1. Select Extend my domain automatically to support the following added products.
2. Select Oracle SOA Suite 11.1.1.0 and Oracle JRF Webservices Asynchronous services 11.1.1.0.
3. Click Next.

Note: The following products should already be selected, and grayed out:

• Basic WebLogic Server Domain
• Oracle Enterprise Manager
• Oracle WSM Policy Manager
• Oracle JRF
  

In the Configure JDBC Component Schema screen, select the SOA Infrastructure, User Messaging Service,
and SOA MDS Schema rows in the table, then click Next.

On the Test JDBC Data Sources screen, the connections should be tested automatically. The Status column displays the results. Verify that all connections were successful, then click Next.

In the Select Optional Configuration screen, select the following JMS Distributed Destinations; Managed Servers, Clusters, and Machines; and Deployments and Services, and then click Next.

On the Select JMS Distributed Destination Type screen, verify that UDD is selected in the drop down list for UMSJMSystemResource and for SOAJMSModule, then click Next.

Note: Ignore the warning message that displays.

On the Configure Managed Servers screen, add the required managed servers A server called soa_server1 is created automatically. Rename this to WLS_SOA1 and give it the attributes listed as below. You then need to, add a new server called WLS_SOA2. The WLS_WSM1 and WLS_WSM2 managed servers should already be present because they are part of the domain that you are extending. When you are finished the list of managed servers should match table below. Click Next when done.

On the Configure Clusters screen, add SOA_Cluster with Cluster Messaging Mode set to unicast, and then click Next.

In the Assign Servers to Clusters screen, assign the WLS_SOA1 and WLS_SOA2 servers to SOA_Cluster. Assign the WLS_WSM1 and WLS_WSM2 servers to WSM-PM_Cluster. When finished, click Next.

On the Configure Machines screen, delete LocalMachine, which appears by default. After deleting the machine, the screen should match the following:

On the Assign Servers to Machines screen, assign WLS_SOA1 and WLS_WSM1 to SOAHOST1, assign WLS_SOA2 and WLS_WSM2 to SOAHOST2, and assign AdminServer to ADMINHOST. When finished, click Next.

On the Target Deployments to Clusters or Servers screen, perform the steps below:

1. To ensure that the wsm-pm application is targeted only to the WSM-PM cluster,
   on the left, select SOA_Cluster, then on the right, deselect wsm-pm.
2. To target usermessagingserver and usermessagingdriver-email to SOA_Cluster,
   on the left, select SOA_Cluster,then on the right, select usermessagingserver and usermessagingdriver-email.
   They should be targeted only to SOA_Cluster. (The usermessaging-xmpp, usermessaging-smpp, and usermessaging-voicexml applications are optional.)
3. To ensure that oracle.sdp.*, and oracle.soa.* libraries should be targeted only to SOA_Cluster,
   on the left select Admin Server, then on the right, deselect oracle.sdp.*, and oracle.soa.* libraries.
4. To ensure that oracle.rules.* library is targeted only to Admin Server and SOA_Cluster,
   on the left select WSM-PM_Cluster, and on the right, verify that oracle.rules.* is deselected.
5. To ensure that oracle.wsm.seedpolicies library is targeted only to WSM-PM_Cluster and SOA_Cluster,
   on the left select Admin Server, and on the right, deselect oracle.wsm.seedpolicies.
6. Click Next.

On the Target Deployments to Clusters or Servers screen, perform the steps below:

1. To ensure sure the JOC-Shutdown, and JOC-Startup services are targeted to the WSM-PM_Cluster only and not targeted to Admin Server or SOA Cluster,
   on the left, select SOA_Cluster, then on the right,deselect JOC-Shutdown, and JOC-Startup. Then on the left, select Admin Server, and on the right, deselect JOC-Shutdown and JOC-Startup.
2. To ensure that mds-owsm is targeted to only WSM-PM_Cluster and AdminServer,
   on the left select SOA_Cluster, then on the right, deselect mds-owsm.
   
3. Click Next.

On the Configuration Summary screen, click Extend.

In the Extending Domain screen, 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.

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.

Log into the Oracle WebLogic Server Administration Console.

In the Domain Structure window, expand the Environment node, then click Servers.

The Summary of Servers page is displayed.

Click the name of the server (WLS_SOA1 or WLS_SOA2, which are represented as hyperlinks) in the Name column of the table.

The settings page for the selected server is displayed.

Click Lock and Edit.

Click the Server Start tab.

Enter the following for WLS_SOA1 and WLS_SOA2 into the Arguments field.

For WLS_SOA1, enter the following:
-Dtangosol.coherence.wka1=SOAHOST1.example.com
-Dtangosol.coherence.wka2=SOAHOST2.example.com
-Dtangosol.coherence.localhost=SOAHOST1.example.com

For WLS_SOA2, enter the following:
-Dtangosol.coherence.wka1=SOAHOST1.example.com
-Dtangosol.coherence.wka2=SOAHOST2.example.com
-Dtangosol.coherence.localhost=SOAHOST2.example.com

Note: There should be no breaks in lines between the different -D parameters. Do not copy or paste the text from above to your Administration Console's arguments text field. This may result in HTML tags being inserted in the Java arguments. The text should not contain other text characters than those included in the example above.

Log in to Oracle WebLogic Server Administration Console and click Lock and Edit.

Expand the Environment node in the Domain Structure window.

Click Servers. The Summary of Servers page appears.

Select WLS_SOA1 (represented as a hyperlink) in the Names column of the table. The Settings page is displayed.

Click the SSL tab.

Click Advanced.

Set Hostname Verification to None.

Click Save.

Repeat the above steps for the WLS_SOA managed server.

Save and activate the changes.

Stop Node Manager by stopping the process associated with it.

• If it is running in the foreground in a shell, simply use CTRL+C.
• If it is running in the background, find the associate process and use the kill command to stop it.

Navigate to ORACLE_COMMON_HOME/common/bin directory

The default location for windows is c:/Oracle/Middleware/oracle_common.
The default location for linux is $HOME/Oracle/Middleware/ oracle_common.

Run setNMProps to set the StartScriptEnabled property to 'true' before starting Node Manager.

For Windows: setNMProps.cmd
For Linux: SOAHOST1> ./setNMProps.sh

A message displays saying that the required properties file was copied.

Navigate to the WEBLOGIC_HOME/common/bin directory.

The default location for Windows is c:/Oracle/Middleware/wlsserver_10.3/server/bin
The default location for Linux is $HOME/Oracle/Middleware/ /wlsserver_10.3/server/bin

Run startNodeManager script to Start Node Manager:

For Windows: startNodeManager.cmd
For Linux: SOAHOST1> ./startNodeManager

Access the Administration Console at http://SOAHOST1VHN0:7001/console.

Click Servers.

Open the Control tab.

Select WLS_SOA1.

Click Start.

Verify that the WLS_WSM1 managed server is up and running.

Verify that the WLS_SOA1 server status is reported as Running in the Admin Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started.

Access http://SOAHOST1:8001/soa-infra/ to verify status of WLS_SOA1.

Access http://SOAHOST1:8001/integration/worklistapp/ to verify status of the worklist application.

Click Start.

Navigate to the ORACLE_COMMON_HOME/common/bin directory.

The default for location for < ORACLE_COMMON_HOME> is c:/Oracle/Middleware/oracle_common.
The default location for < ORACLE_COMMON_HOME> on Linux is $HOME/Oracle/Middleware/ oracle_common.

Run the pack command on SOAHOST1 to create a template pack as follows:
For Windows: pack -managed=true -domain= MIDDLEWARE_HOME \user_projects\domains\<domainName> -template=c:\<domainTemplate>.jar -template_name=<domain Template Name>
For Linux: SOAHOST1> ./pack.sh -managed=true -domain=<MIDDLEWARE_HOME>/user_projects/domains/domain_name -template=<domainTemplate>.jar -template_name=<domain Template Name>

The default for <MIDDLEWARE_HOME> for Windows is c:/Oracle/Middleware.
The default for <MIDDLEWARE_HOME> for Linux is $HOME/Oracle/Middleware.

Copy the template file created on SOAHOST1 to ORACLE_COMMON_HOME/common/bin on SOAHOST2.

Login to the SOAHOST2 Machine.

Navigate to the ORACLE_COMMON_HOME/common/bin directory.

Run the unpack command on SOAHOST2 to unpack the propagated template:
For Windows: unpack -domain=MIDDLEWARE_HOME/user_projects/domains/<domain_name> -overwrite_domain=true -template=<domainTemplate>.jar
For Linux: SOAHOST2> ./unpack.sh -domain=MIDDLEWARE_HOME/user_projects/domains/<domain_name> -template==<domainTemplate>.jar

Stop Node Manager by stopping the process associated with it.

• If it is running in the foreground in a shell, simply use CTRL+C.
• If it is running in the background, find the associate process and use the kill command to stop it.

Navigate to ORACLE_COMMON_HOME/common/bin directory.

The default location for windows is c:/Oracle/Middleware/oracle_common.
The default location for linux is $HOME/Oracle/Middleware/ oracle_common.

Run setNMProps to set the StartScriptEnabled property to 'true' before starting Node Manager.

For Windows: setNMProps.cmd
For Linux: SOAHOST2> ./setNMProps.sh

A message displays saying that the required properties file was copied.

Navigate to the WEBLOGIC_HOME/common/bin directory.

The default location for Windows is c:/Oracle/Middleware/wlsserver_10.3/server/bin
The default location for Linux is $HOME/Oracle/Middleware/ /wlsserver_10.3/server/bin

Run startNodeManager script to Start Node Manager:

For Windows:startNodeManager.cmd
For Linux: SOAHOST2> ./startNodeManager

Verify that at least one of the managed servers (WLS_WSM1 or WLS_WSM2) is up and running.

Start the WLS_SOA2 managed server using the Administration Console.

Verify that the server status is reported as Running in the Admin Console. If the server is shown as Starting or Resuming, wait for the server status to change to Started. If another status is reported (such as Admin or Failed), check the server output log files for errors.

Access http://SOAHOST2:8001/soa-infra.

Access http://SOAHOST2:8001/integration/worklistapp/ to verify status of the worklist application.

In the WebLogic Server Administration Console, in the Change Center section, click Lock & Edit.

In the left pane, select Environment from the Domain Structure window, and then select Clusters. The Summary of Clusters page appears.

Select the SOA_Cluster cluster.

In the Configuration, General tab, enter the following in the Cluster Address field: SOAHOST1:8001,SOAHOST2:8001

Access http://SOAHOST2:8001/integration/worklistapp/ to verify status of the worklist application.

Click Save.

To activate the changes, click Activate Changes in the Change Center section of the Administration Console.

Restart the WLS_SOA1 and WLS_SOA2 managed servers.

In the WebLogic Server Administration Console, in the Change Center section, click Lock & Edit.

In the Domain Structure window, expand the Services node and then click the Persistence Stores node. The Summary of Persistence Stores page is displayed.

Repeat the steps below for each persistence store:

1. Select the persistence store (represented as a hyperlink) from the Name column of the table. The Settings page for the persistence store is displayed.
2. In the Configuration tab, enter the location of a persistent storage solution (such as NAS or SAN) that is available to other servers in the cluster in the Directory field. Specifying this location enables pending JMS messages to be sent. If the persistence Store name contains JMSFileStore, specify jms directory. If the persistence Store name contains AsyncFileStore, specify jrfAsynch directory.
   If the persistence Store name contains JMSFileStore, specify jms directory.
   If the persistence Store name contains AsyncFileStore, specify jrfAsynch directory.
   The location should follow the following directory structure:
   For Windows: Y:/jms
   For Linux: ORACLE_BASE/admin/<domain_name>/<soa_cluster_name>/jms
   Note: The directory should be same as defined during the Shared Storage Prerequisites step.
3. Click Save and activate the changes.
4. Restart the servers to make the change in the persistent stores effective.
   

Log in to the WebLogic Server Administration Console.

In the left pane, select Environment from the Domain Structure window, and then select Servers. The Summary of Servers page is displayed.

Click the name of the server (represented as a hyperlink) in Name column of the table. The settings page for the selected server appears and defaults to the Configuration tab.

Click the Services tab.

In the Default Store section of the page, enter the path to the folder where the default persistent stores will store its data files.
The directory structure of the path is as follows:
For windows: Y:/tlogs
For Linux: ORACLE_BASE/admin/<domain_name>/<soa_cluster_name>/tlogs

Note: The directory should be same as defined during Shared Storage Prerequisites step.

Click Save, then click Activate Changes in the Change Center section of the Administration Console.

To stop the SOA and WSM managed Servers:

1. Connect to Weblogic Console http://host:7001/console where host is the name of the machine.
2. Log on using the WebLogic administrator name and password that you specified for the domain.
3. Expand the Environment node in the Domain Structure window.
4. Click Servers. The Summary of Servers page appears.
5. Click the Control tab.
6. Select the WLS_SOA1,WLS_SOA2,WLS_WSM1 and WLS_WSM2 servers.
7. Click Shutdown, and select Force shutdown Now.

To stop the WebLogic Admin Server:

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

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

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

Note: You can also start the configuration utility using 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):
Server: Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
Port: 1521
Service Name or SID: The database service name that you must use is available in c:\app\<user>\product\11.2.0\dbhome_1\NETWORK\ADMIN\tnsnames.ora
User Name: fcm
Password: welcome1

Example for MS SQl Server database (in this example, the user name is fcm and the database name is FCMdb):
Server: Enter demoserver.example.com. Replace example.com with the fully qualified domain name.
Port: 1433
Service Name or SID: FCMdb
User Name: fcm
Password: welcome1

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

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

The database connection details are displayed for the
Close Manager, FDM Enterprise Edition and Reconciliation Manager databases,
verify the details 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, and click Next.
Administrator User/Password: Use the WebLogic administrator username and password created from SOA configurator.
Domain Name: base_domain (use the existing domain that was created from SOA configurator)

At the prompt regarding password validation, click OK.

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

In the Web Server Type list, select Oracle HTTP Server, and click Next.

Enter the local user credential (the local administrator user you are currently logged in to the machine) 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.

Enter the Shared Services administrator user name and 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. Enter the WebLogic user name and password when prompted.

The start up process will take a few minutes and is complete when you see '<Server started in RUNNING mode>' in the Command Prompt window.

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

Note: You can also start the configuration utility using configtool.bat. For example, c:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat).

Accept the defaults and click Next.

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

Perform these steps:

1. Expand Hyperion Foundation and ensure that only Configure Oracle Configuration manager and Configure Database are selected and grayed out. Select Deploy to Application Server.
2. Expand FDM Enterprise Edition and select Configure Database and Deploy to Application Server.
3. Under Financial Management, Configure DCOM is required for FDM and it should be selected by default.
4. Expand Financial Close Management and select Deploy to application server and Configure Database for both Close Manager and Reconciliation Manager. Do not select Deploy to SOA and Deploy to SOA for FDMEE. Select Configure Content Management System location only if you are using a content management system.
5. Click Next.

The database connection details that were provided in the Shared Services database connection details screen are displayed. Verify the connection details for the Financial Close Management, FDM EE and Account Reconciliation databases, and click Next.

When prompted, select the Reuse the existing database option.

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

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

Enter the local user credential (the local administrator user you are currently logged in to the SOAHOST2) 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 previously you chose to integrate Oracle Enterprise Content Management with your Financial Close Management application you will see this screen, otherwise click Next to skip to the next section.

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

When the configuration is complete, click Finish.

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

Note: You can also start the configuration utility using configtool.bat. For example, c:\Oracle\Middleware\EPMSystem11R1\common\config\11.1.2.0\configtool.bat).

Accept the defaults and click Next.

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

Expand Hyperion Foundation and select only Configure Web Server. Verify that both FDM Fusion Edition and Financial Close are not selected, then 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.

While WLS_SOA2 is running, stop WLS_SOA1 from Oracle WebLogic Server Administration Console.

Access the following URLs and verify the appropriate functionality: WebHost1:19000/soa-infra

Start WLS_SOA1 from Oracle WebLogic Server Administration Console.

Stop WLS_SOA2.

Access the following URLs and verify the appropriate functionality: WebHost1:19000/soa-infra

While WLS_WSM2 is running, stop WLS_WSM1 from Oracle WebLogic Server Administration Console.

Access the following URL and verify the appropriate functionality: WebHost1:19000/wsm-pm

Start WLS_ WSM1 from Oracle WebLogic Server Administration Console.

Stop WLS_ WSM2.

Access the following URL and verify the appropriate functionality: WebHost1: 19000/wsm-pm

In the WebLogic Server Administration Console, in the Change Center section, click Lock & Edit.

In the left pane, select Environment in the Domain Structure window and then select Clusters. The Summary of Clusters page is displayed.

Select the SOA_Cluster cluster.

Select HTTP.

Set the following values:
Frontend Host: SOAHOST1
Frontend Port: 19000

Click Save.

To activate the changes, click Activate Changes in the Change Center section of the Administration Console.

Restart the WLS_SOA1 and WLS_SOA2 servers to make the Frontend Host directive in the cluster effective.

Make sure that both Admin, WSM and SOA servers are running before running
the EPM configurator. Make sure that Node Managers are running SOA_HOST1 and SOA_HOST2.

1. 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.
   Enter the WebLogic admin user name and password if prompted.
   The process will take a few minutes and is complete when you see '<Server started in RUNNING mode>' in the command prompt box.
   
2. Login to weblogic Console using Web Logic admin user name and password and verify that WLS_WSM1,WLS_WSM2 , WLS_SOA1 and WLS_SOA2 are in Running Mode.
   

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

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

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

Expand Financial Close Management, then Close Manager and select Deploy to SOA.
Within Financial Close Management, expand Reconciliation Manager and select Deploy to SOA and
Deploy to SOA for FDM EE 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.

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 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 for the WebLogic Server Domain.

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.

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

Login 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, enter the following command to add the JDK to the path:

set PATH=%PATH%;c:\Oracle\Middleware\jdk160_35\bin\

where c:\Oracle\Middleware\jdk160_35\bin has to be your JDK path

The JDK must be included in the path in order to run the Java keystore utility.

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

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

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

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

Enter your Weblogic administrator name and password to log in.

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

Right-click on WebLogic Domain, then Security, and then Security Provider Configuration.

Expand the Keystore section, and 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.

<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 the above steps to increase the connection pool for the EDNLocalTxDataSource
service 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

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 Lock and Edit.

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 text box, 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.

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

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

To start the Oracle HTTP server, enter the following command at a command prompt:
c:\Oracle\Middleware\user_projects\epmsystem1\httpConfig\ohs\bin\opmnctl.bat startall

To start FDMEE Services, select Start, then Programs, then Oracle EPM System, then epmsystem1, then FDM Enterprise Edition, and then Start ERPIntegrator.
(You can also start it with startErpIntegrator.bat. For example: c:\Oracle\Middleware\user_projects\epmsystem1\bin\startErpIntegrator.bat).

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 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, select Start, then Programs, then Oracle EPM System,
then epmsystem1, then Financial Close, then Start FinancialClose.
(You can also start it with startFinancialClose.bat. For example: c:\Oracle\Middleware\user_projects\epmsystem1\bin\startFinancialClose.bat).

To start the EPM validator tool,select Start, then Programs, then Oracle EPM System, then Foundation Services, then epmsystem1, then EPM System Diagnostics.

(You can also start it with validate.bat. For example:
c:\Oracle\Middleware\user_projects\epmsystem1\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 deployment 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 from a web browser using the following the URL:
http://<FCMHOST>:<FCMPORT>/fcc/faces/oracle/apps/epm/fcc/ui/page/FCCValidation.jspx

• Where FCMHOST is the name of the machine where FinancialClose0 managed server is configured.
• Where FCMPORT is Listening port of FinancialClose0 managed Server in WebLogic console.





 

Log in to Close Manager using 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 the WebLogic admin console (http://<host>:7001/console where <host> is machine name for where admin server is running)

b. Click Lock and Edit.

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

d. Click the myrealm link.

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

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

g. Click OK.

h. Click Activate Changes.

After successfully logging in the following screen is displayed.

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

After validation, the configuration information will be 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.



Login with Shared Service administrator credentials.

 

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

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

Below is the information that is displayed:

Edit the wls-ARM.properties file:

a. Go to directory <EPM_ORACLE_HOME>/products/FinancialDataQuality/bin
b. Modify the wls-ARM.properties file as following:

For WebLogic Admin server connection:

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

Run the wlsConfigARM.bat file:

a.Open a command prompt.

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

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

Restart the FDMEE service and restart WebLogic admin server.

Check the status of the FDMEE server:
Login 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 FDMEE server status is changed to RUNNING.

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

Login 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 login 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 Login Name, password and Confirm password

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

Click OK to create the user.

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

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

b. Enter the database name and owner.

c. Click OK to create the database.

Modify the properties of the database for SOAdb:

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

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

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

Modify the properties of the database for Financial Close Management by using the following commands:
ALTER database <database name> SET READ_COMMITTED_SNAPSHOT ON
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_50.<INSTANCE_NAME>\MSSQL\Binn for SQL Server 2008.

After copying the file, rename the 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 “<your SQL Server Path>\MSSQL\Binn\instjdbc.sql” -o c:\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.

Example for SQL Server 2005:

Example for SQL Server 2008:

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

Run "ipconfig /all" from a command prompt:

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 the other remote machine, ping your machine (Machine A) from a comman 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 verify 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. Select 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 the command prompt to make sure there are no longer any devices using IPv6.
If you find more, then repeat the above steps to turn it them off, until there is no device using IPv6.