Hi,

when I try to deploy my application (worked before just added a few log statements) I get:

Bundle org.eclipse.equinox.ds_1.4.0.v20120112-1400, [SCR] Exception while activating instance com.sap.core.persistence.osgi.config.PersistenceServiceConfiguration@18b9060 of component com.sap.core.persistence.jpa  java.lang.reflect.InvocationTargetException: null

...

Caused by: com.sap.core.tenant.common.TenantAdministrationException: Not authorized to communicate with the system databaseCode: 403

...

The complete stack trace is attached, the exception is coming several times from org.osgi.service.log.LogService.

Can someone explain what to do here?? Or is it just some of that frequent problems of HCP that will go away just by waiting?

Frank

I've posted a couple of questions on an issue I'm having using a destination in HCP but haven't gotten a response.  For example,

403 Error with destination to NWG service

I may be grasping at straws here but I heard from someone that SP09 (Rev. 90) has had issues with the Web Dispatcher.  If this is the case then it might be the problem I'm having.  Does anyone know if this is true and can anyone tell me how what version I have.

Also, are there any official support channels that are available for HCP trial accounts?  I can't figure out how to file an incident without an SID on the support portal.

Thanks,

Ross

Hello Everyone, I just set up a local IDP by following the documentation here:

https://help.hana.ondemand.com/help/frameset.htm?754818ea63874ea38843ab0ed1928765.html

I am using a local production HANA instance as the Service Provider (SP) where I have a simple Hello World app for that I enabled SAML authentication.
I have configured the trust between the SP and IDP as well as between the IDP and SP.

When accessing the app, I am successfully redirected to the IDP and enter my credentials. While creating the SSO response the IDP encounters the following exception:

com.sap.security.saml2.cfg.exceptions.SAML2ConfigurationException: SSO response message could not be created, because there are not any ACS endpoints configured for SP: mymachine:8007/ with binding: urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST

at com.sap.security.saml2.idp.api.IdPUtils.getACSEndpoint(IdPUtils.java:76)

at com.sap.security.saml2.idp.api.IdPUtils.getACSLocation(IdPUtils.java:96)

at com.sap.security.saml2.idp.api.SSOService.getResponseLocation(SSOService.java:767)

at com.sap.security.saml2.idp.api.SSOService.generateAuthenticationResponse(SSOService.java:199)

at com.sap.security.saml2.idp.api.SSOService.createAuthnResponse(SSOService.java:77)

at com.sap.security.saml2.idp.api.SAML2IdPAPI.createSSOResponse(SAML2IdPAPI.java:116)

at com.sap.core.jpaas.security.saml2.localidp.SSOService.processSSORequest(SSOService.java:166)

at com.sap.core.jpaas.security.saml2.localidp.SSOService.doGet(SSOService.java:65)

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 org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)

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:503)

at com.sap.core.jpaas.security.auth.service.lib.AbstractAuthenticator.invoke(AbstractAuthenticator.java:161)

at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:170)

at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)

at com.sap.core.tenant.valve.TenantValidationValve.invokeNextValve(TenantValidationValve.java:255)

at com.sap.core.tenant.valve.TenantValidationValve.invoke(TenantValidationValve.java:101)

at com.sap.js.statistics.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:24)

at com.sap.core.js.monitoring.tomcat.valve.RequestTracingValve.invoke(RequestTracingValve.java:25)

at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)

at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:421)

at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1070)

at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:611)

at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)

at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)

at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)

at java.lang.Thread.run(Thread.java:745)

The IDP however contains the correct XML metadata from my SP (as described in the tutorial), which describes the ACS endpoint that it is strangely not able to find.

The XML metadata in the IDP for my SP looks like this (certificate info removed):

