A 'Pick First Group'.

 
 

Sending HTTP response, confirming an email/jms message etc. This is because the confirmation or sending HTTP response has to done in the same session. When engine crashes these sessions are closed at their socket level. In such cases send response/confirm before checkpoint.



 
 

$_error variable is available in the node following the error transition. It captures the error message, error code etc.

 
 

XML
HTML
Text

 
 

Child axis- What this means is that when you select "BOOK" from the current context, it selects a child node with that name, not a sibling with that name. Other axes are parent , self , sibling etc.

 
 

Basically wait and notify should share a common notification configuration which is just a schema definition for data that will be passed from notifier to waiter. Specific instances of waiter & notifier are corrrelated via a key.

For example: when one process is in wait state for key 'Order-1', it waits till another process issues a notification with the same key value.

 
 

Both of them can be manipulated via the palette resources 'Get shared variable' and 'Set shared variable'.


A job shared variable is private to one instance of job or in other words each job has a fresh copy. In the case of shared variable the same copy is shared across all job instances. It can even be persisted and can survive BW engine restarts and even shared across multiple BW engines(when deployed using DB persistence).


 
 

The scope of user defined process variables is only the process in which it is defined.(Not even inside a sub process that is invoked from this process)

 
 

It can be used to serve the wsdl file of a SOAP Event Source to a (http) client.
Construct a process like: HTTP Receiver -> Retrieve Resources -> Send HTTP Response

Now the WSDL file for a SOAP service can be retreived using the http request

http://<host>:<port>/<path>/<resourceName>?wsdl

where 'path' is the folder path to the SOAP Event Source process and 'resourceName' is the name of the process

Example : http://purch:8877/Purchasing/GetPurchaseOrder?wsdl

 
 

SOAP request reply activity. If the business process needs to be exposed as SOAP service use SOAP Event Source in conjunction with SOAP Send Reply or SOAP Send Fault.