[SAP] Create a development environment with NW AS ABAP Developer Edition (2) Connect with Cloud Platform

Introduction

In this article, you will use Cloud Connector to connect SAP NW AS ABAP installed in a Docker container to Cloud Platform.

Previous article: [SAP] Creating a development environment with NW AS ABAP Developer Edition (1)

Constitution

The environment is Ubuntu (18.04) on AWS EC2. Install Cloud Connector in a separate container from NW AS ABAP.

Install Cloud Connector

Overview

The installation procedure is as described in the GitHub repository below. https://github.com/SAP-samples/cloud-platform-workflow-virtual-event/blob/master/exercises/03/readme.md

However, if it is a Dockerfile in the repository, it can not be executed in Chrome, so it is in Pull Request Make your modifications before creating the Docker image.

Where I stumbled

This time, NW AS ABAP and Cloud Connector are in separate containers, so I stumbled upon the Cloud Connector settings.

I was able to access NW AS ABAP from the Ubuntu browser on localhost (127.0.0.1), so when I set the Internal Host to 127.0.0.1:8000, it became Not Reachable.

In reality, I had to specify an IP address that I could access from the Cloud Connector container. The two containers were connected to the default network "bridge", and each container was assigned an IP within the network. It seems that you should specify 172.17.0.2 to access the container of NW AS ABAP from Cloud Connector.

You can see the IP of the container with the following command.

docker inspect <Container name> 

At the bottom there is a section called "Networs" where you can see the IP Address.

When I specified 172.17.0.2 for Internal Host, it became Reachable. However, I feel that this IP is likely to change depending on the container startup order. As a countermeasure, start NW AS ABAP → Cloud Connector in this order.

Fixed start / stop shell

[Part1](https://qiita.com/tami/items/031c8c8e12e24b467e75#%E8%B5%B7%E5%8B%95%E5%81%9C%E6%AD%A2%E7%94%A8%E3 Add start / stop of Cloud Connector to the start / stop shell created in% 81% AE% E3% 82% B7% E3% 82% A7% E3% 83% AB).

managesap
#!/bin/bash

start_sap(){
  #start container	
  sudo docker container start nwabap752
  #start sap
  sudo docker exec -it nwabap752 /usr/sbin/uuidd 
  sudo docker exec -it nwabap752 su - npladm -c "startsap ALL"
}	

stop_sap(){
  #stop sap	
  sudo docker exec -it nwabap752 su - npladm -c "stopsap ALL"
  #stop container
  sudo docker container stop nwabap752
}

start_scc(){
  #start scc
  sudo docker container start myscc
}	

stop_scc(){
  #stop scc
  sudo docker container stop myscc
}	

start_env(){
  start_sap
  start_scc
}	

stop_env(){
  stop_scc
  stop_sap
}	

From now on, run start_env to start SAP and SCC at the same time, and run stop_env to stop it.

Cloud Platform Destination registration

Register your Destination on Cloud Platform (CF).

The contents of Additional Properties are as follows.

When I run Check Connection, I get the following error, but if I can connect from Business Application Studio, there is no problem.

What I could do so far

--You can now connect your local NW AS ABAP to Cloud Platform. --You can use the OData service of NW AS ABAP from Business Application Studio.

Next time, I would like to develop and deploy Fiori applications.

reference

-SAP Cloud Platform Workflow --Ex.03 --Installing & configuring the SAP Cloud Connector (Video)

• Exercise 03 - Installing & configuring the SAP Cloud Connector（GitHub） -[SAPCP] I tried connecting the trial environment and Cloud Connector