3.1 AWS DevOps for SAP Fiori Apps

Motivation

This lab shows how to setup Continous Integration & Delivery (CI/CD) for SAP Fiori based apps for NetWeaver ABAP.

CI/CD is designed for businesses, that want to improve applications frequently and require a reliable delivery process. The added effort to standardize builds, develop tests, and automate deployments is the manufacturing process for deploying code changes especially at scale and at a high quality.

In this lab, we use AWS CodePipeline including CodeBuild and CodeDeploy as a serverless CI/CD toolset on top of a SAP Fiori sample application. As a benefit, you don’t have to worry about managing any CI/CD servers or infrastructure. Furthermore, it comes with an onDemand pricing model, so that you can directly start practice DevOps at your company. The lab also leverages AWS Cloud9 as development environment and AWS CodeCommit as source code repository, however both these services are optional and can be easily replaced.

Architecture

Preparation menu

Prerequisites

To complete this lab, you will need the following items

  • AWS Account with access to
    • AWS CodePipeline
    • AWS CodeBuild
    • AWS CodeDeploy
    • AWS S3 (Deployment Artifacts)
    • AWS SNS (Notifications e.g. Pending Approval)
    • AWS Secrets Manager (Store SAP Credentials for Deployment)
    • (Optional) AWS CodeCommit
    • (Optional) AWS Cloud9
  • SAP NetWeaver ABAP Backend > 7.40 with ABAP Developer Tools (ADT) enabled = /sap/bc/adt inside SICF activated. Check also the troubleshooting guide.
  • SAP User with common developer authorizations
  • OS access to any server with outbound internet access, so that the AWS CodeDeploy Agent can be installed (should be inside same network/subnet like SAP system or located in the DMZ)

Below is a list of the steps for this lab: