Adsense

January 14, 2021

Filter complex array using dw2-Mule4

Hello friends,

In this article I will show you how we can filter results from complex Arrays. In this use-case we will use select and descendent operators from Mulesoft dataweave.

In this use-case we will try to find out the Book details which is at-least rented once from Library. We will see some variations to dataweave expressions in below section.



Input Payload:

[
  {
    "bookId": "20200114",
    "bookType": "Fiction",
    "title": {
      "en": "Candide"
    },
    "message": {
      "en": ""
    },
    "bookDetails": [
      {
        "label": {
          "en": "Candide"
        },
        "Library": {
          "city": "Pune",
          "rented": {
            "count": "1"
          }
        }
      }
    ]
  },
  {
    "bookId": "20200115",
    "bookType": "Fiction",
    "title": {
      "en": "The Alchemist"
    },
    "message": {
      "en": ""
    },
    "bookDetails": [
      {
        "label": {
          "en": "The Alchemist"
        },
        "Library": {
          "city": "Kolkata",
          "rented": {
            "count": "0"
          }
        }
      }
    ]
  }
]

DW Script:
%dw 2.0
output application/json
---
payload[?($.bookDetails.Library.rented.count[0] >= "1")] default []


Output:
[
  {
    "bookId": "20200114",
    "bookType": "Fiction",
    "title": {
      "en": "Candide"
    },
    "message": {
      "en": ""
    },
    "bookDetails": [
      {
        "label": {
          "en": "Candide"
        },
        "Library": {
          "city": "Pune",
          "rented": {
            "count": "1"
          }
        }
      }
    ]
  }
]


Now let us understand the dataweave script in some details:

filter-complex-array-dw-script
DW-Script

We can add multiple conditions inside red brackets based on our requirement.
For example if we want to add filter books based on Library location. We can use
expression like below:

%dw 2.0
output application/json
---
payload[?(($.bookDetails.Library.rented.count[0] >= "1") and ($.bookDetails.Library.city[0] == "Pune"))] default []
%dw 2.0
output application/json
---
payload[?(($.bookDetails.Library.rented.count[0] >= "1") and ($.bookDetails.Library.city contains "Pune"))] default []

Here, important thing to understand about [0] inside red-brackets. Actually we either need
to use [0], because as we have already said in diagram that it iterates and evaluates each
record and give output result or contains operator to evaluate the condition. Also, when
we are having any count check and compare like "> or <" contains operator will not work.


When we are using selectors for filtering data with one more variation in expression.
Let's see some more variation where we can use descendent operator to evaluate
the results.

%dw 2.0
output application/json
---
payload[?(($..count[0] >= "1") and ($..city[0] == "Pune"))] default []
%dw 2.0
output application/json
---
payload[?(($..count[0] >= "1") and ($..city contains "Pune"))] default []


Results will remain same with expression used with descendent and contains operator.

Happy Learning:)
Read More »

January 10, 2021

How to lookup CSV table using Dataweave2

 Hello Friends, 

In this article we will see how to lookup CSV file data without converting it to xml/json or any other message format.

Let's take one example where we need to lookup data from CSV file and retrieve/filter results from the dataset. Here, we will take one very common dataset with employee details information and then we will filter the data with some set of desired condition.


CSV table Input

Name Location Pincode
Niral Pune 910002
Nikku Pune 910005
Shruthi Bhopal 843001
Manpreet Chandigarh 890021
Little John Mumbai 200011
Harry Delhi 100011
Tom Goa 500110

DW Script:

%dw 2.0
output application/json
---
(payload filter ((item, index) -> item.Location == "Pune"))


Output:
[
  {
    "Name": "Niral",
    "Location": "Pune",
    "Pincode": "910002"
  },
  {
    "Name": "Nikku",
    "Location": "Pune",
    "Pincode": "910005"
  }
]


In above example we are filtering data based on location. Here, we have not converted csv data in json before using filter. You can also store the results in dataweave vars and use those results based on your use-cases. 

Please find below some variations having same output as results:
%dw 2.0
output application/json
---
payload filter ($.Location == "Pune")


