| Author |
Message
|
| mbtc |
 Posted: Mon Oct 07, 2013 6:39 am Post subject: Message broker installation depends on Broker Toolkit |
 |
|
Newbie
Joined: 04 Oct 2013
Posts: 5
|
Hello,
The Message broker installation seems to depend on the Broker Toolkit being installed when using Mapping Nodes.
Is this a bug?
Broker installation : 8.0.0.2 (not toolkit)
Activity:
1) Message flow contains IBM Mapping Node
2) Flow creating using Broker Toolkit 8.0.0.2
3) Try to deploy flow to broker
Error:
| Quote: |
BIP4366E: Unable to create Java node 'GetApplicantId#FCMComposite_1_1' of type 'ComIbmMSLMappingNode'.
An exception has occurred during the creation of the Java node: java.lang.NoClassDefFoundError: com.ibm.xml.xci.type.SchemaResolver |
After upgrading the Broker Toolkit on the server, the message flow deploys successfully.
A search for the class in jar files returns the following locations:
(note no mqsi/path variable seems to ever include SDPShared)
Before applying toolkit FP8002:
/opt/IBM/SDPShared/plugins/com.ibm.etools.mft.map.xml_8.0.0.v20111129_1446/lib/xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.msl.mapping.xml_7.6.100.v20111128_1400/lib_xltxe/xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.xtt.xltxej2_1.0.0.v20100315_2235/lib/com.ibm.xml.jar
After applying toolkit FP8002:
/opt/IBM/SDPShared/plugins/com.ibm.etools.mft.map.xml_8.0.100.v20120808-1331/lib/xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.msl.mapping.xml_7.6.100.v20111128_1400/lib_xltxe/xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.xtt.xltxej2_1.0.0.v20100315_2235/lib/com.ibm.xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.etools.mft.map.xml_8.0.0.v20111129_1446/lib/xml.jar
/opt/IBM/SDPShared/plugins/com.ibm.msl.mapping.xml_8.0.300.v20130318-1011/lib_xltxe/com.ibm.xml.jar
. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Mon Oct 07, 2013 7:36 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
SDPShared is, oddly enough, a Toolkit only directory.
Nothing in the Toolkit install directories will ever be referenced from runtime.
You've done something else to fix the problem you had. nothing you've said shows what that was. Nothing you've said you have done would have caused the problem in the first place, nor fix it. |
|
| Back to top |
|
|
| mbtc |
| Posted: Wed Oct 09, 2013 1:36 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2013
Posts: 5
|
Hello, I am a bit upset by your answer mqjeff, as you are basically saying I am not telling the truth.
All I can recount is the order of events:
1) We had an installation of message broker 8.0.0.0
2) We applied FP 8.0.0.2
3) We have a message flow containing a Mapping Node created in Toolkit 8.0.0.2
4) It failed to deploy with above error.
5) We applied the Toolkit upgrade to the server.
6) The flow was successfully deployed.
The command I used to search the file system for Jars is:
| Code: |
| find /opt/ -name *.jar -exec grep -Hls com.ibm.xml.xci.type.SchemaResolver {} \; |
. |
|
| Back to top |
|
|
| dogorsy |
| Posted: Wed Oct 09, 2013 1:44 am Post subject: |
|
|
Knight
Joined: 13 Mar 2013
Posts: 553
Location: Home Office
|
You may be upset, but what mqjeff is telling you is true.
Now, if you would care to explain your problem properly, then people trying to help you would have a better understanding.
You said you had 8.0.0.0 and then upgraded to 8.0.0.2 and also you updated the toolkit in the server, etc.
From all that , it is unclear to me what the environments are:
Please tell us:
1- in what environment is the WMB "runtime" is installed and the sequence of events.
2- ditto for toolkit.
3- after upgrading the toolkit, and before deploying, did you rebuild the bar file, or you don't have a barfile and deploy the application directly ( which implicitly builds a bar file for you ). |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Wed Oct 09, 2013 4:35 am Post subject: Re: Message broker installation depends on Broker Toolkit |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
| mbtc wrote: |
| The Message broker installation seems to depend on the Broker Toolkit being installed when using Mapping Nodes. |
This can be proven false by the number of environments that the runtime can be installed on versus the number of environments the toolkit can be installed on. |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Oct 09, 2013 4:44 am Post subject: Re: Message broker installation depends on Broker Toolkit |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| joebuckeye wrote: |
| mbtc wrote: |
| The Message broker installation seems to depend on the Broker Toolkit being installed when using Mapping Nodes. |
This can be proven false by the number of environments that the runtime can be installed on versus the number of environments the toolkit can be installed on. |
A flow with mapping nodes works great on a broker using the Solaris OS, and you can't install the Toolkit on that.
You could also take a poll in here of the number of people who:
use the runtime on a platform which does support the Toolkit
use mapping nodes
do not have the Toolkit installed on the runtime machine, especially in higher environments.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mbtc |
| Posted: Wed Oct 09, 2013 7:33 am Post subject: |
|
|
Newbie
Joined: 04 Oct 2013
Posts: 5
|
| joebuckeye wrote: |
This can be proven false by the number of environments that the runtime can be installed on versus the number of environments the toolkit can be installed on. |
I'm sure that is the case, but it is also true that IBM supply different installations/builds for each platform.
We have Linux and AIX.
Does anyone know if there is another archive or source that contains the com.ibm.xml.xci.type.SchemaResolver class?
I agree that we should not need Broker Toolkit installed on our servers in all environments. |
|
| Back to top |
|
|
| lancelotlinc |
| Posted: Wed Oct 09, 2013 8:32 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
| mbtc wrote: |
| joebuckeye wrote: |
This can be proven false by the number of environments that the runtime can be installed on versus the number of environments the toolkit can be installed on. |
I'm sure that is the case, but it is also true that IBM supply different installations/builds for each platform.
We have Linux and AIX.
Does anyone know if there is another archive or source that contains the com.ibm.xml.xci.type.SchemaResolver class?
I agree that we should not need Broker Toolkit installed on our servers in all environments. |
It seems as though whomever installed your system did not install the software in accordance with the step-by-step instructions. We have IIB installed and running on Fedora with no issues.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| wmbjj |
| Posted: Thu Oct 24, 2013 11:40 pm Post subject: |
|
|
Newbie
Joined: 24 Oct 2013
Posts: 2
|
Hi!
I've been searching for similar issues since July and did not find any references. This is the 1st post that matches our WMB installation symptoms.
We have the same problem on our WMB 8.0.0.2 server running on HP/UX (obviously there is no Toolkit on that server). The difference is that we did not resolve this till now. It works fine on WMB 8.0.0.2 Developer edition under Win7 64bit. We never tried on earlier v8.0.0.x versions because v8.0.0.2 was installed from the beginning of the project.
Hope to get useful suggestions what to check to resolve the problem. Please let me know if you have any ideas.
Meanwhile we are going to upgrade WMB installation on HP/UX to 8.0.0.3 and check whether it resolves the issue. |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Fri Oct 25, 2013 1:35 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| wmbjj wrote: |
We have the same problem on our WMB 8.0.0.2 server running on HP/UX (obviously there is no Toolkit on that server). The difference is that we did not resolve this till now. It works fine on WMB 8.0.0.2 Developer edition under Win7 64bit. We never tried on earlier v8.0.0.x versions because v8.0.0.2 was installed from the beginning of the project.
|
I hope you are NOT saying that you installed 8.0.0.2 on a clean system. i.e. one without 8.0.0.0 already installed? If you did then you have to go an remove 8.0.0.2 (or .3 if you have installed it) and start again by installing 8.0.0.0 first.
The 8.0.0.2 Developer edition is AFAIK re specific re-master for Windows and for other non TK platforms you have to install the 8.0.0.0 release first.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| wmbjj |
| Posted: Fri Oct 25, 2013 2:28 am Post subject: |
|
|
Newbie
Joined: 24 Oct 2013
Posts: 2
|
| smdavies99 wrote: |
| wmbjj wrote: |
We have the same problem on our WMB 8.0.0.2 server running on HP/UX (obviously there is no Toolkit on that server). The difference is that we did not resolve this till now. It works fine on WMB 8.0.0.2 Developer edition under Win7 64bit. We never tried on earlier v8.0.0.x versions because v8.0.0.2 was installed from the beginning of the project.
|
I hope you are NOT saying that you installed 8.0.0.2 on a clean system. i.e. one without 8.0.0.0 already installed? If you did then you have to go an remove 8.0.0.2 (or .3 if you have installed it) and start again by installing 8.0.0.0 first.
The 8.0.0.2 Developer edition is AFAIK re specific re-master for Windows and for other non TK platforms you have to install the 8.0.0.0 release first. |
Hi!
Yes, of course 8.0.0.1 and 8.0.0.2 patches were applied consequently on top of 8.0.0.0 |
|
| Back to top |
|
|
|
|
