BITeamwork's management console ("Control Panel") is housed within the Oracle BI Administration page. Therefore only a user account having the Business Intelligences System's Administration privileges may access the console.

Not only has BITeamwork's management system been directly embedded in the Oracle BI application, it re-configures the Oracle BI Administration page contents so that they are more accessible based on usage. This allows a better user experience for accessing both the Oracle BI administrative components as well as those for BITeamwork.

This document lists all of the information regarding the BITeamwork Management Console such as how it is accessed, each area of management, how it is embedded in the BI Application, etc.

As mentioned in the Getting Started section above, the BITeamwork management console is located on the Administration Page of the Business Intelligence application. During the installation of BITeamwork, the out-of-the-box configuration for the Oracle BI Administration page will be customized using the BI System's API. The result is the BITeamwork enhanced Administration page which contains several tabs to provide a stronger user experience. The tab marked "BITeamwork" (a.k.a BITeamwork Control Panel) provides access to the core BITeamwork management console.

Access the BITeamwork Control Panel by clicking on the Administration link in the Global Header of the Oracle BI Application.

See the BITeamwork Layout

The Administration Page of Oracle BI, after the installation of BITeamwork is based on an easy access tab user interface. By clicking on a tab, the content within the tab area changes to show information respective to the tab label. The tabs are labeled as seen in the image below and described by number beneath it.


Figure layout_1
  1. General Tab
    • Provides access to basic, and most commonly used features used in the administration of Oracle BI 11g.
  2. Advanced Tab
    • Provides access to the lesser used features of Oracle BI 11g administration
  3. BITeamwork Tab
    • Provides access to the BITeamwork Control Panel enabling the Oracle BI 11g Administrator to configure BITeamwork. The options within the BITeamwork tab are listed on the left-side of the tab content.

    • Figure layout_2

The Company section of the BITeamwork tab provides the central configuration for the BITeamwork licensee and company information such as Company Name and Company Logo.

When a customer purchases a license for the Enterprise Edition BITeamwork the customer receives a unique license key. In order to activate the Enterprise Edition features the license key must be entered in the field labeled License. This is also true for customers testing the product under the 15-day trial once they receive a trial license key from their trial request.


Figure company_1

How to Enter a License Key

After licensing BITeamwork or accepting a trial version, a license key must be entered on the Company section of the BITeamwork tab in order to access all Enterprise Edition functionality. In order to do this:

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Company link
  3. Enter the Company Name and Contact Email provided in the license email
  4. Enter a contact phone number in the Phone #
  5. Enter the License Key in the in the License field
  6. Click the Save button

The goal of the Environment Eye is to provide users of Oracle BI 11g with a reference to the environment in which they are currently operating. The Environment Eye provides a banner across the top portion of the Oracle BI 11g application. This provides users with a visual reference so that adjustments are not mistakingly made to the wrong environment as seen in the image below.


Figure environment_eye_1

The Environment Eye banner is controlled by the BI Administrator when editing the fields in the Environment Eye section and setting the Active Status dropdown value to True.


Figure environment_eye_2

How to Edit the Environment Eye

In order to set this feature:

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Environment Eye link
  3. Update the fields on the form
  4. Click the Save button

Description of Edit Fields for Environment Eye

  1. Alias
    • Used to identify the object. This an arbitrary name.
  2. Message Text
    • The text that appears on the Environment Eye banner
  3. Background Color
    • The color (HEX code or text color) of the Environment Eye banner background
  4. Font (Hex) Color
    • The text color (HEX code or text color) for the Environment Eye banner
  5. Font Size
    • The text size of the Environment Eye banner
  6. Mode
    • The mode/style of the Environment Eye banner (Default is set to "default")
  7. Active Status
    • Determines if the Environment Eye banner is visible in the environment or not

The ability for BITeamwork to work on the BI Server without interference or calls from other servers such as cross-site access a blocking mechanism referred to URI Access is in place. By default the "localhost" and "*" options are configured during installation of BITeamwork. The "localhost" option allows for access of BITeamwork to work on the server on which it is deployed. The "*" (asterisk) option allows for any other URL contacting the BITeamwork REST and URL commands to be called from that location.

On a closed network BI Server, such as a Oracle BI environment not accessible outside of the Intranet, the default settings may remain. However, if the Oracle BI application is accessible via the Intranet consideration to input a a new entry for the publicly accessible DNS should be made. In this case, entries should be made for the Top-Level Domain only.

How to Manage URI Access

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the URI Access link
  3. The following management options are available:
    • Create a new entry by clicking the + Add New URI Code button
    • Edit an existing entry by selecting the Edit button corresponding to the entry from the list
  4. Edit the form fields when creating or editing an entry.
  5. Click the Save button

Figure uri_access_1

How to Create or Edit a URI Access Point

  1. Access the URI Access Management option in the BITeamwork Control Panel
  2. Click on the Edit button corresponding to the Splash Page of which you wish to edit. To create a new URI Access Point click the Add New URI Code option.
  3. Edit the form fields
  4. Click the Save button.

Figure uri_access_2

Note on URI Access and the Default Settings


URI Access was designed to allow give users from only designated access points to access your BITeamwork solution in your Oracle BI implementation. Although this is a security consideration and not really applied out-of-the-box we still believe there will be a use case for this functionality at which point we will provide further guidance. The default URI Access records (i.e.: "*" and "localhost") installed during the BITeamwork installation should not be removed or edited.

A splash page allows the Oracle BI system to announce or otherwise convey information to end users of the system with an obstructive pop-up window displaying a simple or complex message. Splash pages are created by the BITeamwork Administrator. They can be scheduled to display for a certain period of time and manually set to a visible status. The Enterprise Edition version can create and save multiple Splash Page entries. Regardless of the number of Splash Pages created only one splash page can be made visible at any one time.


Figure splash_page_0

Splash pages display to everyone accessing the Oracle BI system and appear on the following areas of Oracle BI:

  • Sign-in Page
  • Catalog Page
  • Home Page
  • Dashboard Pages
  • Analysis Editor

Users can dismiss the Splash Page by checking the Please don't show this message again today unless its content changes checkbox and then clicking the Close button.

How to Manage Splash Pages

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Splash Page link
  3. The following management options are vailable:
    • Create a new entry by clicking the + Add Splash Page button
    • Edit an existing entry by selecting the Edit button corresponding to the entry from the list
    • Delete an existing entry by selecting the Remove button corresponding to the entry from the list
  4. Edit the form fields when creating or editing an entry.
  5. Click the Save button

Figure splash_page_1

