Kbase P49026: Entry pointing to SonicMQ jar files is left in registry afte
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
20/10/2003 |
|
Status: Unverified
FACT(s) (Environment):
OpenEdge 10.0A
FACT(s) (Environment):
Windows NT 32 Intel/Windows 2000
SYMPTOM(s):
Entry pointing to SonicMQ jar files is left in registry after installation of OpenEdge
OpenEdge Application Server Enterprise license has been installed
CAUSE:
This is a known issue
FIX:
In order to modify CLASSPATH for SonicMQ Adapter, please remove HKEY_LOCAL_MACHINE\SOFTWARE\PSC\PROGRESS\10.0A1B\JAVA\PROGRESS entry from registry and modify %DLC%/properties/AdminServerPlugins.properties instead as per
RN#: 100A-10101
===============
When using the the Adapter for SonicMQ, the CLASSPATH for the adapter must include a reference to the SonicMQ client files. In previous releases, this was done by modifing the PROGRESSCP variable in the registry on NT or in $DLC/bin/java_env on UNIX systems. Starting with version 10.0A, the definition of CLASSPATH is no longer defined in these locations. It is now defined in the file
$DLC/properties/AdminServerPlugins.properties and is specific to each
AdminServer plugin.
The definition of CLASSPATH for the SonicMQ Adapter in this properties file contains "$DLC/java/sonicMQ/lib/sonic_Client.jar" by default. This is the same default used in previous releases. If the SonicMQ client files are in a different location, or if additional SonicMQ Client files need to be specified in the CLASSPATH, this definition will need to be updated. This file is a text file and may be changed using any normal text editor.
The value of CLASSPATH used for the SonicMQ Adapter is defined by the "pluginclasspath" property in the [PluginPolicy.Progress.SonicMQ] group. The definition of this property must contain a reference to the SonicMQ client files and a reference to $DLC/java/progress.jar at a minimum for the SonicMQ Adapter to function.