Installing service for System Automation for Multiplatforms

Installing service means upgrading System Automation for Multiplatforms from release 4.1. Therefore, release 4.1 must be installed before any service can be applied.

Before you begin:
  • Product fix packs are always cumulative.
  • You must have root authority to install a product fix pack.
  • When you downloaded the archives from the System Automation for Multiplatforms support site (see Obtaining fix packs), unpack the product fix pack archive to a temporary directory. For information about how to unpack the archive for your operating system, see Usage instructions for platform-specific archives.
  • Back up your system configuration before you install the service fix pack. For more information, see Managing XML automation policies.
  • To minimize downtime, you can run a prerequisites check before you start the installation. For more information, see Checking prerequisites.
Perform the following steps on each node in the peer domain:

  1. Check whether any resources are online on the node you want to service:

    • If resources are online and must be kept available, exclude the node from automation:
      samctrl -u a <node>
      System Automation for Multiplatforms stops the resources on the node and, if possible, restarts them on a different node in the peer domain.
    • If the resources need not to be kept available during service, bring the resource groups offline.

  2. Stop the node from another node in the domain, and verify that it is stopped: 

    stoprpnode <node>; lsrpnode

  3. After you received the archives, extract them. They create a directory structure with root directory SAM41mfMP, where mf stands for modification level and fix level.

  4. Install the service fix pack with the installSAM script. For detailed information about the script, refer to Running the installation.

  5. Start the node: 
    startrpnode <node>
  6. If you excluded the node in step 2, include the node to the automation:
    samctrl -u d <node>

  7. If you require the resource groups to be online, bring the resource groups online. Otherwise, delay this step until the last node in the peer domain is serviced.

  8. After all nodes are serviced, run the steps that are described in Completing the migration. The changes become effective in the entire domain and the correct version is shown.