Override remote EJB injection mechanism

[nicolyra]

Hello all,

I currently migrate applications from JBOSS-AS5 to JBOSS-EAP-6(.1.1). I want to improve our server-to-server remote EJB call my using @EJB annotation but we have a specific architecture and I don't know what I have to do.

I have two applications (myapp1 ans myapp2), and three servers (srv1, srv2 and srv3).

The application myapp1 is deployed on srv1, myapp2 is deployed on srv2 AND srv3.

Currently, we use a JNDI lookup to allow EJB in myapp1 to call EBJ in myapp2. First, we try to get myapp2 on srv2 and, if we detect exception, we try to connect to srv3.

I implemented my own DeploymentNodeSelector to force srv1 to respect our needs (connect srv3 only if srv2 has error).

Now, I would like to facilitate developers life by using @EJB annotation to inject remote EJB...

However, I don't know :

* What are the interfaces to implement / classes to extend in the way to use our mechanism (connect srv1 to srv2 and immediately to srv3 in case of problem),

* What file to configure in the way to prevent JBoss to use my implementation and not the default.

Thanks in advance for you help!

Nicolas

[wdfink]

You might have a look to the ejb-multi-server quickstart, here I show several methods to invoke remote EJB's.

Feel free to ask here if you have questions

[nicolyra]

Thank you for you response, but I would like to force a JBOSS server to automatically connecting differents servers to call the same EJB.

For example :

On app1.ear is deployed on server1 and contains a jar with this class:

public class MyClass {

@EJB

MyClass02 injectIt;

...

}

MyClass02 implementation is contained in app2.ear deployed on server2 and server3.

I would lile to implements a mechanism wich allows server1 to connect server2 and, in case of problem, automatically contact server3 to inject MyClass02, without any jndi lookup.

[wdfink]

There are two possible solutions.

Use server 2+3 as a cluster or add both servers to the remote-outbound-connection configuration.

You can find how to do that in the MainAppBean and the related server configuration.

You might have a look to the releated document EJB invocations from a remote server instance

[nicolyra]

Indeed I am currently looking for information about clustering which might be the best solution I guess.

Thank you for your help.

I'll close the subject as soon as I'll find the solution.

[nicolyra]

Thank you for your help.

Indeed, cluster is the solution.

Many links which helped me :

http://www.mastertheboss.com/jboss-cluster/jboss-as-7-ha-tutorial/

https://docs.jboss.org/author/display/AS71/Clustered+EJBs

Overview of Client properties - EJB Client Library (AS7+) - Project Documentation Editor

http://blog.akquinet.de/2012/11/09/load-balancing-and-failover-of-remote-ejb-clients-in-eap6-and-jboss-as7/

wildfly/build/src/main/resources/docs/schema/jboss-ejb-client_1_2.xsd at master · wildfly/wildfly · GitHub