[Gianluca84]

We found out another issue that is bothering us:
I’ve configured a workspace enhancing the EARs with a WAS 6 runtime which we have to mantain for some clients.
Unfortunatly our machines are now win7 64 bit, and we were unable install WAS 6 on this machines because the installer didn’t allow us.

I’ve configured the WAS 7 connector and tested and deployed correctly all my projects, all of them are configured to be java 1.4. So far so good. After all the modifications to the project from the enhancement procedures I have committed them to owr svn repository. So we’re building the projects with a was6 runtime and deploy it to a was7.

The problem is that now, when somebody else’s checkout the projects from the repository from a fresh workspace, he will find out that all of them are already enhanced but there is no websphere 6 runtime configured on his myeclipse version! Practically it will be like just before all the enhancement procedure BUT the Enhance function is disabled.

The projects still have the Websphere 6 library “pointer” under build-Path->Libraries but it points nothing as no websphere 6 runtime is configured.

I was wondering, how can I copy all the configuration done by myeclipse during the enhancement to other machine? Where is it? Is there another way to do it?

I hope I was clear enough. I realize that due to our contraints the situation is a bit tricky to understand 🙂

Thanks again

[support-tony]

Gianluca,

You can install WAS 6.1 on Window 7 64 bit. I have done that myself. Just ignore any warning about this being an invalid OS level. If it allows you to continue, then just continue.

I’m not clear on how you are building your project with the WAS 6 runtime, when you haven’t installed WAS 6 on your machine but why can’t other developers do the same?

[Gianluca84]

Unfortunately we need the was 6, since we have some production servers (iseries/as400) that have jvm 1.4.

I’m not clear on how you are building your project with the WAS 6 runtime, when you haven’t installed WAS 6 on your machine but why can’t other developers do the same?

Pretty simple. I’ve copied just the base_v6 directory from another old system that has it installed. That directory contains the libraries and the profiles but it’s not installed it’s just copied! 🙂
Clicking enhancement on an EAR than we speciefied that directory to be the was6 runtime directory. All our project are configured to have the was6 so…it’s working.

The others instead are going to checkout the projects from the svn already enhanced.

[Brian Fernandes]

Gianluca,

We realize this is a pain-point and we’ll be improving the enhancement capabilities in the MyEclipse 10.x series.

In the meanwhile, you will notice that there is a .settings folder in the project – the contents will be something like

myeclipse.enhanced=true
library.source=WAS_RUNTIME
library.path=F\:\\Websphere 7\\AppServer

– if you replace the library.path value with the location of the WAS 6.0 install on your machine and restart Blue, the container should work fine.

Please let me know if you need further assistance.

[Gianluca84]

Thanks, I’ll try that and I’m confident that will suffice to solve our problem.

[Author]

Posts