Your Browser is Out of Date

ShareDemos uses technology that works best in other browsers.
For a full experience use one of the browsers below
Modern Data Management with Boomi Accelerates Business Outcomes
Use case
Introduction Overview Starting point Boomi capabilities used Data sources and data stores Users and groups Exploring data sets Use case workloads Schedule a job RESTful API example

Data sources and data stores

  • Most large enterprise systems that are accessed through DCP have multiple collections of data objects. There must be a mapping between DCP and the data store to control outside access. The first level of defining a data connection is an adapter. Adapters are source-specific connectors that are developed for the product and distributed with the software.

    An adapter must be enabled and configured before creating any higher-level data access objects. Boomi uses three additional object levels for data access control:

    • Data stores
    • Data sources
    • Data sets

    An adapter serves as a connecting code that enables DCP to communicate with the data store. To make a data store available to users, a Boomi administrator (or someone with equivalent privileges) uses the Data Stores page to add an external data location to the Boomi system. This location is a pointer to the location of the data and includes items like the machine name, and on what network port it is accessible. To access the pages listing the defined stores and sources in the system:

    1. Click the Tools > Manage menu.
    2. Select either Data Stores or Data Sources.

    Data stores

    Data stores are locations of data, such as:

    • Databases
    • Files located in various types of file systems
    • Other such items

    See Data stores.

    Figure 1. Data stores
    Data stores

    Data sources

    Data sources are definitions of a service, database, or file that is accessible by certain users. A definition includes any credentials that are required to access the data store, and which Boomi DCP users can see and use it. The definition is also where you establish whether the data source can also be a data sink, or writable repository. Having predefined users and groups with permissions before this step simplifies the creation of the data source. It is possible to define, on a per-column basis, who can see what portion of the data. See Data sources.

    Figure 2. Data sources
    Data sources

    Data sets

    A data set is a subset of data from a data source. DCP users work with datasets to explore the available data, and to configure transform jobs.

    Permissions can be granted to determine which DCP users can access each data set. The following user types can change data access permissions for a dataset:

    • The data set owner
    • The owner of the data source from which the data set was created
    • A user with administrator privileges

    Administrators typically control which adapters and data stores will be created and accessible in DCP, and which users can access each data store. Non-administrators can add a data source from a data store that was added by a DCP administrator if given permissions to that data store. If the non-administrator does not see a data store in the UI, then it has either not yet been added to DCP, or the user has not been granted permission.

next

Users and groups