This document discusses SAP integration tools and processes. It outlines common problems with SAP integration development, testing, governance, monitoring and support. It then introduces the Figaf tool, which aims to automate and simplify these areas of SAP integration. The document discusses how Figaf can help with development workflows, change management, testing, support ticket handling and more. It also covers the Figaf installation options, pricing, and roadmap for additional features.

1. SAP PI/PO, SAP CPI and API management
January 2020
Speed up your SAP Integration
© Figaf 2020

2. ● Why you need to make integration
● What areas can you improve in
● Support process
● Development workflow
○ CPI
○ PI
● Installation
● Pricing
● Roadmap
● QA
● Bonus: How simple is the installation and getting started
Agenda

3. Why you need to develop faster
● Look at your backlog of interfaces, then you can see why
● There will be a lot more integrations
● Many developers do not feel they have the time to spend 2 hours to
see if they can save 20% of their time

4. ● Old delivery model for integration does not fit the requirement for
agile development
● Development is outsourced and it is difficult to control and ensure
what is returned and if it follows the IT architecture of the company
● Cloud Integration requires a lot more integrations to be delivered
● Documentation and auditing is manual or missing process
● Updates and upgrades are postponed because of fear of
consequences
Common problems with SAP Integration

5. • Development
• Testing
• Governance
• Monitoring/Support
• Migration (see video)
Areas where automation is possible

6. Support

7. ● You can resolve problems faster or automated
● People don't need to research already solved problems
● Your costs are reduced due to saving time on alerting
Figaf simplifies your support effort

8. What the tool can do with Support
● Fetch error messages / alerts
○ SAP PI CMBA
○ CPI iflow messages
○ API mgt errors
● Set up filters with Xpath, so everybody can do it
● Notification to
○ Email
○ Webhook to send notifications Jira, etc.
● Mute similar alerts, so you don't get spam
● Reprocess alerts

9. Make it as simple to get integration to production
Development flow

10. ● Prepared a change to the flow, show what change it is
● Get a change request
● Mark the items created with this specific change request
● Test change and evaluate the impact
● Prepare transport and configure iflow
● Approve transport and transport
● Check approval message
● Check the documentation
SAP CPI development process

11. ● Create test cases for flow
● Create transport and test
● Configure communication channel
● Approve transport
SAP PI Development process

12. Change management
Governance

13. Change management also take time
● Document the changes that have been made
● Ensure you know what is going on
● Audit log trail
● Linking to buisness case

14. One place to configure iFlow in the full landscape
Users should not have development role in QA or Production
Configuration of iFlows in full system

15. Figaf has a ticket
It can be used as placeholder for your Service request, Ticket or Jira…
Will not replace your tracking system, just for providing real time data
for it
All changes should like to a request

16. Create a transport only for the iflow that you have made changes to.
Much simpler
You know what have been changed
Linked with ticket
Auto apply changes after import
Transport

17. Some clients only have 2 tier system landscape
Figaf can create virtual CPI packages with updated endpoints and
ProcessDirect Adapters
Run test on the same environment
Virtual testing environments

18. Development

19. ● You still need to create Iflow the way in the WebUI and modify it.
○ Message mapping should also be done in WebUI.
○ Linking scripts to steps
● Modification of scripts, XSLT, WSDL should be done in a better IDE
as IntelliJ or Eclipse
○ Can speedup the development because you can test with one click
○ Syntax highlighting and auto completion
Development

20. ● Git is a version system that allow users to see versions of code
● Has a lot of workflow options for improving code, probably need to
find a good way for CPI working.
● For CPI development it gives a good folder structure that all
developers will be able to use
● Make it easy to maintain code and setup
● Everything is delivered as templates
● No excuse for developers to use it
Why Git

21. One click to run code
Make it a lot faster to deploy code
Build your own steps
All open source
● CPI - Upload/Download/Deploy
● API mgt -Upload/Download
● Figaf IRT - Run test for iflow
All configuration delivered in the templates
Gradle plugins

22. How easy, cheap can you get started
Getting started

23. Figaf tool run on:
● A laptop for a PoC. It has a simple installation with build in
database. You can get started in 5 minutes.
● A server. Figaf is created as an enterprise grade application and can
run in multiple environments
○ Supports the databases PostgreSQL, MSSSQL, Oracle, DB2.
● Figaf Cloud - running in Google Cloud Platform
○ Git is not supported yet
Installation options

24. ● Test
○ Number of ICO/IFlows with test cases
○ Starts at 10.000 EUR/year
● DevOps if you want to harvest the full benefit
○ Number of ICO/iFlows managed by the tool
○ Number of tickets use to link business requirements to changes
○ Starts at 15.000 EUR/year
● Cloud version
○ Starts at 5400 EUR/year for 40 iflows
Licensing

25. ● Secured testing
○ Give option to fetch production data and hide content so you will see
anonymized data
● Transport CPI packages and value mappings
● API for tickets
● PI to CPI migration
Roadmap

26. ● The use of the Figaf tools will reduce the number of hours you need
to spend on tasks related govern, testing, transporting, manage or
support your SAP Integration
● Time or money you can spend on creating more integrations
● How much depend on your desired change process, labour cost and
how much development going on
● Don't spend time on building and maintain an infrastructure self
Figaf help you save money on integration

27. Q and A

28. Signup Figaf IRT
figaf.com/IRT
Getting started session
support@figaf.com

29. Bonus
Install Figaf IRT and run it in 15
minute

30. Installation steps
Get License code signup on Figaf.com/IRT
Download Jar and bat file
Edit bat file and run it
Goto http://localhost:8080/irt
Add connections to PI/CPI connections
Test connection
Create Landscape