Skip Headers
Oracle® Business Intelligence Applications Installation Guide for Informatica PowerCenter Users
Version 7.9.6.1

Part Number E14843-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

C Integrating Interactive Dashboards and Operational Applications Data

This appendix describes the additional configuration steps required for you to run an Oracle Business Intelligence application with a Siebel CRM application.

Tip:

See Oracle Business Intelligence Server Administration Guide before performing any of the tasks in this section.

The integration of Oracle Business Intelligence with a Siebel operational application involves two general processes:

C.1 Importing Oracle's Siebel Industry Applications Seed Data

Oracle Business Intelligence seed data is not installed with Oracle's Siebel Industry Applications. You must import the seed data into your database after the Oracle Business Intelligence installation is completed. You only need to perform this procedure if you are using Oracle's Siebel Industry Applications.

To import Oracle Business Intelligence seed data into a transactional database

  1. Obtain the required language.inp and .dat files from the Oracle Business Intelligence language folder \OracleBI\SeedData\l_xx, where xx is the two-letter code for the language you want to import.

  2. Copy the .dat and corresponding .inp file from the language folder to the server installation folder OracleBI\server\bin.

  3. From the command prompt in \OracleBI\SeedData\bin, run the following command:

    dataimp /u $USERNAME /p $PASSWORD /c "$ODBCDatasource" /d $Tableowner /f analytics_seed_<XXX>.dat /i metadata_upgrade_<XXX>_<DBPlatform>.inp /w y
    

    Replace the XXX with the three-letter code (FRA, ITA) and the DBPlatform with the abbreviation for the database platform being used. For example:

    dataimp /u sadmin /p sadmin /c JPN_CRMDEV1 /d siebel /f analytics_seed_JPN.dat /i metadata_upgrade_JPN_db2.inp /w y
    

For information about merging content into Oracle Business Intelligence Presentation Services, see the topics about using the Catalog Manager in Oracle Business Intelligence Presentation Services Administration Guide.

C.2 Completing the Initialization in the Siebel Operational Application

Once you have configured your Oracle BI Server and are able to access the dashboards, you need to update the Siebel operational application to view Analytics dashboards from within the Siebel operational application. Completing the initialization in the Siebel operational application involves the following processes:

C.2.1 Updating the Siebel Operational Application

The following task changes the Siebel operational application host name to the host name of the machine that runs Oracle Business Intelligence Presentation Services.

To update the Siebel operational application

  1. Open your Siebel operational application and login as SADMIN.

  2. Navigate to View, then Site Map.

  3. Click Integration Administration screen.

  4. Click Host Administration view.

  5. Query for NQHOST in the Virtual Name column:

    • In Windows, change the host name from <AnalyticsServerName> to the host name of the machine that runs Oracle BI Presentation Services.

    • In AIX or Solaris, change the host name from <AnalyticsServerName> to the name of the port.

      For example, servername.siebel.com:8080

      Note:

      For UNIX platforms only: You may need to add the domain name suffix to the server name in order to make sure that action links work on the Oracle Business Intelligence user interface.
  6. Log out of the application and log back in.

C.2.2 Reapplying Customized Style Sheets

For Oracle's Siebel Business Analytics versions 7.7 and later, new styles have been appended to the following style sheets:

  • Go.css

  • PortalBanner.css

  • PortalContent.css

  • Views.css

These new classes are identified in the style sheets. In this version of Oracle Business Intelligence, new styles and files must be added to the underlying style sheet (for example, to s_Siebel7). For complete functionality, any custom styles require similar updating. In addition, views2.css and some other files have been added to the s_ directory. For custom column formatting to work properly, references to font sizes and families should also be removed from the TD Styles section in PortalBanner.css, PortalContent.css, Views.css.

Because of these changes to styles, review your deployment's customizations manually, reapply them, and test them thoroughly to ensure that there are no problems.

After you have tested them, but before you copy the default views.css files back to the implementation server, perform the following task on the server to clear the server caches.

