[evalua]

We’re using the exploded deployment type and in MyEclipse version 8.0 it used to deploy to:
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\rrekas-fa0923ebNode01Cell

However after upgrading to MyEclipse 8.5 it is now deploying to:
C:\Program Files\IBM\WebSphere\AppServer\installedApps

but also creating the corresponding files in C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\rrekas-fa0923ebNode01Cell

The problem is that when a file gets updated in MyEclipse it only automatically updates the file in C:\Program Files\IBM\WebSphere\AppServer\installedApps but not in Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installedApps\rrekas-fa0923ebNode01Cell

Redeploying the application does not update the files either.

Does anyone know how to get MyEclipse to deploy to the correct folder?

Thanks

Radek

[evalua]

Below is a cut/paste of the deployment log

--------------------------------------------------------------------------------------------------------------------------------
MyEclipse: deployment START exploded project: Qbuild-etb-rq server: websphere7Server#AppSrv01 time: Fri May 28 16:23:21 EST 2010
--------------------------------------------------------------------------------------------------------------------------------
WASX7209I: Connected to process "server1" on node rrekas-fa0923ebNode01 using SOAP connector;  The type of process is: UnManagedProcess
WASX7303I: The following options are passed to the scripting environment and are available as arguments that are stored in the argv variable: "[C:\\Program Files\\IBM\\WebSphere\\AppServer\\profiles\\AppSrv01\\installableApps\\Qbuild-etb-rq.war, rrekas-fa0923ebNode01Cell, rrekas-fa0923ebNode01, server1, /Qbuild-etb-rq, Qbuild-etb-rq, {{"Qbuild-etb-rq.war" "Qbuild-etb-rq.war,WEB-INF/web.xml" default_host}}, {{.* .* AppDeploymentOption.Yes 1}}, Qbuild-etb-rq.war, true]"
-contextroot "/Qbuild-etb-rq" -nopreCompileJSPs -distributeApp -useMetaDataFromBinary -nodeployejb -appname "Qbuild-etb-rq" -createMBeansForResources -reloadEnabled -reloadInterval 1 -deployws -validateinstall off -noprocessEmbeddedConfig  -filepermission .*.dll=755#.*.so=755#.*.a=755#.*.sl=755  -buildVersion Unknown  -noallowDispatchRemoteInclude  -noallowServiceRemoteInclude  -MapWebModToVH {{"Qbuild-etb-rq.war" "Qbuild-etb-rq.war,WEB-INF/web.xml" default_host}} -JSPReloadForWebMod {{.* .* AppDeploymentOption.Yes 1}}
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installableApps\Qbuild-etb-rq.war
rrekas-fa0923ebNode01Cell
rrekas-fa0923ebNode01
server1
/Qbuild-etb-rq
Qbuild-etb-rq
{"Qbuild-etb-rq.war" "Qbuild-etb-rq.war,WEB-INF/web.xml" default_host}
{.* .* AppDeploymentOption.Yes 1}
Qbuild-etb-rq.war
true
WASX7327I: Contents of was.policy file:
 //
// Template policy file for enterprise application.
// Extra permissions can be added if required by the enterprise application.
//
// NOTE: Syntax errors in the policy files will cause the enterprise application FAIL to start.
//       Extreme care should be taken when editing these policy files. It is advised to use
//       the policytool provided by the JDK for editing the policy files
//       (WAS_HOME/java/jre/bin/policytool). 
//

grant codeBase "file:${application}" {
};

grant codeBase "file:${jars}" {
};

grant codeBase "file:${connectorComponent}" {
};

grant codeBase "file:${webComponent}" {
};

grant codeBase "file:${ejbComponent}" {
};


ADMA5016I: Installation of Qbuild-etb-rq started.
ADMA5058I: Application and module versions are validated with versions of deployment targets.
WSWS0041I: Web services deploy task completed successfully.
ADMA5005I: The application Qbuild-etb-rq is configured in the WebSphere Application Server repository.
ADMA5053I: The library references for the installed optional package are created.
ADMA5005I: The application Qbuild-etb-rq is configured in the WebSphere Application Server repository.
ADMA5001I: The application binaries are saved in C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\wstemp\Script128dd9460fb\workspace\cells\rrekas-fa0923ebNode01Cell\applications\Qbuild-etb-rq.ear\Qbuild-etb-rq.ear
ADMA5005I: The application Qbuild-etb-rq is configured in the WebSphere Application Server repository.
SECJ0400I: Successfully updated the application Qbuild-etb-rq with the appContextIDForSecurity information.
ADMA5005I: The application Qbuild-etb-rq is configured in the WebSphere Application Server repository.
CWSAD0040I: The application Qbuild-etb-rq is configured in the Application Server repository.
ADMA5113I: Activation plan created successfully.
ADMA5011I: The cleanup of the temp directory for application Qbuild-etb-rq is complete.
ADMA5013I: Application Qbuild-etb-rq installed successfully.
---------------------------------------------------------------------------------------------------------------------
MyEclipse: deployment END project: Qbuild-etb-rq server: websphere7Server#AppSrv01 time: Fri May 28 16:27:51 EST 2010
---------------------------------------------------------------------------------------------------------------------

[evalua]

This is breaking the smart deployment functionality for us which was one of the main reasons for us using MyEclipse Blue.

Is there a support email that we can use to contact support directly?

[Brian Fernandes]

Radek,

Thanks for the information. We made no changes to the deployment process between MyEclipse 8 and 8.5, so I cannot explain why something works in 8 and not in 8.5. I have a few questions:

1) Have you changed your WAS configuration?
2) If you go back to using 8.0 right now, does deployment work as expected?
3) If you edit your configured profile, you can change your deployment mode to “Enhanced”, this does an incremental packaged deployment – does this work for you?

Sorry for the inconvenience caused.
Brian.

[evalua]

Thanks for the reply Brian,

1) WAS configuration has not changed at all, the only changes were that we redeployed the application after the upgrade.

2) Is it possible to have both MyEclipseBlue 8.5 and 8.0 installed?

I tried running the 8.0 installer but it wouldn’t allow me to install to a separate folder and seemed to only want to install/upgrade my existing 8.5 install.

3) Running in enhanced mode does deploy to the correct folder
C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01\installableApps

However we use an ant script to add additional configuration files and as such cant use a packaged deployment/enhanced mode.

I’ve checked the app_install_root and user_install_root paths inside websphere and they are set correctly to “${USER_INSTALL_ROOT}/installedApps” and “C:\Program Files\IBM\WebSphere\AppServer\profiles\AppSrv01”

Is it possible to find out what MyEclipseBlue uses to determine where to deploy to with WAS7?

Thanks,
Radek

[evalua]

bump

anyone able to help me with this?

Thanks,
Radek

[Brian Fernandes]

Radek,

I’m sorry for the delayed response. We have investigated this issue and it turns out that it was caused by a bug that has actually been fixed already in 8.6M1; we were unaware that the bug would cause this issue as well.

At this time you can go to our download page and download 8.6M1 for the fix or go back to 8.0. Our installers currently do not currently allow laying down and older version of 8.x when a newer version is installed – so if you do wish to go back, please uninstall 8.5 before install 8.0. Since 8.6 is a milestone version, you can have both 8.6M1 and (8.0 or 8.5) installed at the same time.

Sorry once again for the inconvenience caused – I would encourage you to try 8.6M1 and confirm that the issue is indeed fixed for you.

[Author]

Posts