Posts

Doing SAP CPI Transports with IRT

/0 Comments/in , /by

Once I started to make my first SAP CPI transports I did not like that you needed to transport the full package. I wanted just to transport a single Iflow and log what was changed with it, then I knew what was being changed. But it was a rather difficult process to make sure you did correctly. So I thought we could optimize the process to make it easier to apply transports for single iflows.

So we have created a flow for developers where they will make the normal changes.

  1. Save it as a version in the development CPI system after normal development
  2. Syncronize the IRT with the CPI system (by clicking the button or wait for the scheduled synchronization job)
  3. Create a ticket and assign the object version to the ticket. A ticket can correspond to a Service Request or Incident. It is possible to update the version if you have multiple attempts to fix the problems
  4. From the ticket, you then create transport with one of the Iflow on the systems
  5. IRT can then import that QA/production system. It will delete the existing iflow and upload the new version.

I have recorded a demonstration video you can see how it works

The following are we working on before it will be released.

  • Fix some of the few bugs we have seen in our test environment
  • Have a way to get the configuration in a global table, so once you import an iflow on QA it will apply the configured configuration from IRT
  • Investigate if we can upload the new iflow without removing the old version.

There may also be other ways we can integrate this both with our testing application part and make a flow that better fits with a DevOps focus of development.

We expect this functionality to be released within the next few weeks both in our cloud application as well as the on-prem deployment of IRT.

Want to try it on your own system

Try out IRT

Get IRT now

Try IRT Cloud

Get IRT Cloud now

News for Figaf IRT – January 2019 Improving SAP CPI and PI development and monitoring

/0 Comments/in , , , , , /by

Enhanced SAP CPI Monitor, Web integration and PI create test form error

So, lately I have been working with development of Figafs Integration Regression Tool, and I think the new stuff is pretty cool. Hopefully, it will be something that is useful for you to improve the ability to develop and run SAP CPI/PI content even faster and give you less support. If you have ideas for improvements I’ll like to hear.

Improved SAP CPI monitoring

We have improved the logging of errors. So it will download the attachments for the failed flows. Then it will be a lot easier for you to monitor and process the alerts. We have also improved the OData filter, so you can specify filters for messages that do not fail. So if you are using sender and receiver information you can setup a filter like Sender = ‘Salesforce’ and Receiver = ‘LOG’ that way you can get the payloads even if there are no errors on the CPI flow.

Support tool with webhooks

The IRT Support desktop is not the only one in your organization. This way you can setup integration with Jira, Paparduty or Solution manager. We configure to receive Jira notifications in about 1 hour with the information we got from the rules using zapier.com but you can use SAP PI/CPI for it.

 

Used Mappings report

Understand what is used on your SAP PI system of mappings, we have now added an option to show also Java Mappings, XSLT and also Message Mappings. Just use the Excel export of your configuration scenario.

In December 2018 I published a blog about this topic: SAP PI/PO Used message mapping.

Create a test case from a failed message

If your message fails because of a message mapping, you can set up a new test case to cover that case. This way it becomes a lot faster to validate that you have fixed the mapping once you have fixed the problem.

 

Want to ease your work?

I do believe that these improvements will make your work a lot easier. If you want to learn more please watch this video:

 

The last details

I also cover my newest insight about IRT in this slideshow:

 

You can try the features now on your own SAP PI/CPI system.

Download IRT for now

Casestory: Using Figaf IRT before testing SAP PI/PO upgrade

/0 Comments/in , , , , /by

Almost a year ago I had the great pleasure of having Mark Oshifeso on the sixth episode of the Integration Podcast. Mark was one of the first users of the  Integration Regression Tool for SAP PI/PO. Mark works for a mid-size oil and gas producer based in Texas, and he and his team found out, that using Figaf IRT made it a lot easier to do upgrades of the SAP PI/PO system. I haven´t had the resources to go deeper into the interview before now, but I do think it is interesting because Mark Oshifeso has some great insights from a customer point of view.

The episode was called How to automate SAP PI/PO testing with Mark Oshifeso from Anadarko Petroleum.

Stock image

You don´t need to be a scientist

By using Figafs IRT-tool Mark Oshifeso was able to test much faster.

“The tool is crazy easy to use. It is another generation from the usually SAP-tools, you list your Iflows, you mark those ones, you press record, and it is basically listening to messages in for example production. Once you have done that, you can run your test cases” Mark says and continue:

“The IRT tool helped us run a test circle with almost no human interaction, and we are now in the situation that we upgraded our production based on the automated testing, and we are hoping now to move from a 2-3 years cycle to a 6-month circle.”

Our ambition at Figaf is to create and keep on developing on the tool, so it is easy to use even in companies with many interfaces. Mark Oshifeso agrees that the tool gives a great overview in the process of the testing:

“It is easy to use, you don´t need to be a scientist, and this is really why we were able to introduce the tooling into our landscape of 300 interfaces. Some companies have more than 20.000 interfaces,
and if you have a large number of interfaces you need to have an easy tool. The tool helped us automate the test. The tool is really intuitive.”

