cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Problems connecting VC6.0 to BW 3.5

Go to solution
Former Member

on ‎03-14-2006 1:23 PM

0 Kudos

Dear Sirs,

We are trying to fetch content from a SAP BW 3.5 SP 14 using Visual Composer 6 (through EP 6.0 Sp14). We are able to read BABI from an ECC system already, using the SAP Connector, so now I want to read information from the BW system.

I have created a regular BW system object (using template SAP_R3_LoadBalancing), and the WAS and Connector tests are executed successfully in the System Connector test. System alias for the system is created, and User mapping is set up correctly.

When I in VC try to read information from the system object. I get the following error:

Error –32006: Search for BW query returned an error. Service not found com.sap.portal.guimachine.BIKit.CommandHandler.

I have seen others have had the same error but I have not seen a good solution to it.

In the portal I can go to, System Administration -> Support -> Portal Runtime, and I can see that the com.sap.portal.guimachine.BIKit is deployed correctly. I can also create a new system using the com.sap.portal.system.BIUDI, so the BIKit should be deployed correctly.

In the Visual Composer Innstallation guide on page 8 (2.2), there a list over the supported BI Systems. Bottom row in the table is:

BW 3.5 Sp3 or higher – Dedicated Application Server for R/3 system – SAP Java Connector, however I am using the SAP_R3_LoadBalancing. Is it not possible to use the SAP connector through a load balancing system.

Any ideas on where I should start solving this issue?

The error message below is the error in defaultTrace, for me it looks like the BIKit sca files are not deployed correctly. Anyone agree?. I will check it out and give feedback on this issue.

+#

#1.5#001185D3D12F00420000005E00001D3C00040F06B1C4576F#1142421333543#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#edbjor#7130####052ed880b41511da8ed9001185d3d12f#SAPEngine_Application_Thread[impl:3]_37##0#0#Error#1#/System/Server#Plain###User edbjor, IP address

HTTP request processing failed. HTTP error will be returned. The error is .#

#1.5#001185D3D12F00500000001C00001D3C00040F06CDDBA3FC#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###com.sapportals.portal.prt.service.ServiceException: Service not found: com.sap.portal.guimachine.BIKit.CommandHandler#

#1.5#001185D3D12F00500000001D00001D3C00040F06CDDBA80E#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:193)#

#1.5#001185D3D12F00500000001E00001D3C00040F06CDDBA89A#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.runtime.Portal$RuntimeResources.getService(Portal.java:146)#

#1.5#001185D3D12F00500000001F00001D3C00040F06CDDBA90A#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.guimachine.portalconnector.dispatcher.Dispatcher.handleCommandHandler(Dispatcher.java:182)#

#1.5#001185D3D12F00500000002000001D3C00040F06CDDBA97A#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.guimachine.portalconnector.dispatcher.Dispatcher.doContent(Dispatcher.java:122)#

#1.5#001185D3D12F00500000002100001D3C00040F06CDDBA9F8#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)#

#1.5#001185D3D12F00500000002200001D3C00040F06CDDBAA69#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)#

#1.5#001185D3D12F00500000002300001D3C00040F06CDDBAAD9#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#

#1.5#001185D3D12F00500000002400001D3C00040F06CDDBAB48#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#

#1.5#001185D3D12F00500000002500001D3C00040F06CDDBABB7#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#

#1.5#001185D3D12F00500000002600001D3C00040F06CDDBAC25#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.component.PortalComponentResponse.include(PortalComponentResponse.java:215)#

#1.5#001185D3D12F00500000002700001D3C00040F06CDDBAC94#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.pom.PortalNode.service(PortalNode.java:646)#

#1.5#001185D3D12F00500000002800001D3C00040F06CDDBAD01#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)#

#1.5#001185D3D12F00500000002900001D3C00040F06CDDBAD71#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:136)#

#1.5#001185D3D12F00500000002A00001D3C00040F06CDDBADE1#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.dispatchRequest(PortalRequestManager.java:189)#

