On successful installation of the Oracle Financial Services IIA 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 Oracle Insurance Accounting Analyzer
· Editing the WDSL Property File
· Backup the OFS_IIA_SCHEMA_IN.xml, OFS_IIA_SCHEMA_OUTPUT.xml, and Silent.props Files
· Stop the Infrastructure Services
· Create and Deploy the EAR/WAR Files
· EAR or WAR File - Build Once and Deploy Across Multiple OFSAA Instances
· Start the Infrastructure Services
· Access the OFSAA Application
· Change the ICC Batch Ownership
· Create and Deploy the EAR or WAR Files
· Configure the excludeURLList.cfg File
· Configure Data Redaction in OFSAA
· Data Protection Implementation in OFSAA
· Post-Deployment Configurations
You can use this checklist to have a 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 |
Note This step is applicable only for deployment on the Oracle Cloud Infrastructure. |
|
3 |
Note This step is applicable only for deployment on the Oracle Cloud Infrastructure. |
|
4 |
Back up the OFS_IIA_SCHEMA_IN.xml, OFS_IIA_SCHEMA_OUTPUT.xml, and Silent.props files. |
|
5 |
Stop the OFSAA Infrastructure services. |
|
6 |
Start the OFSAA Infrastructure services. |
|
7 |
Create and deploy EAR or WAR files. |
|
8 |
Configure the browser settings for the Internet. |
|
9 |
Configure the webserver. |
|
10 |
Configure the Resource Reference in web application servers. |
|
11 |
Configure the Work Manager in the web application servers. |
|
12 |
EAR/WAR File - Build Once and Deploy Across Multiple OFSAA Instances. |
|
13 |
Access the OFSAA application. |
|
14 |
Configure excludeURLList.cfg file. |
|
15 |
Configure Tomcat. |
|
16 |
Change the ICC batch ownership. |
|
17 |
Update the OBIEE URL. |
|
18 |
Configure Data Source. |
|
19 |
Set Data Redaction in Oracle Insurance Accounting Analyzer. |
|
20 |
Implement Data Protection in OFSAA. |
|
21 |
Post-deployment Configuration. OBIEE Configuration – Deploy Oracle Insurance Accounting Analyzer Analytics. Logging as System Administrator. Create Application Users. Map the Application User (or Users) to User Groups. |
The following table includes information about the mandatory patches that must be applied:
|
One-Off Patch |
Description |
|---|---|
33663417 |
Ensure that whenever any installation or upgrade or an incremental patch is applied, the mandatory patch 33663417 for Log4J must be reapplied. For more information, see the MOS Doc ID 2827801.1. |
33995565 |
This is a mandatory AAI one-off patch. |
34058716 |
This is a mandatory AAI one-off patch. |
Oracle strongly recommends installing the latest available patch set to be up-to-date with the various releases of the OFSAA product Contact My Oracle Support for more information on the latest release.
Update the configuration set paramvalue to Y in the Config Schema:
1. Log in to the Config Schema and execute the following query:
update configuration set paramvalue='Y' where paramname='IS_CLOUD_INSTALL'; commit;
See Assign Grants for Schemas section in the OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide on how to assign grants for the schemas.
To edit the WDSL property file, follow these steps:
1. Connect to the Compute virtual machine on which the OFSAA product is installed.
2. Navigate to the $FIC_HOME/ficdb/conf/ directory.
3. Edit the subLedgerRun.properties file.
4. Change the parameter in the WDSL property file to point to the WebLogic server (any of the nodes) and the listener port that is corresponding to that node.
Backup the OFS_IIA_SCHEMA_IN.xml, OFS_IIA_SCHEMA_OUTPUT.xml, and Silent.props files as they can be reused when upgrading existing applications or installing new applications.
|
File Name |
Directory |
|---|---|
|
OFS_IIA_SCHEMA_IN.xml |
OFS_IIA_PACK/schema_creator/conf |
|
OFS_IIA_SCHEMA_OUTPUT.xml |
OFS_IIA_PACK/schema_creator/ |
|
Silent.props |
OFS_IIA_PACK/appsLibConfig/conf |
See Stop the Infrastructure Services in OFS AAI Release 8.1.2.0.0 Installation and Configuration Guide for details.
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.
See Start the Infrastructure Services in OFS AAI Installation Guide for details.
Before accessing the OFSAA application ensure the Internet Settings are configured.
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 15 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 log in 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.
NOTE:
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 16 OFSAA Landing screen
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.
This section describes the user interface components in the OFSAA Landing page.
Figure 17 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 18 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 19 Last Login Details
To launch the navigation drawer, follow these steps:
1. Click the Navigation menu to launch the Navigation Drawer as shown.
Figure 20 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 21 Navigation Drawer Menus and Submenus
3. Click Hierarchical Menu to display the navigation path of the current submenu as shown.
Figure 22 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 a one-time activity that 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 23 System Configuration Submenu
You (System Administrator) must have full access rights to the ftpshare directory with the 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
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.
The user must synchronize the Insurance Distribution Channel members that are a part of the existing Liability Calculation definitions created before Release v8.1.2.0.0 in the OIAA Application. (to be considered as hierarchical dimension members).
Before executing the SQL statement, provided in this section, the user must first create the Insurance Distribution Channel Members for the existing Members that are a part of the existing Liability Calculation definitions.
The Channel Members names/codes that were used in the application before Release v8.1.2.0.0 must be used in the Alphanumeric Code and Name Fields while creating the members in the Dimension Management Screen. For example, if a Channel Member’s name/code was 1500 in the application in Release v8.1.1.2.0. The same name/code 1500 must be used in the Alphanumeric Code and Name Fields when creating the member.
Navigate to Common Object Maintenance, select Dimension Management, and then select Member to open the Members Page. Create members for the Distribution Channel Dimension by selecting the Insurance Distribution Channel Dimension from the Dimension drop-down list. For more information on creating a Member Definition, see the Adding Member Definition Section in the Oracle Financial Services Analytical Applications Infrastructure User Guide.
After the Insurance Distribution Channel Member is created, provide the Insurance Distribution Channel hierarchy name as a user input as the prompt while executing the following SQL statement in the Atomic Schema
INSERT INTO FSI_M_IIA_AGGR_DIMENSION_DTLS (LEVEL_OF_AGGR_ID, DIMENSION_ID, HIERARCHY_ID, DIM_MEMBER_ID)
SELECT DIM_MAP.LEVEL_OF_AGGR_ID, DIM_MAP.DIMENSION_ID, DIM_MAP.HIERARCHY_ID, DIM_MAP.DIM_MEMBER_ID
FROM ( SELECT DISTINCT DM.LEVEL_OF_AGGR_ID
,(SELECT max(DIMENSION_ID) FROM REV_DIMENSIONS_B WHERE MEMBER_B_TABLE_NAME = 'DIM_CHANNEL_B' ) DIMENSION_ID
,(select max(tl.object_definition_id) from fsi_m_object_definition_tl tl
where upper(trim(tl.short_desc))=upper(to_char(trim('&Distribution_Channel_Hierarachy_Name')))
) HIERARCHY_ID
, DCBT.CHANNEL_ID DIM_MEMBER_ID
FROM FSI_IIA_AGGR_NON_HIER_DIM_MAP DM
INNER JOIN DIM_CHANNEL DC ON ( DC.N_CHANNEL_SKEY = DM.DIM_CD AND DM.DYNA_NAME = 'CHAN' )
INNER JOIN DIM_CHANNEL_B DCBT ON ( DCBT.CHANNEL_CODE = DC.V_CHANNEL_CODE )
) DIM_MAP
WHERE NOT EXISTS (SELECT IAD.LEVEL_OF_AGGR_ID FROM FSI_M_IIA_AGGR_DIMENSION_DTLS IAD
WHERE IAD.LEVEL_OF_AGGR_ID = DIM_MAP.LEVEL_OF_AGGR_ID
AND IAD.DIMENSION_ID = DIM_MAP.DIMENSION_ID
AND IAD.DIM_MEMBER_ID = DIM_MAP.DIM_MEMBER_ID
)
/
COMMIT
/
When prompted for the Distribution_Channel_Hierarachy_Name value, enter the name of the Insurance Distribution Channel Hierarchy.
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 Oracle Insurance Accounting Analyzer 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:
· from user 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.
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_IIA_ANALYTICS')
/
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 webserver 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 web.xml 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>
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 Configure the excludeURLList.cfg File in OFS AAI Installation Guide for details.
This section details the configurations required in case you want to enable Data Redaction in the OFSAA applications.
Topics:
· Enable Data Redaction in case of an Upgrade
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 topic in the OFS Analytical Applications Infrastructure Administration and Configuration Guide.
This section details the configurations required in case you want to enable Data Redaction in OFSAA applications after upgrade to OFSAA 8.1.2.0.0 version from a previous version Additionally, these configurations are required in case you did not enable TDE during Oracle Insurance Accounting Analyzer 8.1.2.0.0 installation and want to enable it at a later point in time.
Perform the following steps:
1. From the Configuration window in the System Configuration module, select the Allow Data Redaction checkbox.
2. Run the Data Redaction utility.
For more details on enabling Data Redaction, see the Data Redaction section in the Data Security and Data Privacy topic in the OFS Analytical Applications Infrastructure Administration 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 of Data Controller to the IIA 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 IIA Data Controller user ID from Step 1.
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 Oracle Insurance Accounting Analyzer Analytics
· Logging as System Administrator
· Mapping Application User (or Users) to User Group
The Oracle Insurance Accounting Analyzer Analytics application release 8.1.2.0.0 is based upon a dedicated reporting mart built from the new Fusion Financial Services Data Model Oracle Insurance Accounting Analyzer 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 It also includes various Dashboards and Reports for the user to carry out various Insurance Accounting Analyzer-based analytics.
Follow these steps to configure the Oracle Insurance Accounting Analyzer 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 24 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 (as per the license agreement) in the server where the BI client tools are installed:
— $FIC_HOME /OFS_IIA_DASHBOARDS/12.2.1.4.0/directory containing the IFRS17.rpd in the data model folder and archived.
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 IFRS17.rpd file.
d. In the Open dialog box, select and open the IFRS17.rpd file.
e. Enter the Repository password as Admin123.
f. In the Physical layer, double-click the Connect Pool IIABI 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 IIABITRANS and IIABI_ INIT_BLOCK and IIABI.
— 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 Oracle Insurance Accounting Analyzer Analytics application using the
URL http:// <ipaddress>:<port>/analytics (replace the port number based on your setup).
5. Follow these steps to configure the BI publisher Data Source:
a. Log in to the Oracle Insurance Accounting Analyzer Analytics application.
b. Navigate to Administration, select BI Publisher, and then select Manage BI Publisher.
c. Click JDBC Connection from Data Sources.
d. Click Add Data Source.
e. Enter the Data Source name as IIA.
f. Add Database details in the Connection string, that is the hostname (IP address), port number, and SID.
g. Enter the username (schema name) and password.
h. Click Test Connection.
i. Ensure that the connection is successfully established Click Apply.
6. Perform the following configuration for sub-ledger reports:
For OBIEE:
a. Navigate to the Oracle_Home/user_projects/domains/bi/config/fmwconfig/biconfig/OBIS directory.
b. Edit the value in EVALUATE_SUPPORT_LEVEL to 2 EVALUATE_SUPPORT_LEVEL = 2; IN NQSCONFIG.INI file.
c. Save the file and restart the BI services.
For OAS:
d. Navigate to the OAS reports URL and add /dv at the end of the URL For example http:// <ipaddress>:<port>/dv (replace the port number based on your setup)
e. Log in and click Console, then click System Settings and navigate to Evaluate Support Level.
f. Set the evaluate support level from 0 to 2.
g. Click Restart.
h. Restart the OBI services.
i. After completing the preceding steps, the second report under Subledger appears without errors.
7. 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>.
<Table>
<DefaultRowsDisplayedInDelivery>75</DefaultRowsDisplayedInDelivery>
<DefaultRowsDisplayedInDownload>6500</DefaultRowsDisplayedInDownload>
<MaxCells>4000000</MaxCells>
<MaxVisibleRows>140000</MaxVisibleRows>
</Table>
<Narrative>
<MaxRecords>500000</MaxRecords>
<DefaultRowsDisplayed>25</DefaultRowsDisplayed>
</Narrative>
e. Save the file and restart the BI services.
NOTE:
Take a backup of the instanceconfig.xml file 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 IFRS17.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/IFRS17.rpd -W Admin123 -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.
iii. Navigate to Administration, then Maintenance and Troubleshooting, select Reload Files, and then click MetaData.
NOTE:
If you need to clear the cache in OAS, click Issue SQL and run the Call SAPurgeAllcache() method.
Follow the below steps to configure the OBI Administrator tool to point to the database schema:
1. Open the Administrator tool and navigate to File, select Open, and then select Online/Offline.
a. If you are online, the Presentation, Business Model and Mapping, and Physical panes appear.
b. If you are offline, then select the IFRS17.rpd file and provide the RPD password.
2. In the Physical pane, right-click Insurance Connection Pool, then Insurance Connection Pool Init Blocks, and then click Properties.
3. Click Yes.
4. Open the Atomic Schema and enter details as provided in the below example:
Dsn : (DESCRIPTION =(ADDRESS = (PROTOCOL = TCP)(HOST = 10.40.136.96)(PORT = 1521))(CONNECT_DATA =(SERVER = DEDICATED)(SERVICE_NAME = IFRS18PDB)))
username: atm8081
password: password1
5. If you are online, click Check In Changes If you are offline, navigate to File, then select Save as, then select Repository and then select the IFRS17.rpd file.
After you complete the above steps, you must reload the files and metadata as detailed in step f in the Deploying the Web Catalog section.
Follow the below steps to start and stop OBIEE services:
1. Connect to the OBIEE or OAS 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
To edit the global variables for OBIEE, in this release of the Oracle Insurance Accounting Analyzer application, follow these steps:
1. Host the RPD in the server where you have configured OBIEE or OAS and Catalog for the Oracle Insurance Accounting Analyzer application as part of this release.
2. Log in to OBIEE or OAS by using the URL format (http://<ipaddress>:<port>/analytics) to open the home page.
Figure 25 The Analytics Home Page
3. In the Dashboard drop-down list, click Disclosure Reports to open the dashboard.
4. Click Edit on any of the reports to open the settings window.
5. In the Criteria tab, in the Selected Columns pane, click Onerous Classification Code.
6. Click Settings to open the settings submenu.
Figure 26 The Settings icon adjacent to Onerous Classification Code
7. Click the Edit formula to open the Edit Column Formula window.
Figure 27 The Edit Column Formula
8. In the Variables drop-down list, select Global… to open the Insert Global Variable window.
9. Select the Global Variable that you want to edit, and then click Edit Global Variable.
10. Edit a global variable with the following details:
|
Field |
Value to be added |
|---|---|
|
Name |
denomination |
|
Type |
Text |
|
Value |
case when '@ { denomination}{In: Thousand; } ' = 'In Thousand' then 1000 when '@ { denomination}{In: Thousand; } ' = 'In Million' then 1000000 else 1 end |
This variable is used to divide all amount values by thousand or million, depending on the selected criteria.
11. Click OK, and then click OK again to save.
This section includes provides information about the system administrator roles and privileges.
Topics:
· Role of an Administrator
· Role Maintenance
There are two types of Administrators as defined by the OFS Analytical Applications Infrastructure A User Administrator and a 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 creating 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.0.0 release, with the installation of the IIA 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 IIA 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 Oracle Insurance Accounting Analyzer application pack.
To access the IIA application, you can map the created users to the following user groups:
· IIAADMINGRP - IIA Admin Group
· IIAANALYSTGRP - IIA Analyst Group
· IIAAPPROVERGRP - IIA Approver Group
If you want to use the Oracle Insurance Loss Modeller (OILM) application, then you must run the following query after initializing IAA in the UI:
update rev_dimensions_B
set MEMBER_CODE_COLUMN='COUNTRY_CODE',
HIERARCHY_TABLE_NAME='DIM_COUNTRY_HIER',
ATTRIBUTE_TABLE_NAME='DIM_COUNTRY_ATTR' where DIMENSION_ID IN (select DIMENSION_ID from rev_dimensions_tl
where
DIMENSION_NAME='Country')
/