VC 6.0 EP SP14 compatibility?

[Former Member]

Hi,

We have VC 6.0 Patch 6 installed and I hooked up it with SAP Enterprise Portal SP14, which comes by default with portal addons. Now I want to create BI JDBC system and use it in BI Integrator:

I was going through forums and found many wierd problems with this compatibility?

1. IT seems that the Portal addons that comes by default with SP14 is not compatible with VC 6.0, so where would i get Portal Addons of SP13 so that I can deploy in my Portal?

2. What about BIUDIXX_X.sca and BIMMRXX_X.sca files. Is it Ok to install SP14, if not where can i get SP13 related.

3. What services should i start after installing the above SDA/SCA files?

4. when I login into Visual Admin of J2EE, as mentioned in the Troubleshooting guide, I cant see the default "SDK_JDBC" connector. what might be the problem?

5. final question: I want to get data from the default oracle DB that is connected to my portal, Is it again really necessary to create a driver for this?

Its pretty long list, but please help me in this regard.

Thank You

[Former Member]

Hi Reddy,

I have the portal addons for sp13 and appropriate biudi and bimmr files and some helpful documents...Gimme ur mail id..i ll forward you

regards

Amit

[Former Member]

t

Message was edited by:

Reddy

[Former Member]

Hi Reddy,

I have sent...check it..

regards

Amit

[Former Member]

Amit,

I didnt get those docs... could you please resend.

Thanks

[Former Member]

Hi Reddy,

I have sent u sp13 addons and installation guide..u can get BIUDI and BIMMR files from market place..

https://websmp205.sap-ag.de/swdc -> search for all categories -> search for BIUDI and BIMMR

jus remember that first import BIMMR then addons and finally BIUDI in portal..dont miss the sequence..

regards

Amit

[Former Member]

Hi Amit,

me too facing the same problem, could you send them to yogiatsap@yahoo.com

Thank You

[Former Member]

Hi Amit,

Thanks for sending those documents.

1. I Deployed BIMMR SP14

2. I undeployed all the com.sap.portal.visualcomposer.* sda files

3. I deployed SP13 verion that you sent to me.

4. I deployed BIUDI14 AND BIDUDI14P

Now I am testing the BI JDBC CONNECTIVITY:

Visual Administrator:

I am just connecting to the same oracle db as my portal is connecting to. there was already a driver by name SYSTEM_DRIVER listed in the JDBC Drivers tab.

so I went to Connection Container:

There is already a connector SDK_JDBC. In the Resource Adapter tab, I need to add the driver, so I added the string "library:SYSTEM_DRIVER", as i said that i am using the default driver.

In the properties tab, I entered URL and drivername.

and I am testing my connecting with the servlet:

http://<hostname>:<port>/TJdbc/servlet/TestJdbc

I am getting the following exception:

com.sap.ip.bi.sdk.exception.BIConnectionFailedException: Cannot open the connection at

com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:2

38) at com.sap.ip.bi.sdk.trialarea.connector.servlet.TestJdbc630.service(TestJdbc630.java:68) at

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

com.sap.engine.services.servlets_jsp.server.servlet.InvokerServlet.service(InvokerServlet.java:156) at

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

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

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

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

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

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

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

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

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

com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(Applic

ationSessionMessageListener.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:95) at

com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:160) Caused by:

com.sap.ip.bi.sdk.exception.BIResourceException: Cannot open the connection at

com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:135) at

com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnectionFactory.createManagedConnection(JdbcManagedCo

nnectionFactory.java:119) at

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

com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.ja

va:186) at

com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcConnectionFactory.getConnectionEx(JdbcConnectionFactory.java:2

33) ... 18 more Caused by: com.sap.ip.bi.sdk.exception.BIResourceException: Class DriverName is not

found at com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connectDB(Connection.java:353) at

com.sap.ip.bi.sdk.dac.connector.jdbc.impl.Connection.connect(Connection.java:105) at

com.sap.ip.bi.sdk.dac.connector.jdbc.JdbcManagedConnection.(JdbcManagedConnection.java:130) ... 22 more

exception:Cannot open the connection

Am i Missing some step here?

The probable reasons that I can think of are:

1. adding library:SYSTEM_DRIVER in the resource adapter tab, is the way that I implemented correct?

2. is it ok to use SYSTEM_DRIVER?

3. Is it mandatory to pass username and password in the properties tab.

please guide me.

Thank You

[kevshill]

Hi Reddy,

Were you able to solve this problem?

If so then how did you manage to do so?

We are have a similar kind of problem, we get the same exception .

regards,

Kevin Hill