| Author |
Message
|
| Aryan Soni |
 Posted: Fri Jul 06, 2007 4:01 am Post subject: lil path |
 |
|
Newbie
Joined: 06 Jul 2007
Posts: 1
|
BIP2241E: Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type 'ComJpmIsTpciMqsiConversionNode' in message flow 'TPCI_CORE_FLOW'........this error is coming when i'm trying to deploy the bar file to the execution group.
How to ovecome this problem??
Plz send ur reply asap...  |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Fri Jul 06, 2007 4:09 am Post subject: Re: lil path |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi Aryan Soni,
| Aryan Soni wrote: |
| BIP2241E: Loadable Implementation Library (.lil, .jar or .par) not found for message flow node type 'ComJpmIsTpciMqsiConversionNode' in message flow 'TPCI_CORE_FLOW'........this error is coming when i'm trying to deploy the bar file to the execution group. |
Seems like you are using a custom node 'ComJpmIsTpciMqsiConversionNode'.
Please place the jar file of the node in the runtime jplugin folder and restart the broker....search the forum for custom node related topics.
Regards. |
|
| Back to top |
|
|
| bristewart |
| Posted: Fri Jul 06, 2007 6:40 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2007
Posts: 3
Location: Hursley, UK
|
Aryan,
Your UDE (user-defined extension) plug-in node should have an associated runtime JAR file (if it is a Java UDE) or a LIL file (if it is a C UDE).
All you have to do is ensure that the Broker can read this JAR/LIL at runtime.
From V6 onwards, the recommended way is to add it to the Broker's User Lil Path. Not to place it under the install dir in the jplugin or bin or lil directory.
This can be done as follows:
1) mqsichangebroker <broker name> -l <path to dir containing JAR or LIL file(s)>
2) Restart your broker, before attempting to deploy your UDE again.
The InfoCenter docs on this can be found here:
http://publib.boulder.ibm.com/infocenter/wmbhelp/v6r0m0/index.jsp?topic=/com.ibm.etools.mft.doc/as10004_.htm |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 06, 2007 6:55 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
It's actually kind of annoying to have to add something to the LIL path.
I can understand not wanting to keep stuff in the Install directory, and that IBM wants to encourage people to do something else.
But I think it would have been very easy to add another default location, under the workpath - and thus not require all of the customers to take an extra step like this.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| bristewart |
| Posted: Sun Jul 08, 2007 4:58 am Post subject: |
|
|
Newbie
Joined: 06 Jul 2007
Posts: 3
Location: Hursley, UK
|
| jefflowrey wrote: |
| But I think it would have been very easy to add another default location, under the workpath - and thus not require all of the customers to take an extra step like this. |
If your UDE is Java and you are only deploying to distributed platforms then you can simply put the JAR file in the existing <workpath>/shared-classes dir. E.g. on Windows this location would be:
C:\Documents and Settings\All Users\Application Data\IBM\MQSI\shared-classes |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Sun Jul 08, 2007 12:13 pm Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| bristewart wrote: |
If your UDE is Java and you are only deploying to distributed platforms then you can simply put the JAR file in the existing <workpath>/shared-classes dir. E.g. on Windows this location would be:
C:\Documents and Settings\All Users\Application Data\IBM\MQSI\shared-classes |
A) That's a lot of ifs.
B) Only if I want it to be loaded by the Shared classloader... If I put a PAR file there, does the PAR get it's own classloader, like it would if it were on the LIL path?
C) No offense - but that's still not the point. It's a great idea that one can add one's own directories to the lil Path. It's a significantly poorer idea that one *has* to.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
|
|
