Skip to Content
Technical Articles
Author's profile photo Karl Kessler

Now available: ABAP Platform Trial

Dear SAP customers and partners, dear ABAP developer community,

ABAP  Platform Trial 1909 is available now. ABAP Platform Trial replaces the former Developer Edition 1909. With ABAP Platform Trial 1909 we want to return to you what the ABAP developer community and many SAP customers and partners were missing for a long time: a standalone ABAP trial offering free of charge which you can use for your own educational purposes, for your own configuration and test setups and as a home for your open source projects. Over the last year, we have been in close contact with the SAP Mentors and DSAG (Sebastian Freilinger-Huber and team from AK Development) to better understand their needs and to find a way to offer the trial version again.

Like its predecessor, ABAP Platform Trial is a docker image containing an ABAP application server (ABAP Platform 1909 SP 07) running on top of the SAP HANA 2.0 database and SAP Cloud Connector. You can pull the entire image from docker hub and create a docker container from it, see ABAP Platform Trial on Docker.

ABAP%20Platform%20Trial%20on%20Docker%20Hub

ABAP Platform Trial on Docker Hub

ABAP Platform Trial is modeled as an official SAP product and therefore is delivered through a delivery program. A delivery program ensures that the product meets all SAP product and delivery standards. Special thanks to the SAP HANA team who helped us to get started and for their support during the project.

In this fast-paced world with Cloud and AI everywhere version 1909 might sound a bit like an anachronism. However, this version is still in broad use by SAP customers. It was a good starting point for our new delivery approach. We are already working on a subsequent delivery for ABAP Platform Trial 2022 (we leave out version 2020 and 2021). We plan to deliver ABAP Platform Trial for every new ABAP Platform release (version 2023, 2025 and 2027 according to the release strategy for SAP S/4HANA). In addition, we plan to update ABAP Platform Trial subsequently whenever a new SP update for ABAP Platform is released. Please note that the ABAP Platform Trial roadmap like any other SAP roadmap is subject to the usual roadmap disclaimers.

ABAP Platform Trial 1909 is a docker image and very easy to install. You need to get Docker Desktop installed on your Windows laptop or Mac. Then you open a command prompt or Terminal:

docker pull sapse/abap-platform-trial:1909
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 sapse/abap-platform-trial:1909 -skip-limits-check

Please make sure you have enough main memory on board (>=32 GB). The documentation readme on docker hub provides additional technical details.

Once the docker container is up and running you can log on with ABAP Development Tools for Eclipse, via SAP GUI or via SAP Fiori Launchpad, see screen shots below. Enjoy your ABAP Platform Trial 1909.

The available scope including the preconfigured scenarios are described in Julie Plummer’s ABAP Platform Trial rollout blog.

ABAP Platform Trial is a team effort. Many colleagues have contributed in many ways. I would like to say a big THANK YOU to the core team:

  • Ralf Henning who owns, develops and maintains (upgrade, patch) the master image,
    drives the content and test efforts
  • Stephan Daub who drives the delivery program end to end
  • Jakub Filak who develops the docker image and scripts for publication on docker hub
  • Natalia Brik, Roman Anisovich, Irina Petrov and Derna Hetherton for their support
    around non-ABAP technical assembly
  • Frank Rotter who validates our delivery tasks
  • Sandra Thimme who executes the test plan
  • Julie Plummer who writes the rollout information and interacts with the community
  • Roland Brethauer and Matthis Langhoff for security validation and export classification
  • Bettina Knauss for her CAL support

I would like to thank the SAP Mentors for their continuous engagement. Special thanks go to the following SAP Mentors for testing the image and providing their valuable feedback and input: Gregor Wolf, Wouter Lemaire, Martin Fischer and Paul Hardy.

Last but not least I would like to thank you all for your patience regarding this topic. We will keep you in the loop and should something happen unexpectedly we will brief the SAP Mentors and SAP user groups prior to the publication on external media.

Best regards

Karl

ABAP%20Platform%20Trial%20in%20Docker%20Desktop

ABAP Platform Trial in Docker Desktop

ADT%20connected%20to%20ABAP%20Platform%20Trial

ADT connected to ABAP Platform Trial

SAP%20Fiori%20app%20on%20ABAP%20Platform%20Trial

SAP Fiori app on ABAP Platform Trial

