Please enable JavaScript.
Coggle requires JavaScript to display documents.
Mulesoft 2 - Coggle Diagram
Mulesoft 2
`Hay mac loi:
anypoint studio = create implemnation, design center = DESIGN spi specifications
URI parameter = /car, identify resource. Query param = filter, like model=Toyota
-
privateflow vs subflow
private = normal flow but can be aync, can/cannot have source
subflow: no error (sub = kem hon), only sync, no source at all. sub = kem hon
-
-
-
if didnt import all*, must call func specifically. to call: string mnipulation::stringtoupper()
-
-
-
-
ẽamples: !include ẽamples/patient.raml. Example no need to import, just include
/store:
is: [client-id-required] - nothing such as as, plus {} is only for variable
-
type DATA{format=}. not a fun so make sense, only fun are like ()
-
object store = store value from one execution to another execution (visual: store heads after exucutions)
-
c4e = hip, enablement to do sutff, 4 also more hip.
-
PRACTICAL MULE STUFF
-
-
-
-
-
deploy runtime maneger, error -> env not set in runtime
-
-
DEPLOY & MANAGE APIs
-
-
-
API Manager
-
-
access to APIs
out-of-the-box: rate limit, spike ontrol
-
Client ID enforcement
need for REST connector, requires header
-
-
Exam tips
-
-
Chac chan nho
building api implement
-
the question with how many flows APIkit generate, answer is 4 (get get get post) 
-
modifying mule event
send json, return xml, next processor still json
-
API-led differnce: compliance, security, reusability as opposed to point-to-point
-
-
-
for condition, what ever there IS the condition
-
-