This project provides a Reference Implementation for migrating existing Java EE applications from on-premise to cloud-based deployments, as well as migration to a microservices-based architecture.
Apache License 2.0
17
stars
21
forks
source link
clarification of binary scanner and wamt usage #10
The binary scanner is used for assessment (judging the migration complexity of an app so you can create a detailed cost effort for migrating it) ... binary scanner runs against the class files ... it is not for repackaging the application or making coding changes ... the wamt is used for source migration ... it runs against the source code and can bring up the existing line of code where there is a problem or a potential problem so you can determine whether or not that change is actually required ... remember also that both of these tools are helpers ... in that you still need to provide intelligence in interpreting the results ... you just can simply make all the changes or even apply all the quick fixes ... you have to "apply intelligence" in interpreting the results and making the changes or ignoring them
As we said previously, there are pros and cons of using the Migration Toolkit for Application Binaries Analyze report over the eclipse-based WebSphere Application Server Migration Toolkit plugin to migrate your code to a newer WebSphere Application Server version and viceversa. Therefore, we suggest to use both in conjunction. The advantage of using the eclipse-based WebSphere Application Server Migration Toolkit plugin is, in fact, because it is used in an IDE so you can take advantage of using IDE's suggestions, tools and help:
See slides 5-10 (https://ibm.box.com/s/v8zy4alao59ev27fj4123506jjzc3ado ) for a description of why you use the binary scanner and pay careful attention to slide #10 as that is the ultimate rationale for using the binary scanner .. that is the binary scanner is primarily used to "quantify the migration effort" . For instance, you should not be opening or modifying the JAR/WAR/EAR while using the binary scanner. That's not the intended use of the binary scanner. It treats the archive's as black boxes. On the other hand the WAMT works of an eclipse project so any refactoring or code changes should be made by using the WAMT; not the binary scanner ...
The binary scanner is used for assessment (judging the migration complexity of an app so you can create a detailed cost effort for migrating it) ... binary scanner runs against the class files ... it is not for repackaging the application or making coding changes ... the wamt is used for source migration ... it runs against the source code and can bring up the existing line of code where there is a problem or a potential problem so you can determine whether or not that change is actually required ... remember also that both of these tools are helpers ... in that you still need to provide intelligence in interpreting the results ... you just can simply make all the changes or even apply all the quick fixes ... you have to "apply intelligence" in interpreting the results and making the changes or ignoring them
See slides 5-10 (https://ibm.box.com/s/v8zy4alao59ev27fj4123506jjzc3ado ) for a description of why you use the binary scanner and pay careful attention to slide #10 as that is the ultimate rationale for using the binary scanner .. that is the binary scanner is primarily used to "quantify the migration effort" . For instance, you should not be opening or modifying the JAR/WAR/EAR while using the binary scanner. That's not the intended use of the binary scanner. It treats the archive's as black boxes. On the other hand the WAMT works of an eclipse project so any refactoring or code changes should be made by using the WAMT; not the binary scanner ...