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.
You should not be re-running the analysis tool here. You should be staring with the eclipse workspace. Using that workspace then you would run the WAMT from eclipse run => sanalysis ... and then select the"cloud application migration" and press the set button. Next, select WebSphere on cloud (virtual machine) as your target cloud platform and press the analyze button. That should show you the db connectivity and url issues ... and you can fix them inside eclipse ... remember binary scanner is not intended to be used for fixing problems ... its just used for assessment ... by the time you get ot moving your application to WAS as a Service you are well past the assessment stage so should be using the WAMT; not the binary scanner.
For doing so, we run again the same command: java -jar binaryAppScanner.jar binaryInputPath --analyze [OPTIONS].
(I) binaryInputPath is an absolute or relative path to a J2EE archive file or directory that contains J2EE archive files. (II) in this case, we need to update the options to the current WebSphere Application Server version as well as to the target IBM platform. That is, our [OPTIONS] this time are: --sourceAppServer=was90 --targetAppServer=was90 --sourceJava=ibm8 --targetJava=ibm8 --targetJavaEE=ee7 --targetCloud=wasVM
You should not be re-running the analysis tool here. You should be staring with the eclipse workspace. Using that workspace then you would run the WAMT from eclipse run => sanalysis ... and then select the"cloud application migration" and press the set button. Next, select WebSphere on cloud (virtual machine) as your target cloud platform and press the analyze button. That should show you the db connectivity and url issues ... and you can fix them inside eclipse ... remember binary scanner is not intended to be used for fixing problems ... its just used for assessment ... by the time you get ot moving your application to WAS as a Service you are well past the assessment stage so should be using the WAMT; not the binary scanner.