What is the effect of manually changing folder structure on a Client create by Installation Manager when multiple products with multiple versions of Eclipse have been installed?
On a single Client machine, the user has taken the following folder structures created by Installation Manager and redefined them:
Products are:
Products are:
- InfoSphere Data Architect 9.1.2 (Eclipse 4.2)
- InfoSphere Information Server 11.3.1.1 - some components use Eclipse 3.8 and some use 3.4
- WebSphere AppServer (using Eclipse 3.8)
Installed Names
&loc%\IBM\rationalsdp\workspace
&loc%\IBM\fasttrackworkspace1
&loc%\IBM\ismanager_workspace1
New Name Assigned by the User
WCC\workspace, workspace......
First I have no idea how the workspaces were copied/moved under WCC but I know the .meta files are missing and the tools are all throwing multiple errors. I have attempted to explain this to the customer in terms of showing them how the correct plug-ins and features are pulled based upon the Eclipse version etc. but I need more to convince them.
One answer
IM does not care where the workspace is located. IM manages where the tools are installed. once the tools are installed, then the tool manages where the workspace is located. I am basing this statement on my experience with the RTC client which uses eclipse.
Once the client starts up eclipse, they should be prompted to specify the location of the workspace. Each version of eclipse should point to their own workspace.
Once the client starts up eclipse, they should be prompted to specify the location of the workspace. Each version of eclipse should point to their own workspace.