AAT,ASTK에서 EAR(WAR)를 묶을 때 선택하게 되는 "1) 재로드 사용가능(ReloadingEnabled)"
옵션은, 해당 EAR를 WebSphere에 deploy할 당시에 admin console에서 선택하게 되는
"2) 재로드가능(Reload Enabled)" 옵션과 그 역할과 기능이 완전히 다른 것이었군요.
"Reloading Enabled" is a property of web application not a websphere .
In the console which you are seeing is "Reload Enabled".
-----------------------------
1. About "Reloading Enabled":
This value goes into ibm-web-ext.xmi file, located in config/cells/
<node_name>/applications/<ear>/deployments/<war_name>/<war>/WEB-INF/
ibm-web-ext.xmi.
Changing the ibm-web-ext.xmi file of a WAR file:
(** I see this content in infocenter***)
Edit the extension settings as needed. You can change all of the
extension settings. The only warning is if you set the "reloadInterval"
property to zero (0) or the "reloadEnabled" property to false, the
application will no longer automatically detect changes to class files.
Both of these changes disable the automatic reloading function. The only
way to re-enable automatic reloading is to change the appropriate
property and restart the application. See other task descriptions in
this file for information on restarting an application.
-What i understood was inorder to detect changes in the application ,
customer should have specified "reloadingEnabled" property for webmodule
using AAT tool,ASTK,WSAD, or they can manually edit ibm-web-ext.xmi file and
modify these values manually .
----------------------------------------------
2. About "ReloadEnabled" in the admin console:
"ReloadEnabled" which you see in the console goes into deployment.xml file,
located in config/cells/<node_name>/applications/<ear>/deployments/<war_name>/
deployment.xml.
This property is only effective if customer performing hot deployment
operations. For web container level , customer can perform only the
following operation under hotdeployment section :
Changing or adding WAR files
You can change WAR files on application servers without having to stop
the server and start it again. This file describes--
Changing an existing JSP file
Adding a new JSP file to an existing application
Changing an existing servlet class (editing and recompiling)
Changing a dependent class of an existing servlet class
Adding a new servlet using the Invoker (Serve Servlets by class name)
facility or adding a dependent class to an existing application
Adding a new servlet, including a new definition of the servlet in the
web.xml deployment descriptor for the application
Changing the web.xml file of a WAR file
Changing the ibm-web-ext.xmi file of a WAR file
Changing the ibm-web-bnd.xmi file of a WAR file
- Pls review following section for mor info about hotdeployment and
about reload Enabled :
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp
search with "Changing or adding WAR files" .
-----------------------------------
As per the infocenter document , "reloadingEnabled" property can be
configured only in 2 ways :
1) Before deploying the application.
-There is no way available to configure during application deployment
and after application deployment from admin tools.
2) Manueally update ibm-web-ext.xmi file to reflect changes.
-------------------------------------------------------------------
Since this is documented in infocenter , i would say this is not a
defect . Pls let us know if customer any questions further .
Thanks,
Vikram Thommandru
--------------------
PS: NetworkDeployment에서 Clustering된 환경에서는 DM의 config/...쪽만 변경한 후
관리콘솔(admin console)에서 "노드동기화"를 눌러주면, 각 머신의 node로 변경이 함께
반영됩니다.
|
