7                                  Post-installation

On successful installation of the Oracle Financial Services LLFP 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:

·        Post-installation Checklist

·        Mandatory Patches

·        Patch Oracle Financial Services Loan Loss Forecasting and Provisioning

·        Backup the OFS_LLFP_SCHEMA_IN.xml, OFS_LLFP_SCHEMA_OUTPUT.xml, and Silent.props Files

·        Stop the Infrastructure Services 

·        Create and Deploy the EAR/WAR Files 

·        Build EAR or WAR file once and Deploy Across Multiple OFSAA Instances

·         Start the Infrastructure Services

·        Setting Up Setup the Master Table

·        Access the OFSAA Application

·        OFSAA Landing Page 

·        Configure Tomcat 

·        Add TNS entries in the TNSNAMES.ORA File

·          Configure Data Source

·         Configure the excludeURLList.cfg File 

·        Data Protection Implementation in OFSAA 

·        Users and Roles 

·        Configuring the Sandbox 

·        Configuring OBIEE for Loan Loss Forecasting and Provisioning 

7.1                            Post-Installation Checklist

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.1.0.0 Installation and Configuration Guide to complete the following checklist procedures.

7.2                           Mandatory Patches

The following table includes information about the mandatory patches that must be applied if OFS LLFP is the first pack to be installed.

7.3                           Patch Oracle Financial Services Loan Loss Forecasting and Provisioning

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 the Mandatory Patches section.

Contact My Oracle Support for more information on the latest release.

7.4                          Backup the OFS_LLFP_SCHEMA_IN.xml, OFS_LLFP_SCHEMA_OUTPUT.xml, and Silent.props Files

Backup the OFS_LLFP_SCHEMA_IN.xml, OFS_LLFP_SCHEMA_OUTPUT.xml, and Silent.props files as they can be reused when upgrading existing applications or installing new applications.

7.5 Update the Component Value

After installing the OFS LLFP application, the component value must be updated for data to flow into the dim_gl_account table.

If the component value in the setup_master table that corresponds to the v_component_code for GL_ACCOUNT_HIER is Default, then modify this value to the correct general ledger hierarchy ID that is used in the subledger definition.

NOTE:   

If the correct general ledger hierarchy ID is already present in the setup_master table that corresponds to the component code for GL_ACCOUNT_HIER, then there is no need to update the value.

The following is a sample query that can be used update the value:

Before executing this query, replace the text <GL Hierarchy Name>  with the correct General ledger hierarchy name that is used or will be used in a subledger definition.

update setup_master

set v_component_value = (select object_definition_id

    from fsi_m_object_definition_tl

    where short_desc = '<GL Hierarchy Name>' )

where upper(v_component_code)='GL_ACCOUNT_HIER'

and upper(v_component_value) = 'DEFAULT' ;

commit;

After committing the above update, execute the batch <Infodom>_DIMENSION_DATA_POPULATION. This ensures that the general ledger hierarchy structure is used in the dim_gl_account reporting table.

7.6                        Stop the Infrastructure Services

See Stop the Infrastructure Services in the OFS AAI Release 8.1.1.0.0 Installation and Configuration Guide for details.

7.7                          Create and Deploy the EAR or WAR Files

See Create and Deploy the EAR or WAR Files in the OFS AAI Release 8.1.1.0.0 Installation and Configuration Guide for details.

7.8                          EAR or WAR File - Build Once and Deploy Across Multiple OFSAA Instances

See EAR or WAR File - Build Once and Deploy Across Multiple OFSAA Instances in the OFS AAI Release 8.1.1.0.0 Installation and Configuration Guide for details.

7.9                          Start the Infrastructure Services

See Start the Infrastructure Services in the OFS Analytical Applications Infrastructure Installation Guide for details.

7.10                          Setting Up Setup the Master Table

The following table provides details on setting up the SETUP_MASTER table.

7.10                     Access the OFSAA Application

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 9: 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.

 OFSAA Landing Page

ATTENTION:   

The password change is required only for a new installation scenario and not for upgrade scenarios.

7.10.1            OFSAA Landing Page

