BW 3.5 UDI - Java Connector Config

Hi,
I've installed the Microsoft SQL Server JDBC Driver and am trying to do the J2EE config is the Visual Administrator so that BW can use it to extract data.
Can anyone point me at a how to guide or some more info on this? The Netweaver 04 Help says that this is documented in the install guide, but it's not there.
Many thanks,
Mike

Hi,
I think the question is related to what you have asked.
What is the best approach and the best ressources to learn about SAP BW 3.5 & SAP EP 6.0 Integration?
The topic is documented in great detail. The documentation about the required Customizing is available at http://help.sap.com and "SAP NetWeaver/Release '04/English/SAP Library/SAP NetWeaver/Integration Information /SAP Business Information Warehouse/BI Suite: Business Explorer/Integration into the SAP Enterprise Portal/Settings in SAP BW and SAP EP".
Please also check note 702350.
Implement the required settings for SAP BW 3.5 or higher in the IMG (transaction SPRO) under "SAP Reference IMG/BW Customizing Implementation Guide/SAP NetWeaver/SAP Business Information Warehouse/Reporting-relevant Settings/BEx Web/Integration into the SAP Enterprise Portal". The Customizing step "Overview: Integration into the SAP Enterprise Portal" contains a detailed description of the steps and settings required in SAP BW and SAP EP.
ASSIGN POINTS if you find it usefull
arun

Similar Messages

MDM Java Connector Config Error.

We deployed "com.sap.mdm.tech.connector.sda", "com.sap.mdm.tech.mdm4j.sda" using SDM. The deployment was successful. We wanted to set all the parameters like
UserName, Password,Server, Port, RepositoryLanguage as Key-Value pair in MDM Connector properties in Visual Admin from Server->Connection Container->Connectors -> MDM Factory -> Managed Connection Factory -> Poperties.
The intention was to use "spec.getAllConnectionProperties()" code to get the properties at runtime using following code given below.
Context ctx = new InitialContext();
IConnectionFactory conFactory = (IConnectionFactory)
ctx.lookup("deployedAdapters/MDM Factory/shareable/MDM Factory");
IConnectionSpec spec = conFactory.getConnectionSpec();
While setting these properties in Visual Admin, it threw an error.
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 19149650:com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.mdm.connector.connection.MdmManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1210)
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.registerConnector(DeployAdmin.java:2015)
     at com.sap.engine.services.connector.jca.deploy.ContainerImpl.prepareStart(ContainerImpl.java:1144)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
     at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoSuchMethodException: com.sap.mdm.connector.connection.MdmManagedConnectionFactory.setUserName(java.lang.String)
     at java.lang.Class.getMethod(Class.java:986)
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1190)
     ... 42 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:663)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
     at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 19149650:com.sap.engine.services.connector.exceptions.BaseDeploymentException: Cannot access methods of instance of class "com.sap.mdm.connector.connection.MdmManagedConnectionFactory". Possible reasons: the class is not public and is in another package, the current method does not have access to the appropriate zero-argument constructor or there is no such method.
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1210)
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.registerConnector(DeployAdmin.java:2015)
     at com.sap.engine.services.connector.jca.deploy.ContainerImpl.prepareStart(ContainerImpl.java:1144)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:223)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:171)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:342)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:126)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:645)
     at com.sap.engine.services.connector.jca.deploy.ContainerImpl.startApplication(ContainerImpl.java:1745)
     at com.sap.engine.services.connector.jca15.gui.RuntimeControlsImpl.startApplication(RuntimeControlsImpl.java:169)
     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:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:409)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:258)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:131)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:212)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:766)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:320)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:198)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:129)
     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:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.lang.NoSuchMethodException: com.sap.mdm.connector.connection.MdmManagedConnectionFactory.setUserName(java.lang.String)
     at java.lang.Class.getMethod(Class.java:986)
     at com.sap.engine.services.connector.jca.deploy.DeployAdmin.instantiateMCF(DeployAdmin.java:1190)
     ... 42 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:270)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:127)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:245)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4761)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:661)
     ... 32 more
How do I solve this bug? We tried both in NW04 SP17 J2EE engine and NW04s SPS9 J2EE engine. It is throwing error in both. Any immediate help will highly be recognise.
Best Regards
Kalyan

