8.19.2 Troubleshooting in Migration Wizard
For details on the procedure of Migration kindly refer to the Migration Guide.
API changes and other updates in 4.4
After converting your project(s), you will be able to successfully "Compile and Run" the converted project(s) in Bean Builder. The Bean Builder tool takes care of converting all the resources of the older version so that it is made compatible with the latest one. The Tool does not modify the code written by the user. So the user will have to change the "User Defined Code" if there are any API incompatibilities.
So after conversion, you can open your project using the latest version of the tool and compile the same. If you have added some of your own code, that too using any of the changed API(s) only then there is the possibility of a minor problem and you may not be able to compile your project successfully.
Note : User Code added in the Screen properties form of the previous releases will be available and can be added directly in the "Source" tab. For more details of how to edit the source in the Source tab kindly refer to Editing Source Files.
Problem with old version project : Make sure that the project was successfully compiled and the required output was obtained while using the older version.
Dependency on other classes: If source is being generated for a screen that has other screens/classes dropped in it, the classes for the screens dropped inside need to be present in the CLASSPATH for successful Source generation. This is done by adding the classes directory of the project being converted to the CLASSPATH. Make sure that the project classes are present inside the classes directory of the project being converted so that no problem occurs. i.e., all the old class files should be present in the <Bean_Builder_Old_Version>/projects/<yourproject>/classes directory before migration.
Project built using the Configuration wizard of Client Builder: If you are migrating project built using the Configuration Wizard that is used for Configuration Management then you need to do the following steps :
Add the following entry in the <Web NMS Home>/builderdata/PropertyEditors.list file.
Include the jar that contains the above classes in the CLASSPATH of the Migration Wizard after copying them to the jars directory of the latest BeanBuilder.
Invoke the Migration Wizard and then migrate the project as usual.
Problems due to the customization of source generation templates
If you have already customized the Application Template.tpl to meet your needs such that the main method has been changed (code added/removed) and if you replace the already existing template under the <Web NMS Home>/builder_template directory or as a project level template, you will encounter source generation problems after migration. Error message like "Source Processor : The tags are corrupted. Blocking of source could not be done" will be thrown.
If you have customized the NMSPanel source generation template and if you have added any method in the InnerClass part of the template (like setProperties() method of the AbstractNmsPanel) you will have problems (duplication of the setProperties() method). You must copy your template to the project's template directory to solve this problem.
If you have added your own setProperties() method in old screens then you will not be able to compile your source as there will be a duplication of the same after source generation.
This document can also be accessed directly from the Migration Wizard by clicking on the link as shown below. This link will be available in the bottom most part of the Log Area.