Category: Developer

Posted on by

#1 Introduction – 7 Steps to Get Started With SAPĀ® CAPM

Before we begin!

In this 7 blog series, we are going to provide a small end-to-end scenario to work with SAP® CAPM. Here the usecase we are going to use is of Learning Management System(LMS) and build a Student List App and Deploy it to SCF.

Link to Master(or Main) Blog from which all the other blogs can be reached is Here.

  • If you wanted to check out the detailed course on SAP® CAPM the link is Here.
  • If you want to get learn SAP® Cloud Platform Development in Detailed then we have a 35hrs hands-on course Here.
  • For current offers and discounts check offer page Here.

Now let’s start this series with a little background about SAP® CAPM

Table of Content

#1. Why and What
#2. Developer Stack
#3. Links to Blogs of this Series

 

 

 

#1: Why and What

SAP® Cloud Application Programming Model(CAPM) is a set of Library, Tools, Language and Framework from SAP® for building Apps.

The main reason for creating CAPM is to

  • Provide a Simple way to Create Cloud-Based Apps
  • The Apps and code which developer created can be made more reusable as modules
  • Advantage of Microservice can be utilized
  • Apps in Cloud can be easily integrated with Cloud Services(like DB service, message broker service or Auth Provider service)
  • A developer can focus more on the functional side of problem-solving

The 2 main Principle of SAP® CAPM are:

  • Declarative Approach: Focus on Outcome, not on Way!
  • Service-Based Approach: Get the Functionality from Service

Declarative Approach

So, if you are a developer you need to focus more on understanding the functional side which is what customer needs now, and also thinking about how can the App/Platform you are developing will evolve over time. Keeping this in mind you need to keep your current development modular, so it can allow future changes easily or your current development can be reused in the future easily.

Service-Based Approach

In CAPM all functionalities need to be broken down as service(s). In CAPM Services are stateless which means there is no record of previous interactions and each interaction request has to be handled based entirely on information that comes with it. You will also see, that to implement new service/functionality we will many times query existing service(s).

 

#2: Developer Stack

That Sounds Great! But you might be having questions like How it is Build and How as a developer you will work with it?

 

  • CAPM Lib are Predominantly Build With NodeJS, so you need to have basic know-how of NodeJS
  • We will use a lot of CDS code, may it be for building data structure(entity model/Table Structure), creating services(with functions) or even creating UI(with CDS Annotations)
  • You will find many out of the box tools which are part of CAPM, for example for running Apps with Fiori® Preview just with developed service, for building data structure to deploy in Database like HANA®, Sqlite or Other Other and many more surprises!

 

Prerequisite and Getting Started

We will create a simple End-to-End CAPM App using HDI Container in SAP® Cloud Foundry from Scratch.

Regarding Prerequisites:

  • Basic knowledge of NodeJS is required
  • Basic knowledge of SAPUI5 is required
  • Basic knowledge of CDS is required

#3: Links to Blogs of this Series

  • Introduction – this blog
  • Installation – here
  • Hello World Service – here
  • Creating Schema and Database – here
  • Create UI Annotations – here
  • Create UI5 App – here
  • Deploy App to SCF – here

Before we end!

Link to Master(or Main) Blog from which all the other blogs can be reached is Here.

 

  • If you wanted to check out the detailed course on SAP® CAPM the link is Here.
  • If you want to get learn SAP® Cloud Platform Development in Detailed then we have a 35hrs hands-on course Here.
  • For current offers and discounts check the offer page Here.

 

Also, You can Watch the Entire Blog Series in the below video:

 

 

 

 

 

Thanks for Your Time!

Posted on by

Understanding SAPĀ® FioriĀ® Launchpad and Tiles Types

 

 