Hi Kalyan,
setting the properties in visual admin is not supported for the MDM connector. You always need to set the properties in your code:
                spec.setPropertyValue("UserName", user);
                spec.setPropertyValue("Password", password);
                spec.setPropertyValue("Server", server);
                spec.setPropertyValue("Port", String.valueOf(port));
                spec.setPropertyValue("RepositoryLanguage", lang);
                spec.setPropertyValue("CodeRegion", "English [US]");
               //     Get the Connection
               connection = connectionFactory.getConnectionEx(spec);
               // Retrieve Native inteface
               INative nativeInterface = connection.retrieveNative();
               // Get the CatalogData the physical connection
               catalog = (CatalogData)
               nativeInterface.getNative(CatalogData.class.getName());
Kind regards,
Andreas

RFC JAVA CONNECTOR CAUSING THE JAVA TO BE IN SAFE MODE

Hi GURUS :
We have SolMan with JAVA as Add in . Now during the JSPM Launch the JSPM Aborts with the Err Messages as shown :
in trace file dev_jrfc.trc and in defaultTrace we have this same message :
>>>>
#1.5 #0003BA951BE1004C0000000500007486000456B88DE8595D#1221250561628#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine#J2EE_GUEST#0##n/a##d7e28da080f311ddc3de0003ba951be1#SAPEngine_Application_Thread[impl:3]_27##0#0#Error#1#/System/Server#Plain###Bean SLDJAVA_ACCESSOR_REQUESTnot found on host <fqdn of host name> ProgId =JCOLDAPI: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.registered entries for FuctionName=JNDIName : {}#
#1.5 #0003BA951BE1004C0000000600007486000456B88DE85D04#1221250561629#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##d7e28da080f311ddc3de0003ba951be1#SAPEngine_Application_Thread[impl:3]_27##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host <fqdn of host name>, ProgId =JCOLDAPI: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.#
#1.5 #0003BA951BE1004C0000000700007486000456B88DE85E8C#1221250561629#com.sap.engine.services.rfcengine##com.sap.engine.services.rfcengine.handleRequest#J2EE_GUEST#0##n/a##d7e28da080f311ddc3de0003ba951be1#SAPEngine_Application_Thread[impl:3]_27##0#0#Error##Plain###java.lang.RuntimeException: Bean SLDJAVA_ACCESSOR_REQUESTnot found on host <fqdn of host name>, ProgId =JCOLDAPI: Path to object does not exist at rfcaccessejb_stateful, the whole lookup name is rfcaccessejb_stateful/SLDJAVA_ACCESSOR_REQUEST.
 at com.sap.engine.services.rfcengine.RFCDefaultRequestHandler.handleRequest(RFCDefaultRequestHandler.java:138)
 at com.sap.engine.services.rfcengine.RFCJCOServer$J2EEApplicationRunnable.run(RFCJCOServer.java:254)
 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:102)
 at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)
<<<
Now , this JCOLDAPI is Java RFC Connector with User PORTALADMIN and at the ABAP Side we see that the J2EE_ADMIN pwd was changed by this PORTALADMIN !! We had at the same time stamp, the message in the log file of the JSPM that credential supplied to log in to J2EE Engine is not valid ( 'cause, the PORTALADMIN had changed the PW
of the J2EE_ADMIN ) - While attempting to Launch the JSPM for JAVA Patches > It aborts with the same above message !!
Half of the SW Comp were updated and rest half aborts repeatedly with the above message.
Same way the Vis Admin won't start with the msg that Credential to connect J2EE is not valid. Although there was no change at the Config Tool Secure Store > J2EE Admin and SAPSR3DB passwords !!
I have changed both the J2EE_ADMIN and the PORTAL ADMIN to the User Type Service User ( note 622464 ) ..have
kept the same pw at ABAP and configtool secure store. But the java is not coming up neither through SMICM nor through the startsap j2ee command as SMPADM.
i.e. it would comeup only in SAFE Mode !!
This JCOLDAPI RFC Java Connector 's PORTALADMIN has several rights at the ABAP Side and is used for EWA Purpose.
JAVA is running in SAFE mode and no matter how many time I try at the config tool Side to bring it in normal mode it is not swithcing to normal mode > I disble the safe mode at the ConfigTool Side > Apply > Save . > Restart the JAVA through the jcmon > shutdown and restart cluster under #10 Cluster Admin Menu > it is coming up only in SAFE mode again with the abvoe error message !!! Restart through the SMICM don't even work at all !!. Also, the system is slow ..even to come in safe
mode JAVA takes about 45 minutes !!!
Also, since the JAVA is coming up only in safe mode the SLD and the browser page is not available. The jcomon displays the instance status as ' Synchronizing Binaries' since
last 20 hours ..this means that the instance is in hang state.
Any idea how to solve this problem ?
Thanks a Lot in Advance,
Regards,
- Ishan
Edited by: ISHAN P on Sep 13, 2008 2:54 PM

