Deployment and Configuration Guide 
A standalone client (one that does not use a messaging provider) requires no
deployment or configuration. This is true because it simply sends a request-response
message to an endpoint supplied to the SOAPConnection method
call. A client that uses a messaging provider, on the other
hand, needs to supply certain information about itself and its messaging provider
before it can send messages. This configuration is done using XML files, or
if a tool is available, configuration can be done with the tool.
This document briefly explains
- How to configure a JAXM client running in a servlet container
- How to configure a messaging provider
Deploying a Client
A JAXM client application consists of one or more web components written
in the JavaTM programming language (most
likely servlets), that send and receive messages. Since all web components
exist as part of a web application archive (WAR), a JAXM client application
is a web application. See the JAXM tutorial for instructions on running the
sample applications provided with the JAXM RI.
Client Configuration
To configure the client, you supply an XML file such as the sample configuration
file client.xml. This file, which must conform to the
DTD jaxm-client.dtd,
contains the following information about the client:
-
Endpoint: A string identifying the client
-
A CallbackURL, which tells the provider how it can contact the client
to deliver pending messages. Note that the provider will keep trying to deliver
messages until the delivery is successful or the retry limit is reached.
-
Provider's URI and its URL. This URI is what is used to look up
the ProviderConnectionFactory object when a JNDI service provider
is used. The URI is what goes in the SOAP header elements as the actor URI.
When a deployment tool is available, it may be used in place of the
client.xml file to supply client configuration information.
Provider Configuration
The JAXM RI includes a ProviderAdmin tool that makes it easy to configure the
messaging provider. See the JAXM tutorial for instructions on starting the
ProviderAdmin tool.
If you do not use the ProviderAdmin tool, you need to
supply an XML file such as the sample provider configuration file
provider.xml. This file, which must conform to the
DTD jaxm-provider.dtd, contains the
following information:
-
The internet transport used. For now, the JAXM RI supports only HTTP.
-
A set of endpoint definitions. Each endpoint definition maps a URI to a
URL.
-
Information on where messages are to be logged
-
Directory name for the message log files
-
RecordsPerFile, which indicates how many message records are saved in
one file
-
Error handling information.
-
MaxRetries, which indicates how many times the provider should try to
deliver a message before giving up
-
RetryInterval, which is the time interval in milliseconds between retries