The enterprise application installation process (console
and wsadmin) always appends the .ear extension with the application name.
This is normal and works as designed.
Case 1:
If an Install Directory is not specified, binaries are distributed
to:
Base_Install_Root
/installedApps/<CellName>/ApplicationName.ear
Case 2:
During the installation process, you have the option to specify an
application Install Directory and Application Name .
If an Install Directory is specified, the binaries are distributed
to:
Specified Install Directory /ApplicationName.ear
Install process using Console :

Install process using wsadmin:
$AdminApp install
$WAS_HOME/installableApps/My.ear
{-node my_Node -cell
my_Cell -server MyServer
-installdir C:/WebSphereAppDir -appname MyApp}
In both cases the .ear extension is appended to the ApplicationName to
form the directory name.
How to prevent the .ear extension on the ApplicationName
directory
This cannot be altered during the installation process. After successful
installation, use wsadmin $AdminConfig to make the change, using any path.
The underlying WebSphere® Application Server code will take care of moving
the application from the old location to the new location.
Sample 'wsadmin' commands to edit installedApps .ear extension for
"ivtApp" Enterprise Application .
wsadmin>set deployment [$AdminConfig getid
/Deployment:ivtApp/ApplicationDeployment:/]
(cells/KenGBase/applications/ivtApp.ear/deployments/ivtApp:deployment.xml#ApplicationDeployment_1)
wsadmin>$AdminConfig showAttribute $deployment
binariesURL
$(APP_INSTALL_ROOT)/KenGBase/ivtApp.ear
wsadmin>$AdminConfig modify $deployment
{{binariesURL
$(APP_INSTALL_ROOT)/KenGBase/ivtApp}}
wsadmin>$AdminConfig save
|