9 | Loading...
10 |
16 |
18 |
21 |
22 |
23 |
26 |
27 |
60 | 6 | Test features in Microsoft Azure Data Manager for Energy after loading the TNO data set. 7 |
8 |9 | Note: Manifests are automatically assigned a data.tno.viewers and data.tno.owners Access Control List (ACL). 10 | The first user created during Experience Lab's deployment will be assigned these ACLs. 11 | Additional users will need to be a member of these ACLs to query and manipulate TNO data. 12 | Users can be added to these ACLs from the User Management page. 13 |
14 | 15 |6 | Experience Lab is an automated, end-to-end deployment accelerator with a friendly web-based UI that provides easy, fast deployments of Microsoft Azure Data Manager for Energy with sample dataset(s) for learning, testing, demo, and training purposes. 7 | This enables business audience and domain practitioners who are not familiar with OSDUTM to be able to create fully loaded and configured Microsoft Azure Data Manager for Energy deployments. 8 |
9 |10 | It is not intended to be a guide to Microsoft Azure Data Manager for Energy or intended to deploy in production environments. 11 |
12 |14 | Experience Lab provides several integration capabilities for Microsoft Azure Data Manager for Energy: 15 |
16 |26 | *OSDU is a trademark of The Open Group. 27 |
28 | -------------------------------------------------------------------------------- /developer-portal/src/app/authorization/services/authorization.service.ts: -------------------------------------------------------------------------------- 1 | // Copyright (c) Microsoft Corporation. 2 | // Licensed under the MIT License. 3 | 4 | import { HttpClient, HttpHeaders } from '@angular/common/http'; 5 | import { Injectable } from '@angular/core'; 6 | import { catchError, map, Observable, of } from 'rxjs'; 7 | import { UserGroup } from 'src/app/models/user-group.enum'; 8 | import { environment } from 'src/environments/environment'; 9 | 10 | @Injectable({ 11 | providedIn: 'root' 12 | }) 13 | export class AuthorizationService { 14 | 15 | /** 16 | * Caches the user's groups to prevent unnecessary HTTP calls 17 | */ 18 | private cachedUserGroups: any[] = null; 19 | 20 | constructor(private http: HttpClient) { } 21 | 22 | /** 23 | * Checks if the authenticated user is in the specified group 24 | * @param group The group to verify the user belongs to 25 | * @returns True if the user in the group, false otherwise 26 | */ 27 | public IsUserInGroup(group: UserGroup): Observable7 | Included in Experience Lab is a pre-configured Power BI connector for visualizing TNO data. 8 | The connector is open source, and can be found on Kadri Umay's GitHub. 9 | Currently, the Power BI connector only supports client-side Power BI reports - it does not support reports published to Power BI Online. 10 |
11 |The following steps explain how to use Power BI with Azure Data Manager for Energy.
22 |Name: {{this.profile?.name}}
6 |Email: {{this.profile?.email}}
7 |Id: {{this.profile?.id}}
8 |{{this.tokens?.access}}
20 |{{this.tokens?.refresh}}
33 |Assigned Groups
35 || Group | 51 |{{group.name}} | 52 |Description | 55 |{{group.description}} | 56 |
|---|---|
| No data matching the filter "{{input.value}}" | 61 |
6 | This component assists in testing Microsoft Azure Data Manager for Energy REST APIs to execute underlying service API calls or 7 | perform functional flows. 8 |
9 | 10 |There are many different ways that REST APIs can be called from the use of simple curl commands to complex Postman 13 | projects. For this lab, a Rest Client will be used 15 | for a simple way to send a request. This extension allows for simple http scripts to be executed and leverages 16 | Visual Studio Settings to be able to easily point to different environments.
17 |
32 | "rest-client.environmentVariables": {
33 | "{{this.instanceName}}": {
34 | "TENANT_ID": "{{this.tenantId}}",
35 | "CLIENT_ID": "{{this.clientId}}",
36 | "HOST": "{{this.host}}",
37 | "DATA_PARTITION": "{{this.dataPartition}}",
38 | "DEVELOPER_PORTAL": "{{this.developerPortalUrl}}",
39 | "REFRESH_TOKEN": "{{this.refreshToken}}"
40 | }
41 | }
42 | Basic core functionality for includes: the creation of a legal tag, the submission of a storage record, 52 | and then the search and retrieval for that record.
53 | 54 |Send Requests from rest/check-core.http
56 |Basic manifest ingestion functionality includes: the creation of a legal tag, triggering a workflow, 61 | retrieving the status, waiting for completion, and then querying for the data uploaded.
62 |Send Requests from rest/check-csv.http
64 |Basic csv data ingestion functionality includes: the creation of a legal tag, creation of a schema, 69 | retrieval of an Upload URL, uploading a CSV file to that URL, triggering the workflow, retrieving the 70 | status, waiting for completion, and then querying the data uploaded.
71 |Send Requests from rest/check-csv.http
73 |