Getting Started With BAS and Cloud Connector

5Steps2Fiori – Developer – WP01
Getting Started with the Business Application Studio and Cloud Connector
CUSTOMER
TABLE OF CONTENTS
INTRODUCTION...................................................................................................................................................... 3
GET AN SAP BTP TRIAL ACCOUNT .................................................................................................................... 4
UNDERSTAND YOUR DEPLOYMENT ................................................................................................................ 15
Use Cloud Connector to connect your BTP Trial Account to your SAP backend system - RECOMMENDED 15
Use a direct connection between your BTP Trial Account and your SAP backend system ....................... 15
INSTALL SAP JVM ............................................................................................................................................... 16
INSTALL CLOUD CONNECTOR .......................................................................................................................... 20
Prerequisites: Hardware and internet Access .................................................................................................. 20
SETUP CONNECTIVITY BETWEEN ABAP SYSTEM AND SAP BTP ............................................................... 35
CREATE DESTINATION TO YOUR BACKEND SYSTEM USING CLOUD CONNECTOR ............................... 51
CREATE DESTINATION TO YOUR SAP BACKEND USING A DIRECT CONNECTION ................................. 57
ACTIVATE SAP BUSINESS APPLICATION STUDIO ......................................................................................... 62
CONFIGURE SAP BUSINESS APPLICATION STUDIO (BAS) .......................................................................... 72
VALIDATE CONNECTIVITY IN BUSINESS APPLICATION STUDIO................................................................. 77
TROUBLESHOOTING BUSINESS APPLICATION STUDIO CONNECTIVITY .................................................. 86
UNDERSTANDING DEVELOPMENT IN SAP S/4HANA ..................................................................................... 92
Ensuring Connectivity between SAP BTP, your desktop/network and SAP Backend................................. 93
Connectivity Checks between your desktop/network and SAP BTP ..................................................................... 94
Connectivity Checks between your desktop/network and SAP Backend .............................................................. 96
2
INTRODUCTION
This document has the scope to explain you the steps required to complete all the activities planned for the current work-package.
By executing the steps described in this document you will be able to understand the main procedures required to select and activate SAP Fiori apps in your
implementation project.
Note that the steps described in this document refer only to the technical activation steps, additional functional activation steps may be needed depending on the
application scope. The required functional steps are described in the SAP Fiori apps reference library.
3
GET AN SAP BTP TRIAL ACCOUNT
In this step you will be setting up your SAP BTP Trial Account and subaccount
Steps / Comments Screenshot
1. Open the following link and select

the option to try SAP BTP for free.
https://www.sap.com/products/business-
technology-platform/free-trials.html
4
2. In the next page, select the option to

sign-up for free tier for Individual
User
5
3. The registration form will appear. If

you have already registered for a
Trial account skip to step 6,
otherwise enter the required
information in this form and click on
Register.
Note – If you have an account on

www.sap.com (e.g. a P, S, C, D or I
number) you can enter it or the
associated email along with your
password by selecting the Log in button
Take note of the email and password

used for registration as they will be
used for later steps. Remember that
the password is defined by YOU so
make sure you remember this
information.
4. Upon successful registration an

email will be sent to the registered
address.
6
5. Check your email to find the SAP

BTP Trail confirmation message,
open this email and activate your
account using the button Click to
activate your account
7
6. Start your trial account
8
7. If needed, verify your account by

providing a telephone number
8. Accept legal disclaimers
9
9. Select the region where your trial

account will be generated and click
on button Create Account. You may
select the region closest to your
geographical location.
Note: The following screenshots will be

referencing region: US East (VA) – AWS
but you may select the region closest to
your geographical location.
10
10. Wait for the process to conclude.
11
11. Once the account generation

process concludes click on
Continue.
12
12. Enter your trial account
13
13. Your trial account is now setup,

including a trial subaccount that you
can start using out-of-the-box.
Note – You can use extend this trial