Link to Full Course:
https://www.ui5cn.com/courses/fiori-for-developers

 

  • SAP® Fiori® Launchpad, is the starting point for our developers and users.
  • We will have multiple applications in the Launchpad (which are assigned to us by roles) and Launchpad is also often referred to as the homepage.
  • Each Tile in Fiori® Launchpad® represents one Application.

 

  • The first type of Tiles with Static Text and Icon/Image is Static Tiles, for Example, My Contact Application

 

 

  • The second type of tile or application we can have is the Dynamic Tile which can contain dynamic changing numeric values (representing some form of KPI). For example Timesheet Application, we can go inside this Tile(application) and we can fill our Timecard which then needs to be approved by our manager(s).
  • The KPI it contains also shows from how many days we have last filled out timecard(Missing Days which changes dynamically).

 

 

  • And the third type of application/tile we have is Newsfeed Application Tile. The news feed application tile would be utilizing the RSS Feed and represent news in terms of tiles.

 

 

  • If we go into My Contact Tile then we can see a Split Application(as shown below). In split-screen Application, the screen is divided into a Master and a Detail Page. This is one type of application similar to that we can have list report application, analytical dashboard application, and many more different types.

 

 

Now, how an Application or Tiles are given to a particular user?

  • This is possible with Roles and Authorization. Also, Fiori® follows the Role-Based Principle.
  • If you want to provide a specific application to a user then you just provide them with Roles which is required for that application.
  • Also, we might have multiple types of roles link to an application, for example, in Timecard we can have manager roles to approve a timesheet, user roles to fill and submit a timecard, etc.
  • We will discuss in detail these Authorization concepts in our Fiori® for Developers Course as well(later on).

 

 

For a particular user to see Tiles(or Application) in Launchpad we need to configure 3 Main things:

  • Roles
  • Catalogs
  • Groups

We will see in details how to perform those in Fiori® for Developers Course here:
https://www.ui5cn.com/courses/fiori-for-developers

SAP® Fiori® Blog Series Links :

  1. SAP® Fiori® Launchpad Configuration – Starting with Catalog Creation
  2. SAP® Fiori® – Understanding Fiori® Launchpad (Current Blog)
  3. SAP® Fiori® – Understanding Fiori® Catalogs, Tiles, Roles and Groups (Blog Coming Soon)
  4. Fiori® Applications Types and Architecture (Blog Coming Soon)
  5. Types of Fiori® Apps – Transactional Fiori® Application Overview and Architecture (Blog Coming Soon)
  6. Fact Sheet Fiori® App Architecture | Fact Sheet Applications | Types of Fiori® Application (Blog Coming Soon)
  7. Analytical & KPI Fiori® App Architecture | Analytical Fiori Application | Types of Fiori Application (Blog Coming Soon)
  8. SAP® Fiori® Architecture and Component | SAP® Fiori® Components | Fiori® Architecture (Blog Coming Soon)

 

Posted on by

FioriĀ® For Developers Online Course – Introduction Page

 

Introduction to the Course

Learn and Understand Fiori® Apps Debugging, Development, Deployment and Architecture with Hands-on Exercises. SAP® Fiori® for Developers is an unique course that takes you from the basics to intermediate to advance in a step by step manner. We will understand and deep dive more into the details which we have covered in this course such as:

  • Fiori® Launchpad – How Fiori® Launchpad shows you Role-Based Tiles – Different types of Fiori® Apps
  • The Architecture of Fiori® Apps
  • The Architecture of Fiori® Apps and UI Components
  • Understanding Back-end and Front-end services and components
  • How to Deploy and Configure Fiori® Apps
  • How to Extend Screen Elements, UI, Controllers, and Services in Fiori® Apps with Web IDE
  • And a lot of Debugging to make you Comfortable with Production Scenarios.

 

Link to Full Course:
https://www.ui5cn.com/courses/fiori-for-developers

 