On successful login, the OFSAA Landing screen is displayed.

Figure 10: 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. For more information on the components of OFS Analytical Applications, refer to the OFS Analytical Applications Infrastructure (OFS AAI) Application Pack Installation and Configuration Guide.

View OFSAA Product Licenses after Installation of Application Pack

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.1.0.0.

7.11                       Configure Tomcat

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>

7.12                      Add TNS entries in the TNSNAMES.ORA File

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'

7.13                      Configure Data Source

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 Analytical Applications Infrastructure Release 8.1.1.0.0 Installation and Configuration Guide.

·        Create and deploy the web components into the webserver. For more information on deploying the web components, see the OFS Analytical Applications Infrastructure Release 8.1.1.0.0 Installation and Configuration Guide.

7.14                     Configure the excludeURLList.cfg File

See Configure the excludeURLList.cfg File in the OFS Analytical Applications Infrastructure Installation Guide for details.

7.15                      Data Protection Implementation in OFSAA

See OFSDF Data Protection Implementation Guide for details.

7.16                     Users and Roles

The section provides information about the User Group names that are part of the Oracle Financial Services Loan Loss Forecasting and Provisioning application pack.

To access the OFS Loan Loss Forecasting and Provisioning application, you can map the created users to the following user groups:

·        LLFPADMINGRP - LLFP Admin Group

·        LLFPANALYSTGRP - LLFP Analyst Group

7.17                      Configuring the Sandbox

This section provides information on configuring the sandbox. These steps are optional and are only applicable if you want to use the sandbox feature.

Configuring the Sandbox after a Fresh Installation

Configuring the Sandbox if it is not Present after a Fresh Installation

Configuring the Sandbox after you Upgrade to Release 8.1.1.0

7.17.1             Configuring the Sandbox after a Fresh Installation

This section provides information on configuring the sandbox if it is already present after the fresh installation.

This configuration is required only if you have a license for OFSAAI Enterprise Modelling.

Once you license OFS Advanced Analytical Applications Infrastructure, the following configurations must be made to use the Modelling features. These steps are required to verify and execute the models that are packaged with the OFS LLFP application.

NOTE:   

Ensure that Oracle R Enterprise Server version 1.5.1 is installed on the database server and AAAI Runner Package is installed on the DB server before you perform these configurations. Also, you must access the application with the required privileges.

1.     Grant the RQADMIN role to the config schema user by executing the following query in the config schema: 

2.      grant RQADMIN to <<config_schema>>; grant RQADMIN to <<atomic_schema>>; grant RQADMIN to <<pdmodel_schema>>; 

3.     If Data Redaction is enabled, execute the following query:

4.     alter user <<pdmodel_schema>> default role RQADMIN; grant OFS_SEC_DATA to <<schema_user>>;

5.     grant OFS_NOSEC_DATA to <<schema_user>>; 

6.     Log in as a System Administrator.

7.     Navigate to Identity Management, then Security Management, then User Administrator, and then User Group Domain Map.

8.     Map the newly created sandbox information domain to the LLFP Admin Group. For more information about mapping a domain to a specific user group, see the User Group Domain Map section in the OFS Analytical Applications Infrastructure User Guide.

9.     Map the LLFP Admin User to EMF Group. For more information about mapping a user to a specific user group, see the User Group Role Map section in the OFS Analytical Applications Infrastructure User Guide.

7.17.2            Configuring the Sandbox if it is not Present after a Fresh Installation

This section details the steps that you must perform to configure the sandbox for the OFS LLFP application if it is not present after the fresh installation.

7.17.2.1               Prerequisites

This configuration is required only if you have a license for OFSAAI Enterprise Modelling.

Once you license OFS Advanced Analytical Applications Infrastructure, the following configurations must be made to use the Modelling features. These steps are required to verify and execute the models that are packaged with the LLFP application.

NOTE:   

Ensure that Oracle R Enterprise Server version 1.5.1 is installed on the database server and AAAI Runner Package is installed on the DB server before you perform these configurations. Also, you must access the application with the required privileges.

1.     Grant the RQADMIN role to the config schema user by executing the following query in the config schema: 

