Skip to Content

SAP HANA XSA WebIDE 2.0 SP 2: Building of Launchpad with own app fails

Hi,

we try to include our app within a launchpad.

I was following this docu:

https://help.sap.com/viewer/4505d0bdaf4948449b7f7379d24d0f0d/2.0.01/en-US/8a583342d1c64822837fe49efbafdb53.html

To get sure, that everything in the dev environment works fine, I was building and deploying only the fiori launchpad with the two included sample apps at first successfully.

After that I tried to include our app, but it fails, when I tried to build the whole application. Yes, I was building all modules at first separately without any error. I'm able to start this app by index or by component.js. Every works fine.

The problem is that there is no hint within the logfiles of the web modul. Do you have any ideas where we can look further more for the reasons of this abort?

Check console logs for details: Couldn't find any errors in the console log!

Thanks!

> npm WARN site-entry@ No description
> npm WARN site-entry@ No repository field.
> npm WARN site-entry@ No license field.
> npm info ok 

22:09:31 (DIBuild) [INFO] Logs of build task for module web:
> [INFO] Injecting source code into builder...
> [INFO] Source code injection finished
> [INFO] ------------------------------------------------------------------------

22:09:37 (DIBuild) [INFO] Saving MTA archive NAME_0.0.1.mtar
[ERROR] Could not save the build results.
22:09:37 (DIBuild) Build of /NAME failed.
22:09:37 (Builder) Check console logs for details
22:09:37 (Builder) Build of /NAME failed.
Add comment
10|10000 characters needed characters exceeded

  • Ok, found this in the logs of the di-builder.

    Any idea what this means?

    T:\>xs logs di-builder --recent
    
    
    Connected, dumping recent logs for app "di-builder"
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.CommittingOutputStream.write(CommittingOutputStream.java:229) ~[jersey-
    common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.WriterInterceptorExecutor$UnCloseableOutputStream.write(WriterIntercept
    orExecutor.java:299) ~[jersey-common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.ReaderWriter.writeTo(ReaderWriter.java:116) ~[jersey-common-2.23.2.jar:
    na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.AbstractMessageReaderWriterProvider.writeTo(AbstractMessageReaderWriter
    Provider.java:79) ~[jersey-common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.InputStreamProvider.writeTo(InputStreamProvider.java:105) ~[jersey-comm
    on-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.InputStreamProvider.writeTo(InputStreamProvider.java:60) ~[jersey-commo
    n-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.WriterInterceptorExecutor$TerminalWriterInterceptor.invokeWriteTo(Write
    rInterceptorExecutor.java:265) ~[jersey-common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.WriterInterceptorExecutor$TerminalWriterInterceptor.aroundWriteTo(Write
    rInterceptorExecutor.java:250) ~[jersey-common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.WriterInterceptorExecutor.proceed(WriterInterceptorExecutor.java:162) ~
    [jersey-common-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.message.
    internal.MessageBodyFactory.writeTo(MessageBodyFactory.java:1130) ~[jersey-commo
    n-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.client.C
    lientRequest.doWriteEntity(ClientRequest.java:517) ~[jersey-client-2.23.2.jar:na
    ]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.client.C
    lientRequest.writeEntity(ClientRequest.java:499) ~[jersey-client-2.23.2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.client.i
    nternal.HttpUrlConnector._apply(HttpUrlConnector.java:388) ~[jersey-client-2.23.
    2.jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            at org.glassfish.jersey.client.i
    nternal.HttpUrlConnector.apply(HttpUrlConnector.java:285) ~[jersey-client-2.23.2
    .jar:na]
    06.07.17 10:49:28.867 [APP/10-0] ERR            ... 18 common frames omitted
    <br>
    
    

    Found this:

    HttpUrlConnector.apply(HttpUrlConnector.java:285-->

    So basically, it means that there is a problem in SSL handshaking between the server and client.

    https://stackoverflow.com/questions/34280861/javax-ws-rs-processingexception-while-sending-request-through-jersey/34941703

  • Former Member Did you solve this?

  • No, but let me know if you could fix it.

  • Get RSS Feed

1 Answer

  • Jul 06, 2017 at 11:41 AM

    We use a SSL server certificate for our XSA runtime for HTTPS request.

    Do we need to assign this same certificate to the "Admin Tool" (SAML Identity Provider List). Could this help?

    Add comment
    10|10000 characters needed characters exceeded