As before, we are offering a free, downloadable ABAP Platform on SAP HANA 2.0 for trying out the ABAP language and toolset. It is extensively pre-configured with SAP Fiori launchpad, SAP Cloud Connector, pre-configured backend /frontend connections, roles, and sample applications.
This solution is intended for two groups of developers:
Non-ABAP developers, who are interested in learning more about the ABAP language and development tools
ABAP developers, who are interested in learning about new features (see below for some examples)
You understand the principles of docker container technology
You know the entities docker image / docker container and their relationship
You know the basic commands to work with images and containers
The ABAP license supplied with the Docker image lasts only three months. Therefore, you should download and import the demo license as follows:
Logon to your ABAP system with the user SAP*, client 000, same password as for DEVELOPER (DEVELOPER , client 001, is locked).
Start transaction SLICENSE; copy the hardware key.
Get the license from minisap , choosing the system A4H.
Back in your ABAP System, log off, then log on with the user DEVELOPER, client 001.
The old ("INITIAL") license(s) should be deleted automatically. If not, start SLICENSE again; remove the old invalid licenses. (sap* is not allowed to delete licenses).
Highlights of the 1909 Edition
ABAP RESTful Application Programming Model (RAP)
ABAP RESTful Application Programming Model – The Big Picture
The ABAP RESTful Application Programming Model (short: RAP) offers developers an efficient way to build enterprise-ready, SAP HANA-optimized, OData-based Fiori UI services and Web APIs in the cloud as well as on-premise. It is the evolutionary successor to the ABAP Programming Model for SAP Fiori.
A new way of transporting objects, gCTS enables you to use Git to store your ABAP development objects. gCTS makes use of special Git features, such as working on local copies of a central remote Git repository. Software development takes place in the usual editors like ABAP Development Tools (ADT). Changes to objects are still recorded in transport requests. Current states of objects can be pushed to remote Git repositories, either by releasing a transport request or while you’re working.
For more general information on gCTS, see this blog post: gCTS is here, by karin.spiegel
Some certificates are already available. If you would like to connect to your own GitHub server or to a provider other than github.com, you have to add the appropriate certificates to the ABAP system in transaction STRUST. The configuration has been done for the default user ‘DEVELOPER’.
To get started with gCTS, simply open the gCTS app in the SAP Fiori Launchpad (FLP).
If you are a SAP customer, partner, or employee, the following SAP Note provides additional information: SAP Note: 2821718 . However, the essential configuration has already been done for everyone.
Custom Code Migration with the ABAP Test Cockpit (ATC)
We've pre-configured ABAP Platform Trial to run as a central check system for checking your custom code prior to migration - particularly useful for:
SAP S/4HANA Readiness Checks
SAP Cloud Readiness Check.
You can test this out of the box locally in SAP ADT, then configure the rest of your landscape to work with it.
For more general information on ATC, see these two excellent blogs, by olga.dolinskaja:
SAP Cloud Connector provides a link between SAP Business Technology Platform (BTP) applications and on-premise systems. It runs as on-premise agent in a secured network; acts as a reverse invoke proxy between the on-premise network and SAP BTP; and lets you use existing on-premise assets without exposing the entire internal landscape.