Enterprise Integration is a bit challenging and the field is moving so fast that nobody is able to follow what is going on. That is what Integration Podcast covers.
We focus on the SAP Integration platforms from SAP PI/PO, SAP Cloud Integration, API Management, Gateway and Cloud Platform. There are so many different tools, on which you must be looking to understand what is relevant.
We also are cover the other techniques going on to make sure that your Enterprise works.
Daniel Graversen has worked with SAP Integration for 15+ years. Over the years, there have been several frustrations about how to make different software and tools work optimally for the customers.
Daniel is an SAP Mentor and a part of the community around SAP.
Daniel is both developing software for SAP Integration, blogging about integration and migration, training people in using the tools, and advising companies in getting the most out of their SAP Integration.
Subscribe now
Episodes
017 – What to expect at SAPPHIRENOW 2018 from a integration perspective
Podcast: Play in new window | Download
Subscribe: Apple Podcasts | RSS
Next week is SAPPHIRENOW in Orlando, and I’m looking forward to going there to see what is happening with Integration. SAPPHIRENOW is SAPs biggest event with a focus on what new SAP Software customers should be investing in. The conference has a big focus on the business values that SAP is providing and provide good roadmaps of what is to come.
In this episode of the podcast, I’ll be covering my expectations of SAPPHIRENOW and also something about the sessions that are most interesting from an integration perspective.
Last year SAP announced SAP Leonardo as their platform for handling all the cool new things like blockchain, IoT, Big Data and more. I guess it was mostly a branding of their Cloud Platform and some of the services so people could see it was something new.
I’m looking forward to seeing what is coming out of new things from the conference.
I have created a list of the sessions that look most promising from an integration perspective. The list originally appeared on my blog on SAP community.
| Session ID | Title | Info | |
| ASUG11011 | Integration Architecture for Hybrid System Landscapes | Thu 12:30 p.m. – 01:30 p.m. |
|
| PL60858 | Adopt Winning Strategies for Cloud Integration | Thu 03:00 p.m. – 03:40 p.m. |
|
| PL60859 | Support Rapid Innovation with Straightforward Access to APIs | Tue 11:00 a.m. |
|
| ASUG10522 | APIs and Integration Strategy for SAP S/4HANA Cloud |
|
|
| LE59486 | Discover Extensions and APIs That Drive the Intelligent Enterprise | Wed 01:00 p.m |
|
| ASUG11987 | Integrating SAP S/4HANA Cloud: Road Map and Current Capabilities | Wed 01:00 p.m |
|
| BA60744 | Drive Transformation with Robotic Process Automation and SAP S/4HANA Cloud | Thu 01:00 p.m |
If you have an idea of sessions I forgot please share in the comments.
016 – Building a reliable SAP PI landscape
Podcast: Play in new window | Download
Subscribe: Apple Podcasts | RSS
In this episode, I’ll share some of the different ideas and techniques that I have seen at customers locations.
Integration services are so important to the business that you must find a way to run SAP PI/PO all the time. It is one of the key things to consider how you can make a good distribution of your system and the workloads. And also be able to support the upgrades/patches as well as configuration as easy as possible.
In the podcast, I mention some different setups they can be combined with a different setup to suit what you want to achieve and how it is best for your organization.
- One installation on multiple instances or server nodes. This is SAPs way of scaling the system. They are all linked but allow you to restart single servers or instances and distribute among the servers. You cannot specify where an integration should run.
- Multi productive PI systems to handle the different flow. Then you can patch one while the others are running. It requires some extra maintenance
- Decentral Adapter Engine. Where all systems are connected to one central system that allows you to distribute workload and just have one place for configuration.
- Preprod failover. Where you are using your reproductive system as a way to have a hot-hot failover. It does require some extra configuration of the scenarios on the PreProd system but gives you some benefits if you want to switch to it.
If you have another idea please post a comment below then others can learn from it.
015 – Workflow in SAP Cloud Platform with DJ Adams
Podcast: Play in new window | Download
Subscribe: Apple Podcasts | RSS
I’m excited to welcome DJ Adams to The Integration Podcast this week. DJ has been working with SAP software for more than 30 years. He was an SAP Mentor for many years but has since retired to become an SAP Mentor alumnus. DJ has shared a lot on the SAP Cloud Platform Workflow. He has also written a series of blog posts on the subject where he is using the platform to find which beers he needs to drink next. With my background on the SAP PI systems and BPMs there now is a gradually transitioning to the cloud so DJ’s experience is hugely valuable for my work.
DJ first started working on R/2 on IBM mainframes in the 1980’s and has been working with SAP software ever since. He has been fascinated by the cloud platform and has worked with systems outside of the SAP world including Google App Engine. He never worked much with PI but the workflow service is very closely related to SAP BPM.
Getting started with Workflow is really easy. It’s available as a trial account on the Cloud Platform. Users can easily enable it along with the Portal Service and the full stack Web IDE. You need to define your workflow definitions. You need nothing other than a web browser to access those services.
The workflow service is about orchestrating services and tasks across applications but also across systems, organizations, and individuals. There is a service task building block that effectively gives you the ability to make HTTP calls. You also have script tasks that will let you mess around with the context of the data of the workflow instance. There is also a mail task. Then there is the most important step type in a workflow definition which is the user task. Those let you send tasks to a user to let them be able to interact with that workflow instance.
You don’t need to code very much in the UI when you’re first getting started. But if you are going to do any meaningful workflows you will need to do some coding to create user task interfaces for the SAP Fiori My Inbox app, which is a master-detail style app. The user task components you build are injected into the component container in the My Inbox app when tasks are selected for processing. You need to know some SAPUI5 in order to do that, but the team plans to release a forms-based facility to create user task interfaces in the future.