“With IRT tool there is a very fast learning curve, and if another person takes over, you have people quickly getting familiar with this tool. There is no science, which is also why we choose it.”

There is no waiting anymore

What we want at Figaf is to give people a chance to optimize their workflow by using automated testing. And fortunately Mark Oshifeso thinks, that we have achieved this:

“The tool it selves is very speedy to use. There is no waiting anymore. The tool is really great to help facilitate, save money and especially save so many hours. The figaf tool is the most holistic approach, and easy to get everything set up, I don´t see anyone else so far on the market”, he says and finishes:

“I can really recommend this tool, if you want to go to automated testing, this is one of the tools
I would really look into.”

Here you can find the podcast: How to automate SAP PI/PO testing with Mark Oshifeso from Anadarko Petroleum.

As you can see Mark Oshifeso had great success using the tool. Since the interview we have made many improvements to the Integration Regression Tool, so I should be even more easy to use today.

Download IRT for now

 

 

SAP PI Migration webinar

/0 Comments/in , , , /by

So, on January 15. 2018 I held a webinar I webinar about SAP PI Migration. In the webinar, I talked about my 7 step plan for migration of SAP PI to a single stack. The 7 steps look as following:

  • Goals
  • Current integrations
  • Pattern mappings
  • Resource consumption
  • Migration phases
  • Development
  • Testing

The plan covers an initial assessment on your landscape and an idea of where you want to move your landscape.

Here you can watch the replay on the webinar:

If you want to know more you can also take a look at the blog post 7 steps PI PO migration, which was published on September 25., 2017.

You can also take a look at the slideshow: SAP PI/PO migrations – How to save time and lower risk on your projects:


Lastly, when you are interested in migration, you might want to take a look at this:

  • Seeburger Migration Tool The Figaf Seeburger Migration Tool (SMT) allows you to migrate your existing Seeburger BIC solution to a native B2B Add-on solution.
    It helps update your message mappings to use the new schemas created with the B2B Add-on. It makes your migration process a lot
    faster and have a reduced risk

Highlights from the Integration Podcast 2018

/0 Comments/in , , , /by

So, since I made the first episode of the Integration Podcast on February 4., 2018 I have published 29 episodes. There was one podcast that was skipped and delivered later. It has been a really interesting experience trying to understand how to do a podcast, interview people and learn about integration. I think the cool thing about creating the podcast has been the ability to ask really smart people about what they are working with and how they see the future of integration.

In this blog post, I will take a look back on the three episodes I like the most.

Episode 6: How to automate SAP PI/PO testing with Mark Oshifeso from Anadarko Petroleum

The first episode, I would like to mention is called How to automate SAP PI/PO testing with Mark Oshifeso from Anadarko Petroleum and was published February 28., 2018.

In this episode, I had Mark Oshifeso on the show. Mark was one of the first people to use Figaf´s
Integration Regression Tool for SAP PI/PO.

Mark wanted to make it a lot easier to do an upgrade of the SAP PI/PO system, and with the help of
Figaf IRT he was able to do so.

“It´s crazy easy to use”, Mark says.

Episode 24: SAP Integration and API

The second episode which I would like to highlight is called SAP Integration and API and was published Oktober 29., 2018. I did the episode at SAP Teched Barcelona and it was fun to sit down with Harsh.

In this episode, I talked with Harsh Jegadeesan, who is a product manager from SAP. He is responsible for quite a few of the integration as SAP and has a strong presence in SAP progress
to API.

We talked among other things about the following topics:

  • Using API as a way to remove the complexity of your landscape, as the bedsheet you use to throw over
    your bed to cover the mesh.
  • Why is the API different than the Enterprise SOA. One of the differences Harsh mentioned
    was that E-SOA was a waterfall approach whereas the API is a lot more agile. SAP is using
    the same API for UI so they will do a better job understanding them.

Episode 29: SAP Integration with Adam Kiwon

The last episode I would like to take a look at again is called SAP Integration with Adam Kiwon.

In this episode, I had a conversation with Adam Kiwon who is the part of WhitePaper InterfaceDesign. Adam and his team have created different CPI Adapters, content and products
for making SAP PI/PO better. The thing I liked about it was we got a really great conversion going about what was happening in SAP Integration.

In the podcast we talked among other things about the following topics:

  • Migration strategies when it makes sense. And we talk a little about upgrading single stack 7.31
    system and migration to single stack
  • Creating CPI adapters and how they did it
  • How to create CPI content as a partner and the CPI marketplace
  • How Adam sees the need for tools to improve CPI/PI where he has different interface
    monitoring systems
  • Why Adam had proposed to use the Figaf Seeburger tools for migrating to the B2B Add-on
    on a project
  • We talked about some of the training they where working on for the CPI

Highlights from the Figaf Blog 2018

So, I really hope you enjoyed the three podcasts, I had chosen to highlight. If so, you might also like to read this blog post: Highlights from the Figaf Blog 2018.