Kbase 43056: Problem setting up auto configuring scripts for SonicXQ
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Solution ID: P13056
FACT(s) (Environment):
SonicXQ 1.5
SYMPTOM(s):
Problem setting up auto configuring scripts for SonicXQ
Via XQAdmin tool imported Endpoints not visible within SonicXQ Explorer
CAUSE:
The customer's endpoint's xml did have <endpoint ... type_ref="SonicMQ
instead of type_ref="JMSType".
The reason it does not show up in Explorer, is that explorer shows
Endpoints in a tree and needs the "parent" (which exists as JMSType, not "SonicMQ
Endpoint")
Don't confuse the display name (SonicMQ Endpoint), with the internal
name (JMSType).
The XQAdmin tool is an advanced feature. It does not do referential
integrity on the import. This allows you to
enter an Endpoint before you've entered the EndpointType, or a
connection before the ConnectionType. The
disadvantage to this is that you can use XQAdmin to leave yourself in a
"partial" state that Explorer can't display.
FIX:
The solution is to
a) create the types etc in Explorer
b) use XQAdmin to export the .xml you want
c) use XQAdmin in another D.S. to import
Do not edit the XML by hand as that may leave problems.