This page (revision-23) was last changed on 26-Nov-2021 10:22 by ibarr

This page was created on 26-Nov-2021 10:22 by jmyers

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
23 26-Nov-2021 10:22 8 KB ibarr to previous
22 26-Nov-2021 10:22 8 KB rforbes to previous | to last
21 26-Nov-2021 10:22 8 KB jmyers to previous | to last

Page References

Incoming links Outgoing links

Version management

Difference between version and

At line 3 changed one line
[{$applicationname}] Professional and Self-Service utilizes various components of the Oracle Application Server. Therefore, it is important to know where the logs files are stored for each component before proceeding any further.
Personality Professional and Self-Service utilizes various components of the Oracle Application Server. Therefore, it is important to know where the logs files are stored for each component before proceeding any further.
At line 5 changed one line
!Oracle HTTP Server Logs:
!Oracle HTTP Server Logs
At line 9 changed one line
!J2ee Application Logs:
!J2ee Application Logs
At line 13 changed one line
!OPMN Logs:
!OPMN Logs
At line 19 changed one line
;Problem:There is an attempt to run a report in [{$applicationname}] and a red bar is automatically encountered, indicating the report has failed.
;Problem:There is an attempt to run a report in Personality and a red bar is automatically encountered, indicating the report has failed.
At line 29 changed one line
!!Unable to view report after running it.
!!Unable to View Report After Running It
At line 34 changed one line
!!Unable to write or read from extract or load folder.
!!Unable to Write or Read from Extract or Load Folder
At line 39 changed one line
!!Self Service Tuning Tips:
!!Self Service Tuning Tips
At line 42 changed one line
#Does your server meet the minimum requirements for the number of users and more importantly, does it have sufficient resources to scale when the load increases. Please reference the '[{$applicationname}] Operating Environment’ for more information on the minimum requirements.
#Does your server meet the minimum requirements for the number of users and more importantly, does it have sufficient resources to scale when the load increases. Please reference the 'Personality Operating Environment’ for more information on the minimum requirements.
At line 44 changed 2 lines
!Configuring the Number of Concurrent Self Service Users:
The assumption is made that 500 users will be accessing Self Service currently and that Self Service is deployed separately from [{$applicationname}]. The below configurations changes are based on this fact.
!Configuring the Number of Concurrent Self Service Users
The assumption is made that 500 users will be accessing Self Service currently and that Self Service is deployed separately from Personality. The below configurations changes are based on this fact.
At line 70 changed one line
There are a number of tuning options available to assist with performance related issues. Here are a few of those options, for a complete list of all the java options, please refer to the [Java Virtual Machine Garbage Collection Tuning] document.
There are a number of tuning options available to assist with performance related issues. Here are a few of those options, for a complete list of all the java options, please refer to the [Java Virtual Machine Garbage Collection Tuning|http://www.oracle.com/technetwork/java/javase/gc-tuning-6-140523.html|target="_blank"] document.
At line 87 changed 2 lines
!![{$applicationname}]
The performance of [{$applicationname}] is heavily dependent of the size of the heap and the garbage collector utilized. Please review the above section on [Tuning JVM Options|SOFTWARE_INSTALLATION.TROUBLESHOOTING#TuningTheJVM].
!!Personality
The performance of Personality is heavily dependent of the size of the heap and the garbage collector utilized. Please review the above section on [Tuning JVM Options|SOFTWARE_INSTALLATION.TROUBLESHOOTING#TuningTheJVM].
At line 90 changed one line
A new site preference has been introduced, DB_PRCSS_THREADS which will allow specific update functions to run as a multi-threaded process –in other words the functions will be able to take advantage of multiple processors.
A new site preference has been introduced, [DB_PRCSS_THREADS|DB PRCSS THREADS(System_Preference)], which will allow specific update functions to run as a multi-threaded process. In other words the functions will be able to take advantage of multiple processors.
At line 92 changed 4 lines
The below list of functions can utilize the DB_PROCSS_THREADS:
[UPCALC]
[UPUNDO]
[UTTP]
The below list of functions can utilize the [DB_PRCSS_THREADS|DB PRCSS THREADS(System_Preference)]:
\\[UPCALC]
\\[UPUNDO]
\\[UTTP]
\\[UEGTS]
At line 98 added 4 lines
\\
%%commentbox
[Prev page|WIKI.INSTALLATION] - [Next Page|SOFTWARE_INSTALLATION.GO_LIVE_CONFIGURATION]
%%