hi ishan,
do you have solved the problem?? as ??
thanks
umberto

Error while deploying MDM Java Connector for EP

Hi,
i am a newbie to MDM.i am trying to develop a portal component with the blog "Using MDM5.5 Java Connector with SAP Enterprise Portal 6.0" as reference.
i created an MDM system in portal and the connection tests passed.
But when i deploy the code i get the following exception-
java.lang.NullPointerException
 at com.sap.mdm.connector.connection.MdmConnectionFactory.getConnectionEx(MdmConnectionFactory.java:170)
 at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:304)
 at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:258)
 at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:478)
 at com.sapportals.portal.ivs.cg.ConnectorService.getConnection(ConnectorService.java:85)
 at com.cts.mdm.MDMtestcomp.doContent(MDMtestcomp.java:36)(this points to the line connection = cgService.getConnection("MDM_SYSTEM_ALIAS", prop);)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.serviceDeprecated(AbstractPortalComponent.java:209)
 at com.sapportals.portal.prt.component.AbstractPortalComponent.service(AbstractPortalComponent.java:114)
 at com.sapportals.portal.prt.core.PortalRequestManager.callPortalComponent(PortalRequestManager.java:328)
This is my code-
IConnectorGatewayService cgService = (IConnectorGatewayService)
 PortalRuntime.getRuntimeResources().getService(IConnectorService.KEY);
 ConnectionProperties prop =
 new ConnectionProperties(request.getLocale(), request.getUser());
 IConnection connection = null;
 connection = cgService.getConnection("MDM_SYSTEM_ALIAS", prop);
 INative nativeInterface = connection.retrieveNative();
 CatalogData catalog = new CatalogData();
 catalog = (CatalogData)
 nativeInterface.getNative(CatalogData.class.getName());
 ResultSetDefinition rsd = new ResultSetDefinition("Customers");
 rsd.AddField("Name");
 Search search = new Search("Customers");
 A2iResultSet rs = null;
 rs = catalog.GetResultSet(search,rsd,"Name",true,0);
