Remote Interface to Java Connector

Is there any plans to add remote interfaces to JCA in the future?

basically we have c++ libraries for connecting to EIS systems. These are accessed from java with JNI. I want to build a resource adapter around these classes. The c++ has to be on a separate JVM because it's buggy and we dont want it to take down the whole system if it crashes. so the resource adapter has to be on a separate JVM to the classes accessing it. Therefore a remote interface would be very useful.
-ivan

Similar Messages

Enhancement request: Remote interface java file generation

Problem:
In release 9.0.3, If you want to write a method that is suppossed to be exposed in the remote interface, you have to first right click on the ejb-jar.xml's appropriate EJB name node and then add the method, specify the argument types (say about 25 in number in a small width textbox), return type, etc and check the check box 'Expose in remote interface'. Then only remote interface's java source gets updated and only after doing all this can you actually sit down to write the business logic in that method. If you first code the method and then try to add the same, it gives an error saying "duplicate method exists"
Suggestion:
The similiar feature in release 9.0.2 was much better and flexible as it allowed the generation of remote interface source after coding the actual method in the EJB source. You can first write the method and then expose it in the interface by just choosing it from a method browser and opting for exposing it in the remote interface. You donot have to write the name and number of arguments like we have to currently do in the 9.0.3 release.
(1) Actually, all public methods in the EJB source should by default be exposed in the remote interface because EJB are supposed to be used by other EJBs and JSPs only and all methods that are public but not exposed in the remote interface should actually be private or protected.
(2) Leave it up to the developer to edit the remote interface
(3) When the EJB source file is changed (public methods changed) compiled the remote interface should also be updated automatically. Why? already you have provision to change the remote interface source, so just dump all the public methods in the remote interface source when the EJB source is compiled.
(4) Ditto for EJB Homes
(5) Actually whenever the developer changes and compiles the EJB source, the remote and home source should automatically be updated AND COMPILED. (Refer: Pramati Studio 3.0 SP3 :- URL: www.pramati.com )
I was very happy with the earlier option. If anybody other then the JDeveloper Team finds this interesting, please respond. A suite like developer should be more User-friendly.
And yes expect more like this from me in the future

Hi Raghu,
Thanks for the quick response. This flexiblity in Remote interface generation and choice of methods in it at any given point in the development cycle is very much desired feature.
The other thing I would like to suggest is you look at another enhancement request in my name regarding batch updates of the "web.xml" file. You will find the thread updated today i.e. on 15th September with a reply
I will shortly post one more for lack of modularity in EJB components descriptors.
My Company Four Soft Pvt. Ltd. (www.four-soft.com) is Oracle's development partner and we use and support Oracle products. They are good but naturally we would like them to be better and more User-friendly.
Thanks once again.
Amit

Thru Java connector to update SAP by BAPI

Dear...
How to bring the data from external application through the Java connector to SAP? Pls help....

