ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Adding a message flow as a plu-in node

Post new topic  Reply to topic
 Adding a message flow as a plu-in node « View previous topic :: View next topic » 
Author Message
d
PostPosted: Mon Mar 27, 2006 4:21 am    Post subject: Adding a message flow as a plu-in node Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 25

Hi,

I want to add a message flow to the nodes palette as a plu-in node. Could somebody please guide me ?

Thanks,
d
Back to top
View user's profile Send private message
jsware
PostPosted: Mon Mar 27, 2006 4:23 am    Post subject: Reply with quote

Chevalier

Joined: 17 May 2001
Posts: 455

You don't need to add a node to the nodes palette to use it as a plugin node.

Just drag the flow onto the flow you want it to be a subflow in and it will appear as a node in your flow.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.
Back to top
View user's profile Send private message
d
PostPosted: Mon Mar 27, 2006 7:59 pm    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 25

Hi John,

I totally agree with your point of view. But my requirement is such that I need the message flow to appear as an independent node in the node palette.

Could you please help me out here ?

Thanks,
d
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Mon Mar 27, 2006 9:08 pm    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi d,

Is this your requirement or the clients or your manager's....

If you need to make a flow into a plug-in node, you should rather code the entire thing in Java and then export it as a plug-in node....

I hope you understood what scottj2512 was trying to tell you, as i don't see why anyone would want the entire flow to be converted to a node...

or else, u should make the flow a WebService....that would be the earisr and better way out.

Regards.
Back to top
View user's profile Send private message Send e-mail
d
PostPosted: Tue Mar 28, 2006 3:37 am    Post subject: Reply with quote

Apprentice

Joined: 24 May 2002
Posts: 25

I understand your and scottj2512 's points.

But, I am supporting the Corporate Frameworks Group. The artifacts that we prepare would be used by various projects/developers. Hence, we have to provide the developers with standard installation dumps with reusable functionality packaged as custom nodes.

This particular functionality, I am working now, does not need a java plug-in. It is achieved via a set of MB nodes. Now, that I have this reusable message flow, I need to package it and if possible make it visible in the Nodes Palette. I would appreciate if anyone can guide me or point to possible source of documentation on this.
Back to top
View user's profile Send private message
elvis_gn
PostPosted: Tue Mar 28, 2006 3:46 am    Post subject: Reply with quote

Padawan

Joined: 08 Oct 2004
Posts: 1905
Location: Dubai

Hi d,

Quote:
I need to package it and if possible make it visible in the Nodes Palette.

I feel, you would rather be happier believing thats its not possible........u will have to pick up the java class files of all the nodes involved and make a package.....or atleast reference to them all....I don't even know the issues that might arrise by ur calling then, and the toolkit using them too....That is why i said, u can rather make a Java custom node.

If its only to do with generic flows, to be used throughout your application, then define a generic project and store all the flows in it and call the flows from anywhere....this is a very standard solution.

You will only have to move this from one developer's system to another and also in production.

Regards.
Back to top
View user's profile Send private message Send e-mail
jsware
PostPosted: Thu Mar 30, 2006 3:46 am    Post subject: Reply with quote

Chevalier

Joined: 17 May 2001
Posts: 455

d wrote:
... I need to package it and if possible make it visible in the Nodes Palette. I would appreciate if anyone can guide me or point to possible source of documentation on this.


I understand what you are getting at (provide a re-usable node to another development team in a manner consistent with the standard nodes they currently use) but I am not sure that what you want to achieve is possible.

A flow is something different to a plugin node.

A plugin node has configuration information in the eclipse tooling that enables you to add the node to a flow and configure its properties. There is a matching DLL/shared library deployed separately into a standard location in the runtime environment (i.e. the broker).

A flow on the other hand has its configuration information derived when added as a subflow from eclipse's ability to examine the subflow which is openned in your workspace. If you close the subflow project, then the "parent" flow will generate errors because eclipse can't determine what properties have been promoted. Additionally, when you "compile" the main flow into a bar file for deployment, what is actually happening is the XML is "flattened" and all subflows are included into one big XML flow.

Thus what I believe you could do (not advised, not tried) is add a flow containing a subflow into a bar file and then modify the subflow and add another flow that uses this modified version into the same bar file. Once in the bar file, the subflow is not shared, each flow has its own (different) copy. This bar file can then be deployed to a broker and the two different version of the subflow would be used.

If you have a flow that includes a subflow twice, I would not be suprised if two separate copies of the flow are included in the deployed "flat" XML.

At the end of the day the concept of subflows are just a sugar coating to give the illusion of modularity when in reality, what gets deployed is a monolithic "flat" flow.

I don't think this helps your requirement. We have standard subflows for error handling, date manipulation functions etc. and they are all part of a "common" project which every developer has in their workspace. That's the closest I've been able to get to having common subroutines and "library" functions.
_________________
Regards
John
The pain of low quaility far outlasts the joy of low price.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Adding a message flow as a plu-in node
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.