<ns2:EntityDescriptor

    xmlns:ns2="urn:oasis:names:tc:SAML:2.0:metadata"

    xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion"

    xmlns:ds="http://www.w3.org/2000/09/xmldsig#" entityID="mymachine:8007/">

    <ns2:SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

        <ns2:KeyDescriptor use="signing">

            <ds:KeyInfo>

                <ds:X509Data>

                    <ds:X509Certificate> ... </ds:X509Certificate>

                </ds:X509Data>

            </ds:KeyInfo>

        </ns2:KeyDescriptor>

        <ns2:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="mymachine:8007/sap/hana/xs/saml/logout.xscfunc"/>

        <ns2:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</ns2:NameIDFormat>

        <ns2:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</ns2:NameIDFormat>

        <ns2:AssertionConsumerService isDefault="true" index="0" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="mymachine:8007/sap/hana/xs/saml/login.xscfunc"/>

    </ns2:SPSSODescriptor>

    <ns2:IDPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">

        <ns2:KeyDescriptor use="signing">

            <ds:KeyInfo>

                <ds:X509Data>

                    <ds:X509Certificate> ... </ds:X509Certificate>

                </ds:X509Data>

            </ds:KeyInfo>

        </ns2:KeyDescriptor>

        <ns2:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="mymachine:8007/sap/hana/xs/saml/logout.xscfunc"/>

        <ns2:SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="mymachine:8007/sap/hana/xs/saml/logout.xscfunc"/>

        <ns2:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</ns2:NameIDFormat>

        <ns2:NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress</ns2:NameIDFormat>

        <ns2:SingleSignOnService isDefault="true" index="0" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="mymachine:8007/sap/hana/xs/saml/login.xscfunc"/>

        <ns2:SingleSignOnService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect" Location="mymachine:8007/sap/hana/xs/saml/login.xscfunc"/>

    </ns2:IDPSSODescriptor>

    <ns2:Organization>

        <ns2:OrganizationName xml:lang="en">SAP Labs, LLC</ns2:OrganizationName>

        <ns2:OrganizationDisplayName xml:lang="en">SAP Labs, LLC</ns2:OrganizationDisplayName>

        <ns2:OrganizationURL xml:lang="en">http://www.sap.com</ns2:OrganizationURL>

    </ns2:Organization>

</ns2:EntityDescriptor>

So everything is in there, I don't know what I'm missing. Any ideas?

Let me know if you need more information!

Best,

Daniel

I am getting internal server error accessing my schema's or trying to create new one, I am getting Internal Server Error (500)

Please advice.

Thanks,

Jemin

Hi All,

       While I am connecting  SAP HANA cloud platform through SAP LUMIRA its throughing  an error "Check the server name and instance ID."

where I will get the server name and instance id.

Thanks & Regards,

Hemanth Reddy M.

Hi,

In normal web development, we can secure all projects( html5 etc...) by generating war file or virtual directory and deployed into the web server so that we can secure our application files, in the same we have any thing in XS Engine to secure projects.

Here my basic problem is after deploying html5 projects into the xs engine, I can see all my project files by using browser developer options.

Regards,

Harish

Hi Experts,

I am trying to run SAP HANA Cloud Connector on Windows 8.1 machine , i could see the go.bat command response as below:

But when i run https://localhost:8443 URL in a browser, i don't see any response. Just a blank screen.

By looking at the logs:

#ERROR#com.sap.scc.jni#Start Level Event Dispatcher#  #Cannot load the Cloud Connector native library. (exception java.lang.UnsatisfiedLinkError: no sapscc20jni in java.library.path)

As per this reference https://help.hana.ondemand.com/help/frameset.htm?204aaad4270245f3baa0c57c8ab1dd60.htmlInstallation on Microsoft Windows OS it doesn't talk anything about support of HCC on Windows 8.1, just wondering if above error is because of it.

For more details, PFA log files.

Regards,

JK

p13439331trial

I can access and develop just fine via the workbench, but I can no longer 'Log On' to the 'Repository' view of this within Eclipse.  I had been able to log on in Eclipse for several days but this stopped working a few days ago.

