What is our primary use case?
The main use cases for SAP Integration Suite are popular because its predecessor, PIPO, is going to sunset in two years, prompting companies to move to Integration Suite to integrate their cloud solutions.
The most popular use case is to create hybrid integrations between cloud solutions and some on-premise solutions which customers are still using.
What is most valuable?
The best features of SAP Integration Suite include being up-to-date because SAP invests heavily to support the most current technologies, and it's more flexible than its predecessor.
The popularity contributes significantly because there are many resources developed by partners, SAP, and the community, so development does not start from scratch.
SAP Integration Suite's event-driven architecture has helped automate processes by providing better scalability, performance, and organization compared to point-to-point methods.
What needs improvement?
Areas that could be improved with SAP Integration Suite include tools for monitoring and separated error analysis.
Some reports contain everything, leading to difficulty in finding particular messages, requiring custom fields to filter out.
The reporting should be improved, and currently, performance metrics, statistics, and other essential features require Cloud ALM.
In PIPO, there were complex and effective tools to measure performance and how messages were processed, but Integration Suite still does not have solid reports that are useful for evaluating and understanding possible bottlenecks.
It is essential to predict potential problems in advance, not just react to errors after they occur.
For how long have I used the solution?
I have used SAP Integration Suite for more than three years.
What do I think about the stability of the solution?
I evaluate the suite's integration patterns as getting more mature, as they are evolving.
Five years ago, there was less content and limited support for some adapters, but currently, SAP has fixed this.
How are customer service and support?
I rate SAP support for their Integration Suite an eight out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I used other solutions for integration and API management before, including Google Apigee and SAP PIPO.
The main differences between Google and SAP are that for API management, they are quite similar, but Google has more sophisticated reporting for API usage, while SAP adds additional reports and features.
With Google, you manage APIs but do not orchestrate or have a cloud integration engine.
You deal with proxies rather than flows, which are usually more complicated because a flow can contain calls to external systems, enrichment, and splitting and routing, making Apigee perfect for API management, though it lacks the orchestration part.
How was the initial setup?
The initial setup of SAP Integration Suite is very easy.
Which other solutions did I evaluate?
I have not had experience with Teradata, Boomi, or SnapLogic; however, Boomi is also a powerful integration tool but not specifically SAP focused.
What other advice do I have?
I work in consulting with experience across different industries, including retail, banking, mining, and manufacturing.
SAP Integration Suite is more popular for large enterprises.
SAP is less popular for medium businesses in North America, but in Europe, SAP is popular for middle enterprises as well.
I leverage pre-packaged content from the SAP API Business Hub, which sometimes fits perfectly, while at other times custom development is necessary.
SAP Integration Suite's support for connecting legacy systems with modern applications is effective and flexible.
SAP encourages customers to use the most up-to-date technologies rather than staying with older ones, but the support remains comprehensive.
Machine learning capabilities will play a significant role in testing, as considerable effort is spent testing integrations and providing regression tests.
Machine learning is used for API anomaly detection and sometimes for creating integration flows.
While it isn't crucial for developers to create and design integration flows themselves, machine learning will play a role in automated testing, especially in generating test data.
Integration involves dealing with SAP and the external world, including Salesforce, WMS software, custom solutions, partner software, or EDI.
Understanding the other side and specifications is crucial while elaborating the architecture that allows scaling and avoiding errors.
Beyond Integration Suite, I am primarily familiar with S/4 and ECC, older solutions such as PIPO and Solution Manager, and have applied Cloud ALM for monitoring.
Application Lifecycle Management (ALM) manages the entire lifecycle of an application, serving as the next version of Solution Manager.
It provides templates and guidelines to organize implementation.
My primary focus is configuring monitoring to get alerts and notifications regarding incidents.
With integration, alerts must be aggregated wisely without receiving thousands of emails about the same problem.
It's important to group metrics and understand system functionality beyond simple up or down status, as certain components may experience bottlenecks during high requests.
Monitoring helps reduce manual oversight and automates many processes.
I rate SAP Integration Suite eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?