Home

1.        What is Mulesoft and Why to use Mulesoft? ·        Integration platform to help businesses connect data, applications and devices across on-premises and cloud computing environments. ·        API tools to implement API, micro services and API Management.       2.        What is Mule message/event – what it contains. Mule Message:  (Mule 3)                                         Mule Event: (Mule 4) 3.        Different type of variables in Mule 3? How these are going to work in Mule 4? Variables: (Mule 3) ·        Flow Variables - Flow Variables can pass from one Flow to another only when using a flow reference component. ·        Session Variables - Session Variables cannot cross HTTP CONNECTOR but they can cross VM CONNECTOR. ·        Record Variables - They can persist across multiple batch steps but not in the source (Load and Dispatch) or the On Complete phase. In Mule 4 there is no such variables, there is only one variable.

Introduction Starting from Studio version 7.4, you will be able to import an API specification from Anypoint Exchange and scaffold interfaces. The specification’s RAML file will be added to Studio as a read-only dependency, this will give you better clarity regarding the version management provided by Exchange. One of the most demanded features in Anypoint Studio 7.4 is “API Sync.” This new feature replaces the APIkit with similar functionality that is more in line with an API specification’s lifecycle. Overview Create and publish an API We are following the API design-first approach, so let’s create a simple API which specifies two resources called /bank/account with GET, POST and DELETE methods. /bank/account/{accountNumber} with GET, PUT and DELETE methods.   Next, we publish this initial version to Exchange. Once published, the API specification is available in the Exchange (but also in Anypoint Design Center). Scaffold interfaces in Anypoint Studio In

What is the maximum memory storage for CloudHub logs? CloudHub stores logs of up to 100 MB per application and per worker. Please find more information here: https://docs.mulesoft.com/runtime-manager/viewing-log-data#_about_log_persistence You may also consider using Anypoint Monitoring's Log feature, which provides 200GB storage per production core and the storage is shared globally for all your applications within Anypoint Monitoring. Please refer to Anypoint Monitoring Log FAQ for more details if you plan to use Anypoint Monitoring. Note that this feature is separate from CloudHub logging feature as described here and requires Titanium Subscription. What happens when this limit is reached? When this limit is reached older logs are overwritten by newer logs. Can we store more than 100 MB of logs if we use bigger workers? No, the size of the log is exact the same for all the Mule workers (no matter the vCore assignment). Is there any time limit for log persisten

Introduction CloudHub provides access to log data that includes deployment messages and events for each worker. Logs and diagnostics are currently available only for applications deployed to CloudHub workers. In cases where applications are deployed using the Runtime Manager local server, you can send data to External Analytics Software. Applications deployed to Pivotal Cloud Foundry (PCF) don’t expose any log data through Runtime Manager, but you can see event logs on Pivotal’s UI. Overview View Logs In Runtime Manager, click Applications in the left menu, then click the application that is deployed to CloudHub to open its management options. In the left menu, click Logs . The application logs are displayed. The Deployments section on the right of the logging screen lets you selectively view the output by day, deployment, system log, and workers. You can unapply a filter by unticking the checkbox next to a date.