To clear the server caches and restore your default views

  1. Shut down Oracle Business Intelligence Server, Oracle BI Presentation Service and IIS.

  2. Remove your custom views.css from the directory where it has been installed.

    For example:

    $INSTALL\web\app\res\s_Siebel7\b_mozilla_4
    

    or

    $INSTALL\OracleBIData\Web.
    
  3. Clear the Oracle BI Presentation Services Server Cache.

    In the C:\WINNT\Temp directory, delete the nQs_*.temp files.

  4. Clear the Browser Cache.

    From the Internet Explorer menu, navigate to Tools, then Internet Options, then Settings, then View Files, and delete all the files in these folder.

  5. Restore the default views.css files to the appropriate folder.

  6. Restart the Analytics Server, Oracle BI Presentation Services and IIS.

C.2.3 How to Configure Oracle Business Intelligence with Oracle's Siebel Web Extension (SWE)

Whenever you run Oracle Business Intelligence and Siebel Web Extension (SWE) on separate machines, you must perform additional configuration steps in order for action links and interactive charts to work. If, for example, you plan to run the SWE and Oracle Business Intelligence Presentation Services on different Web servers, you must use some kind of networking or load balancing mechanism to create a single logical domain (or virtual IP address) for the two machines.

Caution:

When Oracle BI Applications Server and Oracle BI Presentation Services are installed on different machines and load balancing software is used to create a single virtual IP address, the action links feature works only if you log onto the Siebel application using a virtual Web browser. Action links fail on a dedicated client if the SWE and Oracle BI Presentation Services servers are on separate machines. Either use a virtual Web browser, or install the Oracle BI Applications Web Server and Oracle BI Presentation Services on the same machine.

When one virtual IP address is created for two machines, the Web browser accesses one IP address and is still routed to different physical machines, based on the port accessed. From the browser, it appears that both servers are running on the same IP address.

You can use any of several physical methods to create a single logical domain, such as running SWE and Oracle Business Intelligence Presentation Services on a single machine if you are not load balancing the SWE, or using a router to do the mapping, or using load balancing software. Your company must determine the best mechanism to accomplish this routing given the topology being used.

Configuring Oracle Business Intelligence to work with Siebel Web Extension includes the following tasks:

C.2.4 Creating a Virtual IP Address for the SWE and Oracle BI Presentation Services

You create a virtual IP address for the Siebel Web Engine (SWE) and Oracle BI Presentation Services in order to make it appear that all servers are running on the same virtual machine. The easiest way to do this is to configure Oracle BI Presentation Services to run on a different port (for example, port 84) from SWE (which usually runs on port 80).

For example, SWE is load-balanced across <machine1>:port 80 and <machine2>: port 80, and Oracle BI Presentation Services is running on <machine3>:port 84, and the virtual address is defined as http://siebel.company.com. Therefore, the network or load-balancing software should be configured to route requests like http://siebel.company.com to <machine1> and <machine2>, and to route requests like http://siebel.company.com:84 to <machine3>.

