DecipherMiddleware

 A database is the most commonly used backend in the integration world. We often build a lot of integrations with databases (be it as a source or target system). Likewise, working on a proof-of-concept, we always find it hard to have a database that we can use on a local machine or on the cloud. If we install a database on a local device it will consume a lot of resources. Not only that connecting from a cloud integration platform i.e. MuleSoft cloudhub is always tricky. Oracle has an always free-to-use Autonomous Database instance available on the cloud with limited features but is really a powerful database to use. We would say, it is one of the best suitable for doing proof of concepts and validation before working on an actual use case. We thought of giving it a try to connect MuleSoft to the Free version of the Autonomous Oracle database. We created a free trial account for Oracle and an always-free autonomous database instance. Once we have the instance created, we can connect

 One of the items on my bucket list was to do a live stream. This item always went to procrastinate bucket. There were multiple reasons for it. First, the most apparent one is "FEAR", fear of doing something new that I never tried before. Then comes the second hurdle, okay now I have decided I will do it but what topic shall I pick.  Now whatsoever topic you choose, you will see someone in some part of the world has already delivered that topic. Okay, now for instance topic is also decided, and now how to engage the audience when you cannot see them. And after getting answers to all the questions, what if you are stuck and things are not moving in the middle of the stream? The damn tense situation you are in. So, in this blog, I will discuss my first-time experience on a live stream. First-time experiences always hold importance in your life and are it good or bad are always remembered. I did my first live stream on the MuleSoft community twitch channel and Twitter 🥳🥳🥳🎉

 Numbers are a simple data type, but become complex in real-time integration transformation scenarios. Number data type, we consider number system in base 10 and perform all kinds of arithmetic operations e.g. +, -, *, / etc. We do this starting in childhood: multiply two numbers, divide one number by another, or add two numbers. Now, where is the tricky part 🤔?  Let’s start with, various tricky aspects and possible remedies to these. This article is published on the MuleSoft Community  LinkedIn page. To continue reading please visit the below link. https://www.linkedin.com/pulse/mule-4catch-numeric-exceptions-inside-dataweave-mulesoftcommunity Please share your valuable feedback 😊😊😊

 The number 11, we call it eleven in the decimal system. Still, it can be a representation of three in a binary system or it can be seventeen in a hexadecimal system. The actual value of a number depends on the base it is calculated. It is interesting changing the base changes the value of the representation. Let us assume in some integration flow we are getting values in binary number system but target system accepts values in a decimal system or hexadecimal system or vice versa. Examples depicting values in various number systems: # DECIMAL BINARY HEXADECIMAL OCTAL BASE 10 BASE 2 BASE 16 BASE 8 I 5 101 5 5 II 14 1110 E 16 III 54 110110 36 66 IV 123 1111011 7B 173 V 240 11110000

 While developing integrations in BPEL 12c, XSLT is most commonly used to transform different XML message structures. We generally come across scenarios wherein based on specific input fields, our transformation logic changes. What we generally do is have all conditions within the same XSLT file. This makes our XSLT look a lot bigger and difficult to maintain. A better way would be to have different XSLTs and move deciding factor out of XSLT. Once we create different XSLTs for specific use cases having the same output format, now the question will come how to configure these XSLTs to be picked at runtime? This blog is curated with answers to such and many more questions. Let's take the example of account creation. There is a source application sending account information in an XML document which we need to update in a backend database. Now source system can send different types of address information like home address, business address, or shipping address. We get this information