| Author |
Message
|
| Empeterson |
 Posted: Mon Apr 14, 2003 10:17 am Post subject: Support Pac ia0g-XML Transformation Node |
 |
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
Hello,
Is anyone using this node successfully? I appear to have it installed successfully (ie, it exists in my control center and I can add it to flows), however, I cant seem to get a message through the output terminal, everything goes to the fail terminal. The stylesheet itself seems fine, as I have no problems running it with such programs as Cooktop or XML Spy. The stylesheet is located in E:\ of the broker machine (Win 2K), and the name is ACORD2CWS.xsl. In the node properties, I have Stylesheet Name set to ACORD2CWS.xsl and the Stylesheet Directory set to E:\, taking all other default values. Am I doing something wrong? This isnt rocket science I know, but I have a feeling I am missing something. |
|
| Back to top |
|
 |
| lillo |
| Posted: Mon Apr 14, 2003 10:38 pm Post subject: |
|
|
Master
Joined: 11 Sep 2001
Posts: 224
|
I was trying a few months ago to use the supportpac without any success. Everything in my stylesheet was correct and we got the same issue. I did an user trace and found some problems about the XML parser.
So, I would suggest you to use the user trace to see the problem in detail. Anyway, this supportpac is supported by IBM so you can open a PMR.
I hope this help you.
_________________
Lillo
IBM Certified Specialist - WebSphere MQ |
|
| Back to top |
|
|
| jby |
| Posted: Thu Apr 17, 2003 2:55 am Post subject: |
|
|
Newbie
Joined: 24 Jan 2003
Posts: 9
Location: Netherlands
|
I've found SupportPac IA0G very useful and we use it on AIX,W2K, and NT4 brokers. It functions as documented ( much to our safisfaction and resultant shorter development time).
My only problem with it is an occasional 'OutOfMemory' exception when transforming large (+/- 16MB) messages on AIX (at least).
If anyone has solved such a situation, or has ideas on how to adjust the resources available to the JVM, I would be interested. (I know this can be done with java -ms/-mx/-ss etc. command-line options, but have yet to test if more resources become available to the node).
If required, I can create and supply a small example of our usage of the XSL Transorm node in a flow. |
|
| Back to top |
|
|
| Empeterson |
| Posted: Thu Apr 17, 2003 9:17 am Post subject: |
|
|
Centurion
Joined: 14 Apr 2003
Posts: 125
Location: Foxboro, MA
|
I have now been able to use this node successfully. After submitting a PM with IBM, the problem was determined to be two-fold:
1) There was some in-line javascript code with the stylesheet which is apparently a no-no.
2) You must have the Message Domain on your input node set to BLOB. The transform node itself will handle all parsing of the input xml.
Thanks for the responses. |
|
| Back to top |
|
|
| wmqiguy |
| Posted: Sat Apr 19, 2003 6:19 am Post subject: |
|
|
Centurion
Joined: 09 Oct 2002
Posts: 145
Location: Florida
|
A bit off subject, but I noticed that you are using 16MB, jby. What kind of performance are you seeing. Is your processing measured in seconds, minutes, or hours?
Thanks. |
|
| Back to top |
|
|
| Ian |
| Posted: Wed Apr 30, 2003 2:34 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
Hi,
| Quote: |
1) There was some in-line javascript code with the stylesheet which is apparently a no-no.
|
-> This is incorrect.
-> SupportPac IA0G and the associated eXMLT engine does support inline JavaScript in the StyleSheet.
-> This is more likely to have been caused by an error within your JavaScript.
_________________
Regards, Ian |
|
| Back to top |
|
|
| chuanchen |
| Posted: Fri May 23, 2003 9:39 am Post subject: SupportPac IA0G embeded style sheet does not working |
|
|
Novice
Joined: 11 Jul 2001
Posts: 11
|
Hi,
I tried successfully supportpac IA0G with MQSI Node Attribute Selection Priority setting stylesheet name and directory,But when
I configure xml embeded selection with like <?xml-stylesheet type="text/xsl"href="foo.xsl"?> as mentioned on the doc, I got
stylesheet not found on the event viewer.
QM_IDF4_BROKER.default ) Java plug-in node error: [com.ibm.xsl.mqsi.XMLTransformResources:Error_Transform]Error: Could not transform data:
com.ibm.xsl.exmlt.TransformRequestException: Stylesheet not found
Stylesheet not found
com.ibm.xsl.exmlt.TransformRequestException: Stylesheet not found
at com.ibm.xsl.exmlt.EnhancedXMLTransform.transformDocument(EnhancedXMLTransform.java:757)
at com.ibm.xsl.mqsi.XMLTransformData.transformData(XMLTransformData.java:520)
at com.ibm.xsl.mqsi.XMLTransformNode.evaluate(XMLTransformNode.java:790)
.
Error message generated by user Java plug-in node.
Contact the node provider for further details.
What is the actual directory foo.xsl has to be in the broker?
Please shed some light anyone has success with embeded stylesheet
in the XML data file.
Thanks!
--Chuan Chen |
|
| Back to top |
|
|
| Ian |
| Posted: Tue May 27, 2003 2:28 am Post subject: |
|
|
Disciple
Joined: 22 Nov 2002
Posts: 152
Location: London, UK
|
Hi,
| Quote: |
Determines what XSL stylesheet to use, where the stylesheet is located and then
retrieves the stylesheet. You can specify the location of the stylesheet by:
1. Defining the name of the stylesheet file and its location on the stylesheet
panel of the properties of your node, inside the MQSI Control Center.
Specifying stylesheet information as one of the properties of the node assures
that the node will always apply the same stylesheet to all the XML data it
receives.
2. Defining the name of the stylesheet file and it location as part of the XML
data that is contained in the MQSI message. Specifying stylesheet information
as part of the XML data allows the node to apply different stylesheets to the
XML data it receives.
3. Defining the name of the stylesheet file and its location in the
LocalEnvironment folder (data structure) contained in the MQSI message.
Specifying stylesheet information as part of the LocalEnvironment allows the
node to apply different stylesheets to the XML data it receives.
|
The IA0G Support Pac indicates there are 3 mechanisms defining the location of the stylesheet.
You have indicated that you have defined the location on the node (node attribute) but have then
also used another mechanism by embedding the stylesheet name in the file.
Choose which mechanism you wish to use and then make it consistant across what you are doing.
_________________
Regards, Ian |
|
| Back to top |
|
|
| chuanchen |
| Posted: Tue May 27, 2003 5:49 am Post subject: SupportPac IA0G |
|
|
Novice
Joined: 11 Jul 2001
Posts: 11
|
Thanks ian.
I guess I need to rephrase my question. I want to test out the following case without setting on the property panel.
2. Defining the name of the stylesheet file and it location as part of the XML
data that is contained in the MQSI message. Specifying stylesheet information
as part of the XML data allows the node to apply different stylesheets to the
XML data it receives.
my xml data contain <?xml-stylesheet type="text/xsl"href="foo.xsl"?>
It complain about stylesheet not found.
Did you have any success on stylesheet embeded on xml data case?
Thanks again,
--Chuan |
|
| Back to top |
|
|
|
|