How to Create or Edit a Splash Page

  1. Access the Splash Pages Management option in the BITeamwork Control Panel
  2. Click on the Add Splash Page or the Edit button corresponding to the Splash Page of which you wish to edit
  3. Edit the form fields:
    • Saved Title - Will appear as the header of the Splash Page when shown to users
    • Message Text - The body of the splash page message. This is full HTML capable by using the rich text editor.
    • Start Date - The beginning date/time for the splash page to be shown to users
    • Finish Date - The final date/time for the splash page to be visible
    • Active - Absolute option for determining if splash page is in use or deactivated in the system
    • Preview Only button allows the editor to view the splash page without saving it. Clicking this give you a previous of what to expect when rendered to the other users. You'll still need to click the Save button to confirm any changes you've made.
  4. Click the Save button.

NOTE: If adding an image via link URL, you must enter a new line underneath the image to save the splash page properly. Failure to do so prevents it from being saved with the image URL. It is a klugy configuration where text or some other content underneath the image is expected.


Figure splash_page_2

Categories are provided as an attribute selection mechanism for end-users creating comments within the BI System. Ultimately categories can be used to segment or otherwise provide taxonomy for comments. The BITeamwork Administrator manages the categories in the BITeamwork Management Console.

How to Manage a Categories

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Categories link
  3. Create a new entry by clicking the + Add Category button
    - or -
    Edit an existing entry by selecting the Edit button corresponding to the entry from the list
  4. Edit the form fields

    The Sort Order field provides the means to order the categories so they appear in a specific sequence when presented to the end users.

  5. Click the Save or Add Category button

NOTE: If the list of records is long you can use the search box to begin typing the name of a potential records to dynamically filter the results.


Figure categories_1

