File name: tins_prodmaintenance.html
Applying product maintenance on z/OS
Maintaining WebSphere® Application Server
requires an in-depth knowledge of MVS service
techniques and the product service stream. This is especially important
in a high yield production environment where availability is of the
utmost importance. Therefore, planning service and knowing how to
best apply service are essential skills.
Before you begin
Contact the IBM® Software Support Center for
information about preventive service planning (PSP) upgrades for WebSphere Application Server for z/OS®.
For more information about PSP upgrades, see the WebSphere Application
Server for z/OS: Program Directory. Although the Program
Directory contains a list of required program temporary fixes
(PTFs), the most current information is available from the IBM Software
Support Center.
The z/OS System Modification Program
Extended (SMP/E) program is used to apply product maintenance to WebSphere Application Server for z/OS.
The WebSphere Application Server update installer
is not used under z/OS. A set of scripts called
the post-installer, a part of WebSphere Application
Server for z/OS, is used to make any configuration file
system changes that are required as a consequence of product-maintenance.
About this task
Use the following procedure whenever you want to apply a
new service release to your system.
Procedure
- Decide whether to run the post-installer automatically
or manually. See Applying a service level or restoring to the previous accepted service level for
more information.
- Make copies of your product datasets and file system structure.
- Ensure your deployment manager node is at the same or a
later service level than the application server nodes.
- Use SMP/E to apply the required maintenance to the copies
of your product dataset and file system structure.
Avoid trouble: Be aware of the following issues:
gotcha
- Stop the application servers and the WebSphere Application
Server for z/OS location service daemon.
- Stop CTRACE.
- Switch to the newly serviced WebSphere Application
Server for z/OS product datasets. You can do
this one of two ways:
- Rename the new datasets to replace the old ones.
- Recatalog the product datasets if the names are identical,
or change WebSphere Application Server for z/OS cataloged
procedures to refer explicitly to the new datasets.
Note: If
you use new dataset names, you need to also handle program controls,
so ensure you update the program control list.
Verify that the MVS link list and APF list refer
to the newly-serviced datasets.
- If the WebSphere Application Server
for z/OS runtime is loaded into the link pack area,
delete the old modules and load the new ones, or IPL the system to
load the new modules into the LPA.
- Verify that the newly-serviced product file system is correctly
mounted.
- Perform any other migration actions as instructed in PTF
or APAR cover letters.
- Start the location service daemon and application servers.
- Complete any necessary post-installation tasks. In particular,
make sure that the post-installer is run (either automatically or
manually) against each node in order to update the configuration file
system to the new service level. For more information, refer to Completing post-installation tasks after using SMP/E to apply a new service level.
In this information ...
| IBM Redbooks, demos, education, and more(Index)
Most of the following links will take you to information that is not part of the formal product documentation and is provided "as is." Some of these links go to non-IBM Web sites and are provided for your convenience only and do not in any manner serve as an endorsement by IBM of those Web sites, the material thereon, or the owner thereof.
|
|
