InfoCenter Home >
6: Administer applications >
6.5: Maintaining and updating applications >
6.5.2: Actions that require a restart
The table summarizes actions that require stopping a server or other
process and starting it again. The actions are usually configuration changes
to one or more administrative resources.
If you change ... |
Stop this and start it again... |
General, authentication mechanism, security server ID, or user registry
settings in the Configure Global Settings security task
|
Any WebSphere administrative servers in the administrative
domain to which the resource belongs |
Properties in the Configure Application Security task |
Any application servers on which the secured
application runs |
Properties in the Configure Resource Security task
while the Web server is running |
Any WebSphere administrative servers in the administrative
domain to which the resource belongs |
Servlet engine queue type or transport properties |
Any application servers containing the servlet engine |
Web application properties or contents |
The Web application whose properties you changed (perform a "Restart Web App") |
Servlet properties |
Any Web application containing the servlet |
Database-related properties for a given Session Manager |
The Session Manager
Specifically:
- Changes on the Tuning and Persistence tabbed pages take effect the next time the
application server containing the Session Manager is started.
- Changes on the Persistence and Interval tabbed pages take effect immediately.
- Changes on the Enable tab vary. See the individual property descriptions.
|
User profile properties |
Any application servers containing the user profile |
Virtual host properties |
Any application servers that contain the resources associated
with the virtual host, if they were running when the virtual host properties
were changed. See below for an example. |
Example of virtual host changes requiring a restart
Suppose the administrator decides to add an alias newalias to
a virtual host that has three servlets. Two of the servlets are running
on application_server_1 and the other servlet is running on
application_server_2.
The administrator adds the new alias to the virtual host properties while
application_server_1 and application_server_2 are running. Users will not
be able to access the servlets by the URL http://newalias/servlet_name
until the administrator stops the two application servers and starts them again.
|
Related topics |
|
| Home (Getting started page) |
|
InfoCenter |
|
To launch the full documentation set in a separate browser window, click: |
| Display InfoCenter |
| |
PDF library |
|
To browse the PDF library for this product, containing this article and others, click: |
| PDF versions |
| |
Using this documentation |
|
Become an InfoCenter super user! To find out more about navigation, numbering, search, downloads, and more, click: |
| Using this documentation |
| |
|