Hai Check the following Document & Links
Bapi to create customer master
BAPI_CUSTOMER_CREATEFROMDATA
BAPI_CUSTOMER_CREATEFROMDATA1
Or you can use FM SD_CUSTOMER_MAINTAIN_ALL
what is BAPI?
BAPI stands for Business API(Application Program Interface).
I have answered this question before..
A BAPI is remotely enabled function module ie it can be invoked from remote programs like standalone JAVA programs, web interface etc..
You can make your function module remotely enabled in attributes of Function module but
A BAPI are standard SAP function modules provided by SAP for remote access. Also they are part of Businees Objest Repository(BOR).
BAPI are RFC enabled function modules. the difference between RFc and BAPI are business objects. You create business objects and those are then registered in your BOR (Business Object Repository) which can be accessed outside the SAP system by using some other applications (Non-SAP) such as VB or JAVA. in this case u only specify the business object and its method from external system in BAPI there is no direct system call. while RFC are direct system call Some BAPIs provide basic functions and can be used for most SAP business object types. These BAPIs should be implemented the same for all business object types. Standardized BAPIs are easier to use and prevent users having to deal with a number of different BAPIs. Whenever possible, a standardized BAPI must be used in preference to an individual BAPI.
The following standardized BAPIs are provided:
Reading instances of SAP business objects
GetList ( ) With the BAPI GetList you can select a range of object key values, for example, company codes and material numbers.
The BAPI GetList() is a class method.
GetDetail() With the BAPI GetDetail() the details of an instance of a business object type are retrieved and returned to the calling program. The instance is identified via its key. The BAPI GetDetail() is an instance method. BAPIs that can create, change or delete instances of a business object type
The following BAPIs of the same object type have to be programmed so that they can be called several times within one transaction. For example, if, after sales order 1 has been created, a second sales order 2 is created in the same transaction, the second BAPI call must not affect the consistency of the sales order 2. After completing the transaction with a COMMIT WORK, both the orders are saved consistently in the database.
Create( ) and CreateFromData! ( )
The BAPIs Create() and CreateFromData() create an instance of an SAP business object type, for example, a purchase order. These BAPIs are class methods.
Change( )
The BAPI Change() changes an existing instance of an SAP business object type, for example, a purchase order. The BAPI Change () is an instance method.
Delete( ) and Undelete( ) The BAPI Delete() deletes an instance of an SAP business object type from the database or sets a deletion flag.
The BAPI Undelete() removes a deletion flag. These BAPIs are instance methods.
Cancel ( ) Unlike the BAPI Delete(), the BAPI Cancel() cancels an instance of a business object type. The instance to be cancelled remains in the database and an additional instance is created and this is the one that is actually canceled. The Cancel() BAPI is an instance method.
Add<subobject> ( ) and Remove<subobject> ( ) The BAPI Add<subobject> adds a subobject to an existing object inst! ance and the BAPI and Remove<subobject> removes a subobject from an object instance. These BAPIs are instance methods.
Check these Links out
http://searchsap.techtarget.com/ateQuestionNResponse/0,289625,sid21_cid558752_tax293481,00.html
http://www.sap-img.com/abap/interview-question-on-bapi-rfc-abap-objects-tables.htm
http://www.sap-img.com/fu033.htm
http://www.sap-img.com/abap/ale-bapi.htm
Please check out this thread..
Re: bapi
Also refer to the following links..
www.sappoint.com/abap/bapiintro.pdf
www.sap-img.com/bapi.htm
www.sap-img.com/abap/bapi-conventions.htm
www.planetsap.com/Bapi_main_page.htm
www.sapgenie.com/abap/bapi/index.htm
Checkout !!
http://searchsap.techtarget.com/originalContent/0,289142,sid21_gci948835,00.html
http://techrepublic.com.com/5100-6329-1051160.html#
http://www.sap-img.com/bapi.htm
http://www.sap-img.com/abap/bapi-conventions.htm
http://www.sappoint.com/abap/bapiintro.pdf
Java Connector(JCO) can call not only BAPI's but also the function modules which are remotely enabled..
BAPI's as i said earlier are remotely enabled function modules..
Hence, JCO can call also BAPI's(n not only BAPI's as u mentioned).
Thanks & regards
Sreenivasulu P

Super interfaces on EJB 3.0 Remote interface in OC4J 10.1.3

We are implementing (on OC4J 10.1.3) an EJB 3.0 Stateless Session Bean with 2 business interfaces (remote and local) both of which extend an inteface we have defined in our system.
When we look up the local interface we see our interface in the bean.
When we look up the remote interface we do not see our interface in the bean.
Any ideas?
Thanks,
Ed Dirago
Computer Sciences Corp.
FAA TFMS System

The EJB 3.0 Remote Business references are not directly stored in CosNaming. EJB 3.0 Remote references do not have the cross-vendor interoperability requirements that the EJB 2.x Remote view had.
You can still access Remote EJB references from a different JVM as long as the client has access to SJSAS naming provider. Please see our EJB FAQ for more details :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html

SJSAS 9.1 does not expose EJB 3.0 remote Interface via JNDI

