2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Community

Ask a Question Write a Blog Post Login

Technical Articles

Andre Fischer
July 7, 2014 6 minute read

How to transport Fiori like applications using SAP Solution Managers Quality Gate Management
Follow RSS feed Like

12 Likes 15,382 Views 12 Comments

Authors

Max-Dirk Dittrich

Andre Fischer

Patrick Schmidt

Updates

22.03.2016 Added information how to make objects that reside in $TMP transportable.

Introduction

In this document we want to describe how to handle the software changes of a project that encompasses the development of

an OData service in SAP Gateway and

the development of a Fiori like SAPUI5 based consumer application

that is deployed on the SAP Gateway server using the Quality Gate Management (QGM) which is part of SAP Solution Manager.

The scenario described is also applicable to projects where SAP Fiori applications and the underlying SAP Gateway service are extended and where the changes need to be transported through
a typical 3-system landscape.

A big plus for both scenarios is that the complete life cycle management of a SAP Gateway service and the corresponding consuming SAP Fiori like application can be managed using the well
known SAP Change and Transport System of an ABAP system.

The only problem however is that service development and consumer application development are usually carried out by di erent developers. In addition complexity is added by the fact that
during the development process of an OData service repository objects and customizing data are created in the SAP Gateway Backend and SAP Gateway Server whereas the development
artefacts of the SAP Fiori like application are only created on the SAP Gateway Server.

As a result 1 customizing request and 3 workbench requests in 2 system landscapes have to transported in synch between the SAP Gateway server and backend systems as shown in the
following picture.

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 1/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

This is where the Quality Gate Management (QGM) comes to the rescue. QGM allows for the creation of so called changes which can contain one or more workbench and customizing requests
in di erent systems. With the help of QGM the workbench and customizing requests that have been assigned to those changes can be transported in synch and the process can be controlled
and monitored centrally from SAP Solution Manager.

Please note:

If the objects that you want to transport cannot be transported since you might have created them in the development class $TMP, please have a look at the following post. How to change dev
class $TMP for the repository objects of an OData service?.

Demo Flow

Step 1 – Create a change

Step 2 – Create workbench requests and customizing request

Step 3 – Gateway Service Builder – OData Service Creation

Step 4 – Gateway Service Builder – OData Service Implementation

Step 5 – Gateway Backend – Service Registration

Step 6 – Maintain Service – Service Activation on SAP Gateway Server

Step 7 – Maintain Service – System Alias Customizing

Step 8 – SAPUI5 Application Development

Step 9 – Transport changes via QGM

Step 1 – Create a change

The QGM supports the creation of transport request in di erent systems that are organized through a change request that spans di erent systems (e.g Gateway Server and Gateway Backend).

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 2/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Step 2 – Create workbench requests and customizing request

In a second step three workbench requests for

the repository objects of the Gateway service

the service implementation and
the Fiori application

will be created.

In addition a customizing request is created for the customizing settings of the Gateway service as shown in the following screen shot.

Step 3 – Gateway Service Builder – OData Service Creation

When the OData service developer starts to create a new project in the Service Builder in the SAP Gateway backend system and assigns it to a development class the developer will be
prompted to assign these changes to the transportable Workbench request (here: EH1K900309) that has been created using QGM before.

Step 4 – Gateway Service Builder – OData Service Implementation

The steps shown in the video are described in detail in the how-to-guide How to Develop a Gateway Service using Code based Implementation.
https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 3/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Step 5 – Gateway Backend – Service Registration

The service implementation ends with the generation of the runtime objects. In this step the repository objects such as ABAP classes are generated and the Gateway service and model are
registered in the SAP backend system.

As a result the developer is prompted to provide a transportable workbench request. Here the same workbench request (here: EH1K900309) will be used that already contains the Service
Builder project.

Step 6 – Maintain Service – Service Activation on SAP Gateway Server

In this step the developer activates the Gateway service on the Gateway Server (Hub). Here the developer is prompted to provide a workbench request (here: GW1K900063). Please note that
this happens on the Gateway Server development system (here: GW1).

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 4/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Step 7 – Maintain Service – System Alias Customizing

You now want to transport the customizing settings for the system alias(es) that are assigned to the Gateway Service. This can be done from within the customizing table maintance view.

The developer will be prompted now to provide a customizing request (here: GW1K900065) that has been created earlier.

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 5/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Step 8 – SAPUI5 Application Development

