Skip to content

Installing Fixes

Angel Tcholtchev edited this page Dec 20, 2017 · 5 revisions

Installing Fixes

It is very important to install latest fixes right after products are installed. Fix installation is similar to product installation.

  1. Open templates/tutorial/template.yaml in the editor
  2. Add fix.repo: ${} parameter in the default section.
  3. Add spm.fixes: ALL parameter. The default value ALL is a special value that instructs to install all applicable fixes from the source fix repository.
  4. Add fixRepo: ${fix.repo} property to the management layer to configure the source fix repository for this layer
  5. Add fixes: ${spm.fixes} property to the plugins template to instruct the template to install a list of fixes after the products have been installed.

The final template looks like this:

alias: tutorial
description: How to bootstrap local nodes
version: 0.5
changes:
  - 0.1 Initial draft
  - 0.2 Added input parameters
  - 0.3 Added local node bootstrap
  - 0.4 Added products/plugins installation
  - 0.5 Added fix installation
 
environments:
  default:
    install.dir:  ${}                              # SPM installation directory
    spm.port:     8192                             # SPM connection port
    spm.alias:    dev${spm.port}                   # SPM alias
    product.repo: ${}                              # default product repo          
    fix.repo:     ${}                              # fixes repository
    spm.fixes:    ALL                              # Default list of fixes to install
 
 
layers:                                            # LAYERS definition
  management:                                      # management layer with SPMs
    productRepo: ${product.repo}                   # product repository for this layer
    fixRepo:     ${fix.repo}                       # fix repository for this layer
    templates:   [plugins]                         # templates to apply to this layer
 
templates:                                         # TEMPLATES definition
  plugins:                                         # template alias
    products:                                      # product list to install
      ISspm:                                       # Platform Manager Plug-Ins / IS
      NUMspm:                                      # Platform Manager Plug-Ins / UM
    fixes: ${spm.fixes}                            # fixes to install
 
nodes:                                             # NODES definition
 default:                                          # defaults for any environment type
   default:                                        # default node definition
     port: ${spm.port}                             # SPM connection HTTP/S port
     secure: false                                 # do not use SSL port
     bootstrapInfo:
       installDir: ${install.dir}                  # installation directory
       installer:  ${cc.installer}                 # cc installer that can be found in cc_home/profiles/CCE/data/installers    
 
   ${spm.alias}:                                   # definition for specific nodeAlias
     host: localhost                               # Use localhost
                                                                                                                                                                    
provision:                                         # PROVISIONing mapping of layers to nodes
  default:                                         # default environment type
    management: ${spm.alias}                       # management layer is single node

Go to the environments/default/env.properties and add a fix.repo= parameter and give the alias of the previously create master fix repository. The empower fix repository contains binaries for all OSes. If using mirror repository it makes sense to have a separate one for each and every OS.

Because of a temporary problem with the fix validation, please also add skip.fix.dep.validation=true

# Defaults for windows
#cc.installer=
#install.dir=C\:\\Users\\${user.name}\\dev\\${spm.alias}
 
# Defaults for linux
#cc.installer=
#install.dir=/home/${user.name}/dev/${spm.alias}
 
# Defaults for mac
#cc.installer=
#install.dir=/Users/${user.name}/dev/${spm.alias}o
 
product.repo=
fix.repo=
 
 
#temporary limitation to avoid fix validation.
skip.fix.dep.validation=true

For cc.insataller, install.dir and product.repo use the values that you used in the previous stages.

After you're sure that all parameters are set up correctly re-import and apply the template.

[user@linuxbox tutorial]$ ant up
...
BUILD SUCCESSFUL
Total time: ....

Installing SPM fixes normally restarts SPM which depending on the Command Central version may return ERROR status of the child template application job just like for SPM plug-ins installation. The shutdown is expected and is automatically handled by Command Central with a subsequent wait and retry. Future version of Command Central may be able to handle it without reporting ERROR status at all.

When the job reports DONE the fixes are listed under Fixes tab in Web UI.

Normally when using the bootstrap installer to create new nodes, the latest fixes will already be installed - you wouldn't normally see any new fixes installed on the SPM node.

Summary

Congratulations! You've successfully installed fixes from Empower.

If you had not achieving the goals of this tutorial stage, just use the following command to checkout everything that needed to be done so far. Make a note about your modifications of environment/default/env.properties because the version that you'll check out will overwrite them.

[user@linuxbox tutorial]$ git checkout stage-05 -f
Switched to branch 'stage-05'
Clone this wiki locally