Sun Java System logo     
JAXM Messaging Provider Admin Sample Application



JAXM Messaging Provider Admin Sample Application


This document describes how to utilize the JAXM Messaging Provider Admin Sample application in conjunction with the Sun Java (tm) System Application Server version 7.

This application document contains the following sections:



Overview

The Provider Administration tool is a convenient means of configuring a messaging provider. A messaging provider, a third party service, handles the behind-the-scenes details of the routing and transmission of JAXM messages. The JAXM tutorial gives more information about messaging providers in the section Messaging Providers.

The Provider Administration tool is normally used by System Administrators, but others may use it as well. Exploring this tool gives you more of an idea of what a messaging provider needs to know. For example, a messaging provider maintains a list of the endpoints to which you can send messages. You can add a new endpoint to this list using the Provider Administration tool. If a message is not delivered successfully on the first try, a messaging provider will continue attempting to deliver it. You can specify the number of times the messaging provider should attempt delivery by supplying a retry limit. Setting this limit is another thing you can do with the Provider Administration tool.

The following lists the ways you can use the tool to set a messaging provider's properties.

  • To add, modify, or delete an endpoint
  • To change the number of retries (the number of times the provider will try to send a message)
  • To change the retry interval (the amount of time the provider will wait before trying to send a message again)
  • To change the directory where the provider logs messages
  • To set the number of messages per log file


IMPORTANT: This admin sample application requires a messaging provider in order to run successfully. The JAXM Messaging Provider Sample application is required to be deployed prior to deploying the JAXM Messaging Provider Admin Sample application. To deploy the messaging provider, see Messaging Provider Sample Application before proceeding further.

It must be emphasized that the Messaging Provider Sample application and Messaging Provider Admin Sample application is provided for sample purposes only. It is not production quality and not supported in any way. These were originally part of the Java Web Services Developer Pack and provided here as a convenience.


For more information on JAXM, go to http://java.sun.com/xml/jaxm/index.html.


Deploying the Admin Sample Application



To deploy the application, do the following:

Execute the command asant deploy under <install_root>/samples/webservices/jaxm/jaxm-provideradmin/src

This will deploy the jaxm-provideradmin.war file located under <install_root>/samples/webservices/jaxm/jaxm-provideradmin/


Note You must run asant undeploy before redeploying this sample. This will ensure that all modules are undeployed and the resources are disabled.




Verifying Deployment

As an optional step, you can use the Sun Java (tm) System Application Server Administration Tool to verify that the application has been registered. Otherwise, proceed directly to Running the Admin Sample Application.

To verify the registration of the application, do the following:

Execute the command asadmin list-components to look at applications deployed with a server instance. For example:

<install_root>/bin/asadmin list-components -u <username> -w <password> -H <host> -p <port> <server instance name>

You will see jaxm-provideradmin listed.


Running the Admin Sample Application



You can run the application through the following URL:

http://<hostname>:<port>/jaxm-provideradmin


Troubleshooting



  • If you encounter problems when running the application, review the log files at <install-root>/domains/domain1/<server-instance>/logs/server.log to learn what exactly went wrong.

Some Known Issues

  • The sample can not be deployed from the application server administration GUI, if Precompile JSPs option is selected. Solution is, try deploying the application without Precompile JSPs, or deploy using asant.

  • The sample can not be deployed using asadmin with option --precompilejsp=true. Solution is, try deploying the application without the option --precompilejsp=true, or deploy using asant.


Copyright © 2002 Sun Microsystems, Inc. All rights reserved.

Last Updated July 12, 2002