response.write(rs.GetFields().toString());
Have i missed anything?
Should i deploy any .jar file? (i've already deployed MDM4J.jar) and referenced it in portalapp!
Thanks in advance
SwarnaDeepika

Hello Swarna:
I believe than rather than deploying the MDM4J.jar, you should deploy this components:
com.sap.mdm.tech.mdm4j.sda
com.sap.mdm.tech.connector.sda
BPMDMTECHN00_0.sca
BPMDMAPPLI00_0.sca
Once you deploy those, you should have no problems. Another solution would be to take your MDM4J.jar and wrap it into an SDA, then deploy, but that would be pretty much the same.
Those components are included on your MDM CD. Please ensure you use the same Version/support package/hotfix all over your landscape.
I hope that helps
Alejandro

SAP Business One - Java Connector

Hi All,
 
We have a SAP Business One Application installed on a laptop. The requirement is to be able to use the SAP Java API to update tables in the system. We are not allowed to connect directly to the database and was advised to use the API instead.
 
The downloaded API that we are using is "sapjco30P_6-10005324 32 bit.zip". I have included the dll file contained in this package in the WINDOWS/system32 folder. I am using Eclipse as IDE and already included the "sapjco3.jar" in the classpath.
 
First question: Am I using the right Java Connector for SAP Business One?
 
I got sample code on how to connect using JCO:
 
package sample; 
import java.io.File; 
import java.io.FileOutputStream; 
import java.util.Properties; 
import java.util.concurrent.CountDownLatch; 
import com.sap.conn.jco.AbapException; 
import com.sap.conn.jco.JCoContext; 
import com.sap.conn.jco.JCoDestination; 
import com.sap.conn.jco.JCoDestinationManager; 
import com.sap.conn.jco.JCoException; 
import com.sap.conn.jco.JCoField; 
import com.sap.conn.jco.JCoFunction; 
import com.sap.conn.jco.JCoFunctionTemplate; 
import com.sap.conn.jco.JCoStructure; 
import com.sap.conn.jco.JCoTable; 
import com.sap.conn.jco.ext.DestinationDataProvider; 
public class StepByStepClient 
{ 
 static String ABAP_AS = "ABAP_AS_WITHOUT_POOL"; 
 static String ABAP_AS_POOLED = "ABAP_AS_WITH_POOL"; 
 static String ABAP_MS = "ABAP_MS_WITHOUT_POOL"; 
 static 
 { 
 Properties connectProperties = new Properties(); 
 connectProperties.setProperty(DestinationDataProvider.JCO_ASHOST, "localhost"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_SYSNR, "06"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "000"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_USER, "manager"); //sapuser 
 connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "manager"); //sap1234 
 connectProperties.setProperty(DestinationDataProvider.JCO_LANG, "en"); 
 createDataFile(ABAP_AS, "jcoDestination", connectProperties); 
 connectProperties.setProperty(DestinationDataProvider.JCO_POOL_CAPACITY, "3"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_PEAK_LIMIT, "10"); 
 createDataFile(ABAP_AS_POOLED, "jcoDestination", connectProperties); 
 connectProperties.clear(); 
 connectProperties.setProperty(DestinationDataProvider.JCO_MSHOST, "localhost"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_R3NAME, "SID"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_CLIENT, "000"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_USER, "manager"); //sapuser 
 connectProperties.setProperty(DestinationDataProvider.JCO_PASSWD, "manager"); //sap1234 
 connectProperties.setProperty(DestinationDataProvider.JCO_GROUP, "GROUP"); 
 connectProperties.setProperty(DestinationDataProvider.JCO_LANG, "en"); 
 createDataFile(ABAP_MS, "jcoDestination", connectProperties); 
 } 
 static void createDataFile(String name, String suffix, Properties properties) 
 { 
 File cfg = new File(name"."suffix); 
 if(!cfg.exists()) 
 { 
 try 
 { 
 FileOutputStream fos = new FileOutputStream(cfg, false); 
 properties.store(fos, "for tests only !"); 
 fos.close(); 
 } 
 catch (Exception e) 
 { 
 throw new RuntimeException("Unable to create the destination file " + cfg.getName(), e); 
 } 
 } 
 } 
 public static void step1Connect() throws JCoException 
 { 
 JCoDestination destination = JCoDestinationManager.getDestination(ABAP_AS); 
 System.out.println("Attributes:"); 
 System.out.println(destination.getAttributes()); 
 System.out.println(); 
 destination = JCoDestinationManager.getDestination(ABAP_MS); 
 System.out.println("Attributes:"); 
 System.out.println(destination.getAttributes()); 
 System.out.println(); 
 } 
 public static void main(String[] args) throws JCoException 
 { 
 step1Connect(); 
 } 
} 
 
Each time I run the application I run into an error:
 