You can have multiple conditions also. Below expression, we are retrieving data from csv file inside project. You can use readUrl to load csv data from classpath and then use filter  based on Location and Pincode.
 
%dw 2.0
output application/json
var fiterResult= readUrl("classpath://csvFiles/ProfileDetails.csv","application/csv") filter ($.Location == "Pune" and $.Pincode == "910005")
---
fiterResult

Output:
[
  {
    "Name": "Nikku",
    "Location": "Pune",
    "Pincode": "910005"
  }
]



Happy Learning :)

Read More »

January 05, 2021

Validation module indepth - Mule4

 Introduction:

Mulesoft has provided a bunch of validation components which is very useful for message field validation during developments. These validations can be general or based on specific requirements. Validators are used to verify that parts of the Mule message/events to meet some kind of criteria which we specify.

If a message doesn't meet the validation criteria, validation component generates Validation error. Here, we can customize the exception message that is displayed in logs/responses.

Let's see some of important and frequently used validation components

mule4-validation-module
mule4-validation-module

Is not null:

This components checks if the field value should be not null or else throws' error with "Name is Mandatory field"

<validation:is-not-null value="#[payload.name]" message="Name is Mandatory field"/>

Is email:

This components checks if the incoming email field is in valid format or not else throws validation error with message "Invalid Email format".

<validation:is-email email="#[payload.email]" message="Invalid Email format"/>

ALL vs ANY

To perform multiple validation at a time in mule flow. Mulesoft provides two scopes ALL and ANY which is used for these purpose.

ALL:- All validation should be passed from a set validation components defined in ALL scope.

<validation:all>
      <validation:is-not-null value="#[payload.name]" message="Name is Mandatory field"/>
      <validation:validate-size value="#[payload.name]" min="5" max="20" message="Name field size should be between 5 and 20"/>
</validation:all>

Here we are checking name field should not empty and name length should be minimum length 5 and max 20. It is similar to AND conditions like any programming language.

ANY:- Any of the validation components should be passed from a set of Validation components defined in ANY scope

<validation:any>
  <validation:is-not-null value="#[payload.name]" message="Name is Mandatory field"/>
  <validation:validate-size value="#[payload.name]" min="5" max="20" message="Name field size should be between 5 and 20"/>
<validation:any>

With Any scope we are ensuring any of the above condition should pass, it will pass the the validation. It is similar to OR conditions like any programming language.

Based on project requirement we can used these scopes with multiple validation components at a time.


Use of validation module Dataweave:

Now let us see how we can use these mule validation components can be used as Mule expression to make decisions without throwing any validation errors.

<choice>
   <when expression="#[ Validation::is-not-null(payload.name) and Validation::is-not-null(payload.name)]">
	<set-payload value='#[payload.name ++ " is a valid name."]'/>
   </when>
   <otherwise>
        <set-payload value='#[payload.name ++ " is NOT a valid name."]'/>
   </otherwise>
</choice>


Happy learning :)

Read More »

January 01, 2021

WSO2 Basic Overview

WSO2 Introduction:

WSO2 is an open-source technology provider which offers an enterprise platform for integrating application programming interfaces (APIs), applications, and web services locally and across the Internet.

WSO2 solutions give enterprises the flexibility to deploy applications and services on-premises, on private or public clouds, or in hybrid environments and easily migrate between them as needed.

WSO2 Platform:

WSO2 platform provides 3 main products to design and maintain application.

API Manger, Enterprise Integrator and Identity Server

WSO2-products
WSO2-products



API MANAGER

Api Manager helps to design and consume APIs. API Gateway helps to manage API requests and apply policies to them. API rate limiting feature helps to regulate traffic and secure against security attacks. API security provide Authentication and authorize features to API requests. 

API Manager provides Analytics feature to monitor application behavior and 

API management platform is available for on-premises, cloud, and hybrid architectures.




ENTERPRISE INTEGRATOR
Enterprise integrator provides hybrid integration platform. It enables API-centric integration using integration architecture styles such as microservices or centralized ESB.
 
