LCM Implementation

We strongly recommend that the initial setup of LCM on your site involve or be done by GoodData specialists. For more information, contact GoodData Support.

Contents:

Implementation Process

The following is the process that the GoodData specialists follow to implement LCM on your site. The implementation is done using the specific bricks (see Bricks).

  1. Initial setup. Based on a predefined template called 'Development master workspace', master workspaces are created for segments. If the segments do not yet exist, they are created as well.
    Brick involved: Release brick
  2. Client provisioning. Clients and their workspaces are created under the appropriate segments. The reports, dashboards, filters, logical data model (LDM), ETL and metadata are deployed from the master workspace to the clients' workspaces within a segment. Obsolete clients and their workspaces are removed.
    Brick involved: Provisioning brick
  3. Synchronization / Release management. The segments' master workspaces and their clients' workspaces are synchronized by propagating the changes that you made in a master workspace (LDM, ETL, dashboards, and so on) to all the clients' workspaces within the corresponding segment.
    Brick involved: Rollout brick
  4. (Optional) User configuration. Users are added to the domain. Users are added/removed to/from a workspace. A user's information and/or role is updated.
    Brick involved: Users brick
  5. (Optional) User filter configuration. User access to the data in a workspace is configured based on data filters.
    Brick involved: User filters brick

This process is the recommended method for managing projects via LCM.

Brick Configuration

For the initial setup, GoodData specialists configure the bricks for you.

So that the GoodData specialists can configure the bricks properly, they will ask you to prepare input data for the bricks and store it in one of the following locations:

The input data should be stored in the CSV format (when located on the staging area, Amazon S3 bucket or web) or be accessible via a query to Data Warehouse (when located in Data Warehouse).

For information about what input data should look like for each brick, see the corresponding section under Bricks.