I'm new to IIB as well as stackoverflow and just playing around with some flows. I'm getting an error The Java method 'MQDepth.getMQDepth' could not be found
. I refered here which says two method of deploying jar, (i) Add the JAR file to the BAR file (ii) Store the JAR file in either of the following locations. I couldn't find any site that explains how I can add the jar to bar, so I opted option (ii). Below explains what I did and the error I'm getting. Any help would be appreciated.
I have created a flow :
"TimeOut Notification Node" set to automatic (say 1 minute) → Compute Node → MQ Output Node
What I want to do :
Automatically detect CurrDepth of a queue and generate a XML for the time being (this will be changed to mail with added conditions). The code (esql) calls a custom procedure (GetCurrDepth).
Compute Node Code :
DECLARE queueManager CHAR;
DECLARE queueName CHAR;
DECLARE queueDepth INT;
SET queueManager = 'DDMQBKD10';
SET queueName = 'INPUT';
CALL GetCurrDepth(queueManager, queueName, queueDepth);
IF queueDepth > 0 THEN
SET OutputRoot.XMLNSC.Report.QManager = queueManager;
SET OutputRoot.XMLNSC.Report.QName = queueName;
SET OutputRoot.XMLNSC.Report.QDepth = queueDepth;
END IF;
Calling GetCurrDepth :
CREATE PROCEDURE GetCurrDepth(IN qMgr CHARACTER
,IN qName CHARACTER
,OUT qDepth INTEGER)
LANGUAGE JAVA
EXTERNAL NAME "MQDepth.getMQDepth";
GetCurrDepth JAVA:
import com.ibm.mq.MQException;
import com.ibm.mq.MQQueue;
import com.ibm.mq.MQQueueManager;
import com.ibm.mq.constants.MQConstants;
public class MQDepth {
public static void getMQDepth(String QManager, String Q, Integer QDepth) throws MQException
{
// define the name of the QueueManager
final String qManager = QManager;
// and define the name of the Queue
final String qName = Q;
// Create a connection to the QueueManager
MQQueueManager qMgr = new MQQueueManager(qManager);
// Now specify the queue that we wish to open and the open options
MQQueue queue = qMgr.accessQueue(qName, MQConstants.MQOO_INQUIRE | MQConstants.MQOO_INPUT_AS_Q_DEF, null, null, null);
// Check the currdepth of the queue
try {
QDepth = queue.getCurrentDepth();
} catch (Exception e) {
// TODO Auto-generated catch block
e.printStackTrace();
}
// Close the queue
queue.close();
// Disconnect from the QueueManager
qMgr.disconnect();
}
}
JAR : I've created a jar of this JAVA and kept it in "C:\ProgramData\IBM\MQSI\shared-classes"
ERROR :
BIP2087E: Integration node 'TESTNODE_Dipanjan' was unable to process the internal configuration message.
The entire internal configuration message failed to be processed successfully.
Use the messages following this message to determine the reasons for the failure. If the problem cannot be resolved after reviewing these messages, contact your IBM Support center. Enabling service trace may help determine the cause of the failure.
BIP4041E: Integration server 'default' received an administration request that encountered an exception.
While attempting to process an administration request, an exception was encountered. No updates have been made to the configuration of the integration server.
Review related error messages to determine why the administration request failed.
BIP3202E: (.GetCurrDepth, 1.1) : An error occurred when trying to resolve the Java class or method 'MQDepth.getMQDepth' which is referred to by the routine 'GetCurrDepth'.
Further messages are generated that explain the error in more detail.
Correct the syntax of your Java expression in node '.GetCurrDepth', around line and column '1.1', then redeploy the message flow.
BIP2946E: The Java method 'MQDepth.getMQDepth' could not be found
The Java method 'MQDepth.getMQDepth' with the specified signature could not be found in the specified class. Ensure the method exists in the specified class and that it exactly matches its ESQL signature.
Examine and correct the SQL program.
BIP2871I: The request made by user 'DESKTOP-6BQMC6G\Dipanjan' to 'deploy' the resource 'C:/Users/Dipanjan/IBM/IIBT10/workspace/GeneratedBarFiles/BigOneproject.generated.bar' of type 'BAR' on parent 'default' of type 'ExecutionGroup' has the status of 'FAILED'.
Based on ESQL-to-Java data-type mapping table, ESQL OUT INTEGER
maps to Java java.lang.Long[]
.
The "Java routine example 2" in CREATE PROCEDURE statement explains your use case.