日韩性视频-久久久蜜桃-www中文字幕-在线中文字幕av-亚洲欧美一区二区三区四区-撸久久-香蕉视频一区-久久无码精品丰满人妻-国产高潮av-激情福利社-日韩av网址大全-国产精品久久999-日本五十路在线-性欧美在线-久久99精品波多结衣一区-男女午夜免费视频-黑人极品ⅴideos精品欧美棵-人人妻人人澡人人爽精品欧美一区-日韩一区在线看-欧美a级在线免费观看

歡迎訪問 生活随笔!

生活随笔

當前位置: 首頁 > 编程资源 > 编程问答 >内容正文

编程问答

一个初学者的SAP Cloud Platform学习笔记

發布時間:2023/12/19 编程问答 23 豆豆
生活随笔 收集整理的這篇文章主要介紹了 一个初学者的SAP Cloud Platform学习笔记 小編覺得挺不錯的,現在分享給大家,幫大家做個參考.

User

p1942400002trial
i042416trial

Host

hanatrial.ondemand.com

工作日志

2017-05-01

956我為什么沒辦法publish 到cloud 上去?
1004可能我有個工具沒裝。新Eclipse還是需要配proxy
Possible hint: https://archive.sap.com/discussions/thread/3857381
finally it works: https://helloworldi042416trial.hanatrial.ondemand.com/JerryTest/

1518: I would like to achieve both servlet and html work. Is it really possible? I tried in local it is possible. Verified 1628, it is possible!
1613: 果然重啟大法好。。。

