| Author |
Message
|
| jgooch |
 Posted: Thu Sep 26, 2002 12:45 am Post subject: Installing C plug-ins. |
 |
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
Hi,
We're working on MQSIv2.0.1.
We're trying to create a plug-in node to allow us to do XSL transforms (to tide us over until our 2.1 upgrade project comes on line next year).
I've created the .wdp file, the XML definition file and the properties file but when I put them into the Control Centre, I do not get the option to check in or lock the node. When I tested this procedure with the sample plug-in, it worked as per the redbook and the programming guide.
The result is that although I can add my node to flows, I cannot then check them in (Control Centre throws a dialogue box with the error BIP1107S NullPointerException).
Any ideas?
Thanks,
J. |
|
| Back to top |
|
 |
| kirani |
| Posted: Thu Sep 26, 2002 3:25 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
J,
Could you post the complete error message (method name and exception text) here?
After this error do you still see files in <wmqi_home>\repository\private\<hostname>\<qmname>\MessageProcessingNodeType directory? Is it possible to post the contents of your .wdp file here?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jgooch |
| Posted: Fri Sep 27, 2002 12:40 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
The error text is:-
________________
BIP1107S: Unexpected exception in Configuration Manager MQProcessor class listen method; exception text: 'java.lang.NullPointerException'.
An exception was caught by the Configuration Manager MQProcessor class listen method. The exception text is: java.lang.NullPointerException. The Configuration Manager will continue processing if it is safe to do so.
Retry the operation if possible. If the exception still occurs, turn on Configuration Manager tracing to capture details of the exception, and contact your IBM support centre.
________________
The files do disappear from the directory. I've put them back in to re-create the error and I noticed that a couple of other files appeared (called 4a161ec3-ef00-0000-0080-8512f0654a19.wdp and the same without the extension).
________________
My wdp file (comAxaXSL.wdp) contains:-
<?xml version="1.0"?>
<properties xmlns:D="DAV:">
<D:creationdate>1999-10-06T12:54:19-04:00</D:creationdate>
<D:displayname>repository\private\MessageProcessingNodeType\comAxaXSL</D:displayname>
<D:getcontenttype>text/plain</D:getcontenttype>
<D:xmi.label>XSLTransform</D:xmi.label>
<D:getcontenttype>text/plain</D:getcontenttype>
<D:lockdiscovery xmlns:D="DAV:"/>
<D:getcontenttype>text/plain</D:getcontenttype>
<D:icon>images/XSLTransform.gif</D:icon>
</properties>
I did find one error (I had left the suffix "...Node" on the end of the display name). I've fixed this but still get the same error.
________________
The XML definition file is:-
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE MessageProcessingNodeType SYSTEM "C:\Program Files\IBM MQSeries Integrator 2.0.1\Tool\mqsi.dtd">
<MessageProcessingNodeType scaleableIcon="" longDescription="longDescription" icon="images/XSLTransform.gif" versionCreator="" package="com.isv" shortDescription="shortDescription" version="" creationTimestamp="" isPrimitive="true" creator="" versionTimestamp="" xmi.uuid="comAxaXSL" xmi.label="XSLTransform" collectionPath="">
<Attribute xmi.label="nodeXSLFile" type="String" value="" xmi.uuid="" valueMandatory="true" encoded="false"/>
<OutTerminal longDescription="" icon="images/OutTerminal.gif" versionCreator="" shortDescription="" creationTimestamp="" creator="" y="0" x="0" versionTimestamp="" xmi.label="failure">
<OutTerminalTypeRef xmi.label="OutTerminalType" type="OutTerminalType" icon="images/OutTerminal.gif" title="OutTerminal" refType="OutTerminalType" href="OutTerminalType/OutTerminalType" xml:link="simple"/>
</OutTerminal>
<OutTerminal longDescription="" icon="images/OutTerminal.gif" versionCreator="" shortDescription="" creationTimestamp="" creator="" y="0" x="0" versionTimestamp="" xmi.label="out">
<OutTerminalTypeRef xmi.label="OutTerminalType" type="OutTerminalType" icon="images/OutTerminal.gif" title="OutTerminal" refType="OutTerminalType" href="OutTerminalType/OutTerminalType" xml:link="simple"/>
</OutTerminal>
<InTerminal longDescription="" icon="images/InTerminal.gif" versionCreator="" shortDescription="" creationTimestamp="" creator="" y="0" x="0" versionTimestamp="" xmi.uuid="" xmi.label="in">
<InTerminalTypeRef xmi.label="InTerminalType" type="InTerminalType" icon="images/InTerminal.gif" title="InTerminal" refType="InTerminalType" href="InTerminalType/InTerminalType" xml:link="simple"/>
</InTerminal>
</MessageProcessingNodeType>
________________
Thanks for the help! |
|
| Back to top |
|
|
| jgooch |
| Posted: Fri Sep 27, 2002 12:49 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
As an addendum to my lengthy missive above:-
The files do stay in the repository directory (if they are not there, you cannot see the node in the Add To Workspace list). However, they disappear when you delete the node from the Control Centre.
Sorry for the confusion... |
|
| Back to top |
|
|
| jgooch |
| Posted: Mon Sep 30, 2002 1:49 am Post subject: Calling Kiran! |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
...bump...
Kiran - if you can spot any mistakes or suggest any different courses of action, I'll be your friend for life  |
|
| Back to top |
|
|
| kirani |
| Posted: Mon Sep 30, 2002 7:05 am Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
jgooch,
I am sorry .. I forgot about your post!
I looked at your files and found one thing different. In your XML Interface definition file, you don't need complete path in <!DOCTYPE ..> tag for mqsi.dtd. After removing that line and I was able to check-in the plug-in node into my Configuration manager.
Try deleting the node from your configuration repository first and then modify your XML Interface defn file. Copy these files into proper directories and select Add To Workspace->Message Flows. Check-in the plug-in node and see if you get this error again.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| jgooch |
| Posted: Mon Sep 30, 2002 7:36 am Post subject: |
|
|
Acolyte
Joined: 29 May 2002
Posts: 63
Location: UK
|
Kiran,
Thanks and I am now your friend for life. If you've seen the way that Azeem follows Robin Of Locksley around in "Robin Hood, Prince Of Thieves", you'll have some idea of what this entails 
I had updated the DTD path so that I could check my validity in XMLSpy. I hadn't thought to change it back.
Well spotted,
J. |
|
| Back to top |
|
|
|
|