2.      grant RQADMIN to <<config_schema>>; grant RQADMIN to <<atomic_schema>>; grant RQADMIN to <<pdmodel_schema>>; 

3.     If Data Redaction is enabled, execute the following query:

4.     alter user <<pdmodel_schema>> default role RQADMIN; grant OFS_SEC_DATA to <<schema_user>>;

5.     grant OFS_NOSEC_DATA to <<schema_user>>; 

6.     Log in to the application as a System Administrator.

7.     Navigate to System Configuration, then Configure Database Server, and then click Configure Database Server.

8.     Add a new database server. For more information about adding a new database server, see the Adding Database Server Details section in the OFS Analytical Applications Infrastructure User Guide.

9.     Navigate to the System Configuration & Identity Management tab.

10.  Click Administration and Configuration, select System Configuration, and click Database Details.

11.  Make a TNS entry for the newly created database. For more information, see the Adding Database Details section in the OFS Analytical Applications Infrastructure User Guide.

12.  Navigate to Identity Management, then Security Management, then User Administrator, and then User Group Domain Map.

13.  Map the newly created sandbox information domain to the LLFP Admin Group. For more information about mapping a domain to a specific user group, see the User Group Domain Map section in the OFS Analytical Applications Infrastructure User Guide.

14.  Map the LLFP Admin User to the EMF Group. For more information about mapping a user to a specific user group, see the User Group Role Map section in the OFS Analytical Applications Infrastructure User Guide.

7.17.2.2              Configurations for Verifying and Executing PD Model

Perform the following configurations to verify and execute the PD Model.

15.  Log in to the application as an LLFP admin user.

16.  By usingthe IFRS ECL Consolidated dataset, create asandbox. For more information on how to create a sandbox, see the Sandbox section in the OFS Enterprise Modelling User Guide.

7.17.2.2.1              Configuring the Sandbox after installing patch 32448421

After installing patch 32448421 and creating a new sandbox, perform the following steps to configure the new sandbox to reflect the dataset changes:

1.     Map the models to the new sandbox in the atomic schema.

2.     Log in to the OFS LLFP application and click the Sandbox/icon to open the Sandbox landing page.

Figure 11: The Sandbox Page

3.     Click the newly created sandbox and navigate to Modeling, then click Model Creation to open the Model Management page.

Figure 12: The Model Management Page

4.     Select the required model and click the Copy  icon. A new model ID is generated via the Model Definition window and it is saved under a new name, for example, IFRS9_PD_Projection.

Figure 13: The Model Definition Window

5.     Click Save and then click Execute. The copy of the model is saved and executed.

7.17.2.3              Configurations for Verifying and Executing Survival Model

Perform the following configurations to verify and execute the Survival Model.

1.     Log in to the application as an LLFP admin user.

2.     Create a sandbox by using the following datasets:

§       Survival Model Input Dataset

§       Survival Model Output Dataset

§       Survival Rate Model Dataset

§       Survival Model UI Data Dataset

For more information on how to create a sandbox, see the Sandbox section in the OFS Enterprise Modelling User Guide.

3.     Navigate to the $FIC_HOME/InstallerScripts/OFS_LLFP folder.

4.     Unzip the scripts_81000.tar.gz file. In this file, a sandbox/create folder is present.

5.      In the sandbox/create a folder, execute the VW_SURVIVAL_MODEL.sql and vw_survival_model_derived_entity.sql files.  

7.17.2.4             Configurations for Verifying and Executing Vintage Model

Perform the following configurations to verify and execute the Vintage Model.

1.     Log in to the application as an LLFP admin user.

2.     Create a sandbox by using the following datasets:

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Historic Dataset

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Prediction Dataset

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Average Loss Rate

For more information on how to create a sandbox, see the Sandbox section in the OFS Enterprise Modelling User Guide. 

7.17.2.5              Replacing the placeholders

After you complete the configurations for each model, you must replace the placeholder sandbox ID in the config schema:

1.     In the config schema, replace the place holder ##LLFPSANDBOX_ID## with the sandbox ID in the following tables:

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_MASTER

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_SCRIPT_MASTER

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_DS_QUERY

