Skip to main content

WSO2 ESB usage of get-property function

What are Properties?

WSO2 has a huge set of mediators but property mediator is mostly used mediator for writing any proxy service or API.

Property mediator is used to store any value or xml fragment temporarily during life cycle of a thread for any service or API.

We can compare “Property” mediator with “Variable” in any other traditional programming languages (Like: C, C++, Java, .Net etc).

There are few properties those are used/maintained by ESB itself and on the other hand few properties can be defined by users (programmers). In other words, we can say that properties can be define in below 2 categories:

  • ESB Defined Properties
  • User Defined Properties.

These properties can be stored/defined in different scopes, like:

  • Transport
  • Synapse or Default
  • Axis2
  • Registry
  • System
  • Operation

Generally, these properties are read by get-properties() function. This function can be invoked with below 2 variations.

  • get-property(String propertyName)
  • get-property(String scope, String propertyName)

1st function doesn’t require to pass scope parameter, which always reads propetries from default/synapse scope.

Performance Hit (Found in WSO2 ESB 4.9.0 and prior versions):

It has been discovered that use of get-properties() function degrades performance drastically for any service.

Why it happens?

Get-Properties() function first does ESB Registry look-up and then later on difference scopes, however, using scope identifiers limits its search to the relevant area only.

Solution (Scope-Style Reading):

Instead of using get-properties() function these properties can be referenced by below prefixes separated by colon

  • $ctx – from Synapse or Default Scope
  • $trp – from Transport scope
  • $axis2 – from Axis2 Scope
  • $Header – Anything from Header
  • $body – for accessing any element in SOAP Body (applicable for SOAP 1.1 and SOAP 1.2)

Example:

Lets assume that there is any property set with name “Test-Property”

From Default Scope

<property name=”Read-Property-value” expression=”get-property(‘Test-Property’)”/>

<property name=”Read-Property-value” expression=”$ctx:Test-Property”/>

From Transport Scope

<property name=”Read-Property-value” expression=”get-property(‘transport’,’Test-Property’)”/>

<property name=”Read-Property-value” expression=”$trp:Test-Property”/>

From Axis2 Scope

<property name=”Read-Property-value” expression=”get-property(‘axis2′,’Test-Property’)”/>

<property name=”Read-Property-value” expression=”$axis2:Test-Property”/>

We should prefer to use blue colour format for accessing these properties for better performance.

Please note this syntax is not applicable for few ESB defined properties, like: OperationName, MessageID, To
It will work as expected with get-properties, but not with $ctx.

So, please make sure you are using correct way for accessing ESB define properties.

Comments

Popular posts from this blog

How to setup an WSO2 API manager distributed setup with a clustered gateway with WSO2 ELB

In this blog post I am going to describe about how to configure a WSO2 API Manager in a distributed setup with a clustered gateway with WSO2 ELB and the WSO2 G-REG for a distributed deployment in your production environment. Before continuing with this post, you need to download the above mentioned products from the WSO2 website. WSO2 APIM - http://wso2.com/products/api-manager/ WSO2 ELB - http://wso2.com/products/elastic-load-balancer/ Understanding the API Manager architecture API Manager uses the following four main components: Publisher Creates and publishes APIs Store Provides a user interface to search, select, and subscribe to APIs Key Manager Used for authentication, security, and key-related operations Gateway Responsible for securing, protecting, managing, and scaling API calls Here is the deployment diagram that we are going to configure. In this setup, you have 5 APIM nodes with 2 gateway...

WSO2 ESB tuning performance with threads

I have written several blog posts explaining the internal behavior of the ESB and the threads created inside ESB. With this post, I am talking about the effect of threads in the WSO2 ESB and how to tune up threads for optimal performance. You can refer [1] and [2] to understand the threads created within the ESB. [1] http://soatutorials.blogspot.com/2015/05/understanding-threads-created-in-wso2.html [2] http://wso2.com/library/articles/2012/03/importance-performance-wso2-esb-handles-nonobvious/ Within this blog post, I am discussing about the "worker threads" which are used for processing the data within the WSO2 ESB. There are 2 types of worker threads created when you start sending the requests to the server 1) Server Worker/Client Worker Threads 2) Mediator Worker (Synapse-Worker) Threads Server Worker/Client Worker Threads These set of threads will be used to process all the requests/responses coming to the ESB server. ServerWorker Threads will be used to pr...

Performance Tuning WSO2 ESB with a practical example

WSO2 ESB is arguably the highest performing open source ESB available in the industry. With the default settings, it will provide a really good performance OOTB. You can find the official performance tuning guide in the below link. https://docs.wso2.com/display/ESB481/Performance+Tuning Above document includes lot of parameters and how to change them for best performance. Even though it provides some recommended values for the performance tuning, that is not straightforward. The values you put in the configuration files will highly reliant on your use case. Idea of this blog post is to provide a practical example of tuning these parameters with a sample use case. For the performance testing, I am using a simple proxy service which iterate through set of xml elements and send request to a sample server and aggregate the responses back to the client. <?xml version="1.0" encoding="UTF-8"?> <proxy xmlns="http://ws.apache.org/ns/synapse"     ...