account up to 365 days
14
UNDERSTAND YOUR DEPLOYMENT
There are mainly two options to connect your SAP BTP Trial account to your SAP Backend system, a decision on which one to use should be taken based on your
learning expectation but also on your current landscape deployment and network architecture. For this exercise you have the option to decide which path you want
to take.
(Optional) For both scenarios we recommend reviewing and understanding the checks available in section Ensuring Connectivity between SAP BTP,
SAP Cloud Connector and SAP Backend as these will help you understand which option fits best to your current network architecture.
Use Cloud Connector to connect your BTP Trial Account to your SAP backend system - RECOMMENDED
In this scenario you will deploy and configure SAP Cloud Connector to establish a secure connection between your SAP Backend system and SAP BTP
(regardless of your SAP backend system being an On-Premise or CAL instance). This is the recommended scenario for the 5 Steps to Fiori training as this
resembles a real implementation project and will help you identify risks and challenges in your current SAP landscape and your network.
To start this path, jump to section INSTALL SAP JVM
NOTE: If you are using a CAL instance, this should have an SAP Cloud Connector already installed, you can check this with the URL
https://vhcals4hcs.dummy.nodomain:8443/, if this is the case you can skip steps 14 thru 29 inclusive.
Use a direct connection between your BTP Trial Account and your SAP backend system
In this scenario you will establish a direct connection from your SAP backend system to your SAP BTP account, this scenario considers that your SAP Backend
system is publicly available on the internet, so network exposure has been correctly defined and your business has no risk in exposing information to the internet.
To start this path, jump to section CREATE DESTINATION TO YOUR SAP BACKEND USING A DIRECT CONNECTION
15
INSTALL SAP JVM
Installation of a Java virtual machine (JVM) version 8 is required for you to make use of SAP Cloud Connector. In the following section you will find the steps to
deploy SAP JVM.
14. Open the following link and scroll down

to the section SAP JVM and download
the file that matches your OS version, for
example, Windows.
https://tools.hana.ondemand.com/#cloud
16
15. Accept the license agreement
17
16. Once the download concludes, open and

extract the file with your favorite
extraction tool.
18
17. Extract the file to an easily identifiable

folder in your desktop. For this training,
we have extracted the files to the
Downloads folder, but you MUST
deploy this component in a proper folder
in your desktop.
Keep note of the folder path where you

extracted SAP JVM as this will be used later,
for example:
C:\Users\Downloads\sapjvm_8
Note – Directory to where SAP JVM was extracted is just for reference, you MUST DEFINE a proper folder in your own desktop where to deploy this
component
19
INSTALL CLOUD CONNECTOR
In the following section you will find the steps to install SAP Cloud Connector in your desktop.
Prerequisites: Hardware and internet Access

• You need at least 2GB of RAM and 3GB of hard disk space to use this version of the Cloud Connector.
• Since the Cloud Connector will act as a gateway between SAP Cloud Platform and systems in your on-premise system landscape, it must have an Internet
connection to the hosts of SAP Cloud Platform as well as LAN access to your systems (SAP Cloud Platform has IP addresses for connectivity for each
region).
• You can check the current prerequisites for newer versions of the Cloud Connector in the official documentation. The list of IP addresses is also given there.
Note – For learning purposes you will be using the portable version of SAP Cloud Connector. The Portable archives for Cloud Connector are meant for non-
productive scenarios only. They can be used even if you don't have administrator permissions on the machine, on which you like to use the Cloud Connector.
However, those variants do not support upgrades from previous versions.
20
18. Open the following link and scroll

down to the section Cloud
Connector.
https://tools.hana.ondemand.com/#cloud
19. Download the file that corresponds to

the Portable version and matches
your OS version, for example,
Windows (Portable).
21
20. Accept the license agreement
22
21. Once the download concludes, open

and extract the file with your favorite
extraction tool.
23
22. Extract the file to an easily identifiable

folder in your desktop. For this
training, we have extracted the files to
the Downloads folder, but you MUST
deploy this component in a proper
folder in your desktop.
In this example, we have deployed SAP

Cloud Connector to the following directory:
C:\Users\I834429\Downloads\SAPCC
Note – Directory to where SAP Cloud Connector was extracted is just for reference, you MUST DEFINE a proper folder in your own desktop where to
deploy this component
24
23. In the directory where you deployed

the SAP Cloud Connector (Portable)
files, search for the file “go.bat” and
open it with a text editor
25
24. Once the file is open, locate line 35

and add the following code:
set JAVA_HOME= <Path to your own

JVM>
Note – You defined this path when

running step 17
26
25. In windows search options, search for

the keyword “cmd” and open a
Command Prompt
Note – You DO NOT need to run the

command line tools as administrator
26. With the command line tools

displayed, navigate to your installation
folder using command
cd <path to your SAP Cloud Connector

folder>
for example: cd Downloads\SAPCC
27
27. Once you have reached the

