Planning Your Multiuser Development Deployment

Review the tasks you need to perform as part of the planning phase before beginning multiuser development.

This section contains the following topics:

About Business Organization and Governance Process Best Practices

You need to provide a strong, effective governance process to make decisions about shared resources and to resolve conflicts among the many stake-holders.

As in any business process, you must have a strong business sponsor, and the steering committee must be staffed with strong business people who can negotiate effectively and make good decisions that will not change over time. Having an effective governance process has proven to be the single most important factor in achieving successful multiuser development with Oracle Business Intelligence.

Before you begin your multiuser development project, you must first lay out the business value, priorities, roadmap, and requirements, as well as lower level details of the design, as described in the table below.

Task Description

Strategic requirements

  • Determine which business processes to measure

  • Determine which data sources and subject areas to access

Business requirements for repository objects

  • Select and define metrics, dimensions, and hierarchies

  • Identify objects that will be shared between development teams

  • Resolve conflicts between teams

  • Define Presentation layer subject areas

Security requirements

  • Define Application Roles and corresponding privileges for your user base

  • Define which repository developers can access which metadata and data


  • Determine the styles of multiuser development to use

  • Define areas to break down into MUD projects

  • Determine the owners for metadata objects

Project management

  • Set initiatives - purpose, goals, requirements, scope, schedule, budget

  • Define phases - scope, schedule

  • Allocate resources - hardware, software, databases, developers

  • Decide on a strategy for development branching

  • Prioritize and schedule production updates from different development teams


  • Negotiate service level agreements

  • Coordinate schedules for updates and downtime

About Technical Team Roles and Responsibilities

These topics describe the hands-on roles involved in repository development and its lifecycle.

Depending on the size of your company and team, some of these roles might be served by one person.

Repository development roles include:

  • MUD administrator, one for each development team, plus backup

    • Assigns repository password

    • Sets up and maintains MUD projects

    • Manages the master repository shared directories

    • Manages branches and branch merges

    • Manages repository migrations

    • Manages test and production connection pools

    • Manages independent semantic models, has metadata read/write privileges for all models

  • Repository developer, many per development team

    • Knows the repository password

    • Owns, operates, and maintains a personal development sandbox that includes all necessary Oracle Business Intelligence components

    • Manages user and application role provisioning on their sandbox stack

    • Creates functional and data authorization content in the repository

    • Performs unit testing

    • Performs check-outs, merges, and publishing, as required

  • Production Operations staff

    • Knows the repository password, for managing connection pools and applying patches

    • Applies updated repositories, and applies XML patch updates to the running BI Server's repository

    • Can log in to production computers and read/write the Oracle Business Intelligence directories or run programs

    • Manages the production file system, including the repository directory, logs, and configuration files

    • Manages the production servers including the Administration Server, Managed Servers with Java components, and Oracle Business Intelligence system components like Oracle BI Server and Oracle BI Presentation Services

    • Manages production security, including provisioning users, groups, and application roles

    • Manages and migrates application roles in production

    • Manages production connection pools, in the case where the MUD administrator does not have security privileges for production connection information

People in other roles outside the repository development team are also involved. These include people administering the test environment and running the tests, and also the Oracle BI Presentation Catalog developers.