Websphere Message Broker - Toolkit

Websphere Message Broker Built In Nodes

1.AggregateControl node
2.AggregateReply node
3.AggregateRequest node
4.Check node
5.Collector node
6.Compute node
7.Database node
8.DatabaseRetrieve node
9.DatabaseRoute node
10.DataDelete node
11.DataInsert node
12.DataUpdate node
13.EmailOutput node
14.EndpointLookup node
15.Extract node
16.FileInput node
17.FileOutput node
18.Filter node
19.FlowOrder node
20.HttpInput node
21.HttpReply node
22.HttpRequest node
23.Input node
24.Java Compute node
25.JMSInput node
26.JMSMQTransform node
27.JMSOutput node
28.JMSReply node
29.Label node
30.Mapping node
31.MQeInput node
32.MQeOutput node
33.MQGet node
34.MQInput node
35.MQJMSTransform node
36.MQOptimizedFlow node
37.MQOutput node
38.MQReply node
39.Output node
40.Passthrough node
41.PeopleSoftInput node
42.PeopleSoftRequest node
43.Publication node
44.Real-timeInput node
45.Real-timeOptimizedFlow node
46.RegistryLookup node
47.ResetContentDescriptor node
48.Route node
49.RouteToLabel node
50.SAPInput node
51.SAPRequest node
52.SCADAInput node
53.SCADAOutput node
54.SiebelInput node
55.SiebelRequest node
56.SOAPAsyncRequest node
57.SOAPAsyncResponse node
58.SOAPEnvelope node
59.SOAPExtract node
60.SOAPInput node
61.SOAPReply node
62.SOAPRequest node
63.Throw node
64.TimeoutControl node
65.TimeoutNotification node
66.Trace node
67.TryCatch node
68.TwineballInput node
69.TwineballRequest node
70.Validate node
71.Warehouse node
72.XSLTransform node
#########################################################

New Web services nodes :

•Provider nodes (SOAPInput, SOAPReply)
•Consumer nodes (SOAPRequest, SOAPAsyncRequest, SOAPAsyncResponse)
•Helper nodes (SOAPExtract, SOAPEnvelope)

WebSphere Service Registry and Repository :

•EndpointLookup
•RegistryLookup

Routing :

•DatabaseRetrieve -- to ensure that information in the message is up-to-date.
•DatabaseRoute and Route -- to direct messages down different paths of a message flow based on certain criteria.
•Collector -- to create a message collection from one or more sources based on configurable criteria.

WebSphere Adapter nodes :

•PeopleSoftInput
•PeopleSoftRequest
•SAPInput
•SAPRequest
•SiebelInput
•SiebelRequest

File nodes :

•FileInput
•FileOutput

Transport nodes

•JMSReply
•EmailOutput

=====================================================
Use the Check node to compare the structure of a message arriving on its input terminal with a message structure definition that you supply when you configure the Check node.

Use the Filter node to route a message according to message content.

A Compute node takes as input a message tree (called InputRoot) and outputs a different message tree (called OutputRoot). Notice that InputRoot is read-only and therefore cannot be modified in place.

HTTPin & HTTPout nodes allow the CGI world to talk to "c" programs.

SOAPin & SOAPreply nodes allow to talk to the WebServices world

Trace node : where to send its output ( diferent at Development and Production ). When the BAR file is generated, select the "Configure" bottom flap and enter the "File Path" property. If empty, does it mean "no trace" ?

Other nodes :

•SendMailPlugIn - support pack IA07.
A xml tag with the error message is added to the original message.
•z/OS File Adapter - support pack IA11.
MQ Output node + "Advanced" settings :
Select the Destination Mode from the drop-down list. This identifies the queues to which the output message is put.

•Queue Name. The message is sent to the queue named in the Queue Name property. The properties Queue Manager Name and Queue Name (on the Basic tab) are mandatory if you select this option. This is the default.
•Reply To Queue. The message is sent to the queue named in the ReplyToQ field in the MQMD.
•Destination List. The message is sent to the list of queues named in the LocalEnvironment (also known as DestinationList) associated with the message.

Providing input to a message flow
The type of input node that is used in a message flow depends on the type of application that sent the message to the broker:

•If the message flow gets the messages from the business application by means of a WebSphere MQ queue, use an MQInput node.
•If the messages are sent to broker by an MQe application, use an MQeInput node.
•If the messages are sent by a telemetry device, use a SCADAInput node.
•If the messages are sent by a Web services client, use an HTTPInput node.
•If the messages are sent by a JMS or multicast application, use a Real-timeInput node or a Real-timeOptimizedFlow node.
•If the message flow is to be reused as part of one or more other message flows, use an Input node.
•MQInput
•JMSInput
•HTTPInput
•SOAPInput
•SAPInput
•Timer node
MQInput Node Properties.

•Message Domain
•Message Set
•Message Type
•Message Format
•Topic
Each input node in a message flow causes the broker to start a separate thread of execution. Including more than one input node might improve the message flow performance.
Message Domain types
In Message Domain, select the name of the parser that you are using from the drop-down list.

•MRM
•XML
•XMLNS
•XMLNSC
•JMSMap
•JMSStream
•MIME
•BLOB (same as blank)
•IDOC
Body is equivalent to Root followed by the parser name (for example, Root.XML), which you can use if you prefer.


----------------------------------------------------