7.17.2.6             Sandbox Execution and deployment

After you complete these configurations, you must follow the instructions in the Oracle Financial Services Analytical Applications Installation and Configuration Guide to view, execute, and deploy the model from the sandbox.

7.17.3            Configuring the Sandbox after you Upgrade to Release 8.1.1.0.0

This section details the steps that you must perform if you want to configure the sandbox for the OFS LLFP application after you upgrade to Release 8.1.1.0.0.

7.17.3.1               Prerequisites

This configuration procedure is required only if you have a license for OFSAAI Enterprise Modelling.

Once you license OFS Advanced Analytical Applications Infrastructure, the following configurations must be made to use the Modelling features. These steps are required to verify and execute the models that are packaged with the OFS LLFP application.

NOTE:   

Ensure that Oracle R Enterprise Server version 1.5.1 is installed on the database server and AAAI Runner Package is installed on the DB server before you perform these configurations. Also, you must access the application with the required privileges.

1.     In the config schema, create a new schema with the following grants:

2.     grant create SESSION to <<schema_user>>; grant create PROCEDURE to <<schema_user>>; grant create SEQUENCE to <<schema_user>>; grant create TABLE to <<schema_user>>; grant create TRIGGER to <<schema_user>>; grant create VIEW to <<schema_user>>;

grant create MATERIALIZED VIEW to <<schema_user>>;

grant create SYNONYM to <<schema_user>>;

grant unlimited TABLESPACE to <<schema_user>>;

3.     Grant the RQADMIN role to the config schema user by executing the following query: 

4.      grant RQADMIN to <<config_schema>>; grant RQADMIN to <<atomic_schema>>; grant RQADMIN to <<pdmodel_schema>>; 

5.     If Data Redaction is enabled, execute the following query:

6.     alter user <<pdmodel_schema>> default role RQADMIN; grant OFS_SEC_DATA to <<schema_user>>;

7.     grant OFS_NOSEC_DATA to <<schema_user>>; 

8.     Log in to the application using System Administrator privileges.

9.     Navigate to System Configuration, then Configure Database Server, and then click Configure Database Server.

10.  Add a new database server. For more information about adding a new database server, see the Adding Database Server Details section in the OFS Analytical Applications Infrastructure User Guide.

11.  Navigate to System Configuration & Identity Management tab.

12.  Click Administration and Configuration, select System Configuration, and click Database Details.

13.  Make a TNS entry for the newly created database. For more information, see the Adding Database Details section in the OFS Analytical Applications Infrastructure User Guide.

14.  Create a new information domain for the sandbox and create a new segment. For more information, see the Creating Information Domain and Creating Segment sections in the OFS Analytical Applications Infrastructure User Guide.

15.  Navigate to Identity Management, then Security Management, then User Administrator, and then User Group Domain Map.

16.  Map the newly created sandbox information domain to the LLFP Admin Group. For more information about mapping a domain to a specific user group, see the User Group Domain Map section in the OFS Analytical Applications Infrastructure User Guide.

17.  Map the LLFP Admin User to the EMF Group. For more information about mapping a user to a specific user group, see the User Group Role Map section in the OFS Analytical Applications Infrastructure User Guide.

7.17.3.2              Configurations for Verifying and Executing PD Model

Perform the following configurations to verify and execute the PD Model.

1.     Log in to the application as an LLFP admin user.

2.     By usingthe IFRS ECL Consolidated dataset, create asandbox. For more information on how to create a sandbox, see the Sandbox section in the OFS Enterprise Modelling User Guide.

7.17.3.3              Configurations for Verifying and Executing Survival Model

Perform the following configurations to verify and execute the Survival Model.

1.     Log in to the application as an LLFP admin user.

2.     Create a sandbox by using the following datasets:

§       Ǽspan style="font: 7.0pt 'Times New Roman';">  Survival Model Input Dataset

§       Ǽspan style="font: 7.0pt 'Times New Roman';">  Survival Model Output Dataset

