When do variables persist? - ANSWER Variables persist through all flows unless the event crosses a transport boundary (e.g. making a http request to another flow)
T/F: Subflows can have their own error handling strate
...
When do variables persist? - ANSWER Variables persist through all flows unless the event crosses a transport boundary (e.g. making a http request to another flow)
T/F: Subflows can have their own error handling strategy - ANSWER False
Syntax to fetch a variable - ANSWER #[vars.foo]
What persists when calling from a parent flow to another flow via http request? - ANSWER Not variables
API Interface definition file (API Specification) - ANSWER defines what you call, what you send it, and what you get back
A Web Service - ANSWER The Actual API implementation you can make calls to or interface of that API implementation
An API Proxy - ANSWER An application that controls access to the web service, restricting access, and usage through an API gateway
What persists when calling from a parent flow to another flow via flow reference? - ANSWER Variables
JMS connector - ANSWER connector capable of sending and receiving messages to and from topics and queues
JMS Publish - ANSWER Operation that allows the user to send a message to a JMS Destination
JMS Publish - Consume - ANSWER Operation that allows the user to send a message to a JMS Destination and waits for response either to the provided replyTo destination or to a dynamically created
Language for Choice Decisions - ANSWER dataweave
#[payload.size != 0]
Execution order of functions - ANSWER the last function in the chain is executed first
Calling flows from a DW Expression - ANSWER use the lookup function
{a: lookup("myFlow",{b:"Hello"})}
How to import a function in a module - ANSWER import dasherize from dw::core::Strings
How to import a module - ANSWER import dw::core::Strings
You can call subflows from a dataweave expressions - ANSWER false
map - ANSWER Iterates over items in an array and outputs the results into a new array.
Scatter gather output - ANSWER returns a collection of all results, collection is an object of objects
each object contains attributes and payload
validation module - ANSWER can use to check whether something has or not been met and you can halt the flow if that condition has not been met
Mule defualt error handler - ANSWER used if no error handler defined
implicitly and globally handles all messaging errors thrown in Mule applications
stops execution of the flow and logs information about the error
cannot be configured
Error object properties - ANSWER error.description = string
error.errorType = an object
Error types - ANSWER identified by a namespace and an identifier
example:
http:unauthorized
ns ident
Most general error type parent - ANSWER ANY
Default success response from HTTP Listener - ANSWER the payload
a status code of 200
Default error repsonse from HTTP Listeners - ANSWER error description
a status code of 500
On Error Propogate - ANSWER at the end of the scope the rest of the flow is not executed
the error is rethrown to the next level and handled there
HTTP Listener returns an error response
On Error Continue - ANSWER at the end of the scope the rest of the flow is not executed
the event is passed up to the next level as if the flow execution had completed successfully
HTTP Listener returns asuccessful response
Error scope execution order - ANSWER the error is handled by the first error scope whose condition evaluates to true
Handling errors at a processor level - ANSWER Try Scope to encapsulate the processors you want to have a try catch
On Error Propogate behavior in try catch - ANSWER rest of try scope is not executed
transaction is rolled back
error is rethrown
On Error Continue behavior in try catch - ANSWER Rest of the try scope is not executed
transaction is committed
event is passed up to the parent flow which continues
APIKIT Routing flow - ANSWER BaD request 400
not found 404
method not allowed 405
not acceptable 406
unsupported media type 415
not implemented 501
To map to a custom error type - ANSWER go to the http request, look at error mapping and map the corresponding error to the custom error type, which then can be referenced by the type field in the type field of error scope handling
Messaging error - ANSWER thrown when a mule event is involved. These errors can be handled using the standard error handlers and scopes
System Error - ANSWER thrown when a mule event IS NOT involved. These type of errors occur during start up or when a connection to an external system fails. These errors are handled by the system error handling strategy and cannot be configured. For all types of system errors, logs the error. For connection type errors, logs and also executes the reconnection strategy for the specific connector (set in advanced settings)
Data model can consist of what types if data - ANSWER Objects, arrays, simple literals
XML details - ANSWER Can only have one top level value and that value must be an object with on property
map input - ANSWER can be JSON or JAVA
Format date - ANSWER someDate as DateTime {format: "yyyyMMddHHmm"}
Format string/num - ANSWER price as Number as String {format: "###.00"}
Connectors for working with files - ANSWER File (for locally mounted file system)
FTP
FTPS
SFTP
All have the same set of operations and they behave almost identically
JMS Queues - ANSWER A sender sends messages to a queue and a single receiver pulls the message off the queue
the receiver does not need to be listening to the queue at the time the message is sent
(point to point or 1:1)
JMS Topics - ANSWER A publisher and all active subscribers receive the message
subscibers not actively listening will miss the published message (unless messages are made durable)
(publish/subscribe or 1:many)
Batch job variables - ANSWER variables created before a batch step are record specific
variables created inside a batch step are record specific
Record fails in batch step - ANSWER Stop processing entire batch (default)
continue processing the batch
continue processing the batch until a max number of failed records is reached
C4E - ANSWER Companies need a way to introduce processes and manage change to make sure that IT projects don't proliferate in the shadows. At the same time, they must keep the road smooth for innovation throughout the business. It is possible, believe it or not, for these seemingly irreconcilable goals to co-exist.
GET - ANSWER retrieves the current state of a resource in some representation
POST - ANSWER creates a new resource
DELETE - ANSWER Deletes a resource
PUT - ANSWER replaces a resource completely
if the resource doesnt exist a new one is created
PATCH - ANSWER partially updates a resource
200 - ANSWER OK
GET DELETE PATCH PUT
201 - ANSWER CREATED
POST
304 - ANSWER Not modified
[Show More]