installation folder of SAP Cloud
Connector, type command go.bat and
press enter.
28. SAP Cloud Connector is now loading,

wait for the success message to
appear.
28
29. You will find a message stating SAP

Cloud Connector has started.
Note – If you want to stop Cloud

Connector just close this command line
window or press CTRL+C while in this
window
29
30. Go to your browser and open the

following link depending on your set-
up:
If you are using your local machine:

https://localhost:8443
If you are using a CAL instance

https://vhcals4hcs.dummy.nodomain:8443/
31. Click on Advanced
30
32. Click Continue
31
33. Logon window will be displayed. To

logon you MUST use the following
User ID and Password:
User Administrator
Password manage
32
34. Once you have logged in you will be

asked to change your password.
Perform this password change, select
Installation Type = Master and Save
Note – Take note of the password you

defined and store it in a safe location.
33
35. You have successfully installed and

deployed your SAP Cloud Connector.
In the following section you will find
the steps to setup connectivity
between Cloud Connector and your
BTP trial account.
34
SETUP CONNECTIVITY BETWEEN ABAP SYSTEM AND SAP BTP
In the following section you will find the steps to connect SAP Cloud Connector and your SAP BTP Trial Account.
36. Before you setup the configuration for your

account you first need to collect some
information. For starters you need to logon to
your BTP trial account, use the following link
and enter your email and password.
https://account.hanatrial.ondemand.com/trial/#/home/trial
Note – The email and password for logon were

defined by YOU when creating your trial
account on Step 3 – Take note of this email
and password as it will be used later.
37. Once you have logged in click button “Go to

your Trial Account”
35
38. Once your Global Account is displayed, click

on the details button in your Trial
Subaccount and select option “More Info”.
36
39. Copy the value of the ID parameter into a

file in your preferred text editor and take
note of the values for Provider and Region.
Once you have gathered this information you

can go back to your Cloud Connector
configuration screen
40. Request your SAP Basis administrator to

provide the list of available ICM ports from
your backend system and the Hostname of
your server.
Note – This list of available ports and hostname

can be obtained by going to transaction SMICM
and selecting the services button
Take note of the available HTTP and HTTPS

port numbers as well as the hostname of
your system as these will be used later.
37
41. In your Cloud Connector configuration

screen, open the value help for the field
Region
42. Search for the Region where your

subaccount is located, foe example, US
EAST (VA)-AWS
38
43. Enter the ID of your subaccount.
Note – You obtained the ID of your

subaccount when running Step 39
44. Enter any identifier in the field Display

Name. You can choose any text, for
example, 5Steps2Fiori.
39
45. Enter email and password used for login to

your BTP Trial Account.
Note – The email and password for logon

were defined by YOU when creating your trial
account on Step 3
46. Click on Save
40
47. On success, Cloud Connector will be

connected to your BTP Trial Subaccount,
however, resources (backend system
endpoints) have not been made available.
41
48. To confirm this connection, you can start by

navigating to your Trial subaccount by
clicking on the trial link.
42
49. Once in your Trial Subaccount, navigate to

Connectivity >> Cloud Connector. You
should find the technical details of your
Cloud Connector and a status flag showing
successful connection
43
50. Go back to your Cloud Connector and in

your recently created subaccount
connection navigate to Cloud To On-
Premise >> Access Control and click on
Add
51. In the system mapping screen select
Back-end Type = ABAP System
And click Next.
44
52. Select the available protocol based on the

information you gathered on Step 40 and
click Next.
Note that HTTPS connection is always

preferred.
53. Enter the hostname of your backend

system (for example:
vhcals4hci.dummy.nodomain) and the port
number for your HTTP/S service (for
example: 443) and click Next.
Note – You gathered this information while

running Step 40
45
54. Enter a new virtual hostname (it can be

any name, for example,
5steps2fiori.dummy.nodomain) and a
new virtual port (it can be any port
number of you can use the same as
your internal system) and click Next.
55. Select Principal Type = None and click

Next.
46
56. Select Use Virtual Host and click Next.
57. Enter a description (it can be anything,

for example: 5Steps2Fiori)
47
58. Review the details in the summary

screen, activate the checkbox to Check
Internal Host and click Finish.
59. Once concluded, you will find a new

mapping and check results should
show that backend system is
reachable.
48
60. You now need to add resources to your

system mapping. Click on the button to
add resources
61. In the Add Resource screen set the