#1.5#001185D3D12F00500000002B00001D3C00040F06CDDBAE50#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.PortalRequestManager.runRequestCycle(PortalRequestManager.java:753)#

#1.5#001185D3D12F00500000002C00001D3C00040F06CDDBAEBF#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.connection.ServletConnection.handleRequest(ServletConnection.java:240)#

#1.5#001185D3D12F00500000002D00001D3C00040F06CDDBAF2D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher$doService.run(Dispatcher.java:522)#

#1.5#001185D3D12F00500000002E00001D3C00040F06CDDBAFA1#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#

#1.5#001185D3D12F00500000002F00001D3C00040F06CDDBB00D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.dispatcher.Dispatcher.service(Dispatcher.java:405)#

#1.5#001185D3D12F00500000003000001D3C00040F06CDDBB07A#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#

#1.5#001185D3D12F00500000003100001D3C00040F06CDDBB0E5#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156)#

#1.5#001185D3D12F00500000003200001D3C00040F06CDDBB154#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)#

#1.5#001185D3D12F00500000003300001D3C00040F06CDDBB1BF#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:390)#

#1.5#001185D3D12F00500000003400001D3C00040F06CDDBB22E#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:264)#

#1.5#001185D3D12F00500000003500001D3C00040F06CDDBB29D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:347)#

#1.5#001185D3D12F00500000003600001D3C00040F06CDDBB30D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:325)#

#1.5#001185D3D12F00500000003700001D3C00040F06CDDBB37B#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:887)#

#1.5#001185D3D12F00500000003800001D3C00040F06CDDBB3EA#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:241)#

#1.5#001185D3D12F00500000003900001D3C00040F06CDDBB459#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Client.handle(Client.java:92)#

#1.5#001185D3D12F00500000003A00001D3C00040F06CDDBB4C5#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:148)#

#1.5#001185D3D12F00500000003B00001D3C00040F06CDDBB53B#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)#

#1.5#001185D3D12F00500000003C00001D3C00040F06CDDBB5B0#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)#

#1.5#001185D3D12F00500000003D00001D3C00040F06CDDBB61D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)#

#1.5#001185D3D12F00500000003E00001D3C00040F06CDDBB688#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at java.security.AccessController.doPrivileged(Native Method)#

#1.5#001185D3D12F00500000003F00001D3C00040F06CDDBB6F2#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:95)#

#1.5#001185D3D12F00500000004000001D3C00040F06CDDBB75F#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160)#

#1.5#001185D3D12F00500000004100001D3C00040F06CDDBBB04#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.broker.PortalServiceInstantiationException: Could not instantiate implementation class com.sap.portal.guimachine.bikit.designtime.CommandHandlerImpl of Portal Service com.sap.portal.guimachine.BIKit|CommandHandler because: could not load the service#

#1.5#001185D3D12F00500000004200001D3C00040F06CDDBBBAD#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:740)#

#1.5#001185D3D12F00500000004300001D3C00040F06CDDBBC1E#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalServiceItem.getServiceInstance(PortalServiceItem.java:540)#

#1.5#001185D3D12F00500000004400001D3C00040F06CDDBBC8E#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.service.ServiceManager.get(ServiceManager.java:185)#

#1.5#001185D3D12F00500000004500001D3C00040F06CDDBBCFA#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### ... 35 more#

#1.5#001185D3D12F00500000004600001D3C00040F06CDDBC09B#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: : com.sap.portal.guimachine.BIKit#

#1.5#001185D3D12F00500000004700001D3C00040F06CDDBC12D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:425)#

#1.5#001185D3D12F00500000004800001D3C00040F06CDDBC1AC#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalApplicationItem._refresh(PortalApplicationItem.java:505)#

#1.5#001185D3D12F00500000004900001D3C00040F06CDDBC21E#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalApplicationItem.getCoreLoader(PortalApplicationItem.java:1334)#

