PostitDelete node


The PostitDelete node icon

This page contains information on:

The PostitCreate, PostitApply and PostitDelete nodes are co-operating nodes that together are responsible for the processing of a virtual postit.  For those not familiar with the term, a postit is a piece of paper (the original ones were yellow in colour) on which notes can be written.  It is sticky-backed, enabling it to be attached to most surfaces.)

The PostitDelete node is responsible for searching the global postit chain looking for any postits which match existing postits based on the search criteria specified on the node.  Matching postits are then deleted.

The PostitDelete node has one input terminal called in and three output terminals, out, noMatch and failure.  When a message is received in the input terminal, the node uses the PostitName, CopyDataFrom and PostitScope values which were configured in the Control Centre to search for matching postits. Matching postits are then deleted if they were created by a message flow in the current execution group, i.e. the execution group in which the PostitDelete is running. The message executing the PostitDelete node remains unchanged and is propagated to the out terminal.  If no matching postits are found, the message is propagated to the noMatch terminal.

Any errors in processing the PostitDelete node result in the message being propagated to the failure terminal and a message logged to the MQSI V2 message log.

Node terminals

The PostitDelete node provides the following terminals:
 
 
in The input terminal that accepts a message for processing by the node.
out The output terminal to which the (unchanged) message is propagated.
noMatch The output terminal to which the message is sent if no matching postits can be found.
failure The output terminal to which the message is propagated if any other errors are encountered.

Configuring the PostitDelete node

When you have put an instance of the PostitDelete node into a message flow you can configure it. Right click on the node in the Message Flow Definition pane and select Properties. Click on the Basic tab and (optionally) enter the name that you wish to give the postit. By giving the postit a name you can associate this PostitDelete node with postits created by a PostitCreate node with a matching name.  You must also specify further matching criteria that will match existing postits with this PostitDelete.  You must specify the name of the syntax element from which the postit data should be copied. This should be the same as the PostitCreate node responsible for creating the postits you wish to delete (the name must begin with 'Root.').

PostitDelete node properties

PostitName   Additional value used to identify the postit.  The value enables the PostitDelete node to restrict matching postits to those created with a specified name. 
CopyDataFrom   Specifies the name of the syntax element within the message into which the stored postit data should be copied.  The value specified here must match the value specified on the PostitCreate node responsible for creating the postits you wish to delete. The name must begin with 'Root.'.

Click on the Advanced tab and (optionally) modify the scope of the postit.
 
PostitScope Execution Group The value set for this property determines the scope of the postit instance.  It can take 3 possible values 
  • ExecutionGroup – only the local indexes, i.e. those indexes that refer to postits created with PostitScope=ExecutionGroup will be searched.
  • Broker - both the local indexes, i.e. those indexes that refer to postits created with PostitScope=ExecutionGroup, and the global indexes, i.e. those indexes that refer to postits created with PostitScope=Broker will be searched.
  • Platform - both the local indexes, i.e. those indexes that refer to postits created with PostitScope=ExecutionGroup, and the global indexes, i.e. those indexes that refer to postits created with PostitScope=Platform will be searched.


© IBM Corporation 2001. All Rights Reserved