Assigned Tags

      116 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Martin Fischer
      Martin Fischer

      Thanks Karl and team for listening to the community and bringing this back! I think and hope that we having it as an official SAP product will make it easier to keep it up-to-date and also make it something the community can trust on!

      Even though it took a while, it was a very good collaboration between the SAP Mentors, DSAG and SAP to get it back. Thanks to all parties envolved!

      Author's profile photo Lars Hvam
      Lars Hvam

      That's really good news for the ABAP Ecosystem, thank you

      Author's profile photo Nils Lutz
      Nils Lutz

      Awesome news, thank you for bringing this back!

      Author's profile photo Mike Pokraka
      Mike Pokraka

      Hooray, big thanks to all who made it possible!

      Author's profile photo MACHIREDDYPALLY SWEEKAR
      MACHIREDDYPALLY SWEEKAR

         Karl Kessler

      Hi kessler,
      could you please do help me with configuration step by step with this please
      my pc  12 gb ram
      1 tb hdd
      i5 configuration
      Author's profile photo Jakub Filak
      Jakub Filak

      Yes, of course, first go to favorite hardware shop and buy more powerful machine. Then we can continue.

      Author's profile photo Marc Bernard
      Marc Bernard

      Funny, but not really. First, his machine isn't far off and might fit some more memory. And second, not everyone can afford the hardware for running SAP software. A simple "no" with a link to the docs would have done.

      Author's profile photo Roland Kramer
      Roland Kramer

      Hello Marc Bernard, Jakub Filak and    Karl Kessler

      As Marc already said: nice try and also HANA needs at a minimum a 32 (better 48) GB node to run at a minimum, and the RAM for the SAP Instance is not added.

      We already made this experience with our internal implementation of SAP Data Intelligence - SAP Data Intelligence 3.0 – implement with slcb tool (more about DI can be found here)

      For internal purposes, the "Developer Edition" aka IDES never disappeared and can still be accessed, but hurry several parties want to dismantle the servers soon ... 🙁

      Running "SAP as mini" like a proper system will be a dream, as SAP (on-premise) can only big(ger) ... 😉

      Author's profile photo maxx currey
      maxx currey

      The term "on-premise" s/b "on premises".  A premise is a proposition not a place.

      Author's profile photo Jakub Filak
      Jakub Filak

      Marc has made a good point - my comment is too vague. So to be more precise, you do not need more powerful machine, you just need more RAM as 12GB is not enough (the official value is 32GB - I have no link to share and I am not a fan of screenshots, but it is the only bold text just below the pull and run command).

      Author's profile photo Andrea Borgia
      Andrea Borgia

      Still have to check this edition but the previous A4H could run on a Linux machine with 32GB, at the same time as the older NPL VM. Long story short, those values have some margin built into them.

      It's also gonna be interesting to see if the minimum kernel version has been upgraded: I'm still using a 5.16 (or something) instead of the current 6.4 series, otherwise the container would not start.

      Author's profile photo Andrea Borgia
      Andrea Borgia

      Pleased to report that the new image runs on kernel 6.4 on the current Debian/testing: this alone is reason enough for me to move my repos from the old to the new one, so thanks!

      A few random remarks:

      • the name of the abapGit complete report should be ZABAPGIT_STANDALONE, not ZABAPGITFULL (can be fixed in the next version, really minor issue)
      • the SFLIGHT scenario is pointing to a branch that has been renamed
      • the SSL certs for GitHub are expired

      Nothing terrible, you just have to know it.

      Author's profile photo Ralf Henning
      Ralf Henning

      Noted. Thanks for the Info!

      Author's profile photo Andrea Borgia
      Andrea Borgia

      Just saw another glitch, an internal SAP URL:internal%20SAP

      Author's profile photo Jakub Filak
      Jakub Filak

      Hi Andrea, good catch but github.tools.sap is a publicly available service.

      Author's profile photo Andrea Borgia
      Andrea Borgia

      "Internal" meaning that a login is required, unlike the other public repositories.

      Author's profile photo MACHIREDDYPALLY SWEEKAR
      MACHIREDDYPALLY SWEEKAR

      Hi Filak ,

       

      can u help how can i get sap abap trial like can u help configuration for aws or azure or gcp we can get that right

      Author's profile photo Jakub Filak
      Jakub Filak

      Sure. First order a Linux machine with 32GB RAM and 200GB disk space. If you can choose distribution, use some RHEL alternative, or Fedora, or OpenSUSE, or Ubuntu. Once you have the machine and working ssh conneciton, we can continue. I have never ever order a machine on Azure nor GCP, so I cannot help you with this task.

      Also, I am not sure this is the right forum for such guidance. You can find the right contact on the overview page:

      https://hub.docker.com/r/sapse/abap-platform-trial

      Author's profile photo Thomas Madsen Nielsen
      Thomas Madsen Nielsen

      Hi Jakub

      You make it sound like it must run on Linux, but as I understand sapse/abap-platform-trial - Docker Image | Docker Hub it can run on Linux, Windows and macOS just as well.

      Or am I wrong?

      I agree that this is not the right forum but does the right forum exist?

      I hope SAP creates a dedicated tag for "ABAP Platform Trial" instead of just using the more generic "ABAP Development". After all, the installation of ABAP Platform Trial has not much to do with the decipline of writing ABAP code.

      Regards

      Thomas Madsen Nielsen

      Author's profile photo Jakub Filak
      Jakub Filak

      You are not wrong. Docker runs in Windows, macOS and GNU/Linux and you can run the image from your Windows, macOS or GNU/Linux workstation.

      Reasons why I asked MACHIREDDYPALLY to order Linux.

      Techincall backgroug:

      As I wrote somewhere else, Docker containers are built on top of Linux Kernel Namespaces (and some other Linux features like cgroups): https://en.wikipedia.org/wiki/Linux_namespaces

      So people running Docker on Windows or macOS, do run a transparent Virtual machine with Operating System built around Linux kernel, which runs the real docker container engine.

      Pople running docker on GNU/Linux do run the docker container engine on their GNU/Linux directly without any additional hypervisior.

      1. Reason efficiency:

      Running docker on GNU/Linux is simply more efficient as you do not need the intermediate VM with GNU/Linux. Ordergin macOS or Windows would mean that you order a VM only to run a hidden VM which runs the docker container engine.

      2. Reason skills:

      I would not be able to help anybody with deploying Docker on Windows or macOS as I have no practical experience with those Operating Systems (I have stopped using windows 12years ago - I have a Windows XP Professional Administrator certificate though; I have seen macOS three times and touched a keyboard connect to a terminal on macOS only once).

      I hope my answer clarifies the topic.

      Disclaimer: I had no intention to start an OS flame war - use whatever OS you like. I did not realize I could offer an OS (actually I could not offer it because of my skills).

      Author's profile photo Gregor Wolf
      Gregor Wolf

      Hi Karl,

      please forward a big thank you to everyone involved! Great to have the ABAP Developer edition back. I think the positive side was the better understanding that SAP gained about the use cases that go beyond just ABAP Development.

      Best Regards
      Gregor

      Author's profile photo Marco Beier
      Marco Beier

      I can just underline what awesome news this is. Big thanks to everyone involved and their continuous effort in bringing this (back)!

      Author's profile photo Jörgen Lindqvist
      Jörgen Lindqvist

      I still have the old version up and running, so I might sit this one out. Nevertheless, I need to say this is great news! Thank you for bringing this back and for the intention to deliver future releases. 👍 It's really valuable for the community!

      Author's profile photo Huseyin Dereli
      Huseyin Dereli

      Great news, thanks!

      Author's profile photo Marc Bernard
      Marc Bernard

      Thank you, SAP! I will just leave this here.

      Unfortunately, some issues with the previous Dev Edition have not been addressed in this new release (like missing ports).

      What is the preferred feedback channel for this product?

       

      Author's profile photo Ralf Henning
      Ralf Henning

      Hi Marc

      Please have a look at section primary contacts at the end of the oververview page.

      https://hub.docker.com/r/sapse/abap-platform-trial

      Your feeedback is very welcome here.

      Kind regards Ralf

       

      Author's profile photo Jakub Filak
      Jakub Filak

      Networking depends on Operating System, but as far as I know, there is no need to change anything in the image to give you access to any port you need.

      For example, my primary OS is Fedora Linux and I can access all ports of my containers regardles of the run command I issue. I just have to use IP address of the container and iptables route my packages at the desired place.

      Windows and Mac are different because containers are build on the top of Linux kernel Namespaces. Therefore, to make Docker running, the real docker process must run in a virtual machine with Linux. I am not sure but I bet setting up ip router on Mac/Windows is probably not a trivial task (well, iptables configuraion on GNU/Linux is certainly not trivial either ...) and thus one has to use the parameter --publish(-p) on the run command to make the required ports available directly on the host. (Since I have no Windows nor Mac machine available my understand of these OSes is limitted and I might have been mistaken. Please, correct me if I am wrong).

      Author's profile photo Vladislav Kustov
      Vladislav Kustov

      Hi Ralf,

      Could you advise a password for SYSTEM user to set up a connection HDB at Eclipse. Thank you.

      Author's profile photo Ralf Henning
      Ralf Henning

      Hi Vladislav, should be the same as for absp login

      greetings from danmark, ralf

      Author's profile photo Vladislav Kustov
      Vladislav Kustov

      Thank you Ralf, I see sapstartsrv service has not started, this is ok?

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Marc,

      I'm just reviewing the comments here. Were you able to resolve the missing ports issue?
      If not, I always advise users to open a new question in the ABAP Development forum:

      ABAP Development: Ask a Question , using the hashtag #ABAP_Trial.

      PS: Thanks for the musical feedback!

      Best wishes,

      Julie Plummer.

      Author's profile photo Marc Bernard
      Marc Bernard

      Hi Julie, I already had a brief exchange with Jakub.

      The documentation should mention that there are other essential ports like for the Tenant DB. It's also important to note that you can't change the ports once the container is started.

      30215: SAP HANA Tenant Database (A4H)
      50213: SAP Control Start Service (Webservice)
      50214: SAP Control Start Service (Webservice SSL)
      1128: SAP Host Controller (Webservice)
      1129: SAP Host Controller (Webservice SSL)

      Maybe it's better to use ranges or alternatively open all ports.

      Author's profile photo Ryan Fleischmann
      Ryan Fleischmann

      Fantastic news! Thank you for the hard work and dedication of the team to make this happen

      Author's profile photo Balint Szebenyi
      Balint Szebenyi

      That's really good news! Thanks for your work.

      Author's profile photo Alban Leong
      Alban Leong

      Yay! Best news of the year!

      Author's profile photo Dirk Obert
      Dirk Obert

      Oh, wow. Do we have already x-mas?

      Many thanks for this great present & thanks to all who were involved in making it possible!

      Just one question.

      Will "docker pull sapse/abap-platform-trial:1909" relplace / overwrite an existing container?

       

      Author's profile photo Jakub Filak
      Jakub Filak

      No, it won't. Even more, it will not remove the image you already have downloaded, so you better have lot of disk space.

      Author's profile photo Dirk Obert
      Dirk Obert

      Hi Jakub,

      thank you very much for your clarification.

      Br.,

      Dirk

      Author's profile photo Asif Irfan
      Asif Irfan

      Great News Karl!

      Thanks for bringing it back & already excited for ABAP Platform Trial 2022.

      Thanks!

      Author's profile photo Sebastian Freilinger-Huber
      Sebastian Freilinger-Huber

      Thanks a lot for this.

      Thank you Karl & everyone who was involved from SAP side plus a big thanks to the involved SAP Mentors.

      This is a great example how a trustworthy relationship to SAP can work based on honest discussions, where every participants puts his statements to the table in a constructive, target-oriented manner.

      Extremly looking forward to the 2022 edition 🙂

      Author's profile photo Jörg Brandeis
      Jörg Brandeis

      Great! Many thanks to SAP and to everyone who repeatedly asked. To the 278 votes on influence.sap.com and to everyone else who didn't let up.

      It's great that the community is being heard by SAP.

      Author's profile photo Wises Keshom
      Wises Keshom

      This is really great new and exited for the in coming 2022 edition (and more). Thank you SAP for helping us especially the independent developer who doesn't have the right to access newer version of SAP environment.

       

      I do believe that with the comeback of ABAP Platform Trial will make good impact to the ABAP community.

      Author's profile photo Wesson Wang
      Wesson Wang

      I see something similar, it is SAP NetWeaver AS ABAP Developer Edition.

      What are the differences between them?

      For ABAP, I am new guy.

      Author's profile photo Sadullah TANRIKULU
      Sadullah TANRIKULU

      Hey Wesson,

      ABAP trial works in Docker container, Netweaver Dev Edition works on Virtual Machine like Oracle Virtual Box.

      Dev Edition version 7.52 (You can't do a "select query" for internal table, you can't create CDS View Entity etc.). Docker needs more memory to run the image as mentioned above, 32 GB. You can run Netweaver Dev Edition with a 8 GB RAM (I did it).

      To brevity, if you need a local SAP environment, choose one of them, of course, it depends on your PC hardware limitations.

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Wesson, hi Sadullah,

      First: Thanks Sadullah for this response; it is correct: ABAP 7.52 SP04 Dev Edition runs on a VM like Oracle Virtual Box or VMWare.

      Also, the 2 products are similar.

      As additional information:

      1. ABAP Platform Trial 1909 is much newer, with some nice new pre-configured goodies. I've talked about these here:

      https://blogs.sap.com/2023/07/31/abap-platform-trial-1909-available-now/

      ABAP Platform Trial is based on the foundation layer of ABAP Platform for S/4HANA 1909. My colleague Olga Dolinskaja has provided a great slide deck of the highlights of this version:

      https://blogs.sap.com/2019/10/17/abap-platform-for-sap-s4hana-1909/

       

      2. ABAP Platform Trial 1909 is on Docker, so you don't need to:

      • Configure VM (e.g. VMWare)
      • Install a Linux system, e.g. openSUSE
      • Configure this system (hostname, start uuidd etc)

      The only advantage that I can see of ABAP 7.52 SP04, is that dev edition on VMWare requires less memory than Trial on Docker. For my intro to ABAP 7.52 SP04, developer edition, see:

      https://blogs.sap.com/2019/07/01/as-abap-752-sp04-developer-edition-to-download/

      Best wishes,

      Julie Plummer.

      Author's profile photo Diego Dora
      Diego Dora

      HI    Karl Kessler ,

      I wanted to thank you and the team for having so many open discussions with the SAP Mentors. Taking the time to get with us and listen our concerns to later on materialize those into viable and tangiable solution motivates us even more to bring our opinions foreward and collaborate with all of you.

      Thank you ALL again and we look forward to continue working together !

      Author's profile photo Martin Ceronio
      Martin Ceronio

      Nice one! The ABAP communities thank you.

      Author's profile photo Praveer Kumar Sen
      Praveer Kumar Sen

      Run Successfully 🙂

      Author's profile photo Joachim Rees
      Joachim Rees

      Awesome, thanks a lot!

      Author's profile photo Nigel James
      Nigel James

      This is really great news.

      Thanks to the mentors and others for pressing SAP with the case that this is needed.

       

      In the 20th year of the community it is great to have this back. I remember back in 2003 downloading my first ABAP trial in the beta community.

       

       

       

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Nigel,

      Thanks for the nostalgia trip. Can't believe it's 20 years since I first listened to my Israeli colleagues explaining the idea of a "Community" :-).

      I can't even believe it's 10 years since we celebrated the 10th anniversary at TechEd Amsterdam.

      Best wishes Julie.

      Author's profile photo Marian Zeis
      Marian Zeis

      Thanks to the whole team for making this possible!
      I am especially looking forward to future releases.

      Have you tested it or made it work on an Apple Silicon?
      I'm stuck on "HDB: starting" at startup.
      There is enough RAM available for Docker.
      Anything I can debug or check?

       

      docker run --sysctl kernel.shmmax=21474836480 --sysctl kernel.shmmni=32768 --sysctl kernel.shmall=5242880 --sysctl kernel.msgmni=1024 --sysctl kernel.sem="1250 256000 100 8192" --ulimit nofile=1048576:1048576  --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 sapse/abap-platform-trial:1909 -agree-to-sap-license -skip-limits-check
      WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
      
      You have accepted the SAP Developer Center Software Developer License Agreement
      by passing the parameter -agree-to-sap-license.
      You can read the license text in the file /SAP_COMMUNITY_DEVELOPER_License
      in the image.
      Hint: docker exec -it a4h less /SAP_COMMUNITY_DEVELOPER_License
      
      WARNING: the following system limits are below recommended values:
        (sysctl vm.max_map_count = 262144) < 2147483647
        (sysctl fs.file-max = 524288) < 20000000
        (sysctl fs.aio-max-nr = 1048576) < 18446744073709551615
      Hint: if you are on Linux, consider running the following system commands:
        sudo sysctl vm.max_map_count=2147483647
        sudo sysctl fs.file-max=20000000
        sudo sysctl fs.aio-max-nr=18446744073709551615
      sapinit: starting
      start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile
      Impromptu CCC initialization by 'rscpCInit'.
        See SAP note 1266393.
      Impromptu CCC initialization by 'rscpCInit'.
        See SAP note 1266393.
      sapinit: started, pid=14
      
      HDB: starting
      Author's profile photo Ralf Henning
      Ralf Henning

      Hi Marian

      we tested it on an Apple with Intel CPU

      Fact is, creation of the container could take some time.

      Log stops at HDB: starting and continues several minutes later.

      Our test settings:

      Author's profile photo Jakub Filak
      Jakub Filak

      Start shell in the container and check HDB logs.

      I start shell in the container this way:

      docker exec -it a4h bash

      Then I would explore the logs at:

      • /usr/sap/HDB/HDB02/vhcala4hci/trace/DB_HDB
      • /usr/sap/HDB/HDB02/vhcala4hci/trace/

       

      I have no idea what to look for as the root cause can be anything and also I am not strong in SAP HANA. Therefore analyzing the logs is up to you.

      Author's profile photo Tom Höpping
      Tom Höpping

      Jakub Filak Jakub, I'm trying to start up the container on Mac M1 using the docker/rosetta emulation to emulate an intel architecture. Right after startUp I get the following error. I've checked the container and basically only the abaptrialinit process is running. Do you have any hint for me, where I can start the investigation?
      It seems that HDB Logfiles are empty/not created at this point in time.

      Author's profile photo Guilherme Gaino Galindo
      Guilherme Gaino Galindo

      That's normal, it does take some time to initialize the DB. Especially if you use it on Virtual Machine (like I do) with 16GB of RAM. Mine took circa 5 min.

      Author's profile photo Andrii Senko
      Andrii Senko

      Hi Marian

      Assume it started well and something also doesn't work. I got the same situation with Apple Silicon.

      But if you run 'docker ps' command it looks good:

      CONTAINER ID   IMAGE                            COMMAND                  CREATED       STATUS          PORTS                                                                                                                                                         NAMES
      adc92cf3fc9e   sapse/abap-platform-trial:1909   "/usr/local/bin/abap…"   2 hours ago   Up 24 minutes   0.0.0.0:3200->3200/tcp, 0.0.0.0:3300->3300/tcp, 0.0.0.0:8443->8443/tcp, 4237/tcp, 0.0.0.0:30213->30213/tcp, 0.0.0.0:50000-50001->50000-50001/tcp, 30215/tcp   a4h
      

      I also can run rcscc_daemon after that:

      docker exec -it a4h bash /usr/local/sbin/rcscc_daemon start
      Starting scc_Daemon
      
      scc_Daemon started.

       

      But nothing works then.

       

      SAP GUI/ Esclipt / SAP Cloud Connector (for localhost:8443 or 127.0.0.1:8443 in a browser)

       

      the server log file /usr/sap/HDB/HDB02/vhcala4hci/trace/DB_HDB/sapstartsrv.log (as recommended by Jakub below) does not contain anything suspicious

      ---------------------------------------------------
      trc file: "sapstartsrv.log", trc level: 0, release: "753"
      ---------------------------------------------------
      pid        537
      
      [Thr 274973443648] Fri Aug  4 19:21:58 2023
      HistoryLog_Init: logfile (/usr/sap/HDB/HDB02/vhcala4hci/trace/history.glf) already exists, check parameter
      No halib defined => HA support disabled
      CCMS agent initialization: WARNING: cannot recognize instance type, checking profile parameter "system/type".
      CCMS agent initialization for instance type ABAP: return code 0.
      CCMS agent disabled by profile parameter ccms/enable_agent = 0.
      Initializing SAPControl Webservice
      Root PSE verification succeeded
      [Thr 275041695488] Fri Aug  4 19:21:59 2023
      Auto PSE update thread started
      Starting AutoRestart thread
      Starting WebService SSL thread
      AutoRestart thread started
      Starting WebService thread
      Webservice SSL thread started, listening on port 50214
      Webservice SSL thread using system PKI credential
      Trusted https connect via Unix domain socket '/tmp/.sapstream50214' enabled.
      Webservice thread started, listening on port 50213
      Trusted http connect via Unix domain socket '/tmp/.sapstream50213' enabled.
      
      trusted unix domain socket user is starting SAP System at 2023/08/04 19:22:21

      Have you made any more progress?

       

      Author's profile photo Saurabh Kabra
      Saurabh Kabra

      Hi Jakub Filak / Ralf Henning

      I am also facing exactly the same error on Mac M1 pro. When I use "docker ps" then I can see that container is up&running.

      I also checked the HDB logs and no errors there as well.

      I have tried with the following connection string in SAP Gui 7.70rev6(for mac) but none working.

      conn=/H/0.0.0.0/S/3200
      conn=/H/127.0.0.1/S/3200
      conn=/H/localhost/S/3200

      Further, when I https://127.0.0.1:50001 or https://127.0.0.1:50000 then also i dont get back any response. Can you please help us how to get this launch via SAP GUI?

      Author's profile photo Sadullah TANRIKULU
      Sadullah TANRIKULU

      Hey MAC users, I needed to say this, probably you already did it. Use ping command to check docker running IP and OS localhost IP. If all is fine, please check permissions/firewall if any. I assume that your port numbers are correct.

      Author's profile photo Andrii Senko
      Andrii Senko

      Hello Sadullah and guys.

      I found this https://github.com/docker/for-mac/issues/2670

      and it looks like this problem has a long story. So I intend to investigate this SOCKS server solution tomorrow.ChatGPT

      But I'm worried it might end up taking more time than I thought.

      Author's profile photo Andrii Senko
      Andrii Senko

      Unfortunately, the attempted SOCKS proxy solution didn't yield the desired results.

      Although I'm not well-versed in Linux, I made an effort to assess these services from within the VM as follow:

      docker exec -it a4h bash

      and then just:

      :/ # curl localhost:50001
      curl: (7) Failed to connect to localhost port 50001: Connection refused
      :/ # curl localhost:8443 
      curl: (7) Failed to connect to localhost port 8443: Connection refused
      :/ # curl 172.17.0.2:8443
      curl: (7) Failed to connect to 172.17.0.2 port 8443: Connection refused
      :/ # curl 172.17.0.2:50001
      curl: (7) Failed to connect to 172.17.0.2 port 50001: Connection refused
      :/ # curl 172.17.0.2:3200 
      curl: (7) Failed to connect to 172.17.0.2 port 3200: Connection refused

      I'd really appreciate it if someone who's had success running SAP GUI or other services with this setup could give this exercise a shot.

      I'm not sure whether you got the same localhost IP inside the container, but you can use this command to check:

      docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}' a4h

      PING 172.17.0.2 (172.17.0.2) 56(84) bytes of data.
      64 bytes from 172.17.0.2: icmp_seq=1 ttl=64 time=0.114 ms
      64 bytes from 172.17.0.2: icmp_seq=2 ttl=64 time=0.053 ms
      64 bytes from 172.17.0.2: icmp_seq=3 ttl=64 time=0.057 ms
      64 bytes from 172.17.0.2: icmp_seq=4 ttl=64 time=0.059 ms

       

       

      Author's profile photo jinhui Gong
      jinhui Gong

      Has anyone run it successfully on a Macbook Pro M1 ???

      My terminal keeps stopping at HDB: starting.

      Author's profile photo Andrii Senko
      Andrii Senko

      That's ok.

      You can run: "docker ps" command and see in STATUS column something like "Up 1 min".

      Now try to set up a connection with SAP GUI.

       

      P.S. Anyway it doesn't help me start using SAP GUI, Eclipse, or HTTP clients from outside despite the fact that all services are running:

      :/usr/sap/A4H/ASCS01/exe # ps -ef |cat
      UID        PID  PPID  C STIME TTY          TIME CMD
      root         1     0  0 07:04 ?        00:00:01 /usr/bin/qemu-x86_64 /usr/local/bin/abaptrialinit /usr/local/bin/abaptrialinit -skip-limits-check
      root        13     0  0 07:04 pts/0    00:00:00 /usr/bin/qemu-x86_64 /bin/sh /bin/sh
      root       159     1  0 07:05 ?        00:00:14 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/saphostexec /usr/sap/hostctrl/exe/saphostexec pf=/usr/sap/hostctrl/exe/host_profile
      sapadm     292     1  0 07:05 ?        00:00:47 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/sapstartsrv /usr/sap/hostctrl/exe/sapstartsrv pf=/usr/sap/hostctrl/exe/host_profile -D
      root       498     1  0 07:05 ?        00:00:45 /usr/bin/qemu-x86_64 /usr/sap/hostctrl/exe/saposcol /usr/sap/hostctrl/exe/saposcol -l -w60 pf=/usr/sap/hostctrl/exe/host_profile
      hdbadm     571     1  0 07:05 ?        00:00:24 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapstartsrv /usr/sap/HDB/HDB02/exe/sapstartsrv pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci -D -u hdbadm
      a4hadm    1099     1  0 07:05 ?        00:00:49 /usr/bin/qemu-x86_64 /usr/sap/A4H/D00/exe/sapstartsrv /usr/sap/A4H/D00/exe/sapstartsrv pf=/usr/sap/A4H/SYS/profile/A4H_D00_vhcala4hci -D -u a4hadm
      a4hadm    1570     1  0 07:05 ?        00:00:39 /usr/bin/qemu-x86_64 /usr/sap/A4H/ASCS01/exe/sapstartsrv /usr/sap/A4H/ASCS01/exe/sapstartsrv pf=/usr/sap/A4H/SYS/profile/A4H_ASCS01_vhcala4hci -D -u a4hadm
      hdbadm    1872     1  0 07:06 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapstart sapstart pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci
      hdbadm    1900  1872  0 07:06 ?        00:00:36 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/vhcala4hci/trace/hdb.sapHDB_HDB02 /usr/sap/HDB/HDB02/vhcala4hci/trace/hdb.sapHDB_HDB02 -d -nw -f /usr/sap/HDB/HDB02/vhcala4hci/daemon.ini pf=/usr/sap/HDB/SYS/profile/HDB_HDB02_vhcala4hci
      hdbadm    1945  1900  0 07:06 ?        00:00:24 [hdbnameserver] <defunct>
      root      4755     0  0 07:25 pts/1    00:00:02 /usr/bin/qemu-x86_64 /usr/bin/bash bash
      root     11428  4755  0 08:09 pts/1    00:00:00 /usr/bin/qemu-x86_64 ./sapstart ./sapstart name=TST nr=00 sapdiahost=test
      root     11431 11428  0 08:09 ?        00:00:00 [sapstart] <defunct>
      root     52810     1  2 12:50 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/bin/su /usr/bin/su - hdbadm -c sapcontrol -nr 02 -function StartWait 3600 2
      hdbadm   52819 52810  1 12:50 ?        00:00:00 /usr/bin/qemu-x86_64 /usr/sap/HDB/HDB02/exe/sapcontrol sapcontrol -nr 02 -function StartWait 3600 2
      root     53014  4755  0 06:45 ?        00:00:00 ps -ef
      root     53016  4755  4 12:50 pts/1    00:00:00 /usr/bin/qemu-x86_64 /usr/bin/cat cat
      Author's profile photo Tom Höpping
      Tom Höpping

      Andrii Senko Hi Andrii, are you sure that everything is running, if I look into the log files it seems for me that there are some errors, beside that from a process side it looks like the same.

      Author's profile photo Andrii Senko
      Andrii Senko

      You're right, Tom.. I found this later yesterday.

      I add some logs about this in the comment to this question https://answers.sap.com/questions/13945356/abap-platform-trial-1909-on-mbp-m1.html

      Unfortunately, I have no ideas how to fix it yet.

      Author's profile photo Tom Höpping
      Tom Höpping

      Yeah, right. Have the same findings and no clue how to fix this.
      I've also tested to turn on rosetta 2 emulation and virtio storage drive instead of quemu for intel/x86 based images. But this leads to an error, right in the abaptrialinit init script, very early. So no sap-log files were created. Basically abaptrialinit is the only process which is running.

      Jakub Filak Do you have some input here for us, where to start analysing?

       

      What I can confirm is, that the image is running using utm emulating a linux/intel machine. But bad performance compared to running the image on a native intel machine.

      Author's profile photo Jakub Filak
      Jakub Filak

      I am sorry folks but running SAP HANA in an emulator in a vm in a docker does sound super fragile. However, the user for starting SAP HANA is hdbadm and not sapadm. abaptrialinit start the DB using this command:

      su - hdbadm -c sapcontrol -nr 02 -function StartWait 3600 2
      Author's profile photo Andrii Senko
      Andrii Senko

      Tom.

      What if we try to pinpoint the problem? I'm thinking that some libraries might not play nice with the M1. But here's the thing: I'm more of a functional person trying to set up a dev environment "out front," and I'm not super confident with the Basis stuff.

      I found this clarification and tried to start each process manually:

      https://wiki.scn.sap.com/wiki/display/SAPHANA/SAP+HANA+System+Down%2C+HANA+not+starting

      There were only two places with HDB:

      /hana/shared/HDB/global/hdb/install/support/HDB
      /hana/shared/HDB/HDB02/HDB

      I have some doubts that the current description corresponds to this setup but tried anyway:

      :/hana/shared/HDB/HDB02 # sudo -u sapadm ./HDB start
      hdbenv.sh: Host name not found out of /usr/sap/sapservices, defaulting to local physical host
      hdbenv.sh: Error: Instance not found for host vhcala4hci
      ERROR: SAP_RETRIEVAL_PATH missing: 

      I'm going to find out what it means first.

      grep -rnw '/usr/sap/' -e 'SAP_RETRIEVAL_PATH'
      Binary file /usr/sap/hostctrl/exe/sapacosprep matches
      Binary file /usr/sap/hostctrl/exe/libSQLDBCHDB.so matches
      Binary file /usr/sap/hostctrl/exe/libsapdbhdbctrl.so matches
      Binary file /usr/sap/A4H/hdbclient/libdbcapiHDB.so matches
      Binary file /usr/sap/A4H/hdbclient/libSQLDBCHDB.so matches
      Binary file /usr/sap/A4H/hdbclient/hdbsql matches
      Binary file /usr/sap/A4H/hdbclient/regi matches
      Binary file /usr/sap/A4H/hdbclient/hdbkeystore matches
      Binary file /usr/sap/A4H/hdbclient/node/prebuilt/linuxx86_64-gcc48/libdbcapiHDB.so matches
      Binary file /usr/sap/A4H/hdbclient/pyhdbcli.so matches
      Binary file /usr/sap/A4H/hdbclient/hdbuserstore matches
      Binary file /usr/sap/A4H/hdbclient/install/instruntime/SQLDBC.so matches
      Binary file /usr/sap/A4H/hdbclient/libodbcHDB.so matches
      :/usr/sap # echo $SAP_RETRIEVAL_PATH
      
      :/usr/sap # 
      

      On this step, I can't believe that it works on intel without this variable and doesn't on M1.

      Any suggestions?

      Author's profile photo Tom Höpping
      Tom Höpping

      Hi @Saurabh Kabra 
      Are you running on MAC M1 -> what parameters are you using docker?
      -> Virtualisation Framework switched on?
      --> With Quemu evaluation or new Rosetta Emulation?
      --> Which storage driver are you using?

       

      Interesting side fact, I'm not able start the HDB, it always stucks somewhere and log files are indicating that there was an error during creation of storage layer of nameserver.
      But with AS Only Option, I'm able to start the application server at least.

       

      Author's profile photo Andrii Senko
      Andrii Senko

      Hello Tom.

      Am I right that you made a "sandwich" like this:

      Macos(M1) ->Rossetta ->Podman VM ->Fedora ->Docker ->Suse -> HanaDB

      Something, as described here:

      https://developer.ibm.com/tutorials/running-x86-64-containers-mac-silicon-m1/

      BR,

      A.

      Author's profile photo Marian Zeis
      Marian Zeis

      Tom.

      Made it work with UTM and Debian like described here:

      https://blogs.sap.com/2021/12/16/how-to-install-abap-1909-on-mac-m1-apple-silicon/

      I changed the standard processor to Intel i7

      Author's profile photo Tom Höpping
      Tom Höpping

      Right. In this setup UMT emulates an intel based machine with ubuntu/docker installation.

      The other approach is to run docker native on apple silicon with rosetta emulation switched on. But there I've have problems, starting the Hana DB.

      Author's profile photo Marian Zeis
      Marian Zeis

      Tom.

      I had the same problem. Did not work in any case and moved to UTM.
      May they address it with the next trial version

      Author's profile photo Rafael Caziraghi
      Rafael Caziraghi

      Big thanks to the team for releasing the ABAP Platform Trial 1909 - it's what we've all been waiting for! It's really cool that you've been working with the SAP Mentors and DSAG to shape it. Looking forward to the next releases!

      Author's profile photo Balint Szebenyi
      Balint Szebenyi

      Do we need an AS ABAP license if we intend to use the container multiple times and for a few months? If so how to obtain one? (I know about License Key in sap for me, but I doubt that for such an instance this would be the way or is it?)

      It seems to be valid to 10.31. So by design it can be used till the new release is not available?

      Author's profile photo Martin Fischer
      Martin Fischer

      Hi Balint,

      it comes with a free developer license. No need to obtain a license in SAP for me.

      I didn't get your last question, maybe you can rephrase it.

      Cheers,

      Martin

      Author's profile photo Balint Szebenyi
      Balint Szebenyi

      Thanks, it is okay then, just the docker install guide mislead me a bit with this. It starts just fine this way out of the box.

      The last question referred to the license being valid till 2023.10.19 and above in the intro you have written that you plan to release a 2022 version of this ABAP Platform trial. I just suspected from this that this validity end date is intentional and makes the image usable till the new version of ABAP Platform trial appears.

      Author's profile photo Ralf Henning
      Ralf Henning

      Get a fresh license here:

      https://go.support.sap.com/minisap/#/minisap

      Call transaction slicense to replace existing one.

      The  license the system comes up with is a temporary one. You need to replace it before you can start to develop.

      Transaction slicense supports you with the hardwarekey. 

      SAP trial license can be renewed several times. It's valid for 3 month.

       

      License%20container%20comes%20up%20with

      License the container comes up with

       

      License%20after%20applying%20a%20trial%20license

      License after applying a SAP trial license

       

      The SAP Hana license expires end of next year. No need to replace the next time 😉

      Author's profile photo Balint Szebenyi
      Balint Szebenyi

      Sorry for the late reply but thanks for the info!

      Author's profile photo Vladislav Kustov
      Vladislav Kustov

      Appreciation to all who made it possible!

      Author's profile photo Jacques Nomssi Nzali
      Jacques Nomssi Nzali

      your efforts to simplify and streamline the installation process paid off. For me it was the smoothest installation for a trial sofar.

      Thanks to your whole team and every helper for the hard work! I look forward to seeing you keep this level on with future releases.

      Best regards,

      JNN

      Author's profile photo Kai Sicker
      Kai Sicker

      Kudos from my side as well !

      Author's profile photo yin he
      yin he

      password for my login account? I am unable to log in

      Author's profile photo Ralf Henning
      Ralf Henning

      Have a look at  https://hub.docker.com/r/sapse/abap-platform-trial overviewpage/sapgui

      Here you will find you're looking for.

      Author's profile photo yin he
      yin he

      Thank you, I saw it

       

      Author's profile photo Guilherme Gaino Galindo
      Guilherme Gaino Galindo

      Successfully run on Virtual Box 7.0 running OpenSUSE Leap 15.5. Virtual Machine: 16GB of RAM and 200GB of disk space.

      You do need to install Docker and dependencies first then pull the image.

      It takes some time to initialize HDB, so be patient.

      Also you will need to route IPs on Virtual Box to your local machine before launching SAP GUI.

      Author's profile photo Ruthiel Trevisan
      Ruthiel Trevisan

      A big thank you for this!

      Author's profile photo Ralf Henning
      Ralf Henning

      Don't forget to update your local hosts file:

      <local host> vhcala4hdb vhcala4hdb.dummy.nodomain vhcala4hci vhcala4hci.dummy.nodomain vhcala4hcs vhcala4hcs.dummy.nodomain

      ->

      127.0.0.1  vhcala4hdb vhcala4hdb.dummy.nodomain vhcala4hci vhcala4hci.dummy.nodomain vhcala4hcs vhcala4hcs.dummy.nodomain

      hosts%20file%20on%20windows

      hosts file on windows

       

      Relevant to fiori scenarios

      Author's profile photo Martin Eckhardt
      Martin Eckhardt

      Thanks to the SAP team who made this possible.
      The system runs successfully with the operating system Ubuntu 20 LTS and virtualized in VMWare Workstation 15.

      Author's profile photo Rajarshi Muhuri
      Rajarshi Muhuri

      This is great.

       

      Is there any way , we could access the HANA DB directly also , and could the credentials be shared ?

      Author's profile photo Andrii Senko
      Andrii Senko

      Hello

      Here is a separate question for Mac user's issues with this topic:

      https://answers.sap.com/questions/13945356/abap-platform-trial-1909-on-mbp-m1.html

      Many thanks to everyone who can help with this.

      BR,

      A

      Author's profile photo SHU FANG
      SHU FANG

      I am looking forward to when I can run it on k8s

      Author's profile photo Peter Matthews
      Peter Matthews

      Many thanks for the efforts by the team.

      Where can we find the abap trial roadmap?

      More specifically, when can we expect the 2022 trial to be made available?

      Author's profile photo Mark Angelier
      Mark Angelier

      Hi,

      First of all a big thanks for bringing this back!

      Been playing around again for a while now since it is back. I have one minor thing which I cannot get solved. After I have shut down the container, almost never happens of course, I have issues getting it started again.

      When I start it again it starts to complain FAIL process disp+work Dispatcher not running. I found a post saying it could be basically 2 things.

      1 Memory

      2 License

      As it was runnign fine I suspect number 2. However I did put in the license and during the start it tells me it is there.

      Has anyone had this as well? I have tried copying the license file in but no luck so far...

      I hope someone has the golden hint here.

      Thanks in advance

      Mark

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Mark,

      I apologise for the delay. I may not be able to help, but what HW do you have?

      These are the requirements. Please note that "16 GB is *dedicated to Docker*. ie NOT 16 GB on the machine.

      I understand that it worked before, but there may be several reasons for that - what else was running etc.

      When you reply, could you please NOT reply to this comment, but rather create a question on the ABAP Development forum : ABAP Development: Ask a Question , using the hashtag #ABAP_Trial.

      This will mean that more users, including some real experts, will see your question.

      Best wishes,

      Julie Plummer.

      Linux

      • 4 CPUs
      • 16GB RAM
      • 150GB Disk

      Windows

      • 4 CPUs for Docker Desktop
      • 16GB for Docker Desktop
      • 170GB disk for Docker Desktop

      macOS

      • 4 CPUs for Docker Desktop
      • 16GB for Docker Desktop
      • 170GB disk for Docker Desktop
      Author's profile photo Elias Kekakos
      Elias Kekakos

      Hello and thanks all for this training environment. I have the following problem when I am ruining the following command.

      PS C:\Windows\system32> 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 sapse/abap-platform-trial:1909 -skip-limits-check -agree-to-sap-license

      and the error

      docker: Error response from daemon: Ports are not available: exposing port TCP 0.0.0.0:8443 -> 0.0.0.0:0: listen tcp 0.0.0.0:8443: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.

      And the Docker looks as following

      SAP%20in%20DOCKER

      SAP in DOCKER

      And when I run it I am getting the same error

      Docker%20SAP%20Error

      Docker SAP Error

      Can you help me how to overcome this problem?

      Thanks in advance

      Elias

      PS: I found that the 0.0.0.0:8443 is used by CLOUD CONNECTOR HOST SERVICE. How can I solve?

      Author's profile photo Andrea Borgia
      Andrea Borgia

      You already have some other process listening on that address/port, be that another docker container or something completely unrelated, and docker is informing you that you cannot use it more than once. Solution is finding the other usage and stopping it or changing the mapping (not sure if this will work here!)

      Author's profile photo Karl Kessler
      Karl Kessler
      Blog Post Author

      Hi Elias,

      Andrea explained the reason very well.

      Please have a look in your Windows services whether a SAP Cloud Connector is running on your laptop. This needs to be stopped before running the docker container.

      Author's profile photo Elias Kekakos
      Elias Kekakos

      Thanks for your valuable help. I did what you are saying and everything are working perfect.

      Author's profile photo Bernd Köhn
      Bernd Köhn

      Hi, many thanks to all those who are involved to make it available. I run it on a HP EliteBook 8570w 32GB with Debian 12. Best regards. Bernd Köhn

      Author's profile photo Igor Garanichev
      Igor Garanichev

      Thank you, Karl!

      Finally, it works!

      System configuration is:

      Docker settings:

      In my case, neither WSL nor WSL2 did not work. I upgraded my Win10 Home to Pro and enabled Hyper-V.

       

      Author's profile photo Fabian Beiser
      Fabian Beiser

      Hi all,

      first of all thank you for making the ABAP Platform Trial available again.

      • Does my HP EliteBook 840 G6 with 32GB RAM, 256GB SSD and Intel I5-8365U processor fullfill the needed requirements?Seems like the processor is too weak, right?
      • With the ABAP Platform Trial I am able to create own Z-Reports and even try different customizing settings?

      Best Regards

      Fabian

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Fabian,

      I see Karl has answered your question below.

      I hope this worked out for you.

      If you haven't yet opened up the ABAP Platform Trial, then yes: You can create Z-Reports, other Z-objects etc. I have not looked at IMG in the Trial, but I can't see why that shouldn't work too.

      Best wishes,
      Julie.

      Author's profile photo Karl Kessler
      Karl Kessler
      Blog Post Author

      Hi Fabian,

      please give it a try if you don't mind. I tested the docker image on an old Lenovo with XEON E-2176 processor and 32 GB RAM successfully. i5 is in a comparable range (depends on other factors such as clock speed etc).

      It takes some minutes to come up, so please be patient, but once it is up and running (ABAP tables loaded into HANA) it works well.

      Best regards

      Karl

      Author's profile photo First Name Last Name
      First Name Last Name

      Is Restful ABAP (RAP) available on that release?

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi First Name Last Name,

      Sorry for the delay.

      This version of ABAP Platform Trial ships with the version of RAP available with 1909.

      This presentation will show you exactly what is available (slide 28 onwards):

      https://www.sap.com/documents/2019/10/cefaa4bb-6c7d-0010-87a3-c30de2ffd8ff.html

      We are currently working on ABAP Platform Trial 2022, which will naturally offer a more mature version of RAP - which you can see here (slide 30 onwards):

      https://www.sap.com/documents/2022/11/ce1e8111-527e-0010-bca6-c68f7e60039b.html

      Hope this helps, Julie.

       

       

      Author's profile photo Ahmet Figen
      Ahmet Figen

      Hello everyone,

       

      I set up the GUI properly, but I cannot call/see TEXT_CONVERT_XLS_TO_SAP function. What did I miss? Thank you in advance.

      Author's profile photo Andrea Borgia
      Andrea Borgia

      The boat 🙂

      Seriously, that is an obsolete function and I am not surprised to see it gone in a demo system.

      It is also not present in the older NPL, time to look for a real solution 🙂

      Author's profile photo Ahmet Figen
      Ahmet Figen

      Hello Andrea,

      Thank you for the quick response and recommendation. You are right, obviously I missed the boat 🙂 I have been following a tutorial series, and it was a new topic for me. I will figure it out.

      Author's profile photo Julie Plummer
      Julie Plummer

      Hi Ahmet,

      Have you looked at this:

      https://github.com/abap2xlsx/abap2xlsx ?

      I have not tried it myself.

      Best wishes,

      Julie.

      Author's profile photo Ahmet Figen
      Ahmet Figen

      Hi Julie,

      Thank you so much. I will look at it.

      Regards,

      Ahmet

      Author's profile photo rama anne
      rama anne

      Hi kressler and other sap community members here


      Thanks for SAP ABAP AS HANA 1909 DEV docker hub image  after a period of inactive state

      I want to know how I can save hanadb persisted may be using Docker volumes either named or bind ,that is even if started container is removed and a new container (a4h) started again ,the sap hana db data must be still accessible not lost ,say for example  I loaded some tables with data using SDI or SLT replication from another sap instance.

      can someone provide clues or steps

      thanks & regards

      rama anne

      Author's profile photo Guilherme Gaino Galindo
      Guilherme Gaino Galindo

      Hi,

      I did it. I tried many folders to mount a volume but what worked for me, at least for now, was attaching it to the root:

      -v hana:/hana

      First you need to create a volume on docker, in my case I used "hana":

      docker volume create <ID>

      If you look inside docker container "a4h" you will see the following structure under hana directory:

      vhcala4hci:/hana # ls
      data  log  shared
      
      vhcala4hci:/hana # du --max-depth=1 -h 
      38G     ./data
      2.2G    ./log
      7.9G    ./shared
      48G     .

      Not sure if this is the optimal way, but I've killed, started/restarted the container many times and my data was still there.

      Author's profile photo rama anne
      rama anne

      Hi Gulherme

      thats great and I will try out your steps and see how it goes (create ztable ,delete container and create a new container )

       

      as a side note it seems docker has commit command and also save

      it looks like container snapshot backed up as a image file(tar) which can be restored

      but i prefer bind mount volume as you have done

      thanks & regards

      rama anne

      Author's profile photo Ferda Tuluay
      Ferda Tuluay

      Hi,

      does anyone have experience with mac m2 max? if this works with the M2-Apple Chip.

      i do not know if that is the problem. Mine doesn't start.

       

      Please, type either Read, Accept, or Refuse: Accept
      WARNING: the following system limits are below recommended values:
        (sysctl kernel.shmmni = 4096) < 32768
        (sysctl vm.max_map_count = 262144) < 2147483647
        (sysctl fs.file-max = 524288) < 20000000
        (sysctl fs.aio-max-nr = 1048576) < 18446744073709551615
      Hint: consider adding these parameters to your docker run command:
        --sysctl kernel.shmmni=32768
      Hint: if you are on Linux, consider running the following system commands:
        sudo sysctl vm.max_map_count=2147483647
        sudo sysctl fs.file-max=20000000
        sudo sysctl fs.aio-max-nr=18446744073709551615
      sapinit: starting
      start hostcontrol using profile /usr/sap/hostctrl/exe/host_profile
      Impromptu CCC initialization by 'rscpCInit'.
        See SAP note 1266393.
      Impromptu CCC initialization by 'rscpCInit'.
        See SAP note 1266393.
      sapinit: started, pid=14
      
      HDB: starting
      
      Author's profile photo Marian Zeis
      Marian Zeis

      Had the same problem. You need to use UTM like described here https://blogs.sap.com/2021/12/16/how-to-install-abap-1909-on-mac-m1-apple-silicon/