E-mail
|
Key
This line was removed.
This word was removed. This word was added.
This line was added.
|
Changes (1)
View Page History
...
{section} !Bottom-exchange-overview-page2.png|thumbnail!
* The message type.
* The message content.
* The total transfer duration of the exchange (in .ms).
* A table displaying key/value of each normalized message property.
* A table showing attachment name of each normalized message attachment.
h3. Exchange and correlation searching
This new functionality it's very useful, because it's allows you to perform database searching
from a +correlation identifier+, either from an +exchange message identifier+.
The search is carried out on _Petals ESB side_, and if a result is returned to the Webconsole
it will be displayed.
The search may have a some impacts in your architecture, like *late response*, *bad localisation*
*of informations* but also more *network traffic generation*.
The result may be two different types:
* Searching error, which informs you that the search request doesn't
have found anything, both for the correlation identifier search or
exchange identifier search.
* Searching result, if a correlation identifier search have have +several+
+message exchanges+ as a result, *one list of these message exchanges*
will be displayed. If a search by message exchange identifier found +only+
+one+ result, *the overview page* of this exchange will be displayed to you.
In the following screen you can provide a _message exchange identifier_ in the searching
textbox, and select _exchangeID_ for searching type.
!search_by_exchange_id1.png|thumbnail!
After clicking on Submit if Petals ESB side return a result, you normally see +the message+
+exchange overview+ (of the searching message exchange identifier) displayed by the Petals
Webconsole.
!search_by_exchange_id2.png|thumbnail!
For the search by correlation identifier you just have +to know the correlation id+ for the search you
want to achieve, set it in the searching textbox and select _correlationID_ for searching parameter.
!search_by_correlation_id1.png|thumbnail!
After clicking on Submit if Petals ESB side return a result, you normally see the list of all
message exchanges which +are include in the same common flow+ (with the correlation
identifier of your previous searching request)
!search_by_correlation_id2.png|thumbnail!
h3. Common flow notions
In the Webconsole you have now the possibility to visualize several message exchange include
in the same common flow. For example if you have a use case that take in account several
message exchanges passing between the BC Filetransfert, EIP and BC SOAP, the common flow
will contain the globality of message exchanges transited between these components.
!BUS_mini2.png|thumbnail!
This function allows you to follow up the beginning of one use case activity until the end, by
visualizing all message exchanges transited during the process.