Author: Wolf-Dieter Fink
Level: Advanced
Technologies: EJB, EAR
Summary: The ejb-multi-server quickstart shows how to communicate between multiple applications deployed to different servers using an EJB to log the invocation.
Target Product: JBoss EAP
Source: https://github.com/jboss-developer/jboss-eap-quickstarts/
The ejb-multi-server quickstart demonstrates communication between applications deployed to different Red Hat JBoss Enterprise Application Platform servers. Each application is deployed as an EAR and contains a simple EJB3.1 bean. The only function of each bean is to log the invocation.
This example consists of the following Maven projects, each with a shared parent:
| Sub-project | Description |
|---|---|
app-main |
An application that can be called by the client. It can also call the different sub-applications. |
app-one and app-two |
These are simple applications that contain an EJB sub-project to build the ejb.jar file and an EAR sub-project to build the app.ear file. Each application contains only one EJB that logs a statement on a method call and returns the jboss.node.name and credentials. |
app-web |
A simple WAR application. It consists of one Servlet that demonstrates how to invoke EJBs on a different server. |
client |
This project builds the standalone client and executes it. |
The root pom.xml builds each of the subprojects in an appropriate order.
The server configuration is done using CLI batch scripts located in the root of the quickstart folder.
The application this project produces is designed to be run on Red Hat JBoss Enterprise Application Platform 6.1 or later.
All you need to build this project is Java 6.0 (Java SDK 1.6) or later, Maven 3.0 or later.
If you have not yet done so, you must Configure Maven before testing the quickstarts.
It is important to start with a clean version of JBoss EAP before testing this quickstart. Be sure to unzip or install a fresh JBoss EAP instance.
In the following instructions, replace EAP_HOME with the actual path to your JBoss EAP 6 installation. The installation path is described in detail here: Use of EAP_HOME and JBOSS_HOME Variables.
The following users must be added to the ApplicationRealm to run this quickstart. Be sure to use the names and passwords specified in the table as they are required to run this example.
| UserName | Realm | Password | Roles |
|---|---|---|---|
| quickuser | ApplicationRealm | quick-123 | leave blank for none |
| quickuser1 | ApplicationRealm | quick123+ | leave blank for none |
| quickuser2 | ApplicationRealm | quick+123 | leave blank for none |
To add the users, open a command prompt and type the following commands:
For Linux:
EAP_HOME/bin/add-user.sh -a -u quickuser -p quick-123
EAP_HOME/bin/add-user.sh -a -u quickuser1 -p quick123+
EAP_HOME/bin/add-user.sh -a -u quickuser2 -p quick+123
For Windows:
EAP_HOME\bin\add-user.bat -a -u quickuser -p quick-123
EAP_HOME\bin\add-user.bat -a -u quickuser1 -p quick123+
EAP_HOME\bin\add-user.bat -a -u quickuser2 -p quick+123
If you prefer, you can use the add-user utility interactively. For an example of how to use the add-user utility, see the instructions located here: Add an Application User.
You configure the domain server by running JBoss CLI commands. For your convenience, this quickstart batches the commands into a install-domain.cli script provided in the root directory of this quickstart.
Start with a fresh instance of the JBoss EAP as noted above under Start with a Clean JBoss EAP Install.
Be sure you add the required users as specified above under Add the Application Users.
Before you begin, back up your server configuration files.
Backup the following files, replacing EAP_HOME with the path to your server:
EAP_HOME/domain/configuration/domain.xml
EAP_HOME/domain/configuration/host.xml
After you have completed testing and undeployed this quickstart, you can replace these files to restore the server to its original configuration.
Start the JBoss EAP server
Start the server using the following command:
bin/domain.sh
Review the install-domain.cli file in the root of this quickstart directory. This script configures and starts multiple servers needed to run this quickstart.
Open a new command prompt, navigate to the root directory of this quickstart, and run the following command, replacing EAP_HOME with the path to your server:
For Linux: EAP_HOME/bin/jboss-cli.sh --connect --file=install-domain.cli
For Windows: EAP_HOME\bin\jboss-cli.bat --connect --file=install-domain.cli
You should see the following result when you run the script:
The batch executed successfully
{"outcome" => "success"}
There are too many additions to the configuration files to list here. Feel free to compare the domain.xml and host.xml to the backup copies to see the changes made to configure the server to run this quickstart.
NOTE: The following build command assumes you have configured your Maven user settings. If you have not, you must include Maven setting arguments on the command line. See Build and Deploy the Quickstarts for complete instructions and additional options.
Type this command to build the artifacts:
mvn clean install
Open a new command prompt and navigate to the root directory of this quickstart. Deploy the applications using the provided CLI batch script by typing the following command:
For Linux: EAP_HOME/bin/jboss-cli.sh --connect --file=deploy-domain.cli
For Windows: EAP_HOME\bin\jboss-cli.bat --connect --file=deploy-domain.cli
This will deploy the app-*.ear files to different server-groups of the running domain.
NOTE: If ERRORs appear in the server.log when the installing or deploying the quickstart, please stop the domain and restart it. This should ensure further steps run correctly.
This example shows how to invoke an EJB from a remote standalone application. It also demonstrates how to invoke an EJB from a client using a scoped-context rather than a properties file containing the parameters required by the InitialContext.
client/ subdirectory.Type this command to run the application:
mvn exec:java
The client will output the following information provided by the applications:
InvokeAll succeed: MainApp[anonymous]@master:app-main > [ app1[anonymous]@master:app-oneA > app2[quickuser2]@master:app-twoA ; app2[quickuser2]@master:app-twoA ]
This output shows that the MainApp is called with the user anonymous at node master:app-main and the sub-call is proceeded by the master:app-oneA node and master:app-twoA node as quickuser2.
Review the server log files to see the bean invocations on the servers.
To invoke the bean that uses the scoped-client-context, you must pass a property. Type the following command
mvn exec:java -DUseScopedContext=true
The invocation of appTwo throws a java.lang.reflect.InvocationTargetException since the secured method is called and there is no Role for the user defined. You get a BUILD FAILURE and the client outputs the following information:
[ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:java (default-cli) on project jboss-ejb-multi-server-client: An exception occured while executing the Java class. null: InvocationTargetException: JBAS014502: Invocation on method: public abstract java.lang.String org.jboss.as.quickstarts.ejb.multi.server.app.AppTwo.invokeSecured(java.lang.String) of bean: AppTwoBean is not allowed -> [Help 1]
Update the user quickuser1 and quickuser2 and give them one of the Roles AppTwo or Intern.
To update the roles, open a command prompt and type the following commands:
For Linux:
EAP_HOME/bin/add-user.sh -a -u quickuser1 -p quick123+ -g Intern
EAP_HOME/bin/add-user.sh -a -u quickuser2 -p quick+123 -g AppTwo
For Windows:
EAP_HOME\bin\add-user.bat -a -u quickuser1 -p quick123+ -g Intern
EAP_HOME\bin\add-user.bat -a -u quickuser2 -p quick+123 -g AppTwo
If the connection was established before changing the roles it might be necessary to restart the main server, or even the whole domain.
After that the invocation will be successful. The log output of the appTwo servers shows which Role is applied to the user. The output of the client will show you a simple line with the information provided by the different applications:
InvokeAll succeed: MainAppSContext[anonymous]@master:app-main > [ {app1[quickuser1]@master:app-oneA, app1[quickuser1]@master:app-oneA, app1[quickuser2]@master:app-oneB, app1[quickuser2]@master:app-oneA, app1[quickuser2]@master:app-oneA, app1[quickuser2]@master:app-oneB, app1[quickuser2]@master:app-oneA, app1[quickuser2]@master:app-oneA} > appTwo loop(7 time A-B expected){app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB, app2[quickuser1]@master:app-twoA, app2[quickuser2]@master:app-twoB} ]
The resulting output in detail:
MainAppSContext bean on the app-main server on host master with no application security.MainAppSContext bean in app-main calls the AppOne bean in app-one using the scoped-context and establishes the clustered view.
quickuser1quickuser2. This takes some time, but once it takes effect, all calls are load-balanced.app-two are made using two different scoped-context settings and both are used alternately 7 times. This means the servers app-twoA and app-twoB are called alternately seven times each.If it is necessary to invoke the client with a different JBoss version the main class can be invoked by using the following command from the root directory of this quickstart. Replace EAP_HOME with your current installation path. The output should be similar to the previous mvn executions.
java -cp EAP_HOME/bin/client/jboss-client.jar:app-main/ejb/target/jboss-ejb-multi-server-app-main-ejb-client.jar:app-two/ejb/target/jboss-ejb-multi-server-app-two-ejb-client.jar:client/target/jboss-ejb-multi-server-client.jar org.jboss.as.quickstarts.ejb.multi.server.Client
NOTE:
app1 might use app-oneA and app-oneB node due to cluster loadbalancing.appOne/appTwo since security is enabled but the method does not include @Roles. You need to set ‘default-missing-method-permissions-deny-access = false’ for the ejb3 subsystem within the domain profile “ha” and “default” to allow the method invocation. See the install-domain.cli script.The JSF example shows different annotations to inject the EJB. Also how to handle the annotation if different beans implement the same interface and therefore the container is not able to decide which bean needs to be injected without additional informations.
NOTE :
MainAppSContext you need to update the user quickuser1 and quickuser2 and give them one of the Roles AppTwo or Intern.An example how to access EJB’s from a separate instance which only contains a web application.
NOTE : A new feature in EAP 6.1 or later will deny the invocation of unsecured methods of appOne/appTwo since security is enabled but the method does not include @Roles. You need to set ‘default-missing-method-permissions-deny-access = false’ for the ejb3 subsystem within the domain profile “ha” and “default” to allow the method invocation. See the install-domain.cli script.
When you are finished testing, type this command to undeploy the archive:
For Linux: EAP_HOME/bin/jboss-cli.sh --connect --file=undeploy-domain.cli
For Windows: EAP_HOME\bin\jboss-cli.bat --connect --file=undeploy-domain.cli
You can remove the domain configuration by manually restoring the back-up copies the configuration files or by running the JBoss CLI Script.
EAP_HOME/domain/configuration/domain.xml and EAP_HOME/domain/configuration/host.xml files with the back-up copies of the files. Be sure to replace EAP_HOME with the path to your server.Note: This script returns the server to a default configuration and the result may not match the server configuration prior to testing this quickstart. If you were not running with the default configuration before testing this quickstart, you should follow the intructions above to manually restore the configuration to its previous state.
Start the JBoss EAP server by typing the following:
For Linux: EAP_HOME/bin/domain.sh
For Windows: EAP_HOME\bin\domain.bat
Open a new command prompt, navigate to the root directory of this quickstart, and run the following command, replacing EAP_HOME with the path to your server.
For Linux: EAP_HOME/bin/jboss-cli.sh --connect --file=remove-configuration.cli
For Windows: EAP_HOME\bin\jboss-cli.bat --connect --file=remove-configuration.cli
This script removes the server configuration that was done by the install-domain.cli script. You should see the following result following the script commands:
The batch executed successfully.
EJB Client (ejb-client) currently has limited support in the Eclipse Web Tools Platform (WTP). For that reason, this quickstart is not supported in Red Hat JBoss Developer Studio.
If you want to debug the source code of any library in the project, run the following command to pull the source into your local repository. The IDE should then detect it.
mvn dependency:sources