following values:
URL Path: /
Active: Checked
Access Path and All Sub-Paths
Policy:
49
62. Once set you should see the status for

both your system mapping and
resources is set to green
63. Go back to your Trial Subaccount,

navigate to Connectivity >> Cloud
Connector. You should find the
technical details of your Cloud
Connector and a status flag showing
successful connection and available
resources.
50
CREATE DESTINATION TO YOUR BACKEND SYSTEM USING CLOUD CONNECTOR
Follow the next steps to help you create and configure a destination in BTP Cloud Foundry to your backend system while connecting through SAP Cloud
Connector.
64. Navigate to the JAM site for the 5Steps2Fiori

training and download the provided sample
destination.
51
65. In your BTP trial subaccount, navigate to

Connectivity → Destinations.
66. Click on Import Destination
52
67. Select and open the file you downloaded on

Step 64
53
68. Configurations will be preloaded, but you

need to make them match to your current
system settings. To do this, edit the following
fields:
• URL: This field should match the hostname

and port defined in Cloud Connector
configuration. You have confirmed these
values when running Step 63. Value should
be entered in the format:
<Protocol>://<virtual_hostname>:<port>
For example:
https://5steps2fiori.dummy.nodomain:44303
• sap-client: This number should match the

system client where you logon in you SAP
backend system, for example: 100
Save the connection.
54
69. Once the destination is saved, select button

Check Connection.
55
70. Connection to backend system should be

successful.
56
CREATE DESTINATION TO YOUR SAP BACKEND USING A DIRECT CONNECTION
Follow the next steps to configure a destination in BTP Cloud Foundry to enable a direct connection to your SAP Backend system.
Note – To run this scenario you have made sure that your SAP Backend system is exposed to public internet, meaning, you can run the checks in
section Connectivity Checks between your desktop and SAP Backend while in your home network without using any VPN or tunneling software.
71. Navigate to the JAM site for the 5Steps2Fiori

training and download the provided sample
destination.
57
72. In your BTP trial subaccount, navigate

to Connectivity → Destinations.
73. Click on Import Destination
58
74. Select and open the file you

downloaded on Step 71
59
75. Configurations will be preloaded, but

you need to make them match to your
current system settings. To do this, edit
the following fields:
• URL: This field should match the

hostname and port used by your
system and the value in this field
should be entered using the following
syntax:
<Protocol>://<virtual_hostname>:<port>
For example:
https://5steps2fiori.dummy.nodomain:44303
Note – If you defined protocol HTTPS you

should activate checkbox Use default JDK
trust store
• Proxy Type: Set value to Internet
• sap-client: This number should

match the system client where you
logon in you SAP backend system,
for example: 100
Save the connection.
60
76. Once the destination is saved, select

button Check Connection results
should be successful
61
ACTIVATE SAP BUSINESS APPLICATION STUDIO
In this section you will go through the setup of SAP Business Application Studio in your SAP BTP Trial Subaccount.
77. In your BTP Trial Subaccount, navigate to

Service Marketplace and search for
Business Application Studio.
78. Once the search results are listed, on the

SAP Business Application tile, click on the
details button and select Create
62
79. Select Service = Business Application

Studio, Plan = trial and click on Create
63
80. Wait for the subscription process to conclude

and click on View Subscription
64
81. Make sure the subscription status is set to

Subscribed.
Note – Do not start the application, permissions

have not yet been granted to your user.
82. Go to Security >> Users and navigate to the

details of YOUR user.
65
83. In the details section click on button Assign

Role Collections
66
84. Assign all the following role collections for

Business Application Studio to your user:
Business_Application_Studio_Administrator
Business_Application_Studio_Developer
Business_Application_Studio_Extension_Developer
85. Navigate to Cloud Foundry >> Spaces

and click on Create Space
67
86. Enter any name for your space (for

example 5Steps2Fiori), make sure the
Space Manager and Space Developer
roles are assigned to your user and click
on Create.
87. Go to Services >> Instances and

Subscriptions, identify your SAP
Business Application Studio subscription
and Go to Application
68
88. Click OK
89. Select the option to Create a New Dev

Space
69
90. Enter 5StepsToFiori as the space name,

select space type SAP Fiori and click on
Create Dev Space
91. Wait for the space status to be set to

Running
70
92. Once the status is set to Running, click on

