MQSeries.net :: View topic - sample java plugin node BIP2241E: LIL not found

seanrocket · Posted: Wed May 26, 2004 8:49 am Post subject:

Hello,

I've been trying to deploy my message flow of the sample Java plugin on Windows 2000 but am having trouble.
The error that I am stuck on is :
----------------------------------------------------------------------------------
BIP2241E: LIL not found for message flow node type 'ComIbmTutorSwitchNode' in message flow 'Tutor'.

The message broker received an instruction to create a message flow node of type 'ComIbmTutorSwitchNode', in message flow 'Tutor'. 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 checked in. Redeploy the new configuration to the broker ensuring that the complete configuration option is used. If the problem persists contact your IBM support center.
----------------------------------------------------------------------------------

I have compiled and jar'ed the SwitchNode.java file and then placed the jar file in the lilpath which is C:\<installdir>\jplugin. I checked to make sure this was the lilpath by checking the registry HKEY_LOCAL_MACHINE\SOFTWARE\IBM\WebSphereMQIntegrator\2\<broker_name>. I have tried both compiling and jarring with the package name com.ibm.samples and without the package name. I made sure the class file was in the appropriate location in both cases.

I have checked to make sure the message flow that the Switch Node is in is assigned to the appropriate execution group.

When I created my plugin I used the plugin SmartGuide and I made sure the Node Id did not have the 'Node' attached to the end because I am aware of the bug where it attaches a 'Node' to the name.

I have tried to restart the broker from the Services Manager and I have also tried with different combinations of restarting the Broker and Configuration manager.

I have amde sure that the message flow and the node were checked in.

1. How do you resolve this issue?

2. Do you need the wdp file?

================ SwitchNode.java ===================
/*
* Licensed Materials - Property of IBM
* 5648-C63
* (C) Copyright IBM Corp. 1999, 2001
*/

//package com.ibm.samples;

import com.ibm.broker.plugin.*;

/**
* Sample plugin node.
* This node propagates the incoming message to one of several output terminals
* depending on the content of the message.
* A minimal test message for this node would be:
* <data><action>change</action></data>
*/
public class SwitchNode extends MbNode implements MbNodeInterface
{
String _nodeTraceSetting;

/**
* Switch node constructor.
* This is where input and output terminal are created.
*/
public SwitchNode() throws MbException
{
createInputTerminal("in");
createOutputTerminal("add");
createOutputTerminal("change");
createOutputTerminal("delete");
createOutputTerminal("hold");
createOutputTerminal("failure");
}

/**
* This static method is called by the framework to identify this node.
* If this method is not supplied, a default name will be generated
* automatically based on the node's package/class name. In this case
* it would be 'ComIbmSamplesSwitchNode'.
*/
public static String getNodeName()
{
return "ComIbmTutorSwitchNode";
}

/**
* This evaluate message is called by the broker for each message passing
* through the flow. The message assembly is passed in with the 'assembly'
* parameter. It is possible for a node to have more than one input
* terminal. The terminal that the message has come in on is represented
* by the 'in' parameter.
*/
public void evaluate(MbMessageAssembly assembly, MbInputTerminal in)
throws MbException
{
// Navigate to the relevant syntax element in the XML message
MbElement rootElement = assembly.getMessage().getRootElement();
MbElement switchElement = rootElement.getLastChild().getFirstChild().getFirstChild();

// To aid debugging, text can be printed to stdout/stderr.
// On NT this can be viewed by selecting 'Allow sevice to interact with
// desktop' on the NT Services properties dialog.
// On Unix set the environment variable MQSI_RUN_ATTACHED=1 before
// starting the broker.
if(_nodeTraceSetting.equals("debug"))
{
System.out.println("Element = " + switchElement.getName());
System.out.println("Value = " + switchElement.getValue());
}

// Select the terminal indicated by the value of this element
String terminalName;
String elementValue = (String)switchElement.getValue();
if(elementValue.equals("add"))
terminalName = "add";
else if(elementValue.equals("change"))
terminalName = "change";
else if(elementValue.equals("delete"))
terminalName = "delete";
else if(elementValue.equals("hold"))
terminalName = "hold";
else
terminalName = "failure";

MbOutputTerminal out = getOutputTerminal(terminalName);

// Now propagate the message assembly.
// If the terminal is not attached, an exception will be thrown. The user
// can choose to handle this exception, but it is not neccessary since
// the framework will catch it and propagate the message to the failure
// terminal, or if it not attached, rethrow the exception back upstream.
out.propagate(assembly);
}

/* Attributes are defined for a node by supplying get/set methods.
* The following two methods define an attribute 'nodeTraceSetting'.
* The capitalisation follows the usual JavaBean property convention.
*/
public String getNodeTraceSetting()
{
return _nodeTraceSetting;
}

public void setNodeTraceSetting(String nodeTraceSetting)
{
_nodeTraceSetting = nodeTraceSetting;
}

}
===============================================

-Sean