On successful installation of the Oracle Financial Services CRA application pack, follow the post-installation procedures mentioned in Post-installation Checklist.
NOTE:
You must clear the application cache before deploying the Application Pack web archive file. This applies to all web servers (WebSphere, WebLogic, Tomcat). For more information, see the Clear Application Cache section.
Topics:
· Patch OFSAA Infrastructure Installation
· Backup the OFS_CRA_SCHEMA_IN.xml, OFS_CRA_SCHEMA_OUTPUT.xml, and Silent.props Files
· Stop the Infrastructure Services
· Start the Infrastructure Services
· Configure Resource Reference in Web Servers
· Configure Work Manager in Web Application Servers
· Create and Deploy the EAR or WAR Files
· Build EAR or WAR file once and Deploy Across Multiple OFSAA Instances
· Access the OFSAA Application
· Configure the excludeURLList.cfg File
· View OFSAA Product Licenses after Installation of Application Pack
· Change the ICC Batch Ownership
· Add TNS entries in the TNSNAMES.ORA File
· Configure Data Redaction in OFSAA
· Data Protection Implementation in OFSAA
· Post-Deployment Configurations
You can use this checklist to have a quick glance at everything that you will be doing post installing this application. The link provided in each step takes you to a section either within this document or to another referenced document.
NOTE:
See the Post-Installation section in the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide to complete the following checklist procedures.
Sl. No. |
Post-installation Activity |
|---|---|
1 |
Verify that all patches are successfully installed. |
2 |
Back up the OFS_CRA_SCHEMA_IN.xml, OFS_CRA_SCHEMA_OUTPUT.xml, and Silent.props files. |
3 |
Stop the OFSAA Infrastructure services. |
4 |
Start the OFSAA Infrastructure services. |
5 |
Configure the webserver. |
6 |
Configure the Resource Reference in web application servers. |
7 |
Configure the Work Manager in the web application servers. |
8 |
Create and Deploy EAR or WAR files. |
9 |
EAR/WAR File - Build Once and Deploy Across Multiple OFSAA Instances. |
10 |
Access the OFSAA application. |
11 |
Configure the exclude URLList.cfg file. |
12 |
Configure the Tomcat server. |
13 |
Change the ICC batch ownership. |
14 |
Add TNS entries in the tnsnames.ora file. |
15 |
Update the OBIEE URL. |
16 |
Configure Data Source. |
17 |
Set Data Redaction in OFS CRA. |
18 |
Implement Data Protection in OFSAA. |
19 |
Post-deployment Configuration. · OBIEE Configuration – Deploy OFS CRA Analytics. · Logging as System Administrator. · Create Application Users. · Map the Application User (or users) to User Groups. · Map the CRA Pack User Group Names. |
Oracle strongly recommends installing the latest available patch set to be up-to-date with the various releases of the OFSAA product. For the mandatory patches, see Mandatory Patches section.
Contact My Oracle Support. for more information on the latest release.
Backup the OFS_CRA_SCHEMA_IN.xml, OFS_CRA_SCHEMA_OUTPUT.xml, and Silent.props files as they can be reused when upgrading existing applications or installing new applications.
File Name |
Directory |
|---|---|
OFS_CRA_SCHEMA_IN.xml |
OFS_CRA_PACK/schema_creator/conf |
OFS_CRA_SCHEMA_OUTPUT.xml |
OFS_CRA_PACK/schema_creator/ |
Silent.props |
OFS_CRA_PACK/appsLibConfig/conf |
See Stop the Infrastructure Services in OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide for details.
See Start the Infrastructure Services in OFS AAI Installation Guide for details.
This step assumes the installation of a web server exists as per the prerequisites. If an installation already exists, skip, and proceed to the next step. Webserver configuration includes the following activities.
See the Configure the Web Server section in the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide to complete these procedures.
· Configure WebSphere Application Server for Application Deployment
§ Create a New Profile in WebSphere
§ Manage IBM WebSphere SDK Java Technology Edition Versions
§ Manage Applications in WebSphere
§ Configure WebSphere Application Server to Initialize Filters before Initializing Load-On Startup Servlets
§ Configure WebSphere Application Server Persistence to JPA Specification 2.0
§ Configure WebSphere Application Server to Use a Load Balancer or Proxy Server
§ Delete WebSphere Profiles
§ Configure WebSphere HTTPS
§ Configure WebSphere Memory Settings
· Configure WebLogic for Application Deployment
§ Create Domain in WebLogic Server
§ Configure WebLogic Memory Settings
· Configure Apache Tomcat Server for Application Deployment
§ Configure Apache Tomcat Memory Settings
§ Configure Tomcat for User Group Authorization
§ Uninstall WAR Files in Tomcat
NOTE:
· See the Oracle Financial Services Analytical Applications Infrastructure Security Guide for configurations to secure your web server.
· You must enable a sticky session or affinity session configuration on the web server. See the respective product-specific Configuration Guide for more details. Additionally, you also must enable the sticky session or affinity session configuration at the Load Balancer level if you have configured a Load Balancer in front of the web server.
· Make a note of the IP Address or Hostname and Port of the web application server. This information is required during the installation process (required if the web server is not configured).
· Add umask 0027 in the .profile of the UNIX account which manages the WEB server to ensure restricted access permissions.
· See the OFSAA Secure Configuration Guide or Security Guide mentioned in the Related Documents section for additional information on securely configuring your web server.
This section provides information for additional configuration required for the web servers on OFS CRA.
NOTE
The instructions in this section are applicable if you are upgrading from an earlier version of OFS CRA to Release 8.1.2.0.0.
· Configuration for WebSphere: To configure WebSphere, see the Configure WebSphere Application Server for Application Deployment section. Additionally, configure for REST services. For details, see the Configuring WebSphere for the REST Services Authorization section in the OFS Analytical Applications Infrastructure Administration Guide.
Additionally, you must configure the Work Manager in WebSphere and map it to the OFSAA instance. For details, see the Work Manager Configurations section in the OFS Analytical Applications Infrastructure Administration Guide.
· Configuration for WebLogic: To configure WebLogic, see the Configure WebLogic for Application Deployment section. Additionally, configure for REST services. For details, see the Configuring WebLogic for the REST Services Authorization section in the OFS Analytical Applications Infrastructure Administration Guide.
Additionally, you must configure the Work Manager in WebLogic. For details, see the Work Manager Configurations section in the OFS Analytical Applications Infrastructure Administration Guide.
· Configuration for Tomcat: For the successful execution of Data Mapping in Tomcat, perform the configurations mentioned in the Configuration for Tomcat section in the OFS Analytical Applications Infrastructure Administration Guide.
For additional configurations, see the Configure Apache Tomcat Server for Application Deployment section.
This is a mandatory security procedure for WebSphere to restrict the unauthorized access of configuration files in directories. For detailed information, see the Oracle Financial Services Analytical Applications Infrastructure Security Guide.
Perform the following configuration to set the WebSphere shared library to support Jersey 2x and Jackson 2.9x libraries.
1. Click Environment from the menu on the left to expand and view the list. Click Shared Libraries to open the Shared Libraries window.
Figure 29: WebSphere Shared Libraries
2. Enter the following details:
§ Name: Enter a uniquely identifiable name.
§ Description: Enter a valid description.
§ Classpath: Enter the absolute path where the JARs related to Jersey 2.x and Jackson 2.9x are copied. These jars are available in the <OFSAA_HOME>/ficweb/webroot/externallib/WEBINF/lib/ directory after creation of the EAR file. Another format of representation of the path is <ofsaa_deployed_area_location>/externallib/WEBINF/lib/.
3. Select Use an isolated class loader for this library.
4. Click OK to save to master configuration.
5. Select the application or module and map the shared libraries. Click OK. In the following figure, ofsa is selected.
Figure 30: WebSphere Shared Library References
6. From the Shared Library Mapping window, move the required shared libraries from Available to Selected. In the following figure, JERSEY2x is selected.
Figure 31: WebSphere Shared Libraries Mapping Selection
7. Click OK.
8. Similarly, select the next application or module and repeat the procedure from steps 5 to 7.
Figure 32: WebSphere Shared Libraries Select Next Application
9. Disable the built-in JAX-RS via JVM property.
a. Navigate to the WebSphere admin console in the Servers select WebSphere Application Servers then select yourServerName.
b. In the Server Infrastructure section, go to Java and Process Management select Process definition, select Java Virtual Machine then select Custom properties.
c. Add the following property:
com.ibm.websphere.jaxrs.server.DisableIBMJAXRSEngine=true
NOTE
If the application does not come up post the steps
mentioned above, then, navigate to Application Servers
select server 1, select Web
container then select Custom properties
and modify the following property to True:
com.ibm.ws.webcontainer.emptyServletMappings
= true
10. Restart the application.
Configuring resource reference in webservers includes the following activities. See Configure Resource Reference in Web Servers section in the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide to complete these procedures.
· Configure Resource Reference in WebSphere Application Server
§ Create a JDBC Provider
§ Create Data Source
§ Create J2C Authentication Details
§ Define JDBC Connection Pooling
· Configure Resource Reference in WebLogic Application Server
§ Configure Multi Data Sources
§ Configure Advanced Settings for Data Source
§ Configure JDBC Connection Pooling
· Configure Resource Reference in Tomcat Application Server
§ Define JDBC Connection Pooling
§ Configure ClassLoader for Apache Tomcat
The process Modelling framework requires creating a Work Manager and mapping it to the OFSAA instance. This configuration is required for WebSphere and WebLogic Web application server types.
Configuring Work Manager in web application servers includes the following activities. See Configure Work Manager in Web Application Servers section in the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide to complete these procedures.
· Configure Work Manager in WebSphere Application Server
§ Creating a Work Manager
§ Mapping Work Manager to OFSAA WebSphere Instance
· Configure Work Manager in WebLogic Application Server
See Create and Deploy the EAR or WAR Files in OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide for details.
See EAR or WAR File - Build Once and Deploy Across Multiple OFSAA Instances in OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide for details.
To access the OFSAA application, follow these steps:
1. Open a browser and enter the URL in the following format:
<scheme>://<IP address/ hostname>:<port>/<context-name>/login.jsp
For example, https://192.0.2.2/ofsaa/login.jsp
The OFSAA Login window is displayed.
Figure 33: OFSAA Login Window
With the installation of every OFSAA Application Pack, there are two seeded user profiles configured in the system:
§ SYSADMN System Administrator
§ SYSAUTH System Authorizer
The SYSADMN and SYSAUTH users are configured with a default password, which you will require to login for the first time. See the MOS Doc ID: 2691681.1 for the password.
2. Log in to the application using the SYSADMN User ID and the default password. After the first login, you are prompted to change the password.
ATTENTION:
The password change is required only for a new installation scenario and not for upgrade scenarios
On successful login, the OFSAA Landing screen is displayed.
Figure 34: OFSAA Landing screen
OFSAA Landing screen shows the available Applications as tiles, for which a user has access to. Clicking the respective Application tile launches that particular application. You can change the landing page based on your preference.
This section describes the user interface components in the OFSAA Landing page.
Figure 35: User Interface Components
· Navigation Menu: 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 in time.
· User Menu: Clicking this icon displays the following menu:
Figure 36: User Menu
§ Preferences: To set the OFSAA Landing Page.
§ Change Password: To change your password. For more information, see the Change Password section in the OFS AAI User Guide . 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 37: Last Login Details
To launch the navigation drawer, follow these steps:
1. Click the
Navigation menu 
to
launch the Navigation Drawer as shown.
Figure 38: Navigation 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.
2. 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 select Data Management select Data Management Framework, select Data Management Tools and then select Data Sources.
Figure 39: Navigation Drawer Menus and Submenus
3. Click 
Hierarchical Menu to display the navigation path
of the current submenu as shown.
Figure 40: Navigation Submenu
4. 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 Navigation
menu .
5. Click Home to display the OFSAA Landing Screen.
The Administration and Configuration section allows the System Administrators to configure the Server details, Database details, OLAP details, and Information Domain along with the other Configuration process such as segment and metadata mapping, and mapping segment to security. System Configuration is mostly an onetime activity which helps the System administrator to make the Infrastructure system operational for usage.
Click the Administration Icon
from
the header to display the Administration tools in the Tiles menu. Click
System Configuration from the Tiles menu to
view a submenu list.
NOTE:
After you have accessed
a tool from the submenu, the options are also available in the Navigation
List to the left. Click the Navigation menu 
to
access the Navigation List.
Figure 41: System Configuration Submenu
You (System Administrator) must have full access rights to FTPSHARE directory with appropriate User ID and password to add and modify the server details.
System Configuration consists of the following sections.
· Database Server
· Application Server
· Web Server
· Database Details
· OLAP Details
· Information Domain
· Configuration
· Create Application
See Configure the excludeURLList.cfg File in OFS AAI Installation Guide for details.
In an integrated environment, where you have multiple applications installed on the same domain or infrastructure, OFSAAI allows you to see the other licensed applications through the UI. For more information, see the View OFSAA Product Licenses after Installation of Application Pack in the OFS Analytical Applications Infrastructure User Guide Release 8.1.2.0.0.
To stop generating static content with one print statement per input line, you must configure the web.xml file.
To configure the web.xml file, perform the following steps:
1. Navigate to the tomcat/conf directory.
2. Edit the web.xml file as follows:
3. Set the mapped file parameter to False in the servlet tag mentioned with
<servlet-name>jsp</servlet-name>.
<init-param>
<param-name>mappedfile</param-name>
<param-value>false</param-value>
</init-param>
All seeded Batches in the OFS CRA pack are automatically assigned to the SYSADMN user during installation. To view the batches in the Batch Maintenance menu, you must execute the following query in the Config Schema of the database:
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromUser','toUser','infodom');
end;
OR
begin
AAI_OBJECT_ADMIN.TRANSFER_BATCH_OWNERSHIP ('fromUser','toUser');
end;
Where:
· fromUser indicates the user who currently owns the batch
· toUser indicates the user to whom the ownership must be transferred
· infodom is an optional parameter. If specified, the ownership of the batches of that Infodom will be changed.
Add TNS entries in the tnsnames.ora file for every schema created for the Application Pack. For details see Add TNS entries in the tnsnames.ora File section.
To find the tnsname for the entries, follow these steps:
1. Log in to the application using System Administrator privileges.
2. Navigate to System Configuration & Identity Management tab.
3. Click Administration and Configuration, select System Configuration, and click Database Details.
4. Expand Name to get the list of TNS entry names.
Alternatively, you can connect to the CONFIG schema and execute the following query:
select dbname from db_master where dbname !='CONFIG'
To access the respective Business Intelligence Analytics Application, you must update the OBIEE URL in the AAI_MENU_B table after the OBIEE environment is up and running. Use the following command:
UPDATE AAI_MENU_B
SET V_MENU_URL = '&obieeURL'
WHERE V_MENU_ID IN ('OFS_CRA_BI')
/
COMMIT
/
This section details the configurations required for Data Sources in the OFSAA applications.
· Create a connection pool in the Information Domain. For more information, see the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide.
· JNDI name of the connection pool must be <res-ref-name> as mentioned in the web.xml file. For example: jdbc/OFSINFDOM
· Create and deploy the web components into the web server. For more information on deploying the web components, see the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide.
· The following tag must be added manually in the web.xml file if not already present in the web.xml file.
<resource-ref>
<!-- description>DB Connection INFODOM</description -->
<res-ref-name>jdbc/ INFODOM</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
</resource-ref>
This section details the configurations required in case you want to enable Data Redaction in the OFSAA applications.
Topics:
Ensure the required Oracle Database Server versions are installed:
· Oracle Database Server Enterprise Edition 18c Release 3 – 64-bit RAC/Non-RAC with/without partitioning option, Advanced Security Option.
· Oracle Database Server Enterprise Edition 19c Release 3 – 64-bit RAC/Non-RAC with/without partitioning option, Advanced Security Option.
OFSAA is enhanced to enable masking of sensitive data and Personal Identification Information (PII) to adhere to Regulations and Privacy Policies. Oracle Data Redaction provides selective, on-the-fly redaction of sensitive data in database query results before display by applications so that unauthorized users cannot view the sensitive data. The stored data remains unaltered, while displayed data is transformed into a pattern that does not contain any identifiable information.
To enable Data Redaction, perform the following steps:
1. Log in as SYSDBA into the database.
2. Execute the $FIC_HOME/utility/data_security/scripts/create_data_sec_roles.sql file only once per database (PDB in case of 18c/19c).
3. Execute the following SQL statement to find out the list of atomic users from the table:
select v_schema_name from aai_db_detail where V_DB_NAME <> 'CONFIG' AND V_DB_ TYPE = 'ORACLE'
4. Execute the $FIC_HOME/utility/data_security/scripts/grant_data_sec_roles.sql file for all atomic users found in the previous step.
5. From the Configuration window in the System Configuration module, select the Allow Data Redaction checkbox.
6. Run the Data Redaction utility.
For more details on enabling Data Redaction, see the Data Redaction section in the Data Security and Data Privacy chapter in the OFS Analytical Applications Infrastructure Administration and Configuration Guide.
Data Protection implementation in OFSAA applications includes the following:
· Right to be Forgotten
· Data Portability
· Pseudonymization
· Notice and Consent
· Data Archival
· Data Redaction
See the OFSDF Data Protection Implementation Guide for details.
Right to be Forgotten is the task of removing Personally Identifiable Information (PII) of a Data Subject for the given Party. The financial institution can delete PII for those Data Subjects who have requested this Right to be Forgotten functionality.
The Data Subjects may have made significant financial transactions, and/or financial information may be required for regulatory or compliance reporting. Deleting the complete record that consists of PII may lead to issues in data reconciliation. In OFSAA, the PII data will be replaced with randomized values and therefore, the complete Data Subject record is retained. As a result, financial information is retained; however, the associated Party PII is removed permanently.
To configure Right to be Forgotten, follow these steps:
1. Ensure that you assign the role Data Controller to the CRA user.
2. Edit the task of the batch <Infodom_name>_RightToForget. By default the parameter is SYSADMN. Modify the user ID in the Metadata Value field to the CRA Data Controller user ID from Step 1.
Figure 42: Configure Right to be Forgotten for OFS CRA
3. Add the party IDs entries for the Right to Forget in the FSI_PARTY_RIGHT_TO_FORGET table.
4. Execute the batch <Infodom_name>_RightToForget, for the specific FIC MIS date mentioned in the FSI_PARTY_RIGHT_TO_FORGET table.
This section includes the post-deployment configuration steps.
Topics:
· Deploy the OFS CRA Analytics
· Logging as System Administrator
· Mapping Application User (or Users) to User Group
The OFS CRA Analytics application release 8.1.2.0.0 is based upon a dedicated reporting mart built from the new Fusion Financial Services Data Model. OFS CRA Analytics 8.1.2.0.0 leverages several components of Oracle Business Intelligence Enterprise Edition (OBIEE) or Oracle Analytics Server (OAS) technology including Dashboards and Answers.
Follow these steps to configure the OFS CRA Analytics:
1. Make sure Oracle Business Intelligence 12.2.1.4.0 or OAS 5.5.0 installation is completed and available. See Installing and Configuring Oracle Business Intelligence 12c (12.2.1.4) (E91876-03) or Installing and Configuring Oracle Analytics Server 5.5.0 (F27232-03) for more details.
2. Configure the ODBC data source to connect to the Oracle BI Server:
a. Navigate to Control Panel, select Administrative Tools, and then select Data Sources (ODBC).
b. Select the System DSN tab and click Add.
c. Select a driver-specific to Oracle BI Server 2.2.1.4.0 or OAS 5.5 and click Finish.
d. Enter the Name and Server details (specify the Hostname or IP Address of the BI Server) and click Next.
e. Enter the Oracle BI Server login ID and password (Enter the User Name and Password created at the time of OBIEE or OAS installation). Update the port with the port number available for the BI Server in the Availability tab of Business Intelligence in the Enterprise Manager.
For example: In the following figure, the port number is 9514.
Figure 43: Update Port Number in the BI Server
f. Click Next.
g. Navigate to the RPD and Catalog folders available in the following directories. Copy the RPD and required Catalog files in the server where the BI client tools are installed:
— $FIC_HOME/OFS_CRA_DASHBOARDS/12.2.1.4.0/datamodel directory containing the CRMBI.rpd file in the data model directory.
— CRMBI.catalog file in the $FIC_HOME/OFS_CRA_DASHBOARDS/12.2.1.4.0/content/catalog directory.
h. Click Finish.
3. Modify the connection pool and set the properties.
a. Open the OBI Administration tool.
b. Select Start, select Programs, select Oracle Business Intelligence, and then select BI Administration.
c. Select File, select Open, select Offline, and then select the CRMBI.rpd file.
d. In the Open dialog box, select and open the CRMBI.rpd file.
e. Enter the Repository password. See the MOS Doc ID: 2691681.1 for the password.
f. In the Physical layer, double-click the Connect Pool: CRMBI to open its properties.
g. In the General tab, edit and check the following entries:
i. Call Interface: (OCI 10g/11g).
ii. Data source name: <TNS Entry connecting to OFSAA atomic schema>
For example: (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=<Database IP address>)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=<Database Name>)))
iii. User name: <enter atomic db user name>.
iv. Password: <enter atomic db user password>.
v. Confirm the password and click OK to close the window.
vi. Similarly, configure the connection pools for CRMBITRANS and CRMBI_INIT_BLOCK and CRMBI.
— Check Global Consistency, that is, press Ctrl+k.
— Double-click on the warning (if you are using OAS).
— Click Reset to defaults and click OK.
vii. Click Save.
h. Click Yes for the Global Consistency Message. No warnings should be generated at this stage.
i. Close the RPD file (close the file and exit).
4. Log in to the OFS Credit Risk Analytics application using the
URL: http:// <ipaddress>:<port>/analytics (replace the port number based on your setup).
5. Perform the following OBIEE presentation server configuration steps:
a. Navigate to the <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory.
b. Edit the instanceconfig.xml file.
c. Insert the following code within the XML tag <Views> </Views>.
<Charts>
<MaxVisibleColumns>50000</MaxVisibleColumns>
<MaxVisiblePages>25000</MaxVisiblePages>
<MaxVisibleRows>10000000</MaxVisibleRows>
<MaxVisibleSections>50000</MaxVisibleSections>
<JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>
</Charts>
d. Insert the following code within the XML tag <Views> </Views>.
<Views> </Views>.
<Table>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>6500</DefaultRowsDisplayedInDownload>
<MaxCells>4000000</MaxCells>
<MaxVisibleRows>140000</MaxVisibleRows>
</Table>
<Narrative>
<MaxRecords>500000</MaxRecords>
<DefaultRowsDisplayed>25</DefaultRowsDisplayed>
</Narrative>
e. Insert the following code within the XML tag
<Views> </Views>
<Pivot>
<DefaultRowsDisplayedInDelivery>70000
</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>70000
</DefaultRowsDisplayedInDownload>
<DisableAutoPreview>false</DisableAutoPreview>
<MaxCells>10000000</MaxCells>
<MaxVisibleRows>140000</MaxVisibleRows>
<MaxVisibleSections>600000</MaxVisibleSections>
<MaxVisibleColumns>50000</MaxVisibleColumns>
<MaxVisiblePages>10000</MaxVisiblePages>
</Pivot>
f. Insert the following code within the XML tag
<Views> </Views>
<Cube>
<CubeMaxRecords>10000000</CubeMaxRecords>
</Cube>
g. Insert the following code within the XML tag
<Views> </Views>
<Charts>
<MaxVisibleColumns>50000</MaxVisibleColumns>
<MaxVisiblePages>600000</MaxVisiblePages>
<MaxVisibleRows>900000</MaxVisibleRows>
<MaxVisibleSections>600000</MaxVisibleSections>
</Charts>
6. Save and close the file.
7. Perform the following OBIEE BI server configuration steps:
a. Navigate to the <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIS directory.
b. Edit the NQSConfig.INI file.
c. Update the following code within the NQSConfig.INI file
NULL_VALUES_SORT_FIRST = ON;
8. Save the file and restart the BI services.
NOTE:
Take a backup of the instance config.xml and NQSConfig.INI files before making any changes.
This section includes steps for the RPD and Catalog deployment.
For RPD deployment, follow these steps:
1. Connect to the OBIEE server.
2. Create a folder. For example, tmp in the following directory:
<Oracle_Home>/user_projects/domains/domain_name
3. Copy the CRMBI.rpd from the local directory (where you have saved the RPD) to the folder created in the preceding step.
4. Open the command prompt, and navigate to the following directory:
/scratch/<mount_name>/Middleware/Oracle_Home/user_projects/domains/bi/bitools/bin
5. Execute the following command:
./datamodel.sh uploadrpd -I <RPDfilepath> -W <RPDpassword> -SI ssi -U <username> -P <password>
For example:
./datamodel.sh uploadrpd -I /scratch/obiee12c/Middleware/Oracle_Home/user_projects/domains/bi/tmp/CRMBI.rpd -W Administrator1 -SI ssi -U weblogic -P weblogic123
For web catalog deployment, follow these steps:
1. Open the catalog manager, navigate to the File menu and open the catalog online by giving the necessary credentials based on your setup:
§ Type: Online
§ URL: http://<ipaddress>:<port>/analytics-ws
2. After the catalog is opened, it will display a directory structure on the left-hand side. Select the Catalog Root and select Shared Folders in the LHS tree structure.
a. Go to the File menu and select Unarchive. It will ask for the path for a file.
b. Browse the path of the archived catalog file saved in your local directory using the Browse button and click OK.
c. The catalog must be extracted in the Shared Folders directory for the reports to display. A successful operation message is displayed.
d. Restart the presentation services once again.
e. Open the analytics OBIEE URL (http://<ipaddress>:<port>/analytics).
f. Login with credentials based on your setup and verify that the catalog is available.
i. Click on catalog in the OBIEE application right top menu list.
ii. In the LHS menu, navigate to shared directories and verify all the directories are available.
Follow the below steps to start and stop OBIEE services:
1. Connect to the OBIEE server.
2. Navigate to the /scratch/<mount_name>/Middleware/Oracle_Home/user_projects/domains/bi/bitools/bin directory.
3. Execute the following commands:
a. Command to stop service: ./stop.sh
b. Command to start service: ./start.sh
1. For OBIEE reporting, configure the following:
a. Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIJH directory.
b. Modify the config.xml file.
c. Increase parameter value for the following tag:
<XMLP>
<InputStreamLimitInKB>40000</InputStreamLimitInKB>
<ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing>
</XMLP>
<DVT>
<InputStreamLimitInKB>40000</InputStreamLimitInKB>
</DVT>
d. Save the config.xml file.
e. Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory.
f. Modify the instanceconfig.xml file.
g. Increase the parameter value for tag if already exists or add the following code:
<Charts>
<MaxVisibleColumns>50000</MaxVisibleColumns>
<MaxVisiblePages>25000</MaxVisiblePages>
<MaxVisibleRows>100000</MaxVisibleRows>
<MaxVisibleSections>50000</MaxVisibleSections>
<JavaHostReadLimitInKB>10240</JavaHostReadLimitInKB>
</Charts>
and
<Pivot>
<MaxCells>1920000</MaxCells>
<MaxPagesToRollOutInDelivery>10000</MaxPagesToRollOutInDelivery>
<MaxVisibleColumns>50000</MaxVisibleColumns>
<MaxVisiblePages>100000</MaxVisiblePages>
<MaxVisibleRows>10000000</MaxVisibleRows>
<MaxVisibleSections>50000</MaxVisibleSections>
<DefaultRowsDisplayed>100000</DefaultRowsDisplayed>
</Pivot>
under <Views> tag
h. Save the instanceconfig.xml file.
i. Restart the BI Services.
This section includes provides information about the system administrator roles and privileges.
Topics:
There are two types of Administrators as defined by the OFS Analytical Applications Infrastructure: A User Administrator and System Administrator.
· System Administration: refers to a process of managing, configuring, and maintaining confidential data in a multi-user computing environment. A System Administrator creates functions, roles, and mapping functions to specific roles. A System Administrator also maintains segment information, holiday list, and restricted passwords to ensure security within the application. The following are the activities of a System Administrator:
§ Function Maintenance
§ Role Maintenance
§ Function-Role Mapping
· User Administration: is one of the core functions of Security Management which involves administrators to create user definitions, user groups, maintain profiles, authorize users and user groups, and map users to groups, domains, and roles. A User Administrator controls the user privileges in accessing the application and is based on business requirements to provide access to view, create, edit, or delete confidential data.
A User Administrator grants permissions based on user roles and requirements.
The respective roles must be mapped to administrative user SYSADMN.
For details, see the System Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
For details, see the System Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
For details, see the System Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
For details, see the User Group Role Map section in Oracle Financial Services Analytical Applications Infrastructure User Guide.
Create the application users in the OFSAA setup before use.
For details, see the User Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
For details, see the User Administrator section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
Starting the OFSAA 8.1.0 release, with the installation of the CRA application pack, preconfigured Application user groups are seeded. These user groups are unique to every OFSAA Application Pack and have application roles preconfigured.
For more information on seeded User Groups, see CRA Pack User Group Names.
Map the application user (or users) to the respective Application User Group (or users) and subsequently authorize the entitlements by logging in as SYSAUTH (System Authorizer) user.
For details, see the Mapping or Unmapping Users section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
The section provides information about the User Group names seeded as part of the OFS CRA application pack.
To access the CRA application, you can map the created users to the following user groups:
· CRAADMNGP - CRA Admin Group
· CRAANLYSTGP - CRA Analyst Group
· CRAAUTHGP - CRA Approver Group