Migration from Neo to Integration Suite
Requirements:
All required CPI composite landscapes have been configured (see that section to learn how to do that).
Since 2212 version Figaf Tool supports browsing and migration from Neo stack to Integration Suite stack.
Get started
-
Go to
Migration to IS → Overviewpage. -
Select
Migration LandscapeandTarget Landscape.
Migration Landscapemust have only one landscape and last system of theMigration Landscapeshould be equal to the first system of theTarget Landscape.If you have old stack
old_Dev → old_QA → old_Prodand new stackDev → QA → Prodand you need to migrate objects fromold_Dev,old_QA,old_Prodsystems toDev, then configure several migration landscapes:old_Dev → Dev,old_QA → Dev,old_Prod → Dev. -
The following features are available:
-
Configure custom mapping for selected objects.
Such custom mappings make sense when some objects can’t be mapped by parameter mapping rules on migration landscape page.
If there are approved or waiting for approval transports with effected objects, custom mapping update will not be successful.
To configure it select objects and click on
Custom Mappings. It opens the dialog where mapping can be configured:
-
Create ticket for migration with selected objects. To do it select objects and click on
Create Ticket for Migration. It opens ticket creation dialog with predefinedTitleandLandscape. Then you can work with created ticket in standard way (see Ticket page). -
Show Test Runs Infoenables test runs viewing for the objects. -
Export to CSVgenerates CSV report with the table data. -
Go to tracked object page clicking on the object link.
-
Go to corresponding transport configuration page for objects with transport configuration clicking on the object link and selecting related option.
-