One of the benefits of being a consultant is having the opportunity to work with a lot of different clients, many just beginning their journey with MuleSoft and API Led Enablement. In this article, I will share some of the observations and findings that I have seen that have enabled this journey to be more successful.
API Manager 2.x has support for environments which correspond to those defined within Anypoint Platform for the Runtime Manager (i.e. DEV, QA, PROD). This is an improvement over the 1.x version, which typically required the construction of version names to reflect an environment. With this enhanced functionality comes a bit of complexity during API deployment.
I've downloaded the latest Anypoint Studio(Version 7.1.2) to use on Ubuntu(18.04) and I wasn't able to view pop up dialog windows, for example, when clicking the Exchange button. This blocked me because of the several pop up dialogs you need to configure single components.
The batch scope within a MuleSoft application enables the ability to process a message as a batch, splitting the incoming payload into individual records to be processed. While the default values within this scope can be used, considerations around what these default values provide along with implications of these chosen values are explained within this article.
The batch scope configurations to be discussed are limited to just the General configurations. For reference, the default values for this configuration are shown below:
MuleSoft’s Dallas API Workshop was an educational and enlightening day dedicated to exploring the value and potential of APIs and harnessing the power of API-led development. Throughout the intervening week, we’ve found ourselves returning again and again to the day’s theme to extract and absorb every last insight. One can hardly overstate what APIs represent for the future of business agility or their centrality to digital transformation.
MuleSoft’s 2017 CONNECT is shaping up to be a great one. So many opportunities to gain insights from MuleSoft experts, hands-on learning and networking opportunities, as well as learning about new MuleSoft capabilities. See my blog for further details regarding top sessions and workshops at CONNECT.
With MuleSoft Connect right around the corner, now is a good time to develop your strategy for sessions and workshops to attend. The workshops, as noted below, require pre-registration, so be sure to sign up sooner rather than later so you won’t miss out.
To help you develop your strategy, AVIO has created a list of top 3 sessions and workshops to attend. Our focus for these picks is on learning about the new tools and features, along with expanding your MuleSoft knowledge.
A tenet of any integration toolset is the ability to interact with databases. With standards in place, this for the most part is fairly easy. But sometimes, the particulars of a database can create some unexpected complexity. One example of this is an integration solution developed within Mulesoft that invokes Oracle PL/SQL stored procedures and functions. In this scenario, knowing about some of the complexity beforehand will ensure less frustration by a developer during the development phase.