Java Reference
In-Depth Information
Creating Resources for the
sendremote
Example
This example uses the connection factory named
jms/ConnectionFactory
and the
topic named
jms/Topic
. These objects must exist on both the local and the remote serv-
ers.
This example uses an additional connection factory,
jms/JupiterConnec-
tionFactory
, which communicates with the remote system; you created it in “
To
Create Administered Objects for Multiple Systems
” on page
400
.
This connection factory
must exist on the local server.
The
build.xml
file for the
multiclient
module contains targets you can use to cre-
ate these resources if you deleted them previously.
To create the resource needed only on the local system, use the following command:
ant create-remote-factory -Dsys=
remote-system-name
The other resources will be created when you deploy the application.
To Enable Deployment on the Remote System
GlassFish Server by default does not allow deployment from a remote system. You must
create a password for the administrator, then execute an
asadmin
command on the re-
mote system to enable deployment of the message-driven bean on that system.
1. On
jupiter
, start the Administration Console by opening a browser at
ht-
tp://localhost:4848/.
2. In the navigation tree, expand the Configurations node, then expand the
server-config node.
3. Expand the Security node.
4. Expand the Realms node.
5. Select the admin-realm node.
6. On the Edit Realm page, click Manage Users.
7. In the File Users table, click admin in the User ID column.
8. On the Edit File Realm Users page, type a password (for example, jmsadmin)
in the New Password and Confirm New Password fields, then click Save.
9. From a command prompt on the remote system (
jupiter
), run the following
command:
asadmin enable-secure-admin