Attributes: 
Exception in thread "main" com.sap.conn.jco.JCoException: (102) JCO_ERROR_COMMUNICATION: Connect to SAP gateway failed 
Connection parameters: TYPE=A DEST=ABAP_AS_WITHOUT_POOL ASHOST=localhost SYSNR=06 PCS=1 
LOCATION CPIC (TCP/IP) on local host with Unicode 
ERROR connection to partner '127.0.0.1:3306' broken 
TIME Mon May 09 10:46:46 2011 
RELEASE 720 
COMPONENT NI (network interface) 
VERSION 40 
RC -6 
MODULE gwxx.c 
LINE 646 
DETAIL NiIRead: P=127.0.0.1:3306; L=0.0.0.0:50496 
SYSTEM CALL GwRead 
ERRNO 10054 
ERRNO TEXT WSAECONNRESET: Connection reset by peer 
COUNTER 2 
 at com.sap.conn.jco.rt.MiddlewareJavaRfc.generateJCoException(MiddlewareJavaRfc.java:662) 
 at com.sap.conn.jco.rt.MiddlewareJavaRfc$JavaRfcClient.connect(MiddlewareJavaRfc.java:1362) 
 at com.sap.conn.jco.rt.ClientConnection.connect(ClientConnection.java:721) 
 at com.sap.conn.jco.rt.PoolingFactory.init(PoolingFactory.java:103) 
 at com.sap.conn.jco.rt.ConnectionManager.createFactory(ConnectionManager.java:293) 
 at com.sap.conn.jco.rt.DefaultConnectionManager.createFactory(DefaultConnectionManager.java:46) 
 at com.sap.conn.jco.rt.ConnectionManager.getFactory(ConnectionManager.java:262) 
 at com.sap.conn.jco.rt.RfcDestination.initialize(RfcDestination.java:509) 
 at com.sap.conn.jco.rt.RfcDestination.getAttributes(RfcDestination.java:347) 
 at com.sap.conn.jco.rt.RfcDestination.getAttributes(RfcDestination.java:27) 
 at sample.StepByStepClient.step1Connect(StepByStepClient.java:74) 
 at sample.StepByStepClient.main(StepByStepClient.java:304) 
Caused by: RfcException: [null] 
 message: Connect to SAP gateway failed 
Connection parameters: TYPE=A DEST=ABAP_AS_WITHOUT_POOL ASHOST=localhost SYSNR=06 PCS=1 
 
Second question: What seems to be the problem with my sample application? Do I need to use a different Java Connector for SAP Business One or SAP Business One does not support Java Connector?
 
Please help.
 
Thank you all.
Edited by: kevinroy on May 9, 2011 4:51 AM

