The SAPUI5 Repository technically bases on the BSP repository of the ABAP server. The BSP repository is only used as a repository or storage for SAPUI5 application files; the BSP runtime, however, is not used at runtime and, hence, the flow logic ABAP parts cannot be used as they are not executed at runtime.
The following sections describe how to use the SAPUI5 Repository and how to deploy the SAPUI5 application project on the ABAP Server. For this application type, the ABAP Server is used as a file share to serve browser requests.
The SAPUI5 repository is available in SAP Business Suite systems with version 7.00 or higher containing the user interface add-on for SAP NetWeaver, which contains the software component UI_INFRA. The team repository provider functionality, which is available in the Eclipse IDE, is available in SAP Business Suite systems with version 7.31 containing the user interface add-on, which contains the software components UI_INFRA and UI5_731.
The used SAPUI5 libraries are available in SAP Business Suite systems with version 7.00 or higher containing the UI add-on for SAP NetWeaver in the software component UISAPUI5.
As of SAP NetWeaver 7.4 SP1 all required SAPUI5 parts are already part of software component SAP_UI.
As an alternative for SAP Business Suite system of version 7.00 and higher you can use an interactive ABAP report offering similiar functionality. For more information, see the report documentation Using an Interactive ABAP Report to Synchronize.
When uploading the files to the SAPUI5 repository, you can perform a virus scan.
As of SAP NetWeaver 7.0, SAP delivers the following virus scan profile for ABAP with the UI Add-On: /UI5/UI5_INFRA_APP/REP_DT_PUT.
This profile is used by the SAPUI5 repository API to store files in the SAPUI5 repository based on BSP repository. For example: Upload of a local file using SAPUI5 repository API /UI5/CL_REP_DT, method /UI5/IF_UI5_REP_DT~PUT_FILE from SAP NetWeaver 7.0 on, or the SAPUI5 team repository provider in SAP NetWeaver 7.3 EHP1 or 7.40.
The profile is deactivated when delivered. To activate it, create at least one basis profile. You can then activate one of the delivered profiles. By default, it links to a reference profile, which is the default profile.
If you view the corresponding BSP pages on the ABAP server, they might look different to the version in Eclipse or at runtime:
Trailing spaces in text lines are escaped with "! " in the respective BSP pages.
Lines longer than 254 are broken into several lines and have a + on position 255.