2. ● Why Integration and DevOps
● How the Figaf tool can help you with your integration
● Getting started with the Figaf tool
Agenda
3. Why is integration important?
Vital to your business
Your business consists of a number of
business process
If they span multiply systems you need
the systems integrated
The business process only works if all
integration works
Integration is important for SAP
4. SAP CPI is a great platform to create integration it.
Lots of pre delivered content
Enables developers to create the cloud integration needed
SAP CPI
5. ● Development
● Operations
About developers should be able to move development easier to
production and also support/operations it easier.
That is inline with most organisation where you just have one team
that handles both development and support.
Make it easier for developers to release code and ensure proper
testing and procedures are followed.
What is DevOps
6. Why DevOps
● Look at your backlog of interfaces, you can see why you must
deliver more integrations
● Changes in team with reduction/increase of employee and
consultants
○ New people many not be able to support the process in the same way
8. ● Git repository with option to create branches and tags
● One global repository for all systems
● Commit to deploy
● Specify branch/tag to deploy
● Our current investigation
○ it is pretty difficult to manage
○ Online (BPM model) vs Offline options like Groovy
○ Local deployment
● For now this it not in the scope of Figaf DevOps Tool
In DevOps people may think of more
9. 1. Coding – code development and review, source code management tools,
code merging
2. Building – continuous integration tools, build status
3. Testing – continuous testing tools that provide quick and timely feedback on
business risks
4. Packaging – artifact repository, application pre-deployment staging
5. Releasing – change management, release approvals, release automation
6. Configuring – infrastructure configuration and management, infrastructure
as code tools
7. Monitoring – applications performance monitoring, end-user experience
DevOps Processes (from Wikipedia)
10. ● Create a ticket that contains all information about the change.
Ticket links to Jira/Service Now ...
● List all objects that is changed
○ Packages
○ Iflows
○ Value mappings
● Tickets are used to document the full process
● Basis for the transports
Development
11. ● Development of Iflows (BPMN) Model via UI
● Git repository
○ Change management
○ User friendly Groovy scripts development via IDE
○ Unit testing for Groovy scripts
● Gradle plugins
○ CPI Plugin provides direct integration with CPI system: Download, Upload,
Deployment
○ IRT Plugin provides testing with the Figaf tool
● Shared scripts/resources
○ Keeps the state/version of resource synchronized across multiply iflows
○ Replication of shared iflows
Development
12. ● Git object is created by
Figaf IRT
○ Provides templates
○ Test cases
○ Possible all iflows
● User can stay in IRT
branch or move to a
different branch
Git process
13. 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
14. ● Test SAP CPI Iflows
● Record/Replay
● Mocking of Iflows
○ so you can test all services you have in your landscape
○ also test scheduled instances
● Reuse test cases to create unit tests in
● Test confidential data
Testing
15. ● Once place to configure iflow in all system
● Part of the transport and approval
Configuring
16. ● Create transports with the packages, iflows and value mappings in
charge
● Upload to virtual systems (so you can save QA)
● Configuration after upload
● Approval of transports
○ Different approvers in the process
○ Configure if deployment needed
● Documentation of the ticket/change
Transports
17. ● Iflow Monitoring with groups
● Alerting of iflow based on status
Monitoring
18. ● One as template then make copies of it
● For each company code you can then create versions
● Simplify the deployment process
● Handle the updates of the copied iflows
New: Multi iflow configuration
19. SAP API Management
● Development Tool
○ Git and Gradle
● Transport mechanism
● Monitoring
○ Modification to save to KVM
Same support for
SAP PI/PO
● Transport
○ both with or without CTS+
● Testing
● Monitoring
● Documentation of changes
20. ● Laptop for PoC Build in database.
It takes 5 minutes to get started
● Figaf Cloud
● Production Standalone Java application that needs a database like
MSSQL, Oracle, DB2, Postgresql
● Most would deploy it in Azure or AWS
Deployment Options
21. ● Undelete of Iflows or Value mappings
● Cloud Foundry support
● Open Connectors to support
● Any Good ideas?
Roadmap
22. ● DevOps
○ 3 Agents (CPI systems)
○ 40 Iflows Managed
○ Full DevOps package
○ Test cases
○ Git Repository
○ Monitoring
○ 600 EUR/month
○ 6 EUR/month for extra iflows
○ Billed for 3 months
Price
