8.21.1.1 RPD and Catalog Deployment

This section includes steps for the RPD and Catalog deployment.

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 Liquidity_Risk_Management_Pack.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/b itools/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/Liquidity_Risk_Management_Pack.rpd -W Administrator1 -SI ssi -U weblogic -P weblogic123

    Figure 8-9 RPD deployment command


    Description of the RPD Deployment follows This illustration shows the command you must execute for RPD deployment.

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.
    1. Go to the File menu and select Unarchive . It will ask for the path for a file.
    2. Browse the path of the archived catalog file saved in your local directory using the Browse button and click OK.
    3. The catalog must be extracted in the Shared Folders directory for the reports to display. A successful operation message is displayed.

      Note:

      In OAS, the following error occurs in the Catalog Manager after unarchiving Liquidity_Risk_Management_pack.catalog file.

      Figure 8-10 Error in OAS Catalog Manager


      Description of the OAS Catalog Manager error follows This illustration shows the error which occurs in the Catalog Manager after unarchiving Liquidity_Risk_Management_pack.catalog.

    4. To retrieve the catalog folders, follow these steps:
      1. Click on the Refresh icon to view the unarchived catalog folders.

        Figure 8-11 Refresh to View the Unarchived Catalog Folders


        Description of Refresh to View the Unarchived Catalog Folders follows This illustration shows how you need to refresh the folder to view the unarchived Catalog folders.

      2. The unarchived catalog folders are displayed.

        Figure 8-12 Unarchived Catalog Folders Displayed after Refresh


        Description of Unarchived Catalog Folders Displayed after Refresh follows This illustration shows the unarchived Catalog folders being displayed after refresh.

    5. Restart the presentation services once again.
    6. Open the analytics OBIEE URL (http://<ipaddress>:<port>/analytics).
    7. Login with credentials based on your setup, and verify that the catalog is available.
      1. Click on catalog in the OBIEE application right top menu list.
      2. In the LHS menu, navigate to shared directories and verify all the directories are available.

Starting and Stopping Services in OBIEE

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/b itools/bin directory.

  3. Execute the following commands:
    1. Command to stop service: ./stop.sh
    2. Command to start service: ./start.sh

OBIEE Configurations Post-Deployment of RPD and Catalog Files

For Post-deployment of RPD and Catalog files, follow these steps:

  1. For Intraday RBI reporting template, ensure that you update the following SQL query in the setup master table:
    1. Name of the Bank

      UPDATE SETUP_MASTER SET V_COMPONENT_VALUE = '<<Bank Name>>' WHERE V_COMPONENT_CODE = 'INTRA_DAY_BANK';

    2. Whether the Bank provides Correspondent banking services (Y/N)

      UPDATE SETUP_MASTER SET V_COMPONENT_VALUE = '<<Y or N>>' WHERE V_COMPONENT_CODE = 'PROVIDE_CORRESPONDENT_BANKING_SERVICES';

  2. Perform the following RPD changes, to set the Early Warning Indicators 1 and 2:
    1. Open the Repository in Online or Offline mode.
    2. Select Manage and then select Variables .
    3. Navigate to hierarchy Repository , select Variables , and then select Static .
    4. Modify EARLYWARNIND1 and EARLYWARNIND2 variable values as required.
    5. Save and commit the changes to RPD.

      Note:

      You must redeploy the RPD on BI server if you have made changes in the offline mode.
  3. For OBIEE reporting, configure the following:
    1. Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIJH directory.
    2. Modify the config.xml file.
    3. Increase parameter value for the following tag:
      <XMLP>
      <InputStreamLimitInKB>40000</InputStreamLimitInKB>
      <ReadRequestBeforeProcessing>true</ReadRequestBeforeProcessing>
      </XMLP>
      <DVT>
      <InputStreamLimitInKB>40000</InputStreamLimitInKB>
      </DVT>
    4. Save the config.xml file.
    5. Navigate to the <<obiee <<Oracle BI Instance Home>/config/fmwconfig/biconfig/OBIPS directory.
    6. Modify the instanceconfig.xml file.
    7. 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
    8. Save the instanceconfig.xml file.
    9. Restart the BI Services.
  4. To configure the real-time intraday reporting, Auto Refresh Dashboard Interval to perform the following steps:
    1. Log in to the respective server where LRM analytics is deployed.
    2. After successful login, select Liquidity Risk , and then select Intraday Real Time Monitoring .
    3. Select Edit Dashboard from Page options in Intraday Real Time Monitoring Dashboard .
    4. In the Intraday Real Time Auto Dashboard Refresh section from the Edit Dashboard page, select Properties from the text object (which is to the top right corner of the text object).
    5. From the HTML code in the Properties dialog box, edit the auto-refresh interval in the setInterval method to the required time.

      Note:

      This value must be edited in terms of seconds*1000. For example, If the required refresh interval is 5 minutes (5*60 = 300 seconds), then the refresh time in the set Interval method should be 300*1000 = 300000 and the HTML code should be as follows, “setInterval('refreshTheFrame()',"300000");” in the text object properties.
    6. After editing is completed, submit and save the Dashboard.
    7. Open the required dashboard and verify whether the dashboard is refreshed automatically in the given interval.
  5. Intraday BIS reports are configured with data source LRM. You can create a new data source

    LRM DB in case it is needed that these reports populate from other database sources.

    1. Steps to configure Intraday BIS reports with new data sources:
      1. Create a data source with name LRM DB in the system.
      2. Edit the data model for the report you wish to change the data source.

        Figure 8-13 Edit Data Model


        This image illustrates Edit Data Model

      3. Click the group present in the data set and edit the dataset properties. The Edit Data Set dialog box is displayed.

        Figure 8-14 Edit Data Set


        This image illustrates Edit Data Set

      4. Choose the data source LRM DB . Click OK and save the Data model.

        Note:

        Since these reports are pointing to the LRM DB data source by default, an error message appears if the LRM DB data source is not created in the system. This error can be ignored, and you can proceed to the next step

        Figure 8-15 Edit Data Set - BIS-Direct Participants


        This image illustrates Edit Data Set - BIS-Direct Participants

      5. Perform this step for all the reports you wish to change the data source.

        Note:

        Data model to be changed for Intraday BIS reports in the /Shared Folders/Intra-day/ directory are as follows:
        • DM - BIS-Direct Participants
        • DM - BIS-Correspondent Banks
        • DM - BIS-Respondent banks
    2. You do not require to configure OBIEE if you are using the existing data source, that is, LRM which is used by other regulatory reports.