I don't know if this is the correct route for this problem, so please advise as to how I can access my instance in Eclipse.

Thanks

I posted a question a few days ago and got no response but I've continued to research it and have learned a little more but it raises a fundamental question.

I'm attempting to create a destination in HCP but have run into some issues and I'm having trouble understanding how this works.  I'm hoping someone can clear it up for me.  I've created services on our HANA system and in NWG.  I can access both successfully using a REST client through the internet.  When I create a destination in the HCP Cockpit or connection in SMP cloud I configure it using Internet as opposed to OnPremise because I'm able to access via the Internet.  However, when I test it, I get a 403 or Target Service Not Allowed error.  According to the SMP documentation, this means that the service should be configured as OnPremise.  This is confusing.  What is the criteria for requiring an OnPremise connection?  My understanding was that it was required when a service could not be accessed directly via the Internet.

If anyone can clear it up for me, I would greatly appreciate it.

Ross

I created a trial user and now want to add a cloud system It comes up the following screen:

But I have no idea what password to use, my normal password does not work.

Can anyone help me

Wim

Hello, I would like to ask about SAP HANA developing. What tools I need for developing SAP HANA database application with gui? it should be like web application. I already use HANA cloud platform. What more do I need ?

Hello,

I need to know what is the process to setup Zero down Time for your application.

How can i request for more VMs?

Thanks,

Sachin Kaura

Hello Experts

I'm still following the Open SAP tutorial for development in Hana, i was trying to create a CDS artifact but i'm getting the following error:

Failed to generate CDS artifact "p12345trial.myhanaxs.ivyrepxs::partner" to schema "XYZ" as index server config switch "view_activation_for_hcp" is set. In this mode only generation to schema "_SYS_BIC" is allowed.

I thought that the DEV Schema was supposed to be there for using it during tests, is there anything else that is missing for been able to work with it?

This is the code that i'm using:

namespace p1101189trial.xstrial1.XSProject3.data;

  @Schema: 'DEV_1VKKPRJI2LZT43BFTKBIJ510A'

context user {

  type SString : String(40);

  type LString : String(255);

  @Catalog.tableType: #COLUMN

    Entity Details{

      key PERS_NO: String(10);

      FIRSTNAME: SString;

      LASTNAME: SString;

      E_MAIL: LString;

    };

};

Thanks

Francisco

Hello,

I have a problem with widget updating on the Cloud Portal.

Here what is going on:

1. I create a widget, upload it to Cloud Portal. Then I can drag the widget to a site, it works OK.

2. I make some changes in JavaScript code of the widget in Eclipse.

3. I delete currently uploaded widget from the content.

4. The updated widget is uploaded to Cloud Portal.

