|
|
|
|
|
The purpose of the pre-migration phase is to determine the scope of the migration (the data and application changes that will be moved from a current CONVERSANT platform to Avaya IR). The pre-migration scripts, including the Scanit tool, are packaged together in a pre-migration package. You install and execute the pre-migration package on the source CONVERSANT system.
Pre-migration scanning tool (Scanit)
Scanit is the primary data gathering tool used to quantify the data and applications on source CONVERSANT platform. The log files from Scanit are a primary input to determining the work effort involved in the migration to an Avaya IR platform. Actual effort estimates require analysis of the log files created from the pre-migration tool and are expected to be made by an experienced development organization such as an ISV or Avaya professional services.
Note:
Scanit should not be confused with the existing SCAN tool that is run by Avaya services. The existing SCAN tool captures an entire CONVERSANT configuration (boards, RTU licenses, etc). Scanit is dedicated to applications and data and complements the existing SCAN tool.
Scanit looks at application source files for occurrences of code that are out of compliance with the new Avaya IR release. These occurrences are referred to as tokens. The Scanit tool allows the user to configure the extensions for which to scan. The default extension types are:
Scanit searches for files from a root directory by the above extensions. It searches in one pass starting from the specified root directory and continuing downward into all subordinate subdirectories for all source files.
In addition to searching for files by extension type, Scanit can also be configured to specifically look at particular files, regardless of extension type. The input list of files can be a set of files residing anywhere on the system. The user-supplied file list provides an option for the user to specify an explicit file type for each file. This allows the user the flexibility to input files to the tool that may not be readily identifiable by their extension type, and therefore would not be found in a standard search.
An example of an unsupported token would be IRD_FLEXWORD, which is a value supplied to the irSettParams functions in IRAPI. If this token is found in a source file on a system being migrated to the Avaya IR system, the tool flags the parameter, identifies the file and line number, and logs this information into the log file.
Scanit generates a report identifying where unsupported tokens are found in the customer source code. The tool also provides a set of summary reports which include a list of files with specific token locations and total summaries of individual tokens found.
Scanit provides the ability to assign a weighted value for each token type. This weighted value, is used to symbolize the complexity of the work required to replace the token. The complexity values may be used to determine hours of work. As with all other parameters in the scanning tool these values can be edited and changed in a configuration file.
Data and speech scanning tool
The following describes how the data and speech scanning tool evaluates recorded speech and Oracle data:
Compound speech files, where multiple types are concatenated into one file, are not flagged and identified as compound by the scanning tool.
Note:
Actual speech conversion does not take place in this phase.
