Oracle® Real User Experience Insight User's Guide Release 6.5.2 for Linux x86-64 Part Number E20330-01 |
|
|
View PDF · Mobi |
This appendix provides a detailed discussion of the support available for the accurate monitoring of Oracle FLEXCUBE Universal Banking or Direct Banking applications. Note that this support is only available if you have a valid Application Management Suite for Oracle FLEXCUBE licence. For more information, contact your Oracle representative.
If your monitored Web environment contains Oracle FLEXCUBE Universal Banking or Direct Banking applications, is it strongly recommended that you make use of this support. It not only saves time in configuration of your Oracle FLEXCUBE applications within RUEI, makes these applications more compatible, but also ensures that Oracle FLEXCUBE applications are monitored correctly. For convenience, this appendix has been structured to be relevant to both environments. However, where information is specific to one environment, this is highlighted.
The monitoring support provided by RUEI has been verified against Oracle FLEXCUBE Universal Banking version 10.3, and Oracle FLEXCUBE Direct Banking version FC V.DB5.0 to FC V.DB5.4. Note that Oracle FLEXCUBE Universal Banking version 11g is not supported.
Often the Oracle FLEXCUBE software is configured to use a non-standard port, such as 9000 or 9082. The port on which your Oracle FLEXCUBE installation is running can be found by examining the applications' URLs.
In the case of an Oracle FCUB installation, this usually takes the following format:
http(s)://hostname:portnumber/FCJNeoWeb...
In the case of an Oracle FCDB installation, this usually takes the following format:
http(s)://hostname:portnumber/B001/Internet...
Verify the portnumber
is configured as one of the defined ports (HTTP or HTTPS). In addition, if a HTTPS port is specified, ensure a copy of the Web server's private SSL key is imported into the Collector system(s). To verify the port number, follow the procedure described in Section 8.1, "Managing the Scope of Monitoring".
You can create suite definitions for Oracle FLEXCUBE-based applications in the same way as for any other supported Oracle Enterprise architecture. The procedure to create suites is described in Section 6.5, "Working With Suites".
In order for RUEI to correctly translate the FLEXCUBE business logic within your environment, do the following:
Copy the create_FCUD_info.sh
and/or create_FCDB_info.sh
scripts to the home directory of the Oracle FCUB and FCDB servers. The scripts are located in the /var/opt/ruei/processor/local/download/FCDB
and /var/opt/ruei/processor/local/download/FCDB directories of the RUEI system.
Run the create_FCUD_info.sh
and/or create_FCDB_info.sh
scripts as any user on the Oracle FLEXCUBE server.Foot 1 These scripts assign an identification to the identified page IDs within the environment. The scripts must be run with the following required parameter:
create_FCUB_info.sh connect-string create_FCDB_info.sh connect-string
where connect-string
is the string used to authorize the script to access the Oracle FLEXCUBE database. The script reads from the schemas, and generates .txt
files in the current directory. For example:
create_FCDB_info.sh "sys/oracle@dliild-jde:1522 as sysdba"create_FCDB_info.sh "fcdbuser@fcdbdatabase"
Note that if the connect string uses "sys as sysdba", the script tries to detect the correct schema for the various tables used. Otherwise, it assumes the user is the default schema user.
The script creates a number of .txt
files in the directory where the script is executed. All relevant .txt
files are collected and stored in a .zip
file. Copy this .zip
file to a location that can be used for uploading the files to the RUEI Reporter system.
Select Configuration, then Applications, then Suites, and select the suite you defined earlier.
Specify the name of the .zip
file containing the generated .txt
files. If you manually create .txt
files, you should use the same structure present in the .zip
file. To protect against empty definitions, the upload will fail when it contains empty .txt
files. When ready, click Upload.
When creating an Oracle FLEXCUBE suite instance, a preconfigured cookie for the FCUB and FCDB environments is automatically created. This is implemented as a custom cookie, with the name JSESSIONID
. This will probably be suitable for your Oracle FLEXCUBE environment. However, depending on the configuration of your environment, you may need to modify this. In addition, to enable RUEI to monitor and track users over the complete session, please ensure the cookie path is set to "/".
Verifying the Cookie Configuration
To verify your cookie configuration, do the following:
Clear all cookies in the browser.
(Re)login to the Oracle FLEXCUBE application.
View a few pages in the Oracle FLEXCUBE application.
Logout.
Wait for at least 10 minutes.
Open the RUEI Reporter environment.
Select Browse data, open the All sessions group, select Session diagnostics, and locate the recorded session (by user ID or time). You can filter on applications.
Open the session and verify that:
There are more page views reported than just the login. This verifies the session ID is preserved after the login.
At least some Oracle FLEXCUBE application activity has been recorded.
When not all hits are connected with the same cookie (these are reported as anonymous pages), it is recommended you investigate where the problem is located, and resolve it in the appropriate manner. For example, the domain or path option of the cookie.
To ensure the quality of the data being collected and reported by RUEI for your Oracle FLEXCUBE applications, it is strongly recommended you verify their reported details. You should pay particular attention to the number of associated pages detected for the defined suite(s).
Select Browse data, then select the All pages group, and then the Applications sub-group. Within the individual dimensions, such as Page views and hits, you can see page views are reported for several applications. The suite name in the definition is shown between brackets. An example is shown in Figure L-1.
Figure L-1 Oracle FLEXCUBE Suite Page Views
Oracle FLEXCUBE Direct Banking can be configured in such a way that the portal name does not appear in the application URLs. In this case, a configuration file needs to be uploaded to enable RUEI to translate either the server IP address or the virtual hostname (fully qualified hostname) of the Oracle FLEXCUBE Direct Banking Web server to the correct portal name. This configuration file should be called FCDB_hostnameorserverip2portalcode.txt
, and contain the tab-separated hostname/IP to portal code translations. These portal codes should be available in the database. After running the create_FCDB_info.sh
script, the FCDB_portalcode2portalname.txt
file contains the valid portal codes found in the database.
The following is an example of a valid host /IP address to portal configuration:
# This translation file is used to identify the portal when the portal information # is not available in the URL. Fill this file with either hostname -> portal or # server IP -> portal information. The description will be extracted from the # FCDB database. # Format example: #myhost.mybank.com B004 #10.72.11.89 B007 www.oraclebanking.com B001 192.168.32.78 B002
The file should be added to the zip file created by the create_FCDB_info.sh
script prior to uploading it to RUEI.
Currently, RUEI does not work with all Oracle FLEXCUBE functionality. In particular, the following known limitations exist:
Reporting is based on the last activated area. Hence, when an end user is browsing simultaneously in multiple browser windows, the reported page name may contain incorrect information.
Currently, the create_FCDB_info.sh
and create_FCUB_info.sh
scripts only run on Unix Oracle FLEXCUBE servers.
An error is not immediately reported if an invalid connect string is specified when running the create_FCDB_info.sh
or create_FCUB_info.sh
scripts. You will need to press Enter several times before any error is reported.
Currently, the Traffic summary facility (select System, then Status, and then Data processing) is based on application logic. Therefore, FCDB and FCUB traffic is not represented in the processing overviews.
An Oracle FLEXCUBE implementation, and the FCDB or FCUB instance, can be identified with a hostname. Generally, an Oracle FLEXCUBE suite can be accessed in two ways: using only the hostname, or using the fully-qualified hostname (including the domain). Generally, you only need to specify the domain.
Table L-1 shows how an FCDB application's dimensions are reported in RUEI.
Table L-1 FCDB Suite Definitions Mapping
Dimension level | Content |
---|---|
Application.name |
|
Application. page-group |
|
Application.page-name |
|
where:
module_name
is the name of the FCDB module of the user flow. For example, the application code for the "load details" user flow is "loan management". In most situations, this corresponds with the selected item in the top menu, and/or the first item in the crumblepath.
user_flow_name
is the name of the FCDB user flow being used. In most situations, this corresponds with the selected item in the bottom menu, and/or the second item in the crumblepath.
user_flow_code
is the full user flow code used by the end user. Usually, this code usually consist of three parts. The first two characters indicate the application code, and is usually "RR". The next three characters contain the user flow code (for example, "TDD" for "term deposit details"). The last two characters indicate the step within a user flow. This is usually a number between "01" and "05". For more information, please refer to the Oracle FLEXCUBE Direct Banking documentation.
Figure L-2 shows an example of how a FCDB application is reported in RUEI.
Figure L-2 Example FCDB Application Page Name Reporting
Table L-2 shows how a FCUB application's dimensions are reported in RUEI.
Table L-2 FCUB Suite Definitions Mapping
Dimension level | Content |
---|---|
Application.name |
|
Application. page-group |
|
Application.page-name |
|
where:
module_name
is the name of the FCUB module of the screen used by the user. Every screen belongs to a module. Modules can be separately licensed, but most are part of a standard installation or setup. Examples of such modules include Static Maintenance and Security Management System.
module_code
is the code of the FCUB module of the screen used by the user. Module codes usually consist of two characters (for example, "ST", "CO", and so on).
screen_name
is the name of the FCUB screen being used. Almost all FCUB interaction takes place using screens. Screens can also have subscreens. These are windows opened by pressing a button or link within a screen. Example of screen names are "Customer maintenance", "Sweep account details", and so on.
subscreen_code
is the name of the subscreen opened by a user. For example, "main", "CVS_INTEREST", "CVS_DIARY", and so on.
action
contains the actions performed by an user. For example, "start screen", "show list of values sweep type", "executequery", "QueryCustAcc", and so on.
Figure L-3 shows an example of how a FCUB application is reported in RUEI.
Figure L-3 Example FCUB Application Page Name Reporting
This section describes the database tables used within an Oracle FLEXCUBE environment to retrieve customization information.
The following Oracle FLEXCUBE database tables are used by the create_FCDB_Info.sh
script to retrieve information about the customizations:
MSTUSERTYPE (ID_ENTITY, IDCHANNEL, USERTYPE, IDTXN, TOKEN2) in conjunction with table MSTTXN (IDTXN) and APPLDATA(IDDEVICE, DATAVALUE and DATANAME) to generate the files FCDB_identityidtxnidchannelusertype2menulevel1.txt
, FCDB_identityidtxnidchannelusertype2menulevel2.txt
, FCDB_identityidtxn2menulevel1.txt
, and FCDB_identityidtxn2menulevel2.txt
.
MSTUSERTYPES (TYPEUSER and DESCRIPTION) to generate FCDB_usertypecode2usertypedescription.txt
.
APPLDATA: (DATANAME and DATAVALUE) to generate FCDB_portalcode2portalname.txt
and FCDB_channelcode2channelname.txt
.
The following Oracle FLEXCUBE database tables are used by the create_FCUB_info.sh
script to retrieve information about the customizations:
FBTBMSG (MSGCODE and MSGDESCRIPTION) to generate FCUB_ec2desc.txt
.
SMTBFUNCDESC (FUNCTION_ID and DESCRIPTION) to generate FCUB_fnid2desc.txt
.
GWTMFCJUNC (FUNCTION_ID, ACTION, OPERATION_CODE) to generate FCUB_fnidac2adesc.txt
.
SMTBMENUNAME (FUNCTION_ID and MODULE) to generate FCUB_fnid2moduleid.txt
.
SMTBMENUNAME (FUNCTION_ID) and SMTBMODULES (MODULE_ID and MODULE_DESC) to generate FCUB_fnid2moduledesc.txt
.
STTMBRANCH (BRANCH_CODE and BRANCH_NAME) to generate FCUB_brcd2brnm.txt
.
The Oracle FLEXCUBE-specific data items shown in Table L-3 are reported by RUEI.
Item | Description |
---|---|
FC Direct Banking suite/Code |
The code of a Oracle FLEXCUBE Direct Banking suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored Oracle FLEXCUBE Direct Banking suites. |
FC Direct Banking suite/Name |
The name of a Oracle FLEXCUBE Direct Banking suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored Oracle FLEXCUBE Direct Banking suites. |
FC Direct Banking portal/Code |
The code of the Oracle FLEXCUBE Direct Banking portal used. The Oracle FLEXCUBE Direct Banking portal makes it possible to distinguish between the different portals monitored during sessions. |
FC Direct Banking user type/Code |
All users are assigned a user type in the Oracle FLEXCUBE Direct Banking database. This provides information about the assigned user type of users. The Oracle FLEXCUBE Direct Banking user type code/name makes it possible to distinguish between the different types of monitored users. |
FC Direct Banking user type/Name |
All users are assigned a user type in the Oracle FLEXCUBE Direct Banking database. This provides information about the assigned user type of users. The Oracle FLEXCUBE Direct Banking user type code/name makes it possible to distinguish between the different types of monitored users. |
FC Direct Banking channel/Code |
The code of the Oracle FLEXCUBE Direct Banking channel used. The Oracle FLEXCUBE Direct Banking channel name makes it possible to distinguish between the different channels used by application users. |
FC Universal Banking suite/Code |
The code of a Oracle FLEXCUBE Universal Banking suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored Oracle FLEXCUBE Universal Banking suites. |
FC Universal Banking suite/Name |
The name of a Oracle FLEXCUBE Universal Banking suite, as defined in its configuration definition. This data makes it possible to distinguish between different monitored Oracle FLEXCUBE Universal Banking suites. |
FC Universal Banking Action/Code |
The code of the action performed by the user in a screen. This makes it possible to distinguish between the different actions seen during sessions. |
FC Universal Banking Action/Name |
The name of the action performed by the user in a screen. This makes it possible to distinguish between the different actions seen during sessions. |
FC Universal Banking Branch/Code |
The code of the branch in which a user has been working. This makes it possible to distinguish between actions/work in different branches. |
FC Universal Banking Branch/Name |
The name of the branch in which a user has been working. This makes it possible to distinguish between actions/work in different branches. |
FC Universal Banking Module/Code |
The code of the Oracle FLEXCUBE Universal Banking module used. All screens are part of a module. This makes it possible to distinguish between the different modules used by application users. |
FC Universal Banking Module/Name |
The name of the Oracle FLEXCUBE Universal Banking module used. All screens are part of a module. This makes it possible to distinguish between the different modules used by application users. |
FC Universal Banking Screen/Code |
The code of the Oracle FLEXCUBE Universal Banking screen used. The Oracle FLEXCUBE Universal Banking screen code makes it possible to distinguish between the different screens used by application users. |
FC Direct Banking Screen/Name |
The name of the Oracle FLEXCUBE Universal Banking screen used. The Oracle FLEXCUBE Universal Banking screen name makes it possible to distinguish between the different screens used by application users. |
Footnote Legend
Footnote 1: The script can also be run in the acceptance environment if it is equivalent to the production environment.