Deploying EAR fails on WebSphere

  1. MyEclipse Archived > Application Servers and Deployment

This topic contains 7 replies, has 3 voices, and was last updated by  ehodges 7 years, 3 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #340623 Reply

    ehodges
    Member

    I’m upgrading from MyEclipse 9 to Version: 2013 SR1, Build id: 11.0.1-20130621.

    I build my EAR and install it on WebSphere (Platform 7.0.0.19 [BASE 7.0.0.19 cf191132.09]) from the WebSphere admin console web page. I select “Generate default bindings” and leave everything else alone.

    I shut down WebSphere and go to the Servers tab in MyEclipse. I right-click on the WebSphere server and select “Add Deployment”.

    I deploy the exploded EAR in overwrite mode.

    The status for my EAR says “Deploying…” for some time, then switches to “Redeploy”.

    When I right mouse on the EAR and select “Redeploy” I get a dialog that says my EAR “could not be redeployed because it could not be completely removed in the undeployment phase.”

    The EAR is then marked with a red X and has the status “Undeploy”.

    This all used to work in MyEclipse 9.

    What do I need to do to properly deploy my EAR?

    #340647 Reply

    support-swapna
    Moderator

    ehodges,

    Sorry that you are seeing this issue.

    Can you please answer some more questions for us ?

    1. Is the EAR developed in MyEclipse 9.x and being imported to MyEclipse 2013 ? Did you go through the project migration wizard for the EAR after importing to MyEclipse 2013 ?

    2. What OS are you running on? Can you try running MyEclipse Blue as an administrator and see if that fixes the issue? There can be permission problems which prevent some actions from correctly executing in some cases.

    3. Can you please clarify that you are deploying in the Classic mode and exploded deployment ? If you have not tried the Classic mode, On the profile configuration page, switch to Classic deployment mode. Try deploying with this mode enabled and see how it works.

    4. If you are still seeing issues, please switch to a new workspace, import the project , replicate the issue with the deployment and share the contents of the deployment log to help us investigate further. Right click on the server – view deployment log. Paste the contents of the deployment log here.

    #340659 Reply

    ehodges
    Member

    @support-swapna wrote:

    ehodges,

    Sorry that you are seeing this issue.

    Can you please answer some more questions for us ?

    1. Is the EAR developed in MyEclipse 9.x and being imported to MyEclipse 2013 ? Did you go through the project migration wizard for the EAR after importing to MyEclipse 2013 ?

    The EAR has been developed in several previous versions of MyEclipse. I copied the workspace and opened it in ME 2013. ME 2013 modified its files, which might have been done by a wizard. I don’t recall precisely.

    @support-swapna wrote:

    2. What OS are you running on? Can you try running MyEclipse Blue as an administrator and see if that fixes the issue? There can be permission problems which prevent some actions from correctly executing in some cases.

    Windows 7 is the OS.

    We don’t use MyEclipse Blue. We develop for multiple app servers, not just WebSphere.

    I’ll try running as admin on MyEclipse, but my user is an admin on this PC.

    @support-swapna wrote:

    3. Can you please clarify that you are deploying in the Classic mode and exploded deployment ? If you have not tried the Classic mode, On the profile configuration page, switch to Classic deployment mode. Try deploying with this mode enabled and see how it works.

    No idea what the “Classic mode” is. I’m guessing that has something to do with Blue?

    @support-swapna wrote:

    4. If you are still seeing issues, please switch to a new workspace, import the project , replicate the issue with the deployment and share the contents of the deployment log to help us investigate further. Right click on the server – view deployment log. Paste the contents of the deployment log here.

    There’s no “view deployment log” when I right click on the server.

    #340683 Reply

    support-swapna
    Moderator

    ehodges,

    Thank you for the details.

    Are you trying to point the WAS 6.1 connector to the WAS 7 installation?

    MyEclipse Blue has extensive and advanced support for Websphere server and it also includes all the other servers available in MyEclipse. I suggest you upgrade to MyEclipse Blue edition to be able to deploy and run projects smoothly on Websphere server. Please email to sales@genuitec.com with your current license details and a request to upgrade to Blue license.

    Let us know if you see any issues.

    #340831 Reply

    ehodges
    Member

    @support-swapna wrote:

    ehodges,

    Thank you for the details.

    Are you trying to point the WAS 6.1 connector to the WAS 7 installation?

    MyEclipse Blue has extensive and advanced support for Websphere server and it also includes all the other servers available in MyEclipse. I suggest you upgrade to MyEclipse Blue edition to be able to deploy and run projects smoothly on Websphere server. Please email to sales@genuitec.com with your current license details and a request to upgrade to Blue license.

    Let us know if you see any issues.

    So you’re saying there’s no way to cleanly redeploy WebSphere 7 with the latest version of MyEclipse?? Because we’ve been using it with several previous MyEclipse versions with no trouble. Why do we have to buy Blue now?

    #340878 Reply

    support-swapna
    Moderator

    ehodges,

    I have escalated your concern to the dev team. They will get back to you.
    Sorry for the inconvenience.

    #340879 Reply

    Brian Fernandes
    Moderator

    ehodges,

    Sorry for the delayed response.

    Some background on Pro vs Blue: We created the MyEclipse Blue product to cater to the needs of WebSphere developers nearly five years ago, these connectors are significantly more advanced than the connectors we have in MyEclipse Pro given WebSphere’s needs. We stopped developing the “standard” WebSphere connectors in the Pro edition and continued development only in Blue, while continuing to ship the connectors that we already had in Pro “as is”.

    With 2013, there have been significant changes in our server connector design and architecture and while we have specifically tested the other connectors, we don’t test WebSphere in Pro as almost all our WebSphere users now use Blue.

    We are unsure of where the problem is right now, but my team will take a look. I will say upfront that fixing this bug will be a low priority for us given reasons mentioned above; unfortunately the only workaround possible until then would be to remain with MyEclipse 10.x.

    Blue is a superset of MyEclipse Pro, so it includes all other server connectors as well as faster deployment modes for WebSphere, I would encourage you to try it. If switching to that is an option you would like to consider please write to to support@genuitec.com with a link to this thread and your subscription details so we can work something out given your long standing use of MyEclipse.

    Sorry for the inconvenience caused.

    #340883 Reply

    ehodges
    Member

    That’s too bad. It used to work and now it doesn’t.

Viewing 8 posts - 1 through 8 (of 8 total)
Reply To: Deploying EAR fails on WebSphere

You must be logged in to post in the forum log in