Recommended
More Related Content
What's hot
What's hot (20)
Similar to Automate your Cloud Integration governance with CPILint @ SIT Netherlands 2022
Similar to Automate your Cloud Integration governance with CPILint @ SIT Netherlands 2022 (20)
Recently uploaded
Recently uploaded (20)
Automate your Cloud Integration governance with CPILint @ SIT Netherlands 2022
- 1. ©KMD Public - KMD A/S 1 @ sitNL, June 11th 2022 Automate your Cloud Integration governance with CPILint
- 2. ©KMD Public - KMD A/S INTERNT WHO AM I? 2 _ Morten Wittrock _ Principal architect at KMD in Denmark _ SAP Mentor _ SAP PRESS author _ SAP Inside Track Copenhagen co-organizer _ Frequent speaker at other SAP Inside Track events _ SAP Community: https://people.sap.com/mortenw _ Twitter: @mwittrock
- 3. ©KMD Public - KMD A/S INTERNT INTERNT A BRIEF INTRODUCTION TO CPI 3 _ SAP Cloud Integration (or CPI) is SAP’s integration middleware for the cloud _ Similar in concept to e.g. SAP PO, but built for the cloud from the ground up _ CPI is a capability of the SAP Integration Suite product _ Based on the Apache Camel open source integration framework _ Integrations are modelled visually using integration flows (iflows for short)
- 4. ©KMD Public - KMD A/S INTERNT INTERNT INTEGRATION FLOW EXAMPLE 4
- 5. ©KMD Public - KMD A/S INTERNT INTERNT INTEGRATION GOVERNANCE 5 _ CPI gives you a lot of options for modelling your integrations, which is good _ On the flip side, achieving coherence across your integrations requires governance _ Part of your integration governance is guidelines for how to build integration flows _ Examples: _ What are the naming conventions? _ Which scripting languages should be used? _ Which adapters are allowed? _ Which Java libraries are allowed?
- 6. ©KMD Public - KMD A/S INTERNT INTERNT INTEGRATION GOVERNANCE 6 _ There is an inherent problem with such guidelines _ They often sit in a Word document in SharePoint or Solution Manager _ Are your integrations compliant with the rules set out in the guidelines? _ The only way to know is to manually check each iflow _ Obviously, that does not scale _ The size of the problem is proportional to the number of developers and the amount of integration content _ This is the problem CPILint exists to solve
- 7. ©KMD Public - KMD A/S INTERNT INTERNT WHAT IS CPILINT? 7 _ CPILint is a tool that enables you write executable developer guidelines _ You select the rules, that your iflows should comply with _ The tool does the heavy lifting of checking each iflow for compliance _ You are then presented with a report of the iflows that are not compliant _ You can run the tool interactively from your computer or scheduled in e.g. a CI pipeline _ Your guidelines will no longer be gathering dust in SharePoint o/
- 8. ©KMD Public - KMD A/S INTERNT INTERNT WHAT IS CPILINT? 8 _ CPILint ships with a number of rules built in _ The rules cover: _ Naming _ Adapters _ Security _ Mappings _ Scripting _ And more _ Not all rules are relevant to everybody; apply the ones that make sense in your situation!
- 9. ©KMD Public - KMD A/S INTERNT INTERNT WHAT’S IN A NAME? 9 _ So why is the tool called CPILint, anyway? _ Let’s break down the name: _ CPI: SAP Cloud Integration _ Lint: A tool that detects “programming errors, bugs, stylistic errors, and suspicious constructs” (Wikipedia) _ You may know other linters like ESLint (JavaScript) and abaplint (ABAP) _ So: CPILint is a linter for Cloud Integration
- 10. ©KMD Public - KMD A/S INTERNT INTERNT THE DEMO SCENARIO 10 _ We’re going to check one of SAP’s suggested naming conventions _ The names of all iflow participants (= senders and receivers) should have one of the following prefixes: _ OP_ (for on-premise systems) _ B2B_ (for business partners) _ CP_ (for cloud providers)
- 11. ©KMD Public - KMD A/S INTERNT INTERNT THE DEMO IFLOW 11
- 12. ©KMD Public - KMD A/S INTERNT INTERNT THE DEMO NAMING RULE 12
- 13. ©KMD Public - KMD A/S 13 Demo
- 14. ©KMD Public - KMD A/S INTERNT INTERNT HOW DOES IT WORK? 15 _ Rules are at the core of CPILint _ The rules inspect integration flow artifacts _ The artifacts contain: _ Metadata _ Resources (such as scripts, XML Schema files etc.) _ The iflow BPMN2 XML document _ Some rules only inspect resources _ But most examine the iflow XML
- 15. ©KMD Public - KMD A/S INTERNT INTERNT HOW DOES IT WORK? 16 _ Some examples of rules: _ Naming conventions _ Allowed/disallowed adapters _ Duplicate resources check _ Unencrypted HTTP endpoints not allowed _ Allowed/disallowed mapping types _ Client certificate in sender channels not allowed _ Iflow description required _ Basic authentication in cleartext not allowed
- 16. ©KMD Public - KMD A/S INTERNT INTERNT HOW DOES IT WORK? 17 _ Some rules only look at a single iflow at a time _ Other rules inspect all iflows to determine compliance _ If an iflow is not compliant with a rule, an issue is created _ The issue contains the information you need to do something about the problem _ Like: _ Which iflow _ Which channel, mapping step etc. _ Which resource
- 17. ©KMD Public - KMD A/S INTERNT INTERNT HOW DOES IT WORK? 18 _ At the moment, all issues are written to the console _ Future possibilities: _ Add the issue to an incident tracking system like Jira _ Log the issue to a file _ Post the issue to e.g. Slack or Microsoft Teams _ Send a text/email
- 18. ©KMD Public - KMD A/S INTERNT INTERNT CPILINT IS OPEN SOURCE 19 _ CPILint is free and open source _ What does that mean for you? _ First, you have access to the complete source code _ On GitHub and included in every CPILint release. _ Want to learn how the tool works? You can. _ Second, the license allows you to modify the code _ CPILint is released under the MIT License. _ Want to change or add something? Go right ahead; the license lets you do that.
- 19. ©KMD Public - KMD A/S INTERNT INTERNT SYSTEM REQUIREMENTS 20 _ To run CPILint all you need is a Java 11 runtime _ Everything else is included in the download _ To build the code you will need: _ A Java 11 JDK _ Apache Ant _ Apache Ivy
- 20. ©KMD Public - KMD A/S INTERNT INTERNT HOW TO GET STARTED 21 _ Three easy steps to CPILint _ Step 1: Go to GitHub and download the latest release _ Step 2: Follow the installation instructions in the wiki _ Step 3: There is no step three
- 21. ©KMD Public - KMD A/S INTERNT INTERNT WHAT’S NEXT FOR CPILINT? 22 _ Even more rules _ Extensibility _ Documentation for developers _ Exceptions for rules _ Support for more names you can check _ Do you have a suggestion or an idea? Create a GitHub issue!
- 22. ©KMD Public - KMD A/S 23 Questions?