How to use message properties component
Download as pptx, pdf0 likes135 views
This document discusses using message properties in Mule applications. It provides an example Mule configuration file that demonstrates setting message properties in different scopes and logging their values. The example shows setting a property in the session scope and outbound scope in one flow, and accessing the same properties from the inbound scope in a second flow to illustrate how message properties propagate between flows.
1 of 7
Download to read offline
![• .mflow
• <?xml version="1.0" encoding="UTF-8"?>
• <mule xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:vm="http://www.mulesoft.org/schema/mule/vm"
xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation"
xmlns:spring="http://www.springframework.org/schema/beans" version="EE-3.4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
• http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
• http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/current/mule-vm.xsd
• http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd">
• <flow name="MessagePropertiesFlow1" doc:name="MessagePropertiesFlow1">
• <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8089" path="messageproperties" doc:name="HTTP"/>
• <message-properties-transformer scope="session" doc:name="Message Properties">
• <add-message-property key="property1" value="studio"/>
• </message-properties-transformer>
• <message-properties-transformer scope="outbound" doc:name="Message Properties">
• <add-message-property key="property2" value="mule"/>
• </message-properties-transformer>
• <logger message="--flow1--#[message.outboundProperties['property2']]--#[sessionVars['property1']]" level="INFO" doc:name="Logger"/>
• <vm:outbound-endpoint exchange-pattern="request-response" path="messageproperties" doc:name="VM"/>
• </flow>
• <flow name="MessagePropertiesFlow2" doc:name="MessagePropertiesFlow2">
• <vm:inbound-endpoint exchange-pattern="request-response" path="messageproperties" doc:name="VM"/>
• <logger message="---flow2--#[message.inboundProperties['property2']]--#[sessionVars['property1']]" level="INFO" doc:name="Logger"/>
• </flow>
• </mule>](https://image.slidesharecdn.com/howtousemessagepropertiescomponent-160326153551/85/How-to-use-message-properties-component-4-320.jpg)
![• Output:
• INFO 2015-10-03 16:00:23,705 [[messageproperties].config.change.14.thread.1] org.mule.DefaultMuleContext:
• **********************************************************************
• * Application: messageproperties *
• * OS encoding: Cp1252, Mule encoding: UTF-8 *
• * *
• * Agents Running: *
• * Clustering Agent *
• * JMX Agent *
• **********************************************************************
• INFO 2015-10-03 16:00:23,706 [[messageproperties].config.change.14.thread.1]
org.mule.module.launcher.MuleDeploymentService:
• ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
• + Started app 'messageproperties' +
• ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
• INFO 2015-10-03 16:00:26,480 [[messageproperties].connector.http.mule.default.receiver.02]
org.mule.api.processor.LoggerMessageProcessor: --flow1--mule--studio
• INFO 2015-10-03 16:00:26,482 [[messageproperties].connector.http.mule.default.receiver.02]
org.mule.lifecycle.AbstractLifecycleManager: Initialising: 'connector.VM.mule.default.dispatcher.771015974'.
Object is: VMMessageDispatcher
• INFO 2015-10-03 16:00:26,482 [[messageproperties].connector.http.mule.default.receiver.02]
org.mule.lifecycle.AbstractLifecycleManager: Starting: 'connector.VM.mule.default.dispatcher.771015974'. Object
is: VMMessageDispatcher
• INFO 2015-10-03 16:00:26,489 [[messageproperties].connector.http.mule.default.receiver.02]
org.mule.api.processor.LoggerMessageProcessor: ---flow2--mule--studio](https://image.slidesharecdn.com/howtousemessagepropertiescomponent-160326153551/85/How-to-use-message-properties-component-5-320.jpg)
Ad
Recommended
Message properties component in mule
Message properties component in mulejaveed_mhd This document discusses using message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a session property in one flow and an outbound property in another, then logging both properties in each flow to see how they are passed between flows and transformed to an inbound property.
How to use message properties component
How to use message properties componentmdfkhan625 The document discusses how to use message properties in Mule applications. It provides an example Mule configuration file that demonstrates setting message properties in different scopes and logging their values. The configuration contains two flows, one that sets session and outbound properties and logs them, and another that receives the message and logs the now inbound property and session property.
How to use message properties component
How to use message properties componentmaheshtheapex This document discusses how to use message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties with different scopes and logging their values. The flow shows setting a session property in one flow and an outbound property, then accessing them as an inbound property in a second flow to illustrate how message properties work across flows.
Wildcard Filter
Wildcard Filtersivachandra mandalapu This document discusses using a wildcard filter in a Mule application. It shows an XML configuration for a flow that uses a wildcard filter to check if the payload contains the letter "m", ignoring case. If it matches, it logs "Success", otherwise processing stops. The document also provides the URL to trigger the flow and explains that the wildcard filter checks the payload against the pattern "*m*" before allowing the message to continue.
Expression filter in Mule
Expression filter in MuleMohammed246 The document discusses using expression filters in Mule applications. It provides an example Mule configuration file that uses an expression filter to check the value of a session variable and route the message to a second flow if the value is not equal to "mule". The output shows the message being logged in both flows, demonstrating that the expression filter passed the message to the second flow since the session variable value was "mule studio" rather than just "mule".
Data Mapper
Data Mappersivachandra mandalapu This document discusses using a DataMapper transformer in Mule applications. DataMapper transforms data from one format to another. The example shows a flow that uses a JDBC connector to execute a SQL query, transforms the results using a DataMapper configuration, and logs the output. Upon receiving an HTTP request, it connects to a database, runs a select statement, maps the results to a new format defined in a graph, and prints the transformed payload.
Splitter
Splittersivachandra mandalapu The document discusses using the Splitter component in Mule applications. The Splitter splits an incoming message into fragments based on an expression and sends each fragment to the next processor. This allows processing message parts asynchronously and then reassembling them using an Aggregator. An example flow splits an XML shipment order message by item title and logs the results.
Filter expression in mule
Filter expression in muleRajkattamuri This document demonstrates how to use expression filters in Mule applications. It shows an example Mule configuration file with two flows, one that sets a session property and logs it, and another that is called conditionally by the first flow via a VM endpoint based on the expression filter evaluation of the session property. The output log shows the session property being set and logged in both flows, demonstrating the expression filter functionality.
Salesforce
Salesforcesivachandra mandalapu This document provides an example of using the Salesforce connector in Mulesoft to query an Account by ID from Salesforce and output the results. The example flow hits an HTTP endpoint, uses the Salesforce connector configured with a username/password to query for a specific Account by ID, and logs the response. It provides the XML configuration and output showing the Account details being returned from Salesforce.
Bean as Datasource
Bean as Datasourcesivachandra mandalapu The document discusses using a Bean as a data source in Mule's database connector. It shows an XML configuration that defines a Bean pointing to a SQL Server database, and uses it to configure the database connector. It then demonstrates a flow that exposes an HTTP endpoint, uses the database connector to execute a SQL select query, and logs the results.
How to use expression filter
How to use expression filter Praneethchampion This document provides an example of how to use an expression filter in Mule applications. It shows XML configuration with two flows, one that sets a session property and logs it, and another that is called by the first flow via VM connector if the session property value is not equal to "mule". The output logs from both flows are displayed, demonstrating the expression filter functionality.
Defining global exception strategies
Defining global exception strategiessivachandra mandalapu This document discusses defining global exception strategies in Mule applications. It provides an example Mule flow that references a global catch exception strategy, which sets a 400 status code and error payload when exceptions occur. The example shows log output for valid and invalid token inputs, with the invalid input triggering the global exception strategy. References are provided to the Mule documentation on error handling.
Collection aggregator
Collection aggregatorsivachandra mandalapu The document discusses using a collection aggregator in Mule applications. It provides an example Mule flow that uses a HTTP listener, splitter, collection aggregator, and logger. The flow splits an XML payload containing multiple items, aggregates them into a collection, and logs the result. It also notes that the collection aggregator will fail if items are not received within a timeout period.
Property place holder
Property place holdersivachandra mandalapu This document discusses how to use property placeholders in Mule applications. It provides an example Mule configuration file that defines a property placeholder for environment-specific properties files. When the flow is triggered, it will load the properties from the correct file based on the environment variable specified in mule-app.properties. The document aims to demonstrate how to configure properties using placeholders in Mule.
How to use expression filter
How to use expression filterAnand kalla The document discusses using expression filters in Mule applications. It provides an example Mule configuration file that uses an expression filter to check the value of a session variable and route the message to a second flow if the value is not equal to "mule". The output shows the message being logged in both flows, demonstrating that the expression filter passed the message to the second flow since the session variable value was "mule studio" rather than just "mule".
Mapping and listing with mule
Mapping and listing with muleAnand kalla Mule ESB allows storing data in variables that can be accessed throughout a flow or entire application. Lists and maps can be defined as Mule variables similarly to Java by using square brackets. Values are retrieved from lists by index and from maps by key. An example demonstrates defining a list and map variable, reassigning list values, and logging all values.
Anypoint data gateway
Anypoint data gatewayAnand kalla Anypoint Data Gateway allows users to integrate data from legacy back-office systems like SAP, Oracle, and SQL into Salesforce through a simple point-and-click interface without extensive coding. It supports instant connections to various data sources and automatically retrieves and configures metadata. The gateway is installed via Salesforce AppExchange and its visual designer makes it easy to create and publish connections to external data sources within Salesforce.
Data weave
Data weave Anand kalla The document discusses how to use the DataWeave transformer in Anypoint Studio to transform messages. The DataWeave transformer allows writing transformations using the DataWeave language. It takes the incoming message elements as inputs and performs actions to produce an output message. The editor provides autocomplete, output previews, and generates .dwl files to store the transformation code. Multiple outputs can be defined by adding tabs in the transform section.
Mule esb api layer
Mule esb api layerAnand kalla The document discusses API layers in Mule and their uses. An API layer offers a decoupled interface for interacting with applications through a common language-agnostic way. Common uses of API layers include connecting to legacy systems that lack REST APIs and publishing APIs for partners to communicate with systems. The Anypoint Platform helps build, design, and manage APIs to expose enterprise data securely to various devices and apps. It includes an API gateway to connect to backends behind firewalls, an API manager to manage users and traffic, an API contract manager to issue keys and monitor compliance, and an API policy manager to apply security policies without downtime.
Mule security saml
Mule security samlAnand kalla The document discusses Mule's support for SAML (Security Assertion Markup Language) for exchanging security information between federated systems. It describes how to configure the SAML module in Mule, including adding the SAML JAR, configuring the security manager with key providers and realms, and configuring security filters on CXF endpoints. It also explains the differences between the Sender Vouches and Holder-of-Key SAML profiles.
Mmc rest api user groups
Mmc rest api user groupsAnand kalla This document outlines the REST API operations for user groups in MMC, including creating, getting, updating, and deleting user groups. It also covers getting all user groups and all user group permissions. The operations use HTTP methods like POST, GET, PUT, and DELETE and require authentication via username and password in the URL or headers. CURL examples are provided for each operation.
Maven in Mule
Maven in MuleAnand kalla This document provides an overview of Maven, including:
- Maven is a build tool that manages Java projects and dependencies through XML POM files.
- Projects are built from local and remote repositories of dependencies specified in POMs.
- The document outlines the directory structure for Maven projects including components, source files, and generated artifacts.
- Maven plugins are used to generate documentation, compile code, test, package artifacts and more through goals defined in POM files.
Java in Mule
Java in MuleAnand kalla This document provides an overview and outline of an extensive Java programming course. The course aims to teach students Java syntax, object-oriented programming concepts, exceptions, generics, streams, concurrency, data structures, and build tools to make them proficient Java developers. It contains 12 sections covering these topics through over 12 hours of video lessons. The target audience is programmers and developers looking to build software and systems using Java.
1450 – 1750 changes in belief systems
1450 – 1750 changes in belief systemsAshley Birmingham Protestant Christianity broke from Roman Catholic Christianity in the 1500s and both groups worked to spread their faith to the Americas and Asia. Several Islamic reform movements emerged aiming to reduce corruption and syncretism, including Wahhabism in the 1700s which called for a strict adherence to monotheism and Sharia law. Hinduism saw the Bhakti movement emphasize achieving union with the divine through rituals and songs, while Sikhism blended Hindu and Islamic influences to become its own religion. In China, Buddhism became more accessible to common people and Confucianism experienced a revival under the Ming and Qing dynasties.
A2 evauation 1
A2 evauation 1Lauren Gilbert This document discusses conventions of music videos in the indie/pop genre. It notes that performance is a main focus, with many videos showing the artist/band playing their instruments up close. Narratives are also commonly used to connect visually with the song lyrics and message. Unlike some other genres, indie/pop videos tend to use narrative to convey a single purpose or meaning rather than just attract attention. Close-up shots of instruments and emotional connections between audience and artist are also typical conventions.
Amee - PAPER PRESENTATION ON GAS HANDLING
Amee - PAPER PRESENTATION ON GAS HANDLINGamee terdue Compressed gas cylinders require safe handling practices to prevent accidents and injuries. Key safety practices include: transporting cylinders securely and properly labeled; keeping cylinders away from heat sources; wearing protective equipment when handling cylinders; and never attempting cylinder repairs or modifications. Failure to follow established safety methods for compressed gas cylinders risks creating dangerous environments that could lead to fires, explosions or oxygen depletion.
Actividades procesoadministracion 270116
Actividades procesoadministracion 270116johannaAC El documento describe las actividades clave del proceso de administración de proyectos de software libre, incluyendo la definición del alcance, la priorización de funcionalidades, el establecimiento de estándares, la elaboración del plan del proyecto y la gestión del proyecto a través del seguimiento y la evaluación. También recomienda herramientas para apoyar estas actividades como Trac, XPTracker, Git y Redmine.
Mule esb stripe
Mule esb stripeAnand kalla MuleSoft's Stripe connector allows developers to integrate their MuleSoft applications with the Stripe API to perform payment-related functions like accepting payments, creating invoices and customers. The document provides steps for setting up a Stripe developer account, configuring the Stripe API key, and using the Stripe connector in a Mule flow to create a customer and coupon in Stripe. Sample Mule flows are demonstrated to showcase how to trigger customer and coupon creation via HTTP requests.
More Related Content
What's hot (6)
Salesforce
Salesforcesivachandra mandalapu This document provides an example of using the Salesforce connector in Mulesoft to query an Account by ID from Salesforce and output the results. The example flow hits an HTTP endpoint, uses the Salesforce connector configured with a username/password to query for a specific Account by ID, and logs the response. It provides the XML configuration and output showing the Account details being returned from Salesforce.
Bean as Datasource
Bean as Datasourcesivachandra mandalapu The document discusses using a Bean as a data source in Mule's database connector. It shows an XML configuration that defines a Bean pointing to a SQL Server database, and uses it to configure the database connector. It then demonstrates a flow that exposes an HTTP endpoint, uses the database connector to execute a SQL select query, and logs the results.
How to use expression filter
How to use expression filter Praneethchampion This document provides an example of how to use an expression filter in Mule applications. It shows XML configuration with two flows, one that sets a session property and logs it, and another that is called by the first flow via VM connector if the session property value is not equal to "mule". The output logs from both flows are displayed, demonstrating the expression filter functionality.
Defining global exception strategies
Defining global exception strategiessivachandra mandalapu This document discusses defining global exception strategies in Mule applications. It provides an example Mule flow that references a global catch exception strategy, which sets a 400 status code and error payload when exceptions occur. The example shows log output for valid and invalid token inputs, with the invalid input triggering the global exception strategy. References are provided to the Mule documentation on error handling.
Collection aggregator
Collection aggregatorsivachandra mandalapu The document discusses using a collection aggregator in Mule applications. It provides an example Mule flow that uses a HTTP listener, splitter, collection aggregator, and logger. The flow splits an XML payload containing multiple items, aggregates them into a collection, and logs the result. It also notes that the collection aggregator will fail if items are not received within a timeout period.
Property place holder
Property place holdersivachandra mandalapu This document discusses how to use property placeholders in Mule applications. It provides an example Mule configuration file that defines a property placeholder for environment-specific properties files. When the flow is triggered, it will load the properties from the correct file based on the environment variable specified in mule-app.properties. The document aims to demonstrate how to configure properties using placeholders in Mule.
Viewers also liked (20)
How to use expression filter
How to use expression filterAnand kalla The document discusses using expression filters in Mule applications. It provides an example Mule configuration file that uses an expression filter to check the value of a session variable and route the message to a second flow if the value is not equal to "mule". The output shows the message being logged in both flows, demonstrating that the expression filter passed the message to the second flow since the session variable value was "mule studio" rather than just "mule".
Mapping and listing with mule
Mapping and listing with muleAnand kalla Mule ESB allows storing data in variables that can be accessed throughout a flow or entire application. Lists and maps can be defined as Mule variables similarly to Java by using square brackets. Values are retrieved from lists by index and from maps by key. An example demonstrates defining a list and map variable, reassigning list values, and logging all values.
Anypoint data gateway
Anypoint data gatewayAnand kalla Anypoint Data Gateway allows users to integrate data from legacy back-office systems like SAP, Oracle, and SQL into Salesforce through a simple point-and-click interface without extensive coding. It supports instant connections to various data sources and automatically retrieves and configures metadata. The gateway is installed via Salesforce AppExchange and its visual designer makes it easy to create and publish connections to external data sources within Salesforce.
Data weave
Data weave Anand kalla The document discusses how to use the DataWeave transformer in Anypoint Studio to transform messages. The DataWeave transformer allows writing transformations using the DataWeave language. It takes the incoming message elements as inputs and performs actions to produce an output message. The editor provides autocomplete, output previews, and generates .dwl files to store the transformation code. Multiple outputs can be defined by adding tabs in the transform section.
Mule esb api layer
Mule esb api layerAnand kalla The document discusses API layers in Mule and their uses. An API layer offers a decoupled interface for interacting with applications through a common language-agnostic way. Common uses of API layers include connecting to legacy systems that lack REST APIs and publishing APIs for partners to communicate with systems. The Anypoint Platform helps build, design, and manage APIs to expose enterprise data securely to various devices and apps. It includes an API gateway to connect to backends behind firewalls, an API manager to manage users and traffic, an API contract manager to issue keys and monitor compliance, and an API policy manager to apply security policies without downtime.
Mule security saml
Mule security samlAnand kalla The document discusses Mule's support for SAML (Security Assertion Markup Language) for exchanging security information between federated systems. It describes how to configure the SAML module in Mule, including adding the SAML JAR, configuring the security manager with key providers and realms, and configuring security filters on CXF endpoints. It also explains the differences between the Sender Vouches and Holder-of-Key SAML profiles.
Mmc rest api user groups
Mmc rest api user groupsAnand kalla This document outlines the REST API operations for user groups in MMC, including creating, getting, updating, and deleting user groups. It also covers getting all user groups and all user group permissions. The operations use HTTP methods like POST, GET, PUT, and DELETE and require authentication via username and password in the URL or headers. CURL examples are provided for each operation.
Maven in Mule
Maven in MuleAnand kalla This document provides an overview of Maven, including:
- Maven is a build tool that manages Java projects and dependencies through XML POM files.
- Projects are built from local and remote repositories of dependencies specified in POMs.
- The document outlines the directory structure for Maven projects including components, source files, and generated artifacts.
- Maven plugins are used to generate documentation, compile code, test, package artifacts and more through goals defined in POM files.
Java in Mule
Java in MuleAnand kalla This document provides an overview and outline of an extensive Java programming course. The course aims to teach students Java syntax, object-oriented programming concepts, exceptions, generics, streams, concurrency, data structures, and build tools to make them proficient Java developers. It contains 12 sections covering these topics through over 12 hours of video lessons. The target audience is programmers and developers looking to build software and systems using Java.
1450 – 1750 changes in belief systems
1450 – 1750 changes in belief systemsAshley Birmingham Protestant Christianity broke from Roman Catholic Christianity in the 1500s and both groups worked to spread their faith to the Americas and Asia. Several Islamic reform movements emerged aiming to reduce corruption and syncretism, including Wahhabism in the 1700s which called for a strict adherence to monotheism and Sharia law. Hinduism saw the Bhakti movement emphasize achieving union with the divine through rituals and songs, while Sikhism blended Hindu and Islamic influences to become its own religion. In China, Buddhism became more accessible to common people and Confucianism experienced a revival under the Ming and Qing dynasties.
A2 evauation 1
A2 evauation 1Lauren Gilbert This document discusses conventions of music videos in the indie/pop genre. It notes that performance is a main focus, with many videos showing the artist/band playing their instruments up close. Narratives are also commonly used to connect visually with the song lyrics and message. Unlike some other genres, indie/pop videos tend to use narrative to convey a single purpose or meaning rather than just attract attention. Close-up shots of instruments and emotional connections between audience and artist are also typical conventions.
Amee - PAPER PRESENTATION ON GAS HANDLING
Amee - PAPER PRESENTATION ON GAS HANDLINGamee terdue Compressed gas cylinders require safe handling practices to prevent accidents and injuries. Key safety practices include: transporting cylinders securely and properly labeled; keeping cylinders away from heat sources; wearing protective equipment when handling cylinders; and never attempting cylinder repairs or modifications. Failure to follow established safety methods for compressed gas cylinders risks creating dangerous environments that could lead to fires, explosions or oxygen depletion.
Actividades procesoadministracion 270116
Actividades procesoadministracion 270116johannaAC El documento describe las actividades clave del proceso de administración de proyectos de software libre, incluyendo la definición del alcance, la priorización de funcionalidades, el establecimiento de estándares, la elaboración del plan del proyecto y la gestión del proyecto a través del seguimiento y la evaluación. También recomienda herramientas para apoyar estas actividades como Trac, XPTracker, Git y Redmine.
Mule esb stripe
Mule esb stripeAnand kalla MuleSoft's Stripe connector allows developers to integrate their MuleSoft applications with the Stripe API to perform payment-related functions like accepting payments, creating invoices and customers. The document provides steps for setting up a Stripe developer account, configuring the Stripe API key, and using the Stripe connector in a Mule flow to create a customer and coupon in Stripe. Sample Mule flows are demonstrated to showcase how to trigger customer and coupon creation via HTTP requests.
Mule security jaas
Mule security jaasAnand kalla The document discusses how to configure the JaasSimpleAuthenticationProvider security provider in Mule to use the Jaas Authentication Service. It describes two configuration methods - passing a Jaas configuration file that defines login modules and credentials, or configuring attributes directly on the provider. The Jaas configuration file example shows a file defining a login module, required flag, and authorized users mapped to passwords.
Mule anypoint exchange
Mule anypoint exchangeAnand kalla This document discusses Anypoint Exchange in Mule, listing how it can be classified by products, patterns, difficulty levels, and common business objects. Specifically, it notes that Anypoint Exchange allows for patterns like aggregation, bi-directional integration, and broadcast integration. It also supports common objects like accounts, contacts, leads, opportunities, and products. The document provides information on integrating different systems using Anypoint Exchange in Mule.
Mule soa
Mule soaAnand kalla The document discusses how and why the company selected Mule as their service-oriented architecture, providing examples of Mule use cases and best practices learned. It describes evaluating major open source ESB products based on criteria like support and performance. Testing uncovered some issues with Mule 3.1.1 that were quickly resolved with MuleSoft's help. Examples shown include using Mule as a scalable web application, accessing heterogeneous data sources, and sending support requests. Best practices discussed include test-driven development, customizing Mule's distribution, and staged migration of systems.
Dn indisciplina escola
Dn indisciplina escolapr_afsalbergaria O documento discute a indisciplina nas escolas portuguesas. Aponta que no ano passado houve mais de 9 mil expulsões em 4200 alunos, o que equivale a mais de 200 mil participações disciplinares no país. Defende que reduzir o número de alunos por turma, criar gabinetes multidisciplinares e melhorar a formação de professores pode ajudar a reduzir a indisciplina. Partidos de esquerda concordam com a necessidade de turmas menores.
Ad
Similar to How to use message properties component (20)
Message properties component
Message properties component Sunil Komarapu This document discusses using message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a session property in one flow and an outbound property in another, then logging both properties in each flow to see how they are passed between flows and transformed to an inbound property.
Message properties component
Message properties componentF K This document discusses using message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a session property in one flow and an outbound property in another, then logging both properties in each flow to see how they are passed between flows and transformed to an inbound property.
How to use message properties component
How to use message properties componentprinceirfancivil The document discusses how to use message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a property in the session scope and another in the outbound scope in one flow, then accessing them as an inbound property and session property in a second flow to illustrate how properties propagate between flows.
How to use message properties component
How to use message properties componentirfan1008 The document discusses how to use message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a property in the session scope and another in the outbound scope in one flow, then accessing them as an inbound property and session property in a second flow to illustrate how properties propagate between flows.
How to use message properties component
How to use message properties componentPhaniu The document discusses how to use message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a property in the session scope and outbound scope in one flow, and accessing the same properties from the inbound scope in a second flow.
Mule Message Properties Component
Mule Message Properties ComponentDurga Prasad Kakarla This document discusses using message properties in Mule applications. It provides an example Mule flow that demonstrates setting message properties in different scopes and logging their values. The flow shows setting a property in the session scope and outbound scope in one flow, and accessing the same properties from the inbound scope in a second flow after being passed between the flows.
Message properties component in mule demo
Message properties component in mule demoSudha Ch The document discusses using message properties in Mule applications. It shows an example Mule flow with two flows: Flow1 sets a session property and outbound property, and logs both values. Flow2 receives the message and logs the now-inbound property and session property, demonstrating how the property scope changes between flows. The example illustrates how to use message properties to pass data between flows in Mule.
Message properties component in mule
Message properties component in muleKhan625 The document discusses using message properties in Mule applications. It shows an example Mule flow that uses message-properties-transformer components to add properties with different scopes (session and outbound). The flow displays the values of properties in both the outbound and subsequent inbound messages to demonstrate how message properties function between flows.
Basic example using message properties component
Basic example using message properties componentprudhvivreddy This document describes using message properties in Mule to pass data between flows. It shows adding properties in different scopes using message-properties-transformer, and logging the properties in each flow. The example sets a "property1" session variable and "property2" outbound property in flow1, then flow2 reads the inbound "property2" and session "property1" properties.
Mule message
Mule messageSon Nguyen The document discusses Mule properties and flow variables, explaining:
- Mule properties include inbound properties from incoming messages, outbound properties sent with messages to endpoints, invocation properties within a flow, and session properties spanning message processing.
- A Mule message contains a payload, properties like headers, and optional attachments. Mule reads, transforms and routes messages between applications as an ESB.
- Compared to traditional ESBs, Mule only converts data as needed between applications rather than requiring adapters, reducing development time.
Vm component in mule
Vm component in mulejaveed_mhd The document discusses using the VM component in Mule applications for intra-JVM communication between flows. The VM component uses in-memory queues by default but can be configured to use persistent queues. An example flow is provided that demonstrates a main flow triggering a subflow using the VM component, with log messages output from each flow. Key features of the VM component are that request-response endpoints deliver messages directly in the same thread, while one-way endpoints deliver asynchronously via a queue.
Vm component
Vm componentSunil Komarapu The document discusses using the VM component in Mule applications for intra-JVM communication between flows. The VM component uses in-memory queues by default but can be configured to use persistent queues. An example flow is provided that demonstrates a main flow triggering a subflow using the VM component, and logging messages from both flows. Key features of the VM component like request-response vs one-way messaging and in-memory vs persistent queues are also outlined.
Vm component
Vm componentF K The document discusses using the VM component in Mule applications for intra-JVM communication between flows. The VM component uses in-memory queues by default but can be configured to use persistent queues. An example flow is provided that demonstrates a main flow triggering a subflow using the VM component, and logging messages from both flows. Key features of the VM component like request-response vs one-way messaging and in-memory vs persistent queues are also outlined.
Mule advanced
Mule advancedD.Rajesh Kumar Mule messages contain a header and payload. The header includes properties and variables that provide metadata about the message. Properties have inbound and outbound scopes, while variables have flow, session, and application scopes. Transformers can change the type, content, or properties of a message. Splitters break messages into parts that are routed to different endpoints. Aggregators reassemble split messages using correlation properties. Resequencers reorder messages that were processed out of order to put them back in the correct sequence.
Vm component in mule demo
Vm component in mule demoSudha Ch The document discusses using the VM transport in Mule applications for intra-JVM communication between flows. The VM transport uses in-memory queues by default but can be configured to use persistent queues. An example flow is provided that demonstrates a main flow triggering a subflow using a VM outbound endpoint.
How to use vm component
How to use vm componentmaheshtheapex The document discusses how to use the VM component in Mule applications for intra-JVM communication between flows. The VM transport uses in-memory queues by default but can be configured to use persistent queues. An example flow is provided that demonstrates a main flow triggering a subflow using the VM outbound and inbound endpoints to pass a message between the two flows in the same application.
Mule esb
Mule esbcharan teja R The document provides information on Mule ESB and its core components for handling message structure and flow. It describes how a Mule message contains a header and payload, and how properties and variables provide metadata about messages. It also explains key components like splitters that divide messages, aggregators that combine related messages, and resequencers that reorder out-of-order messages. Transformers are described that can change message types, contents, and properties during flow processing in Mule applications.
Mule esb
Mule esbvishnukanthro45 The document provides information on Mule ESB and its core components for handling message structure and flow. It describes how a Mule message contains a header and payload, and how properties and variables provide metadata about messages. It also explains key components like splitters that divide messages, aggregators that combine message parts, and resequencers that reorder out-of-order messages. Transformers are discussed for changing message types, formats, and properties during flow processing.
Choice component in mule
Choice component in mule Rajkattamuri The document describes how to use the Choice component in Mule applications to conditionally route messages based on message properties or payload values. It provides an example Mule flow that sets a session property, logs it in two flows, and uses the Choice component in the second flow to check the session property value and route the message accordingly. The Choice component allows conditional logic similar to if/else statements.
Mule Choice component
Mule Choice component AbdulImrankhan7 The document describes how to use the Choice component in Mule applications to conditionally route messages based on message properties or payload values. It provides an example Mule flow that sets a session property, logs it in two flows, and uses the Choice component in the second flow to check the session property value and route the message accordingly. The Choice component allows conditional logic similar to if/else statements.
Ad
More from Anand kalla (16)
Unit testing using Munit Part 1
Unit testing using Munit Part 1Anand kalla A unit test is an automated piece of code that invokes a unit of work in the system and checks a single assumption about its behavior. A unit of work spans a single logical functional use case that can be invoked through a public interface, such as a method or class. Unit tests are fully automated, isolated, repeatable, fast, and test a single concept. Frameworks like JUnit and MUnit provide tools for writing unit tests in Java and Mule applications.
Java Fundamentals in Mule
Java Fundamentals in MuleAnand kalla This document introduces an object oriented programming course in Java that will cover core computer science concepts needed to create software applications in Java. The course objectives are listed and include learning Java features and applying OOP principles like encapsulation, inheritance, polymorphism. The course will be divided into units covering Java basics, inheritance, data structures, exception handling, and GUI programming. An overview of Java is also provided, noting its portability, object oriented nature, and standard library of classes and methods.
web services
web servicesAnand kalla The document discusses web services and how they allow different software applications to communicate and share resources despite running on different platforms or using different programming languages. Web services use open standards like XML, SOAP and HTTP to define interfaces and transmit data between applications in a self-contained, platform-independent way. They enable reuse of application components and integration of existing software.
SOAP Service in Mule Esb
SOAP Service in Mule EsbAnand kalla This document provides an overview of web services and related technologies including:
- Web services allow for integration and communication between organizations through standardized XML messaging and protocols.
- A service-oriented architecture uses services that can be discovered and invoked over the web.
- Key technologies that enable web services are XML, XML Schema, SOAP, WSDL, and UDDI. These provide standards for messaging, data description, service description and discovery.
UDDI in Mule Esb
UDDI in Mule EsbAnand kalla The document describes the Universal Description, Discovery, and Integration (UDDI) API, which allows businesses to publish themselves on the internet and discover other businesses. UDDI is an XML-based registry for businesses to publish information on their products and services to allow other businesses to find them. It consists of three elements - businessEntity, businessService, and bindingTemplate - that describe a business, its services, and how to access those services.
WSDL in Mule Esb
WSDL in Mule EsbAnand kalla WSDL is an XML language used to describe web services, defining operations provided by the service, data formats, and location. It describes what a service does via operations, how it is accessed via protocols and data formats, and where it is located via URLs. A WSDL document defines types, messages, operations, bindings and services. Translators can generate code from WSDL or derive WSDL from existing code.
Send email attachment using smtp in mule esb
Send email attachment using smtp in mule esbAnand kalla Mule ESB is a lightweight Java-based integration platform that allows developers to connect applications together quickly and easily. It enables integration regardless of application technologies. The document provides an example of using Mule ESB to send an email attachment by reading a file from a source directory using the SMTP connector and attachment transformer. It describes the prerequisites and provides the full XML configuration for the flow.
Mule oracle connectors
Mule oracle connectorsAnand kalla This document provides summaries of various Oracle connectors available through the MuleSoft Anypoint Platform. It describes connectors for Oracle Service Cloud (RightNow), PeopleSoft, Database, E-Business Suite, Siebel, and a Siebel to Salesforce contact broadcast. The connectors allow integration between these Oracle applications and third party systems, enabling synchronization of data and automation of business processes between Oracle products and other cloud or on-premises applications and databases.
Mule google connectors
Mule google connectorsAnand kalla The document describes Google connectors that can be used to integrate Google services like Prediction, Tasks, Contacts, Calendar, and Spreadsheets with third party applications. It provides details on each connector, explaining how they allow applications to perform operations with the corresponding Google API and sync data between Google services and other applications and systems.
Mule execution
Mule executionAnand kalla The document discusses implementing an example loan broker application using Mule ESB. It provides an overview of the key components involved - a Loan Broker service, Credit Agency service, Lender service, Banking Gateway and individual Bank services. It describes the message flow and how each component is implemented as a Mule endpoint, service or router. It discusses how Mule handles message routing, transformation and correlation to orchestrate the end-to-end request and response processing across the different systems and services.
Mule database-connectors
Mule database-connectorsAnand kalla This document provides information on various database connectors available through Anypoint Platform by MuleSoft. It lists and describes connectors for connecting to databases such as Oracle Database, MySQL, JDBC, PostgreSQL, DB2, and Cassandra. The connectors allow applications to perform CRUD operations on database records and integrate databases with other applications and systems.
Mule batch processing
Mule batch processingAnand kalla Batch processing in Mule allows processing of messages in batches by initiating batch jobs. A batch job splits messages into individual records, performs actions on each record in parallel, and reports results while optionally outputting processed data to other systems. Batch processing is useful for integrating or synchronizing data between applications, extracting-transforming-loading data from flat files to databases, and handling large volumes of API data. Mule's batch feature introduced in 2013 simplifies processing large amounts of data through record-based reporting, error handling, and parallel processing.
Mule architecture
Mule architectureAnand kalla Mule is a lightweight integration platform that enables connecting systems, services, APIs, and devices. It manages message routing, data mapping, orchestration, reliability, security, and scalability between nodes. Mule architecture is based on Enterprise Service Bus concepts and allows applications to communicate by carrying data between them. A Mule flow processes messages through a sequence of message sources, processors, and endpoints to integrate applications on-premise or in the cloud.
Mule soap
Mule soapAnand kalla The document discusses validating SOAP requests against an XSD schema file in Mule. It explains how to use a schema validation filter to validate the SOAP request and throw a custom error message if invalid. The code sample shows placing the filter before the SOAP service, and adding a subflow to handle invalid requests. The schema validation filter refers to the XSD file and validates the request against it.
Mule for each scope header collection
Mule for each scope header collectionAnand kalla The document discusses using a foreach scope to process a list of values passed as a query parameter in a URL. It describes how a Java component can convert a comma-separated string of query parameter values into a list, which can then be iterated over using a foreach scope. The flow listens on an HTTP listener, uses the Java component to convert the query parameter to a list, and then processes that list with a foreach scope to output each value individually.
Mule esb
Mule esbAnand kalla The document discusses Mule Enterprise Service Bus (ESB). Mule ESB is a lightweight Java-based integration platform that allows developers to connect applications together quickly and easily, enabling them to exchange data across various technologies and protocols. It acts as a transit system to carry data between applications within or across organizations. Key capabilities include support for multiple access points and protocols, simplified programming model, and ease of configuration and extensibility.
Recently uploaded (20)
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdf
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdfICT Frame Magazine Pvt. Ltd. Artificial Intelligence (AI) is rapidly changing the face of cybersecurity across the globe. In Nepal, the shift is already underway. Vice President of the Information Security Response Team Nepal (npCERT) and Information Security Consultant at One Cover Pvt. Ltd., Sudan Jha, recently presented an in-depth workshop on how AI can strengthen national security and digital defenses.
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdf
GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now.pdfPriyanka Aash GenAI Opportunities and Challenges - Where 370 Enterprises Are Focusing Now
FIDO Seminar: Evolving Landscape of Post-Quantum Cryptography.pptx
FIDO Seminar: Evolving Landscape of Post-Quantum Cryptography.pptxFIDO Alliance FIDO Seminar: Evolving Landscape of Post-Quantum Cryptography
Raman Bhaumik - Passionate Tech Enthusiast
Raman Bhaumik - Passionate Tech EnthusiastRaman Bhaumik A Junior Software Developer with a flair for innovation, Raman Bhaumik excels in delivering scalable web solutions. With three years of experience and a solid foundation in Java, Python, JavaScript, and SQL, she has streamlined task tracking by 20% and improved application stability.
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025
CapCut Pro Crack For PC Latest Version {Fully Unlocked} 2025pcprocore 👉𝗡𝗼𝘁𝗲:𝗖𝗼𝗽𝘆 𝗹𝗶𝗻𝗸 & 𝗽𝗮𝘀𝘁𝗲 𝗶𝗻𝘁𝗼 𝗚𝗼𝗼𝗴𝗹𝗲 𝗻𝗲𝘄 𝘁𝗮𝗯> https://pcprocore.com/ 👈◀
CapCut Pro Crack is a powerful tool that has taken the digital world by storm, offering users a fully unlocked experience that unleashes their creativity. With its user-friendly interface and advanced features, it’s no wonder why aspiring videographers are turning to this software for their projects.
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance Securing Account Lifecycles in the Age of Deepfakes
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante Delivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.
Powering Multi-Page Web Applications Using Flow Apps and FME Data Streaming
Powering Multi-Page Web Applications Using Flow Apps and FME Data StreamingSafe Software Unleash the potential of FME Flow to build and deploy advanced multi-page web applications with ease. Discover how Flow Apps and FME’s data streaming capabilities empower you to create interactive web experiences directly within FME Platform. Without the need for dedicated web-hosting infrastructure, FME enhances both data accessibility and user experience. Join us to explore how to unlock the full potential of FME for your web projects and seamlessly integrate data-driven applications into your workflows.
Techniques for Automatic Device Identification and Network Assignment.pdf
Techniques for Automatic Device Identification and Network Assignment.pdfPriyanka Aash Techniques for Automatic Device Identification and Network Assignment
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante We live in an ever evolving landscape for cyber threats creating security risk for your production systems. Mitigating these risks requires participation throughout all stages from development through production delivery - and by every role including architects, developers QA and DevOps engineers, product owners and leadership. No one is excused! This session will cover examples of common mistakes or missed opportunities that can lead to vulnerabilities in production - and ways to do better throughout the development lifecycle.
The Future of Technology: 2025-2125 by Saikat Basu.pdf
The Future of Technology: 2025-2125 by Saikat Basu.pdfSaikat Basu A peek into the next 100 years of technology. From Generative AI to Global AI networks to Martian Colonisation to Interstellar exploration to Industrial Nanotechnology to Artificial Consciousness, this is a journey you don't want to miss. Which ones excite you the most? Which ones are you apprehensive about? Feel free to comment! Let the conversation begin!
Lessons Learned from Developing Secure AI Workflows.pdf
Lessons Learned from Developing Secure AI Workflows.pdfPriyanka Aash Lessons Learned from Developing Secure AI Workflows
AI VIDEO MAGAZINE - June 2025 - r/aivideo
AI VIDEO MAGAZINE - June 2025 - r/aivideo1pcity Studios, Inc AI VIDEO MAGAZINE - r/aivideo community newsletter – Exclusive Tutorials: How to make an AI VIDEO from scratch, PLUS: How to make AI MUSIC, Hottest ai videos of 2025, Exclusive Interviews, New Tools, Previews, and MORE - JUNE 2025 ISSUE -
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdf
Oh, the Possibilities - Balancing Innovation and Risk with Generative AI.pdfPriyanka Aash Oh, the Possibilities - Balancing Innovation and Risk with Generative AI
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...Safe Software Utilities and water companies play a key role in the creation of clean drinking water. The creation and maintenance of clean drinking water is becoming a critical problem due to pollution and pressure on the environment. A lot of data is necessary to create clean drinking water. For fieldworkers, two types of data are key: Asset data in an asset management system (EAM for example) and Geographic data in a GIS (ArcGIS Utility Network ). Keeping this type of data up to date and in sync is a challenge for many organizations, leading to duplicating data and creating a bulk of extra attributes and data to keep everything in sync. Using FME, it is possible to synchronize Enterprise Asset Management (EAM) data with the ArcGIS Utility Network in real time. Changes (creation, modification, deletion) in ArcGIS Pro are relayed to EAM via FME, and vice versa. This ensures continuous synchronization of both systems without daily bulk updates, minimizes risks, and seamlessly integrates with ArcGIS Utility Network services. This presentation focuses on the use of FME at a Dutch water company, to create a sync between the asset management and GIS.
Crypto Super 500 - 14th Report - June2025.pdf
Crypto Super 500 - 14th Report - June2025.pdfStephen Perrenod This OrionX's 14th semi-annual report on the state of the cryptocurrency mining market. The report focuses on Proof-of-Work cryptocurrencies since those use substantial supercomputer power to mint new coins and encode transactions on their blockchains. Only two make the cut this time, Bitcoin with $18 billion of annual economic value produced and Dogecoin with $1 billion. Bitcoin has now reached the Zettascale with typical hash rates of 0.9 Zettahashes per second. Bitcoin is powered by the world's largest decentralized supercomputer in a continuous winner take all lottery incentive network.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019 A presentation at Internetware 2025.
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdf
Information Security Response Team Nepal_npCERT_Vice_President_Sudan_Jha.pdfICT Frame Magazine Pvt. Ltd.
You are not excused! How to avoid security blind spots on the way to production
You are not excused! How to avoid security blind spots on the way to productionMichele Leroux Bustamante
How to use message properties component
- 1. Message Properties component in Mule
- 2. Abstract • The main motto of this PPT is how to use Message Properties in our applications.
- 3. Example
- 4. • .mflow • <?xml version="1.0" encoding="UTF-8"?> • <mule xmlns:http="http://www.mulesoft.org/schema/mule/http" xmlns:vm="http://www.mulesoft.org/schema/mule/vm" xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:spring="http://www.springframework.org/schema/beans" version="EE-3.4.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd • http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd • http://www.mulesoft.org/schema/mule/vm http://www.mulesoft.org/schema/mule/vm/current/mule-vm.xsd • http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd"> • <flow name="MessagePropertiesFlow1" doc:name="MessagePropertiesFlow1"> • <http:inbound-endpoint exchange-pattern="request-response" host="localhost" port="8089" path="messageproperties" doc:name="HTTP"/> • <message-properties-transformer scope="session" doc:name="Message Properties"> • <add-message-property key="property1" value="studio"/> • </message-properties-transformer> • <message-properties-transformer scope="outbound" doc:name="Message Properties"> • <add-message-property key="property2" value="mule"/> • </message-properties-transformer> • <logger message="--flow1--#[message.outboundProperties['property2']]--#[sessionVars['property1']]" level="INFO" doc:name="Logger"/> • <vm:outbound-endpoint exchange-pattern="request-response" path="messageproperties" doc:name="VM"/> • </flow> • <flow name="MessagePropertiesFlow2" doc:name="MessagePropertiesFlow2"> • <vm:inbound-endpoint exchange-pattern="request-response" path="messageproperties" doc:name="VM"/> • <logger message="---flow2--#[message.inboundProperties['property2']]--#[sessionVars['property1']]" level="INFO" doc:name="Logger"/> • </flow> • </mule>
- 5. • Output: • INFO 2015-10-03 16:00:23,705 [[messageproperties].config.change.14.thread.1] org.mule.DefaultMuleContext: • ********************************************************************** • * Application: messageproperties * • * OS encoding: Cp1252, Mule encoding: UTF-8 * • * * • * Agents Running: * • * Clustering Agent * • * JMX Agent * • ********************************************************************** • INFO 2015-10-03 16:00:23,706 [[messageproperties].config.change.14.thread.1] org.mule.module.launcher.MuleDeploymentService: • ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ • + Started app 'messageproperties' + • ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ • INFO 2015-10-03 16:00:26,480 [[messageproperties].connector.http.mule.default.receiver.02] org.mule.api.processor.LoggerMessageProcessor: --flow1--mule--studio • INFO 2015-10-03 16:00:26,482 [[messageproperties].connector.http.mule.default.receiver.02] org.mule.lifecycle.AbstractLifecycleManager: Initialising: 'connector.VM.mule.default.dispatcher.771015974'. Object is: VMMessageDispatcher • INFO 2015-10-03 16:00:26,482 [[messageproperties].connector.http.mule.default.receiver.02] org.mule.lifecycle.AbstractLifecycleManager: Starting: 'connector.VM.mule.default.dispatcher.771015974'. Object is: VMMessageDispatcher • INFO 2015-10-03 16:00:26,489 [[messageproperties].connector.http.mule.default.receiver.02] org.mule.api.processor.LoggerMessageProcessor: ---flow2--mule--studio
- 6. • Flow of execution: 1. URL to trigger the service from browser http://localhost:8089/messageproperties 2. In flow1 both outbound and session property is created using message property component 3. Service displays both outbound and session properties in flow1 4. In flow2 the outbound property is changes to inbound proeprty 5. Flow2 displays both inbound and session property