Posts

IRT 2.0 Release event. Taking SAP PI/PO Testing to the next level

If I had a big marketing department this invitation would probably look like the unveiling of the new Samsung phone. But since I’m the marketing department it is just some fact. And no cool graphics. I do hope you want to join anyway.

Testing SAP PI/PO is not really fun. It takes way too much time and is challenging. That is the reason I created Figaf IRT. I got the idea for IRT two years and it is time for a new release. We are ready to IRT 2.0 Simpler, Easier and Everywhere.

One of the big challenges has been the deployment of the IRT testing application and the difference between different Java and Netweaver that gave different results. We have therefore spent 3 months planning and rewriting the application to be able to run standalone so customers will be able to run IRT if they have 7.31+.

This enables us to create different models for deployment and license options.

We have a release party on February 8 ( which coincidently also is Daniels birthday).

I will be sharing some of the new features and what it means for licensing models.

You can join by clicking the button below.

And as with all good events, there is a surprise. I’m burning to share this with you also but want to keep the suspense.

SAP Teched takeaways for non developers

SAP Teched is not only for geeks, and the impact is not only for those either. I normally only make a presentation for people that already know alot about SAP Integration platform. Integration is an important topic in the future where customers will be using cloud products and mixing them with their existing systems.

I do recommend watching the video below where I’m covering all the things.

The first part is about SAP Strategy for their integration products. It is crucial to understand when working on your own strategy. They use the ISA-M method to learn from what you are doing to what platforms you should be working with in the future.

API is a big topic that is important to how we are opening our landscapes. They are like BAPI where the B is removed. So it is a common language that all developers can understand and use. You can see all the API SAP has created at http://api.sap.com

The integration product PI/PO that most people are using is not the one SAP has most focus on. The biggest focus is on SAP Cloud Platform Integration (Cloud Integration, CPI or what was HCI) the biggest benefit is that you can get pre delivered content if you want to integration with SAP Cloud Products like Ariba or SuccesFactor. Or for E-Invoicing scenarios for some locations.

SAP Leonardo is also a big topic. For Integration there are 3 important topics

  • IoT(Internet of Things) is about connecting billions of devices, manage and analyze data from them. This is one of the things that SAP is focusing on, they have a platform that allow users to handle all the devices.
  • Machine Learning is about finding algorithms for handling complex tasks and automate them. It could be finding what is on a image or how to book a payment. SAP has some pretrained models that can perform some tasks. Customers can take the models and train them on their own data so they match their requirements.
  • Blockchain is also one of the hyped technologies. SAP has a server you can run and connect with your partners. Then blockchain allow you to have one shared truth of what is happening and everybody agrees on it.

You can watch the slides below

https://www.slideshare.net/DanielGraversen/sap-integration-for-non-developers-teched-2017 

IRT 1.4 Testing big messages in SAP PI/PO

You asked for it. Or our customers asked for it so now we have created it. IRT, our tool to make SAP PI/PO testing easy, has now been upgraded.

I created the following video

We had a customer that requested that we could process 400Mb messages and verify that they worked. We found that the messages about 10Mb were stuck, so we had to find a way around it. The JMS queue we are using, the build into SAP PI/PO has some limits for external clients. So we try to ZIP the payload, and if that is not enough, we save the message in the database on the agent. We can then fetch the message with a web service call later.
The comparison algorithms were using a lot of memory, so we had to refactor them to be able to compare bigger files. For comparing two 1Mb Text documents, it was using 100Mb, so that did not scale. Now the comparison algorithm has been updated to support messages of 200Mb depending on the hardware. Let’s see if the bigger also works with the memory consumption. If the compare fails it will only be on your development system, so no real problem.
We still have one improvement on the UI to show the big files, but it will come in one of the next releases. For now, you can see it in the Excel reports.

The other improvement was about creating unique numbers in each message. Here we are leveraging the option to use the number range module from the B2B Add-on because it enables good flexibility.

Learn more on how you can test your SAP PI/PO better https://figaf.com/irt

SAPPHIRENOW 2017 from an integration perspective

SAPPHIRENOW and the ASUG annual conference is just around the corner. I’m looking forward to packing my bags and get on the way to the event. To see what is going on in the SAP ecosystem.

I normally do a short preview of the session that I’m planning to attend at the conference so you also can follow along in what is happening. So this blog is about that.

As something new I’ll try to create Facebook live videos from the conference if it possible. I guess there is a lot of things that can go wrong like wifi and location. I’ll give it a try so you can follow along.

