Discussion:
Running Broker on Aix and Configuration Manager on Windows
(too old to reply)
r***@yahoo.com
2005-07-07 20:15:26 UTC
Permalink
We have resolved almost all the issues except for this one: when deploying and trying to run our 3rd party plug-in we get the following error: "BIP2241E: LIL not found for message flow node type 'DSTXPlugInNode' in message flow 'DataStageTXNodeMessageFlow'.

The message broker received an instruction to create a message flow node of type 'DSTXPlugInNode', in message flow 'DataStageTXNodeMessageFlow'. The broker does not have the capability to create nodes of this type because an implementation library for this node type was not found in the LIL path.

Ensure that the LIL path is correct and contains all the necessary node implementation libraries, including those supplied by IBM. Then ensure that the message flow and any nested message flows have been saved. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center."

The 3rd party lil file is present in /opt/mqsi/lil, so why can't the Configuration Manager find it.

We would appreciate your help,
Thank you!!!
Please respond to ***@yahoo.com
Andy Piper
2005-07-08 09:10:27 UTC
Permalink
Post by r***@yahoo.com
when deploying and trying to run our 3rd party plug-in we get
the following error: "BIP2241E: LIL not found for message flow
node type 'DSTXPlugInNode' in message flow
'DataStageTXNodeMessageFlow'.
[snip]
Post by r***@yahoo.com
The 3rd party lil file is present in /opt/mqsi/lil, so why
can't the Configuration Manager find it.
The Configuration Manager is not looking for the plugin. The
broker is looking for it.

Assuming that your broker on AIX is installed in /opt/mqsi (I
thought it usually installed to /usr/opt/mqsi on AIX but I could
be wrong about that), and the DataStageTX lil file is in the lil
directory, did you restart the broker before trying to deploy
the flow which contains the node?
--
SWG WBI Services
North Region EMEA
r***@yahoo.com
2005-07-08 13:55:42 UTC
Permalink
The dstxwmqi.lil file is in /usr/opt/wmqi/lil directory. Still I'm getting the error mentioned above. What does "not found in the LIL path" mean. Do I have to initiate an environment variable LIL?
a***@uk.ibm.com
2005-07-08 09:16:31 UTC
Permalink
It's the broker that can't find it!
I believe that there is a problem with the DSTX plugin. Contact Ascential
r***@yahoo.com
2005-07-08 13:56:45 UTC
Permalink
The dstxwmqi.lil file is in /usr/opt/wmqi/lil directory. Still I'm getting the error mentioned above. What does "not found in the LIL path" mean. Do I have to initiate an environment variable LIL?
Kailash Peri
2005-07-22 23:35:05 UTC
Permalink
Post by r***@yahoo.com
The dstxwmqi.lil file is in /usr/opt/wmqi/lil directory. Still I'm getting the error mentioned above. What does "not found in the LIL path" mean. Do I have to initiate an environment variable LIL?
The broker on startup loads all the lil files and jar files from
/usr/opt/mqsi/lil and /usr/opt/mqsi/jplugin directories. If your message
flow contains a plugin node there should be a lil or jar file that
contains the code to be executed when a message passes through the flow.
If the lil or jar file is not found in the appropriate directory
(/usr/opt/mqsi/lil for C/C++ plugins) and (/usr/opt/mqsi/jplugin for
java plugins) then you will get this error.

You will have to stop and restart the broker after the lil file is copied.

Still have a problem? An EG startup trace might give you some clues....

Regards, Kailash
a***@hotmail.com
2007-08-09 07:06:26 UTC
Permalink
I have also faced the same problem. when i tried to deploy messageflow with DSTXPlugIn Node, i was getting the same error "Lil path could not found" that you have got.
Before applying solution,
1. Stop the broker,
2. Clear your Event Viewer --> Application Log:
3. Start the broker, then check the application log again.
4. If you will get the error like "File install_dir\wmqi\dtxwmqi.lil could not be loaded: operating system return code '127'", then use the following solution,

Solution:
first ensure that, do you have RAD / RAC(Agent Controller) installed in your system??
if YES, then The reason for this error is that the IBM RAC 6.0.1 / RAD installs a xerces-c_2_4_0.dll that is incompatible with IBM WebSphere
Transformation Extender for Message Broker and it installs it in
the <windows>\system32 directory.
So just copy xerces-c_2_4_0.dll from DSTX Extender installation, and paste it in broker's bin directory and restart your broker.

(go through this link: http://www-1.ibm.com/support/docview.wss?rs=2320&context=SSVSD8&dc=DA400&uid=swg27008243&loc=en_US&cs=UTF-8&lang=en&rss=ct2320websphere)

regards,
amit

Loading...