| Author |
Message
|
| wilsonjohn24 |
 Posted: Thu Jun 19, 2008 10:37 pm Post subject: mqsicreatebar: working with .jar/java compute nodes.... |
 |
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Hi,
Firstly, I have tried searching forums etc for this one. As I very sure I cant be the first person to have encountered this issue - so please be gentle if the answer is obvious -
------------------
Got MSG Flow project with Java compute node- which creates two projects:
MF_TTM_MsgFlow
MF_TTM_MsgFlowJava
This is fine from Eclipse Toolkit it creates the .jar and adds it to the .bar.
What is the equivlent from the command line mqsicreatebar - do I create the jar with standard ant tasks then add it to the .bar outside of the mqsicreatebar? Do I reference the .jar in someway via -o parameter or do I go straight to Jail not collecting £200 on the way past go?
thanks in Advance
John |
|
| Back to top |
|
 |
| joebuckeye |
| Posted: Fri Jun 20, 2008 4:30 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
What happens when you try the mqsicreatebar command?
If your project references are right then the jar should automatically get added when you add in the message flow.
We have a flow that references an external jar file (in addition to the flow jar file) and it is automatically included in the bar file via the mqsicreatebar command. |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Fri Jun 20, 2008 6:10 am Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
| Basically I reference the java project within the -p , but not explicitly reference anything other than the msgflow in -o . Should I reference the jar or something in the -o ? |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Fri Jun 20, 2008 12:47 pm Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
| Can you please provide a sample of your mqsicreatebar? |
|
| Back to top |
|
|
| joebuckeye |
| Posted: Wed Jun 25, 2008 6:33 am Post subject: |
|
|
Partisan
Joined: 24 Aug 2007
Posts: 365
Location: Columbus, OH
|
We don't reference the Java project at all.
We use the -p to point to the project and then use the -o options to include the message flows.
The jar files are automatically included in the bar file created due to project references. |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Thu Jun 26, 2008 12:16 pm Post subject: |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
Thanks for that..
I got it to work for simple msg flow + java project. But I cant get it to work with an existing projects ( yet these existing projects work ok- when the msgflow is added the jar is added in MB Toolkit).
Even for the simple flow ( 1 msg flow + 1 java project) the jar is added to the bar. But when I add several additional projects ( non java ) via the command line it fails to add the jar.
Apart from a few Null pointer stack traces ( which happens even for non msgflow + esql projects) - the mqsicreatebar completes succesfully. The logs in the metadata file dont provide any additional clues as to why the jar was not added ).
Me thinks it time to raise the issue via our IBM support contract....
thanks again for your replies .....
cheers
John |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Fri Jun 27, 2008 5:42 am Post subject: Further Info.... |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
The java project is in the correct location and seems identical to the project in the resource view of MB toolkit.
|-TTM - Message FlowsJava
- .classpath
- . project
- com
- xxx
- A.java
- A.class
The Bar file produced contains cmf file but does not run as obviously the java dependency is not in the .bar.
Command:
C:\"Program Files"\IBM\MessageBrokersToolkit\6.0\eclipse\mqsicreatebar.exe -data c:\build\wmb\wmb -b xxxx.bar -p "Generic - Message Flows" "TTM - Message Flows" "TTM - Message FlowsJava" -o "TTM - Message Flows"\MF1_TTM_ApplicationFlow.msgflow
Service. log
(see bold section below ).
==============================================
!Fri Jun 27 14:11:45 BST 2008
Message flow MF1_TTM_ApplicationFlow.msgflow successfully loaded
Message flow MF1_TTM_ApplicationFlow.msgflow successfully compiled
Message flow MF1_TTM_ApplicationFlow.msgflow successfully added to archive file
Node Flow Version Reason
----------------------------------------------------------------------------------------------------
Compute_FormatUknownMF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Filter_TTMReq MF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
JavaCompute_toTTM_frMF1_TTM_ApplicationF
COM_SetInputLogging MF3_InboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageCHD MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
JavaCompute_toCHD_frMF1_TTM_ApplicationF
COM_SendMessageMFT MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Filter_CHDReq MF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetDestinationLaMF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageCIC MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_FormatErrorLog MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageESW MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageFMS MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageIDO MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetInputLogging MF3_InboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetInputLogging MF3_InboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetMQRFH2 MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageSAM MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_BitstreamMsg MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageTOP MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetInputLogging MF3_InboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Compute MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageESV MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageACT MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Compute_toTTM_fromUnMF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetOutputLoggingMF3_OutboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_ResetLabel MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageISV MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SetInputLogging MF3_InboundLogging 5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageARL MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Compute_Response MF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageTTM MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Compute1 MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageISW MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Compute_TTMtoSNS MF1_TTM_ApplicationF5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
COM_SendMessageGEN MF3_GenericErrorHand5.0 Generate 5.0 compatible ESQL by default.
This compatibility level supports ESQL source code debugging.
Deploying 5.0 compatible ESQL code will cause a syntax error on version 2.1 or previous brokers.
Resource TTM - Message FlowsJava.jar was not added to the BAR file because it was not found in the
workspace nor found built in metadata. This resource may be required by the
broker because it contains java dependencies for a flow to be deployed in this
BAR. If actually required and java project is to be found in worskpace, you can
force a build on this project and then retry adding the flow to this BAR. You can
also deploy a JAR resource containing these dependencies from the tooling
adding it manually to a BAR file or copying it directly to the broker. |
|
| Back to top |
|
|
| wilsonjohn24 |
| Posted: Mon Jun 30, 2008 11:02 pm Post subject: Solution |
|
|
Voyager
Joined: 02 Feb 2007
Posts: 93
Location: Scotland
|
|
| Back to top |
|
|
|
|
