![[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
The following note applies to the xmi file references
in this topic:
支援的配置: 對於 IBM® 延伸和連結檔而言,.xmi 或 .xml 副檔名取決於您是使用 Java EE 5 之前的應用程式或模組,或 Java™ EE 5 或更新版本的應用程式或模組。
IBM 延伸或連結檔稱為 ibm-*-ext.xmi 或 ibm-*-bnd.xmi,其中 * 是延伸或連結檔的類型,例如:app、application、ejb-jar 或 web。
適用的條件如下:
支援的配置: 對於 IBM® 延伸和連結檔而言,.xmi 或 .xml 副檔名取決於您是使用 Java EE 5 之前的應用程式或模組,或 Java™ EE 5 或更新版本的應用程式或模組。
IBM 延伸或連結檔稱為 ibm-*-ext.xmi 或 ibm-*-bnd.xmi,其中 * 是延伸或連結檔的類型,例如:app、application、ejb-jar 或 web。
適用的條件如下:不過,即使應用程式含有 Java EE 5 之前的檔案,且所用的副檔名是 .xmi,其中也可以有 Java EE 5 或更新版本的模組。
ibm-webservices-ext.xmi、ibm-webservices-bnd.xmi、ibm-webservicesclient-bnd.xmi、ibm-webservicesclient-ext.xmi 和 ibm-portlet-ext.xmi 檔會繼續使用 .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.
Important: See Ways to update enterprise application files and determine whether hot deployment
is the appropriate way for you to update your application files. Other
ways are easier and hot deployment is appropriate only for experienced
users. You can use
the update wizard of the administrative console to make the
changes without having to stop and restart the server.
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 |
作業主題