Define migration scope

Migration scope definition is key for successful migration project. It is also challenging, as legacy buildup and irregular availability of the test messages might obscure the picture. Your mileage might vary.

Running PI import from production environment without any filters will load all the ICO’s present in the platform. It will not bring any information about the interface relevance nor availability of the test data. Thus it is important to validate the imported list against a reference. The organization could have an integration architect and a document representing a master interface list. These would be helpful in defining the migration scope.

For each interface imported by PI import tool, consider these questions to decide whether they should be in or out of the migration scope.

Migration relevance - interface questionnaire

Question	Relevance

Question	Relevance
When was the interface last used?	The interface might be a test or might be already obsolete, or replaced by a newer version. It could also be a interface that is used infrequently - e.g. a tax office interface used once a year.
How many messages were transmitted in the last month?	This will enable You to understand the criticality of the interface and estimate the necessary amount of testing.
What kind of documentation is available for the interface, when was it last updated?	Available documentation will help to understand the interface relevance. Also, an interface not used in the last year and with no documentation updates for a few years is likely to be obsolete and could be considered out of scope. On the other hand, having recent documentation will help to understand interface criticality.
Is the interface referenced in other sources? E.g. support tickets or internal FAQ.	In absence of official documentation, it’s worth validating other knowledge sources in the organization for references to the interface.

Defining the migration relevance is the responsibility of the migration project team. Int4 Suite supports the scope definition by allowing to mark specific imported ICO’s as irrelevant for the migration, allowing to focus the cockpit only on the interfaces in scope.

Marking interfaces as in/out scope in the Migration Cockpit

Example screen of the Migration Cockpit

Marking interface out of scope

Please select an interface, using the checkbox at left and click Remove from Scope button.

Filtering interfaces

At the top of the screen, there are filtering options available. Using the Migration Status filter one can select interfaces in scope, out of scope or all to further refine and validate the interface list.

Reverting interface status

If an interface is wrongly selected as out of scope, the status can be reset using the ICO details screen. Click on the interface to reset and a detail screen will open.

Example screen with ICO details

Click the Reset button to revert interface status to Not Started