Completing post-installation tasks after updating or rolling back to a different service level

This article describes post-installation tasks that you complete after applying a new service level.

About this task

The post-installation functionality includes actions that are performed at the following times:
  • At installation time

    Installation Manager calls the post-installer for any non-profile related configuration actions using positnstall.sh or positnstall.bat. You can see a mention of the post-installer in the installation log.

    Installation manager considers the post-installation step a nonfatal one; therefore, it does not roll back the installation if the post-installer returns FAIL or PARTIAL SUCCESS. Installation manager will display The packages are installed with warnings at the end of the installation. If the post-installation action fails, run app_server_root/bin/postinstall.sh or app_server_root/bin/postinstall.bat with the following parameters (on one line):
    -WS_CMT_CONF_DIR app_server_root/properties/postinstall/
    -MASTER_ACTION_REGISTRY app_server_root/properties/postinstall/masterRegistry.xml
    -SUB_ACTION_REGISTRY app_server_root/properties/postinstall/cacheRegistry.xml
    -WS_PI_ACTION_REGISTRY_EXTENSION app_server_root/properties/postinstall/registryExtension.xml
    -WS_CMT_LOG_HOME app_server_root/logs/postinstall/
    -POSTINSTALL_LOG_FILE app_server_root/logs/postinstall/postinstall.log
    Note: Application Client for IBM® WebSphere® Application Server and IBM HTTP Server for WebSphere Application Server also use the post-installer at installation time. If the post-installer fails, the installation completes with warnings just like for WebSphere Application Server and recovery is very similar. Simply replace app_server_root in the example with app_client_root or IHS_root.
  • At server-startup time
    The runConfigActions.sh or runConfigActions.bat script runs before server startup. This script runs all the necessary configuration actions for all product fix packs and interim fixes that are installed in app_server_root.
    • If the script returns RC=0 (SUCCESS) or RC=2 (PARTIAL SUCCESS), the server starts.
    • If the script returns RC=1 (FAIL), the server does not start.
    If the runConfigActions script returns FAIL or PARTIAL SUCCESS, complete the following actions:
    1. Read the logs.
      The logs are in the following locations:
      Overall log for all products installed
      profile_root/properties/service/productDir/runConfigActions.log
      Log specific to WebSphere Application Server
      profile_root/properties/service/productDir/WebSphere/logs/postinstall.log
      profile_root/properties/service/productDir/PreConfigActions/logs/postinstall.log
      Configuration-manager log specific to a run of the post-installer for WebSphere Application Server
      profile_root/properties/service/productDir/WebSphere/logs/postinstallerConfigActionstimestamp.log
      profile_root/properties/service/productDir/PreConfigActions/logs/postinstallerConfigActionstimestamp.log
      Log specific to a stack product or feature pack
      profile_root/properties/service/productDir/product_name/logs/postinstall.log
      Configuration-manager log specific to a run of the post-installer for a stack product or feature pack
      profile_root/properties/service/productDir/product_name/logs/postinstallerConfigActionstimestamp.log
      Log specific to an interim fix for a stack product or feature pack
      profile_root/properties/service/productDir/product_name/iFixes/interim_fix_name/logs/postinstall.log
      Configuration-manager log specific to a run of the post-installer for an interim fix for a stack product or feature pack
      profile_root/properties/service/productDir/product_name/iFixes/interim_fix_name/logs/postinstallerConfigActionstimestamp.log
    2. Fix any problems.
    3. Start the server again, or run profile_root/bin/runConfigActions.sh or profile_root/bin/runConfigActions.bat.

      The user running the script must have enough authority to update the profile—in other words, enough authority to start the server.

This applies to all platforms as well as any feature pack, interim fix, or stack product that requires post-installation tasks at server startup.
Depending on your system restrictions, you can choose to initialize post-installation processing either automatically or manually.
  • Automatic mode, which is recommended, includes a step that automatically launches the runConfigActions.sh or runConfigActions.bat script before starting the server. The runConfigActions script, which is located in your profile_root/bin 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 there is something else in your configuration that prevents the runConfigActions script from running properly, or if you are applying a particular service release that requires manual intervention.

If batch service is delivered, you'll find the needed user authority noted in the service-level documentation.

[Updated in July 2012] After you apply a service update, and run startServer for the first time, you can modify the permissions for a specific profile, as needed. To ensure that these permissions do not change when you run startServer subsequent times, you can create a file called runConfigActions.disableAtServerStartup, and place it in the profile_root/properties/service/ directory. Subsequent startServer invocations will not run the Postinstaller for this profile, and the permissions for this profile will retain their settings. However, the next time you need to apply service, you must remember to delete this file before you run startServer. After you run startSterver you must reset the permissions for this profile, and then recreate the runConfigActions.disableAtServerStartup file. [Updated in July 2012]

jul2012

Procedure




In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Feb 6, 2014 11:24:07 PM CST
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=matt&product=was-nd-zos&topic=tins_postinstallapp
File name: tins_postinstallapp.html