Posted: Thu May 27, 2010 1:36 am Post subject: Not able to deploy the custom node which is to access .lil
Newbie
Joined: 27 May 2010 Posts: 1
Hi,
I have created a custom node to access the C program that is there in the particular location. I have created the .lil file for the C programs and kept in a particular location. And i have set the path of the lil location using mqsichangebroker command also ... But while deploying the bar file into the execution group i am getting the following errors ... can you please help me to get some solution for this.
BIP2078E : Broker brk1 was unable to process the internal configuration message. The entire internal configuration message failed to be processed sucessfully.
BIP4041E : Execution group received and invalid confirguration message. The broker was asked to deploy a message flow which contained properties there were not recognized by broker. this typically results from a message flow requiring a version or type of node that is not supported by broker installation.
BIP2241E : The lodable implementation library (.lil,.jar,.par) is not found for the message flow node type 'NumComputeNode' is message flow 'NumCompute'.
I have tested this with the sample that has come with WMB 7.0, and i have copied the IBM given .lil to the particular directory. It was working with out any issues. If i create the .lil using the following command it is not working.
you have compiled the lil file using the documented options (I haven't checked if the ones you gave are the ones to use)
you have defined a lil directory with the mqsichangebrokercommand
you have put your compiled lil file there
you have RESTARTED your broker
You confirmed that broker did not throw any errors during startup about failing to load the lil or any shared libraries or etc.
you have THEN attempted to deploy your flow
If you've done all of those things and you are still getting the error about failing to find the LIL file for your node, then likely the name of your node in the toolkit description does not match the name of your node in the implementation. Remember that there's a common failing with c nodes to get errors because you did or didn't add the word "node" to the end of the node implementation name. Broker runtime ends up looking for "NumComputeNodeNode" for example.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum