lemieux
Active Member
I am not a Developer and am hoping somebody might be able to help us understand how a version got corrupted while being worked on by a developer in our office.
We have a workstation called EXTRA. On this workstation was WebSphere Express 5.0 and is often used by developers.
On the weekend, WebSphere Express 6.0, WEBDEV feature H4A6_setup.exe was installed on EXTRA.
Not knowing about WebSphere 6.0 being installed on EXTRA, the developer began working on a version thinking EXTRA was still WebSphere Express 5.0.
It was then reported that;
1) A remote developer was using EXTRA not knowing that the PC was upgraded to WAS 6.0. The developer was not able to save the changes
2) This issue caused spec corruption locally and in DV811 for a version. It took me three hours to recover the specs and get them to check in.
Is it possible that having WebSphere Express 6.0 on EXTRA could have caused the spec corruption and if so, any idea why?
Do you know, once a PC is upgraded to WAS 6.0, what needs to happen next for developers to work on a fat client and make changes to specs via OMW?
Anything you could offer would be much appreciated.
Thanks in advance,
8.11 - SP1 - 8.96.G1
Planner ESU JJ12489
DS = Windows 2003, SP1, 2GB of RAM and a 3.2ghz processor
ES = iseries 400, OS/400 V5R3
Windows Application server - Windows 2003 - Service pack 1
IBM WebSphere Application Server, 5.0.2.14
Build Number: cf140544.02
Build Date: 10/31/2005
And
IBM WebSphere Application Server - Express, 6.0.2.17
Build Number: cf170648.05
Build Date: 11/28/06
We have a workstation called EXTRA. On this workstation was WebSphere Express 5.0 and is often used by developers.
On the weekend, WebSphere Express 6.0, WEBDEV feature H4A6_setup.exe was installed on EXTRA.
Not knowing about WebSphere 6.0 being installed on EXTRA, the developer began working on a version thinking EXTRA was still WebSphere Express 5.0.
It was then reported that;
1) A remote developer was using EXTRA not knowing that the PC was upgraded to WAS 6.0. The developer was not able to save the changes
2) This issue caused spec corruption locally and in DV811 for a version. It took me three hours to recover the specs and get them to check in.
Is it possible that having WebSphere Express 6.0 on EXTRA could have caused the spec corruption and if so, any idea why?
Do you know, once a PC is upgraded to WAS 6.0, what needs to happen next for developers to work on a fat client and make changes to specs via OMW?
Anything you could offer would be much appreciated.
Thanks in advance,
8.11 - SP1 - 8.96.G1
Planner ESU JJ12489
DS = Windows 2003, SP1, 2GB of RAM and a 3.2ghz processor
ES = iseries 400, OS/400 V5R3
Windows Application server - Windows 2003 - Service pack 1
IBM WebSphere Application Server, 5.0.2.14
Build Number: cf140544.02
Build Date: 10/31/2005
And
IBM WebSphere Application Server - Express, 6.0.2.17
Build Number: cf170648.05
Build Date: 11/28/06