1. Download It

2. Move the BITeamwork zip file to the Server and decompress

3. Create the BITeamwork DB Schema (Just like MDS & BIPLATFORM)

4. Edit the BITeamwork Deployment Script

5. Execute the BITeamwork Deployment Script

6. Complete Post-Installation Configuration Steps

Done!

  1. Download the Software
  2. S/FTP or move the downloaded compressed file to the Oracle BI 11g or 12c Server
  3. Copy the compressed file to a temporary drive (ex: C:\tmp or /tmp) and extract the file's contents
  4. Navigate to the BITeamwork_<version#> folder
  5. Expand the folders InstallFiles > DB > Scripts and then choose the folder of the database vendor you will use to store the BITeamwork metadata, i.e.: Oracle or SQLServer.

    NOTE: Choose whichever database vendor works for your organization. Running the initial vendor dependent SQL scripts (next step) is the only part that creates a variation in the BITeamwork install process.

  6. Execute the two SQL Scripts using your favorite Oracle or SQL Server Management IDE (ex: SQLDeveloper or Management Studio) to create the BITEAMWORK repository schema and to populate the schema objects. Execute the files using the order below:
    • 1) Execute W_CREATE_BITEAMWORK_USER.sql or 1_CREATE_BITEAMWORK_USER_MSSQLSERVER.sql
    • 2) Execute X_BITEAMWORK_BUILD_SCHEMA.sql or 2_BITEAMWORK_BUILD_SCHEMA_MSSQLSERVER.sql
    • Only if you are upgrading from previous BITeamwork version using an Oracle database schema:
      • Execute any Z_BITEAMWORK_.....sql
      • If you experience any problems because you've executed this script then drop the schema and re-build with only the X_BITEAMWORK_BUILD_SCHEMA.sql script and do not run the Z_BITEAMWORK..sql scripts any more
    • You may potentially need your DBA to create the BITEAMWORK schema so provide her with the W_CREATE_BITEAMWORK_USER.sql script.
    • Connect then to the newly created BITEAMWORK (i.e.: BITEAMWORK_OBI) schema and execute the X_BITEAMWORK_BUILD_SCHEMA.sql script, as well as any Z_BITeamwork...sql scripts available if conducting an UPGRADE of BITEAMWORK.
  7. If updating, upgrading, or patching an existing version of BITeamwork, execute the SQL scripts that reflect your closest SQL version and all of the additional scripts available in the directory. You may receive warning messages stating that some objects already exists.
    • During an upgrade you should always run a diff or compare using the latest X_BITEAMWORK_BUILD_SCHEMA.sql and your current db repository that was patched as the X_BITEAMWORK_BUILD_SCHEMA.sql will always be the most accurate of the current state of the current release repository.
  8. In the BITeamwork_<version#> folder root, edit the installBITeamwork.[bat|sh] file
    • (Right-click > Edit , if using a Windows OS; Use VIM Editor on *Nix)

    Warning! Pre-Requisite

    Be certain that the Oracle BI environment on which you are installing BITeamwork is currently running and active. The WebLogic Server should be running and available for access and MUST NOT be in Lock & Edit mode (i.e.: Release Configuration).
    • Locate the section labeled Set env variables and UPDATE beneath the file description header when editing the installBITeamwork.[bat|sh] file.

      If using a *Nix OS, you may also need to run the dos2unix command on the installBITeamwork.sh and the /installFiles/createDSandDeploy.py files. You may also need to run the command chmod a+x installBITeamwork.sh to give the script executable rights.

    • Edit the following variables to reflect your Oracle BI environment:
      • OBIEE_FMW_HOME
      • OBIEE_IS_SIMPLE_INSTALL

        If OBIEE 12c, then leave as the default, 0.
        If OBIEE 11g, this will typically be 0 (Default), unless you know for certain that you installed a simple installation, usually done in legacy 11g sandbox environments. In a simple install the /analytics server is usually accessible with the following url on port 7001 instead of 9704, http://<server_name>:7001/analytics

      • OBIEE_BASE_VERSION

        The default value is for any version of OBIEE 11.1.1.6.x as noted by the simple integer 11116. If installing on OBIEE 11.1.1.7.0, change the value to 11117, OBIEE 11.1.1.7.1, change the value to 111171, etc. Try to use the value most representative of your installation of OBIEE. In BITeamwork 3.0, the latest, 1111714xxx, 1111715xxx, 11119, 122100 options were introduced. You may use this as well if you have confirmed that your version of OBIEE is certified with BITeamwork and not other specific option matches your version. Hotfix versions should select the closest matching version option.

      • WEBLOGIC_URL

        The default value here t3://localhost:7001 will work for 99.8% of all installations. If your implementation port has changed from the default 7001 then make the adjustment accordingly.

        REMEMBER: t3:// is the WebLogic Server Protocol. Do NOT change this protocol to HTTP!

      • WEBLOGIC_USERNAME
      • WEBLOGIC_PASSWORD
      • DB_VENDOR

        The default value is set for an Oracle RDBMS as ORACLE. If using MS SQL Server change the value to SQLSERVER.

      • DB_SCHEME_USER_FOR_APP
      • DB_SCHEME_USER_PASSWORD_FOR_APP
      • DB_DRIVER

        NOTE: If using the Oracle BI SampleApp Linux Virtual Machine Image or simply an Oracle Database, the string should appear as oracle.jdbc.OracleDriver
        NOTE: If using a MS SQL Server database as the metadata repository for BITeamwork uncomment the SQL Server Connection Configuration information and comment out the Oracle RDBMS Connection Configuration.

      • DB_URL

        NOTE: If using the Oracle BI SampleApp Linux Virtual Machine Image the string should appear with the service name, for example jdbc:oracle:thin:@localhost:1521/orcl.us.oracle.com or similar depending on the SampleApp version. See this blog post for more information on the difference between connection string types.

        NOTE: If using a MS SQL Server database as the metadata repository for BITeamwork uncomment the SQL Server Connection Configuration information and comment out the Oracle RDBMS Connection Configuration.

      • TEMP_DIR
        • This is a location of a file on the server with temporary space the installation may use for saving configuration files during installation. Required free space ~50MB.
    • Save the file.

    Warning! Simple Installation Type for Oracle BI 11g

    If you are running a demonstration environment based on the Oracle BI 11g "Simple" Installation, you must set the OBIEE_IS_SIMPLE_INSTALL variable in the installBITeamwork.[bat|sh] file to a value of 1 by changing the default value of 0.
  9. Open a command prompt or terminal window and execute the installBITeamwork.[bat|sh] script.
  10. Restart the Oracle BI System Components
    • Open a command prompt or terminal.
    • Navigate to the BI_INSTANCE/bin directory, ex: C:\Oracle\FMW\instances\instance1\bin\
    • Execute the following commands at the prompt:
      • opmnctl stopall
      • opmnctl startall
  11. Open Oracle BI in a new browser. Login and navigate to the Administration page to see the new BITeamwork Administration layout to validate BITeamwork was installed correctly.
  12. Done with the Installation of BITeamwork - Let's move to configuration!
  13. Configuration Steps (Watch the Video)

Next: Post-Installation Configuration Steps

  1. Login to the Oracle BI System and access the BI Administration Page
  2. Configure the Web Services
  3. Sync the Application Roles
  4. Set the Application Manager Directories
  5. Assign any user Security

Check out the Installation Videos and have fun collaborating with BITeamwork.

Provide feedback when you can on our forums.

Linux Installation

Windows Installation

Post-Installation (Required for full functionality)