Skip to Content

Lumira Discovery error, Unable to connect to BI Platform. Check your connection settings (HDB 05408)

Many many questions out there re: this specific error, but they are all related to older Lumira and SAP BI Platform versions, so here's a new question for you experts.

BI Platform: 4.2 SP05 Patch 200

Lumira Discovery: 2.1 SP1

Landscape:

Public Users(a) --> Firewall(b) -- Load Balancer(c) --> Web Node(d) (in DMZ) --> Firewall(e) --> Proc Node(f) / Lum Node(g) / CMS Node(h)

a. Users are outside our network, so this is a public facing application, requiring SSL with port 80 redirect to 443

b. Firewall is open to 80, 443, & 4443 only (4443 was open to run WACS, but as of SP05 this should no longer be required and I hope to close this port)

c. Splits traffic up to clustered environment

d. On this node, the following components are installed (but none are running in CMC):

BI Platform

  • web apps (all of them)
  • Web Application Container Server
  • Platform Processing Servers
  • Platform Scheduling Services
  • RESTful Web Services
  • Insights to Action Service
  • Connectivity Services
  • Data Federator Service
  • Analysis Services
  • SAP Crystal Reports Services
  • Web Intelligence Services
  • Dashboard Processing Services
  • ALL Database Access

Lumira Server

  • All components

