At this introductory session, Marcin Nowiński covers the basics of MuleSoft Composer, where he explains use cases, the tool's pros and cons, and how it can be incorporated into the organization to speed up the development of integration.
5. ● Chief Integration Architect at PwC Poland
● MuleSoft Mentor
● 16+ years of experience (6+ with MuleSoft)
https://www.linkedin.com/in/marcin-nowinski-13ab7310/
5
Marcin Nowiński
Speaker
Your Photo
6. ● Subject Matter Expert at PwC Poland
● MuleSoft Ambassador
● MuleSoft Meetup Leader for Warsaw, Poland
● Working with MuleSoft products for over 10 years now
Organizer
Check out my integration blog
https://ambassadorpatryk.com/blog
6
7. Share the event
● Share the Meetup in your social media
● Tag the event using
#MuleSoftMeetup
#WarsawMuleSoftMeetup
Thanks ☺
7
11. What is Hyperautomation
12
● Business-driven approach to automation
● Combination of use cases
○ Integrations
○ API Management platforms
○ RPA
○ Low-code (no code) integrations
● Task Automation
● Process Automation
“Hyperautomation” is when any process can be automated across teams & across systems.
Task automation
Process
automation
Hyperautomation
13. MuleSoft Hyperautomation packaging
14
Anypoint Platform MuleSoft RPA MuleSoft Composer
Composer Starter N/A N/A 250,000 Tasks / month
SF, TB, Slack Connectors
3 additional connectors
Composer Plus N/A N/A 2,500,000 Tasks / month
SF, TB, Slack Connectors
Unlimited connectors
MuleSoft Automation „Anypoint Lite”
0.5 Production vCores, 0.5
Pre Production vCores
57,000 Automation Credits 57,000 Automation Credits
SF, Tableau, Slack
Connectors
3 Additional Connectors
Anypoint Base Subscription 2 Production (v)cores
4 Pre-Production (v)cores
N/A N/A
1 Automation Credit = 2 RPA Bot Minutes = 100 RPA API Calls = 50 Composer Tasks
Composer Task = when a Composer Connector’s flow invokes an action e.g. Read, Create, Update, Delete
Both pre-production and production consumption is counted against production quota
14. Composer
15
● Low-Code proces automation tool
● Based on Mulesoft Anypoint Platform
● Web based GUI
● Either standalone (MuleSoft Composer) or built in within Salesforce
● Simple to use (targeted for non IT teams – admins, business analysts)
● Simplified used case
● Point to point integrations
15. When to use MuleSoft products
16
MuleSoft RPA
● Automating manual repetitive tasks involving UI or desktop applications (e.g., Excel, web browser)
● Accessing legacy, terminal-only systems
● Automating processes that require a “human in the loop” or involve reading data without defined syntax or OCR data
● LoB SMEs use point and click UIs to create Automation processes
● Last mile in hybrid automation solution
MuleSoft Composer
● Integrating SaaS systems using pre-built, IT-approved connectors (Workday, Slack, …)
● Orchestrating multi-step automations and integrations using clicks instead of code – ??
● LoB SMEs use point and click UIs to create integrations.
Anypoint Platform
● Implementing API-led connectivity or event platform (Kafka, Anypoint MQ, …)
● Producing composable assets
● Integrating with DevOps processes
16. When not to use MuleSoft products
17
MuleSoft RPA
● Accessing a system via the UIs in order to bypass approved APIs and controls
● Using bots to create point-to-point integrations between systems
● Automating applications that cannot be installed on or accessed by a Windows RPA bot
● High volume, bulk/ETL data transfer
MuleSoft Composer
● Integrating on-premise systems
● Implementing complex integrations or data transformations that require coding
● High volume, bulk/ETL data transfer
Anypoint Platform
● Consuming data from user interfaces
● Simple integration of SaaS systems with available Composer connectors ??
● Disposable assets that cannot be discovered or consumed by the rest of the organization
17. Typical scenarios of interactions
18
HTTP request from Anypoint Mule flow to RPA Manager
● Anypoint Mule can submit "start process" command Including a command payload, e. g. a correlation ID
● Anypoint Mule can inquire process status
● RPA publishes interface definitions of its APIs in the Anypoint Exchange
HTTP requests from MuleSoft RPA Bot to Anypoint API endpoint
● Bot can retrieve API responses (poll for status)
● Bot can submit commands or propagates events
HTTP request from Composer to RPA Manager
● Composer can submit "start process" command
● Composer can inquire process status
HTTP request from Composer to Anypoint API endpoint
● Composer can retrieve data from Anypoint API.
18. Composer – Create a flow
19
● Step 1: Choose or create a connection
● Step 2: Choose a trigger
● Step 3: Define the actions you want to take
● Step 4: Test your flow on one record
● Step 5: Activate the flow
● Step 6: Monitor the behavior of your flow
20. Additional thoughts on Composer
(personal view)
21
• Very simple too use
• Might help organizations with busy IT
• Only for non critical data integration
• P2P integration, no API-led connectivity
• Public flows and no environments
• Hard to debug - no direct log access
• No CI / CD support
25. Share your knowledge
● Become a speaker and share your knowledge with our community
● Submit your idea via this form:
https://tinyurl.com/become-speaker
via email patryk.bandurski@gmail.com
or
28
26. ● Share:
○ Tweet using the hashtag #MuleSoftMeetups
○ Invite your network to join: https://meetups.mulesoft.com/warsaw/
● Feedback:
○ Fill out the survey feedback and suggest topics for upcoming events
○ Contact MuleSoft at meetups@mulesoft.com for ways to improve the program
What’s next?
29