Kbase 19405: What Files to Deploy to a JMS Client with SonicMQ 2000(x)
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
21/08/2003 |
|
Status: Technically Reviewed
GOAL:
Which SonicMQ jar files are necessary to deploy a Java messaging client.
FACT(s) (Environment):
SonicMQ 2000(x)
FIX:
Deployment of Java messaging applications developed with SonicMQ must be done manually. In addition to your application code, the following files must be installed on the messaging client:
- client.jar (or webclient.jar if you are using HTTP tunneling)
- jndi.jar if your code uses JMS Administered Objects, or uses ConnectionFactories to instantiate connections, rather than instantiating connections directly by using constructors.
- gnu-regexp-1.0.6.jar if you use Pub/Sub messaging, and use message selectors in your subscriptions. This file need not be deployed to clients using message selectors only with Point-to-Point messaging, since SonicMQ evaluates message selectors on the broker in the Point-to-Point domain.
- xml4j.jar if you use XML messages.
These files are installed with Progress SonicMQ, and are located in the directory:
Progress SonicMQ InstallDir\lib
If you run an applet on a webserver to do your messaging, the necessary jar files from the list above must be deployed on the web server, and specified by the ARCHIVE attribute within your APPLET tag:
APPLET ARCHIVE="client.jar,jndi.jar,gnu-regexp-1.0.6.jar, xml4j.jar">