05-02-2021 1:07 AM
#ABAP_Trial
Hello experts, I am facing a issue with setting up GUI configuration.
I followed the below tutorial to set up ABAP platform on my WINDOWS OS.
SAP ABAP Platform 1909 Developer Edition: Wrapup&Tips of Installation on Windows 10 | SAP Blogs
Docker installed, image extracted, container successfully runs. On the final step, I am facing a issue with
setting up GUI configuration. I get an error saying the connection is broken.
As you can see from the attached images, docker containers are working fine and port 3200 are published.
As instructed in the blog, I run the below command so that 3200 can be published.
"docker run --stop-timeout 3600 -i --name a4h -h vhcala4hci -p 3200:3200 -p 3300:3300 -p 8443:8443 -p 30213:30213 -p 50000:50000 -p 50001:50001 store/saplabs/abaptrial:1909 -skip-limits-check".
The problem is that "localhost" is not reached somehow, can anyone please tell me what is wrong? I am so close to the finish line!
(Tried to ping 127.0.0.1 and it works. Log attached.)
Cheers.
dev-disp.txtdev-ms.txtdev-w0.txt
05-04-2021 12:17 PM
I don't know this kind of installation but what is strange is your screenshot with what seems to be a port forwarding.
0.0.0.0 :30xxx is strange, it should be 127.0.0.1
The commande line with docker, it was run in your windows ? did you check if the hosts are know in the windows ? ping vhcala4hci works ?
if not, try to find the /etc/hosts in your windows directory & update it with these hosts
05-04-2021 12:36 PM
The port mappings are OK.
Pinging localhost or 127.0.0.1 is always working. Or at least should.
Did you wait for the magic *** Have fun! *** after starting the docker?
Depending on HW resources it can take quite a lot of time.
05-04-2021 12:50 PM
Hi Robert,
Yes I waited until "Have Fun" was displayed. After that I tired to connect to SAP GUI but the connection broken error occured. So I quit the docker and rebooted my PC. That is why "My termination has been requested. Stopping services." was shown after the "Have fun" in my attached image.
05-04-2021 2:00 PM
Hi Aocheng,
seems you have done everything correct. Could you please upload some trace files here. The command to copy them to c:\temp is:
docker cp a4h:/usr/sap/A4H/D00/work/dev_w0 c:\temp
docker cp a4h:/usr/sap/A4H/D00/work/dev_disp c:\temp
docker cp a4h:/usr/sap/A4H/ASCS01/work/dev_ms c:\temp
05-04-2021 2:22 PM
Hi Fredreic
I run in my windows command. In the /etc/hosts I have put the below lines but sill the same error on the SAP GUI.
127.0.0.1 localhost
127.0.0.1 vhcala4hci
Regarding the 0.0.0.0 vs 127.0.0.1, according to the below blog,
0.0.0.0 is the defualt IP and if you do not specify the IP when using "docker run".
Docker Port Binding explained | Better Programming
But yes, maybe I should specify 127.0.0.1 in the "docker run" command and see if it works....
"docker run --stop-timeout 3600 -i --name a4h -h vhcala4hci -p 127.0.0.1:3200:3200"
05-04-2021 2:59 PM
Hi Robert, really appreciate your help.
The traces are attached so please check them out.
Today I run the abap image with "--network host" paramter but ended in error so that log might be in there, After the error, I run the image properly again with the below command and like before, the container is running and the 3200 port is open the same way.
PS: I somehow could not attach the files on this comment so I added them on my original post above in the below file names.
dev_disp.txt, dev_ms.txt, dev_w0.txt
05-04-2021 5:42 PM
I haven't tried on Windows, but on Linux it runs fine with 32GB of system memory, with room to spare for Eclipse, the SAPGUI, Firefox, you name it.
05-04-2021 6:34 PM
Hi Former Member , thanks for checking!
My Windows system is running on:
Intel(R) Core(TM) i7-4770 CPU, 16,0 GB RAM, 1TB diskspace. As long as I see it in the blog, 16GB is enough to make it work for Windows. It's also the requirement in the official doc.
Therefore I was thinking 16GB would work...Do they mean it needs 16GB to start HANADB and you need more RAM on top of it to be able to acess the application server?
05-04-2021 6:58 PM
Hi aocheng,
yes 16 GB should be fine, but this is for the Docker alone. Plus the needed for Windows i guess the bare minimum will be 24 GB. In WSL2 you have not precise control over the allocated to Docker resources, but 16 for Windows and 1909 is not enough, sorry.
Powerful CPU is nice to have although not essential in this case.