I recorded a video on the agenda that I have put together and my thought about it. You can view it here on facebook please comment if there is a session that you think I should add to my agenda.

If you want to meet, I’m planning to see the keynotes at the remote theater DS425. I do hope it is a place where they will stream the keynotes otherwise I may go to find a different location

Here is my list of integration topics. If you are looking at IoT/SAP Leonardo and API there is also many sessions on those. I do hope to be able to attend some of them.   

session

Title

Time

BITI8502

Roundtable: Tackling Your Cloud Integration Challenges

Tue
12:30 p.m. – 01:30 p.m. 

S320 Roundtable Corridor – Roundtable #4

DP44055

Apply the Best Strategies for Cloud Integration

Tue
02:00 p.m. – 02:40 p.m.

Data, Analytics, and Cloud Platform DP532

BA49329

Become a Driving Force for Digital Business with SAP Leonardo IoT

Wed
01:00 p.m. – 01:20 p.m.
Live Business Theater

BITI6663

Best Practices to Migrate from SAP Process Integration 7.1 to SAP Process Orchestration 7.4

Best Practices to Migrate from SAP Process Integration 7.1 to SAP Process Orchestration 7.4

BITI7809

Enterprise Integration Consolidation and Business-to-Business Collaboration with SAP Process Orchestration

Thu
11:00 a.m. – 12:00 p.m.
S310G (South Concourse, Level 3)

SAP Integration Landscape and Emerging Complexity

The field of process integration is changing quickly, setting new challenges for Integration professionals, and I think a good understanding of the available tools is key.

When we talk about paradigms in process integration, there have been 3 major phases:

  • Mainframes: Back in the day, most companies had one mainframe or two. The good thing about the mainframe was that it was fairly simple to integrate what were essentially internal programs – even if you had to work across mainframe platforms.
  • Client-server: With the emergence of client-servers and SAP R/3, the number of application servers was growing quickly. Suddenly, as an Integration Department, you had to figure out how to integrate the applications in your landscape so that you could create a new interface. In SAP terms, it may have been a Business Connector or eXchange Infrastructure (XI). You only had one tool to use.
  • The Cloud: Today, cloud integration is the norm, and the goal is to be able to quickly and easily leverage new cloud capabilities from existing development. A couple of examples of existing cloud capabilities are Hybris Cloud for Customer (e-commerce solutions) and SuccessFactor (human capital management).  There are also a number of non-SAP cloud applications. In fact, you most likely have some of them in your landscape already. As the integration expert, your job requires you to make them all play together seamlessly. Some come with prebuild content others you have to create for yourself.

As I said earlier, it used to be that you had integration consolidation that mostly worked in XI/PI. Now, Integration departments are faced with a very different landscape, driven by the need for new integration capabilities, and need to be looking outside of their space at the tools that are already available in other areas of process development. If we understand what’s out there, we can choose the right tool for the job.

I’m talking about tools like the HANA Cloud Platform – integration services (HCP-IS)/HCI, Process Orchestration (PRO), API Management, and Data Services to do bigger data ETL. We’ve also got the Application Integration Framework Overview (AIF), for when you want to do any integration with backend services. There are also SAP Gateway solutions available for exposing OData. Those are the SAP integration technologies that I can think of off the top of my head, other vendors have similar offerings that may be relevant.

I did this exercise with a customer and we spend 6 hours on the different topics and when it did fit into their architecture.

The big problem for the integration manager/architect is that you need to know the tools, and know when it makes sense to use one and how to select one over another. You also need to be able to train your team to use them. As you learn more, you’ll find a lot of overlap between the capabilities of the various tools, and knowing what each one can do will allow you to streamline your process when you have complex situations.

The challenge with all these tools is that it is both labor-intensive and potentially expensive to try them out. Say you have a situation where you want to expose some data to the user. First, you will have to figure out the logic and the capabilities of the various tools to find the best one to combine the elements so your API management will call  PRO or Gateway — to get or expose some data. Then you’ll need to acquire the tools and start using them, in order to really understand where they fit and what you can do with them. Once you get that down, you will need to work out how to leverage the technology internally. So, a lot of work is involved whenever you introduce new technology like this. You also have to keep in mind that you will be paying for licensing to use the tool, even if you don’t end up implementing it.

So as integration experts and enterprise architects, working in a rapidly changing field, we want to do our homework and really understand any tool and how we can leverage it before we place it in our systems.

What is your strategy for landscape integration? How do you cope with training problems?