§       Ǽspan style="font: 7.0pt 'Times New Roman';">  Survival Rate Model Dataset

§       Ǽspan style="font: 7.0pt 'Times New Roman';">  Survival Model UI Data Dataset

3.     Navigate to the $FIC_HOME/scripts_OFS_ IFRS/atomic/create folder.

4.     Execute theVW_SURVIVAL_MODEL.sql and vw_survival_model_derived_entity.sql files.

7.17.3.4             Configurations for Verifying and Executing Vintage Model

Perform the following configurations to verify and execute the Vintage Model.

1.     Log in to the application as an LLFP admin user.

2.     Create a sandbox by using the following datasets:

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Historic Dataset

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Prediction Dataset

ռspan style="font: 7.0pt 'Times New Roman';">          IFRS - Vintage Model Average Loss Rate

7.17.3.5             Replacing the placeholders

After you complete the configurations for each model, you must replace the placeholder sandbox ID in the config schema:

1.     In the config schema, you must replace the place holder ##LLFPSANDBOX_ID## with the sandbox ID in the following tables:

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_MASTER

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_SCRIPT_MASTER

ռspan style="font: 7.0pt 'Times New Roman';">          MF_MODEL_DS_QUERY

7.17.4                 Sandbox Execution and deployment

After you complete the above configurations, you must follow the instructions in the Oracle Financial Services Analytical Applications Installation and Configuration Guide to view, execute, and deploy the model from the sandbox.

7.18                     Configuring OBIEE for Loan Loss Forecasting and Provisioning BI Analytics

The Oracle Financial Services Loan Loss Forecasting and Provisioning Analytics application release 8.1.1.0.0 is based upon a dedicated reporting mart built from the new Fusion Financial Services Data Model. Oracle Financial Services Loan Loss Forecasting and Provisioning Analytics 8.1.1.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 Loan Loss Forecasting and Provisioning Gap based analytics.

OBIEE Server Configuration for Upgrade

Deploying the RPD

Deploying the Web Catalog

Starting and Stopping Services in OBIEE

Update the OBIEE URL

Editing Global Variables for OBIEE or OAS

Follow these steps to configure the Oracle Financial Services Loan Loss Forecasting and Provisioning 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 14: 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:

—    ޼span style="font: 7.0pt 'Times New Roman';">        $FIC_HOME/LLFP_DASHBOARDS/LLFP.rpd in the data model folder and archived.

h.     Click Finish.

3.     Modify the connection pool and set the properties.

4.     Open the OBI Administration tool.

a.     Select Start, select Programs, select Oracle Business Intelligence and then select BI Administration.

b.     Select File, select Open, select Offline, and then select the LLFP.rpd file.

c.     In the Open dialog box, select and open the LLFP.rpd file.

d.     Enter the Repository password as Administrator1.

e.     In the Physical layer, double-click the Connect Pool: LLFPBI to open its properties.

f.       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 LLFPBITRANS and LLFPBI_ INIT_BLOCK, and LLFPBI.

—    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.

g.     Click Yes for the Global Consistency Message. No warnings should be generated at this stage.

h.     Close the RPD file (close the file and exit).

5.     Log in to the Oracle Financial Services Loan Loss Forecasting and Provisioning Analytics application using the

URL: http:// <ipaddress>:<port>/analytics (replace the port number based on your setup).

6.     Follow these steps to configure the BI publisher Data Source:

a.     Log in to the Oracle Financial Services Loan Loss Forecasting and Provisioning 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 LLFP.

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.

7.     Follow these steps to implement the Writeback feature:

a.     Add the tag <LightWriteback>true</LightWriteback> in between <ServerInstance></ServerInstance> in the instanceconfig.xml file.

For example:

<ServerInstance>

<LightWriteback>true</LightWriteback>

ŅŅŅŅ.

ŅŅŅŅż/span>

</ServerInstance>

b.     Copy the writeback.xml file available in the $FIC_HOME/OFS_LLFP_DASHBOARDS/12.2.1.4.0/content/msgdb/ directory to the following OBIEE server directories. If the customMessages directory is not present, create the directory manually.

