OFSAA – Oracle Financial Services Analytical Application Installation Overview

Oracle Financial Services Analytical Application (OFSAA) is business intelligence application that enables financial institutes to measure and meet risk-adjusted performance objectives.

This post covers overview of OFSAA (v 7.2) installation

1. OFSAA Infrastructure consists of Database tier, Application tier, and Web Tier  (all three tiers can be on same machine or on different machines)

2. Minimal recommended configuration for OFSAA is 2 CPU, 4GB RAM and 1.5 GB Hard Disk (for dev/test environment)

3. OFSAA is certified on Sun/Oracle Solaris, IBM AIX, RedHat/Oracle Enterprise Linux, Microsoft Windows Server.

4. Certified Application Servers are IBM WebSphere, Apache Tomcat, Oracle/BEA WebLogic Server

5. Certified Database for OFSAA is Oracle Database

6. Hyperion Essbase is optional component. Hyperion Essbase is required only if you wish to use OLAP features of OFSAA.

7. If OFSAA is deployed on Windows Server and you wish to integrate OFSAA with LDAP server (for user authentication) then OPEN LDAP 2.2.29+ is required

8. OFSAA can be installed in

a) Single Tier Installation mode – All tiers i.e. database, application and web are installed on same machine.

b) Multi Tier Installation mode – one or all of Database, Application and Web Tier are deployed/configured on different machines. (install oracle database client on application tier)

9. Multiple Instances of Application or Web Tier can be installed for scalability and resilience . First application instance is called as Default Application Instance. Additional application instances can be added later.

10. Database used for OFSAA application should be created with default NLS_NCHAR_CHARACTERSET as AL16UTF16 and OPEN_CURSORS value should be at least 100 .

Step by step installation of OFSAA coming soon ..

After R12 Clone: Consult the OPP service log for details

After make a clone of R12, the new instance gave “Completed, Warning” for all XML output requests the request log show the following:

Post-processing of request 509561 failed at <timestamp> with the error message:

One or more post-processing actions failed. Consult the OPP service log for details.

you can review the OPP log file from the following query to find the location and file name for the OPP log:

SELECT

fcpp.concurrent_request_id req_id, fcp.node_name, fcp.logfile_name

FROM fnd_conc_pp_actions fcpp, fnd_concurrent_processes fcp

WHERE fcpp.processor_id = fcp.concurrent_process_id

 AND fcpp.action_type = 6

 AND fcpp.concurrent_request_id = &request_id;

the OPP log file will be in the $APPLCSF/$APPLLOG with an name of “FNDOPP*.txt”

now the log file shows the error:

[UNEXPECTED] [50032:RT509560] oracle.apps.xdo.XDOException: Unable to create font cache directory: /u01/SID/instapps/CONTEXT_NAME/temp/xdofonts/SID

Solution:

1. Navigation Path:

(Responsibility) XML Publisher Administrator > (Menu) Home > (Tab) Administration > (SubTab) Configuration > Properties > General > Temporary directory

2. Provide a valid value to ‘Temporary directory’, and click button ‘Save’.

3. Re-test the issue.

How to update EBS XML Publisher Temporary Directory

SQL> select value from apps.XDO_CONFIG_VALUES WHERE  property_code = 'SYSTEM_TEMP_DIR';

VALUE

--------------------------------------------------------------------------------

/u1/appl/SHAIK1/wrongdir_tmp

SQL> update apps.XDO_CONFIG_VALUES set value='/u01/share/temp' WHERE  property_code = 'SYSTEM_TEMP_DIR';

1 row updated.

SQL> commit;

Commit complete.

SQL> select value from apps.XDO_CONFIG_VALUES WHERE  property_code = 'SYSTEM_TEMP_DIR';

VALUE

--------------------------------------------------------------------------------

/u01/share/temp

Reference:-

How To Find the EBS XML Publisher Temporary Directory Via SQL? (Doc ID 1189723.1)

