IBM Support

Rolling Update XSLD fix packs using IBM Installation Manager

How To


Summary

This document explains detailed steps for updating XSLD server.

Steps

1.  [8.6.1.4+]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}
 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. Verify whether Derby Replication is enabled and take the backup of Derby Database before proceeding further. 
      a. If DerbyReplication is enabled, run DisableDerbyReplicationTaskCommand.
      b. Disable AutoDerbyReplication  
      c. Stop the Primary Derby Server
          <InstallPath>/wxs/derby/script/stopNetWorkServer.sh 
     d. Back up the Derby Database by copying <InstallPath>/wxs/derby/script/wxsdb directory
     e.  Start the Primary Derby Server
          <InstallPath>/wxs/derby/script/startNetWorkServer.sh

3. Update catalog and container servers.
    a. If MMR is used in the environment, break the MMR link.
    b. Run the xscmd showPrimaryCatalogServer command to identify the primary and non-primary catalog servers.
           xscmd -c showPrimaryCatalogServer
    
      Repeat steps 4-10 for each XSLD member in the following sequence
          i.  Update the XSLD member hosting non-primary catalog server one at a time.
         ii.  Update the XSLD member hosting primary catalog server last.
         iii. Update any remaining XSLD members, if any. These servers are not hosting catalog servers, but only container servers.
4.  Run the stopXSLD and stopNetWorkServer command to stop all XSLD processes that are running in the server.
Linux
<InstallPath>/wxs/stopXSLD.sh
<InstallPath>/wxs/derby/script/stopNetWorkServer.sh
 
Windows
<InstallPath>\wxs\stopXSLD.bat
<InstallPath>\wxs\derby\script\stopNetworkServer.bat
Where <InstallPath> is XSLD installation path
5. In Installation Manager, install the XSLD fix pack.
    a. Specify a repository for the XSLD fix pack.
    b. Click Update.
    c. Select the package group to update.
    d. In Update Packages, select the fix pack to install.
    e. Click Next.
    f. Click Update.
    g. After the installation completes, click Finish.
6. 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:
   a.  Create your custom keystore and truststore.
   b. Import your custom certificates to the custom truststore.
   c. Upload both the keystore and truststore to XSLD.

7. [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 or Administrative 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

8. [8.6.1.5+]Derby database upgrade will happen in background, so verify no derby process is running post update and before running startXSLD.
Linux
    ps -ef | grep derby
   If derby process is running wait until it completes. It generally takes less than 30 seconds.
9. [8.6.1.5+] [Windows only] [Optional] Update restConnector-1.0 to restConnector-2.0 as below in all mentioned files.
<feature>restConnector-2.0</feature>
Files to update:
<InstallPath>\wlp\usr\servers\<catalogServer>\server.xml
<InstallPath>\wlp\usr\servers\<containerServer>\server.xml
<InstallPath>\wlp\usr\servers\wlp\usr\servers\restAdminServer\server.xml
<InstallPath>\wlp\usr\servers\wlp\usr\servers\restDataServer\server.xml
<InstallPath>\wlp\usr\servers\wlp\usr\servers\restUIServer\server.xml
<InstallPath>\wlp\wxs\servers\xscmd\server.xml
10. Run the startXSLD command to start XSLD.
Linux
<InstallPath>/wxs/startXSLD.sh
Windows
<InstallPath>\wxs\startXSLD.bat
11. [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

Document Location

Worldwide

[{"Type":"SW","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSTVLU","label":"WebSphere eXtreme Scale"},"ARM Category":[{"code":"a8m0z000000bnqyAAA","label":"Extreme Scale->XSLD"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"8.6.1"}]

Document Information

Modified date:
11 August 2021

UID

ibm16455169

Page Feedback