NEO Cloud Deployment and Configuration

Deploying and running your applications to the SAP Cloud Platform (SCP) requires the base FAB application to be installed.  The FAB application is provided as a ZIP file that can easily be imported.  Once the core application is installed, it will allow you to run any of your dynamic applications without the need for further application installation.  The only requirement for this is that SCP's OData Provisioning Service is used to serve up all your OData services.  If the services are being served from the SAP Gateway system on-premise, then special care must be taken in how the service URLs are referenced as in an SCP deployment, the application is running in the SCP space (https://[app-name] and the services will be served from another server.  This means that relative URLs will not work in this scenario.


Those apps requiring the best performance via the use of standard caching techniques are candidates for individual installation into the SCP platform.  Instructions to install individual applications is described below.

The FAB application consists of the following UI5 Apps the require deployment to SCP:

  • Fab App - BSP: /IQX/FAB2
  • Icon picker – BSP: /IQX/FAB_ICONS
  • J editor (for data report) – BSP: /IQX/JSON_EDIT
  • Process editor – BSP: /IQX/PROCESS_EDIT

Each of the apps should be installed on the cloud platform following the instructions below.  Please note that the Icon Picker, Jason Editor, and Process Editor apps do NOT need to be configured onto the Fiori launchpad.

Post-deployment, the above three apps need to be configured in the IQX FAB Configuration: /IQX/FAB_CONFIG →Editors (See below)

Installing the FAB Application into your SCP Instance

  1. Log into the SAP Cloud Platform Cockpit
  2. Expand the Applications menu group on the side and select HTML5 Applications

  3. Select the Import from File option
  4. Upload the FAB SCP Install ZIP file and provide details for the Application Name (fab) and Version Name (Version number in major.minor.patch format.  e.g. 2.3.0)

  5. Once the upload is complete, ensure the application shows "Started" in the status column.  The application is not started, click the play button in the actions column.



Installing the FAB Framework into SCP Instance (correct steps)

  1. Log into the SAP Cloud Platform Cockpit
  2. Open WebIDE
  3. From the Menu select File → Import → File or Project
  4. Select the file to import (supplied by IQX)
  5. Select/Enter the Import folder (e.g. /fab)
  6. Once the import has completed, right-click on the new fab project in the Workspace tree
  7. Select Deploy → Deploy to SAP Cloud Platform
  8. Select Deploy a new application and click on Deploy
  9. After Deployment completed successfully, you have the option to Deploy the application to the SAP Fiori Launchpad (not required)
  10. Repeat steps 1 to 8 for the Icon Picker, Jason Editor, and Process Editor apps (only applicable to the Development environment)

Installing your Custom Applications into SCP

Option 1: Using Eclipse

  1. Convert the app to an offline application using the standalone and offline checkboxes in the property dialog within the FAB developer workbench.  (FAB already exists as a BSP/standalone application)
  2. Use Eclipse to extract the application.  (See here for details - Exporting an Application using Eclipse)
  3. Right-click the web-content folder and export to an archive.
  4. Open the archive and rename the web-content folder to webapp.  (Zip again if necessary)
  5. Open up the WebIDE full-stack.
  6. Create a new project.
  7. Right-click on the newly created project and use the Import from file option.
  8. Use the ZIP file you created.

Deploying FAB Core to SAP Systems lower than 740

This is the recommended approach when working on a SAP version lower than 740. The reason being is that the ADT service/node will not be available in those systems and using SAP WebIDE to access the SAPUI5 repository will not work.

Option 2: Using SAP WebIDE

  1. Convert the app to an offline application using the standalone and offline checkboxes in the property dialog within the FAB developer workbench.  (FAB already exists as a BSP/standalone application)
  2. Ensure you have a Destination created for the HTTP connection to the required SAP backend
  3. Open SAP WebIDE
  4. Go to the Home page
  5. At the bottom, there should be an Import from SAP UI5 Repository option
  6. Select the destination for the SAP system
  7. Search for the application and select it.
  8. After the import, right-click on the Web-Content folder and rename to webapp


 The neo-app.json file must be in the root of the folder.  When importing FAB2, there are instances where the file will be saved incorrectly inside the web-content/webapp subfolder.  It MUST be moved to the root!

You may also need to manually copy the following folders and files into the project once created.

  • /controls
  • /core
  • /scripts
  • /searchHelps
  • /Formatter.js
  • /userFunctions.js

FAB Configuration for Icon Picker, Jason Editor and Process Editor Apps.

Navigate to the /IQX/FAB_CONFIG transaction.  Open the Editors tab:

  1. Configure the JavaScript Editor URL

http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_script2/default.htm

Page across to the Left >

Configure JavaScript Editor Help URL:

http:// <SAPNWGWServer:port>/sap/bc/bsp/iqx/fab_help_s/index.html#File:fab.js

Page across to the Left >

2. Configure the Icon Picker URL:  https://fabicons-<ScpID>.dispatcher.<region>

e.g.  -

Page across to the Left >

3. Configure the Process (Workflow) Editor URL: https://processedit-<ScpID>.dispatcher.<region>

Page across to the Left >

4. Configure the JSON Editor URL:  https://jsonedit-<ScpID>.dispatcher.<region>