IBM Support

Rolling Update XSLD fix packs using IBM Installation Manager

How To


Summary

This document explains detailed steps for updating XSLD server.

Environment

Note: Extract XSLD-upgrade-script-files.zip, attached at the bottom of this article, for the following files:
  • collectConfigFiles.bat
  • restoreConfigFiles.bat
  • collectConfigFiles.sh
  • restoreConfigFiles.sh

Steps

Preparations
  1. Verify whether AutoDBReplicaiton is enabled by running below curl command. 
    > curl -k -u xsadmin:xsadmin4Me! -X GET --header 'Accept: application/json' 'https://jsmith.abc.com:9445/wxsadmin/v1/runtimesetting/AutoDBReplication'
{"passwd":false,"name":"AutoDBReplication","value":"true","updatedTime":1621441925826}
    1. If the value is true as stated in above example, disable the AutoDBReplcation by running below curl command. 
      > curl -k -u xsadmin:xsadmin4Me! -X PUT -H "Content-Type:application/json" -d "{\"value\":\"false\"}"    https://jsmith.abc.com:9445/wxsadmin/v1/runtimesetting/AutoDBReplication
    2. Run DisableDerbyReplicationTaskCommand to remove DB replication. For more information, see DisableDerbyReplicationTaskCommand.
  2. Update catalog and container servers.
    1. If MMR is used in the environment, break the MMR link.
    2. Check the db_host in <XSLD InstallPath>/wlp/usr/shared/resources/dbconfig.json for primary DB server.
Procedure Overview
  1. Repeat the 12-step procedure described in XSLD Member Rolling Update Procedure for each XSLD member in the following order.
    1. Update the XSLD member hosting non-primary DB servers one at a time.
    2. Update the XSLD member hosting primary DB server last. Before updating primary DB, run SetupDerbyReplicationTaskCommand on any other machine containing catalog server. For more information, see DisableDerbyReplicationTaskCommand.        
  2. Wait for some time for the DB replication to complete. Monitor for below in the ./wlp/startscripts/nanny/log/nanny.log in primary DB server to check if derby replication is complete. 
    "DB is on the replica mode, Primay hostname = <primaryHost> and Replica hostname = <replicaHost>"
  3. After DB replication is complete, proceed to XSLD Member Rolling Update Procedure.
XSLD Member Rolling Update Procedure
           
  1. Run the stopXSLD and stopNetWorkServer command to stop all XSLD processes that are running in the server.
    Linux 
    <InstallPath>/wxs/stopXSLD.sh|stopXSLD.bat
    <InstallPath>/wxs/derby/script/stopNetWorkServer.sh|stopNetWorkServer.bat

    <InstallPath> is the XSLD installation path.

  2. Take the backup of configurations by running the following command with quotes: 
    collectConfigFiles.sh "<InstallPath>" "<path to place the backup files>"

    or

    collectConfigFiles.bat "<InstallPath>" "<path to place the backup files>"

    The path should be Fully Qualified path.
    After running the command, verify the folder for collected_files.tar.gz to check if backup is successful.
     

  3. Run the following command: 
    <InstallPath>/wxs/uninstallAll.sh

    or

    <InstallPath>/wxs/uninstallAll.bat
  4. Uninstall XSLD from Installation Manager and delete the installation folder <InstallPath>.
  5. Install the XSLD 8.6.2.0 refresh pack. Use same <InstallPath> as before. 
    Note : Install in the same path as previous installation
    Use the same cacheGroup name/memory size/secret/password as used in previous installation
  6.  Run the following command. 
    <InstallPath>/createGridServers.<sh||bat>
  7. Run the following command. 
    stopNetworkServer<sh||bat> 
  8. Restore the backup files by running the following command with fully Qualified Path in Quotes: 
    restoreConfigFiles.sh "<path of collected_files.tar.gz>" "<InstallPath>"

    or

    restoreConfigFiles.bat "<path of collected_files.tar.gz>" "<InstallPath>"
  9. If you used a custom certificate for the XSLD truststore, you might need to import custom certificates. During fix pack installation, the installer upgrades XSLD keystores and truststores. After upgrading, XSLD might not be able to communicate with the secure LDAP server. To reestablish communication between XSLD and the secure LDAP server, import custom certificates:
    1.    Create your custom keystore and truststore.
    2.    Import your custom certificates to the custom truststore.
    3.    Upload both the keystore and truststore to XSLD.
  10. [8.6.1.3+] If you are completing a non-root installation and are upgrading XSLD from version 8.6.1.1 or later, log in as a root user and then run registerServices.sh to register services. Unless you run the registerServices command as root after the upgrade, XSLD won't start. For details on how to run the registerServices command, see Installing XSLD as non-root user.
  11. Run the startXSLD command to start XSLD.
    1. [non-root installation] registerService.sh|registerService.bat <non-root> with root user login
    2. <InstallPath>/wxs/startXSLD.sh|startXSLD.bat
    3. Verify if the updated machine joined with the cacheGroup and able to replicate data before proceeding with the other machines upgrades
    4. Run XSCMD showPlacement command and check if the newly upgraded machine is shown in the output along with other machines 
  12. [8.6.1.4+] [Optional]  After update is completed on all XSLD members, enable AutoDBReplication.
    Note: It is recommended to enable AutoDBReplicaiton for high availability of restServers.

Additional Information

Rollback is not possible as XSLD is uninstalled before upgrading to WXS 8.6.2.0.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"ARM Category":[{"code":"a8m50000000L2AFAA0","label":"IBM WebSphere Extreme Scale"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.6.2"}]

Document Information

Modified date:
08 October 2025

UID

ibm17246118

Page Feedback