Overview
ENROLL TO THE COURSE HERE (in case you haven’t, yet): Course: Introduction to SAP HANA Cloud Platform (repeat)
You can find a list of the course guides for each week of this course in the corresponding parent project of this blog post.
Course Guide Week 2 – Persistency Basics
Hi everyone,
in the second week of the course Introduction to SAP HANA Cloud Platform we will provide you with some basics around the usage of the Persistence Service of our platform.
Find below additional information that can be useful to you during this course week. While monitoring the forums I’ll also add some sections around common mistakes and how to fix them into the corresponding units.
Table of Contents
Unit 1 – Introduction & First Steps With EJB
Common Issues
Persistence operation failed with reason: The bean encountered a non-application exception
When inserting a value in the ejb sample’s UI he following exception is displayed:
Persistence operation failed with reason: The bean encountered a non-application exception; nested exception is: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services – 2.4.1.v20121003-ad44345): org.eclipse.persistence.exceptions.DatabaseException Internal Exception: com.sap.db.jdbc.exceptions.JDBCDriverException: SAP DBTech JDBC: [274]: inserted value too large for column: 49620af6-80cd-454b-a95b-258eab7e287c Error Code: 274 Call: INSERT INTO T_PERSONS (ID, FIRSTNAME, LASTNAME) VALUES (?, ?, ?) bind => [3 parameters bound] Query: InsertObjectQuery(com.sap.cloud.sample.persistence.Person@8de9f444)
Solution: You’re using HANA schema without setting the additional property: <property name=”eclipselink.target-database” value=”com.sap.persistence.platform.database.HDBPlatform”/> in the persistence.xml.
1. go the cockpit -> Your application -> Database Schemas and delete the schema of the application.
2. set the property in persistence.xml
3. deploy/run the application again
MaxDB, HANA database, and the Target Database
Some participants realized that after deployment of their application they ended up with a schema on a MaxDB rather than a HANA database. You can check this in the Cloud Cockpit. Just click on Database Schemas and check the database type of your schema.
In the course you learned how to set the target database to com.sap.persistence.platform.database.HDBPlatform. (in the video this step has been shown at around 10:20). It is necessary to instruct EclipseLink to use HANA specific commands, types, etc. to access (an already existing) HANA database. However, it does not create a schema on a HANA database.
Actually a schema is created when an application is deployed in the cloud for the first time. The DB type that is used depends on the default settings that you can control in the Cloud Cockpit. So what you have to do in addition is to change the default settings in the Cloud Cockpit to HANA as described in Changing the Default Database and deploy your application with a new name (that forces the creation of a new schema).
I don’t see the JPA Content object in my eclipse IDE
- Right Click on your JPA project, in the menu which appears click on properties.
- In the properties window Select Project Facets.
- If Project Facets are not displayed click on link saying convert to facetted project.
- If Facets already available select Checkbox against JPA.
- Below the Properties window a link appears “Further configurations required”.
- Click on this link.
- In JPA facets window which appears select EclipseLink 2.X.X from Platform drop down and Disable Library Configuration from JPA Implementation drop down.
- Click OK
The JPA Content should appear now.
Additional Links
- About EJB (Enterprise Java Beans): http://en.wikipedia.org/wiki/Enterprise_JavaBeans
Unit 2 – Connecting To Your Database
Compared to the first course we’ve conducted last year it got much easier to connect to your HANA instance on the SAP HANA Cloud Platform via Eclipse or the SAP HANA Studio. The necessary db-tunnel is created for you automatically without you having to setup something.
Additional Links
- Connecting to SAP HANA Instances on SAPHCP from Eclipse IDE
- Syntax of the properties file provided in the console client commands
- Setting up the console client
Unit 3 – Creating A JDBC Application
Additional Links
- About JDBC (Java DataBase Connectivity): http://en.wikipedia.org/wiki/Jdbc
Hi Rui,
Re unit 2 – I think we should not refer to SAP HANA Studio any longer now that it’s part of the SAP Development Tools for Eclipse site. You could link to my blog instead: Connecting to #SAP #HANA Instances on #SAPHCP from #Eclipse IDE
Cheers,
–Vlado
PS: Sorry for Portugal’s defeat yesterday, I also expected more from Cristiano…
Thanks Vlado! Good idea. Just changed the blog post.
Rui
PS: Didn’t even notice during the game that Ronaldo was playing. Thought he was sleeping 🙂
Haii Rui
I am getting issues while adding system through admn console pls help
After adding trial landscape/finish then popup shows could not connect to SAP HANA cloud system.Check error log for more details. Error log showing db tunnel error. your suggestion is awaited
Seem to be getting issue when importing the EJB, I had no issues until now. Something todo with Java setup but not sure what issue is.
Hi Karl,
please provide the following screenshot:
Right-click on the project -> Properties -> Java Build Path
This schould looks like this:
Best regards,
Artem
Thanks Artem, looks like I have the wrong sdk set up, trying now to re configure the server to point to neo-javaee6-wp-sdk-2.34.16.1
HI there,
I completed Week2 and Unit1 yesterday. Everything worked perfectly.Once I tried opening Eclipse today I get the error below:
I have not changed anything in my system.Please help.Thank you
Somebody must have changed something, since the eclipse can’t find you Java installation anymore 🙂
Please open the eclipse.ini in the eclipse folder and add following line at the top of the file:
-vm
<Path to the java on your system>
for example:
-vm
C:/Program Files/Java/jdk6/bin/javaw.exe
This let eclipse know which java it should use instead of look up for the java on your system automatically
Best regards,
Artem
It works!! Thank you for your help 🙂
You are welcome!
Hi All, I am struggling with the following error when trying to implement the exercise week 2 unit 1: When I goto the Application URL , I get the following message:
Persistence with EJB Sample!
Persistence operation failed with reason: while trying to invoke the method com.sap.cloud.sample.persistence.PersonBean.getAllPersons() of an object loaded from field com.sap.cloud.sample.persistence.PersistenceWithEJBServlet.personBean of an object loaded from local variable ‘this’
Note I have also implemented the recommended solution for “Persistence operation failed with reason: The bean encountered a non-application exception”
Any tips would be apprecaited
LOGGING INFO
LOGGER
com.sap.cloud.sample.persistence.PersistenceWithEJBServlet
TEXT
Persistence operation failed
java.lang.NullPointerException: while trying to invoke the method com.sap.cloud.sample.persistence.PersonBean.getAllPersons() of an object loaded from field com.sap.cloud.sample.persistence.PersistenceWithEJBServlet.personBean of an object loaded from local variable ‘this’
at com.sap.cloud.sample.persistence.PersistenceWithEJBServlet.appendPersonTable(PersistenceWithEJBServlet.java:57)
at com.sap.cloud.sample.persistence.PersistenceWithEJBServlet.doGet(PersistenceWithEJBServlet.java:34)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:735)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at com.sap.core.communication.server.CertValidatorFilter.doFilter(CertValidatorFilter.java:321)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
at com.sap.security.auth.service.webcontainer.internal.Authenticator.invoke(Authenticator.java:192)
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:98)
at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
at com.sap.core.tenant.valve.TenantValidationValve.invokeNextValve(TenantValidationValve.java:221)
at com.sap.core.tenant.valve.TenantValidationValve.invoke(TenantValidationValve.java:103)
at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:24)
at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:27)
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:315)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:743)
You seem to be using the wrong SDK. EJB is only supported with neo-javaee6-wp-sdk-2.x.
Hi Rui,
I have made the changes as you mentioned for the error “
Persistence operation failed with reason: The bean encountered a non-application exception”.
But I am still getting the same error, can yoiu please help here.,\
Regards,
Manish
Hi Manish, please post your question into the openSAP forum for the course. At that place you have many of my colleagues providing help and support.
Best,
Rui
Hi Rui,
I am getting the following issue while adding SAP HANA Cloud Platform System,
Connection Failed:
Could not connect to SAP HANA Cloud Platform System.
But of course I was able to fetch trial instance. The error is only after clicking ‘Finish’.
Pl help.
Regards
Lakshmi
Can you provide more details about the error e.g. from the Eclipse log (<workspace>/metadata/.log)?
Hi Pavlov,
here is the Error log : Could not add SAP HANA Cloud Platform system
Exception Stack Trace :
com.sap.jpaas.infrastructure.console.exception.CommandException: Failed to connect the tunnel
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:69)
at com.sap.core.persistence.commands.tunnel.api.CommandTunnelHandler.openTunnel(CommandTunnelHandler.java:97)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.openTunnel(CloudSystemHelper.java:270)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.connectToSapSystem(CloudSystemHelper.java:327)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:87)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.sap.core.connectivity.tunnel.api.management.ConnectionFailedException: Unable to establish tunnel connection
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:40)
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:66)
… 10 more
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Unknown Source)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:108)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:70)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.channel.Channels.connect(Channels.java:634)
at org.jboss.netty.channel.AbstractChannel.connect(AbstractChannel.java:207)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182)
at com.sap.core.connectivity.tunnel.client.AbstractClient.establishConnection(AbstractClient.java:96)
at com.sap.core.connectivity.tunnel.client.AbstractClient.doConnect(AbstractClient.java:83)
at com.sap.core.connectivity.tunnel.client.TunnelClient.connect(TunnelClient.java:102)
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:36)
… 11 more
Error 2 : Connection to host ‘hanatrial.ondemand.com’ failed.
Exception Stack Trace :
org.eclipse.core.runtime.CoreException: Could not add SAP HANA Cloud Platform system
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.connectToSapSystem(CloudSystemHelper.java:424)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:87)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: com.sap.jpaas.infrastructure.console.exception.CommandException: Failed to connect the tunnel
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:69)
at com.sap.core.persistence.commands.tunnel.api.CommandTunnelHandler.openTunnel(CommandTunnelHandler.java:97)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.openTunnel(CloudSystemHelper.java:270)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.connectToSapSystem(CloudSystemHelper.java:327)
… 7 more
Caused by: com.sap.core.connectivity.tunnel.api.management.ConnectionFailedException: Unable to establish tunnel connection
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:40)
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:66)
… 10 more
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Unknown Source)
at sun.nio.ch.SocketChannelImpl.connect(Unknown Source)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:108)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:70)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.channel.Channels.connect(Channels.java:634)
at org.jboss.netty.channel.AbstractChannel.connect(AbstractChannel.java:207)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182)
at com.sap.core.connectivity.tunnel.client.AbstractClient.establishConnection(AbstractClient.java:96)
at com.sap.core.connectivity.tunnel.client.AbstractClient.doConnect(AbstractClient.java:83)
at com.sap.core.connectivity.tunnel.client.TunnelClient.connect(TunnelClient.java:102)
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:36)
… 11 more
Thanks in advance
Lakshmi
Hi Rui,
I am getting the following issue when I am clicking loggers – unit3 week 2 one
Please provide me the solution on it.
Hi Naveen,
we have a problem in the monitoring&logging infrastructure. Please follow
which will be updated once the issues are solved.
Best regards,
Nikolay
Thanks Nikolay…..
hello Rui,
While i was trying to work on week 2 unit 5 and i complete the demo and in the last step when i try to restart the server to get results it just stays in status starting and never gets to status started.
i get follwoing 2 warnings which are attached can you please help me as to why this is happening.
warnings
Hi Anu, nothing to be worried about. As long as you don’t have any errors everything is fine.
Best,
Rui
Thanks Rui for another week of training material. Well explained in an enthusiastic way.
The logging part looked different compared to what you showed in the training. Guess that’s a release thingy 😉
Up to the next week…
Twan
You are welcome Twan. Hope you enjoy it.
Best,
Rui
Hi Rui,
I have been enjoying the course.
By the time I got into week2 assignment yesterday it was late and now it is locked.
I could not take the test. can you help please?
Thanks
Bala
Hi Bala, if the weekly assignment is passed there is nothing you can do. Sorry.
Just move on with the next week.
Best,
Rui
Hi Rui
Hi Rui
Week2- Unit 2
I a not able to add the Cloud Trial Instance. When I try to add Cloud account and Select Dropdown of Trial instance it gives me error- Could not connect to SAP HANA Clpud platform system.
java.util.concurrent.ExecutionException: com.sap.jpaas.infrastructure.console.exception.CommandException: Failed to connect the tunnel
at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
at java.util.concurrent.FutureTask.get(FutureTask.java:83)
at com.sap.ndb.studio.common.CallableUtil.executeCallable(CallableUtil.java:62)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1.run(CloudSystemConnectionWizard.java:96)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
Caused by: com.sap.jpaas.infrastructure.console.exception.CommandException: Failed to connect the tunnel
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:75)
at com.sap.core.persistence.commands.tunnel.api.CommandTunnelHandler.openTunnel(CommandTunnelHandler.java:141)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.openTunnel(CloudSystemHelper.java:268)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemHelper.addCloudSystem(CloudSystemHelper.java:323)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:87)
at com.sap.cloud.tools.eclipse.hana.tunnel.ui.CloudSystemConnectionWizard$1$1.call(CloudSystemConnectionWizard.java:1)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
at java.lang.Thread.run(Thread.java:695)
Caused by: com.sap.core.connectivity.tunnel.api.management.ConnectionFailedException: Unable to establish tunnel connection
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:36)
at com.sap.core.persistence.commands.tunnel.connection.DbTunnelManager.startTunnelClient(DbTunnelManager.java:72)
… 10 more
Caused by: java.nio.channels.UnresolvedAddressException
at sun.nio.ch.Net.checkAddress(Net.java:36)
at sun.nio.ch.SocketChannelImpl.connect(SocketChannelImpl.java:512)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.connect(NioClientSocketPipelineSink.java:108)
at org.jboss.netty.channel.socket.nio.NioClientSocketPipelineSink.eventSunk(NioClientSocketPipelineSink.java:70)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.handler.codec.oneone.OneToOneEncoder.handleDownstream(OneToOneEncoder.java:54)
at org.jboss.netty.channel.Channels.connect(Channels.java:634)
at org.jboss.netty.channel.AbstractChannel.connect(AbstractChannel.java:207)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:229)
at org.jboss.netty.bootstrap.ClientBootstrap.connect(ClientBootstrap.java:182)
at com.sap.core.connectivity.tunnel.client.AbstractClient.establishConnection(AbstractClient.java:85)
at com.sap.core.connectivity.tunnel.client.AbstractClient.doConnect(AbstractClient.java:72)
at com.sap.core.connectivity.tunnel.client.AbstractTunnelClient.connect(AbstractTunnelClient.java:47)
at com.sap.core.connectivity.tunnel.client.management.DirectTunnelOperatorImpl.connect(DirectTunnelOperatorImpl.java:32)
… 11 more
Hi Akash, did you check your proxy settings? If yes, please post your question into the openSAP forum for the course. At that place you have many of my colleagues providing help.
Best,
Rui
Thanks RUi. I will move this thread to Opensap forum. My Proxy setting are as per what is suggested but still getting this error. I am usig Macbook. I also checked my port and its not using 3 series
Hi Rui,
I’m following the week 2 unit 4 Sharing data between applications.
I was trying to check and try the different console commands.
When I try to connect from within the SDK directory I’m almost connected (after specifing host, user and account, and correct pasword) but I get the message
” User Pxxxxxxx has no permission to ‘read DBI Information’ in account pxxxxxxx”.
Can you let me know how to solve this issue ?
Thanks,
Guy
Did you provide the right account name? It needs to be pxxxxxtrial
Have you provided that?
Best,
Rui
Hi rui,
thanks for the quick reply.
Indeed I did not use the ‘trial’ extension, but once I do that I still get the same error about “no permission for ‘readDBInforamtion’ in the account pxxxxxxtrial”
Any idea about this error ?
Thanks,
Guy
What other settings did you provide? Host is hanatrial.ondemand.com
Yes Rui, the host is indeed the trial one.
The password was also accepted.
Any further idea is welcome.
Kr,
Guy
Hi Rui,
I managed to fix it now (indeed combination of the missing ‘trial’ as well in the host and in the account).
Thanks for your support,
Guy
Hello Rui,
The sessions on openSAP for HANA is very interesting and gripping. I have followed all the steps mentioned by you till now and everything works fine except when I tried to import “persistence-with-ejb” to the workspace. When I click at the JPA content -> Open Diagram, I get the following error: “diagramTypeProvider must not be null”
I have even tried to install JPA package “Helios” separately but that also didnt help. I get the following error:
tried searching on the net for some assistance but havent found a suitable answer. Could you please guide me? I am using MacOSX Yosemite.
Thanks,
Lakshmi
Hi – is it too late to post questions on this site? I’m trying to setup the DB connection, but only the “helloworld” connection shows up. By the way, it might also help to point out that for the time being users should install the Luna tools into eclipse even if they are using the mars version.
Hello,
I know, that this openSap course is little bit out of date, and I have searched forums and discussions, but I can’t find answer to my problem. Currently I’m on W2U1, publishing EJP app to cloud. My app is published, but it wont start. I think, that problem is with data sources, they are not created.
I have read, that there is problem with default database, but in my trial account I can’t change it. My trial account is old, because I have done several other openSAP courses.
I have read in some discussion, that I need to add property “<property name=”eclipselink.target-database” value=”com.sap.persistence.platform.database.HDBPlatform” />” to persistence.xml. Tried that, with deleting app, and publishing again, still data sources are not created.
Any Help ?
Thank You.