Rediger

Del via

Tutorial: Perform manifest-based file ingestion

  • Artikkel

Manifest ingestion provides the capability to ingest manifests into an Azure Data Manager for Energy instance.

In this tutorial, you learn how to:

  • Ingest sample manifests into an Azure Data Manager for Energy instance by using Postman.
  • Search for storage metadata records created during manifest ingestion by using Postman.

Prerequisites

Before you start this tutorial, complete the following prerequisites.

Get details for the Azure Data Manager for Energy instance

  • You need an Azure Data Manager for Energy instance. If you don't already have one, create one by following the steps in Quickstart: Create an Azure Data Manager for Energy instance.

  • For this tutorial, you need the following parameters:

    Parameter Value to use Example Where to find this value
    CLIENT_ID Application (client) ID 3dbbbcc2-f28f-44b6-a5ab-xxxxxxxxxxxx You use this app or client ID when registering the application with the Microsoft identity platform. See Register an application.
    CLIENT_SECRET Client secrets _fl****************** Sometimes called an application password, a client secret is a string value that your app can use in place of a certificate to identity itself. See Add a client secret.
    TENANT_ID Directory (tenant) ID 72f988bf-86f1-41af-91ab-xxxxxxxxxxxx Hover over your account name in the Azure portal to get the directory or tenant ID. Alternately, search for and select Microsoft Entra ID > Properties > Tenant ID in the Azure portal.
    SCOPE Application (client) ID 3dbbbcc2-f28f-44b6-a5ab-xxxxxxxxxxxx This value is the same as the app or client ID mentioned earlier.
    refresh_token Refresh token value 0.ATcA01-XWHdJ0ES-qDevC6r........... Follow How to generate auth token to create a refresh token and save it. You need this refresh token later to generate a user token.
    DNS URI <instance>.energy.Azure.com Find this value on the overview page of the Azure Data Manager for Energy instance.
    data-partition-id Data partitions <instance>-<data-partition-name> Find this value on the overview page of the Azure Data Manager for Energy instance.

Follow the Manage users guide to add appropriate entitlements for the user who's running this tutorial.

Set up Postman and execute requests

  1. Download and install the Postman desktop app.

  2. Import the following files into Postman:

    To import the Postman collection and environment variables, follow the steps in Importing data into Postman.

  3. Update CURRENT VALUE for the Postman environment with the information that you obtained in the details of the Azure Data Manager for Energy instance.

  4. The Postman collection for manifest ingestion contains multiple requests that you must execute sequentially.

    Be sure to choose Ingestion Workflow Environment before you trigger the Postman collection.

    Screenshot of the Postman environment.

  5. Trigger each request by selecting the Send button.

    On every request, Postman validates the actual API response code against the expected response code. If there's any mismatch, the test section indicates failures.

Here's an example of a successful Postman request:

Screenshot of a successful Postman call.

Here's an example of a failed Postman request:

Screenshot of a failed Postman call.

Ingest sample manifests by using Postman

To ingest sample manifests into the Azure Data Manager for Energy instance by using the Postman collection, complete the following steps:

  1. Get a User Access Token: Generate the user token, which will be used to authenticate further API calls.

  2. Create a Legal Tag: Create a legal tag that will be added to the manifest data for data compliance purposes.

  3. Get a Signed URL for uploading a file: Get the signed URL path to which the manifest file will be uploaded.

  4. Upload a file: Download the Wellbore.csv sample to your local machine. It could be any file type, including CSV, LAS, or JSON. Select this file in Postman by clicking the Select File button.

    Screenshot of uploading a manifest file.

  5. Upload File Metadata: Upload the file metadata information, such as file location and other relevant fields.

  6. Get the File Metadata: Call to validate if the metadata was created successfully.

  7. Ingest Master, Reference and Work Product Component (WPC) data: Ingest the master, reference, and work product component (WPC) manifest metadata.

  8. Get Manifest Ingestion Workflow status: The workflow starts and is in the running state. Keep querying until the state changes to finished (typically 20 to 30 seconds).

Search for ingested data by using Postman

To search for storage metadata records created during the manifest ingestion by using the Postman collection, complete the following steps:

  1. Search Work Products: Call the search service to retrieve the work product metadata records.
  2. Search Work Product Components: Call the search service to retrieve the WPC metadata records.
  3. Search for Dataset: Call the search service to retrieve the dataset metadata records.
  4. Search for Master data: Call the search service to retrieve the master metadata records.
  5. Search for Reference Data: Call the search service to retrieve the reference metadata records.

Next step

Advance to the next tutorial:

Tutorial: Use sdutil to load data into Seismic Store

For more information about manifest ingestion, see the OSDU Operator Data Loading Quick Start Guide.