| Author |
Message
|
| WBIMaestro |
 Posted: Sun Dec 11, 2011 8:58 pm Post subject: JobExecution Node IA9Z install? |
 |
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
Hi Folks,
anyone have any success using the JobExecution Node supportpac IA9Z?
Im trying to install it on WMB 7 on Red Hat Linux . I've copied over the
JobExecutionNode_v70.jar to /opt/ibm/mqsi/7.0/jplugin/ and the JEN_70.jar to C:\Program Files\IBM\WMBT700\plugins. Restarted the toolkit with mb.exe -clean, but I still get a 'JobExecution Subflow not found' error when I drag the JobExecution node onto a flow and it won't deploy due to errors. Any idea what the issue might be?
a |
|
| Back to top |
|
 |
| Vitor |
| Posted: Mon Dec 12, 2011 5:35 am Post subject: Re: JobExecution Node IA9Z install? |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WBIMaestro wrote: |
| Any idea what the issue might be? |
We might have more idea if you posted the deploy errors.
Not having tried this support pac, looked at the support pac or even thought about the support pac I'd theorise the runtime component isn't installed correctly but given the utter absence of diagnostic information you've provided it could just as easily be the broker throwing errors as a political protest about being used as cron or indicating it's membership of the "Occupy Linux" campaign.
Better information, better advice.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Dec 12, 2011 7:48 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Don't ever put anything into jplugin on Broker 6.1 or later.
Create your own MQSI lil path using mqsichangebroker.
Almost certainly, you will find that your Broker 7.0 doesn't treat jplugin as a lilpath. |
|
| Back to top |
|
|
| WBIMaestro |
| Posted: Mon Dec 12, 2011 8:50 am Post subject: |
|
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
| well, all the logs that I find in the /var/mqsi/common/log directory seem to be 0 byte. where can I find any additional diagnostic information. the issue with using cron is that the arguments(like filename etc...) will vary based on the messages being written to file. thiught this might be a neat little solution. I found that the jplugin directory permsissions were wrong, but fixing that and boucing the broker and toolkit didnt seem to help either. |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 12, 2011 8:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WBIMaestro wrote: |
| well, all the logs that I find in the /var/mqsi/common/log directory seem to be 0 byte. where can I find any additional diagnostic information. |
What does the deploy fail with? If the deploy is failing then of course the broker isn't reporting any problems.
In the same way no mechanic has ever reported the car I buy 3 years from now has a dangerous (and expensive) rattle I need to get fixed at once. Until it's successfully deployed, broker has no knowledge of it.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WBIMaestro |
| Posted: Mon Dec 12, 2011 9:01 am Post subject: |
|
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
the deploy fails right away when I save the msgflow with the jobexec node since the jobexecnode has a tiny x mark on it indicating that the subflow could not be located. Im going to try the custom lilpath approach,though I found this APAR which indicates that LILPATH64 also needs to be set.
http://www-01.ibm.com/support/docview.wss?uid=swg1IZ25261 |
|
| Back to top |
|
|
| Vitor |
| Posted: Mon Dec 12, 2011 9:35 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| WBIMaestro wrote: |
| the deploy fails right away when I save the msgflow with the jobexec node since the jobexecnode has a tiny x mark on it indicating that the subflow could not be located. |
You've not mentioned that before. You said the deploy wasn't working, not that the reference in the Toolkit couldn't be resolved.
That's a different problem and not a runtime one.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| WBIMaestro |
| Posted: Mon Dec 12, 2011 9:48 am Post subject: |
|
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
| ok, sorry abouyt that. but, even for that, all that the manual says is to copy JEN_70.jar to C:\Program Files\IBM\WMBT700\plugins which I have done. can I find the tollkit eclipse logs somewhere.. maybe that will help |
|
| Back to top |
|
|
| mqjeff |
| Posted: Mon Dec 12, 2011 9:50 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
Contact the author/maintainers of the supportPac.
Make sure you're using the correct fixlevel of Broker Toolkit 7.0 for the package you're trying to install. |
|
| Back to top |
|
|
| WBIMaestro |
| Posted: Mon Dec 12, 2011 2:02 pm Post subject: |
|
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
| for some unknown reason the x mark on the node just disappeared. must have done something right. testing now. |
|
| Back to top |
|
|
| deepak_paul |
| Posted: Tue Dec 13, 2011 7:53 pm Post subject: |
|
|
Centurion
Joined: 04 Oct 2008
Posts: 147
Location: US
|
| mqjeff wrote: |
Don't ever put anything into jplugin on Broker 6.1 or later.
Create your own MQSI lil path using mqsichangebroker.
Almost certainly, you will find that your Broker 7.0 doesn't treat jplugin as a lilpath. |
| IA9Z.pdf wrote: |
WebSphere Message Broker v7.0
• Copy ‘\WMB JobExecutionNode\V7.0Runtime\JobExecutionNode_v70.jar’ file
to ‘<WMB-Install–Directory>\jplugin’ |
mqjeff,
What has changed in Broker 6.1 or later? you are trying to say that it is a best practice to create our own LIL path using mqsichangebroker to keep all jars or it will not work if we place the jar file in jplugin in WMB v7.0?
_________________
Regards
Paul |
|
| Back to top |
|
|
| mqjeff |
| Posted: Wed Dec 14, 2011 2:47 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| deepak_paul wrote: |
[mqjeff,
What has changed in Broker 6.1 or later? you are trying to say that it is a best practice to create our own LIL path using mqsichangebroker to keep all jars or it will not work if we place the jar file in jplugin in WMB v7.0? |
At some point, and I think it was at 6.1, jplugin stopped being added to the LILPATH. So, yes, if you put jar files in jplugin, but jplugin is *not* on the lilpath, then the jars won't get loaded.
And, yes, it has always been a better idea to create your own LILPATH and add extensions there - so that you are not changing the base product install folder that can get modified when you apply fixpacks. |
|
| Back to top |
|
|
| WBIMaestro |
| Posted: Wed Dec 14, 2011 8:24 am Post subject: |
|
|
Acolyte
Joined: 18 Feb 2005
Posts: 53
|
| got the job exec node woking. thanks guys |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Dec 14, 2011 10:29 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
| WBIMaestro wrote: |
| got the job exec node woking. thanks guys |
Jolly good show what! 
Would you mind sharing your solution with us?
_________________
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 |
|
|
|
|
