Oracle Financial Services Analytical Applications Infrastructure (OFSAAI) is a general-purpose Analytics Applications infrastructure that provides the tooling platform necessary to rapidly configure and develop Analytic Applications for the financial services domain. It is built with Open-Systems Compliant architecture providing interfaces to support business definitions at various levels of granularity.
Applications are built using OFSAAI by assembling Business Definitions or Business Metadata starting from Data Model to lower grain objects like Dimensions, Metrics, Security Maps, and User Profile to higher-order objects like Rules, Models, and Analytic Query Templates which are assembled using the lower grain ones. In addition to application definition tools, it provides the entire gamut of services required for Application Management including Security Service, Workflow Service, Metadata Management, Operations, Life-cycle Management, Public API’s and Web Services that are exposed to extend and enrich the tooling capabilities within the applications.
Oracle Financial Services Analytical Applications Infrastructure is the complete end-to-end Business Intelligence solution that is easily accessible via your desktop. A single interface lets you tap your company’s vast store of operational data to track and respond to business trends. It also facilitates the analysis of the processed data. Using OFSAAI you can query and analyze data that is complete, correct, and consistently stored in a single place. It has the prowess to filter data that you are viewing and using for analysis.
It allows you to personalize information access to the users based on their role within the organization. It also provides a complete view of your enterprise along with the following benefits:
· Track enterprise performance across Information Data Store.
· Use one interface to access all Enterprise Databases.
· Create consistent business dimensions and measures across Business Applications.
· Automate the creation of coordinated Data Marts.
· Use your own business language to get fast and accurate answers from all your Databases.
· Deploy an open XML and Web-based Solution against all major relational or Multi-dimensional Databases on Microsoft Windows and UNIX Servers.
This chapter provides an overview of Infrastructure, its components, and explains how these components are organized in the Splash Window with the user login process.
The OFSAA Infrastructure consists of the following components/modules that are used to deploy an Analytical Solution.
· Data Entries Forms and Queries
· Infrastructure Modules Operations
· Infrastructure Modules System Configuration and Identity Management
All components are encapsulated within a common Security and Operational Framework as shown in the following figure.
Figure 1: Security and Operational Framework
Infrastructure also supports many business analytical solution(s) like Operational Risk, PFT, and Basel, which are licensed separately to the organization. This manual provides an overview of only the technological components.
For a detailed overview of OFSAAI Modules, see Modules in OFSAAI section.
OFSAA can be accessed through your Web Browser as soon as the System Administrator (SA) installs and configures Oracle Financial Services Analytical Applications.
The SA will provide you with a link through which you can access Oracle Financial Services Analytical Applications. You can access the login window through your Web Browser using the URL http(s): <IP Address of the Web Server > :<servlet port>/<context name>/login.jsp.
You can also log in to the application with the hostname instead of the IP Address.
On entering the URL (<IP Address/hostname of the Web Server>:<servlet port>/<context name>/login.jsp) in your browser window, the OFSAA Login Page is displayed:
Figure 2: OFSSA login Page
You can select the required language from the Language drop-down list. The language options displayed in the drop-down list are based on the language packs installed for the OFSAA infrastructure. Based on the selected language, the appropriate Language Login Window is displayed.
Enter the User ID and Password provided by the System Administrator and click Login. You will be prompted to change your password on your first login. For details on how to change a password, see the Changing Password Section.
In case the OFSAA Setup has been configured for OFSAA native Security Management System (SMS) Authentication, the password to be entered will be as per the password restrictions set in the OFSAA SMS repository.
Post-installation, the first login into Infrastructure is possible only for a System Administrator through User-ID “sysadmn”. This ID is created at the time of installation with the default password as “password0”.
Enter User ID as “sysadmn” and password as “password0”. Click Login.
System Authorizer ID is also created at the time of installation with the default password “password0”. This ID is required to authorize the users created by the system administrator.
Enter login id as “sysauth” and password as “password0”. Click Login.
The Business Users will be created by System Administrator and will be authorized by the System Authorizer.
Enter User ID and Password provided by the System Administrator and click Login.
If the OFSAA setup has been configured for LDAP Authentication, the Login Page is displayed as shown:
Figure 3: OFSSA Login Page
1. Enter your User ID and Password (as in LDAP store) in the respective fields.
2. Select the appropriate LDAP Server from the drop-down list, against which you want to get authenticated. This is optional. If you do not select any server, you will be authenticated against the appropriate LDAP Server.
NOTE:
For SYSADMN/ SYSAUTH/ GUEST Users, no need to select any LDAP Server as they are always authenticated against the SMS store. Additionally, in case a specific user has been marked as “SMS Auth Only” in the User Maintenance window even though the OFSAA instance is configured for LDAP authentication, then that user will also be authenticated against the SMS store instead of LDAP store. The user has to enter the password as per the SMS store.
You can choose to change your password any time by clicking your username appearing on the right top corner and selecting Change Password.
Note that this option is available:
· If SMS Authentication and Authorization is configured as Authentication Type from the Configuration Window.
· If LDAP Authentication and SMS Authorization is configured as Authentication Type from the Configuration Window and the SMS Auth Only check box is selected for the user in the User Maintenance Window.
· If SSO Authentication and SMS Authorization is configured as Authentication Type from the Configuration Window and the SMS Auth Only check box is selected for the user in the User Maintenance Window.
Figure 4: OFSSA Change Password window
In the Change Password Window, enter a new password, confirm it, and click OK to view the OFSAA Login Window. See the following guidelines for Password Creation:
· Passwords are displayed as asterisks (stars) while you enter. This is to ensure that the password is not revealed to other users.
· Ensure that the entered password is at least six characters long.
· The password must be alphanumeric with a combination of numbers and characters.
· The password should not contain spaces.
· Passwords are case sensitive and ensure that the Caps Lock is not turned ON.
· By default, the currently used password is checked for validity if password history is not set.
· The new password should be different from previously used passwords based on the password history, which can be configured. For more information, see the Configuration section in the System Configuration Chapter.
If you encounter any of the following problems, contact the System Administrator:
· Your user ID and password are not recognized.
· Your user ID is locked after three consecutive unsuccessful attempts.
· Your user ID has been disabled.
· The Guest User cannot change the password.
On successful login, the OFSAA Landing Page is displayed.
Figure 5: OFSAA Landing Page
OFSAA Landing Screen shows the available Applications as tiles, for which a user has access. Clicking the respective Application tile launches that particular Application. You can change the Landing Page based on your preference. For more information, see the Preferences Section.
Figure 6: OFSSA Header
Hamburger/Navigation Menu Icon- This icon is used to trigger the Application Navigation Drawer.
Application Icon- This icon is used to show the available Applications installed in your environment at any time.
Administration Icon- This icon is used to go to the Administration Window. The Administration Window displays modules like System Configuration, Identity Management, Database Details, manage OFSAA Product Licenses, Create New Application, Information Domain, Translation Tools, and process Modelling Framework as Tiles.
Reports Icon- This icon is used to launch various User Reports such as user Status Report, User Attribute Report, User Admin Activity Report, User Access Report, and Audit Trial Report.
Language Menu- It displays the language you selected in the OFSAA Login Screen. The language options displayed in the Language Menu are based on the language packs installed in your OFSAA instance. Using this menu, you can change the language at any point of time.
User Menu- Clicking this icon displays the following menu:
Figure 7: User Menu
§ Preferences- To set the OFSAA Landing Page.
§ Change Password- To change your password. For more information, see the Change Password section. This option is available only if SMS Authorization is configured.
§ Log Out- To log out from OFSAA Applications.
Last Login Details - This displays the last login details as shown:
Figure 8: Last Login Details
Click Hamburger Icon to launch the Navigation Drawer as shown:
Figure 9: Navigation List drawer
Here the navigation items appear as a list. The First Level menu shows the installed applications. Clicking an application displays the second-level menu with the application name and Common tasks menu. The arrangement of the menu depends on your installed application.
Clicking an item in the menu displays the next level sub-menu and so on. For example, to display Data Sources, click Financial Services Enterprise Modeling>Data Management>Data Management Framework>Data Management Tools>Data Sources.
Figure 10: Data Management Tools Menu
Click 
Hierarchical Menu to display the navigation path
of the current sub-menu as shown:
Figure 11: Data Management Tools Hierarchical Menu
The RHS Content Area shows the Summary Page of Data Sources.
Click anywhere in the Content Area to hide the Navigation Drawer. To launch
it back, click the Hamburger Icon
.
Click Home to display the OFSAA Landing Screen.
· Data Model Management is intended for uploading the Warehouse Data from the Operational Systems to Database Schema using ERwin XML file.
· Data Management Framework is a comprehensive Data Integration Platform that facilitates all the Data Integration requirements from high-volume and high-performance batch loads to event-driven integration processes and SOA-enabled Data Services. This module is used for managing Data Movement. This includes sub-modules like Data Sources, Data Mapping, Post Load Changes, and Data Quality Framework.
· Data Entry Forms and Queries Module facilitates you to design Web-based user-friendly Data Entry Windows with a choice of layouts for easy Data View and Data Manipulation. This module has sub-modules like Forms Designer, Data Entry, and Excel Upload.
· Data Maintenance Interface Module helps in the design and creation of forms that are in a user-specified format. Authorized users with the required privileges can use these forms to view and update existing data in the Database.
· Unified Analytical Metadata is intended for the Information and Business Analysts who are instrumental in supporting and affecting analytical decisions. This module is used to define and maintain Analytical Metadata Definitions. This module has sub-modules like Alias, Derived Entity, Dataset, Dimension Management, Business Measure, Business Processor, Build Hierarchy, Business Dimension, Essbase Cube, Filters, Expression, Map Maintenance, and Cube Migration.
· Rule Run Framework facilitates you to define a set of rules, reporting objects, and processes that are required to transform data in a warehouse. This module has sub-modules like Rule, Process, Run, and Manage Run Execution.
· Metadata Browser module provides extensive browsing capabilities of metadata, helps in tracking the impact of changes to metadata, and traces through to the source of originating data. The metadata in the Metadata Browser Window is organized into different categories like Data Foundation Metadata, Business Metadata, and Process Metadata.
· Operations Module facilitates you in the administration and processing of business data to create the highest level of efficiency within the system and to derive results based on a specified rule. It includes sections like Batch Maintenance, Batch Execution, Batch Scheduler, Batch Monitor, Batch Processing Report, Batch Cancellation, and View Log.
· Questionnaire Module is an assessment tool, which presents a set of questions to users, and collects the answers for analysis and conclusion. It can be interfaced or plugged into OFSAA Application Packs.
· System Configuration & Identity Management Module facilitates System Administrators to provide Security and Operational Framework required for Infrastructure. The Administration Window has a Tiles menu with Tiles like System Configuration, Identity Management, Database Details, Manage OFSAA Product Licenses, Create New Application, Information Domain, Translation Tools, and Process Modelling Framework.
· Object Administration facilitates System Administrators to define the Security Framework with the capacity to restrict access to the data and metadata in the warehouse, based on a flexible, fine-grained access control mechanism. These activities are mainly done at the initial stage and then on a need basis. It includes sections like Object Security, Object Migration, and Utilities (consisting of Metadata Difference, Metadata Authorization, Save Metadata, Write-Protected Batch, Component Registration, Transfer Document Ownership, and Patch Information).
Logging in OFSAA is done using Log4J. The log files are available in the following locations:
· UI/Web Logs: <DEPLOYED LOCATION>/<Context>.ear/<Context>.war/logs
· Application Logs: $FIC_HOME/logs
· Execution Logs: /ftpshare/logs/<MISDATE>/<INFODOM>/<COMPONENT NAME>/<LOG FILE NAME>.log
Configure the logger-related attributes in the RevLog4jConfig.xml file available in the $FIC_HOME/conf/ folder. Each log file will have appenders in this file and attributes pertaining to this particular appender can be changed.
The default size of the log files is set to 5000 KB and the number of maximum backup log files retained is set to 5, both of which are configurable. Increasing these parameters to a higher value should depend on the Server Hardware Configurations and may reduce the performance.
To configure the Logs file size, follow these steps:
1. Navigate to $FIC_HOME/conf folder or <DeployedLocation>/<context.war>/<context>/ and locate RevLog4jConfig.xml file.
2. Configure the logger-related attributes in the RevLog4jConfig.xml file. This file will have Appenders for each log file.
Sample Appender for UMM log file is shown:
<RollingFile name="UMMAPPENDER" fileName="/scratch/ofsaaweb/weblogic/user_projects/domains/cdb/applications/cdb.ear/cdb.war/logs/UMMService.log"
filePattern="/scratch/ofsaaweb/weblogic/user_projects/domains/cdb/applications/cdb.ear/cdb.war/logs/UMMService-%i.log" >
<PatternLayout>
<Pattern> [%d{dd-MM-yy HH:mm:ss,SSS zzz aa}{GMT}] [%-5level] [WEB] %m%n </Pattern>
</PatternLayout>
<Policies>
<SizeBasedTriggeringPolicy size="5000 KB" />
</Policies>
<DefaultRolloverStrategy max="5"> <!-- number of backup files -->
</DefaultRolloverStrategy>
</RollingFile>
3. To change the log file size, modify the value set for SizeBasedTriggeringPolicy size.
4. To change the number of backup files to be retained, modify the value set for DefaultRolloverStrategy max.
In OFSAA, the log format is standardized and can be read by any standard log analysis tool. The standard log format is as follows:
[GMT TIMESTAMP] [LOGGER LEVEL] [LOGGER LOCATION] [MODULE/COMPONENT] [LOGGED IN USER] [JAVA CLASS] <LOG MESSAGE>
Sample:
[25-04-18 10:08:41,066 GMT AM] [INFO ] [WEB] [UMM] [UMMUSER] [BUSINESSMETADATA] Inside createImplicitObjectsForAllInfodom
[25-04-18 10:08:41,069 GMT AM] [INFO ] [WEB] [UMM] [UMMUSER] [BUSINESSMETADATA] Call createImplicitObjectsForMapper for infodom = TESTCHEF
[25-04-18 10:08:42,142 GMT AM] [DEBUG] [WEB] [UMM] [UMMUSER] [BUSINESSMETADATA] Source created successfully for infodom TESTCHEF
[25-04-18 10:08:42,142 GMT AM] [INFO ] [WEB] [UMM] [UMMUSER] [BUSINESSMETADATA] Start - code added to create user group hierarchy for this infodom
[25-04-18 10:08:42,142 GMT AM] [INFO ] [WEB] [UMM] [UMMUSER] [BUSINESSMETADATA] Inside createUserGroupHierarchyForInfodom