cancel
Showing results for 
Search instead for 
Did you mean: 

Error when create connection in Xcelcius 2008 SP3 to BW EHP 1 SPS 6

Former Member
0 Kudos

Dear All,

Last week there is no problem in this connection, buat since today this error happen.

We found error when trying to connect Xcelcius and and BW,below the error:

com.sap.ip.bi.bics.remote.impl.rmi.ApplicationCreationException: Could not to create the application. This is probably due to a misconfigured Abap/Java connection.

at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getApplication(AbstractConnectionContext.java:195)

at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.createBicsRemoteMessageProducer(AbstractConnectionContext.java:387)

at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getMessageProducer(AbstractConnectionContext.java:209)

at com.sap.ip.bi.bics.remote.BicsRemoteImpl.getDesignTimeInfo(BicsRemoteImpl.java:156)

at com.sap.ip.bi.bics.remote.BicsRemoteBean.getDesignTimeInfo(BicsRemoteBean.java:109)

at com.sap.ip.bi.bics.remote.BicsRemoteObjectImpl0_0.getDesignTimeInfo(BicsRemoteObjectImpl0_0.java:379)

at com.sap.ip.bi.bics.remote.BicsRemote_Stub.getDesignTimeInfo(BicsRemote_Stub.java:328)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

at java.lang.reflect.Method.invoke(Method.java:331)

at com.sap.engine.services.webservices.runtime.EJBImplementationContainer.invokeMethod(EJBImplementationContainer.java:126)

at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:157)

at com.sap.engine.services.webservices.runtime.RuntimeProcessor.process(RuntimeProcessor.java:79)

at com.sap.engine.services.webservices.runtime.servlet.ServletDispatcherImpl.doPost(ServletDispatcherImpl.java:92)

at SoapServlet.doPost(SoapServlet.java:51)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)

at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:386)

at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:364)

at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:1039)

at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:265)

at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)

at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:175)

at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)

at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)

at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)

at java.security.AccessController.doPrivileged(Native Method)

at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:104)

at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:176)

Caused by: com.sap.ip.bi.base.service.connection.ConnectionException: No connection possible to BI master system BD1CLNT500

at com.sap.ip.bi.base.portal.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:71)

at com.sap.ip.bi.base.application.impl.Application.createService(Application.java:568)

at com.sap.ip.bi.base.application.impl.Application.getMasterSystemService(Application.java:1027)

at com.sap.ip.bi.base.application.impl.Application.getProperty(Application.java:829)

at com.sap.ip.bi.base.application.impl.Application.startApplicationStep(Application.java:346)

at com.sap.ip.bi.base.application.impl.Application.initialization(Application.java:326)

at com.sap.ip.bi.base.application.ApplicationFactory.createApplication(ApplicationFactory.java:63)

at com.sap.ip.bi.bics.remote.impl.rmi.cc.ConnectionContextStateless.createApplication(ConnectionContextStateless.java:72)

at com.sap.ip.bi.bics.remote.impl.rmi.cc.AbstractConnectionContext.getApplication(AbstractConnectionContext.java:172)

... 31 more

Caused by: com.sap.ip.bi.base.service.connection.ConnectionException: No connection exists for system "BD1CLNT500"

at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:206)

at com.sap.ip.bi.base.portal.connection.impl.GenericConnectionPool.getMasterSystemConnection(GenericConnectionPool.java:67)

... 39 more

Caused by: com.sap.mw.jco.JCO$Exception: (101) RFC_ERROR_PROGRAM: 'user' missing

at com.sap.mw.jco.MiddlewareJRfc.generateJCoException(MiddlewareJRfc.java:518)

at com.sap.mw.jco.MiddlewareJRfc$Client.connect(MiddlewareJRfc.java:1086)

at com.sap.mw.jco.JCO$Client.connect(JCO.java:3256)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.connectWithJCO(SAPCFConnectorManagedConnection.java:429)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.establishInitialConnection(SAPCFConnectorManagedConnection.java:204)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnection.init(SAPCFConnectorManagedConnection.java:183)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:129)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:338)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:262)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:156)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:295)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:256)

at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:446)

at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:84)

at com.sap.ip.bi.base.portal.connection.PortalConnectionPool.getConnection(PortalConnectionPool.java:170)

Please your help and solution on this,

Thanks and Best Regards,

Widi

Accepted Solutions (1)

Accepted Solutions (1)

ravishanker_cheedepudi
Active Participant
0 Kudos

Your BW system has JAVA stack installed ? other wise we can not connect Xcelsius directly to BI .

Ravi

former_member182416
Active Contributor
0 Kudos

HI

IF BW does not hava Java Stack then can we use java Stack of Other Netweaver 7 System?

Regards

Rajendra

marcio_evaldt
Active Participant
0 Kudos

No. The Java stack must be integrated to the BW system as per SAP Note 917950 for Xcelsius integration purposes.

So, no Java stack from another system (like in an FPN scenario) can be used.

The requisites note is number 1400236.

Kind Regards,

Marcio

Former Member
0 Kudos

Folks,

Just as a data point. The fix for the connection issue (adjust the connection settings to Assertion Ticket) worked for us as well.

We do however, have the J2EE stack separate from the BW system. We have the BI components (BI-BASES in particular) deployed in our portal.

We've been successful in a BW ABAP and Portal J2EE stack configuration.

Cheers,

Tim

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Theodorus,

We are experiencing exactly the same error. Have you been able to resolve the issue and if so how?

Thanks,

Mustafa.

Former Member
0 Kudos

Hi Mustafa,

Yes, we are able to resolve the issue.

This issue happen because we change the configuration in

System Admin -> System Configuration -> Portal Content -> Systemlandscape -> (your system landscape)

- Display = Object

- Property Category = User Management

- Authentication Ticket Type = SAP Assertion TIcket

- Logon Method = SAPLOGONTICKET

- User Mapping type = admin,user

After we change this configuration, our we can connect with our Xcelcius to SAP BW.

Please kindly check your User Management configuration.

Regards,

Widi

Former Member
0 Kudos

Hi Widi,

Thanks very much for the prompt response. It has solved our problem. Can I ask how you came across this solution as it is not so obvious from the standard SAP documentation?

Regards,

Mustafa.

PS: Our Portal Administrator says "terima kasih". Apparently you will know what it means.

Former Member
0 Kudos

Hi Mustafa,

I read from the SAP notes and SAP Forums.

But I forgot the SAP notes number, I remember when you want to connect your Portal to SAP BW, you must add this configuration.

PS:

hahaha.. say "sama-sama" to your Portal Admin.

Do I know your portal Admin? apparently he/she knows my language 😃

Regards,

Widi