Sun Microsystems Logo
Products and Services
 
Support and Training
 
 

A  B  C  D  E  F  G  H  I  J  K  L  M  N  O  P  Q  R  S  T  U  V  W  X  Y  Z  
 
File Formatssoftware.conf(4)


NAME

 software.conf - SMCT configuration file to define the additional software packages and patches to be deployed to each node group

SYNOPSIS

 SMCT_CONFIG_DIR/services/node_group_name.architecture.operating_system
 config-dir/services/node_group_name.architecture.operating_system

DESCRIPTION

Do not use the SMCT tool with the current patch level of the Foundation Services product.

The software configuration file is an optional file that defines the additional software packages and patches to be deployed to a specific node group. There must be a software configuration file for each node group that contains user applications.

The software configuration file must be named in the following format:

node_group_name.architecture.operating_system

  • node_group_name

    Name of the node group, as defined in the cluster.conf file, for example, master_el.

  • architecture

    This must be set to SPARC.

  • operating_system

    This must be set to SOLARIS.

For example, the software configuration file for a node group called master_el would be master_el.SPARC.SOLARIS.

PARAMETERS FOR ADDING PACKAGES

Use the following syntax to describe software packages:

{ ELEMENT software software_location
              type PACKAGE
              mode mode_value
              [name name_value]
              [version version_value]
              [base base_dir]
              [adminFile adminFile_location]
              [responseFile responsefile_location]
       }*
  • software_location

    Location of the package expressed as a URI.

  • mode_value

    Package installation mode. This value can be one of the following:

    • LOCAL

      The installation directory relative to the node root file system.

    • SHARED

      The installation base directory relative to the diskless node group shared file system, /usr, or the shared file system mount point for the master-eligible nodes.

  • name_value

    Name of the package. If this parameter is defined, it must match the package name.

  • version_value

    Version of the package. If this parameter is defined, it must match the package version.

  • base_dir

    Package installation directory. This parameter overrides the default installation directory.

  • adminFile_location

    Location of the special package administration file used by the pkgadd tool.

  • responsefile_location

    Location of the special package response file used by the pkgadd tool.

PARAMETERS FOR ADDING PATCHES

Use the following syntax to describe the software patches:

{ ELEMENT software software-location
              type type-value
              mode mode-value
              [name name-value]
              [version version-value]
       }*             
  • software_location

    Location of the patch expressed as a URI.

  • type_value

    Package type. This value can be one of:

    • PRE_PATCH

      Installs the patch after the Solaris operating system packages have been installed, but before the Foundation Services packages and the user-defined applications have been installed.

    • POST_PATCH

      Installs the patch after the Solaris operating system packages, the Foundation Services packages, and the user-defined applications have been installed.

  • mode_value

    The patch installation mode. This value can be one of the following:

    • LOCAL

      The installation base directory relative to the root file system of the node.

    • SHARED

      The installation base directory relative to the shared file system of the diskless node group, /usr, or the shared file system mount point for the master-eligible nodes.

  • name_value

    Name of the patch. If this parameter is defined, it must match the patch name.

  • version_value

    Version of the patch. if this parameter is defined, it must match the patch version.

PARAMETERS FOR ADDING SOFTWARE DISTRIBUTIONS

Use the following syntax to describe the software distribution:

{ ELEMENT software software-location
               [installScript install-script_location
               type type-value
               [name name-value]
               [version version-value]
       }*             
  • software_location

    Location of the software distribution expressed as a URI.

  • install_script_location

    Location of the installation script expressed as a URI.

  • type_value

    Software distribution type. This parameter must be set to GENERIC.

  • name_value

    Name of the software.

  • version_value

    Version of the software.

EXAMPLE

The following is an example of a software configuration file master_el.SPARC.SOLARIS, for a node group master_el:

ELEMENT software 'file:/<DS_DIR>/directory-5.1-us.sparc-sun-solaris2.8.tar.gz'
        installScript 'file:/<DS_DIR>/ldap-install.sh'
        type GENERIC name ldap-ds version 5.1

ELEMENT software 'file:/<APPS_PKG_DIR>/SUNWnhhad' mode SHARED
        base /<--SWLID-->/opt
        type PACKAGE  

ELEMENT software 'file:/<APPS_PKG_DIR>/SUNWnhccs' mode SHARED
        base /<--SWLID-->/opt
        type PACKAGE 

ELEMENT software 'file:/<APPS_PKG_DIR>/SUNWnhmes' mode SHARED 
        base /<--SWLID-->/opt
        type PACKAGE

ELEMENT software 'file:/<APPS_PKG_DIR>/SUNWnhapp' mode LOCAL 
        responseFile 'file:/export/home/LDAP/SUNWnhapp.resp'
        type PACKAGE

ELEMENT software 'file:/<SMCT_SOL_DIR>/Solaris_9/Product/SUNWxcu4' mode LOCAL
        type PACKAGE

ELEMENT software 'file:/<SOL_PAT_DIR>/108434-06' mode LOCAL
        type POST_PATCH  version 06

ELEMENT software 'file:/<SOL_PAT_DIR>/108435-06' mode LOCAL
        type POST_PATCH  version 06

ATTRIBUTES

See attributes(5) for descriptions of the following attributes:

ATTRIBUTE TYPEATTRIBUTE VALUE
ArchitectureSPARC
AvailabilitySUNWnhsmc
Interface StabilityEvolving

SEE ALSO

slcreate(1M)


Netra HAS FS 2.1Go To TopLast Changed September 2004