This section describes additional tasks required to configure Financial Close Management. Perform these tasks after you install and configure Oracle SOA Suite and Financial Close Management.
If you are applying the maintenance release to move from Financial Close Management Release 11.1.2.0 to Release 11.1.2.1, the only task you need to perform is Reconfiguring External Providers (Maintenance Release Only).
Caution! | You must perform these tasks before you can start and run Financial Close Management. Perform the tasks in the order in which they are listed. |
The following table describes Financial Close Management postfiguration tasks.
Note: | For the procedures that follow, note that if you selected Production Mode when you created the WebLogic domain, to make changes in the WebLogic Administration Console you must first click Lock & Edit in the Change Center. After you make the changes, click Activate Changes in the Change Center. |
Table 61. Financial Close Management Postconfiguration Tasks
| Task | Reference |
|---|---|
| To enable Lifecycle Management with Financial Close Management in a distributed environment, target WSM-PM and MDS-OWSM to Shared Services. | Targeting WSM-PM and MDS-OWSM to Foundation Services |
Configure the SOA managed server. | Configuring the SOA Managed Server |
Configure the keystore for Oracle Web Services Manager. | Configuring the Keystore for Oracle Web Services Manager |
| If Financial Close Management and SOA are deployed on different machines, set the soa.oracle.home environment variable. | Setting the soa.oracle.home Environment Variable |
| If Financial Close Management and SOA are deployed on different machines, add a grant to bpm-services.jar. | Adding a Grant to bpm-services.jar |
| If you are using Microsoft SQL Server, enable EdnJmsMode. | Enabling EdnJmsMode |
| If you are using Microsoft SQL Server or Oracle Database and you are using OAM for single sign-on, perform additional steps. | Configuring for OAM |
Start managed servers. | Start Managed Servers |
Raise the maximum capacity in the connection pool. | Raising the Maximum Capacity in the Connection Pool |
| Modify the JTA Timeout. | Modifying the JTA Timeout |
To receive e-mail notifications in a language different from the default language specified on the SOA server, perform additional steps. | Specifying the Language for E-Mail Notifications |
| If you are using Microsoft SQL Server, there is a known issue with WebLogic and Logging Last Resource (LLR) datasources. The error comes from inserting/updating rows in a table used by LLR. To work around this issue, the DBA must drop the LLR table and recreate it with a larger column size. Tip: This step is needed only if the managed server for Financial Close Management has a name other than the default FinancialClose0. | http://download.oracle.com/docs/cd/E13222_01/wls/docs92/jta/llr.html |
| If you are using Microsoft SQL Server, remove EDNLocalTxDataSource and EDNDataSource. | |
Maintenance Release Only Reconfigure external providers. | Reconfiguring External Providers (Maintenance Release Only) |
Create and manage Integration Types. | Oracle Financial Close Management Administrator's Guide. You can download integration xml files from My Oracle Support. |