SAP Fiori Embedded Deployment Configuration

We will tackle the purpose of the SAP Fiori embedded deployment configuration. Also, let us learn how they properly deploy this kind of configuration.

What Is SAP Fiori Embedded Deployment Configuration?

SAP Fiori embedded deployment configuration is a set of embedded SAPUI5 pages. They are associated with a form field or view object. 

It means they are directly associated with the underlying data source.

Basic Purpose of SAP Fiori Embedded Deployment Configuration

The embedded deployment configuration is used to deploy the SAP Fiori components. Also, it helps you to create a link between the data source and an application. 

Moreover, it helps you to define the relationship between the UI and the database. You can easily deploy them in a single package or multiple packages.

SAP Fiori Embedded Deployment Configuration With Form Fields

You can create a link between the form field and the SAPUI5 page by configuring them as embedded deployment configurations. The SAPUI5 page will be rendered on the server side as well as on the client-side. 

The client-side data will be fetched from the server-side through HTTP(s) services API calls.

With View Objects:

If you are using view objects in your business logic layer. Then you can use embedded deployment configuration for those view objects. 

This deployment allows you to access view objects directly from an HTML page. In this case, no user interface will be provided for accessing those view objects. 

You can embed these view objects into your HTML pages by using SAPUI5 components like text fields, buttons, etc. You can also embed these views into a standard SAPUI5 app by using SAP Web IDE (SAPUI5 App Generator). 

In this case, a normal user interface will be provided for accessing those view objects through a client-side JavaScript API called W3C’s fetch(). This API allows you to access RESTful services through HTTP requests with XML or JSON payloads in return format. 

It is similar to AJAX functionality in web browsers. Without making any changes in the underlying application server architecture (like JEE/Java EE).

Who Can Use This Configuration?

This embedded deployment configuration can be used by developers as well as users. Developers can use this configuration to design and build end-user applications. 

On the other hand, users can use this configuration to access data from SAP systems through user interfaces. They can also use this configuration to fetch data from SAP systems through JavaScript code on the client-side. 

Users must be familiar with JavaScript to use this configuration.

How to Create an Embedded Deployment Configuration?

You can create an embedded deployment configuration for a form field or a view object. They are created by using the method called ‘createEmbeddedDeploymentConfiguration’ from the UI5 Component Model. 

Here is the step to create from the following:

1: Create a New Project:

Create a new project in SAP Web IDE (SAPUI5 App Generator). 

2: Import a Form Field or View Object:

Import a form field or view object into your project by using the ‘Import’ option in the Project menu. 

3: Create a New Embedded Deployment Configuration:

Next, create a new embedded deployment configuration for your form field. Or view the object by using the ‘New’ option in the ‘Deployments’ section of your project menu.

4: Associate Embedded Deployment Configuration With Form Field or View Object:

Associate your embedded deployment configuration with your form field. Or view the object by selecting it from the ‘Embedded Deployment Configurations’ section of your project menu.

Then select the ‘Create’ option. This will create an embedded deployment configuration for your form field or view object. 

You will see it under the ‘Embedded Deployment Configurations’ section of your project menu after completion of this step. 

5: Run Your Application and Test Your Configuration:

Now run your application by using the ‘Run’ option in your project menu and test your embedded deployment configuration functionality.