WSO2 Enterprise Integrator is having 2 different architectural styles:
  • Micro Integrator: It is event-driven standard message based engine. It supports message routing, transformation and other type messaging use-cases. Micro integrator is used when you need centralized, API-driven integration architecture. Micro integrator can also be used where you need a decentralized cloud-native integration like Microservices and where you need low-code integration and application monitoring.


















  • Streaming Integrator: It is very useful for performing ETL (Extract, Transform, Load) and where streaming operations required. It provides real time analysis of streamed data with the help of SQL-like query languages. Streaming integrator is fully compatible with systems like Kafka and NATS to full utilize of stream data. It has native support to work with WSO2 Micro integrator to trigger complex integration flows.


Benefits of WSO2 ESB

  • Ensures loosely coupled solution with easy to manage plug-ins.
  • Suited for Scalable design.
  • It provides agile incremental solutions for development, early/often deployment, and seamless change management.
  • Configuration driven design, as opposed to code driven design.

IDENTITY SERVER

WSO2 Identity server is an open source API-driven tool which provides CIAM(Customer identity and access management) solutions effectively.
It is extensible, highly scalable platform which helps to manage identities at both cloud and enterprise environments. With CIAM solutions, it gives enhanced, seamless, and secure digital experiences.






Happy Learning :)
Read More »

December 30, 2020

.NET key concepts and introduction of .NET Core

What is .NET Core? Is this the future of .NET? Is this will obsolete the existing platform? Is this backward compatible? If all this are buzzing in your mind, please take a cup of coffee and go through the below topic, I promise you when you have your last sip of coffee you will have brief idea about this booming topic.

Basic of .NET

.NET is a free, open-source development platform for building many kinds of apps. .NET is open source, using MIT and Apache 2 licenses. A .NET app is developed for and runs in one or more implementations of .NET. .NET Framework, .NET 5 (and .NET Core), and Mono are the three most important implementations of .NET. Below are the key concepts of .NET.

 

What is .NET Standard?

There are various implementations of .NET. Each implementation allows .NET code to execute in different places—Linux, macOS, Windows, iOS, Android, and many more. .NET Standard is a formal specification of the APIs that are common across all these .NET implementations.

The relationship between .NET Standard and a .NET implementation is the same as between the HTML specification and a browser. The second is an implementation of the first.

Each .NET version has an associated version of the .NET Standard. .NET Standard is defined as a single NuGet package because all .NET implementations are required to support it. Tooling becomes easier because the tools have a consistent set of APIs to use for a given version. You can also build a single library project for multiple .NET implementations.


.NET Ecosystem

.NET includes the below components for each implementations:

.NET Ecosystem



.NET Implementations

There are four .NET implementations that Microsoft supports:

.NET Implementations


 Glimpse of .NET Implementations

.NET Implementations

What to choose when? (.NET Framework and .NET 5(including .NET Core))

Microsoft maintains both runtimes for building applications with .NET, and they share many of the same APIs. This shared API is what is called the .NET Standard.

.NET 5


Pick .NET 5

ü  If there is a new application to build, and have a choice between .NET Core and .NET Framework, .NET Core is the way to go.

ü  If the application need cross platform implementation(Windows, Linux, and macOS)

ü  Microservice architecture supported, so it allows the cross platform service developed under .NET framework, Ruby, Java etc communicate within another

ü  Containers are the VMs of today. .NET Framework can be used on Windows containers but .NET core is more modular, flexible and lightweight and after containerize because of it’s cross platform nature it can deploy in various Docker(ex:- Linux Docker containers)

ü  .NET CORE is one of the best performing one among web based frameworks in terms of performance and scalability 


Pick .NET Framework

ü  If existing application is .NET framework and there is no mind to change it

ü  The old technologies are using in the project which are not yet incorporated in .NET CORE(ASP.NET webforms , Visual Basic and F#)

ü  In cases where the libraries or NuGet packages use technologies that aren't available in .NET Standard or .NET 5 then it is required the .NET framework.


Happy Learning :)

Read More »