I have successfully deployed a simple Stateful EJB 3.0 bean (CartBean, like the one in the Java EE 5 tutorial remote interface Cart) on SJSAS 9.1, located on machine host1.
After I deployed the CartBean, I browsed the SJSAS and noticed the existence of the following JNDI entries:
ejb/Cart
ejb/Cart__3_x_Internal_RemoteBusinessHome__
ejb/Cart#main.Cart
ejb/mgmt
ejb/myOtherEJB_2_x_bean ( +myOtherEJB_2_x_bean+ is a different 2.x bean that I have deployed as well)So, I am trying to access the remote interface of the CartBean from a remote machine, host2. The client application is a Java-standalone client.
I am using the Interoperable Naming Service syntax: corbaname:iiop:host1:3700#<JNDI name>
The problem is that the remote interface of the bean does NOT seem to be available via JNDI. I get the javax.naming.NameNotFoundException when I try to do a lookup like:
corbaname:iiop:host1:3700#ejb/Cart
On the other hand, the following lookups succeed:
corbaname:iiop:host1:3700#ejb/mgmt
corbaname:iiop:host1:3700#myOtherEJB_2_x_bean
and also the following succeeds:
corbaname:iiop:host1:3700#ejb/Cart__3_x_Internal_RemoteBusinessHome__So it seems like the Remote interface is not available via JNDI, rather only some internal SJSAS implementation (the object returned from the ejb/Cart__3_x_Internal_RemoteBusinessHome__ lookup is of type: com.sun.corba.se.impl.corba.CORBAObjectImpl
Why is this happening? I know there used to be a bug in Glassfish, but I thought it had been fixed since 2006.
Many thanks in advance, any help would be greatly appreciated.

The EJB 3.0 Remote Business references are not directly stored in CosNaming. EJB 3.0 Remote references do not have the cross-vendor interoperability requirements that the EJB 2.x Remote view had.
You can still access Remote EJB references from a different JVM as long as the client has access to SJSAS naming provider. Please see our EJB FAQ for more details :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html

Multiple inheritance in remote interfaces for EJB 3.0 session beans on Webl

Hi All,
We started migration from EJB 2.1(WLS 8.1) to EJB 3.0(WLS 10.3.2) and identified few serious problems. One of them is related with multiple business interfaces inheritance. I wrote simple example that presents point of the problem.
we have session bean AImpl:
+@Stateless(name="A")+
+@Remote({A.class})+
+@TransactionAttribute(TransactionAttributeType.REQUIRED)+
+public class AImpl implements A {+
+@Override+
+public void writeA() {+
System.out.println("A");
+}+
+@Override+
+public void writeB() {+
System.out.println("B");
+}+
+@Override+
+public void writeC() {+
System.out.println("C");
+}+
+}+
with remote interface A:
+@Remote+
+@JNDIName(A.JNDI_NAME)+
+public interface A extends B, C {+
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
+}+
As you can see A extends B, and C. Definition of both interfaces is very simple:
+public interface B {+
void writeB();
+}+
+public interface C {+
void writeC();
+}+
Everything looks nice until we want to invoke some method on AImpl bean. For above implementation code:
A a = ctx.lookup(A. JNDI_NAME);
a.writeA();
a.writeB();
a.writeC();
writes down ”A \n B” and throws exception:
caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeC()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
so.. in stub generated by WLS there is no method from interface C ! What more interesting after small change in interface A rely on change in interface implementation order from B, C to C, B (+public interface A extends C, B {+) server writes down only A and I have stack like below:
Caused by: java.lang.NoSuchMethodException: pl.gov.arimr.zszik.bazowe.slowniki.ejb.A_vt0zts_AImpl_1032_WLStub.*writeB()*
at java.lang.Class.getMethod(Class.java:1605)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.getTargetMethod(RemoteBusinessIntfProxy.java:165)
at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:57)
After this experience I came up with suspicion that Weblogic 10.3 does not support inheritance from multiple interfaces in one “generation”. Instead of that it takes only the first interface from the list.
Does anybody have some experience with such a situation? maybe someone have an idea how to work around this problem?

