message broker session extra
TRANSCRIPT
OSOL OGS
© 2009 IBM Corporation
Message Broker Session Extra
Message Broker Review
GBS
Business Unit or Product Name
© 2009 IBM Corporation
Message tree structure
Business Unit or Product Name
© 2009 IBM Corporation
Accessing elements in a message tree
Business Unit or Product Name
© 2009 IBM Corporation
<Employees> <Employ>
<name>Esteban</name> </Employ> <Employ>
<name>Pamela</name> </Employ> <Employ>
<name>Andrea</name> </Employ></Employees>
1.- DECLARE myRef REFERENCE TO OutputRoot; CREATE FIELD OutputRoot.XMLNSC.Employes[2] AS myRef; SET myRef='Virginia'2.- DECLARE myRef REFERENCE TO OutputRoot.XMLNSC.Employees.Employ[2]; CREATE NEXTCHILD OF myRef NAME 'name'; SET myRef = 'Virginia'3.- DECLARE myRef REFERENCE TO OutputRoot.XMLNSC.Employees.Employ[2]; CREATE NEXTSIBLING OF myRef NAME 'Employ'; SET myRef.name = 'Virginia'4.- DECLARE myRef REFERENCE TO OutputRoot.XMLNSC.Employees.Employ[2]; CREATE NEXTSIBLING OF myRef AS myRef NAME 'Employ'; SET myRef.name = 'Virginia' .
QUESTION....
Business Unit or Product Name
© 2009 IBM Corporation
Correlation names
A correlation name is a field reference that identifies a well-defined starting point in the logical message tree and is used in field references to describe a standard part of the tree format.
InputRoot The root of the input message.InputProperties The standard properties of the input message.Environment The structure that contains the current global environment variables that are available to the node. Environment can be read and updated.InputLocalEnvironment The structure that contains the local environment variables for the message passing through the node.InputDestinationList The structure that contains the local environment variables for the message passing through the node.
InputExceptionList
The structure that contains the exception list for the message passing through the node.OutputRoot The root of the output message.
Business Unit or Product Name
© 2009 IBM Corporation
OutputRoot The root of the output message.
OutputLocalEnvironment The structure that contains the local environment variables that are sent out from the node.
. OutputExceptionList The structure that contains the exception list that the node is generating.
Business Unit or Product Name
© 2009 IBM Corporation
Local environment tree structure
The local environment tree is a part of the logical message tree in which you can store information while the message flow processes the message.
The root of the local environment tree is called LocalEnvironment. This tree is always present in the input message, it is created when a message is received by the input node. Some input nodes create local environment fields, others leave it empty.
Business Unit or Product Name
© 2009 IBM Corporation
Environment tree structure
The environment tree is a part of the logical message tree in which you can store information while the message passes through the message flow.
The root of the environment tree is called Environment. This tree is always present in the input message; an empty environment tree is created when a message is received and parsed by the input node. You can use this tree as you choose, and create both its content and structure.
Business Unit or Product Name
© 2009 IBM Corporation
Exception list tree structure
The exception list tree is a part of the logical message tree in which the message flow writes information about exceptions that occur when a message is processed.
The root of the exception list tree is called ExceptionList, and the tree consists of a set of zero or more exception descriptions. The exception list tree is populated by the message flow if an exception occurs. If no exception conditions occur during message flow processing, the exception list that is associated with that message consists of a root element only. This list is, in effect, an empty list of exceptions.
The exception list tree can be accessed by other nodes in the message flow that receive the message after the exception has occurred. You can modify the contents of the exception list tree only in a node that provides an interface to modify the outbound message tree; for example, the Compute node.
Business Unit or Product Name
© 2009 IBM Corporation
“Original Error type information is found in the innermost exception child structure”
Business Unit or Product Name
© 2009 IBM Corporation
When a process ends abnormally (an abend or dump), an entry is made in the syslog, or the Windows Event log. If there is more data to be written than is appropriate for the log, a new file is created to contain it, and the log entry tells you the file name.
WebSphere Message Broker abend files
Abend files are located in /var/mqsi/common/errors directory
Business Unit or Product Name
© 2009 IBM Corporation
1. Start trace .
mqsichangetrace <brokername> -u -e <egroup> -f "<Message Flow Name>" -l debug -r -c 50000
<brokername> is the name of your broker <egroup> is the name of your execution group You can also start tracing, by going to Operations tab, and right click Message Flow, and click Start Trace
2. Put a message on the input node queue to cause the failure to occur.
3. Stop trace.
mqsichangetrace <brokername> -u -e <egroup> -f "<Message Flow Name>" -l none
You can also stop tracing, by going to Operations tab, and right click Message Flow, and click Stop Trace
4. Retrieve the trace log for the specified component.
mqsireadlog <brokername> -u -e <egroup> -f -o flowtrace.xml
5. Format XML tracefile.
mqsiformatlog -i flowtrace.xml -o userflowtrace.txt
The userflowtrace.txt will be in the current working directory.
ACCESS THE INFORMATION LOGGED IN USER TRACE
Business Unit or Product Name
© 2009 IBM Corporation
Exception handling paths in a message flow
QUESTION....
Business Unit or Product Name
© 2009 IBM Corporation
QUESTION....
Un message flow necesita guardar Errores en un archivo, cómo Se puede implementar esto en el Message broker Toolkit?
Business Unit or Product Name
© 2009 IBM Corporation
Message flow statistics and accounting data
Message flow statistics and accounting data can be collected to record performance and operating details of one or more message flows.
Message flow statistics and accounting data captures dynamic information about the runtime behavior of a message flow. For example, it indicates how many messages are processed and how large those messages are, as well as processor usage and elapsed processing times. The statistical data is collected and recorded in a specified location when an event occurs, such as when a snapshot interval expires or when the execution group that you are collecting information about stops.
Sets the Environment.Broker.Accounting.Origin tree element to identify the origin.
When you request accounting origin support for collecting message flow accounting and statistics data on the mqsichangeflowstats command, you must also configure your message flows to provide the correct identification values that indicate what the data is associated with.
Business Unit or Product Name
© 2009 IBM Corporation
MQSI COMMANDS TO STUDY
mqsireportbrokermqsilistmqsistartmqsistopmqsisetdbparmsmqsichangepropertiesmqsiapplybaroverridemqsicreateconfigurableservicemqsichangeflowstatsmqsireadbarmqsicreatemsgdefsmqsideploymqsichangebrokermqsichangetrace
Business Unit or Product Name
© 2009 IBM Corporation
Introducing IBM WebSphere Process Server (WPS)
WebSphere Process Server (WPS) is one of the key and core products in the IBM WebSphere BPM suite. Referring back to the key capabilities needed for a successfully process-driven integration approach enabled by SOA, WPS addresses capabilities including Business Process Execution, Business Rules, Enterprise Service Bus, and a key enabler for Business Process Monitoring. WPS platform provides a standards-based uniform programming model for representation of data, invocation of services, and structure of composite applications. It provides a unified tooling, namely, WebSphere Integration Developer (WID) for the visual development of composite applications
Business Unit or Product Name
© 2009 IBM Corporation