This article describes post-installation tasks that you complete after applying a new service level.
About this task
See Applying product maintenance on z/OS,
for more information about applying service to WebSphere® Application
Server for z/OS®.
The post-installation functionality
includes actions you perform the first time the server is restarted
after you install service with SMP/E. This applies to WebSphere Application
Server for z/OS as well as WebSphere Business
Integration Server Foundation for z/OS.
Depending on your system restrictions, you can choose to initialize
post-installation processing either automatically or manually.
Automatic
mode, which is recommended, includes a new step that automatically
launches the "applyPTF.sh" shell script in the server procedure. The applyPTF.sh script,
which is located in your bin directory (was_home/bin,
where was_home is the absolute path of the WebSphere runtime home directory), verifies
that any pending post-installation actions are properly applied before
starting the server.
Manual mode is necessary only if the automatic
mode does not conform to your organization standards (if multistep
procedures are not allowed for example), if there is something else
in your configuration that prevents the applyPTF.sh shell
script from running properly, or if you are applying a particular
service release that requires manual intervention. Refer to the section
below, "Running the post installer manually," for more information.
Post-installtion
processing executes under the controller proc, so it executes with
the identity assigned to that particular proc. While that identity
has sufficient authority to perform most file system actions required
on the WebSphere runtime home directory, you cannot
assume it to have the appropriate authority for your
applyPTF.sh shell
script. Therefore, you cannot perform any post-installationon that
requires special authority by "inline" apply processing. You must
manually perform any such apply processing in "batch" mode, running
applyPTF.sh or
the appropriate jobs from a user that has the needed authority to
apply a particular action.
Note:
- Before you run applyPTF.sh, ensure that WebSphere Application Server for z/OS is
running with code page IBM-1047. See Preparing z/OS to run WebSphere Application Server for more information.
- When you launch the shell script from the server proc, it automatically
runs in "inline" mode and can only apply service that qualifies as
"inline."
- If batch service is delivered, you'll find the needed user authority
noted in the service level documentation.
You can run the post-installer either automatically
or manually. Follow the set of steps below that applies to your circumstance.
What to do next
The post installer component enforces that certain actions
are performed successfully and preconditions are met before applying
service, otherwise, warnings or error messages result. If you launched
the applyPTF.sh script from the server proc, the output is appended
to the was_home/properties/service/logs/applyPTF.out file.
If you run applyPTF.sh manually from the shell,
the output goes right to stdout (on the shell from where the applyPTF.sh script
was run) and WTO messages are issued. In the latter case, no output
is appended to the applyPTF.log log file.
Whenever
actions are performed on the runtime home directory, a log file is
kept. When warnings or errors occur, the absolute path to the log
file is displayed so that you can examine the details of the problem.
The following is a list of common errors that might occur when the
post installer (
applyPTF.sh) applies service.
The errors will most likely appear in the form of error codes on the
console on which
applyPTF.sh was issued.
- The post installer ran and determined that SMP/E restored the
SMP/E home directory to a previous level of service than that at which
the WebSphere runtime home directory is running.
- This occurs if you used SMP/E to restore to the previous accepted
service level without first running the backoutPTF.sh shell
script. The server will not start if it detects this condition, and
post-installation action halts without applying service.
- The post installer issued a warning message while installing service.
- The WebSphere Application Server for z/OS multiproduct
PTF post installer detected warnings that were issued during the application
of post-installation service for the product listed. The application
of service was successful, but the warning messages should be examined.
The warning messages are listed in the log file in the HFS file that
is specified in the message.
- The post installer incurred an error and stopped processing.
- The WebSphere Application Server for z/OS multiproduct
PTF post installer encountered an error while installing service for
the product indicated in the message. The details of the error are
contained in the HFS log file that is specified in the message. When
this happens, review the log and correct the error. The servers will
not be permitted to start until the error is corrected.
- The post installer encountered warnings while applying service.
- The WebSphere Application Server for z/OS multiproduct
PTF post installer detected warnings that were issued during the application
of post-installation service. The warnings might have been issued
while post-installation service was being applied for WebSphere Application
Server for z/OS or any of the extension products that are
installed. A BBOO0250W message should have already been issued for
each product that encountered warnings when the post-installation
service was applied.
Reply with Continue to
continue starting the application server. Reply with Cancel to
cancel starting the application server. Because service has already
been completed, the multiproduct PTF post installer will not run again
the next time the server is restarted.
- Running the post installer manually.
- As mentioned above, there are reasons why an organization might
require the post installer to be run manually, also known as batch
mode. The post installer will not allow post install service to be
applied if a node is moved to a different system other than the system
where it was configured. (In this case the WTO BBOO0287A will be issued)
. Running the post installer in batch mode, however, will apply post
install service to a node, even if it is now located on a system other
than the one where it was originally configured.
The post installer
can be invoked manually by using either of the two following procedures:
- Run the batch job that was created by the customization tool walkthrough
(CNTL dataset) for each node. Use BBOWAPLB for standalone application
server nodes and BBOWAPLD for Network Deployment cell nodes.
- Invoke the shell script directly. It is stored in the /bin directory
of each node. From OMVS running under the authority of the WebSphere Admin ID, issue the ./applyPTF.sh
batch shell script.