How to Edit a Category

  1. Access the Category Management option in the BITeamwork Control Panel
  2. Click on the Edit button corresponding to the category of which you wish to edit
  3. Edit the form fields:
    • Category Name - Appears to end users as category option
    • Description - General purpose of the category.
    • Sort Order(#) - Provided as a way to create a precedence for how the categories are ordered when viewed in a drop-down menu, etc.
    • Cell Comment Color - Determines the background color "highlight" when category is used for a cell annotation comment.
    • Cell Comment Icon - Determines the icon shown in a table cell when category is used for a cell annotation comment.
    • Deleted - Determines if the category is to be deleted from the system. Checking this and clicking the "Save" button will soft delete the category. All comment references will remain intact an this will not deleted the associated comments.
    • Secureable - Determines if the category must be secured with privileges to a specific user or application role/group. Use the Manage Category Security option for assigning category privileges.
  4. Click the Save button.

Figure categories_2

Categories can be secured by selecting the "Secureable" checkbox as mentioned in the Editing a Category section above.

How to Secure a Categories

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Category Security link or within the Categories page click Manage Category Security link at the bottom of the section.
  3. Select a secureable category from the Privilege dropdown menu
  4. Select either Application Role or User from the Principal Type dropdown menu
  5. Select a principal (Application Role or User) from the left choice box, then click on the Add >> button
  6. Click the Save button in order to save the change

NOTE: To remove a principal from this category security, click the desired user or Application Role from the right-side choice box and click the << Remove button then click Save to complete the change.


Figure categories_security_1

Dashboard commentary controls can be set at the "Dashboard" level. The current release allows for the administrator to lock the ability to input commentary on any dashboard at any point in time. They may then release the locked status. During the locked status users (with permissions) can view commentary in a read-only format. This is excellent for companies locking comments during a financial close period where comments are being reviewed and then re-opened for the next financial period when ready.

How to Control Dashboard Access for Commentary

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Dashboard Access link
  3. View the list of Dashboards. If the list is long you may use the Search field underneath the Dashboard Manager heading and begin a type ahead search
  4. Click the Edit Info button to begin editing a dashboard

Figure dashboard_access_1

Dashboard Creation and Editing

The dashboard listed in Dashboard Access are only those that have once had at least one comment created within its pages. Only then does BITeamwork record the dashboard in its system for you to control here. As of version 3.8, there is no pre-population of all dashboards for listing in this section.


Figure dashboard_access_2

How to Edit Dashboard Access for Commentary

  1. Editing the dashboard can now take place in the Edit Info view of the Dashboard Access page
  2. Review the form fields:
    • Dashboard Name - Name of the dashboard as stored in the BITeamwork repository
    • Description - Ad hoc description as provided by BITeamwork administrator used only in BITeamwork
    • Unique Ref - BITeamworks Unique Reference to the dashboard
    • Dashboard URL - URL of the dashboard as originally captured when first comments were created on a dashboard page in dashboard
    • Status - Status of activity allowed by BITeamwork for commentary on the dashboard
    • Active - Status for BITeamwork's acknowledgement of the dashboard as active or non-active
    • Deleted - Status for BITeamwork's acknowledgement of the dashboard as deleted or non-deleted
    • Created - Timestamp for when the dashboard record in BITeamwork was created
    • Modified - Timestamp for when the dashboard record in BITeamwork was modified (typically initially the same as created timestamp)
    • Last Modified by - User who actually last modified (not necessarily created) this dashboard record by creating a first comment
  3. Enter a description to provide more detail about the purpose of the dashboard, if desired
  4. Change the Status to Comments Locked, in order to lock comments and place in read-only mode, or select Normal for standard operation
  5. Check the Active checkbox to keep the dashboard as active in the system for BITeamwork commentary usage
  6. Check the Deleted checkbox to deactivate the dashboard in the system for BITeamwork commentary usage
  7. Click the Save button in order to save any changes

Comments can become untimely or for some reason become unnecessary. As an administrative feature you are able to remove comments from the system.

Comments are Soft Deleted

BITeamwork uses a concept referred to as "Soft Deletion" in order to purge/delete comments from the BITeamwork system. This means that the records are not truly removed/deleted from the underlying database repository but rather a flag column is toggled to an "is deleted" state rendering the visibility of comments off.


Figure purger_1

How to Purge Comments

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Comment Manager link
  3. Select a user from the Comments from Users(s) list box or select All Users
  4. Select date range by editing the Date Start and Date Finish fields
  5. Select the type of comments to delete by choosing an options from the Comment Type dropdown

    For example, Choosing Analysis Cell would delete only the cell comments for the user and date range selected in the form once the Save button is clicked.

  6. Click the Save button to run the routine selected.

BITeamwork functionality, such as creating comments, etc. can be restricted on a per user or per Application Role basis. These privileges are separate from the Oracle BI 11g privileges but are controlled from the BITeamwork Management Console.


Figure security_1

How to Add or Remove Privileges

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Security link
  3. Select a privilege option from the Privilege dropdown
  4. Select a principal type from the from the Principal Type, User or Application Role
    • Based on the principal type selected a list of principals filtered by that type appear in the left listbox column
  5. Add a principal to an access privilege by moving the principal (i.e.: User(s) or Application Role(s)) from the left column to the right column by clicking on the Add button between the columns
  6. Remove a principal from an access privilege by selecting the principal (i.e.: User(s) or Application Role(s)) from the right column and moving it to the left column by clicking on the Remove button between the columns
  7. Click the Save button to save the configuration

Note on Populating Security

Application Roles and Users are populated in this section by the Sync Manager. The Sync Manager communicates with the Oracle BI System Web Services and requires an Oracle BI administrator user's credentials to be updated in the Web Service Manager section and then the Sync Manager to be executed.
See Configuring the Oracle BI Web Service and Using Sync Manager

Security Privileges

Privilege Name Privilege Description Since Version
Can Add Footnote Comment Users can add a footnote comment to bottom of an OBIEE view object 3.7
Can Add Data Point to Comment Users can add a data attribute associated with comment for later aggregation or review 3.8.3
Can Save Comments in Bulk Users can use the bulk update and save option for inline cell commentary (functionality for bulk save not integrated currently) 3.8.3
Can Change Own Comment Context Sensitivity Allows users to switch between strict context of prompt references of originating commentary and loosely based context sensitivity to view comments of all context on a dashboard/dashbord page 3.7
Can Leave Dashboard Comment Allows users to create a general dashboard comment on any dashboard or dashboard page on which they have access 2.0
Can Leave Cell Comment Allows users to create an inline cell comment or cell annotation on any dashboard or dashboard page analysis/report on which they have access 2.0
Can Reply to Comment Allows users to reply to any type of comment on any dashboard or dashboard page on which they have access 2.0
Can Push Comments to Salesforce Chatter Allows users access to a configured Salesforce Chatter integration with BITeamwork for OBIEE for posting or viewing comments from Chatter inside of OBIEE 2.0
Can Push Comments to Yammer Allows users access to a configured Yammer integration with BITeamwork for OBIEE for posting or viewing comments from the social network inside of OBIEE 2.0
Can Use Metadata Search Allows users to make use of the metadata search capability for viewing metadata in OBIEE (functionality incorporated in version 4.0) 2.8
Can Add Metadata Annotation via MDSearch Allows users to make use of the metadata dictionary collaboration capability in OBIEE (functionality incorporated in version 4.0) 2.8
Can Access the Collaboration Side Bar Allows users to access the side bar that minimizes and maximizes, contains the social network integration, and allows dashboard commentary 2.0
Can Access the BITeamwork ToolBar Allows users to access the options in the OBIEE Global Header that are for commentary and settings configuration for BITeamwork 2.0
Can Push Comments to Podio Allows users access to a configured Citrix Podio integration with BITeamwork for OBIEE for posting or viewing comments from the social network inside of OBIEE 3.5
Can Vote-Up Comments Allows a user to vote/like comments posted by themselves or other users 2.2
Can Secure a Comment Allows a user to secure a comment from viewing from or by other users 2.3
Can Use Comment Notification Allows a user to use the notification option to send other OBIEE system users an email (via OBI Delivers) or a dashboard alert about a comment posting 2.4
Can Select a Comment Category Allows a user to have the option to choose a comment category for adding taxonomy to a comment 3.0
Can Set a Comment Prompt Focus Context Allows a user to modify the context sensitivity of a comment when created by leveraging only one or more of the total number of prompt context options available thus reducing the context focus of the comment to few user prompt selections. 3.2
Can Create an Embedded BI View Allows a user (recommended administrators only) to created an Embedded BI view of which can be used in SharePoint or another intranet portal where an OBIEE data set, view, or graph is desired to be seen. 3.4
Can Mark Comments as Sticky Allows a user to mark a dashboard comment as "sticky" meaning it rests at the top of the list of dashboard comments 3.5
Can Mark Comments as Final Allows a user to mark a comment as final (as of version 3.4 final status is only a database flag an no functional usage) 3.4
Can Mark Comments as Approved Allows a user to mark a comment as approved (as of version 3.4 final status is only a database flag an no functional usage) 3.4
Can Modify Configuration Files Allows a user (Recommended administrators only) to modify configuration options via the BITeamwork Control Panel 3.8
Can Create/Modify Dashboard Documentation Mode Comments Allows a user to create or edit a dynamic dashboard document (an extension of inline cell comment via BITeamwork API) for creating rich dynamic user-based content with templates to overlay existing or new dashboard pages. 3.6

An advanced collaboration feature for BITeamwork is leveraging Social Vendors such as Salesforce Chatter, Citrix Podio, and Microsoft Yammer. After the basics of creating social vendor application for your organization has been accomplished, along with any pre-requisites, the Social Vendor must be configured in the BITeamwork Management Console so that BITeamwork can make a reference to the social vendor application.


Figure social_1

How to Edit a Social Vendor

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Social Apps link
  3. Select a Social Vendor from the Social Application dropdown
  4. Update the following required fields
    • API URL

      Is the URL for the instance of Social Vendor portal for which you will connect this environment. This is typically the main login url path you use for your company to connect to the social vendor website or the specific security URL assigned to your company. For example, organizations using Salesforce.com have a My Salesforce.com portal URL, which is usually https://mycompanyname.salesforce.com/.

    • API Secret
    • API Key
    • Access Scope

      For Salesforce.com the default value is id api refresh_token which reflects the settings required for the Salesforce.com Administrator to enter for OAuth privileges when they create the Custom App in the Salesforce.com portal.

    • Callback URL
      • This URL must be in the following format http://<server_name>:<port>. For example, https://intranet.obiee.companyxyz.corp or https://intranet.obiee.companyxyz.corp:9704
      • No trailing slash should be entered
      • Salesforce Chatter requires an SSL Callback (Read more)
    • Active Status
    • Test Social Connection

      Usage Note: Although this is not a field that requires editing, it is a link that only works after the social vendor configuration has been completed, the save button pressed, and the page refreshed. If the page is not refreshed the Test Social Connection link is not operational.

  5. Click the Save button to save the configuration

Note on Callback URL

Enter ONLY the Server Name and port in the Callback URL form, i.e.: http[s]://<server_name>[:<host_name>].
FYI, the BITeamwork application dynamically concatenates this URL path at runtime to the one shown below (not entered by you) in order to receive the proper callbacks from the Social Vendor Application.

  • For Yammer
    • https://servername:port/bitw/x/social/yammer/callback
  • For Salesforce.com Chatter
    • https://servername:port/bitw/x/social/chatter/callback
  • For Podio
    • https://servername:port/bitw/x/social/podio/callback

Troubleshooting a Social Vendor Connection Attempt

Below are issues we have seen encountered when configuring or attempting to integrate an enterprise social vendor.
Usually, once the configuration has been successfully completed there is no need to adjust the settings for the Social Vendor on any continued frequency.

  • Blank Screen in IE after Clicking the Authorize Chatter link in Collaboration Pane
    • This is usually a problem with one of the values entered either on the social vendor site or through BITeamwork's configuration area. Use a different browser such as FireFox or Chrome to see the error message as shown by the Social Vendor.

Maintenance Mode provides an Oracle BI Administrator with the ability to cast a page block description on the BI Application in order to inform users that the BI Application is down or undergoing maintenance. A custom message can also be displayed in order to communicate the maintenance window and effort. The use case for this functionality is to ensure that during migrations or other maintenance window causing efforts that users understand potential risk of loosing data or accessing stale data if accessing the system during a maintenance window.


Figure maintenance_1

How to Edit Maintenance Mode

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Maintenance Mode link
  3. Update form field values:
    • Active - Determines if Maintenance Mode is on and visible to users
    • Alias Title - Arbitrary title for the item
    • Appears On - Used to discern ares of the BI System which maintenance mode will appear
    • Coverage - Used to discern page coverage area when displayed, ex: full screen, half screen, pop-up
    • Projection - Used to determine if message is displayed as a modal, pop-up or always visible at top or bottom of screen
    • Message Text - Full HTML text shown in Maintenance Mode message. It can include images and video references as well as rich HTML code.
    • Preview Only button allows the editor to view the maintenance mode window without saving it. Clicking this give you a previous of what to expect when rendered to the other users. You'll still need to click the Save button to confirm any changes you've made.
  4. Click the Save button to save the configuration

The Oracle BI Web Service integration is a key feature of BITeamwork for Oracle BI. Without it many of the features in BITeamwork will not work properly. In order to configure the Web Service for BITeamwork to access a user with all SOAP privileges must be used and that accounts credentials stored in the OBIEE Web Service page from the BITeamwork management console. The WS URL should be the full URL to reach the Oracle BI 11g WSDL, for example: http[s]://<server_name>:9704/analytics-ws/saw.dll/wsdl/v6

Enter the credentials for the user who will act as the power user making calls to Oracle BI on behalf of BITeamwork. The credentials are stored in th BITeamwork repository and encrypted with a high level of algorithm similar to that which is used popular e-commerce systems such as Facebook.com.


Figure ws_config_1

Sync Manager updates the BITeamwork metadata repository with the most recent updates or changes within the Oracle BI environment. This is mainly concerns new Application Roles and Users, security updates, and other metadata aspects of Oracle BI.

This section must be assessed during configuration at least once. A sync for Refreshing Application Roles is required as BITeamwork acts as a guest plug-in on the Oracle BI system and as such it only has access to the most current Oracle BI metadata information at the BI server start-up and when the Sync Manager Begin Sync option is executed.

NOTE: You must first configure the Web Service Manager with the credentials of an OBIEE Administrator User before running any Sync options.


Figure sync_1

How to Use Sync Manager

  1. Click on the BITeamwork tab on the Administration Page
  2. From the left navigation options click the Sync Manager link
  3. Determine which link or action to conduct
    • Refresh Application Roles
      • Updates the BITeamwork application with the latest recently added Application Roles and Users. An use case for executing this sync would be after adding a new application role via Enterprise Manager or WLST and needing to update BITeamwork privileges. In which case a sync is required so that BITeamwork can reference the newly created Application Role.
    • Refresh all Users from Web Catalog
      • This option is not recommended. However, it updates the BITeamwork application with the all of the users who have Web Catalog folders associated with their profiles. Any new users that log in to BITeamwork, after BITeamwork is installed will be automatically added to the list of users that BITeamwork will track.
  4. Click the respective Begin Sync option
  5. Wait for the Sync Message to appear confirming the sync response
  6. Done

BITeamwork application information is controlled in this section of the BITeamwork Control Panel. Items found in this section would be global configuration settings such as cell comment color and icons, providing attribute values for the location of the Fusion Middleware (FMW) HOME folder, etc.

For maintainability this section is broken up into several segments which expand and collapse upon your selection. Each of the items is listed below in further detail:


Figure server_app_info_1
  • Cell Comment Icon URI:
    • URL path for icon to indicate that a cell comment when exists. Icons should be 16px x 16px in dimension. Valid URL syntax examples include:
      • http://mycompany.com/images/icon.png
      • /bitw/images/icons/[fire-small|balloon-small|plus-small].png (See More Examples Here)
    • Default: Blank
  • Cell Comment Color:
    • Determines the background color of a cell comment/annotation on a dashboard report view.
      • Any single hex color code or text color. For example, #FF9900 for a bright orange or pink for the color pink. Text colors are acceptable but hex colors are preferred.
      • Enter None so that regardless of a background image or color of an existing cell no color will show but the existing and the hover over the cell will still work as designed.
    • Default: Blank
    • Note: Blank or Transparent Color

      If you need to ensure that a cell annotation has no color or is transparent, enter the word, None
  • SideBar Bkg Color:
    • Determines the background color of a collaboration pane shown in the dashboard.
      • Any single hex color code or text color. For example, #FF9900 for a bright orange or pink for the color pink. Text colors are acceptable but hex colors are preferred.
    • Default: Blank
  • SideBar Logo URI:
    • Provides an image URL that will be shown towards the top of the collaboration pane in the dashboard.
      • Any URL referencing a valid image accessible through the firewall on which the BI System resides will be permitted.
        A refresh of the BITeamwork collaboration pane is required for this change to take affect. Users which have not previously logged in to the BI portal will see the change of the URL once it has been made in the BITeamwork Control Panel. Other users having already accessed the system may require a refresh of BITeamwork or wait until their session times out (one day) in order to see the change.
    • Default: Blank
  • SideBar Logo Position:
    • Determines the position of the image established in the SideBar Logo URL fields.
      • The dropdown menu provides the only relevant options: left, center, right. Center is the default.
    • Default: Center
  • Vote Up Icon URI:
    • Provides an image URL that will replace the existing "thumbs up" icon used for voting comments..
      • Any URL referencing a valid image accessible through the firewall on which the BI System resides will be permitted.
        A refresh of the BITeamwork collaboration pane is required for this change to take affect. Users which have not previously logged in to the BI portal will see the change of the URL once it has been made in the BITeamwork Control Panel. Other users having already accessed the system may require a refresh of BITeamwork or wait until their session times out (one day) in order to see the change.
      • Icons should be 16px x 16px in dimension. Valid URL syntax examples include:
        • http://mycompany.com/images/icon.png
        • /bitw/images/icons/[fire-small|balloon-small|plus-small].png (See More Examples Here)
    • Default: Blank
  • Most Helpful Comments Icon URI:
    • Provides an image URL that will replace the existing "thumbs up" icon used for voting comments..
      • Any URL referencing a valid image accessible through the firewall on which the BI System resides will be permitted.
        A refresh of the BITeamwork collaboration pane is required for this change to take affect.
      • Icons should be 24px x 24px in dimension (16x16 icons work as well). Valid URL syntax examples include:
        • http://[any server name]/images/icon.png
        • /bitw/images/icons/[fire-small|balloon-small|plus-small].png (See More Examples Here)
    • Default: Blank
  • Show Print Comments on Views:
    • Determines if the Print Comments link appears under a view (i.e.: graph, chart, table) on a dashboard having comments associated with it.
      When set to true the link should only appear if:
      1. A comment exists for the view
      2. The dashboard "print" option is turned on for that view, section or dashboard
    • Default: True

Figure server_app_info_2
  • Default Language:
    • Establishes the default language of the BITeamwork collaboration system. This is a localization override. This means that if there is a valid locale entered in this text field then it will negate any other language localization attempts for users reaching the BI System from another language location.
      • Default: EN-US
      • A valid two (ex: EN) or five code (ex: EN-US) locale is required.
        If desiring the localization of key terms and messages from the BITeamwork Collaborative BI plug-in to be translated then leave this field blank.
  • Scratch / Temp Dir:
    • This is a directory on the BI System (where BITeamwork is also deployed) which may be accessed to read and write temporary files.
      • An icon to the left of the field indicates whether or not the location is accessible. If the icon is red then the location is either not found on the server or proper read/write permissions are not set. If the icon is green then the location is accessible.
        On a Linux Operating System all paths should start the reference to this physical location with the root directory forward slash (/). On a Windows Operation System use the full drive letter path with the standard back slash (\). After entering the path and saving the form you must refresh the page in order for the icon to change color indicating the accessibility of the directory location entered.
      • Default: /tmp
  • FMW HOME Dir:
    • In Oracle BI this location is the Fusion Middleware (FMW) Home directory in which the BI System is installed. Common folders inside of this directory are /user_projects, /Oracle_BI1, and /instances.
      • Do NOT use a trailing slash for the directory
      • An icon to the left of the field indicates whether or not the location is accessible after the form has been saved and this page refreshed. If the icon is red then the location is either not found on the server or proper read/write permissions are not set. If the icon is green then the location is accessible.
        On a Linux Operating System all paths should start the reference to this physical location with the root directory forward slash (/). On a Windows Operation System use the full drive letter path with the standard back slash (\). After entering the path and saving the form you must refresh the page in order for the icon to change color indicating the accessibility of the directory location entered.
      • Example: C:\Oracle\FMW or /var/Middleware
      • Default: /u01/fmw
  • OBI Domain Dir:
    • In Oracle BI this the location of the domain directory in which the BI System is installed. This is different usually from the FMW HOME Dir, especially when the WebLogic Best Practices for High-Availability have been incorporated for the Oracle BI Architecture. The path for this folder structure may appear as follows, /app/bimw/mserver/binst1.
      Leave this field blank if you are using a standard OBIEE configuration where the FMW HOME Directory path is the default.
      • Do NOT use a trailing slash for the directory
      • An icon to the left of the field indicates whether or not the location is accessible after the form has been saved and this page refreshed. If the icon is red then the location is either not found on the server or proper read/write permissions are not set. If the icon is green then the location is accessible.
        On a Linux Operating System all paths should start the reference to this physical location with the root directory forward slash (/). On a Windows Operation System use the full drive letter path with the standard back slash (\). After entering the path and saving the form you must refresh the page in order for the icon to change color indicating the accessibility of the directory location entered.
      • Example: C:\Oracle\FMW\user_projects\domains\bifoundation_domain
      • Default:
  • Cluster Instances:
    • Enter instances by name residing in the BI System architecture separated by a colon (:).
      • This provides BITeamwork with an understanding of the scaling of the BI System and also provides the logic for the dropdown options when viewing the configuration files manager in the BITeamwork Control Panel.
    • Example: inst1 or instance1 or biinst1
    • Default: instance1:instance2
    • Example: instance1:instance2, or instance2:instance3:instance4, or instance1
  • Environment URI:
    • Creates a single point of entry to your OBIEE system for referencing comments and other bookmarks for links. This URI will be prepended (i.e.: prefixed) to links automatically in order to provide a consistent collaboration link reference.
    • Default:
    • Example: http://obi.mycompany.uk.com:9704, or https://192.168.1.190. or https://secureobi.obiprod.altrex.com

Figure server_app_info_4
  • Admin Page Window'd:
    • This option provides the ability to modify the default options of the Oracle BI Administration link for any administrators of the BI System. By setting this value to True, once the page is refreshed, all subsequent clicks on the Administration link in the Oracle BI Global Header will open the Administration page in a new pop-up window. This is similar to the default operation in the legacy version of Oracle BI, Oracle BI 10g.
      • Default value is: False
  • Show Sketch:
    • Determines if the Sketch option is visible to users having access to the BITeamwork collaboration pane when viewing a dashboard. The sketch option is the option which allows a user to mark the screen with an overlay which is toggled via the marker icon .
      • Default value is: True
  • Show Homepage VoteUp:
    • Determines if the OBIEE Home page will show the "Most Voted Comments" section to users as they access this page.
      • Default value is: True
  • Mobile Device Capable:
    • Determines if the BITeamwork commenting functionality will be available on the Oracle BI Mobile applications.
      • Default value is: True
  • SideBar Initial Position:
    • Determines if the BITeamwork sidebar collaboration pane will render at the bottom of the BI portal in a collapsed "Minimized" position when a user first enters the BI system after BITeamwork has been installed or another position as dictated by the drop-down options.
      • Default value is: Full/Open
  • Min/Max Comment Length:
    • Determines the smallest to largest number of characters range that can be entered in a comment field when authoring a comment or cell annotation.
      • Default value is: 6 and 2000
      This feature is very important in non-latin language such as Chinese where a single character could have the same meaning as a full sentence in English.
  • Max Dashboard Doc Length:
    • Determines the largest number of characters that can be entered in a dynamic dashboard document comment field when authoring a special type of inline cell comment called a dynamic dashboard document.
      • Default value is: 20000
  • Inline Comment Logic Delimiter:
    • The delimiter that will be used to correctly parse user created attributes and other Inline Cell Commentary (ILC) BITeamwork API options and values. We recommend leaving this to a pipe (|) by default but if it must be changed for any reason, please conduct thorough testing before going into production with a modification.
      • Default value is: |
  • Use Advanced Editor:
    • Determines if the comment field used when authoring comments is a simple text box or a robust rich HTML editing form field. When set to True the rich HTML editor is used.
      • Default value is True
  • Allow Comment Editing:
    • Determines if comments may be edited globally. This is a global override setting. So, if security privileges are given to a user or application role allowing them to edit or set edit permissions on a comment, this setting will either allow those edit permissions to continue or prevent them entirely.
      • Default value is True
  • Auto Populate Pred Matrix:
    • Predicate Matrix is a table that captures the specific prompt values when a comment is created (i.e.: per comment transaction). Each prompt having a value becomes one record in this BITeamwork repository schema table which can later be used for reporting and commentary aggregation. If set to false, the population or inserting of records in this repository schema table will cease.
      • Default value is True
  • Capture Cell Commentary History:
    • When a cell annotation or inline cell comment is created, it is stored as a single transaction in the analysis cell commentary table in the BITeamwork repository. Particularly in the case of an inline cell comment (ILC), if a user updates the comment, regardless the ownership of the comment, the comment is overwritten and the previous comment not necessarily visible any longer. If this option is set to true, the updated recorded is stored as history as a historical record in a single transaction as a row in the analysis cell history table of the BITeamwork repository. This provides the ability to always find or retrieve the previous record's information or potentially even restore an overwritten comment.
      • Default value is False

Figure server_app_info_4
  • Mobile BI XML Config:
    • Field for containing the OBIEE Mobile BI XML script which will enable end-user Mobile Devices to automatically be configured with your organization's OBIEE server access.
      • Default value is: blank
    • Example: Mobile BI Deploy Config Syntax
  • Mobile BI Launch Page URI:
    • The link that you will use to provide your organization's OBIEE Mobile application users in order to gain access to the Mobile BI configuration link for your OBIEE servers.
      • Default value is: http[s]:<servername>/bitw/x/mobilebi/a/29894849/v2
  • SmartView Provider XML:
    • XML syntax for SmartView and the Hyperion Provider logic to supply end-users with a central point for referencing all hyperion and OBIEE based access points for SmartView. Set it once here and have the end-users configure their SmartView provider to this location for access to all possible servers you wish to give access for querying or inputs.
      • Default value is: blank
    • Example: Mobile BI Deploy Config Syntax
  • SmartView Provider XML:
    • The link that you will use to provide your organization's SmartView users.
      • Default value : http[s]:<servername>/bitw/x/smartview/a/29894849/all/vCurrent.xml
  • Comments Editable by Default:
    • Determines if comments are editable by default. That is once, a comment is created is its text editable after submission or does the author have to declare as editable after it is created.
    • Default value : True
  • Bulk Save Capable:
    • Determines if the bulk save feature for Inline Cell Comments is possible or active. Bulk save is not available in the 3.x versions of BITeamwork.
    • Default value : True
  • Auto Save Capable:
    • Determines if the auto save feature for Inline Cell Comments is possible or active.
    • Default value: True
  • Sync All Web Catalog Users:
    • Historical reference to whether Web Catalog Users will be automatically loaded when syncing application roles. Currently there is a secondary option in the Sync Manager which allows for users and application roles to be independently sync'd.
    • Default value : false
  • Application Active:
    • Default value is True ( There is no other option for shutting off the entire BITeamwork application in the current release.)
  • Export App Config Settings:
    • Provides the ability for the BI Administrator to export the BITeamwork Application Configuration settings found on this page. It is a soft backup of the values of each field on the Application Configuration page.
  • Attribute #1:
    • TBD and Support Usage Only.
  • Attribute #3:
    • TBD and Support Usage Only.

Figure server_app_info_6
  • Advanced Print URI:
    • If using the special advanced print functionality which must be additionally configured using a a third-party plug-in and dependent on specific server builds.
      This configuration is only recommended in special circumstances. And, mainly not necessary for OBIEE 12c.
      See document, BITeamwork 3.0 "Advanced Printing" Configuration
      • Default value is: [Empty]
  • Page to PDF Options:
    • Printing a view or a dashboard page as an image is possible via BITeamwork. However, not all users need such a feature when the ability to print to PDF is attainable with ease. The BITeamwork Administrator may set this to false to prevent users from printing to images.
      • Default value is: Show Only Page to PDF
      • Show Only Page to PDF - Default option. Will show only the page to PDF options
      • Show Only Page to PDF Template - Will show only the page to PDF Template option
      • Show Both Page to PDF Options - Will show both the aforementioned options.
  • Advanced Print Active:
    • Determines if the advanced print functionality and options are active. Advanced Print uses the PhantomJS configuration which is best used in a Windows OS, however it also works in standard RHEL Linux OS and Oracle Linux OS environments. Advanced Print provides a headless browser capability which gives the BITeamwork system via WebLogic the ability to capture an OBIEE window dashboard page with commentary and any other HTML logic. Then it is rendered as a PDF. Please contact support if desiring to use this functionality.
      • Default value is: False
  • Show Print as Image:
    • Printing a view or a dashboard page as an image is possible via BITeamwork. However, not all users need such a feature when the ability to print to PDF is attainable with ease. The BITeamwork Administrator may set this to false to prevent users from printing to images.
      • Default value is: True
  • Ancillary configuration:
    • Holds information about extra configuration options for BITeamwork or other plug-in functionality
      This file (JSON) system of setting variables is advanced and done specifically to give BITeamwork flexibility to support one-off patches, temporary solutions, and near endless adjustments to the BITeamwork application without being locked in to a rigid structure of configuration settings.

      This is pure JSON syntax that is verified once the "Save" button is pressed. The value must start with an open bracket and end with a close bracket.
      Additionally the structure and available values are released by BITeamwork develop and either provided here or in the support portal for documentation.

      • Default value is: {}
      • Other Values:
        { "name":"BITWControlOptions", "showAnswersBITWILCInstructions":false, "showAnswersBITWHeader":true, "showAnswersBITWMDSubjectAreaHeader":true, "answersBITWMDActive":true }

As an insightful feature, BITeamwork pulls metadata and JVM stats from the server on which the BI Server Application is hosted. Clicking on the Server Information link on the left panel of the BITeamwork Management Console will show the Server Information metadata, the version of BITeamwork currently deployed to the BI Server, and more.


Figure server_info_1

Setting Logging Level

As a means to provide extra data and logging information to support issues/tickets, the Logging Level option within the Server Information area give your BITeamwork Administrator a filter for the flow of data capture in the log files.

  • Setting Logging Levels:
    • Click the Server Information option from the left menu in the BITeamwork Control Panel.
    • Select an option from the Log Level drop-down menu:
      • WARN - Default option. This should be the normally selected option in a dev,test, or production environment.
      • DEBUG - Option which collects the most information for the BITeamwork application. Turn on only during sandbox or development testing. Revert to WARN when not needing to track low level details.
      • OFF - Use potentially for a production implementation. Usually keeping at WARN provides high-level logging information even in production.
    • Click the Save button to confirm the change.

Figure server_info_2

BITeamwork allows administrators to control several core OBIEE configuration files. These files known simply by their names, NQSConfig.INI and InstanceConifg.xml are available for reading and writing through this interface.

NOTE: The Application Manager "FMW HOME Dir" setting must be correctly configured prior to view any configuration files.

BITeamwork provides this functionality without requiring the BI Administrators to log into a terminal window or using an FTP system to access these files. The editor highlights the syntax of the file showing specific context to an INI file, XML file, etc.

Prior to BITeamwork 3.0 the configuration files were read-only but after that release full read/write control is enabled.


Figure config_files_1

Select and Edit a Configuration File

BI Administrators can read, review, and write to the configuration files where the "Update" option is available. Upon updating a write to the configuration file, BITeamwork first makes a backup of the configuration file with appropriate timestamps and then overwrites the file with the edit you are making via the update. A backup file will always exist but your updated file becomes the primary file in the server location where the file resides. You will need to restart the BI Services manually for any updates or changes to take affect per the normal instructions of the BI system.

  1. Click the Configuration Files link from the side menu of the BITeamwork Control Panel
  2. Select an instance from the Select Instance drop-down options
  3. Click on the configuration file link that you desire to read or editorial. For example: NQSConfig.INI
  4. Review the content and make an edit if desired.
  5. If making and edit, Click the Update button.
  6. Acknowledge any prompts confirming the update execution being made.
  7. Done. You may review the update by refreshing the page or using a S/FTP or SSH system to check the updated file on the server.

BITeamwork now gives administrators functionality to deploy the configured Oracle BI systems to hundreds of mobile BI uses at once. By providing a central location for Mobile BI users to access the Oracle BI server configurations established for the company, users will access the link via their mobile devices and the Oracle Mobile BI application will automatically configure itself.


Prerequisite

In order to achieve this you will need to have BITeamwork 3.0+ installed and have either installed on your mobile phone or tablet the:


Template XML Configuration

We make use of the Oracle BI Mobile configuration XML logic and update the corresponding area of the BITeamwork interface. This allows an administrator to edit the base configuration with your Company’s Oracle BI server infrastructure access information in the XML logic, save the logic within BITeamwork, and the configuration will automatically be accessible to hundreds of users once you provide the BITeamwork access URL to them via email or other means of access. Here is the basic XML template from which we may start making the configuration adjustments. An example configuration for you to emulate for learning purposes is seen in the section below the configuration steps. This template immediately below is an approved configuration structure for the Oracle BI Mobile application which contains two Oracle BI server configurations. You may read more about the structure here, http://www.oracle.com/technetwork/middleware/bi/documentation/bieqj-2284016.pdf

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>obim</key>
<dict>
<key>servers</key>
<array>
<dict>
<!-- Analytics Web App Context Path -->
<key>analyticsPath</key>
<string>/analytics/saw.dll</string>
<!-- Machine Name including Domain or IP address -->
<key>host</key>
<string>192.168.1.32</string>
<!-- Use Device Locale -->
<key>locale</key>
<true/>
<!-- Configuration name, any name-->
<key>name</key>
<string>ArtOfBI SampleApp v406</string>
<!-- Analytics Web App Port -->
<key>port</key>
<integer>7780</integer>
<!-- use this server as default -->
<key>selected</key>
<true/>
<!-- enable SSL -->
<key>ssl</key>
<false/>
<!-- enable SSO -->
<key>sso</key>
<false/>
<!-- Publisher Web App Context Path -->
<key>xmlpPath</key>
<string>/xmlpserver</string>
</dict>
<dict>
<!-- Analytics Web App Context Path -->
<key>analyticsPath</key>
<string>/analytics/saw.dll</string>
<!-- Machine Name including Domain or IP address -->
<key>host</key>
<string>192.168.1.38</string>
<!-- Use Device Locale -->
<key>locale</key>
<true/>
<!-- Configuration name, any name-->
<key>name</key>
<string>ArtOfBI Config1</string>
<!-- Analytics Web App Port -->
<key>port</key>
<integer>9704</integer>
<!-- use this server as default -->
<key>selected</key>
<true/>
<!-- enable SSL -->
<key>ssl</key>
<true/>
<!-- enable SSO -->
<key>sso</key>
<true/>
<!-- Publisher Web App Context Path -->
<key>xmlpPath</key>
<string>/xmlpserver</string>
</dict>
</array>
<key>version</key>
<string>11.1.1.6.0</string>
</dict>
</dict>
</plist>

Configuration Steps

The steps below walk through an example configuration and how-to setup for the Oracle BI Mobile configuration access point

  1. Access the BITeamwork control panel

  2. Click on the Application Manager link on the left side of the control panel

  3. In the Application Configuration Manager area click on the Advanced Configuration section to expose the Mobile BI XML Config option:


    Figure server_app_info_2


  1. Open your favorite notepad editor (such as notepad++, textedit, or plain ‘ol notepad) on your workstation then copy the XML template above and paste it into a new document for editing.


    Based on the structure it should be immediately apparent that this is a key/value configuration script. Each Oracle BI server that you wish to configure as part of your automated configuration deployment to end users will be listed between a <dict></dict> tag. multiple <dict></dict> tags can be created as siblings of each other by specifying the properties for each OBIEE server by adjusting the tags in between.


    Each value between the <key></key> tags are default structural tags required by the configuration XML. The tag immediately below each <key></key> tag is the value associated with that key attribute. For example,

    <key>port</key>

    <integer>9704</integer>

    represents the port attribute of the Oracle BI Server where the application presentation layer is running. The tag for the attribute value in this case is listed as “integer”, other attribute value tags are “string” and for a boolean (true or false) the tag is simply the boolean value listed as <true/> or <false/>.


  1. Modify the Oracle BI server properties section under the first <dict></dict> tag and change the values to correspond with your server. You will need to modify all the attribute values as it relates to your Oracle BI Servers. We recommend only updating the first section with the attributes for your development or sandbox environment. Preferably an environment that is easy to test such as one that is not secured by SSL or SSO until you’ve successfully established a connection to an Oracle BI server with a plain configuration.

  1. Modify the host, name, and port <key> tags. Change:

    1. 192.168.1.32 to the server name or IP for one of your OBIEE instances.

      1. Do not include HTTP or HTTPS

      2. If using the server name just enter bi.companyxyz.com but not http://bi.companyxyz.com

    2. ArtOfBI SampleApp v406 to any alias name you would like to show your end users in the configuration list. For example, Oracle BI Production or TEST BI SERVER

    3. 7780 to the port number for which you are accessing the instance of the BI Server you are configuring. For example, 9704.

      1. If there is no port number shown in the browser address bar when you are accessing the Oracle BI dashboards then you would use enter 80, which is the default HTTP web server default.

  2. Copy the text within the text editor containing your changes above.

  3. Paste the copied text into the Mobile BI XML Config field

  1. Click the “Save” button to save your changes.

  2. Now provide the following link to your users via email or via a intranet portal page for them to access. The link to be provided is:

    1. http[s]://<servername>/bitw/x/mobilebi/a/29894849/v2

  3. Modify the link above so that it references your key Oracle BI implementation on which BITeamwork is now installed. For example use HTTPS only if your Oracle BI server will be secured via SSL, otherwise use HTTP. Change the URL and replace the <servername> placehoder with the name or IP of your server. For example, if testing this version of BITeamwork in your sandbox or development environment with IP address 192.168.1.11 running OBIEE on default port 9704 then the URL to provide your end users becomes, http://192.168.1.11:9704/bitw/x/mobilebi/a/29894849/v2

  4. Navigate to the URL you’ve configured in the previous step using the browser on your desktop workstation to ensure that you’ve entered it correctly.


    Figure server_app_info_4

    This is the access page URL you will provide your Mobile BI users. The users will then click on the link present in this URL page while accessing the URL via their mobile devices. Once they click on the link, if the Oracle BI Mobile application is installed on their device, all server configurations you established in the XML configuration file will be added to the users’ list of available OBIEE servers which are available to them on their network. Users will still be required to enter and save their credentials but all server configuration information will be immediate visible on their mobile device.

  1. Test on your mobile device and confirm the alias of the OBIEE server your configured in the XML script above is now visible for the first time in your list of available servers on your mobile device.

OBIEE and Hyperion administrators can further integrate the two systems through a SmartView configuration called SmartView Providers. The BITeamwork interface and functionality is called SmartView Provider Management. This functionality provides a single configuration place for allowing a central point for which SmartView clients can reference in order to have all required curated connections available. Administrators then have the ability to add or remove a connection from the centralized SmartView Provide Management system having changes made take effect in real-time.


Procedure for Setting up SmartView Providers

In to use SmartView Provider Management (requires version BITeamwork 3.8.5+):

  1. Open the BITeamwork Control Panel
  2. Click the Application Manager from the left side of the control panel
  3. Expand Advanced Configuration
  4. Edit the SmartView Provider XML text area with the full XML syntax for the SmartView Provider connections you wish to have
  5. Ensure the SmartView Provider XML text area is complete with your XML content desired
  6. Click the Save button to save your edits
  7. Click on the link underneath the SmartView Provider XML text area, SmartView Provider URI having the .../vCurrent.xml text as the suffix in the link

Figure svprovider_1

Configure Microsoft Office with BITeamwork SmartView Provider Management

After the BITeamwork SmartView Provider XML text area has been configured and tested by the administrator, and the SmartView Provider URI (../vCurrent.xml) link has been assessed , the steps below will walk you through configuring SmartView in Microsoft Office using the BITeamwork SmartView Provider Management reference.

  1. Obtain the BITeamwork SmartView Provider Management link from the administrator
  2. Open a SmartView Microsoft Office compatible application such as Excel, Word, or PowerPoint
  3. Click on the SmartView tab/ribbon
  4. Click on the Options button in the ribbon
  5. Pase the provided BITeamwork SmartView Provider Management reference link (../vCurrent.xml) in the Shared Connections URL textfield/dropdown area
  6. Click the OK button to confirm your change
  7. Click on the Panel button from the ribbon to open the vertical panel for connections that appears on the right of the application
  8. Click on the Shared Connections button in the smartview panel
  9. Click the dropdown menu arrow to reveal the connections from the centrally managed smartview provider connections
  10. Select a connection to begin your connection to the Hyperion/OBIEE data source.

Watch the SmartView Connection Provider Video

Example of a Hyperion and OBIEE SmartView Provider List


<?xml version="1.0" encoding="UTF-8"?>
<res_GetProvisionedDataSources><Product id="Oracle Essbase - DEV" name="APS-11.1.2.2" displayVersion="version">
<Server name="Oracle Essbase - DEV" context="http://DEV:19000/aps/SmartView"></Server>
</Product>
<Product id="HP" name="HP-11.1.2.2" displayVersion="version">
<Server name="Oracle Hyperion Planning, Fusion Edition - DEV" context="http://DEV:19000/HyperionPlanning/SmartView"></Server>
</Product>
<Product id="RAFramework" name="RAFramework-11.1.2.2" displayVersion="version">
<Server name="Reporting and Analysis Framework - DEV" context="http://DEV:19000/raframework/browse/listXML"></Server>
</Product>
<Product id="Oracle Essbase - QA" name="APS-11.1.2.2" displayVersion="version">
<Server name="Oracle Essbase - QA" context="http://QA:19000/aps/SmartView"></Server>
</Product>
<Product id="HP" name="HP-11.1.2.2" displayVersion="version">
<Server name="Oracle Hyperion Planning, Fusion Edition - QA" context="http://QA:19000/HyperionPlanning/SmartView"></Server>
</Product>
<Product id="RAFramework" name="RAFramework-11.1.2.2" displayVersion="version">
<Server name="Reporting and Analysis Framework - QA" context="http://QA:19000/raframework/browse/listXML"></Server>
</Product>
<Product id="Oracle Essbase - Prod" name="APS-11.1.2.2" displayVersion="version">
<Server name="Oracle Essbase - Prod" context="http://Prod:19000/aps/SmartView"></Server>
</Product>
<Product id="HP" name="HP-11.1.2.2" displayVersion="version">
<Server name="Oracle Hyperion Planning, Fusion Edition - Prod" context="http://Prod:19000/HyperionPlanning/SmartView"></Server>
</Product>
<Product id="RAFramework" name="RAFramework-11.1.2.2" displayVersion="version">
<Server name="Reporting and Analysis Framework - Prod" context="http://Prod:19000/raframework/browse/listXML"></Server>
</Product>
<Product id="Oracle Essbase - Local" name="APS-11.1.2.3" displayVersion="version">
<Server name="Oracle Essbase - Local" context="http://myserver:9000/aps/SmartView"></Server>
</Product>
<Product id="HP" name="HP-11.1.2.3" displayVersion="version">
<Server name="Oracle Hyperion Planning, Fusion Edition - Local" context="http://myserver:9000/HyperionPlanning/SmartView"></Server>
</Product>
<Product id="RAFramework" name="RAFramework-11.1.2.3" displayVersion="version">
<Server name="Reporting and Analysis Framework - Local" context="http://myserver:9000/raframework/browse/listXML"></Server>
</Product>
</res_GetProvisionedDataSources>

                        
                        

The web page which can be shown as a pre-reference page for SmartView end users.


Figure svprovider_2

The link reference provided to the SmartView end users.


Figure svprovider_3

The Support section within the BITeamwork Management Console provides information on how and where to submit product enhancements, support tickets, and access BITeamwork forums. Clicking on the Support link in the left navigation area of the BITeamwork Management Console shows this information. All support and maintenance is a conducted in accordance to our Maintenance and Support Service Level Agreement.


Figure support_1