![[AIX]](../images/aixlogo.gif)
![[Linux]](../images/linux.gif)
![[Windows]](../images/windows.gif)
![[IBM i]](../images/iseries.gif)
Changing or adding application files
You can change or add application files on application servers without having to stop the server and start it again.
About this task
Configurações suportadas: Para arquivos de extensão e de ligação IBM®,
a extensão do nome do arquivo .xmi ou .xml é diferente dependendo de você estar utilizando um aplicativo pré-Java EE 5 ou
um módulo ou um aplicativo ou módulo Java™
EE 5 ou posterior. Um arquivo de extensão ou de ligação IBM é denominado ibm-*-ext.xmi ou ibm-*-bnd.xmi em que * é o tipo de arquivo de extensão ou de ligação como app, aplicativo, ejb-jar ou web. As seguintes condições se aplicam: No entanto, um módulo Java EE 5 ou posterior pode existir dentro de um aplicativo que inclui arquivos pré-Java EE 5 e usa a extensão do nome do arquivo .xmi.
Os arquivos ibm-webservices-ext.xmi, ibm-webservices-bnd.xmi, ibm-webservicesclient-bnd.xmi, ibm-webservicesclient-ext.xmi, e ibm-portlet-ext.xmi continuam a usar as extensões de arquivo .xmi.
sptcfg![[Solaris]](../images/solaris.gif)
Restriction: The hot deployment and
dynamic reloading function is supported when the product is running
on these operating systems only when JVM system property sun.zip.disableMemoryMapping is
set to true. The Java archive (JAR) files within
the associated Java Development Kit (JDK) are memory mapped. If these
JAR files are updated by the hot deployment and dynamic reloading
functionality when they are being used by the Java virtual machine
(JVM), the files become inconsistent, which results in an application
server crash. When you make changes to an application on these operating
systems and JVM system property sun.zip.disableMemoryMapping is
not set to true, do not use the hot deployment
and dynamic reloading functionality. Instead, restart the application
to reflect the changes.There are several changes that you can make to deployed application files without stopping the server and starting it again.
The following table lists the changes that you can make by manipulating an application file on the server where the application is deployed. The table also states whether you use hot deployment or dynamic reloading to make the changes.
| Change | Hot deployment | Dynamic reloading |
|---|---|---|
| Update an existing application on a running server by providing a new EAR file. | Yes | Yes |
| Add a new application to a running server. | Yes | No |
| Remove an existing application from a running server. | Yes | No |
| Change or add files to existing EJB or web modules. | Yes | No |
| Change the application.xml file for an application. | Not applicable | Yes |
| Change the ibm-app-ext.xmi file for an application. | Not applicable | Yes |
| Change the ibm-app-bnd.xmi file for an application. | Not applicable | Yes |
| Change a non-module Jar file contained in the EAR file. | Yes | Yes |
Tópico de Tarefa