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:
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:
- Para um aplicativo ou módulo que usa um Java EE versão anterior à versão 5, a extensão do arquivo deverá ser .xmi.
- Para um aplicativo ou módulo que usa Java EE 5 ou posterior, a extensão do
arquivo deve ser .xml. Se os arquivos .xmi forem incluídos no aplicativo ou módulo, o produto ignorará os arquivos .xmi.
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.
- Update an existing application on a running server
by providing a new EAR file.
Reinstall an updated application
using the administrative
console or the wsadmin $AdminApp install command with
the -update option.
Both reinstallation methods enable
you to update an existing application using any of the other steps
listed in this file, including changing classes, adding modules, removing
modules, changing modules, or changing metadata files. The application
reinstallation methods detect the changes in your application and
prompt you for additional binding data that might be needed to install
the application. The reinstallation process automatically stops and
restarts your application on the appropriate servers.
- Add a new application to a running server.
Install an application using the administrative console or
the wsadmin install command.
- Remove an existing application from a running
server.
Stop the application and then uninstall it from
the server. Use the administrative console to stop the application and
then uninstall it.
Or use the stopApplication attribute of the AdminControl
object with the wsadmin tool and then run the uninstall command.
- Change or add files to existing EJB or web modules.
- Update the application files in the application_root location.
- Restart the application.
Use the administrative
console to restart
the application. Or use the startApplication and stopApplication attributes
of the AdminControl object with the wsadmin tool.
- Change the application.xml file for
an application.
Restart the application. Automatic reloading
will not detect the change. Use the administrative console to restart the application.
Or use the startApplication and stopApplication attributes
of the AdminControl object with the wsadmin tool.
- Change the ibm-app-ext.xmi file for
an application.
Restart the application. Automatic reloading
will not detect the change. Use the administrative console to restart the application.
Or use the startApplication and stopApplication attributes
of the AdminControl object with the wsadmin tool.
- Change the ibm-app-bnd.xmi file for an
application.
Restart the application. Automatic reloading
will not detect the change. Use the administrative console to restart the application.
Or use the startApplication and stopApplication attributes
of the AdminControl object with the wsadmin tool.
- Change a non-module Jar file contained in the
EAR file.
- Update the non-module Jar file in the application_root location.
- If automatic reloading is not enabled, restart the application.
Use the administrative console to restart the application. Or use the startApplication and stopApplication attributes
of the AdminControl object with the wsadmin tool.
If
automatic reloading is enabled, you do not need to take further action.
Automatic reloading will detect the change.