You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/10-concepts/abap-development-tools-for-eclipse-54dd712.md
+17-9Lines changed: 17 additions & 9 deletions
Original file line number
Diff line number
Diff line change
@@ -8,9 +8,9 @@ ABAP development tools for Eclipse is SAP’s state-of-the-art integrated develo
8
8
9
9
## Features
10
10
11
-
ABAP development tools for Eclipse enables you to perform ABAP-based development tasks, when you want to build, to extend, and to run ABAP applications based on SAP products, such as SAP S/4HANA and SAP S/4HANA Cloud, private edition for classic ABAP development as well as SAP BTP ABAP environment and SAP S/4HANA Cloud for Cloud development.
11
+
ABAP development tools for Eclipse enables you to perform ABAP-based development tasks when you want to build, extend, and run ABAP applications based on SAP products, such as SAP S/4HANA and SAP S/4HANA Cloud Private Edition for classic ABAP development as well as SAP BTP ABAP environment and SAP S/4HANA Cloud Public Edition for Cloud development.
12
12
13
-
ABAP development tools for Eclipse supports ABAP developers with the following possibilities:
13
+
It supports ABAP developers with the following possibilities:
14
14
15
15
- Highly flexible, customizable Eclipse UI for ABAP development tools
16
16
@@ -27,7 +27,7 @@ ABAP development tools for Eclipse supports ABAP developers with the following p
27
27
- Built-in extensibility of the IDE using the established Eclipse plug-in technology
28
28
29
29
30
-
In particular, ABAP development tools for Eclipse is a modern development toolset where ABAP developers can use, for example the following features:
30
+
In particular, ABAP development tools for Eclipse is a modern development toolset where ABAP developers can use, among others, the following features:
31
31
32
32
- Syntax check
33
33
@@ -43,18 +43,26 @@ In particular, ABAP development tools for Eclipse is a modern development toolse
The [ABAP Development Tools for Eclipse guide](https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/about-abap-development-tools-user-guide?version=sap_cross_product_abap) describes the following features and functionalities of ADT:
54
+
55
+
- Joule for developers, ABAP AI capabilities supports you in the end-to-end development using generative AI and can be integrated into ABAP development tools for Eclipse. It's currently only available for customers using SAP BTP ABAP environment or SAP S/4HANA Cloud Public Edition. To leverage Joule for developers, ABAP AI capabilities, you need to purchase an additional license. See [Getting Started](https://help.sap.com/docs/abap-ai/generative-ai-in-abap-cloud/prerequisites-and-required-authorizations).
56
+
- Within the ABAP core development scenario: In particular, it focuses on use cases for creating, editing, testing, debugging, and profiling development objects like ABAP classes, ABAP Dictionary objects, function modules and so forth.
57
+
58
+
- For Core Data Services \(CDS\) in ABAP development for SAP HANA scenarios: In particular, it focuses on use cases for creating, editing, testing, and analyzing **ABAP CDS entities** like data definitions and so forth.
59
+
60
+
- When developing all types of SAP Fiori applications as well as publishing Web APIs in the context of the ABAP RESTful Application Programming Model \(RAP\)
61
+
62
+
- When creating lifecycle-stable and cloud-ready business apps, services, and extensions in the context of the [ABAP Cloud development model](https://help.sap.com/docs/abap-cloud/abap-cloud/abap-cloud-in-nutshell)
54
63
55
-
The [ABAP Development Tools: User Guide](https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/about-abap-development-tools-user-guide?version=sap_btp) describes the functionality and usage of the possibilities. It focuses on use cases for creating, editing, testing, debugging, and profiling development objects.
64
+
- For the integration of native SAP HANA objects \(in the context of SAP HANA repository content\) within the ABAP layer
56
65
57
-
The [ABAP CDS Development Tools: User Guide](https://help.sap.com/docs/abap-cloud/abap-cds-tools-user-guide/about-abap-cds-development-tools-user-guide?version=sap_btp) describes the functionality and usage of tools for ABAP Core Data Services \(CDS\) in the ABAP environment. It focuses on use cases for creating, editing, testing, and analyzing ABAP CDS entities.
58
66
59
67
60
68
@@ -88,5 +96,5 @@ To install ABAP development tools for Eclipse, follow the [Installation Guide](h
88
96
89
97
## Support
90
98
91
-
The use of ABAP development tools for Eclipse is subject to the terms and conditions of your license agreement with SAP which is directly related to the SAP shipment channel from whichABAP development tools for Eclipse was initially downloaded and installed.
99
+
The use of ABAP development tools for Eclipse is subject to the terms and conditions of your license agreement with SAP which is directly related to the SAP shipment channel from which ABAP development tools for Eclipse was initially downloaded and installed.
Copy file name to clipboardExpand all lines: docs/10-concepts/kyma-cli-292454b.md
+1-1Lines changed: 1 addition & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
# Kyma CLI
4
4
5
-
Kyma CLI is an essential tool for application developers who want to get started quickly and efficiently with SAP BTP, Kyma runtime. Designed to streamline workflows, it simplifies complex tasks, enabling developers to deploy and manage applications easily
5
+
Kyma CLI is an essential tool for application developers who want to get started quickly and efficiently with SAP BTP, Kyma runtime. Designed to streamline workflows, it simplifies complex tasks, enabling developers to deploy and manage applications easily.
6
6
7
7
> ### Caution:
8
8
> The `alpha` group commands are still in development, which means their functions and API may be modified over time. We encourage you to explore them, but keep in mind that changes may occur.
- To see all navigation options and the resources' aliases, enter enter the question mark sign `(?)`. For example, if you want to see your namespaces, it's enough to type `ns`.
19
+
- To see all navigation options and the resources' aliases, enter the question mark sign `(?)`. For example, if you want to see your namespaces, it's enough to type `ns`.
Copy file name to clipboardExpand all lines: docs/10-concepts/service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md
+92-15Lines changed: 92 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -16,7 +16,7 @@ This page explains the relationship between the service plans in the SAP Discove
16
16
17
17
### Overview
18
18
19
-
The diagram below shows how the service plans listed in the [SAP Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all&tab=service_plan) correspond to the plans you choose in the [SAP BTP cockpit](https://cockpit.btp.cloud.sap), depending on the commercial model of your enterprise global account. For more information about the commercial models offered by SAP, see [Commercial Models](commercial-models-263d400.md).
19
+
The diagram below shows how the service plans listed in the [SAP Discovery Center](https://discovery-center.cloud.sap/serviceCatalog/cloud-foundry-runtime?region=all&tab=service_plan) correspond to the plans you choose in the SAP BTP cockpit, depending on the commercial model of your enterprise global account. For more information about the commercial models offered by SAP, see [Commercial Models](commercial-models-263d400.md).
20
20
21
21

22
22
@@ -40,11 +40,15 @@ The plan that the global account administrator can assign to a subaccount or a d
40
40
> ### Tip:
41
41
> Open image in new tab for the full-screen version.
42
42
43
-

43
+

45
46
46
47
For more information about the procedure, see [Configure Entitlements and Quotas for Subaccounts](../50-administration-and-ops/configure-entitlements-and-quotas-for-subaccounts-5ba357b.md) or [Configure Entitlements and Quotas for Directories](../50-administration-and-ops/configure-entitlements-and-quotas-for-directories-37f8871.md).
47
48
49
+
> ### Note:
50
+
> The greyed out parts of the diagram indicate service plans that are automatically assigned to all subaccounts by default.
51
+
48
52
49
53
50
54
</dd><dt><b>
@@ -61,8 +65,9 @@ The plan that the subaccount administrator can select on the *Overview* page of
61
65
> ### Tip:
62
66
> Open image in new tab for the full-screen version.
63
67
64
-

68
+

66
71
67
72
68
73
@@ -271,9 +276,41 @@ standard
271
276
272
277
This is a **paid** plan for productive use. In the subscription-based commercial model, you pay for runtime memory quota in advance.
273
278
274
-
The runtime memory quota purchased with your subscription must be entitled to subaccounts through the service plan MEMORY. This service plan is associated with the service Cloud Foundry Runtime \(`APPLICATION_RUNTIME`\), which is specific to the subscription-based commercial model.
279
+
The runtime memory quota purchased with your subscription must be assigned to subaccounts through the service plan MEMORY. This service plan is associated with the service Cloud Foundry Runtime \(`APPLICATION_RUNTIME`\).
280
+
281
+
The plan **standard** is assigned to all subaccounts by default and can be enabled by a subaccount administrator. The runtime memory quota can be assigned to the subaccount only by a global account administrator \(or a directory administrator\). These steps are independent, but both of them are required to run applications in the Cloud Foundry environment.
282
+
283
+
</td>
284
+
</tr>
285
+
<tr>
286
+
<tdvalign="top"align="center">
287
+
288
+
\-
289
+
290
+
</td>
291
+
<tdvalign="top">
292
+
293
+
Cloud Foundry Environment \(`cloudfoundry`\)
294
+
295
+
</td>
296
+
<tdvalign="top">
297
+
298
+
build-runtime
299
+
300
+
</td>
301
+
<tdvalign="top">
302
+
303
+
build-runtime
304
+
305
+
</td>
306
+
<tdvalign="top">
307
+
308
+
This plan is only for using the SAP BTP, Cloud Foundry runtime as part of SAP Build. For more information, see [What Is SAP Build](https://help.sap.com/docs/build-service/build-service-guide/what-is-sap-build) and [Service Plans and Metering](https://help.sap.com/docs/build-service/build-service-guide/service-plans-and-metering).
309
+
310
+
> ### Note:
311
+
> The plan is not depicted on the diagram in the **Overview** section.
312
+
275
313
276
-
The plan **standard** is available for all subaccounts by default and can be enabled by a subaccount administrator. The runtime memory quota can be entitled to the subaccount only by a global account administrator \(or a directory administrator\). These steps are independent, but both of them are required to run applications in the Cloud Foundry environment.
277
314
278
315
</td>
279
316
</tr>
@@ -324,12 +361,17 @@ The table below provides details about the metrics for SAP BTP, Cloud Foundry ru
324
361
<tr>
325
362
<thvalign="top"align="center">
326
363
327
-
Service
364
+
Metric
328
365
329
366
</th>
330
367
<thvalign="top"align="center">
331
368
332
-
Metric
369
+
Service \(SAP BTP Cockpit\)
370
+
371
+
</th>
372
+
<thvalign="top"align="center">
373
+
374
+
Metric \(SAP BTP Cockpit\)
333
375
334
376
</th>
335
377
<thvalign="top"align="center">
@@ -346,6 +388,11 @@ Additional Information
346
388
<tr>
347
389
<tdvalign="top">
348
390
391
+
GB Memory
392
+
393
+
</td>
394
+
<tdvalign="top">
395
+
349
396
Cloud Foundry Runtime
350
397
351
398
</td>
@@ -354,7 +401,7 @@ Cloud Foundry Runtime
354
401
GB Memory
355
402
356
403
</td>
357
-
<tdvalign="top"rowspan="2">
404
+
<tdvalign="top"rowspan="3">
358
405
359
406
Temporary memory bank where computers store data that needs to be retrieved and processed quickly.
360
407
@@ -363,13 +410,40 @@ The memory represents the size of the data that can be processed and CPU represe
363
410
</td>
364
411
<tdvalign="top">
365
412
366
-
For billing purposes, the metric GB Memory is calculated as the total hourly usage of Cloud Foundry runtime memory across all spaces in the global account over a calendar month, divided by 730 hours and rounded up to the next full GB. For an example of such calculation, see [Consumption Monitoring](https://help.sap.com/docs/cf-runtime/cloud-foundry-runtime/monitoring-and-troubleshooting?version=Cloud#consumption-monitoring).
413
+
For billing purposes, the GB Memory metric for the Cloud Foundry Runtime service is calculated as the total hourly usage of Cloud Foundry runtime memory across all spaces in the global account over a calendar month, divided by 730 hours and rounded up to the next full GB. For an example of such calculation, see [Consumption Monitoring](https://help.sap.com/docs/cf-runtime/cloud-foundry-runtime/monitoring-and-troubleshooting?version=Cloud#consumption-monitoring).
367
414
368
415
> ### Note:
369
416
> In the Cloud Foundry environment, applications get a guaranteed CPU share of ¼ core per GB of runtime memory quota reserved for an application instance. For more information, see [SAP BTP-Specific Configurations](sap-btp-specific-configurations-9809fa4.md).
370
417
371
418
372
419
420
+
</td>
421
+
</tr>
422
+
<tr>
423
+
<tdvalign="top"rowspan="2">
424
+
425
+
Capacity Units
426
+
427
+
</td>
428
+
<tdvalign="top">
429
+
430
+
SAP Build
431
+
432
+
</td>
433
+
<tdvalign="top">
434
+
435
+
GB Memory
436
+
437
+
</td>
438
+
<tdvalign="top">
439
+
440
+
In SAP Build, the usage of SAP BTP, Cloud Foundry runtime is measured in capacity units. The GB Memory metric for the SAP Build service in the SAP BTP cockpit is intended only for monitoring the approximate usage of SAP BTP, Cloud Foundry runtime in GB when it's consumed as part of SAP Build. For more information, see [What Is SAP Build](https://help.sap.com/docs/build-service/build-service-guide/what-is-sap-build?version=Cloud).
441
+
442
+
> ### Note:
443
+
> The metric is not depicted on the diagram in [Service](service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md#loio8d41fa40e47b45bf90d38e393a989c4c__service).
444
+
445
+
446
+
373
447
</td>
374
448
</tr>
375
449
<tr>
@@ -385,7 +459,7 @@ CF Runtime
385
459
</td>
386
460
<tdvalign="top">
387
461
388
-
The metric CF Runtime is intended for monitoring the usage of SAP BTP, Cloud Foundry runtime when it's used as part of SAP Build Code. For more information, see [What Is SAP Build Code](https://help.sap.com/docs/build_code/d0d8f5bfc3d640478854e6f4e7c7584a/504854f457cc4fbf9f79136dbc773618.html).
462
+
In SAP Build Code, the usage of SAP BTP, Cloud Foundry runtime is measured in capacity units. The CF Runtime metric for the SAP Build Code service in the SAP BTP cockpit is intended only for monitoring the approximate usage of SAP BTP, Cloud Foundry runtime in GB when it's consumed as part of SAP Build Code. For more information, see [What Is SAP Build Code](https://help.sap.com/docs/build_code/d0d8f5bfc3d640478854e6f4e7c7584a/504854f457cc4fbf9f79136dbc773618.html) and [SAP Build Code Capacity Unit Calculator](https://build-code-calculator.cfapps.eu10-004.hana.ondemand.com/).
389
463
390
464
> ### Note:
391
465
> The metric is not depicted on the diagram in [Service](service-plans-and-metering-for-cloud-foundry-runtime-8d41fa4.md#loio8d41fa40e47b45bf90d38e393a989c4c__service).
@@ -417,6 +491,9 @@ There are two application settings that define how much runtime memory an applic
417
491
- Number of running application instances \(default: 1\)
418
492
419
493
494
+
> ### Note:
495
+
> The total amount of runtime memory that an application uses when all of its instances are running is displayed on the application's *Overview* page under *All Instances Memory*.
496
+
420
497
You can specify custom values for these settings when deploying an application in the Cloud Foundry environment. You can also change them for an application that has already been deployed without having to redeploy it.
421
498
422
499
@@ -435,9 +512,9 @@ You can specify custom values for these settings when deploying an application i
435
512
- Using the SAP BTP cockpit: [Deploy an Application](../50-administration-and-ops/deploy-an-application-09fdb9b.md)
436
513
- Using the Cloud Foundry CLI: [https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html](https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html)
437
514
438
-
-**Option 2:** In the SAP BTP cockpit, choose *Deploy Application*, deselect *Use Manifest* and specify the following:
515
+
-**Option 2:** In the SAP BTP cockpit, choose *Deploy Application*, select *Custom Settings* and specify the following:
439
516
440
-
-*Instance Memory \(MB\)*: runtime memory quota per application instance
517
+
-*Memory per Instance\(MB\)*: runtime memory quota per application instance
441
518
-*Number of Instances*: number of application instances
442
519
443
520
For more information about the procedure, see [Deploy an Application](../50-administration-and-ops/deploy-an-application-09fdb9b.md).
@@ -456,7 +533,7 @@ You can specify custom values for these settings when deploying an application i
456
533
457
534
-**Option 1:** In the SAP BTP cockpit, on the *Overview* page of the application you can:
458
535
459
-
- Change the runtime memory quota per application instance under *Change Instance Details*\>*Instance Memory \(MB\)*
536
+
- Change the runtime memory quota per application instance under *Change Instance Details*\>*Memory per Instance\(MB\)*
460
537
- Change the number of application instances as described in [Manage Application Instances](../50-administration-and-ops/manage-application-instances-75836f1.md)
461
538
462
539
-**Option 2:** In the Cloud Foundry CLI, you can use the command `cf scale` with the following flags:
The error ***401 Unauthorized*** occurs when you try to access a Service that requires authentication, and the appropriate credentials were not provided or were incorrect. You get the error ***403 Forbidden*** when you try to access a Service or perform an action for which you lack permission.
0 commit comments