M Oracle FLEXCUBE Support
Introduction to Oracle FLEXCUBE
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 11g, and Oracle FLEXCUBE Direct Banking version FC V.DB5.0 to FC V.DB5.4.
Verifying the Scope of Monitoring
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 Managing the Scope of Network Based Monitoring.
Creating Oracle FLEXCUBE Suite Definitions
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 Working With Suites.
Running the create_FCUB_info.sh and create_FCDB_info.sh Scripts
In order for RUEI to correctly translate the FLEXCUBE business logic within your environment, do the following:
Verifying the Cookie Technology
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:
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.
FCDB Portal Recognition
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.
Hostnames and URL Prefixes
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.
Database Tables
This section describes the database tables used within an Oracle FLEXCUBE environment to retrieve customization information.
FCDB Customizations
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
, andFCDB_identityidtxn2menulevel2.txt
. -
MSTUSERTYPES (TYPEUSER and DESCRIPTION) to generate
FCDB_usertypecode2usertypedescription.txt
. -
APPLDATA: (DATANAME and DATAVALUE) to generate
FCDB_portalcode2portalname.txt
andFCDB_channelcode2channelname.txt
.
FCUB Customizations
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
.
Data Items
The Oracle FLEXCUBE-specific data items shown in Table M-1 are reported by RUEI.
Table M-1 Dimensions
Item | Description |
---|---|
FC Direct Banking Channel |
The name of the FLEXCUBE Direct Banking channel that was used by a user during the session |
FC Direct Banking Channel Code |
The code of the FLEXCUBE Direct Banking channel that was used by a user during the session |
FC Direct Banking Portal |
The name of the FLEXCUBE Direct Banking portal used during the session |
FC Direct Banking Portal Code |
The code of the FLEXCUBE Direct Banking portal used during the session |
FC Direct Banking User Type |
The name of the FLEXCUBE Direct Banking user type of the user |
FC Direct Banking User Type Code |
The code of the FLEXCUBE Direct Banking user type of the use |
FC Universal Banking Action |
The name of the FLEXCUBE Universal Banking action that was performed in a screen or subscreen |
FC Universal Banking Action Code |
The code of the FLEXCUBE Universal Banking action that was performed in a screen or subscreen |
FC Universal Banking Branch |
The name of the FLEXCUBE Universal Banking branch that was active during the views |
FC Universal Banking Branch Code |
The code of the FLEXCUBE Universal Banking branch that was active during the view |
FC Universal Banking Module |
The name of the FLEXCUBE Universal Banking module to which the screen or subscreen belongs |
FC Universal Banking Module Code |
The code of the FLEXCUBE Universal Banking module to which the screen or subscreen belongs |
FC Universal Banking Screen |
The name of the FLEXCUBE Universal Banking screen that was viewed |
FC Universal Banking Screen Code |
The code of the FLEXCUBE Universal Banking screen that was viewed |
FC Universal Banking Subscreen |
The name of the FLEXCUBE Universal Banking subscreen that was viewed |
FC Universal Banking Subscreen Code |
The code of the FLEXCUBE Universal Banking subscreen that was viewed |
Known Limitations
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
andcreate_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
orcreate_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 Reporter Statistics) is based on application logic. Therefore, FCDB and FCUB traffic is not represented in the processing overviews.
-
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.