First Three Weeks at WSO2

Though leaving the uni life and uni friends and switching to the career life feels very sad

I would like to say it was an awesome time period ,I was able to experience during my first three weeks at WSO2.

I started my career from 13th of September 2010.

The first week at WSO2 was full of different experiences including Introduction program,Two-days WSO2 conference,Discussion about products with customers and the fabulous WSO2 birthday party.

The second week began with dividing new comers to teams.I was allocated to GS (Gadget Server)team.

Our team is for developing a web based portal as a dashboard solution to integrate WSO2 back-end products and more as gadgets.

At the first day of WSO2,we were given laptops and the first thing that I was done as a task ,is installing Ubuntu.Since I'm new to Ubuntu environment,I had to get familiarized with friends' support.

Then I started to get the Carbon product to my machine.First I checked out the Carbon product from the trunk and then built it successfully.Though it took couple of days to finish by fixing some build errors.

Since my Product Manager was getting study leave from my second week at WSO2,he gave me a task to do during that time.For that as the initial step, I got familiarized with jQuery,Json,JSP and JavaScript technologies.

During working on this task,I was able to participate some training sessions and get a better idea about OSGI framework,Create OSGI bundles, Importance of OSGI bundles,about Axis2,about WSDL and Web services,Create web services in different ways,etc.

Finally I would say,it's really a great opportunity to start my career from WSO2 and wants to ensure myself as a permanent member of WSO2 family after probation period. :)

Comments

Passing end-user details from client to real backend endpoint via JWT token

In real-world business system,WSO2 API Manager useful on exposing company APIs, in a secured and controlled manner with the features provided by APIManager as; OAuth support [To secure API invocations] Throttling support [To control API invocations] Monitoring support [To track API usage] More technically what happening is when a user sends a particular API request,it will goes to WSO2 APIManager node and from there,the request will route to the real implemented back-end endpoint of the particular API and get back the response and returned it to the API invoked user. There can be a use-case,that this back-end endpoint may expect the details of API invoked user as to pass those details to some internal company usage as; Additional authentication/authorization Track usage data from an internal system. So how to support above requirement from WSO2 AM. There comes the use of JSON Web Token[JWT] implementation done inside WSO2 AM. JWT is a means of representing claims to...

Covid19 - A threat against traditional Banking

I would like to start this blog post by wishing all of you to be safe from Covid19 and wish all infected ones safe speedy recovery from the decease.. Due to the global pandemic situation, 'working from home' , "delivery food/goods to your homes" and importantly "purchases via digital money" have been become the norms for the situation. Thinking further this global epidemic situation has made a huge opportunity for banks on digitalizing projects. As I expressed earlier "purchases via digital money" is the norm which banks has to rethink about their current offerings. For "purchases via digital money" ,Open Banking is the main capability that banks should have.Open Banking has become a global trend during last few years due to the regulations and obligations set by law in different regions as EU, AU. From the experiences with closely worked on open banking field the common observation which I felt was banks tried to become open ba...

How to rollback/commit processing messages from WSO2 ESB when enabled JMS transaction

This blog post describes the below use-case where WSO2 ESB 4.6.0 act as the intermediate channel in-between two JMS queues. The Use-case First messages will be de-queue to a proxy service deployed in WSO2 ESB from an queue in ActiveMQ message broker. Then inside ESB,the incoming messages will undergo with some message mediation flow and then the message will be send to another JMS queue deployed in JBoss server. Inside the ESB,following failures could be happen; a) Failures during message mediation process failure inside ESB [for example if you use dbreportmediator/lookup mediator inside mediation flow,some times failures can happen due to database connection failures] b) Message sending failure,due to endpoint is unavailability.[For example,the JBoss ...

Open Space

Search This Blog