I am using RAD 7.0 working with WAS 6.1, but we want to move to eclipse + WAS 8 developer edition as development platform. However, even we successfully connect eclipse with WAS 8 Developer with IBM donated plugin
and working fine to deploy application on the eclipse. But we found that it is strange on generating plugin-cfg.xml on HTTP server to simulate the flow.
In RAD 7.0, when we generate a plugin-cfg.xml within admin console (both
Web or within RAD environment), the xml will include all application context
in it, there is no webserver being registered within the WAS 6.1 within RAD.
However, in eclipse + WAS 8 Developer edition, when we generate the xml in admin console, it does not include any application context within the xml.
I have many ways but still failed.
Actually, I also tried to register the HTTP server 8 into a managed
node within WAS 8 developer admin console. However, when I go into
an application managed module section, it does not allow me to include
webserver node in managed module ("OK" button is missing, only "Cancel"
button there). It is strange that only those applications deployed by
eclipse will exhibit this behaviour. When I explicit install another
application via admin console, it is fine it allows me to add appserver
and webserver node in managed module.
Does anyone can give me some hints/solutions on how to proceed?
I really need to generate plugin-cfg.xml for developer to test
before they proceed to SIT environment for more testings.
I attach the plugin-cfg.xml generated from WAS 8 DEV in which no
application context is included.
Please kindly help!
Thanks for your kind attention in advance,
This topic has been locked.
2 replies Latest Post - 2012-11-13T16:54:13Z by SystemAdmin
Pinned topic eclipse + WAS 8 developer --> failed to generate plugin-cfg.xml
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Re: eclipse + WAS 8 developer --> failed to generate plugin-cfg.xml2012-11-09T19:22:55Z in response to SystemAdminBy default, the publishing setting is setup with "Run server with resources within the workspace" and "Minimize application files copied to the server". The admin console cannot modify any of the application level config in this mode. You can try disable "Minimize application files copied to the server" in the server editor under the "Publishing settings for WebSphere Application Server" section to see if that fixes the problem.
Note that for those changes to take place, you'll need to remove the application, do a publish and add it back again with another publish.
If that is still not working, then, you'll have to switch to use "Run server with resources on Server" and run through the same steps to republish the application.