the space name: 5Steps2Fiori to access
your space.
71
CONFIGURE SAP BUSINESS APPLICATION STUDIO (BAS)
In this section you will go through the required configurations in SAP BAS to setup your Development Space.
93. Once your Dev Space in Business Application

Studio is loaded you need to run some
additional configurations
72
94. You now need to setup the organization and

space. For this, you first need to open a new
terminal.
95. In the terminal, enter command*:
cf login
Note - API endpoint should be defined automatically
73
96. If your API endpoint is not defined

automatically, you can search for this
information in your BTP subaccount overview,
as shown in the image
Note – Take note of the values for parameters

Org Name and API Endpoint as they will be
used in the following steps
97. Enter the email and password you used to

register for your trial account. These were
defined by YOU when running Step 3
74
98. If required, select your organization according

to the details obtained in Step 96. Otherwise,
select your Dev Space created on Step 85
99. Once concluded, make sure the configuration

matches your own organization and space
75
100. If you want to validate your target at a later

stage, you can use command:
cf target
76
VALIDATE CONNECTIVITY IN BUSINESS APPLICATION STUDIO
In this section you run an initial check to validate connectivity between SAP BTP, SAP Cloud Connector and your SAP Backend system
101. Once you have finished the setup of

Business Application Studio (BAS) and
the connection to you Backend system
via your Cloud Connector or a direct
connection, you can now test the
connectivity in your landscape. To start
this test, launch a new terminal window
in BAS.
77
102. Type the following command in the

terminal and press enter:
curl http://localhost:8887/reload
103. On successful execution you will get a

confirmation message
78
104. In the welcome screen of BAS, click on

“Create project from template”
79
105. Select SAP Fiori Application and

click on Start
80
106. Select Application Type = SAP Fiori

Elements, List Report Object Page
and click Next.
81
107. Select “Connect to a System” as your

Data Source
82
108. Select the name of the

destination you created earlier: 5
Steps
83
109. Enter the User ID and password

from your SAP Backend system
and click on the login icon
Note – If you are not aware of your

User ID and password in from the SAP
backend system contact your Team
Lead
84
110. On successful authentication you

will be able to see the list of
available OData services from your
SAP backend system.
111. The purpose of this check was to

reach this point as you are
successfully retrieving metadata
from your SAP backend system.
You can now close the project
wizard.
Note – This concludes the connectivity

checks to your backend system either
using SAP Cloud Connector or a direct
connection to your CAL system. You
will come back to use BTP on Step 4
of the 5 Steps to Fiori training
112. If you are having issues running

this check, go to the next section:
Troubleshooting Business
Application Studio Connectivity,
otherwise proceed to section
Understanding Development in
SAP S/4HANA
85
TROUBLESHOOTING BUSINESS APPLICATION STUDIO CONNECTIVITY
In this section you will learn about some additional troubleshooting options for SAP BAS.
113. First option to troubleshoot BAS is

going through the steps mentioned in
this blog:
How to check the connectivity to your

backend system in Business Application
Studio
86
114. If you are sure your destination setup

is correct and suspect there is an error
on your Cloud Connector one good
option is to navigate to the Log and
Trace File section of your subaccount
configuration and launch the Support
Log Assistant
87
115. While the tool finishes loading in a

separate browser tab, download the
ljs_trace.log file from your cloud
connector.
Note – This file is downloaded as a ZIP file.
88
116. Once the download concludes, go to

the browser tab where Support Log
Assistant Tool was loaded and
upload the zip file with the cloud
connector logs
89
117. In the following screen you will get an

overview of the uploaded files and
warnings for the files that will or will not
be analyzed by the tool.
Click on Scan Files
90
118. Once the analysis is complete you will

find a list of alerts, errors and details
that can help you troubleshoot your
SAP Cloud Connector issues.
Note – We recommend you explore the

options in this tool as you will find
reports for download and quick links to
possible information sources that may
contain the solution to your error.
You can learn more about Support Log