(I would only have liked to install the web apps component, but per other blogs it's suggested to install all components, just in case. And given the difficulty in getting Lumira up and running, I figured this would be the best chance).

e. Between the Web Node (in DMZ) and the LAN (f thru h), I have bi-directional access to thru 6400 & 6436, plus the JMX ports for BIPST.

f. & g. Same components installed as (d) EXCEPT for the WebTier / tomcat components. Additionally, all of the Administrative Tools and Developer components.

h. Installed on these nodes is the CMS, Event, and FRS and that is it.

In CMC, I have Lumira services running as well as RESTful Web Services, all servers are assigned their unique communication request port. All servers are green.

In CMC, Application RESTful Web Service, the access URL is set to:

https://bidev.teamsoftware.com/biprws/

There is NO port here anymore, because with SP05 this goes away and now the traffic goes through Tomcat, not WACS. Hence why I will be wanting to close off port 4443 in landscape (b). This is a public facing app, so you the reader can browse to that site directly and see that it works.

Regarding Lumira Discovery

I have set my Network preferences in Lumira Discovery. I have used the new port-less RESTful Web Services URL, basically removed the port 4443 that was for WACS from the URL.

Then, I try to connect to the BI Platform.

I enter the CMS Name (although it says Server), and I hit enter. At this point, the error is produced.

Suggestions?

error.png (469.9 kB)
Add comment
10|10000 characters needed characters exceeded

  • And... the most important thing, the trace log. Here it is. It would seem that it is still trying to go through port 80, and not redirect to 443?

    |2381D2BE797F40E78745AFAFA72EB3381059|2018 04 20 23:28:27.861|-0500|Debug| |<<| | |TraceLog|11592|  60|qtp836570670-60 | ||||||||||||||||||||com.sap.hilo.platform.boe.internal.BOERestPlatform||Looking for an existing session...
    |2381D2BE797F40E78745AFAFA72EB338105a|2018 04 20 23:28:27.862|-0500|Debug| |<<| | |TraceLog|11592|  60|qtp836570670-60 | ||||||||||||||||||||com.sap.hilo.platform.boe.internal.BOERestPlatform||Opening new session
    |2381D2BE797F40E78745AFAFA72EB338105b|2018 04 20 23:28:29.185|-0500|Information| |>>| | |TraceLog|11592|  60|qtp836570670-60 | ||||||||||||||||||||com.sap.hilo.desktop.core.embeddedserver.httpservice.HTTPAdapter||Call to service 'openBOERestSession' failed
    Unable to connect to the BI Platform. Check your connection settings. (HDB 05408)
    at com.sap.hilo.platform.boe.internal.BOERestAuthenticationService.logon(BOERestAuthenticationService.java:105)
    at com.sap.hilo.platform.boe.internal.BOERestUserSessionInfo.logon(BOERestUserSessionInfo.java:146)
    at com.sap.hilo.platform.boe.internal.BOEUserSessionManager.openSession(BOEUserSessionManager.java:40)
    at com.sap.hilo.platform.boe.internal.BOEUserSessionManager.openSession(BOEUserSessionManager.java:1)
    at com.sap.hilo.service.infrastructure.base.Platform.openSession(Platform.java:65)
    at com.sap.hilo.desktop.share.v2.boe.service.OpenBOERestSession.execute(OpenBOERestSession.java:197)
    at com.sap.hilo.desktop.h5v2.common.service.BaseService.execute(BaseService.java:33)
    at com.sap.hilo.desktop.core.embeddedserver.httpservice.HTTPAdapter.execute(HTTPAdapter.java:89)
    at com.sap.hilo.desktop.core.embeddedserver.DispatcherServlet.handleRequest(DispatcherServlet.java:109)
    at com.sap.hilo.desktop.core.embeddedserver.DispatcherServlet.doPost(DispatcherServlet.java:89)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
    at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:841)
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1650)
    at com.sap.hilo.desktop.core.embeddedserver.JsonPaddingFilter.doFilter(JsonPaddingFilter.java:125)
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
    at com.sap.hilo.desktop.core.embeddedserver.configurator.internal.SecurityFilter.doFilter(SecurityFilter.java:113)
    at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1637)
    at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:533)
    at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188)
    at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1595)
    at org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:188)
    at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1253)
    at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:168)
    at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:473)
    at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:1564)
    at org.eclipse.jetty.server.handler.ScopedHandler.nextScope(ScopedHandler.java:166)
    at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1155)
    at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:141)
    at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132)
    at org.eclipse.jetty.server.Server.handle(Server.java:564)
    at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:317)
    at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:251)
    at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:279)
    at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:110)
    at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:124)
    at org.eclipse.jetty.util.thread.Invocable.invokePreferred(Invocable.java:128)
    at org.eclipse.jetty.util.thread.Invocable$InvocableExecutor.invoke(Invocable.java:222)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.doProduce(EatWhatYouKill.java:294)
    at org.eclipse.jetty.util.thread.strategy.EatWhatYouKill.run(EatWhatYouKill.java:199)
    at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:672)
    at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:590)
    at java.lang.Thread.run(Thread.java:805)
    Caused by: java.net.ConnectException: Connection refused: connect (local port 52260 to address 0:0:0:0:0:0:0:0, remote port 80 to address 192.168.0.129 (TST-BICMS))
    at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
    at java.net.DualStackPlainSocketImpl.socketConnect(DualStackPlainSocketImpl.java:86)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
    at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:173)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:363)
    at java.net.Socket.connect(Socket.java:899)
    at org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
    at org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
    at org.apache.http.impl.conn.AbstractPoolEntry.open(AbstractPoolEntry.java:144)
    at org.apache.http.impl.conn.AbstractPooledConnAdapter.open(AbstractPooledConnAdapter.java:131)
    at org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
    at org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
    at org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
    at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
    at com.sap.hilo.http.internal.HttpRequest.handleRequest(HttpRequest.java:157)
    at com.sap.hilo.http.internal.HttpRequest.sendRequest(HttpRequest.java:309)
    at com.sap.hilo.platform.boe.internal.BOERestAuthenticationService.logon(BOERestAuthenticationService.java:102)
    ... 42 more
  • Get RSS Feed

1 Answer

  • Best Answer
    Apr 21 at 07:39 AM

    as you selected "Enable RESTfull logon" under network,

    so simply enter the user name and password when logging in and keep the server as is.

    here a screenshot from your system while try to logon:

    Add comment
    10|10000 characters needed characters exceeded