To create a virtual IP address for Siebel Web Engine and Oracle BI Presentation Services

  1. On the network, set up CSS to direct requests from <virtual domain> to <physical Siebel Web Server Extension machine>:

    • Where the acronym CSS represents the load-balancer or router used to do the virtual IP configuration.

    • Where <virtual domain> is the virtual IP prefix that users enter to navigate to the Siebel applications (in the preceding example, this is http://siebel.company.com).

  2. On the network, set up CSS to direct requests from <virtual domain>:84 to <physical Oracle BI Presentation Services machine>:84.

  3. In the Siebel application, using the Siebel Administration screen, set the NQHost parameters for Oracle Business Intelligence Symbolic URLs to point to the <virtual domain>:84, instead of directly to the Oracle Business Intelligence Presentation Services server physical machine.

    Note:

    If you are running Oracle's Siebel Business Analytics 7.5.3 instead of version 7.7 or later, perform the following additional step.
  4. In the Siebel application on the Oracle Business Intelligence Presentation Services server machine, locate the registry setting \SOFTWARE\Siebel Systems, Inc.\Siebel Analytics\Web\7.5\Charts.

  5. Add a new key, ForceFileBasedPainter, and enter TRUE into the Data string.

C.2.5 Testing the Virtual IP Configuration for Oracle Business Intelligence and the SWE

Use a client browser to verify that Oracle Business Intelligence and SWE work when accessed directly through a physical machine address, using the following procedure. For <virtualdomain>, substitute the Virtual IP address you created in Section C.2.4, "Creating a Virtual IP Address for the SWE and Oracle BI Presentation Services".

To test the Virtual IP configuration with Oracle Business Intelligence and SWE

  1. In a client browser, type <virtual domain>:84/analytics. The Oracle Business Intelligence logon appears.

  2. In a client browser, type <virtual domain>/callcenter (or other Siebel application). The SWE appears.

  3. Navigate to an Analytics screen within the Siebel application to see if Oracle Business Intelligence appears.

  4. Interact with Oracle Business Intelligence charts and action links.

C.2.6 How to Configure Oracle BI Action Links

Oracle BI Applications supports action links in reports and dashboards to allow users to navigate from a record in an Oracle Business Intelligence dashboard to the same record in a Siebel operational applications.

For example, you can drill down directly from an Order Management Business Intelligence dashboard to the same record in a Sales view. The link is based on the row-ID column contained in a report. You can also create new action links for any existing report. For how to create Interactive Oracle Dashboards action links, see Oracle Business Intelligence Presentation Services Administration Guide.

Depending on your deployment, you may need to perform additional configuration of your Oracle Business Intelligence application in order for the action links feature to work properly. The following tasks are relevant to the configuration of your application for action links:

C.2.7 Testing Action Links

This task is part of the Section C.2.6, "How to Configure Oracle BI Action Links".

Use the following procedure to make sure that action links you create work correctly.

To test an Oracle Business Intelligence action link

  1. Log on using your system.

    Go to Service Analytics screen, then Employee Analytics, then To Do List.

  2. Click the action link on the pie chart in Overdue Activities.

    You should be in Overdue Activities Detail in Analytics.

  3. Click any ROW_ID action link.

    You should be in the Employee screen in Oracle's Siebel Call Center operational application.

C.2.8 Accessing Optional Analytics Applications

Depending on the options you purchased with your Siebel operational application, you must perform additional steps in order to access the corresponding Oracle Business Intelligence options. Table C-1 shows the additional options for Oracle Business Intelligence.

Table C-1 Oracle Business Intelligence Applications Options

Siebel Application Options

Sales

Sales Analytics

Service

Service Analytics, Contact Center Telephony Analytics

Marketing

Marketing Analytics


By default, the dashboards and reports contained in these optional areas are hidden. If, for example, you purchased Sales Analytics with your Sales application, you must perform the additional steps shown in the following procedure to access the Sales Analytics.

To turn on options for Sales Analytics

  1. Log in to Oracle Business Intelligence as Administrator.

  2. Navigate to Answers, then Oracle BI Presentation Services Administration and select the option to manage Presentation Services groups and users.

  3. Locate the Web Group corresponding to your option.

    The Web Group options are shown in the following list.

    • No Forecasting

    • No Forecasting Lite

    • No Universal Queuing

    • No Email Response

    • No Service Agreements

    • No Partner Marketing

    • No Partner ERM

    • No Partner ISS

  4. Click on the Edit icon.

  5. Under the Group Membership section, click the delete icon (X) to delete Analytics Users from this group.

  6. Click Finished and log out of the application.

  7. Log in again to access the additional optional dashboards and reports.

C.2.9 Process of Customizing Oracle BI Application Home Page and Dashboards

The process of customizing your Oracle Business Intelligence application's home page and dashboards may include the following tasks:

C.2.9.1 Customizing Oracle BI Content on the Siebel Operational Application Home Page

Oracle Business Intelligence applications are integrated with Siebel operational applications using the symbolic URL infrastructure. The following task describes how to use symbolic URLs to link a new report to a Siebel operational application home page and how to add new Analytics Dashboards to the Siebel operational application. The symbolic URL specifies how the HTTP request to the external application should be constructed and to defines any arguments and values to be sent as part of the request.

Note:

For more information on the symbolic URL infrastructure, see Siebel Portal Framework Guide. This topic assumes that you have successfully built a symbolic URL to link some external content, using the instructions given in Siebel Portal Framework Guide.

For each Analytical report on a Siebel operational application home page, there is a symbolic URL record defined that links the home page to the Analytics report. If you have not already done so, you need to create a new home page and set it up to use a symbolic URL.

Note:

For Oracle Business Intelligence Disconnected settings, see Section C.2.9.4, "Verifying NQHOST Setup for Pharma Disconnected Analytics Client".

The figure below shows example Inline and IFrame symbolic URL arguments.

Figure C-1 Examples of Symbolic URL Arguments.

This image is an example of the populated screen.

To configure a new Home Page to use a symbolic URL

  1. Make sure the symbolic URL has been set up.

  2. Launch the Siebel operational application and navigate to the Integration Administration, then Symbolic URL Administration view.

  3. Query for the symbolic URL that has been set up for Analytics.

    The name of this symbolic URL should be exactly the same as the calculated value of the field that was added to the Business Component. For example, you may have a symbolic URL named HomePageAnalytics.

  4. In the URL field, enter the Web URL. For example:

    http://NQHOST/Analytics/saw.dll
    

    For the Host Name, choose the Analytics Server Name from the drop-down list. The following table shows the other parameters for reports.

    Parameter Value
    NQHOST A virtual name in the URL that points to the Oracle BI Presentation Services machine
    Fixup Name Inside Applet
    SSO Disposition Inline
    Oracle BI Presentation Services application name Select from the drop-down list

  5. Create the appropriate symbolic URL Arguments.

    These arguments depend upon the particular Analytics report that you are trying to display. The Argument Values should be the same for any Analytics report you work with, except for the Path Argument Value. Use the procedure in Section C.2.9.2, "Determining the Oracle BI Report Path Argument" to determine the path to the Analytics report.

C.2.9.2 Determining the Oracle BI Report Path Argument

The Path argument tells the symbolic URL the path to the report on the Oracle BI Presentation Services. (For example, /shared/Sales/Pipeline/Overview/Top 10 Deals.) Use the following procedure to determine the path to the Analytics report.

To determine the path to the report

  1. Log on to your Oracle BI Presentation Services as an Administrator.

  2. In the Siebel operational application, navigate to Answers, then Oracle BI Presentation Services Administration.

  3. Select Manage Analytics Catalog, and then navigate to your report.

  4. Add this path name to the Symbolic URL argument.

    The following table shows the symbolic URL path arguments for reports.

    Name Type Path Argument Value Append Sequence #
    Cmd Constant GO Y 1
    Path Constant /shared/Sales/Pipeline/Overview/Top 10 Deals Y 2
    Syndicate Constant Siebel Y 3
    nQUser Command UseSiebelLoginId Y 4
    nQPassword Command UseSiebelLoginPassword Y 5
    PostRequest Command PostRequest Y 6

C.2.9.3 Adding Views for Custom Oracle BI Interactive Dashboards

This task is similar to that of adding Oracle Business Intelligence reports to the home page:

  • Using Oracle's Siebel Tools, set up a new view.

  • In the Siebel operational application, define a symbolic URL for that view.

For more information on how to set up a view to use Symbolic URLs, see Siebel Portal Framework Guide.

To configure the symbolic URL for Analytics dashboards

  1. Define a Symbolic URL.

    1. Navigate to Site Map, then Integration Administration, then Symbolic URL Administration.

    2. In the Symbolic URL Administration view, add a new record.

  2. Define Symbolic URL arguments.

    1. Navigate to Symbolic URL Administration.

    2. In the Symbolic URL Administration list, select the Symbolic URL you want to configure.

C.2.9.4 Verifying NQHOST Setup for Pharma Disconnected Analytics Client

Pharma Disconnected Analytics is a prebuilt Disconnected Analytics application for Oracle's Siebel Pharma Sales. When you run Oracle Business Intelligence Disconnected Client, your client application runs against a local instance of the database on your machine. You need to confirm that NQHOST is using the correct port number and DLL files to work with the Pharma Disconnected Analytics Client.

To verify the NQHOST setup

  1. Run the Disconnected Client application against your local database.

  2. Log in as Administrator.

    You must have access to the following Integration Administration Screen views:

    • WI Host Admin View

    • WI Symbolic URL Admin View

  3. Navigate to Administration – Integration.

  4. Click WI Symbolic URL List, and search for NQHOST in Virtual Name field.

    The Host Name value should be localhost:9762.

  5. Select the Host Administration View from the drop-down list and choose Symbolic URL Administration.

  6. The following table shows Disconnected Client symbolic URLs to search for.

    For each of the URLs, the URL field is:

    http://NQHOST/Analytics/sawd.dll
    

    The Disconnected Client Symbolic URL Names are:

    • ePharmaHomePageAnalytics1

    • ePharmaHomePageAnalytics2

    • ePharmaHomePageAnalytics3

    • ePharmaHomePageAnalytics4

    • SISMLSDistrictManagerDashboard1

    • SISMLSSalesRepDashboard1

    • SiebelAnswers

    • SiebelDelivers

    The following table shows the symbolic URL path arguments for Oracle BI Answers and Oracle BI Delivers.

    Name Type Path Argument Value Append Sequence #
    Cmd Constant Answers for SiebelAnswers Y 1
        Delivers for SiebelDelivers    
    nQUser Command UseSiebelLoginId Y 2
    nQPassword Command UseSiebelLoginPassword Y 3

C.2.9.5 Integrating the Pharma Application Home Page with the Pharma Disconnected Analytics Client

If you have licensed both the Siebel Pharma operational application and Oracle Business Intelligence Disconnected Client, you must change part of the operational application configuration file in order to access Analytics reports on the LS Analytics Home Page and to allow Create Target List integration.

To allow integration of Pharma Analytics Home Page with Pharma Disconnected Analytics

  1. On the machine where you have installed the Siebel operational application, navigate to $INSTALLDIR\sea77\siebsrvr\BIN\ENU\epharma.cfg.

  2. Using a text editor, open the file epharma.cfg.

  3. In the Local section, find the parameter UseCachedExternalContent.

    The default value for this parameter is TRUE.

    Note:

    If this parameter remains set to TRUE, Analytics reports on the Home Page return an error.
  4. Set the UseCachedExternalContent parameter to FALSE.

  5. Save and close the file.

C.2.9.6 Importing Pharma Application Target Lists to the Pharma Disconnected Analytics Client

If you have licensed both the Siebel Pharma operational application and Oracle Business Intelligence Disconnected Client, you must change part of the operational application configuration file in order to allow you to import the contacts from the Pharma Analytics Create Target List function into the Disconnected Analytics Client.

To allow importation of Target List contacts into Oracle Business Intelligence Disconnected Client

  1. On the machine where you have installed the Siebel operational application, navigate to $INSTALLDIR\sea77\siebsrvr\BIN\ENU\epharma.cfg.

  2. Using a text editor, open the file epharma.cfg.

  3. In the Siebel Client section, find the parameter EnableFQDN.

    The default value for this parameter is TRUE.

    Note:

    If this parameter remains set to TRUE, the Create Target List functionality is disabled in the Pharma Disconnected Analytics Client.
  4. Set the EnableFQDN parameter to FALSE.

  5. Save and close the file.

    1. In the Symbolic URL Arguments list, enter the arguments that need to be sent to the external host.

      The following table shows the symbolic URL argument definitions for dashboards.

      Parameter Value
      Fixup Name Default
      SSO Disposition IFrame
      Oracle BI Presentation Services application name Select from the drop-down list.

      The following table shows the symbolic URL path arguments for dashboards.

      Name Type Value Append Sequence #
      Cmd Constant Dashboard Y 1
      PortalPath Constant / Y 2
      Page Constant Sales Y 3
      Syndicate Constant Siebel Y 4
      nQPassword Command UseSiebelLoginPassword Y 5
      nQUser Command UseSiebelLoginId Y 6

  6. In Oracle Business Intelligence, create the dashboards.

    Note:

    Only an Oracle BI Presentation Services administrator can perform this step.
  7. In Oracle Business Intelligence, set up the dashboards to your requirements.

C.3 Viewing Information About Preconfigured Dashboards

If your organization has prebuilt applications installed, you can use Catalog Manager to locate and view information about preconfigured dashboards. You may first have to expose the dashboards and requests.

C.3.1 Exposing Dashboards and Requests

Depending on the Oracle Business Intelligence options your organization purchased, you may need to expose these options before the associated dashboards and requests can be viewed in Oracle BI Presentation Services and in Catalog Manager. This applies to sites that have the following prebuilt applications:

  • Sales Analytics

  • Service Analytics

  • Contact Center Analytics

  • Marketing Analytics

  • Partner Analytics

C.3.2 Locating Dashboards, Page Names and Reports

In Catalog Manager, the Presentation Catalog distributed with prebuilt applications has the following structure: Presentation Catalog > shared folder > prebuilt application name > _portal folder > dashboard name > page name. The path to locate reports is Presentation Catalog > shared folder > prebuilt application name > Folder name > Report name.