Unable to use the workbench to publish the same application that was installed by using the administrative console
An application that is published by using the workbench might display a different application name on the server, as the same application installed by using the administrative console from WebSphere® Application Server.
Important: Applicable to WebSphere
Application Server traditional
This scenario occurs when an application contains different
names for the Enterprise Application (EAR) project and the name that
is specified in the display-name tag in the application
deployment descriptor (application.xml) file. The
development workbench uses the EAR project name as the application
name when published onto the server; whereas, the administrative console
uses the display-name of the application that is
contained in the application.xml file. If you install
this application by using the administrative console and then by using
the workbench to publish this same application onto the same server,
the application is going to exist twice on the server under two different
names: One of the application names is generated when you install
the application by using the administrative console and corresponds
to the display-name from the application.xml file.
The other application name is generated when you publish the application
by using the workbench and corresponds to the EAR project name. Using
the workbench to make more updates and publish to this application
fail and result in the following runtime error message followed by
various publishing exceptions:The publish encountered some problems and the application may not have been installed or it may have been successfully installed but was unable to start.
Here
are examples of publishing exceptions in the Console view of the workbench:- javax.naming.NameAlreadyBoundException
- com.ibm.ws.webcontainer.exception.WebAppNotLoadedException