Kbase 20813: SonicMQ 3.0: What Files to Deploy to a JMS Client
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
09/04/2001 |
|
SUMMARY:
This solution applies to Progress SonicMQ Version 3.0 and discusses the SonicMQ jar files necessary to deploy a SonicMQ Java messaging client.
SOLUTION:
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).
- SonicSSL.jar if you are using webclient.jar and you want to use
an SSL protocol.
- jndi.jar if your code uses JMS Administered Objects, or uses
ConnectionFactories to instantiate connections, rather than instantiating connections directly by the use of 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 that use message
selectors, only with point-to-point messaging. SonicMQ
evaluates message selectors on the broker in the
point-to-point domain.
- xml4j.jar if you use XML messages.
- certj.jar, jsafe.jar and sslj.jar if you are using an RSA
implementation of SSL.
- iaik_jce.jar and isik_ssl.jar if you are using an IAIK
implementation of SSL. If you are using a 1.1.x jdk, you also
need jdk11x_update.jar.
These files are installed with Progress SonicMQ in the directory:
<Progress SonicMQ InstallDir>\lib
If you run an applet on a Web server 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">
References To Written Documentation:
SonicMQ Installation and Administration Guide, Chapter 2,
Administration Concepts, "JMS Administered Objects".
Progress Knowledge Base Solution 19675, "SonicMQ: Example for HTML code using with an Applet".
Progress Knowledge Base Solution 20155, "SonicMQ and JMS Administered Objects".
Progress Knowledge Base Solution 19405, "What Files to Deploy to a JMS Client with SonicMQ 2000.x".