This is Not Supported in WebLogic that the Remote Interface extends other Interfaces. Because Annotation Processor just looks up inside the implemented interface methods. The actual interface which is Implemented by the Bean Class. So the Methods declared inside the Interface B and Interface C will be ignored and will not be available as part of the generated Stubs. Thats why u are getting NoSuchMethodError.
You can even contact Oracle Support on this...there are 3-4 Cases on it. And the Solution is Work As Designed.
Workaround is : edit your interface A as following
Declare all the Business Methods only in the Remote Interface and not inside it's Super Interfaces.
Example:
@Stateless(name="A")
@Remote({A.class})
@TransactionAttribute(TransactionAttributeType.REQUIRED)
public class AImpl implements A {
@Override
public void writeA() {
System.out.println("A");
@Override
public void writeB() {
System.out.println("B");
@Override
public void writeC() {
System.out.println("C");
@Remote
@JNDIName(A.JNDI_NAME)
public interface A extends B, C {
public static String JNDI_NAME = "A_JNDI_NAME";
void writeA();
void writeB();
void writeC();
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

A problem while getting a EJB remote interface from SJSAS 9.0

I hava deployed a session bean in SJSAS 9.0
I wrote some codes to get the remote interface as follow:
Context ctx = null;
Hashtable env = new Hashtable();
env.put ("java.naming.factory.initial","com.sun.jndi.cosnaming.CNCtxFactory");
env.put("java.naming.provider.url","iiop://127.0.0.1:3700");
try {
ctx = new InitialContext(env);
} catch (NamingException ex) {
ex.printStackTrace();
try {
Object cs =ctx.lookup(ejb.MySessionBean);
} catch (NamingException ex) {
ex.printStackTrace();
A exception occured during the lookup operation.
javax.naming.NameNotFoundException [Root exception is org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0]
at com.sun.jndi.cosnaming.ExceptionMapper.mapException(ExceptionMapper.java:44)
at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:453)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:492)
at com.sun.jndi.cosnaming.CNCtx.lookup(CNCtx.java:470)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at demo.Main.run(Main.java:46)
at demo.Main.main(Main.java:62)
Caused by: org.omg.CosNaming.NamingContextPackage.NotFound: IDL:omg.org/CosNaming/NamingContext/NotFound:1.0
at org.omg.CosNaming.NamingContextPackage.NotFoundHelper.read(NotFoundHelper.java:72)
at org.omg.CosNaming._NamingContextExtStub.resolve(_NamingContextExtStub.java:406)
at com.sun.jndi.cosnaming.CNCtx.callResolve(CNCtx.java:440)
... 5 more
Anyone can solve this problem for me???
Thanks a lot

We don't recommend explicitly instantiating the CosNaming provider within a stand-alone java client when accessing beans within the Java EE SDK. We have a simpler approach that involves just instantiating the no-arg InitialContext. Details are in our EJB FAQ :
https://glassfish.dev.java.net/javaee5/ejb/EJB_FAQ.html
--ken

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.

Remote interface distribution

Hi,
I am just learning to use RMI, have a typical setup, Server and Client and everything works fine, BUT.......
I have compiled my remote classes, ie RmtServer, RmtServerImpl, then run the rmiregistry
and then started the service, so far so good.
I then compile etc the Client class and run
My question is this, I am currently working from the same directory for all classes, I would like to truly
distribute the client and server. Do I need to put a copy of the RmtServer interface on the client?
Currently in my client I have the line:
RmtServer server = (RmtServer)Naming.lookup("rmi://" + serverHost + "/ProjectServer");
I have been reading about dynamic class loading but I am slightly confused!!!
It says that the stubs created by running "rmic" on the server classes can be loaded dynamically, thats great, but the stubs created and the RmtServer interface are not the same thing. If I have to have a "local" copy of every interface I want to use then it seems a bit limited.
My impression was that I could specify a location for a class repositry on a remote machine and then
instantiate classes from the server on the local machine! So then I would only need to have one interface on the client to enable me to connect to the server for the first time!!!
Im really confused as people can probably tell. Any help would be really appreciated

The purpose of dynamic loading is really so that you don't have to distribute the stub, or the implementation classes of any interfaces.
You can certainly load the remote interface dynamically from the codebase in the client, e.g. with URLClassLoader, but you will also have to have already loaded all the classes that use the remote interface the same way, rather than via the system class loader. Otherwise they won't load (NoClassDefFoundError). You can download the entire client actually, and this is not a bad way to go: see the the RMI 1.1 Specification, 'Bootstrapping the client', for details (if you can find it: try http://java.sun.com/products/archive/jdk/1.1/index.html), and the RMI-USERS archives of about five-six years ago for discussions (see http://archives.java.sun.com/archives/rmi-users.html). The description of this was removed from the 1.2 specification for some reason, and I did encounter problems migrating a 1.1 bootstrap client to 1.2, so beware.

Remote Interface problem using Sun ONE App & web server

HI,
1) I am using an S'less SB. I have local & remote interfaces. I am using the sun one appserver7 & the sun ones's htttp server. By default it doesnt pick up the remote interfaces is it ? How do i make my remote interfaces work ? what are the changes required in config/xml ?
2) However i changed my client code (i.e my action class which is called by the struts action servlet ) to access the localhome rather than the remote home, but then i get java.lang.classcastexception.
pls help !
sanjay

Hi parsuram,
Thanks for the tip. After looking at the sample source code, I did finally figure out the solution - so I'll post it in case anyone else happens to be working with websphere studio has the same issue deploying on sun one.
To access local interface ejb, you must have the following
1. ejb-local-ref tag in the ejb-jar.xml like so underneath the <session> or <entity> tag of the bean which you plan to access the local ejb with.
<ejb-local-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<ejb-ref-type>Session</ejb-ref-type>
<local-home>memory.simple.TestLLocalHome</local-home>
<local>memory.tool.simple.TestLLocal</local>
<ejb-link>TestL</ejb-link>
</ejb-local-ref>
2. similar ejb-ref tag in sun-ejb-jar.xml
<ejb-ref>
<ejb-ref-name>TestL</ejb-ref-name>
<jndi-name>localejbs/module_memory.betaEJB/TestL68640023372300293</jndi-name>
</ejb-ref>
note: sun generates the <jndi-name> and overwrites whatever you put in that tag no matter what you put in there.
3. here is the code to access
Context initial = new InitialContext();
TestLLocalHome tlHome=(TestLLocalHome) Initial.lookup
("TestL");
//the string must match <ejb-ref-name> underneath <ejb-local-ref>
4. note that the jndi name for the local interface bean becomes irrelevant. only the <ejb-ref-name> in the ejb-jar and sun-ejb-jar matter. furthermore, both <ejb-ref-name> must be the same or you won't be able to deploy.
5. This is completely my fault for not checking the "proper" way to access local interfaces. in websphere, they let you get away without the ejb-ref tags and just use the string "local:/TestL"!
-matt

Unable to call exported client methods of EJB session bean remote interface

I am unable to call client methods of a BC4J application module deployed as a Session EJB to Oracle 8i at the client side of my multi-tier application. There is no documentation, and I am unable to understand how I should do it.
A business components project has been created. For instance, its application module is called BestdataModule. A few custom methods have been added to BestdataModuleImpl.java file, for instance:
public void doNothingNoArgs() {
public void doNothingOneArg(String astr) {
public void setCertificate(String userName, String userPassword) {
theCertificate = new Certificate(userName, userPassword);
public String getPermission() {
if (theCertificate != null)
{if (theCertificate.getPermission())
{return("Yes");
else return("No, expired");
else return("No, absent");
theCertificate being a protected class variable and Certificate being a class, etc.
The application module has been tested in the local mode, made remotable to be deployed as EJB session bean, methods to appear at the client side have been selected. The application module has been successfully deployed to Oracle 8.1.7 and tested in the remote mode. A custom library containing BestdataModuleEJBClient.jar and BestDataCommonEJB.jar has been created.
Then I try to create a client basing on Example Oracle8i/EJB Client snippet:
package bestclients;
import java.lang.*;
import java.sql.*;
import java.util.*;
import javax.naming.*;
import oracle.aurora.jndi.sess_iiop.*;
import oracle.jbo.*;
import oracle.jbo.client.remote.ejb.*;
import oracle.jbo.common.remote.*;
import oracle.jbo.common.remote.ejb.*;
import oracle.jdeveloper.html.*;
import bestdata.client.ejb.*;
import bestdata.common.ejb.*;
import bestdata.common.*;
import bestdata.client.ejb.BestdataModuleEJBClient;
public class BestClients extends Object {
static Hashtable env = new Hashtable(10);
public static void main(String[] args) {
String ejbUrl = "sess_iiop://localhost:2481:ORCL/test/TESTER/ejb/bestdata.BestdataModule";
String username = "TESTER";
String password = "TESTER";
Hashtable environment = new Hashtable();
environment.put(javax.naming.Context.URL_PKG_PREFIXES, "oracle.aurora.jndi");
environment.put(Context.SECURITY_PRINCIPAL, username);
environment.put(Context.SECURITY_CREDENTIALS, password);
environment.put(Context.SECURITY_AUTHENTICATION, ServiceCtx.NON_SSL_LOGIN);
BestdataModuleHome homeInterface = null;
try {
Context ic = new InitialContext(environment);
homeInterface = (BestdataModuleHome)ic.lookup(ejbUrl);
catch (ActivationException e) {
System.out.println(e.getMessage());
e.printStackTrace();
System.exit(1);
catch (CommunicationException e) {
System.out.println(e.getMessage());
e.printStackTrace();
System.exit(1);
catch (NamingException e) {
System.out.println(e.getMessage());
e.printStackTrace();
System.exit(1);
try {
System.out.println("Creating a new EJB instance");
RemoteBestdataModule remoteInterface = homeInterface.create();
// Method calls go here!
// e.g.
// System.out.println(remoteInterface.foo());
catch (Exception e) {
System.out.println(e.getMessage());
e.printStackTrace();
It doesnt cause any errors. However, how must I call methods? The public interface RemoteBestdataModule has no such methods:
void doNothingNoArgs();
void doNothingOneArg(java.lang.String astr);
void setCertificate(java.lang.String userName, java.lang.String userPassword);
java.lang.String getPermission();
Instead of that it has the following methods:
oracle.jbo.common.remote.PiggybackReturn doNothingNoArgs(byte[] _pb) throws oracle.jbo.common.remote.ejb.RemoteJboException, java.rmi.RemoteException;
oracle.jbo.common.remote.PiggybackReturn doNothingOneArg(byte[] _pb, java.lang.String astr) throws oracle.jbo.common.remote.ejb.RemoteJboException, java.rmi.RemoteException;
oracle.jbo.common.remote.PiggybackReturn customQueryExec(byte[] _pb, java.lang.String aQuery) throws oracle.jbo.common.remote.ejb.RemoteJboException, java.rmi.RemoteException;
oracle.jbo.common.remote.PiggybackReturn setCertificate(byte[] _pb, java.lang.String userName, java.lang.String userPassword) throws oracle.jbo.common.remote.ejb.RemoteJboException, java.rmi.RemoteException;
oracle.jbo.common.remote.PiggybackReturn getPermission(byte[] _pb) throws oracle.jbo.common.remote.ejb.RemoteJboException, java.rmi.RemoteException;
I cannot call those methods. I can see how they are called in BestdataModuleEJBClient.java file:
public void doNothingNoArgs() throws oracle.jbo.JboException {
try {
oracle.jbo.common.remote.PiggybackReturn _pbRet = mRemoteAM.doNothingNoArgs(getPiggyback());
processPiggyback(_pbRet.mPiggyback);
if (_pbRet.isReturnStreamValid()) {
return;
catch (oracle.jbo.common.remote.ejb.RemoteJboException ex) {
processRemoteJboException(ex);
catch (java.rmi.RemoteException ex) {
processRemoteJboException(ex);
throw new oracle.jbo.JboException("Marshall error");
However, I cannot call getPiggyback() function! It is a protected method, it is available to the class BestdataModuleEJBClient which extends EJBApplicationModuleImpl, but it is unavailable to my class BestClients which extends Object and is intended to extend oracle.jdeveloper.html.WebBeanImpl!
It seems to me that I mustnt use RemoteBestdataModule interface directly. Instead of that I must use the public class BestdataModuleEJBClient that extends EJBApplicationModuleImpl and implements BestdataModule interface. It contains all methods required without additional arguments (see just above). However, how must I create an object of BestdataModuleEJBClient class? That is a puzzle. Besides my custom methods the class has only two methods:
protected bestdata.common.ejb.RemoteBestdataModule mRemoteAM;
/*This is the default constructor (do not remove)*/
public BestdataModuleEJBClient(RemoteApplicationModule remoteAM) {
super(remoteAM);
mRemoteAM = (bestdata.common.ejb.RemoteBestdataModule)remoteAM;
public bestdata.common.ejb.RemoteBestdataModule getRemoteBestdataModule() {
return mRemoteAM;
It looks like the remote application module must already exist! In despair I tried to put down something of the kind at the client side:
RemoteBestdataModule remoteInterface = homeInterface.create();
BestdataModuleEJBClient dm = new BestdataModuleEJBClient(remoteInterface);
dm.doNothingNoArgs();
Of course, it results in an error.
System Output: null
System Error: java.lang.NullPointerException
System Error: oracle.jbo.common.PiggybackOutput oracle.jbo.client.remote.ApplicationModuleImpl.getPiggyForRemovedObjects(oracle.jbo.common.PiggybackOutput) (ApplicationModuleImpl.java:3017)
System Error: byte[] oracle.jbo.client.remote.ApplicationModuleImpl.getPiggyfront(boolea
System Error: n) (ApplicationModuleImpl.java:3059)
System Error: byte[] oracle.jbo.client.remote.ApplicationModuleImpl.getPiggyback() (ApplicationModuleImpl.java:3195)
System Error: void bestdata.client.ejb.BestdataModuleEJBClient.doNothingNoArgs() (BestdataModuleEJBClient.java:33)
System Error: void bes
System Error: tclients.BestClients.main(java.lang.String[]) (BestClients.java:76)
I have studied a lot of documents in vain. I have found only various senseless discourses:
"Use the Application Module Wizard to make the Application Module remotable and export the method. This will generate an interface for HrAppmodule (HrAppmodule.java in the Common package) which contains the signature for the exported method promoteAllEmps(). Then, deploy the Application Module. Once the Application Module has been deployed, you can use the promoteAllEmps() method in your client-side programs. Calls to the promoteAllEmps() method in client-side programs will result in calls to the promote() method in the application tier."
However, I have failed to find a single line of code explaining how it should be called.
Can anybody help me?
Best regards,
Svyatoslav Konovaltsev,
[email protected]
null

Dear Steven,
1. Thank you very much. It seems to me that the problem is solved.
2. "I logged into Metalink but it wants me to put in both a tar number and a country name to see your issue." It was the United Kingdom, neither the US nor Russia if you mean my issue.
I reproduce the text to be written by everyone who encounters the same problem:
package bestclients;
import java.util.Hashtable;
import javax.naming.*;
import oracle.jbo.*;
public class BestdataHelper {
public static ApplicationModule createEJB()
throws ApplicationModuleCreateException {
ApplicationModule applicationModule = null;
try {
Hashtable environment = new Hashtable(8);
environment.put(Context.INITIAL_CONTEXT_FACTORY, JboContext.JBO_CONTEXT_FACTORY);
environment.put(JboContext.DEPLOY_PLATFORM, JboContext.PLATFORM_EJB);
environment.put(Context.SECURITY_PRINCIPAL, "TESTER");
environment.put(Context.SECURITY_CREDENTIALS, "TESTER");
environment.put(JboContext.HOST_NAME, "localhost");
environment.put(JboContext.CONNECTION_PORT, new Integer("2481"));
environment.put(JboContext.ORACLE_SID, "ORCL");
environment.put(JboContext.APPLICATION_PATH, "/test/TESTER/ejb");
Context ic = new InitialContext(environment);
ApplicationModuleHome home = (ApplicationModuleHome)ic.lookup("bestdata.BestdataModule");
applicationModule = home.create();
applicationModule.getTransaction().connect("jdbc:oracle:kprb:@");
applicationModule.setSyncMode(ApplicationModule.SYNC_IMMEDIATE);
catch (NamingException namingException) {
throw new ApplicationModuleCreateException(namingException);
return applicationModule;
package bestclients;
import bestdata.common.*;
import certificate.*;
public class BestClients extends Object {
public static void main(String[] args) {
BestdataModule bestdataModule = (BestdataModule)BestdataHelper.createEJB();
Certificate aCertificate = new Certificate("TESTER", "TESTER");
//calling a custom method!!
bestdataModule.passCertificate(aCertificate);
Thank you very much,
Best regards,
Svyatoslav Konovaltsev.
[email protected]
null

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!!

ClassCastException at Remote object although remote interface is implemented

Hi,
I want to access a remote object via T3 (on WebLogic 10) but I am
getting a ClassCastException in the client. The exception is thrown if
the generic "Remote" object is casted into a concrete remote interface.
The following works ok (client side, get remote object via JNDI):
Hashtable hashTable = new Hashtable();
hashTable.put(Context.INITIAL_CONTEXT_FACTORY,
"weblogic.jndi.WLInitialContextFactory");
hashTable.put(Context.PROVIDER_URL, "t3://localhost:7001);
ic = new InitialContext(hashTable);
Remote r = (Remote) ic.lookup("...jndi bind name...");
But this cast fails:
IMyRemoteIntf i = (IMintRemoteIntf) r;
The ClassCastException has the classname of the class which implements
the remote interface - the lookup should be ok therefore. With
r.getClass().getInterfaces() I have verified that the remote object
actually implements the appropriate interface. I suppose it is a class
loader issue then and added some debug output.
Class loader parent chain of IMyRemoteIntf:
weblogic.utils.classloaders.ChangeAwareClassLoader@1715ee2
-> weblogic.utils.classloaders.GenericClassLoader@123ade0
-> weblogic.utils.classloaders.FilteringClassLoader@1312cf9
-> weblogic.utils.classloaders.GenericClassLoader@159ea8e
-> java.net.URLClassLoader@82d37
-> sun.misc.Launcher$AppClassLoader@e39a3e
-> sun.misc.Launcher$ExtClassLoader@a39137
Class loader parent chain of IMyRemoteIntf as reported by r.getInterfaces():
sun.misc.Launcher$AppClassLoader@e39a3e
-> sun.misc.Launcher$ExtClassLoader@a39137
IMyRemoteIntf is in a jar file in WEB-INF/lib of my web application. I
tried prefer-web-inf-classes = true in weblogic.xml as well as
prefer-application-packages in weblogic-application.xml (with the
respective package of the interface).
Any ideas? I don't know what more I can try. I can access the same
server with this t3 URL just fine from outside of the WebLogic server.
Regards
Werner

I meant an issue about multi-connections. Although the socket is shared by all of the connections, each connection in RMI might correspond to a separated thread, I guess. Since the socket is shared by all rmi clients, the RMI channel would be a blocking connection. I am not sure if the RMI in JDK1.4 or above also use the nonblocking new I/O technique. Thanks.

[wscompile] error: invalid remote interface

I have an interface I want to publish as a web service. This interface extends java.rmi.Remote and each of its methods throws a RemoteException. But when I run wscompile (via ant) against this interface in order to have the wsdl file generated it gives me:
error: invalid remote interface; class manplan.j2ee.service.project.ProjectManager is not an interfacee
I have searched the forum and the internet yet could not find an answer. Any hints are most welcome. Below you will find excerpts from the relevant files.
Cheers,
Olaf
[interface]
public interface ProjectManager extends java.rmi.Remote
 void createProject(final Project project) throws DuplicateProjectException,
 ProjectManagementRuntimeException, RemoteException;
[ant]
<wscompile
 keep="true"
 define="true"
 base="${ws.build.classes.dir}"
 xPrintStackTrace="true"
 verbose="true"
 model="${ws.build.dir}/${ws.model.rpcenc.file}"
 config="${ws.conf.rpcenc.file}">
 <classpath>
 <path refid="ws.class.path"/>
 </classpath>
</wscompile>
[interface-config.xml]
<configuration
xmlns="http://java.sun.com/xml/ns/jax-rpc/ri/config">
<service
name="ProjectManagementService"
targetNamespace="urn:manplan:Services"
typeNamespace="urn:manplan:Types"
packageName="manplan.j2ee.webservice">
<interface name="manplan.j2ee.service.project.ProjectManager"/>
</service>
</configuration>

OK. Found it: unlike Axis' java2wsdl does wscompile not support JavaBeans and so it gets confused by all those Project params and return types. So I guess wscompile is not the right tool for me in this situation?
Cheers,
Olaf

Remote Interface to Java Connector

Similar Messages

Maybe you are looking for