Hi, 
Thank you very much for the reply. I am now able to move forward with what I am doing. 
I used the following code in connecting but am encountering an error: 
public class ConnectSAP {
 // company interface
 public ICompany company;
 private SBOErrorMessage errMsg = null;
 public static void main(String[] args) {
 ConnectSAP company = new ConnectSAP();
 company.conn();
 //method make connection andinitialize company instance
 public int conn() {
 int rc = 0;
 try {
 company = SBOCOMUtil.newCompany();
 company.setServer("192.168.0.216"); //192.168.0.216
 company.setCompanyDB("SBODemoUS");
 company.setUserName("manager");
 company.setPassword("manager");
 company.setDbServerType(SBOCOMConstants.BoDataServerTypes_dst_MSSQL2005);
 company.setUseTrusted(new Boolean(false));
 company.setLanguage(SBOCOMConstants.BoSuppLangs_ln_English);
 company.setDbUserName("username");
 company.setDbPassword("password");
 //company.setAddonIdentifier("...");
 //company.setLicenseServer("...");
 rc = company.connect();
 if (rc == 0) {
 System.out.println("Connected!");
 } else {
 errMsg = company.getLastError();
 System.out.println(
 "I cannot connect to database server: "
 + errMsg.getErrorMessage()
 + " "
 + errMsg.getErrorCode());
 } catch (Exception e) {
 e.printStackTrace();
 return -1;
 return rc;
 public void freeConnection(){
 company.disconnect();
} 
I am getting the error "Failed to Connect to SBOCommon -111". 
Error is still the same even if I set UseTrusted to true and comment the DbUserName and DbPassword. 
Do I need to specify the license? Or login to SAP before connecting? 
Thank you.

How to get pdf file from sap presentation server using java connector

Hi Friends,
with the below code i am able to get po details in pdf in presentation server.
DATA : w_url TYPE string
 VALUE 'C:\Documents and Settings\1011\Solutions\web\files\podet.pdf'.
CALL FUNCTION 'ECP_PDF_DISPLAY'
 EXPORTING
 purchase_order = i_ponum
 IMPORTING
PDF_BYTECOUNT =
 pdf = file " data in Xsting format
*Converting Xstring to binary_tab
 CALL FUNCTION 'SCMS_XSTRING_TO_BINARY'
 EXPORTING
 buffer = file
APPEND_TO_TABLE = ' '
IMPORTING
OUTPUT_LENGTH =
 TABLES
 binary_tab = it_bin " data in binary format
**Downloading into PDF file
 CALL FUNCTION 'GUI_DOWNLOAD'
 EXPORTING
BIN_FILESIZE =
 filename = w_url
 filetype = 'BIN'
 TABLES
 data_tab = it_bin
when i am using java connector , to retirve the file from presentation server , the follwoing error i am getting...
init:
deps-jar:
compile-single:
run-single:
com.sap.mw.jco.JCO$Exception: (104) RFC_ERROR_SYSTEM_FAILURE: Error in Control Framework
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.nativeExecute(Native Method)
 at com.sap.mw.jco.rfc.MiddlewareRFC$Client.execute(MiddlewareRFC.java:1244)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3842)
 at com.sap.mw.jco.JCO$Client.execute(JCO.java:3287)
 at PdfGen.<init>(PdfGen.java:35)
 at PdfGen.main(PdfGen.java:78)
Java Result: 1
BUILD SUCCESSFUL (total time: 1 second)
i debugged too, problem with gui_download......
I am very glad to all with your suggestions!!
Regards,
Madhu..!!

Hi
You can try to create an external command (transaction SM69).......sorry I've forgotten,,,,they works on application
How do you call CL_GUI_FRONTEND_SERVICES=>EXECUTE?
Max
Edited by: max bianchi on Oct 13, 2011 10:27 AM

How to install the SAP Java Connector

Hi,
I am unsure how to install the SAP Java Connector on Linux (Suse Linux Enterprise 10). The SAP Integration Kit install and admin guide says:
===
u2022 Copy the librfccm library and the libsapjcorfc library to busines
sobjects_root/enterprise120/PLATFORM_PATH, where busines
sobjects_root is the full path to your businessobjects directory,
and PLATFORM_PATH is your platform. For example, PLATFORM_PATH
is solaris_sparc for an installation on Solaris.
u2022 Use symbolic links for the location of the librfccm library and the lib
sapjcorfc library.
u2022 Add the location of the librfccm library and the libsapjcorfc library
to the library path.
===
Do I have to do all 3 steps or is the 1st one (copying of files) enough?
On the other hand, the SAP Java Connector guide says:
===
Then add {sapjco-install-path} to the LD_LIBRARY_PATH environment variable.
Finally, add {sapjco-install-path}/sapjco.jar to your CLASSPATH environment variable.
===
So, what to do?
Thanks!

Thanks for your help. So i copied the 2 files as mentioned in point 1.
Where do I have to copy the file sapjco.jar to? There is no shared lib folder after installing BO Edge 3.1 on a Linux system.
I copied the sapjco.jar to /bobje/tomcat/common/lib but still get the message that the Java Connector files are not in the correct directory.
I already copied the files librfccm.so and libsapjcorfc.so to /bobje/enterprise120/linux_x86 .
Thanks again!
Edit: problem solved: Copying the sapjco.so to tomcat/shared/lib is correct, if the directory doesn't exist then just create it (mkdir). The message is just plain information 7 hint.

Enterprise JavaBeans and SNMP Java Connector

There is possible to develop a Java Connector that will allow my J2EE application to collaborate ( send , receive) SNMP commands with various network devices ( sensors, Access Points, hardware devices).
The information eventualy will be pushed back to the subscribed users using AJAX technologies.
Mike

Hi,
I do not get your question.....
You want to connect from MI7.1 directly to a BAPI in the Middleware? Well, in 7.0 there was Generic Sync to do that - and I think this should be still there. With Generic sync it was possible to connect to call any BAPI in the middleware directly - if your user had appropiate rights. Check MDK for details.
And if you want to do that in our own app - if this is the intention of your question.... well.... then I would tell you this is under SAP (C), so as you know you could decompile the MI client code, but this is not allowed.
But I guess it was the first thing you are after, so see if that answer helps. But even there you need the running MI middleware - and this thing confused me in your question - are you using MI already or not and what do you want to do?
Regards,
Oliver

Is this possible: SAP Java Connector - XI - R3 with XI RFC Adapter?

Hi,
I try to call a RFC on a remote R/3 System over the XI Server in a Java Application with SAP Java Connector.
I have configured a RFC Sender Adapter in XI. I get the
following Exception:
"lookup of alternativeServiceIdentifier via CPA-cache failed for channel 'SenderChannel_RFC"!
Is this scenario possible? Or do the connection from
a SAP Java Connector App to the XI RFC Adapter not work?
You can't set the Client and System ID of a Third-Party or
Standalone Java system in the SLD.
Thanks for any help!
Regards
Wolfgang

Hi,
We use a JCO for directly connecting to sap systems.
In that case we need not use any XI also.
But if you want to use RFC adapter and java application the best way is to use java proxies as sender and reciever as RFC adapter.
I donot think there is any architectural significance in using rfc adapter of XI while using JCO.
Let me know if I mis-understood the context.

Using Java Connector Calling RFC.....But it's not returning correct result

Hi Friends,
In the code ....
I am calling Remote Function module ZRFC_PO_VEND_VALID using java connector and passing PO_Number and Vendor Number as input parameters and after execution it returns (E_POVALID =1 [PO_NUMBER exists for Vendor number] otherwise E_POVALID = 0 )
when i am executing the below code ....in both cases it is returning Zero value.
I tested the function module in se37 its working....
may i know the reason for this....
import com.sap.mw.jco.*;
@author Thomas G. Schuessler, ARAsoft GmbH
http://www.arasoft.de
public class TutorialBapi1 extends Object {
JCO.Client mConnection;
JCO.Repository mRepository;
public TutorialBapi1() {
try {
// Change the logon information to your own system/user
mConnection =
JCO.createClient("100", // SAP client
"abap", // userid
"abap", // password
"en", // language
"sapdev1", // application server host name
"00"); // system number
mConnection.connect();
mRepository = new JCO.Repository("ARAsoft", mConnection);
catch (Exception ex) {
ex.printStackTrace();
System.exit(1);
JCO.Function function = null;
JCO.Table codes = null;
try {
function = this.createFunction("ZRFC_PO_VEND_VALID");
if (function == null) {
System.out.println("ZRFC_PO_VEND_VALID" +
" not found in SAP.");
System.exit(1);
//mConnection.execute(function);
JCO.Field vendID = function.getImportParameterList().getField("I_EBELN");
JCO.Field poID = function.getImportParameterList().getField("I_LIFNR");
vendID.setValue("20081");
poID.setValue("4500000017");
try {
mConnection.execute(function);
catch (Exception ex) {
     ex.printStackTrace();
     System.exit(1);
JCO.Field povalid =
     function.getExportParameterList().getField("E_POVALID");
//if (povalid.getValue() == null ){
     // System.out.println("Error Message");
System.out.println(povalid.getValue());
     //if (povalid == null ){
          //System.out.println(povalid.getValue("E_POVALID"));
          //System.out.println("Error Message");
          //System.exit(1);
catch (Exception ex) {
     ex.printStackTrace();
     System.exit(1);
mConnection.disconnect();
public JCO.Function createFunction(String name) throws Exception {
     try {
     IFunctionTemplate ft =
     mRepository.getFunctionTemplate(name.toUpperCase());
     if (ft == null)
     return null;
     return ft.getFunction();
     catch (Exception ex) {
     throw new Exception("Problem retrieving JCO.Function object.");
     public static void main (String args[]) {
     TutorialBapi1 app = new TutorialBapi1();
with warm regards,
Madhu.

Hi Ravi ,
I tried as per your sugggestion..still getting the same problem.
Regards,
Madhu!!

Need Standard BAPI To Create Opportunity in SAP Using Java Connector.

Hi All,
What is the standard BAPI to create an opportunity in SAP CRM through Java Connector.
Please share code if available for doing same. I have found BAPI_OPPORTUNITY_CREATE_MULTI .
How to create opportunity in SAP through java connector using BAPI_OPPORTUNITY_CREATE_MULTI .

Hi,
I think you can search for it or you can create a thread at ABAP section.

Where can i find the BI Java Connector Files (for example: bi_sdk_jdbc.rar)

Hi,
where can i find the BI Java Connector Files:
bi_sdk_jdbc.rar
bi_sdk_xmla.rar
bi_sdk_sapq.rar
bi_sdk_odbo.rar
Can anyone help me?

hi Christian,
these files should be included in bi java sdk
https://www.sdn.sap.com/irj/sdn/downloaditem?rid=/webcontent/uuid/78b3db58-0501-0010-b895-f75cd8fdf674 [original link is broken]
hope this helps.

Integrating SAP Java Connector with SAP XI

Hi XI experts
We are about to integrate our SAP ERP2004 system with a new WMS system. The vendors of the WMS system normally integrates with ERP directly through SAP Java Connector, but we would like to put SAP XI between the two systems so we have good way of monitoring the messages beeing sent.
I would like to make a synchronous test scenario where we send a ARTMAS idoc from SAP to XI which sends it to the WMS. After WMS system receives the ARTMAS Idoc it sends an acknowledgement back to XI which passes it on to SAP.
The integration would then look like this:
SAP ERP <-> SAP XI <-> WMS (Jco)
Is this scenario possible? And if so, how would you suggest to set it up?
I was thinking of using the RFC adapter to connect to the Java Connector of WMS, but am not sure if this is the right approach or how it should be set up.
Any help or comments would be greatly appreciated.
Best Regards
Chris

I have made a setup like this:
SAP <-> XI <-> WMS
The Scenario is like this:
SAP sends an ARTMAS03 idoc to XI which maps it directly to the same ARTMAS03 idoc structure (need a few changes in the future so thats why im not using IDOC tunnelling) then it uses a RFC receiver adapter to connect to our SAP gateway, where the WMS is registrered through JCO.
When I first sent the idoc, i got a "RfcAFWException: failed to read funtionname from XML document: missing namespace declaration(2)" then after reading Q23 in note 730870, I used the RFCNormalizer xslt to change the namespace to a "urn:sap-com:document:sap:rfc:fuctions" instead of the "urn:sap-com:document:sap:idoc:messages". The error is now "functiontemplate from repository was <null>".
As far as i can see the error is because the metadata repository defined in the RFC adapter cant find the function module that normally would be in the root of a RFC-XML. But I dont know how I can send an Idoc through the rfc adapter to the gateway then. Anyone got some ideas?
Thanks
Chris

SAP - Lumira - ECC 6.0 - Source by java connector - timeout

Hi,
I try , to create a dataset for ERP 6.0 data by java connector ( SQL-Source).
After connection to ERP, I can select an ERP-infoset .
By selection of an infoset a SQL-Statement is created .
( select * from "Local"."INFOSET"."id of erp-infoset" )
After click "preview" and a long time I get " timeout....".
can anybody help me ?
Regards Wolfgang

Hi,
I work with version 1.15.
Without where - condition, I get the data.
(select * from Z_SD_ADR)
But by where condition I see only the header line ( Field-names)
without data.
My select statement:
select * from Z_SD_ADR where 'KNVV-KUNNR' = '1000'
( I tried also with 6 leading-Zero).
The Query contains a join from KNVV to KNA1.
Regards Wolfgang

DI Java Connector

Hello All,
First of all i have to say that im sick of searching abt this.......so if anyone can help it'll mean a lot to me. im trying to connect to SAP Business One from Java, in the SDK help file it says that i can connect to B1 through DI API, but how can i do it with Java???...........it says to use "SAPbobsCOM67.dll" file to connect with java....how can i do this??........and it says it includes the packages "com.sap.smb.sbo.api" , "com.sap.smb.sbo.util" , "com.sap.smb.sbo.wrapper.util" but i cant find it......i downloaded the SAP JCo 2.0 too from SAP Service Market Place....but it only has classes to connect to SAP R/3 System. What i need to do is connect to Business One with pure Java Code........using those class packages i listed above....but i don't seem to find it on the internet.....somebody pls help me on this.....because im not into VB .Net.... Thanks.

Hi Malinda,
You have to install the DI API and the SBO SDK to have the Java Connector (JCO)libraries and to have the JCO help file.
In basic the API is the same as with .NET, but there are some differences.
You can scan this forum for some samples.
Regards
Ad

BW 3.5 UDI - Java Connector Config

Similar Messages

Maybe you are looking for