SAP® Fiori® Blog Series Links :

  1. SAP® Fiori® Launchpad Configuration – Starting with Catalog Creation
  2. Understanding SAP® Fiori® Launchpad and Tiles Types
  3. SAP® Fiori® – Understanding Fiori® Catalogs, Tiles, Roles and Groups (Blog Comming Soon)
  4. SAP® Fiori® Applications Types and Architecture (Blog Comming Soon)
  5. Types of Fiori® Apps – Transactional Fiori® Application Overview and Architecture (Blog Comming Soon)
  6. Fact Sheet Fiori® App Architecture | Fact Sheet Applications | Types of Fiori® Application (Blog Comming Soon)
  7. Analytical & KPI Fiori® App Architecture | Analytical Fiori Application | Types of Fiori Application (Blog Comming Soon)
  8. SAP® Fiori® Architecture and Component | SAP® Fiori® Components | Fiori® Architecture (Blog Comming Soon)

 

Refer the Blow Video to Understand More,

 

Posted on by

SAPĀ® FioriĀ® Launchpad Configuration ā€“ Starting with Catalog Creation

 

Link to Full Course:
https://www.ui5cn.com/courses/fiori-for-developers

 

  • Step 1 – Login to our system with the newly created user which is DEVELOPER3 and it will ask to change our previous password.

 

 

 

  • Step 2 – Give a new password and there are some pre-checks for the password, some of which include that the password should not be the same as the previous password and it should be having 8 characters. 
  • Step 3 – Using T-Code SU01 we can see login information of the user as well, we can click on information Icon to check the rules and regulations about the password as well.

 

 

  • Step 4 – Now we are in a new User Login and then we have to go into the Fiori® Launchpad using the URL. Now to find the URL for Fiori® Launchpad, go to the Start-up and then using /n go into the Home Screen.

 

 

  • Step 5 – We will see the Fiori® Launchpad and right-click on /UI2/FLP – SAP Fiori® Launchpad and Execute in New Window. 

 

 

 

  • Step 6 – It opens in Internet Explorer then copy the Fiori® Launchpad URL then go to Chrome (Browser Choice for Development) and open a new incognito window, it would ask for credentials of this new user which is DEVELOPER3.

 

 

 

  • Step 7 – Now we get a blank screen because we have not added any application to our Launchpad of DEVEOPER3. So our objective is to provide this user with our Purchase Order App access.
    Now we will log in with Admin User in Fiori® Launchpad to configuration Approve Purchase Order App which we are basically going to provide access to the App to DEVELOPER3.

 

 

 

  • Step 8 – Go to Launchpad Configurator(With Admin User). To get the Launchpad Configurator URL we would be replacing existing URL from “/ui2” with “sap/arsrvc_upb_admn/”(as shown in image below). This will basically use the service ‘arsrvc_upb_admn’ and we have to go into main.html.
    We can check the service in our SICF Transaction, which is responsible for Catalog and Group Management.

 

 

 

 

  • Step 9 –  We will be creating a new Catalog for that click on + Icon which is present in the bottom left side of the screen. The Catalog will be a Standard Catalog and for now let’s name it as Zdemo1_01 and unique ID Zdemo1_01, then click on Save.

 

 

 

  • Step 10 – In this step, we have seen how to Create Catalog, to Configure Fiori® Apps we need to Create Semantic Object Next and Action. Then Provide this Role With Target Mapping.

To view all the steps of Fiori® App Configuration you can Enroll in Fiori® for Developers Course With UI5CN here:

https://www.ui5cn.com/courses/fiori-for-developers

 

SAP® Fiori® Blog Series Links :

  1. SAP® Fiori® Launchpad Configuration – Starting with Catalog Creation (Current Blog)
  2. Understanding SAP® Fiori® Launchpad and Tiles Types
  3. SAP® Fiori® – Understanding Fiori® Catalogs, Tiles, Roles and Groups (Blog Comming Soon)
  4. Fiori® Applications Types and Architecture (Blog Comming Soon)
  5. Types of Fiori® Apps – Transactional Fiori® Application Overview and Architecture (Blog Comming Soon)
  6. Fact Sheet Fiori® App Architecture | Fact Sheet Applications | Types of Fiori® Application (Blog Comming Soon)
  7. Analytical & KPI Fiori® App Architecture | Analytical Fiori Application | Types of Fiori Application (Blog Comming Soon)
  8. SAP® Fiori® Architecture and Component | SAP® Fiori® Components | Fiori® Architecture (Blog Comming Soon)

 

