一个初学者的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

1. Sometimes after restart, I need to Maven->Update project or else the servlet could not be successfully instantiated again!
2. 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

1. 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

1. https://jerrylist.cfapps.eu10.hana.ondemand.com/ui5 - SCN offline list

2018-04-23

1. 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.wdjerry.sap.corp

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.wdf.sap.corp: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.wdf.sap.corp:44355 does not work as well! 12:03PM

vete2015ld001.dhcp.wdf.sap.corp:8010 in video - can work! 12:05PM

ldai2gm6.wdf.sap.corp:50033 - can work as well! 12:08PM

1. create a destination based on my virtual system in Cloud-Foundry: http://my-backend:80
2. 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.

1. 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

1. 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 V**!!