Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Figaf IRT for SAP CPI

•Download as PPTX, PDF•
•
D
Daniel Graversen

In this presentation, you can see what the Figaf IRT tool can do in regards to SAP CPI development. To make it easier to help with the Change Management of the CPI and monitoring. So you can make faster use of the tools and get your development done faster.

Related slideshows

Total Control Brochure
Total Control BrochureTotal Control Brochure
Total Control Brochure
 
Going Global with Outsystems Mobile
Going Global with Outsystems MobileGoing Global with Outsystems Mobile
Going Global with Outsystems Mobile
 
Modeling Integration to AFS Retail Appications
Modeling Integration to AFS Retail AppicationsModeling Integration to AFS Retail Appications
Modeling Integration to AFS Retail Appications
 
1 of 21
Alerting, Testing, Documentation and Change Management Manage your SAP PI better © Figaf 2019
• SAP PI • SAP CPI • Api management Which SAP Integration tools do you use
Scoping Development Testing Document Transport Validation Go live Support Development process
Governance Require you to document all the developments that you have created And what is changing and link it to a request Normally a manual process to create the documentation
Spend long time on the documentation of what is going on. Difficult to find it after it have been used Most of the time out of date Documentation
For SAP PI/PO Figaf IRT take on transports
Ticket can be linked to a service request Contain all information for the change request ● Objects changed ● Transports and History ● Tests ● Alerts triggered All can be exported and saved into Solman, Jira or your tool Main object is a ticket
Create your CTS transport the normal way with exports from SAP PI/PO Import the transports in IRT and link it to the ticket See all differences in the configuration CTS transports
One place to make all configurations of your landscape. Configure all systems in one place. Host names in production is different than production. No need to give users access to make modifications in production or create elaborate documents for production configuration. Channel Configuration
Once you have imported your change list ● IRT can handle the change list that needs to be activated ● Configure the channels ● Update the documentation ● Test the solution if on QA CTS Import
Easier to use ● Collect test data and setup test cases faster ● Cover more patterns, modules, bridges and comparison ● Run multiple test cases at the same time ● Can use data from your first upgrade ● Generate reports of changes ● Anonomy data Integrates with a development lifecycle tool so you can run test based on what is changed One tool for both PI and CPI Figaf Testing tool
● Scenario documentation with History ○ Channels used ○ Mappings ● Ticket history ○ Objects in the ticket on all systems ○ Test cases and the status of them ○ Configuration ○ Transports Documentation
Rule based alert on CBMA actions. Easy setup rules ● Learn from mistakes ● Faster support ● Reprocessing Alerting
Reason and benefits of tools
Your developers leaves, how do you know how the interface should work and support them. There maybe some documentation, but is it updated and how do you really test the function. Keep knowledge
Be able to perform you upgrade faster Faster deployment of changes to production Saving in terms of developer time One way to manage both PI, CPI and API mgt Short term benefits
Less errors with your integration Better documentation of changes Be able to fix your interfaces even when developers leave Faster time from support problem to fix in production More stable environment Long term benefits
For SAP Cloud Integration suite
● Monitoring ○ CPI current performance ● Alerting ○ Querying failed or any type of flow ○ Latency and CPU alerts ● Change management ○ Documentation ○ Transport of individual iflow ○ Configuration of iflow ○ Testing SAP CPI
● Versioning ● Transport ● Alerting SAP Api management
https://figaf.com/IRT Try Figaf IRT on your own Free trial

More Related Content

Figaf IRT for SAP CPI

  • 1. Alerting, Testing, Documentation and Change Management Manage your SAP PI better © Figaf 2019
  • 2. • SAP PI • SAP CPI • Api management Which SAP Integration tools do you use
  • 4. Governance Require you to document all the developments that you have created And what is changing and link it to a request Normally a manual process to create the documentation
  • 5. Spend long time on the documentation of what is going on. Difficult to find it after it have been used Most of the time out of date Documentation
  • 6. For SAP PI/PO Figaf IRT take on transports
  • 7. Ticket can be linked to a service request Contain all information for the change request ● Objects changed ● Transports and History ● Tests ● Alerts triggered All can be exported and saved into Solman, Jira or your tool Main object is a ticket
  • 8. Create your CTS transport the normal way with exports from SAP PI/PO Import the transports in IRT and link it to the ticket See all differences in the configuration CTS transports
  • 9. One place to make all configurations of your landscape. Configure all systems in one place. Host names in production is different than production. No need to give users access to make modifications in production or create elaborate documents for production configuration. Channel Configuration
  • 10. Once you have imported your change list ● IRT can handle the change list that needs to be activated ● Configure the channels ● Update the documentation ● Test the solution if on QA CTS Import
  • 11. Easier to use ● Collect test data and setup test cases faster ● Cover more patterns, modules, bridges and comparison ● Run multiple test cases at the same time ● Can use data from your first upgrade ● Generate reports of changes ● Anonomy data Integrates with a development lifecycle tool so you can run test based on what is changed One tool for both PI and CPI Figaf Testing tool
  • 12. ● Scenario documentation with History ○ Channels used ○ Mappings ● Ticket history ○ Objects in the ticket on all systems ○ Test cases and the status of them ○ Configuration ○ Transports Documentation
  • 13. Rule based alert on CBMA actions. Easy setup rules ● Learn from mistakes ● Faster support ● Reprocessing Alerting
  • 15. Your developers leaves, how do you know how the interface should work and support them. There maybe some documentation, but is it updated and how do you really test the function. Keep knowledge
  • 16. Be able to perform you upgrade faster Faster deployment of changes to production Saving in terms of developer time One way to manage both PI, CPI and API mgt Short term benefits
  • 17. Less errors with your integration Better documentation of changes Be able to fix your interfaces even when developers leave Faster time from support problem to fix in production More stable environment Long term benefits
  • 18. For SAP Cloud Integration suite
  • 19. ● Monitoring ○ CPI current performance ● Alerting ○ Querying failed or any type of flow ○ Latency and CPU alerts ● Change management ○ Documentation ○ Transport of individual iflow ○ Configuration of iflow ○ Testing SAP CPI
  • 20. ● Versioning ● Transport ● Alerting SAP Api management
  • 21. https://figaf.com/IRT Try Figaf IRT on your own Free trial