Path1: <BI Domain Home>/bidata/components/OBIPS/custommessages

For example: /scratch/oraobiee/Oracle/Middleware/Oracle_Home/user_projects/domains/bi/bidata/components/OBIPS/custommessages

Path2: <BI Domain Home>/bidata/service_instances/ssi/metadata/content/msgdb/l_en/customMessages

For example:

/scratch/oraobiee/Oracle/Middleware/Oracle_Home/user_projects/domains/bi/bidata/service_instances/ssi/metadata/content/msgdb/l_en/customMessages

c.     Restart the BI Services.

d.     Login to OBIEE Analytics and navigate to the Administration section on the right top corner.

e.     Click Manage Privileges and scroll down to Writeback.

f.       Grant Writeback to Database privilege to Authenticated User and BI Administrator roles.

8.     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.

7.18.1            OBIEE Server Configuration for Upgrade

Perform the following OBIEE server configuration steps. You can ignore the steps if OBIEE is already configured in your setup.

1.     Execute the following steps to implement the Writeback feature:

a.     Add the tag <LightWriteback>true</LightWriteback> in between <ServerInstance></ServerInstance> in the instanceconfig.xml file.

For example:

<ServerInstance>

<LightWriteback>true</LightWriteback>

ŅŅŅŅ..

ŅŅŅŅż/span>

</ServerInstance>

b.     Copy the writeback.xml file available in the $FIC_HOME/OFS_LLFP_DASHBOARDS/12.2.1.4.0/content/msgdb/ directory to the following OBIEE server directories. If customMessages directory is not present, create the directory manually.

Path1: <BI Domain Home>/bidata/components/OBIPS/custommessages

For example: /scratch/oraobiee/Oracle/Middleware/Oracle_Home/user_projects/domains/bi/bidata/components/OBIPS/custommessages

Path2: <BI Domain Home>/bidata/service_instances/ssi/metadata/content/msgdb/l_en/customMessages

For example:

/scratch/oraobiee/Oracle/Middleware/Oracle_Home/user_projects/domains/bi/bidata/service_instances/ssi/metadata/content/msgdb/l_en/customMessages

c.     Restart BI Services.

d.     Login to OBIEE Analytics and navigate to Administration section on the right top corner.

e.     Click Manage Privileges and scroll down to Writeback.

f.       Grant Writeback to Database privilege to Authenticated User and BI Administrator roles.

2.     Perform the following OBIEE presentation server configuration steps:

a.     Navigate to the <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory.

b.     Edit the file instanceconfig.xml.

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.

3.     Perform the following RPD changes, to set the Early Warning Indicators 1 and 2:

a.     Open the Repository in Online or Offline mode.

b.     Select Manage and then select Variables.

c.     Navigate to hierarchy Repository, select Variables, and then select Static.

d.     Modify EARLYWARNIND1 and EARLYWARNIND2 variable values as required.

e.     Save and commit the changes to RPD.

NOTE: You must redeploy the RPD on the BI server if you have made changes in the offline mode.

4.     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 a 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.

7.18.2           Deploying the RPD

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 LLFP.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/L LLFP.rpd -W Administrator1 -SI ssi -U weblogic -P weblogic123

7.18.3           Deploying the Web Catalog

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.

7.18.4          Starting and Stopping Services in OBIEE

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

7.18.5           Update the OBIEE URL

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_LLFP_BI')

/

COMMIT

/

7.18.6           Editing Global Variables for OBIEE or OAS

To edit the global variables for OBIEE, in this release of the Oracle Financial Services Loan Loss Forecasting and Provisioning application, follow these steps:

1.     Host the RPD in the server where you have configured OBIEE or OAS and Catalog for the Oracle Financial Services Loan Loss Forecasting and Provisioning 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 15: The Analytics Home Page

3.     In the Dashboards drop-down list, click CECL 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 Criteria (ԉFRS 9ԩ.

6.     Click Settings . 

7.     Click the Edit formula to open the Edit Column Formula window.

8.     In the Variables drop-down list, select Globalż/b> 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:

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.

Part II

Topics:

·        Upgrade