WAS v8.0 > Install the application serving environment > Distributed operating systems > Install the product > Use the post-installer after updating or rolling back to a different service level

Complete 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.

The post-installation functionality includes actions 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. We 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 WAS_HOME/bin/postinstall.sh or WAS_HOME/bin/postinstall.bat with the following parameters (on one line):

  -WS_CMT_CONF_DIR WAS_HOME/properties/postinstall/
  -MASTER_ACTION_REGISTRY WAS_HOME/properties/postinstall/masterRegistry.xml
  -SUB_ACTION_REGISTRY WAS_HOME/properties/postinstall/cacheRegistry.xml
  -WS_PI_ACTION_REGISTRY_EXTENSION WAS_HOME/properties/postinstall/registryExtension.xml
  -WS_CMT_LOG_HOME WAS_HOME/logs/postinstall/
  -POSTINSTALL_LOG_FILE WAS_HOME/logs/postinstall/postinstall.log
  

  Application Client for IBM WAS and IBM HTTP Server for WAS also use the post-installer at installation time. If the post-installer fails, the installation completes with warnings just like for WAS and recovery is very similar. Simply replace WAS_HOME 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 WAS_HOME.

  • 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 WAS
     PROFILE_ROOT/properties/service/productDir/WebSphere/logs/postinstall.log
     Configuration-manager log specific to a run of the post-installer for WAS
     PROFILE_ROOT/properties/service/productDir/WebSphere/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.

Procedure

• Run the post-installer automatically.

  This is running under the authority of the WebSphere Admin ID.

• Run the post-installer manually.

+

Search Tips   |   Advanced Search