2017-05-07

  • Sometimes after restart, I need to Maven->Update project or else the servlet could not be successfully instantiated again!

  • workaround does not work for resources in HCP?! Verified, workaround can still works if the web application is started in local server, but does not work in HCP.

  • 2017-05-20

    My Fiori application in HCP: https://flpportal-i042416trial.dispatcher.hanatrial.ondemand.com/sites?siteId=6af9e0d2-8b95-413c-9dc5-7d8b0c8b0ec1#jerrylist-Display

    • 2018-11-21 checked and it still works.

    I am in Europe-Rot-Trial.

    cf target -s dev

    Error restarting application: BuildpackCompileFailed

    cf logs jerry_list_wiesloch --recent
    package.json is missing

    npm install express - lots of file generated in my project folder 😃

    cf api https://api.cf.us10.hana.ondemand.com

    cf api https://api.cf.eu10.hana.ondemand.com - Jerry

    2017-07-15

    https://jerry-list-wiesloch.cfapps.us10.hana.ondemand.com

    how the CF is clever enough to know that index.html should be executed??

    https://jerrylist.cfapps.eu10.hana.ondemand.com/ui5 can access now.
    https://jerrylist.cfapps.eu10.hana.ondemand.com - 囧,要加https

    set HTTPS_PROXY=http://proxy.diablo.corp:8080

    2017-05-27

  • https://jerryordercount.cfapps.eu10.hana.ondemand.com
  • https://jerryordercount.cfapps.eu10.hana.ondemand.com/jerry/OneOrderHCP.html --Jerry checks on 2017-07-15 that it could still be accessed.
    2018-04-23 12:44PM - down.

    2017-07-15

    user: my sap email
    password: the one to access my laptop!!!

    2017-08-05

  • https://jerrylist.cfapps.eu10.hana.ondemand.com/ui5 - SCN offline list
  • 2018-04-23

  • 12-factor application
  • 2018-04-30

    how to set proxy for cf login

    CF_TRACE=true

    2018-04-29

    jpa - java persistence api - 只需要定義annotation即可訪問DB。

    p1942399991trial

    10:10PM - 不出所料要出幺蛾子,部署上去之后404 error。

    2018-04-30

    JPA支持XML和JDK5.注解兩種元數據的形式,元數據描述對象和表之間的映射關系,框架據此將實體對象持久化到數據庫表中;

    • API

    用來操作實體對象,執行CRUD操作,框架在后臺替代我們完成所有的事情,開發者從繁瑣的JDBC和SQL代碼中解脫出來。

    • 查詢語言

    這是持久化操作中很重要的一個方面,通過面向對象而非面向數據庫的查詢語言查詢數據,避免程序的SQL語句緊密耦合。

    10:03AM SCP sample用的也是EclipseLink作為JPA實現。

    the transaction-type defines the application type (J2EE of JSE). The value RESOURCE_LOCAL defines a JSE application

    org.eclipse.persistence.jpa.PersistenceProvider:EclipseLink class

    11:24am 還是沒進展。

    5:15PM - Server jerryjdbc.p1942399991trial at hanatrial.ondemand.com was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor.

    JDBC done on 5:23PM

    2018-05-01

    11:23AM

    6:27PM - week 3 done.

    http://services.odata.org/v2/Northwind/Northwind.svc/

    6:58PM - Failure reason: “Not Implemented” Received status code: “501”

    A 501 error is not something you can fix, but requires a fix by the web server you are trying to access.
    A 501 response is cacheable by default.

    7:05PM - no answer: https://archive.sap.com/discussions/thread/3607977

    7:21PM - error message: Content is unexpected for the Get operation

    With this configuration you can use the destination for any app inside SAP Web IDE. Whenever an app calls a (local) service beginning with /destinations/northwind/*, the created destination becomes active as a simple proxy. This helps to prevent any possible issues related to the same-origin policy of browsers.

    Actual url observed in my Chrome: https://webidetesting5799545-i042416trial.dispatcher.hanatrial.ondemand.com/Jerry_destination_northwind/v2/Northwind/Northwind.svc/$batch

    At runtime, the relative URL /V2/Northwind/Northwind.svc/ is prefixed with /destinations/northwind. As a result, all our Northwind OData requests will be proxied via the Northwind OData Service destination that is defined in the SAP HANA Cloud Platform Cockpit. The destination contains the URL to the resource http://services.odata.org and has the proxy type Internet. From this configuration the proxy knows where the requests shall go to.

    8:06PM works 😃

    url: https://webidetesting5799545-i042416trial.dispatcher.hanatrial.ondemand.com/Jerry_destination_northwind/v2/Northwind/Northwind.svc/$batch

    unit 1 done

    2018-05-10

    unit 2 in Jinan hotel:幺蛾子又來了。我點test connection結果和video不一樣。3:49PM
    預料中的500 error:4:28PM

    SAP help 4:40PM

    6:00PM - neo-java-web-sdk-2.73.15 - Java Web Tomcat 7

    neo-java-web-sdk-2.98.15 - Tomcat 7

    to consume connectivity configuration using JNDI, you need to define the ConnectivityConfiguration API as a resource in the web.xml file. Below is an example of a ConnectivityConfiguration resource, named connectivityConfiguration.

    <resource-ref><res-ref-name>connectivityConfiguration</res-ref-name><res-type>com.sap.core.connectivity.api.configuration.ConnectivityConfiguration</res-type> </resource-ref>

    6:26PM - 一大堆編譯錯誤!

    6:32PM try neo-java-web-sdk-3.52.15.zip Tomcat 8

    SAP Cloud Platform applications run on a modular and lightweight application runtime container where they can use the platform services APIs and Java EE APIs according to standard patterns.

    Eclipse log location: C:\Users\i042416\scp20180425.metadata

    Fetch the lastest SDK version - 6:40死在這里了。

    !ENTRY com.sap.core.tools.eclipse.server.javaweb 4 0 2018-05-10 18:41:22.609
    !MESSAGE Failed to get latest neo-java-web version from maven central
    !STACK 0
    java.net.SocketException: Connection reset

    6:55PM java8的SDK老是下載不下來。
    7:02PM download via WTS

    http://maps.googleapis.com/maps/api/distancematrix - 404 not found during test

    7:16PM - 至少學會了如何local調試。

    7:59pm - application部署不上去-啟動不起來。 8:04PM

    Server jerryconnecttest.i042416trial at hanatrial.ondemand.com was unable to start within 120 seconds. If the server requires more time, try increasing the timeout in the server editor.

    8:17PM server在Eclipse里顯示一直是Not authenticated狀態

    8:23PM 找到solution了,先把resource從server移除,publish,再重新run as server,可以work。

    SYSTEM/Saptest1Sap12345

    10:45PM - 繼續幺蛾子。HANA dev workbench無法使用。
    403 - Forbidden
    The server refused to fulfill the request.

    10:50 SAP HANA Web-Based Development Workbench 403 error - 還真有人和我遇到一樣的問題。

    10:55 問題解決。

    2018-05-11

    11:02AM - 還是403 error
    11:09AM - issue resolved.

    2018-05-14

    3:03PM week4 unit 2 done.
    3:41PM gradle in Jianshu

    4:04PM - Exception in thread “main” com.google.gson.JsonSyntaxException: java.lang.IllegalStateException: Expected a string but was BEGIN_OBJECT at line 31 column 15 path $.request

    4:27PM - 在request屬性掛了。

    4:50PM - Expected BEGIN_ARRAY but was BEGIN_OBJECT at line 31 column 15 path $.request

    5:04PM - Expected a string but was BEGIN_OBJECT at line 35 column 17 path $.request.options

    2018-05-15

    11:24AM - once cloud connector is installed, service could not be launched!

    11:46AM - 500 Failed to sign the cloud connector certificate for subaccount i042416trial@hanatrial.ondemand.com. Verify configuration and proxy settings — see ‘‘Log And Trace Files’’ for details

    root cause: proxy should be proxy.

    2:11PM unit 4

    3:42PM - Problem while publishing 幺蛾子又來了。
    Problem during deploymentDeploy REST API failed to process request
    Deploy REST API failed to process request

    Connector維護的是SCP的用戶和密碼,proxy為proxy.sha.

    2018-05-16

    6:01PM - Unit 5: Connecting Cloud Databases

    2018-05-17

    3:45PM - some one also has the same question as me: https://archive.sap.com/discussions/thread/3953840

    5:34PM if I change with this one:

    javax.persistence.jdbc.driver=com.sap.dbtech.jdbc.DriverSapDB

    I will end up with error:

    Type Exception Report

    Message javax.naming.NamingException: Cannot create resource object instance due to exception in the object factory [Root exception is java.lang.NullPointerException]

    Description The server encountered an unexpected condition that prevented it from fulfilling the request.

    Exception

    javax.servlet.ServletException: javax.naming.NamingException: Cannot create resource object instance due to exception in the object factory [Root exception is java.lang.NullPointerException]
    com.sap.cloud.sample.persistence.PersistenceWithJDBCServlet.init(PersistenceWithJDBCServlet.java:40)
    javax.servlet.GenericServlet.init(GenericServlet.java:158)
    org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504)
    com.sap.cloud.runtime.impl.bridge.security.AbstractAuthenticator.invoke(AbstractAuthenticator.java:206)

    correct: com.sap.db.jdbc.Driver

    2018-05-28

    for RFC, the host ldciag3:sapgw54 works. If I type port number 54, it will be written to sapgw54 automatically. If I manually remove sapgw, only reserve 54, the ping connection does not work any more.

    ldai1ag3:44355 does not work as well! 12:03PM

    vete2015ld001:8010 in video - can work! 12:05PM

    ldai2gm6:50033 - can work as well! 12:08PM

  • create a destination based on my virtual system in Cloud-Foundry: http://my-backend:80

  • create a destination instance in Service MarketPlace, name: jerry-destination-lite
    how to bind this instance with application?

  • adding the name of the destination instance in the manifest of the application. During the deployment of the app, the binding will be then added automatically.

  • create connectivity instance.
  • SAP Cloud Platform Connectivity provides a standard HTTP proxy for on-premise connectivity to be accessible by any application.

    In order to consume the data coming from the on-premise in the application via the HTTP proxy, we need to create an SAP Cloud Platform Connectivity instance and bind it to the application. When a binding is created the application gets connectivity credentials in its environment variables.

    name: connectivity-jerry-demo

  • XSUAA instance creation
  • This central identity management service for the Cloud Foundry environment manages application authorizations and the trust to identity providers.

    By calling the application, the user will be redirected to the XSUAA and will be prompt to give his credentials. It will then achieve certain checks like verifying the OAuth client, client’s scopes, user’s scopes (Scopes are permissions to access one or more resources). Assuming everything is fine, the user will be authenticated and the XSUAA will redirect the browser to the application.

    In a second step the application will take the client Id and the client secret and will talk directly with the XSUAA to get an access token. Then the application will sent both tokens as HTTP header so that it can consume the backend system via the SAP Cloud Platform Connectivity.

    name: xsuaa-jerry-demo

    parameter:

    {"xsappname" : "connectivity-jerryapp-demo","tenant-mode": "dedicated" }

    2018-05-29

    幺蛾子又開始了 11:46AM npm config set @sap:registry https://npm.sap.com/

    The operation was rejected by your operating system.
    npm ERR! It’s possible that the file was already in use (by a text editor or antivirus),
    npm ERR! or that you lack permissions to access it.

    Error: EPERM: operation not permitted, open ‘C:\Users\i042416.npmrc’
    npm ERR! at Error (native)
    npm ERR! { Error: EPERM: operation not permitted, open ‘C:\Users\i042416.npmrc’
    npm ERR! at Error (native)
    npm ERR! stack: ‘Error: EPERM: operation not permitted, open ‘C:\Users\i042416\.npmrc’\n at Error (native)’,
    npm ERR! errno: -4048,
    npm ERR! code: ‘EPERM’,
    npm ERR! syscall: ‘open’,
    npm ERR! path: ‘C:\Users\i042416\.npmrc’ }
    npm ERR!
    npm ERR! The operation was rejected by your operating system.
    npm ERR! It’s possible that the file was already in use (by a text editor or antivirus),
    npm ERR! or that you lack permissions to access it.
    npm ERR!
    npm ERR! If you believe this might be a permissions issue, please double-check the
    npm ERR! permissions of the file and its containing directories, or try running
    npm ERR! the command again as root/Administrator (though this is not recommended).

    npm ERR! A complete log of this run can be found in:
    npm ERR! C:\Users\i042416\AppData\Roaming\npm-cache_logs\2018-05-29T04_20_06_965Z-debug.log

    multiple target application in SAP help

    The HANA DB runs as a service as part of SAP CF. Hence all the DB artifacts are deployed into its runtime container of Hana DB on CF.

    XS Classic has been deprecated since HANA 2.0 SPS02. It means that if you choose to develop on top of it now, you will eventually have to migrate.

    2018-07-08

    Reminder: by default my SAP Cloud Connector has been configured under corporate proxy, so if you are at home, please establish connection via VPN!!

    創作挑戰賽新人創作獎勵來咯,堅持創作打卡瓜分現金大獎

    總結

    以上是生活随笔為你收集整理的一个初学者的SAP Cloud Platform学习笔记的全部內容,希望文章能夠幫你解決所遇到的問題。

    如果覺得生活随笔網站內容還不錯,歡迎將生活随笔推薦給好友。