To Build, Package, Deploy, and Run the sendremote Modules Using NetBeans IDE

1. To build the replybean module, follow these steps:

   1. In NetBeans IDE, select File->Open Project.

   2. In the Open Project dialog, navigate to:

      tut-install/examples/jms/sendremote/

   3. Select the replybean folder.

   4. Select the Open as Main Project check box.

   5. Click Open Project.

   6. In the Projects tab, right-click the replybean project and select Build.

      This command creates a JAR file that contains the bean class file.

2. To build the multiclient module, follow these steps:

   1. Select File->Open Project.

   2. Select the multiclient folder.

   3. Select the Open as Main Project check box.

   4. Click Open Project.

   5. In the Projects tab, right-click the multiclient project and select Build.

      This command creates a JAR file that contains the client class file and a manifest file.

3. To deploy the multiclient module on the local server, follow these steps:

   1. Right-click the multiclient project and select Properties.

   2. Select Run from the Categories tree.

   3. From the Server list, select GlassFish v3 Domain (the local server).

   4. Click OK.

   5. Right-click the multiclient project and select Deploy.

      You can use the Services tab to verify that multiclient is deployed as an App Client Module on the local server.

4. To deploy the replybean module on the local and remote servers, follow these steps:

   1. Right-click the replybean project and select Properties.

   2. Select Run from the Categories tree.

   3. From the Server list, select GlassFish v3 Domain (the local server).

   4. Click OK.

   5. Right-click the replybean project and select Deploy.

   6. Right-click the replybean project again and select Properties.

   7. Select Run from the Categories tree.

   8. From the Server list, select GlassFish v3 (2) (the remote server).

   9. Click OK.

   10. Right-click the replybean project and select Deploy.

       You can use the Services tab to verify that replybean is deployed as an EJB Module on both servers.

5. To run the application client, right-click the multiclient project and select Run Project.

   This command returns a JAR file named multiclientClient.jar and then executes it.

   On the local system, the output of the appclient command looks something like this:

   running application client container. Sent message: text: id=1 to local app server Sent message: text: id=2 to remote app server ReplyListener: Received message: id=1, text=ReplyMsgBean processed message: text: id=1 to local app server Sent message: text: id=3 to local app server ReplyListener: Received message: id=3, text=ReplyMsgBean processed message: text: id=3 to local app server ReplyListener: Received message: id=2, text=ReplyMsgBean processed message: text: id=2 to remote app server Sent message: text: id=4 to remote app server ReplyListener: Received message: id=4, text=ReplyMsgBean processed message: text: id=4 to remote app server Sent message: text: id=5 to local app server ReplyListener: Received message: id=5, text=ReplyMsgBean processed message: text: id=5 to local app server Sent message: text: id=6 to remote app server ReplyListener: Received message: id=6, text=ReplyMsgBean processed message: text: id=6 to remote app server Sent message: text: id=7 to local app server ReplyListener: Received message: id=7, text=ReplyMsgBean processed message: text: id=7 to local app server Sent message: text: id=8 to remote app server ReplyListener: Received message: id=8, text=ReplyMsgBean processed message: text: id=8 to remote app server Sent message: text: id=9 to local app server ReplyListener: Received message: id=9, text=ReplyMsgBean processed message: text: id=9 to local app server Sent message: text: id=10 to remote app server ReplyListener: Received message: id=10, text=ReplyMsgBean processed message: text: id=10 to remote app server Waiting for 0 message(s) from local app server Waiting for 0 message(s) from remote app server Finished Closing connection 1 Closing connection 2

   On the local system, where the message-driven bean receives the odd-numbered messages, the output in the server log looks like this (wrapped in logging information):

   ReplyMsgBean: Received message: text: id=1 to local app server ReplyMsgBean: Received message: text: id=3 to local app server ReplyMsgBean: Received message: text: id=5 to local app server ReplyMsgBean: Received message: text: id=7 to local app server ReplyMsgBean: Received message: text: id=9 to local app server

   On the remote system, where the bean receives the even-numbered messages, the output in the server log looks like this (wrapped in logging information):

   ReplyMsgBean: Received message: text: id=2 to remote app server ReplyMsgBean: Received message: text: id=4 to remote app server ReplyMsgBean: Received message: text: id=6 to remote app server ReplyMsgBean: Received message: text: id=8 to remote app server ReplyMsgBean: Received message: text: id=10 to remote app server