OUTPUT POST PROCESSOR (OPP) LOG CONTAINS ERROR “JAVA.LANG.OUTOFMEMORYERROR”

To obtain the Output Post Processor log file, follow the navigation below:
1.  Select the System Administrator responsibility.
2.  Select the menu Concurrent – Manager – Administer.
3.  Select the Output Post Processor Service.
4.  Select the Processes button.
5.  Select Manager Log.
6.  The log will contain a java stack error similar to the following:

/18/06 5:00:14 PM] [UNEXPECTED] [128085:RT1585526] java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:58)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java(Compiled Code))
at oracle.apps.xdo.common.xml.XSLT10gR1.invokeProcessXSL(XSLT10gR1.java:580)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:378)
at oracle.apps.xdo.common.xml.XSLT10gR1.transform(XSLT10gR1.java:197)
at oracle.apps.xdo.common.xml.XSLTWrapper.transform(XSLTWrapper.java:156)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:916)
at oracle.apps.xdo.template.fo.util.FOUtility.generateFO(FOUtility.java:178)
at oracle.apps.xdo.template.FOProcessor.createFO(FOProcessor.java:1507)
at oracle.apps.xdo.template.FOProcessor.generate(FOProcessor.java:913)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:1766)
at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:1277)
at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:229)
at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:153)
Caused by: java.lang.OutOfMemoryError
at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java(Compiled Code))
at oracle.xdo.parser.v2.XMLOutputStream.flush(XMLOutputStream.java(Inlined Compiled Code))
at oracle.xdo.parser.v2.XMLOutputStream.write(XMLOutputStream.java(Compiled Code))
at oracle.xdo.parser.v2.XMLOutputStream.writeChars(XMLOutputStream.java(Compiled Code))
…

Troubleshooting Steps

Generic errors can be resolved by performing the following steps:

1.  Log into the XML Publisher Administrator responsibility.
2.  Navigate to Home – Administration – Configuration.
3.  Under the General Properties select Temporary directory.
4.  Select a temporary file location on your concurrent processing node.  This should be at least 5Gb or 20 times larger than the largest XML data file you generate.

OR

1. Log into the XML Publisher Administrator responsibility.
2. Navigate to Home – Administration – Configuration.
3. Under the FO Processing Properties set:
a.  Use XML Publisher’s XSLT processor to True.
b.  Enable scalable feature of XSLT processor to False.
c.  Enable XSLT runtime optimization to True.

OR

1. As System Administrator: Navigate to Concurrent->Program->Define.
2. Query up the report: Account Analysis Report (for example).
3. Add a parameter named ScalableFlag:
Value Set: yes_no
Default Value: Yes
Select check boxes Enable Security and Required
Do not select the check box Display, or users could turn this off at runtime.
Token needs to be ScalableFlag (this is a case sensitive value).
Note:  Complete these steps for both the application General Ledger and the Subledger Accounting concurrent program definitions.

OR

1. Determine what the heap size per OPP process is currently:

select DEVELOPER_PARAMETERS from FND_CP_SERVICES
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);

2. The default should be:

J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx512m

3. Increase the Heap Space per Process to 1024:

update FND_CP_SERVICES
set DEVELOPER_PARAMETERS =
‘J:oracle.apps.fnd.cp.gsf.GSMServiceController:-mx1024m’
where SERVICE_ID = (select MANAGER_TYPE from FND_CONCURRENT_QUEUES
where CONCURRENT_QUEUE_NAME = ‘FNDCPOPP’);

4.  Bring the managers down.
5.  Run cmclean.sql script from Note 134007.1 – CMCLEAN.SQL Non-Destructive Script to Clean Concurrent Manager Tables.
6.  Bring the managers up again.

OR

1.  Navigate to the System Administrator responsibility.
2.  Navigate to Concurrent – Program – Define.
3.  Query up the XDOTMGEN executable short name.
4.  In the Options field add a value such as -Xmx512m or -Xmx1024m or other relevant number to increase the heap size.
5.  Save the changes.
6.  Resubmit the request.