Software Delivery

This is a repost of an article originally posted to the SAP Community Network. This is the second part of my answer to Christian Drumm’s question What System Landscapes Setup to use for Add On Development? - and probably more of an answer to the original question than the first part. At the moment, many authors choose to place obscure references to Trifluoroacetic acid (or TFA for short) in their blogs, but since this post will be about rather fundamental aspects, I’d like to choose a different setting. ...

This is a repost of an article originally posted to the SAP Community Network, extended by a proposal I made later in the discussion. Introduction In the last years, ABAP development has become a lot easier. The individual developer’s perspective has improved considerably through advanced tooling (ADT!), better online documentation and community support. When I started ABAP development around 2001, you still needed a dedicated machine with quite a price tag only to run the development system of our landscape at a decent speed. Today, that’s easily accomplished using a virtual machine, even on cheap off-the-shelf hardware (which is obviously not recommended for a production system, but hey – what do you think the average Hudson CI server in a small development shop runs on?). With pre-packaged demo systems, a complete ABAP development environment is in reach for most people – I just installed a system a within a few hours (including downloading 15 GB of installation files, setting up the VirtualBox server and the underlying OS, while doing other stuff alongside). If you don’t want to run the system on your own hardware, you can get a CAL account and run the systems in the cloud as well. ...

If you’re setting up a linux box to run an Eclipse PDE headless build and by choice or accident end up using a Debian system and again by choice or accident installed the OpenJDK, you’ll probably see the following p2 director error message after enabling the p2 integration: One or more certificates rejected. Cannot proceed with installation. This message does not contain a wealth of information, it doesn’t even state which certificates where rejected. Even more bizarre is the fact that this message appears even if you turned code signing off. The reason for this can be found buried inside the OpenJDK web site: ...

If your product-based Eclipse PDE Headless Build seems to work just fine and creates some archives with files and executables inside, you might still experience one ugly problem: Unable to acquire application service. Ensure that the org.eclipse.core.runtime bundle is resolved and started (see config.ini) This message will appear in the error log, brought to you by a very plain dialog box. You can solve this problem by editing the product definition file. In the Configuration section, add the plug-in org.eclipse.core.runtime to the list. ‚Then enable Auto-Start and set the Start Level to 2. Since the default start level of OSGi bundles is 4, this will ensure that this plug-in is loaded before the others. ...