Posted on by

5 reasons why nodeJs is so popular

Node.js_logo

Node.js outshines other web applications by replacing websockets with revolutionary push technology. You would ask, what is so unique about it? Well, we finally have cutting-edge web applications with two-way, real-time connections where both the server and client can build communication, allowing them to exchange valuable data. Now this is in stark contrast to our conventional web response paradigm where only the client initiates communication

Node.js server technology is used to create and run a wide variety of web applications, and is quite similar to what Ruby On Rails, Spring Framework and ASP.NET does. It leverages JavaScript as the main language, which is a lightweight built-in web server and has a plethora of Plugins managed via the Node Package Manager (NPM), allowing you to custom-build your applications to meet your needs. It may sound like any other good web technology, but it has certain features that make it a popular choice among developers to build a wide spectrum of web applications.

Here are the top 5 reasons why nodeJs is so popular nowadays:

1. Node.js is superfast

Node.js is primarily a JavaScript runtime that is powered by V8, developed by Google for use in Chrome. V8 has the ability to compile and execute JavaScript at lightning fast speed, mainly because it compiles JavaScript into a native machine code. In addition to this, Node.js has a magical event loop, which is a single thread performing all I/O operations in an asynchronous manner. In Node.js, when an application has to perform I/O operation, it sends asynchronous tasks and callback action to the event loop, and then continues to perform the rest of the program. On completion of sync operation, the event loop automatically returns to the task to execute callback. This is much unlike traditional looping, which consumes a lot of memory and is exceptionally difficult to execute. Thus, reading/writing to file system, network connections, and to the database is executed very fast in Node. It allows developers to build fast and highly scalable network applications that are capable of handling bulk amounts of simultaneous connections having high throughput.

2. High Performance

PayPal uses Node.js, and has reported doubling the number of requests per-second and reducing the response time by 35%. On the other hand, Wal Mart, the retail giant had a superb experience with Node.js in 2013, when they put all their mobile-based traffic via Node.js on Black Friday, the busiest shopping time of the year. Amazingly, on Black Friday, Wal Mart servers did not go over a mere 1% CPU utilization and yet they deploy with 200,000,000 users online. LinkedIn, the global networking site, moved from Ruby to Node to handle their mobile traffic, and reduced the number of servers to 30 to 3, i.e. almost 90% reduction. The new system was up to 20 times faster. All these figures clearly indicate performance capability of Node.js.

3. JavaScript Everywhere

One of the biggest reasons why Node.js is so popular is because it uses JavaScript as its main language to build web applications. And to be honest, JavaScript is now the only choice to develop web applications in the browser. What more! A new and robust framework is introduced quite frequently to woo developers. With Node.js, JavaScript has literally revolutionized on the server. The language is common to most web developers, and is certainly driving the world today. And according to experts, the trend will not fade away soon.

Since JavaScript is a language that most developers know or have used at some point of time, the transition from another web technology to Node.js is a breeze. This makes it a preferred choice among web developers.

4. It is Lightweight

Typically, Node.js uses a basic event-driven architecture. This means everything executed on it, including every single operation and call, is a series of asynchronous callback. This enables Node to run on a single thread as unlike other web technologies where a new thread is spawned for every client request. This not only makes it light-in-weight, but also forms the foundation of Node’s non-blocking I/O feature.

5. It is Easy to Modify and Maintain

Traditionally built applications become less adaptive and rigid over time as new requirements are fed. Eventually, they start creaking under the stress they were not built for. However, developing new services using Node.js is comparatively easier. With Node, a bunch of small applications is built instead of a single, large application. This allows making changes or adding a new functionality with much ease, without having to make changes deep inside the code-base.

pexels-photo