#1.5#001185D3D12F00500000004A00001D3C00040F06CDDBC28F#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalServiceItem.getClassLoader(PortalServiceItem.java:903)#

#1.5#001185D3D12F00500000004B00001D3C00040F06CDDBC2FF#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalServiceItem.__createServiceInstance(PortalServiceItem.java:727)#

#1.5#001185D3D12F00500000004C00001D3C00040F06CDDBC36D#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### ... 37 more#

#1.5#001185D3D12F00500000004D00001D3C00040F06CDDBC721#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.runtime.PortalRuntimeException: Exception during start of application: SAPJ2EE::library:bimmrjmi#

#1.5#001185D3D12F00500000004E00001D3C00040F06CDDBC7B4#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:323)#

#1.5#001185D3D12F00500000004F00001D3C00040F06CDDBC825#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.PortalApplicationItem.prepare(PortalApplicationItem.java:385)#

#1.5#001185D3D12F00500000005000001D3C00040F06CDDBC893#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### ... 41 more#

#1.5#001185D3D12F00500000005100001D3C00040F06CDDBCC33#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain###Caused by: com.sapportals.portal.prt.core.broker.ExternalApplicationNotFoundException: Could not find portal application SAPJ2EE::library:bimmrjmi#

#1.5#001185D3D12F00500000005200001D3C00040F06CDDBCCC6#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### at com.sapportals.portal.prt.core.broker.SAPJ2EEApplicationItem.prepare(SAPJ2EEApplicationItem.java:277)#

#1.5#001185D3D12F00500000005300001D3C00040F06CDDBCD34#1142421804872#System.err#sap.com/irj#System.err#edbjor#7181####1e1b8090b41611da8290001185d3d12f#SAPEngine_Application_Thread[impl:3]_12##0#0#Error##Plain### ... 42 more#+

Message was edited by: Jørgen Ruud

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎03-23-2006 4:35 AM
0 Kudos

Hi Jørgen,

To solve Error-32006 follow the following steps:-

In BW Server -

Go to transaction WSCONFIG, to configure Query_view_data Service

Web service definition:- ‘query_view_data’ and then click on create Icon.

Provide the URL (in our case it is: /sap/bw/xml/

soap/queryview).This will also Create External aliases.

Thanks in advance,

Deep.

Show replies
Show replies

Answers (1)

Answers (1)

Former Member
‎03-20-2006 6:44 AM
0 Kudos

Hi Jørgen,

guimachine.BIKit may not be deployed in your SDM.

Moreover open your storyboard, open the option dialog box. Inthe option box, go to portal tab. Check out the BW url in the options and set the same url in the BW Server.

Thanks in advance,

Deep

Show replies
Show replies
Former Member
‎03-20-2006 7:21 AM
0 Kudos

Hello Deep,

thanks for the answer. When you say, set the "same URL in the BW server", could you please ellaborate on where to do this?

Best regards,

Jørgen.

Former Member
‎03-20-2006 3:06 PM
0 Kudos

The checks for this are detailed in this "How-to" guide that Scott Cairncross and I put together. Check it out...

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/92d80512-0a01-0010-32a3-cd3...

Former Member
‎03-21-2006 7:40 AM
0 Kudos

Hello Prakash,

this paper was highly valuable and I hope you will make sure that this paper when it is completed, is always displayed on the top in this forum.

But I have one question regarding section 5 Configuring SAP BW Native Connector. In this section you say that the system has to be a SAP system using dedicated application server. Is this a requirement?, or would it be possible to use it with a loadbalancing system as well?

Best regards,

Jørgen

Former Member
‎03-22-2006 4:09 PM
0 Kudos

Load balancing works as well. I'll add that example to the paper.

Former Member
‎04-05-2006 7:25 AM
0 Kudos

Hello Prakash,

in the paper Visual Composer - Howto resolve problems in section 2.1, is it a BI problem. I think it would be a good idea to specify which system this test should be performed on (BW or portal server?)

It is a very good paper, so keep up the good work.

Best regards,

Jørgen

Ask a Question