The implementation project has identified a need to retrieve and update data from the energy provider s legacy billing application The customer is already a MuleSoft customer, but they also use middleware technology from another supplier
What approach should you recommend to build this integration to the legacy billing application?
26 comments · newest first
LI
Lisbeth
11 months ago
A is definitely the most efficient approach here.
BA
Barrett
11 months ago
D? Really? Another partner? That’s surprising!
CO
Cordell
12 months ago
C could work, but custom Java? Seems risky.
JU
Junita
12 months ago
I disagree, B is way too complicated for this.
LI
Linette
1 year ago
A sounds like a smart move, leveraging existing templates!
RE
Reuben
1 year ago
Introducing another integration partner, like in Option D, might complicate things further. I feel like we should try to utilize what we already have with MuleSoft.
KI
Kiley
1 year ago
I think defining APIs first, as mentioned in Option C, could be a solid approach, but I'm a bit uncertain about the need for custom Java code.
AN
Annice
1 year ago
I'm not sure about building a custom integration from scratch like in Option B. That sounds time-consuming and risky.
JE
Jerry
1 year ago
I remember we discussed the importance of leveraging existing assets in AnyPoint Exchange. Option A seems like a good starting point.
DO
Donte
1 year ago
Bringing in a specialized integration partner could be a good idea, especially if the customer is already using middleware from another supplier. They might have some useful experience and tools to leverage.
MA
Marguerita
1 year ago
Defining APIs in both systems and then writing custom Java code could work, but that might be overkill for this use case. I'd want to explore some more out-of-the-box integration options first.
LO
Louvenia
1 year ago
Hmm, I'm not sure if building a custom UI and data model is the best approach here. That could end up being a lot of extra work, and we'd need to make sure it aligns perfectly with the legacy system.
LU
Lucina
1 year ago
This seems like a pretty straightforward integration problem. I'd start by looking for any existing templates or assets on Anypoint Exchange that could give me a head start.
TA
Taryn
2 years ago
I'm leaning towards option D, bringing in a specialized integration partner could save us time and resources in the long run.
BE
Benedict
2 years ago
I disagree, I believe option C is the best choice as it involves defining APIs and custom Java code for integration.
LA
Lauran
2 years ago
Option D? Are you kidding me? Bringing in another partner is like adding a third wheel to a bicycle. No, thank you!
SH
Shawn
2 years ago
C) Start by defining APIs in both Salesforce and the legacy billing system, and then build custom Java code to implement a point-to-point integration
CL
Clarence
2 years ago
A) Go to Any point Exchange and search for energy assets (to locate templates for previously built integrations with billing systems), and then enhance these assets
LO
Louvenia
2 years ago
I'm going to have to go with Option C. Defining APIs and writing custom Java code is the way to go. It's the only solution that truly integrates the legacy system.
KA
Karima
2 years ago
Introducing a new systems integration partner is just adding another layer of complexity. Let's keep it simple and use MuleSoft's capabilities.
SH
Sheridan
2 years ago
A) Go to Any point Exchange and search for energy assets (to locate templates for previously built integrations with billing systems), and then enhance these assets
WI
Wilda
2 years ago
C) Start by defining APIs in both Salesforce and the legacy billing system, and then build custom Java code to implement a point-to-point integration
BE
Benedict
2 years ago
A) Go to Any point Exchange and search for energy assets (to locate templates for previously built integrations with billing systems), and then enhance these assets
DA
Dana
2 years ago
Building a custom, point-to-point integration from scratch is a lot of work and risk. I'd rather leverage the existing middleware technology and APIs.
NI
Nickole
2 years ago
Option A seems like the easiest and most efficient approach. Why reinvent the wheel when MuleSoft already has pre-built integrations for energy assets?
CH
Christoper
2 years ago
I think we should go with option A, it seems like the most efficient approach.