How can you do a migration on SAP PI/PO? How do you eliminate risks and make it as fast as possible?
It is some of the things that will be shared in the 7 step approach to an SAP PI Migration whether it is an upgrade or a conversion.
4. Why migrate
• Get a simpler platform
• Different license form
• Not make anymore legacy interfaces
• Will the platform still work
5. Business Case for a migration
• Technical requirement
• Problem finding the correct Java version
• End of support
• Newer options to allows faster integrations
• More adapter and some new functionality
• Simpler platform to develop and release on
• Run CPI on PO and B2B Add-on instead of Seeburger
• Pause the development for a period of time
6. Understand your integration
• Cloud integration requires different forms for integration patterns
and different tools. You can use SAP PI for everything, but not ideal
• ISA-M gives a good understanding of what patterns you have in your
landscape
• Understand where you should not just migrate to PI but move to
something else
8. 7 Steps to migration
1. Goals
2. Current integrations
3. Pattern mappings
4. Resource consumptions
5. Migration phases
6. Development
7. Testing
9. 1. Goals for the migration
Why are you migrating
1. Speed/Performance
2. Clean up
3. Simplify
4. Learning
5. Licensing
> Business Case
10. 2. Current integrations
1. Volumes for all interfaces
2. What is used. What can be removed. Yearly interfaces challenge.
3. Sync can be difficult to monitor
4. Business dialog is all used components
5. Map message into criticality, time, message
6. Map the used patterns used
11. Relevant fields
• ID
• Scenario
• Sender
• Interface
• Namespace
• Receiver
• Sender Interface Type
• Receiver Interface Type
• Number of ICO
• Number of mappings
• Messages last month:
• Criticality: Will the business break if this interface fails
• Urgency: Can we wait to fix this in two days
• Message volume/payloadsize
• Pattern: Async-sync, collect
• Estimation: Migration estimation
• Challenges: Missing password, business information
• Status: How is the migration going
12. Use the Figaf IRT tool to gather the data
• The metrics was rather difficult to get at a deep enough level.
Therefore the Figaf IRT application contains some of the information
required for margin
• 4 Steps
13. Install Figaf IRT and Configure
• Go to Figaf.com/IRT and download the application
• Then start the application can run on your laptop*
• Connect to the SAP PI system you want to monitor usage from
• Download all directory and repository data
* Good CPU, 3 GB free and good internet connection to PI system
18. 3. Pattern mappings
Pattern could be Sync/Async, RFC webservice enablement
1. If I was to start over on this how would I do it
2. Which can be removed
3. Updated to better performing
4. New things to learn, CPI, Gateway, ICO/flow, AS2 adapter, SFTP,
Modules, B2B Add-on.
19. Seeburger Migration
• Biggest development requirement in a migration is the Seeburger
Migration
• Manual task to move update each mapping because the structure
changes
• Redevelop your mappings
• Use the update structure
21. • Figaf Seeburger Migration Tool automates the remapping of your
Seeburger mappings.
• Improve consistency
• Faster development
• Less Error Prone.
• 100 EUR/mapping
Figaf.com/SMT
Seeburger Migration Automation
22. 4. Resource consumptions
1. How many developers do you need
2. Can handle internal or extern resources
3. Is it core or can we handle it with knowledge transfer
4. Business involvement
23. 5. Migration phases
1. First POC test new server works not critical, few messages.
Perform the full cycle with validations and go live
Have rollback option and try it out
2. Ramp up to take high volume, to get feeling of how it performs
Avoid having backlog of non migrated interfaces
3. Critical interfaces
4. All the rest
5. Changes to existing interfaces. If they change you need to migrate
them. Save the testing
24. 6. Development
1. Move SWCV
2. Move java modules/adapters Rework? NWDI
3. SAP Migration tool
4. Channels
5. Update documentation
6. Test
7. Transport
25. 7. Test
1. Don't want to involve business/partners in testing
2. Rerun production data on new system and validate
3. Easy to collect the test data.
4. Collect test data
5. Prove nothing is changed
6. Tool to support and document test
26. Big frustration with testning
• Testing with the business
• Picking out real productive data
• Business test to little PI relevant
• The want to make the simple one line document. It does test end to
end. Does not cover the complexity of the business.
27. Automation of testing with Figaf IRT
• Fastest solution to make it possible to test your SAP PI/PO system
• Record multiply interfaces at one time
• Data anomysation really easy
• Can also be used to document your scenarios
• Prices start at 10.000 EUR/year
• Free version
• Figaf.com/IRT
29. • Now to get the most of the SAP PI/CPI development
• Signup on https://figaf.com/7vuw
Webinar next week
30. • Want to help you with organizing your process
• 1 x 3 hour web meeting to get started your process
• 4 x 1,5 hours web meetings to go thru the process
• If 5 sign up for the process then 5 mastermind sessions of 1,5 hour
• IRT installation to setup used mapping report and show 5 examples
on how you can perform testing in your landscape
• Email dgr@Figaf.com to signup
Migration process help
BEMÆRK: Denne skabelon er IKKE layoutet!
Du skal selv indsætte dine egne tekster og grafik. Jeg har med vilje holdt skabelonen bar, så jeg kan fokuserer på hvad der skal være på de enkelte slides (ikke hvordan de ser ud).
***
Dit løfte til deltagerne på webinaret.
Start med god energi, og gør dem begejstret over at skulle deltage i webinaret (bekræft dem i deres beslutning om at deltage på webinaret)