5. Using the Network tab of the developer tools, I can see that the code of my JS file did not change (and, of course, the widget doesn't work as it should after the changes to the code were made).

In my case, at the beginning, I had a table in widget that was defined as follows:

oTable = new sap.m.Table( {                   id: "descriptionTable",               mode: sap.m.ListMode.SingleSelect,               backgroundDesign: sap.m.BackgroundDesign.Translucent,               columns: [                         oPopulation,                          oCapital,                ],
});

  Then, I have updated the table as follows:

oTable = new sap.m.Table( {                    id: "descriptionTable",                mode: sap.m.ListMode.SingleSelectMaster,                selectionChange: prepublish,                backgroundDesign: sap.m.BackgroundDesign.Translucent,                columns: [oPopulation, oCapital ],
});

But the table still looks as it is shown in the first code snippet.

The question is how do I update widgets on the Cloud Portal after I update their code in Eclipse?

Regards,

Yuri.

Hi guys,

I want to expose a HANA Cloud App that I created to let's say 20 different customers.

Does this mean that I need to buy 20 SHC lisenses and run these customers on 20 different SAP Cloud accounts with 20 different SAP HANA cloud connectors?

Thanks

/Tom

Hi All,

Does anyone know if the cloud connector requires a different installation procedure (or different installation files) to be installed on a clustered server? I can't see any mention in the help files or installation notes so presume it should be possible using the standard installation files found here: SAP Development Tools for Eclipse

Has anyone successfully installed the connector on a clustered server?

Thanks,

Malcolm

Update on our Cloud Foundry Activities

Earlier this year Pivotal – a joint venture by EMC, VMware and GE – announced to establish a formal open governance model for Cloud Foundry, an open platform-as-a-service framework. Together with five other veterans of the IT industry (EMC, HP, IBM, Intel and VMware) SAP announced to become platinum sponsor of the Cloud Foundry Foundation.

• Pivotal press release
• SAP press release

Much has happened since then. And much has been written and spoken about our decision to contribute to Cloud Foundry and to leverage it in our own PaaS, the SAP HANA Cloud Platform:

• Matthias Steiner’s recent blog about SAP HANA Cloud Platform
• Two interesting analyses (SCN, Diginomica) done by Richard Hirsch
• Presentations from Dirk Basenach (SAP, recording) and René Welches (hybris, recording) during the Cloud Foundry Summit
• Interview with Pieter Humphrey (Pivotal), Andreas Wesselmann (SAP) and Steve Winkler (SAP) during SAP TechEd && d-code 2014

With this blog post we want to revisit the latest events, talk more in detail about our approach and principles to adopt Cloud Foundry and give an outlook of what you can expect during the next months.

Cloud Foundry Foundation

And now the great news: Today Pivotal announced that the Cloud Foundry Foundation has been successfully established.

“The Cloud Foundry Foundation's mission is to establish and sustain Cloud Foundry as the global industry standard open source PaaS technology with a thriving ecosystem; to deliver continuous quality, value and innovation to users, operators and providers of Cloud Foundry technology; and, to provide a vibrant agile experience for the community's contributors that delivers the highest quality cloud-native applications and software, at high velocity with global scale.”

As you can read in today's Cloud Foundry Foundation announcement, we are excited to be part of the Cloud Foundry Foundation:

“As a Platinum member of the Cloud Foundry Foundation, SAP is actively engaged in helping to define one of the industry-leading, open-source PaaS technologies as well as part of the evolving ecosystem around it. It is important to be open, and we believe that Cloud Foundry is fast becoming ‘a platform of choice’ for many of SAP’s partners, customers and developers. SAP is committed to contributing to open-source PaaS technologies, including integration of technologies such as the SAP HANA® platform and Internet of Things as part of SAP HANA Cloud Platform.”
Björn Goerke, Executive Vice President and Corporate Officer, Product and Innovation Technology, SAP

The Cloud Foundry Foundation now has around 50 corporation members of different sizes and from different industries.

For us, the launching of the Cloud Foundry Foundation is an important milestone, because its bylaws and contribution rules formalize the governance of influence, intellectual property and opportunities for the contributors and give us a reliable path for the future of this open platform-as-a-service initiative.

We look forward to working closely with the the Cloud Foundry community.

Our approach to adopt Cloud Foundry

Matthias Steiner already nicely outlined our roadmap to adopt Cloud Foundry in our PaaS. Today we like to take a closer look at the principles we follow and the phases we run through during our journey.

For SAP it is important to follow three simple principles while adopting Cloud Foundry:

• Learn by example: work with stakeholders to understand concrete requirements and derive backlogs accordingly
• Use instead of write: avoid developing new platform components, but use externally available alternatives (open source) where applicable
• Prefer value adding new features over re-implementing existing ones: instead of immediately replacing features already available on SAP HANA Cloud Platform with the equivalent features based on Cloud Foundry, start with leveraging Cloud Foundry to offer “more” to stakeholders of our PaaS (i.e. more programming models, more application services, more openness)

Now let’s take a brief look at what has happened so far and what is going to happen next.

Phase 1 (done)

During the last months we have been on a steep learning curve. After making the commitment to join the Cloud Foundry Foundation, we have set up dedicated teams in Walldorf (Germany) and Sofia (Bulgaria) to familiarize themselves with the technology, to run our first own Cloud Foundry instance and to support first internal frontrunner applications. To facilitate the learning process two developers joined the Cloud Foundry Dojo in San Francisco during Summer 2014.

The teams were able to run a Cloud Foundry instance in our German data center. In this setup Cloud Foundry BOSH acts as the abstraction layer to deploy and run the platform on the underlying infrastructure. BOSH supports (via so-called Cloud Provider Interfaces, CPIs) different infrastructure providers (AWS, OpenStack, vSphere). Currently we use the AWS CPI as our own, internal IaaS layer called Monsoon which offers an AWS API.

Our major frontrunner application for Cloud Foundry has been hybris-as-a-service, an offering to build commerce solutions. We worked very closely with the teams responsible to implement this offering in order to learn and plan our backlog in accordance with their requirements.

SAP has also started to make contributions to Cloud Foundry e.g. with the SAP HANA Service Broker for Cloud Foundry and you’ll see initial results of these contributions soon, also inside products from SAP and SAP companies.

Specifically in the SAP HANA Cloud Platform, Cloud Foundry will enable supporting scenarios like bring-your-own-runtime or bring-your-own-service so that customers and partners can have even more choice to leverage their know-how and technologies on SAP’s Platform-as-a-Service offering.

Phase 2 (ongoing)

Now we are in phase two of our Cloud Foundry journey. For this phase we plan to increase our investment in Cloud Foundry, to look into enterprise-readiness of our Cloud Foundry instances and to support additional application developers within SAP interested in utilizing the Cloud Foundry technology.

The number of SAP developers busy with the groundwork to make Cloud Foundry part of our PaaS offering has gone up significantly. It will further increase in 2015. Some of these developers are planning to join the Cloud Foundry Dojo training program in the next quarter.

To allow productive usage of Cloud Foundry as part of SAP HANA Cloud Platform, we have started to look at what is needed for monitoring, logging, backup and restore etc. We need to ensure that existing services offered by our PaaS are also available from within Cloud Foundry. We need to decide, too, which services to port to Cloud Foundry.

In parallel we like to allow additional internal applications to be built on Cloud Foundry. This requires training of application developers. Therefore, we have set up an internal trial system which can be used to gain a basic understanding of what Cloud Foundry is. And my partner-in-crime Matthias Steiner has already managed to run his famous Granny application there which he originally had used on SAP HANA Cloud Platform.

Phase 3 (future)

As soon as we feel comfortable we also want to give external developers (i.e. from customers and partners) a chance to take a look at Cloud Foundry in the SAP HANA Cloud Platform.

Therefore: stay tuned and look out for updates here in the SAP Community Network.

Best,

Rui

Hi,

I'm facing an issue while activating the file in sap hana studio to server. I'm able to activate these files when I created. After updated these files and tried activate it again, it was not activating. Hana studio doesn't give any error message also. These files will retain grey  colored square shape.

How to resolve this issue??

Best Regards,

Desanth

Hi,

can I connect to my Hana DB on neo.ondemand.com via ODBC?

Preferably from a Linux SLES VM?

I tried using SAP corporate wired and SAP internet wireless connections.

Thanks in advance!

I have created a sample application with the HCP Trial account, using the WebIDE, Fiori Start template and the Northwind OData service from odata.org. It works great

I now want to create a similar application, except I want to use the HANA database with XSOData services.

I have create the database and the service and it is working (also with HCP Trial account).

The difficulty I am having is setting up the destination in the HCP cockpit with the correct authentication settings. I have tried a number of options, but when setting the URL in the in the Fiori Starter Template wizard, it says its an invalid URL.

Using a trial account, does anyone know how I can connect the XSOData services to HCP & the WebIDE?

Thanks in advance.

Gareth.