Why and when to perform this task
This topic describes post-install tasks you complete after applying a new service level.
The post-install 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-install 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 run-time home directory), makes sure that any pending post-install actions are properly applied before starting the server.
Manual mode is necessary only if the automatic mode does not conform to your organization standards (for example, if multi-step procedures are not allowed), 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. See below for more details on using manual mode.
Post-install 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 HFS file actions required on the WebSphere run-time home directory, you cannot assume it to have the appropriate authority for your applyPTF.sh shell script. Therefore, you cannot perform any post-install action 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:
You can run the post installer either automatically or manually. Follow the set of steps below that applies to your circumstance.
Steps for this task
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 file $WAS_HOME/properties/service/logs/ applyPTF.out. If you ran 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 run-time 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.
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 multi-product PTF post installer will not run again the next time the server is restarted.
The post installer can be invoked manually by using either of the two following procedures: