This repository is a fork of nzamani/sap-cloud-connector-docker The main SAPCC Cloud Connector Docker provides an image which can help run a SAP Cloud Connector inside a docker container. However we can't use it for any kind of test automation setup. In order to call any API on the cloud connector 2 things need to be fixed viz.
- You need to change the password.
- You need to set the Instalation Type.
This image tries to address those issues by copying the users.xml and scc_config.ini. The password for the connector remains the same. And it is set to master as installation type. You can directly start calling APIs after running this image.
Easily setup SAPCC in docker.
See my YouTube video for additional details: Installing SAP Cloud Connector (SAPCC) into Docker and connecting it to SAP Cloud Platform (SAPCP)
Check also my blog Installing SAP Cloud Connector into Docker and connecting it to SAP Cloud Platform. There you'll find links to the whole blog series.
The Dockerfile is based on https://github.com/PaxSchweiz/SAPHCPConnector/blob/master/Dockerfile
-
Install Docker
Windows: Make sure you are running on Windows 10! For installing Docker you will need admin rights on your machine. Furthermore, you might have to run your Terminal/CLI as "Administrator" in case your current user is not an admin user (i.e. GitBash, PowerShell).
-
Install Git
On Windows I suggest to install Git Bash as well (you'll be asked during the installation process).
Hint: Installing git is actually not really needed. Alternatively, you could also copy/download this Dockerfile to yor machine manually.
-
Clone this repo
git clone https://github.com/nzamani/sap-cloud-connector-docker.git cd sap-cloud-connector-docker
-
Build the Docker image
-
Without Proxy
docker build -t sapcc:2.12.3 .
-
Behind a Proxy
docker build --build-arg http_proxy=http://proxy.mycompany.corp:1234 --build-arg https_proxy=http://proxy.mycompany.corp:1234 -t sapcc:2.12.3 .
Hint: In a proxy environment your
docker build
command (see above) will fail in case you don't set the proxy as mentioned above or in case you use wrong proxy settings. Also consider that you might have to set the proxy manually for some software installed in the container, i.e. for the SAPCC you can set it manually for each SAPCP connection.
-
-
Create a container running as a deamon
-
Use this if you want to map the default SAP ports as they come on localhost (preferred)
docker run -p 8443:8443 -h mysapcc --name sapcc -d sapcc:2.12.3
-
Use this one if "random" ports on localhost are fine for you
docker run -P -h mysapcc --name sapcc -d sapcc:2.12.3
-
-
Starting/Stopping the container
- Starting:
docker start sapcc
- Stopping:
docker stop sapcc
- Starting:
-
Post Installation Steps
Logon to https://localhost:8443 with the default credentials:
- User: Administrator
- Password: manage
You will be asked to change your password.
Hint: It might take a few seconds after you can access https://localhost:8443. This is because the SAP Cloud Connector needs some time to start (even though the Docker Container has immediately started).
-
Proxy Settings
A proxy can be set manually for each SAPCP connection after logging on to the SAPCC using a browser. Make sure to use the correct proxy settings (incl. credentials if required), otherwise your SAPCC might not be able to connect to your SAPCC account.
docker network create -d bridge saptrial
docker network connect --alias mysapcc saptrial sapcc
docker network connect --alias vhcalnplci saptrial nwabap751
docker network connect --alias vhcalnplci.dummy.nodomain saptrial nwabap751
docker network disconnect saptrial nwabap751
docker network disconnect saptrial sapcc
docker network rm saptrial
# Suggestion: stop the container you want to backup before continuing
docker stop sapcc
# create an image "sapccbackup" from the container "sapcc"
docker commit sapcc sapccbackup:1
# later you can create a new container from the new image "sapccimage"
# Hint: if the ports etc are already used by other containers you must use different ports (or i.e. deleting the other containers first)
docker run -p 8443:8443 -h mysapcc --name sapccNewContainer -d sapccbackup:1
In case you followed my YouTube Video Installing SAP NW ABAP 7.51 SP02 into Docker or followed the steps described here then the following SAPCP Destinations can be used:
Field | Value |
---|---|
Name | NW_ABAP_751_Docker_BasicAuth |
Type | HTTP |
Description | NW ABAP 7.51 in Docker on localhost Basic |
Location ID | |
URL | https://nwabap751:44300/sap/opu/odata |
Proxy Type | OnPremise |
Authentication | BasicAuthentication |
User | DEVELOPER |
Password | Appl1ance |
Field | Value |
---|---|
Name | NW_ABAP_751_Docker_PrincipalPropagation |
Type | HTTP |
Description | NW ABAP 7.51 in Docker on localhost PP |
Location ID | |
URL | https://nwabap751:44300/sap/opu/odata |
Proxy Type | OnPremise |
Authentication | PrincipalPropagation |
Property | Value |
---|---|
WebIDEUsage | dev_abap,bsp_execute_abap,ui5_execute_abap,odata_abap,odata_gen |
WebIDESystem | NPL |
WebIDEEnabled | true |
HTML5.SocketReadTimeoutInSeconds | 300 |
-
Youtube: SAP HANA Academy - SAP CP: Blueprint #1.4: Cloud Connector Principal Propagation
-
Youtube: SAP HANA Academy - SAP CP: Blueprint #1.5 ABAP Principal Propagation
-
Youtube: SAP HANA Academy - SAP CP: Blueprint #1.6: Principal Propagation using X509 certificates
-
SAP Help: Creating Intermediate Certificates
-
SAP Community: How to Guide โ Principal Propagation in an HTTPS Scenario