abapGit is available in 2 editions: standalone or development.
-
standalone version: for end users. It consists of a (huge) program that contains all the required code. The user runs the stand-alone version in transaction SE38, executing the created program.
-
Developer Edition: For developers who contribute to the abapGit codebase. It consists of all ABAP programs/classes/interfaces/etc. Developers can run the developer version using transaction ZABAPGIT. Only the developer edition supports parallel processing.
premise
ABAP Git requires SAP BASIS version 702 or higher.
菜单：SAP GUI Options > Interaction Design > HTML Control > Browser Control
Make sure to use IE:
Source code address: https://raw.githubusercontent.com/abapGit/build/main/zabapgit_standalone.prog.abap
When using the Internet Explorer-based HTML control, abapGit can run without restrictions on SAP GUI on Windows 7.60 or higher.
For SAP GUI on Windows 7.70 or later, there is an option to use Edge (based on Chromium) as HTML control.
In general, Git servers require a secure connection. Therefore, abapGit is using a secure connection over HTTPS to access the Git server.
NOTE: An insecure HTTP connection can be used but is strongly discouraged as the repository's contents will be visible on the web.
To support HTTPS, your SAP system must be configured accordingly:
- Enable HTTP/HTTPS service connection in SAP system profile
- Import Git server certificate into SAP trust manager
- If necessary, define an HTTP proxy server in the abapGit settings
The report zabapgit_test_ssl can be used to test an SSL connection to GitHub or any other Git server.
Expected output:
If your server is behind a proxy, you can maintain the proxy host and port here.
Do not enter any "http://" or "https://" prefixes for the proxy host. Just enter the hostname or its IP address.
If your proxy requires you to log in, set the proxy authentication flag. Then, when an online connection is required, abapGit will prompt you for a proxy user and password.