This appendix provides a detailed discussion of the support available for the accurate monitoring of applications available as part of the Oracle Fusion Applications suite.
RUEI supports out-of-box monitoring of modules and components that are available as part of the Oracle Fusion Applications suite. For example, Oracle Fusion Customer Relationship Management (CRM) and Oracle Fusion Human Capital Management (HCM). It automatically discovers these applications, and translates network objects to business functions.
http://www.oracle.com/us/products/applications/fusion/index.htm
You can create suite definitions for Oracle Fusion Applications applications in the same way as for any other supported Oracle Enterprise architectures. The procedure to create suites is fully described in Section 10.1.1, "Creating Suite Definitions".
The default session tracking cookie depends on the default schema that is used in the deployment. Usually the cookie contains FND_SESSION somwhere in the name. To enable RUEI to monitor and track users over the complete session, you should ensure the cookie path is set to "/". If your Oracle ADF application uses another cookie name for state tracking, you need to update the application definition to reflect this. In addition, be aware that user name recognition is based on the userid construction. See Section 12.2, "Specifying the Session Tracking Mechanism" for more information on cookie configuration.
In order for RUEI to correctly translate the Oracle Fusion business logic within your environment, do the following:
Copy the create_FUS_info.pl script to the home directory of the Oracle Fusion server. It is located in the RUEI_DATA /processor/local/download directory of the RUEI system.
Run the create_FUS_info.pl script as any user on the Oracle Fusion server.Foot 1 This script assigns an identification to the identified page IDs within the environment. The create_FUS_info.pl script must be run with the following required parameter:
create_FUS_info.pl connect-string
where connect-string is the string used to authorize the script to access the Oracle Fusion database. The script reads from the schemas, and generates .txt files in the current directory. For example:
create_FUS_info.pl "sys/oracle@myshop-fus:1522" create_FUS_info.pl "sys/oracle@FUS"
Note that the FND_APPL_TAXONOMY_VL and FND_APPL_TAXONOMY_HIERARCHY tables are used to obtain the product name. From this, the product family is derived. The reported view ID is derived from Adf-View-Id HTTP header in the response. When this header is not found in any of the related hits, RUEI attempts to obtain the view ID from the URL of the hit related to the click.
Follow the procedure described in Section 10.1.2, "Uploading Configuration Files" to upload the generated files to the Reporter System.
Predefined content messages are automatically provided for all standard Oracle Fusion Application messages. This enables the customization of their types (message or error) and reporting. The error types shown in Table P-1 are supported.
Table P-1 Predefined Fusion Error Types
| Type | Type | Type | Type | Type |
|---|---|---|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The Oracle Fusion Applications-specific data items shown in Table P-2 are reported by RUEI.
Table P-2 Oracle Fusion Applications-Specific Data Items
| Item | Description |
|---|---|
|
Fusion Component |
The display name of the component activated by the previous end-user action |
|
Fusion Component Client ID |
A unique identifier for the element clicked by the end-user on the previous page |
|
Fusion Component Type |
The type of the component activated by the previous end-user action |
|
Fusion Component Type Class |
The ID of the component activated by the previous end-user action |
|
Fusion Context Root |
The context root (top level directory) that was active on the end-user action |
|
Fusion Event Type |
The type of action that was triggered by this hit (such as view, action, dialog, focus, disclosure, launch, query, sort, or valueChange) |
|
Fusion Product |
The name of the fusion product that was active on the end-user action. The value is derived from the viewId through mapping files. |
|
Fusion Product Code |
The short name of the fusion product that was active on the end-user action. The value is derived from the viewId. |
|
Fusion Product Family |
The name of the fusion product family that was active on the end-user action. The value is derived from the product short name through mapping files. |
|
Fusion Product Family Code |
The short name of the fusion product family that was active on the end-user action. |
|
Fusion Region |
The region that was active on the end-user action (derived from same source regionViewID as taskflow). |
|
Fusion Task Flow Code |
The taskflow that was active on the end-user action (derived from same source regionViewID as region) |
|
Fusion View ID |
The ViewID identifier (for the part) of the screen part where the previous end-user action took place. |
For further information about these data items, see the Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework, available at the following location:
http://download.oracle.com/docs/cd/E12839_01/web.1111/b31974/title.htm
Currently, RUEI does not support all Oracle Fusion Applications functionality. In particular, the following known limitation exists:
RUEI requires PPRGET in order to trace page performance (12371586).
Client IDs are not always correctly reported (12944375).
Applications that make use of a Rich Internet Application (RIA) framework (such as Ajax) may have reduced replay capability.
Footnote Legend
Footnote 1: The script can also be run in the acceptance environment if it is equivalent to the production environment.