The developer of the SAPUI5 app can now develop the app and publish it nally on the Gateway server which is also called the frontend server for Fiori like applications. The SAPUI5 developer
can submit the app so that it is published in the SAPUI5 ABAP repository from within his Eclipse development environement. Here the developer will be prompted to provide a workbench
request (here: GW1K900067).

Step 9 – Transport changes via QGM

Now QGM will be used to transport the three workbench requests and the customizing request in synch to the quality assurance system and nally to production.

The status of the transports can be monitored. If for example a request is missing this can be easily be monitored in QGM

Finally all requests have been transported to the production system.

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 6/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

Result – SAPUI5 App runs

Finally the SAPUI5 app runs and displays a list of products  .

Appendix – List of repository objects being transported

SAP Gateway Server

Alert Moderator
The following objects have to be transported between the SAP Gateway server systems:

Object Transport Type PGMID OBJECT

Assigned tags
Service Repository Object R3TR IWSG
Model Repository Object R3TR IWOM
SAP Gateway | SAP Fiori | SAP Solution Manager | former jive document | gateway;sapui5; |
ICF Node Repository Object R3TR SICF
View more...
System Alias Customizing R3TR TABU
Serivice Registation on the Hub Customizing R3TR TABU
Related Blog Posts
Objects to be transported between the SAP Gateway backend systems
How to change dev class $TMP for the repository objects of an OData service?
>
By Andre Fischer , Mar 21, 2016
New SAP Gateway Demo System available
By Andre Fischer , Dec 05, 2017
Object Transport Type PGMID OBJECT
Day 2 at SAPPHIRE
Service – NetWeaver Gateway
Builder Project and Duet Enterprise
Repository Object R3TRteam inIWPR
full speed!
By PeterProvider
Model Ng , MayClass
16, 2013 Repository Object R3TR CLAS
Model Provider Extension Class Repository Object R3TR CLAS
Data Provider Class Repository Object R3TR CLAS
Related Questions
Data Provider Extension Class Repository Object R3TR CLAS
Model object Repository Object R3TR IWMO
OpenID Connect
Service object Repository Object R3TR IWSV
By Former Member , Jan 14, 2015

Register a service and transport it

Fiori
By Paullike application
Lauwers , Nov 12, 2014
The
How repository objects
to Upload Image of cation
in Noti an Fiori likeSAP
using application are deployed on the so called Frontend Server which is the same as the SAP Gateway server
Odata service
By Former Member , Jun 26, 2015
Object Transport Type
ICF Service Repository Object
Info Object from MIME Repository Repository Object

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 7/11
2/10/2020 How to transport Fiori like applications using SAP Solution Managers Quality Gate Management | SAP Blogs

12 Comments
Object Transport Type
BSP page Repository Object
You must be Logged on to comment or reply to a post.

Krishna Kishor Kammaje

July 12, 2014 at 12:34 am

Thanks Andreas. Very usefull. I have a question.

I have read your document on creating System Aliases in Production.

This document mentions transporting system aliases. I do not see any value in transporting system alias from Dev to Quality (since Dev system alias will point to Dev backend). Am I missing
anything?

Like (0)

Andre Fischer | Post author

July 13, 2014 at 6:44 am

Hi Krishna,

you are right that any system alias in a DEV system should point to a DEV backend.

But the system alias is just a wrapper for the underlying RFC destination.

So for testing purposes you should use the same name for a system alias (e.g. CRM_BACKEND) in your DEV system as in your QAS and PRD system. This system alias should however point to
the DEV CRM backend.

This is especially true if you want to test scenarios where several backends are used with a multi origin.

The assignment of a system alias to a service using transaction /IWFND/MAINT_SERVICE is customizing which is not allowed in a productive system.

Therefore I described in my document http://scn.sap.com/docs/DOC-42241 how it is possible to maintain the system alias itself in a productive system since this can be done as a so called
direct setting whereas this is not possible for the assignment of the system alias to a service itself.

This way you can change the RFC destination which will be di erent in DEV, QAS and PRD.

Best Regards,

Andre

Like (0)

Krishna Kishor Kammaje

July 13, 2014 at 5:26 pm

Perfect. Got it now.

I was used to naming the system alias same as RFC destination. So I need to be careful in naming the system alias so that it does not convey wrong meaning.

Like (0)

https://blogs.sap.com/2014/07/07/how-to-transport-fiori-like-applications-using-sap-solution-managers-quality-gate-management/ 8/11