Skip to content

Latest commit

 

History

History
39 lines (22 loc) · 2.19 KB

Challenge-02.md

File metadata and controls

39 lines (22 loc) · 2.19 KB
Raw

Challenge 02 - .NET Web frontend with OpenAPI and OData via APIM

< Previous Challenge - Home - Next Challenge >

Introduction

Now that we have an SAP landscape deployed in Azure, it's time to connect it to the outside world. In this challenge, you'll configure and connect up an ASP.NET core MVC application to consume OData services from SAP using SAP's demo data set.

Description

Odata

At this point your SAP data will no longer be an island! There are a number of steps for you to perform.

  • Review the following repository and familiarise yourself with it's concepts.

  • Deploy a new Resource Group in your Azure Subscription 'SAP-WTH046'

  • Deploy an empty Developer Tier Azure API Management Instance into your subscription. For this setup you can leave it as not network integrated, but production environments should be located inside a VNet.

    • Hint: Look in the Azure Portal for "API Management" as a service in the Marketplace.

  • Deploy an empty Azure Web Application into your subscription. Again here you do not need to be concerned about network/vnet integration, but you would consider this model in a production-ready environment.

  • Configure the API Management instance to connect to your S/4HANA or SAP ECC services as detailed here.

    • SAP Configuration
    • Hint: for now do not enable principal Propagation. Instead, simply configure SAP Basic Auth for now. We will enable this in the APIM policy later in another challenge. But let's connect to the data first!

Success Criteria

  • Run an ASP.NET MVC Core app that can view and edit data in the SAP Application Layer (SAP S/4HANA or SAP ECC) via RESTful OData calls, that have been secured and routed via an Azure API Management gateway.

Learning Resources