Assistant in here
91
UNDERSTANDING DEVELOPMENT IN SAP S/4HANA
Development in SAP S/4HANA is a very broad topic, covering:
• ABAP Development,
• ABAP CDS (Core Data Service) Development
• Programming models for SAP Fiori
• Developing with SAP Cloud Platform.
As this is a long and complex topic, the first approach is to align and understand strategy for developments in SAP S/4HANA. You can find a summary
of key concepts, key architectural options, and decision matrix in:
Custom Extensions in SAP S/4HANA Implementations – A Guide for Senior IT Leadership
The following content is also helpful and can help your developers get a better understanding of the development efforts in SAP S/4HANA. You can
use these references to guide you in building a strong and flexible development plan after this training
• Introducing UI5 Tooling for SAPUI5 Projects
• The UI5 Tooling and SAPUI5 – The Next Step
• UI5 Tooling
• openSAP: SAP Fiori Overview: Design, Develop and Deploy
• openSAP: Evolved Web Apps with SAPUI5
• openSAP: Building Applications with SAP Cloud Application Programming Model
92
Ensuring Connectivity between SAP BTP, your desktop/network and SAP Backend
When working with SAP BTP you need to be aware of the connectivity requirements of each of the components in your landscape which in summary
are three:
1. Your desktop/network – Which acts as the integrator between the backend system and the SAP BTP Cloud services.
2. Your backend system – Which provides data from the business processes.
3. Your Cloud BTP account – Where cloud service administration is performed.
With these elements considered in your architecture, you need to make sure connections between all components are set up correctly. In the following
sections you will find the checks you should try to run to validate these connections.
Be aware that depending on your IT infrastructure some checks, or adjustments would need to be run by your IT department
93
Connectivity Checks between your desktop/network and SAP BTP
1. In your Global Account, per each of

your subaccounts identify the
Provider and Region where the
subaccount is located
2. Once you have identified Provider

and Region for your subaccount you
need to identify the IP addresses
listed for ingress communication
https://help.sap.com/viewer/65de2977205c403
bbc107264b8eccf4b/Cloud/en-
US/350356d1dc314d3199dca15bd2ab9b0e.ht
ml#loiof344a57233d34199b2123b9620d0bb41
94
3. The IP addresses listed in the

documentation need to be reachable
from your desktop/network. You can
test connectivity by using tools like
telnet and running the following
command
telnet <ingress IP Address> 443

Note – If you try running the command and the output mentions the command is not recognizable it most probably means telnet is not installed in
Note – Port 443 is the standard port used for your device. Depending on your OS you would need to run different procedures to install telnet.
HTTP(S) communication. Windows 10 – Install Telnet
MAC OS – Install Telnet
4. To test egress ports, you will most

probably need support from your IT
department, however, using tools like
NMAP you can find if the service is
reachable, and ports are open in your
network.
Nmap -Pn -p 80,443 <egress IP address>
Note – Using NMAP requires authorization

from your company as this is a powerful
network analysis tool.
Note – NMAP is NOT installed by default in your OS you first need to install NMAP in your system. This tool is widely used for network analysis so
you must first make sure your IT department allows you to install such tool
NMAP – Install on Windows
NMAP – Install on MAC
5. Once you have made sure that

ingress and egress ports are
reachable you have confirmed correct
communication between your
desktop/network and SAP BTP.
Note that depending on your IT administration policies some additional corrections or check might need to be done by your IT administration
team based on the results of the checks we have listed
95
Connectivity Checks between your desktop/network and SAP Backend
NOTE – In this section we will assume you have access to an SAP Cloud Appliance Library based backend system so we will show instructions for
checking connectivity to such type of systems, however, you can apply the same checks to your On-Premise SAP system.
1. Request your CAL administrator to

provide the ERP EXTERNAL IP
ADDRESS found in the instance
details in SAP CAL.
Take note of the IP address number
Note - In case of On-Premise systems,

request your SAP administrator to provide
the internal IP address of your SAP
Backend system
96
2. Request you SAP Basis administrator

to provide the list of available ICM
ports
Note – This list can be obtained by going to

transaction SMICM and selecting the services
button
Take note of the HTTP/HTTPS port numbers

and system hostname.
3. Ensure Hostname resolution works

correctly.
For On-Premise deployments, contact your

Basis team or IT department
For CAL deployments, before testing you first

need to add the external IP address to the
HOSTS file in your system.
Note – When using CAL, adding the external

IP address and hostname to your HOSTS file
will help the system map the resolution of the
numbers in the IP address to the default CAL
image system hostnames which are:
• vhcals4hci
Note – If using CAL, depending on your OS you will need to follow different instructions to add entries into your hosts file, use the following link to
• vhcals4hci.dummy.nodomain identify proper instructions to update your hosts file:
• vhcals4hcs.dummy.nodomain Linux, Windows and MAC – Edit Hosts file
• vhcals4hcs
• vhcalhdbdb
• vhcaldhbdb.dummy.nodomain
Ensure you add all 6 hostnames to the HOSTS

