My Dear Debuggers,
Last week another customer came round the corner with a tooling question.
He migrated his application created on Websphere Integration Developer (WID) v7.0.x to IBM Integration Designer (IID) v8.5.7. The migration finished properly, but when he closed the workspace and re-opened it again the application migration was triggered again.
Clients issue is that IID should not be asking to migrate projects that have already been migrated. Also client made the experience that if he has Process Server installed as test environment on the same workstation he no longer experience this issue.
The first thing I checked was the migration.log file from customers. Unfortunately, there aren't any hints visible related to possible problems
INFO Validating project: Test_Web
INFO Running validator: Legacy Workspace Detector (id= LegacyWorkspaceDetector)
INFO Finished running validator: Legacy Workspace Detector (id= LegacyWorkspaceDetector)
INFO Running validator: EJB Mapping Validator (id= EjbMappingValidator)
INFO The project has no EJB model associated with it. EJB mapping backend validation will not be
INFO Finished running validator: EJB Mapping Validator (id= EjbMappingValidator)
INFO Running validator: WebSphere Facet Validator (id= WebSphereFacetValidator)
OK The WebSphere facet "WebSphere Web (Extended) 8.5" is compatible with the WebSphere runtime
"IBM Process Server v8.5.7".
OK The WebSphere facet "WebSphere Web (Co-existence) 8.5" is compatible with the WebSphere
runtime "IBM Process Server v8.5.7".
OK The WebSphere Co-Existence facet pre-requisite exists for the WebSphere Extended facet.
INFO Finished running validator: WebSphere Facet Validator (id= WebSphereFacetValidator)
INFO Running validator: WebSphere Runtime Validator (id= WebSphereRuntimeValidator)
OK The WebSphere runtime is valid at the configured path:
OK The WebSphere runtime is at a supported level: 8.5
INFO Finished running validator: WebSphere Runtime Validator (id= WebSphereRuntimeValidator)
INFO Finished validating project: Test_Web
After performing a new IID installation without changing anything I checked for differences between installation of IID with / without test environment.
When installing the test environment you can see server environments like that
Without the test environment we can see only
The main difference is the Application Server Stub (base_v85_stub) does N O T exist in the file system.
Lets have a look at the installation folder (install_root\runtimes).
Indeed, the runtimes stub folders exist, but the base_v85_stub folder is missing the runtime information
The answer you can find here:
Our customer confirmed that he selected only the first installation features but NOT the Monitor Model editor.
After changing that (he corrected that step via IBM Installation Manager Modify option), the stub information were installed afterwards and the problem with triggering the migration wizard on every workspace start does not happened again.
Mission complied, problem solved.
And if this does not help, take two of these and call me in the morning.
Your Dr. Debug