DevOps for SAP CPI with Figaf tool webinar replay

/0 Comments/in /by

We hosted a webinar with the topic of how you could get to use DevOps for SAP CPI and API management.

The presentation is almost exclusive done via demostrations showing that it is possible to deliver and test your SAP CPI iflows.

The reason why this is interesting for you is that it gives the flexibity to release integrations faster, without having to create all the manual paperwork required for any type of SAP Integration.

We covers the following in the presentatin:

  • Git integration and how it can improve your Groovy development
  • Testing of iflows with the build in tool
  • Version of objects
  • Tracking of changes
  • Configuration of iflows
  • Transport of the iflows

You can see the full replay here:

The reason why we could not open the configuration, has been identified. It was because we recently changed the transport settings, so it will be fixed in next release.

You can start a free trial of the Figaf tool.

Guide for configuration of DevOps for SAP CPI. This is a 30 minute video where I show all the steps you need to perform to make it possible to setup the Figaf tool.

You can register for Figaf IRT here

Getting started with Figaf and SAP CPI

/0 Comments/in /by

This presentation I’ll show how you can get started with the Figaf IRT tool. In the 28 minute video you can see how to configure everything to get the Figaf tool to work.

The tool guides you thru all the steps involved with creating a platform that allow you to run DevOps for SAP CPI.

In the presentation we cover how the following topics

  1. Register for Figaf. Just Go to Figaf.com/IRTCloud
  2. Add agents for your SAP CPI systems
  3. Create Landscape
  4. Create Test case and also run it with the mocking of the endpoints.
  5. Create Ticket for change
    1. Track changes
    2. Test
    3. Transport and configure
  6. Create Monitor
  7. Create Alerts

If you open the video in youtube you can see timestamps for the different parts.

It is possible to go into much more details on each element. The purpose of this video is to give you a broad understadning of what the tool can help with and ensure you have everything configured.

Signup here.

You can signup at IRTCloud

You can also run the tool in your own laptop with our downloadable tool. You can find it at IRT. The process is the same. You just need to download and run IRT from your PC.

Setting up the Figaf Migration Tool

/0 Comments/in /by

I have been creating a lot of webinars where I showed how the Figaf tool could do for migration. Here I always had a scenario configured that I could use for the migration. I have never shown how to configure the full setup.

How is Figaf tool different from SAP Migration tool. The goal of the Figaf migration tool is to support the migration process. This includes managing the process of the migration, testing the changes, and then making sure everything is configured correctly.

I got asked how to configure the solution and use it. This is what this video is about. To show the process end to end.

  1. Download and run Figaf IRT
  2. Add Agents (PI systems) and synchronize
  3. Create Landscape
  4. Create System Mapping
  5. Create test cases
  6. Create Release
  7. Run migration
  8. Run development

You can see the video here. It takes 33 minutes. And everything is in one go. From download to running your first migration.

It would be possible to spend a lot more time on the testing part where the Figaf tool can help out in a lot of different ways. The goal of the presentation is to show the steps involved.

Since it is mostly all in one take, there is some configuration that is giving some challenges. There is a lot of configuration that you need to do, my hope is that it gives you some idea of what is necessary. If you run into the problems you can ask for assistance for the configuration.

Limitations: The Figaf tool does not support migrations of dual-stack objects, here SAP tool has an advantage. The Figaf tool does support fetching messages from your 7.1 system, where SAPs test tool only supports 7.31-7.4 with some support packages.

Try Figaf Tool

You can download the Figaf IRT tool and try it out at https://figaf.com/IRT.

We do have free trials that allows you to get started.

Webinar Replay: Automate SAP PI/PO Migrations

/0 Comments/in /by

May 7th i hosted a webinar where we covered how how you can automate your SAP PI/PO Migration.

One good question that gave a lot of reflection: What is the difference between SAPs Migration tool and the Figaf migration tool?

The SAP Migration is about migratin secenarios from one system to another. It has good support for clasical scearios and normal migrations.

The Figaf tool is about managing the full process of migration. The tool handles transports, copy Repository content, running tests, and then be able to configure everything in the landscape. So you will get consistency and reduce the risk of the projects.

We also cover Seeburger to B2B Add-on conversion. That allows you to convert Seeburger Message Mappings to B2B Add-on wiht just a few clicks.

The main part is about how the Figaf IRT tool can help govern your SAP PI/PO migration and handle all the manual steps normally involved in such a migration.

Automate your Migration

You can sign up to the Figaf tool and try it or book a session to get help getting Figaf Installed and

Figaf IRT 2.13 released

/0 Comments/in , /by

This week we are releasing the new version of Figaf IRT. It contains quite a bit of improvement to make it easier to get started the tool and make it easier to run your SAP Integration.

You can See a video of it here

General

Make it easier to get started with tool. Both login with the default user, guides to get started with adding license and agents. Updated tours to see the tool in action.

Improved EDIFACT comparison and ignoring of specific segments/fields. This function will also be on X12, in one of the patches. You can ignore if rounding of values. So 5.2 is the same as 5.20.

Improved documentation of changes, so you can see what has been changed as a part of a ticket.

Bug fixes and improvements in the database performance.

CPI

Tracking and transports of Packages, Value mappings. So you can see what is changed between versions. They are also added to your Git repository.

Monitor to show persisted messages. So you can let business monitor the persisted messages.

For people working with the Git workflow, we have also added an option on an agent to prevent commits of iflow changes during synchronization in IRT to avoid duplication of changes committed by user and IRT. This will only create the scaffolding for your Git repository including templates for all plugins. So you can still download/upload your CPI iflows from your IDE with the Gradle plugins. You can then follow your own workflows for working with the Git Repository. This is one of the areas where we need more input on how we can help make the flow better.

In the next releases, we will also be improving the Transport system giving you options to approve and test the changes better and hopefully find a good way to handle a Git flow in the same area.

SAP PI/PO

We had a client using the Figaf IRT tool to test their Seeburger Migration, which was done with our SMT tool. It did lead to a number of improvements to be able to support this case. Existing data was saved in the separate archive so we have created a custom solution to build the test data. If you have migration and want our help to create the test data let us know and let’s create an estimation of the effort

Improvement in the way testing is possible with the SAP Logging module. So it becomes much easier to use it for testing.

SAP PI/PO support for Decentral adapter engine in conjunction with Logging module.

Testing of BE/sync scenarios with mock data on PRO systems really useful when testing secured interfaces. This will enable to test with confidential data.

Consolidation with SAP Logging module. This is useful if you send multiply messages and consolidate them into one message. Or have a BPM process between test cases. It is something that is something that requires custom configuration on your scenarios.

Throttle the number of messages sent to a test case to limit the impact on the system. So the test will not overload the system.

Get started

You can download Figaf IRT here or if you want you can use the trial cloud verion at IRTCloud