file
97
4. You can now test connectivity by

running the following telnet command
with syntax:
telnet <hostname> <your system HTTP(S) port>
Using this syntax when running a CAL system, you

could run the following command:
Note – Using the telnet command you will test IP to hostname mapping from your HOSTS file as you will notice the IP address is listed in the test.
telnet vhcals4hci.dummy.nodomain 9443 Plus, when the test is succesful you will notice a message stating a succesful connection to the host which means you can call any service from
that system.
5. If tests fail when using CAL instances,

you might need to review and request
you SAP CAL administrator to
validate available Access Points in
the instance configuration as access
might have been restricted during
initial configuration. You might need
to edit the settings of your SAP CAL
instance to allow HTTP(S) access for
ERP and specify your local IP or
public IP under “IP Range” on the
highlighted section shown in the
image.
Note – Depending on your OS version you will

need different instructions to identify your local
IP address. Use the following links to identify
the correct procedure to find your local IP
address:
Windows – Find local IP address

MAC – Find local IP address
To find your public IP address you can use a

public service like:
https://www.whatismyip.com/
Note – Your SAP CAL Administrator must enter IPv4 addresses in the configuration and can enter a single IP address (for example:
192.168.68.16) or specify a range of IP addresses using CIDR notation, also known as “slash notation” (for example: 192.168.0.0/16).
98
6. Once you have made sure that it is

possible to connect to the HTTP(S)
services exposed by the backend
system you have confirmed correct
communication between your
desktop/network and the SAP
backend.
Note that depending on your IT administration policies some additional corrections or check might need to be done by your IT administration
team based on the results of the checks we have listed
99
www.sap.com/contactsap
© 2021 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company.
The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product
specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty statements accompanying such products and services, if
any. Nothing herein should be construed as constituting an additional warranty.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related presentation, or to develop or release any functionality mentioned therein. This
document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platform directions and functionality are all subject to change and may be changed by
SAP SE or its affiliated companies at any time for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and
they should not be relied upon in making purchasing decisions.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product
and service names mentioned are the trademarks of their respective companies. See www.sap.com/trademark for additional trademark information and notices.

Getting Started With BAS and Cloud Connector

Uploaded by

Copyright:

Available Formats

Getting Started With BAS and Cloud Connector

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Getting Started With BAS and Cloud Connector

Uploaded by

Copyright:

Available Formats

5Steps2Fiori – Developer – WP01

1. Open the following link and select

2. In the next page, select the option to

3. The registration form will appear. If

Note – If you have an account on

Take note of the email and password

4. Upon successful registration an

5. Check your email to find the SAP

6. Start your trial account

7. If needed, verify your account by

8. Accept legal disclaimers

9. Select the region where your trial

Note: The following screenshots will be

10. Wait for the process to conclude.

11. Once the account generation

12. Enter your trial account

13. Your trial account is now setup,

Note – You can use extend this trial

Steps / Comments Screenshot

14. Open the following link and scroll down

15. Accept the license agreement

16. Once the download concludes, open and

17. Extract the file to an easily identifiable

Keep note of the folder path where you

Prerequisites: Hardware and internet Access

18. Open the following link and scroll

19. Download the file that corresponds to

20. Accept the license agreement

21. Once the download concludes, open

22. Extract the file to an easily identifiable

In this example, we have deployed SAP

23. In the directory where you deployed

24. Once the file is open, locate line 35

set JAVA_HOME= <Path to your own

Note – You defined this path when

25. In windows search options, search for

Note – You DO NOT need to run the

26. With the command line tools

cd <path to your SAP Cloud Connector

for example: cd Downloads\SAPCC

27. Once you have reached the

28. SAP Cloud Connector is now loading,

29. You will find a message stating SAP

Note – If you want to stop Cloud

30. Go to your browser and open the

If you are using your local machine:

If you are using a CAL instance

31. Click on Advanced

32. Click Continue

33. Logon window will be displayed. To

34. Once you have logged in you will be

Note – Take note of the password you

35. You have successfully installed and

Steps / Comments Screenshot

36. Before you setup the configuration for your

Note – The email and password for logon were

37. Once you have logged in click button “Go to

38. Once your Global Account is displayed, click

39. Copy the value of the ID parameter into a