Difference between revisions of "Automatic Updates"

From SEPsesam
Jump to: navigation, search
(Added missing anchors, fixed links to existing anchors, added Special:MyLanguages to links and prepared for translation.)
Line 1: Line 1:
{{Navigation_latest|release=4.4.3|link=[[SEP_sesam_Documentation#Previous_versions|Documentation archive]]}}
+
<languages />
{{Copyright SEP AG|en}}
+
<translate>{{Copyright SEP AG|en}}
  
==Overview==
+
 
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b>Additional resources</b></center>
+
 
 +
{{Navigation_latest|release=4.4.3|link=[[SEP_sesam_Documentation#previous|Documentation archive]]}}
 +
 
 +
==Overview==</translate>
 +
<div class="boilerplate metadata" id="Additional resources" style="background-color:#ecedf1; color:#8695a7; border: 1px ridge #cdd3db; margin: 0.5em; padding: 0.5em; float: right; width: 35%; "><center><b><translate>Additional resources</translate></b></center>
  
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_Sesam_CLI]]
 
| rowspan="2" style="padding:0px 10px 0px;" |[[File:SEP_next.png|45px|link=Special:MyLanguage/SEP_Sesam_CLI]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | See also: [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Applying Service Packs on Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] – [[Release Notes]]
+
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>See also: [[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Applying Service Packs on Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]] – [[Special:MyLanguage/Release_Notes|Release Notes]]</translate>
 
|}
 
|}
  
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=SEP sesam OS and Database Support Matrix|]]
+
| rowspan="2" style="padding:0px 10px 0px;" | [[File:support-matrix.png|45px|link=SEP_sesam_OS_and_Database_Support_Matrix|]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Check supported [[SEP sesam OS and Database Support Matrix|configurations and versions]] and [[Special:MyLanguage/Java_Compatibility_Matrix|Java compatibility matrix]].
+
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Check supported [[Special:MyLanguage/SEP_sesam_OS_and_Database_Support_Matrix|configurations and versions]] and [[Special:MyLanguage/Java_Compatibility_Matrix|Java compatibility matrix]].</translate>
 
|}
 
|}
  
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_Video.png|45px|link=Video Tutorials & Screencasts|]]
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP_Video.png|45px|link=Video Tutorials & Screencasts|]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Watch SEP sesam [[Special:MyLanguage/Video Tutorials & Screencasts#installation|installation videos & screencasts]].
+
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Watch SEP sesam [[Special:MyLanguage/Video_Tutorials_&_Screencasts#installation|installation videos & screencasts]].</translate>
 
|}
 
|}
  
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Tip.png|45px|link=Special:MyLanguage/FAQ|FAQ]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Check [[Special:MyLanguage/FAQ#installation_and_configuration|FAQ]] for installation and configuration issues.
+
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Check [[Special:MyLanguage/FAQ#installation_and_configuration|FAQ]] for installation and configuration issues.</translate>
 
|}
 
|}
  
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
{|style="margin: auto; margin-bottom:1em; width:100%; border:0px solid grey;"
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]
 
| rowspan="2" style="padding:0px 10px 0px;" | [[File:SEP Troubleshooting.png|45px|link=Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | Problems? See the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]].  
+
| style="padding:0px 40px 0px 10px; color: grey; font-size: 90%; text-align:left;" | <translate>Problems? See the [[Special:MyLanguage/Troubleshooting_Guide|Troubleshooting Guide]]. </translate>
 
|}</div>
 
|}</div>
 +
<translate>SEP sesam provides free updates from previous versions of SEP sesam to new versions and new features within the [[Special:MyLanguage/Licensing#maintenance|maintenance period]]. You can enable a SEP sesam Server to check for the relevant updates and remotely update your clients by using the [[Special:MyLanguage/Updating_SEP_sesam#CLI|CLI command <tt>sm_update_client</tt>]].</translate>
 +
<onlyinclude>
 +
<translate>=={{anchor|sm_update}}Using <tt>sm_update_client</tt> for automatic updates==
  
SEP sesam provides free updates from previous versions of SEP sesam to new versions and new features within the [[Special:MyLanguage/Licensing#SEP_Maintenance|maintenance period]]. You can enable a SEP sesam Server to check for the relevant updates and remotely update your clients by using the [[Special:MyLanguage/Updating_SEP_sesam#CLI|CLI command <tt>sm_update_client</tt>]].
 
<onlyinclude>
 
=={{anchor|sm_update}}Using <tt>sm_update_client</tt> for automatic updates==
 
 
The <tt>sm_update_client</tt> command is used to automatically update all clients, RDS, and GUI (including a client). The <tt>sm_update_client</tt> command uses [http://download.sep.de/ SEP sesam download center] to check for new installation packages available for the configured clients.
 
The <tt>sm_update_client</tt> command is used to automatically update all clients, RDS, and GUI (including a client). The <tt>sm_update_client</tt> command uses [http://download.sep.de/ SEP sesam download center] to check for new installation packages available for the configured clients.
  
The following applies for updating components:
+
The following applies for updating components:</translate>
*'''On Linux''', a specific component is always required for an update: a ''client'' can be updated using a SEP sesam Client package, updating ''GUI'' requires a GUI package, and ''RDS'' requires an RDS package.  
+
*<translate>'''On Linux''', a specific component is always required for an update: a ''client'' can be updated using a SEP sesam Client package, updating ''GUI'' requires a GUI package, and ''RDS'' requires an RDS package. </translate>
*'''On Windows''', a ''client'' can be updated with any of the three installation packages, updating GUI can be done with either the GUI or SEP sesam Server package, and ''RDS'' requires a server package.  
+
 
 +
*<translate>'''On Windows''', a ''client'' can be updated with any of the three installation packages, updating GUI can be done with either the GUI or SEP sesam Server package, and ''RDS'' requires a server package.  
  
 
The <tt>sm_update_client</tt> executable is located in the {{Sesamroot|/bin/sesam/}}, for example <tt>c:\Program Files\SEPsesam\bin\sesam\</tt> on Windows. The <tt>sm_update_client</tt> command is aware of the operating system of the component that needs to be updated and does not perform an update if the available update package is not supported on the respective system. For example, SEP sesam v. 4.4 does not work on Windows XP, therefore this client system will not be updated.
 
The <tt>sm_update_client</tt> executable is located in the {{Sesamroot|/bin/sesam/}}, for example <tt>c:\Program Files\SEPsesam\bin\sesam\</tt> on Windows. The <tt>sm_update_client</tt> command is aware of the operating system of the component that needs to be updated and does not perform an update if the available update package is not supported on the respective system. For example, SEP sesam v. 4.4 does not work on Windows XP, therefore this client system will not be updated.
  
=== Usage of <tt>sm_update_client</tt> ===
+
=== {{anchor|usage}}Usage of <tt>sm_update_client</tt> ===
The following options are available  
+
 
  Options:
+
The following options are available </translate>
     -U update clients
+
  <translate>Options:</translate>
     -c <client name>
+
     -U <translate>update clients</translate>
     -C <r|s> client <remote access|sbc connection> check
+
     -c <<translate>client name</translate>>
     -d download packages only
+
     -C <r|s> <translate>client <remote access|sbc connection> check</translate>
     -F force update by same version
+
     -d <translate>download packages only</translate>
     -L <location>
+
     -F <translate>force update by same version</translate>
     -N <regex> uses only packages matching <regex>
+
     -L <<translate>location</translate>>
     -n check available version (no update)
+
     -N <regex> <translate>uses only packages matching <regex></translate>
     -O <os> matches begin of operating system string
+
     -n <translate>check available version (no update)</translate>
     -u <URL> Use 'URL' instead of 'http://download.sep.de'
+
     -O <os> <translate>matches begin of operating system string</translate>
       file:///<local directory> can be used
+
     -u <URL> <translate>Use 'URL' instead of 'http://download.sep.de'</translate>
 +
       <translate>file:///<local directory> can be used</translate>
 
  <!-- previous version was:
 
  <!-- previous version was:
 
options:
 
options:
Line 67: Line 73:
 
       -u <URL> Use 'URL' instead of 'http://download.sep.de'-->   
 
       -u <URL> Use 'URL' instead of 'http://download.sep.de'-->   
  
<ol><li>To '''check''' which components (CLI/RDS/GUI) '''can be updated''', run the following command:</li>
+
<ol><li><translate>To '''check''' which components (CLI/RDS/GUI) '''can be updated''', run the following command:</translate></li>
  
 
  sm_update_client -n
 
  sm_update_client -n
  
First, the list of all available packages, found in the [http://download.sep.de/ SEP sesam download center], is displayed. Next, a list of your configured components and their currently installed SEP sesam packages is shown, followed by the available updates for the respective CLI/RDS/GUI.
+
<translate>First, the list of all available packages, found in the [http://download.sep.de/ SEP sesam download center], is displayed. Next, a list of your configured components and their currently installed SEP sesam packages is shown, followed by the available updates for the respective CLI/RDS/GUI.</translate>
 +
 
 +
<li><translate>Now you can decide whether you want to update '''all''' CLI/RDS/GUI components, which were listed as update candidates, or you only want to '''update a specific component'''.</translate></li>
 +
*<translate>To ''update all'' listed update candidates, run the following command:</translate>
  
<li>Now you can decide whether you want to update '''all''' CLI/RDS/GUI components, which were listed as update candidates, or you only want to '''update a specific component'''.</li>
 
*To ''update all'' listed update candidates, run the following command:
 
 
  sm_update_client -U
 
  sm_update_client -U
*If you want to update the CLI/RDS/GUI component with the same package as the currently existing one, use the -F switch:
+
*<translate>If you want to update the CLI/RDS/GUI component with the same package as the currently existing one, use the -F switch:</translate>
 +
 
 
  sm_update_client -U -F
 
  sm_update_client -U -F
*If you want to update ''only specific'' CLI/RDS/GUI, use the following command and replace the ''<client name>'' with the name of the target CLI/RDS/GUI component. The second line shows the example for updating a client named ''seagull''.
+
*<translate>If you want to update ''only specific'' CLI/RDS/GUI, use the following command and replace the ''<client name>'' with the name of the target CLI/RDS/GUI component. The second line shows the example for updating a client named ''seagull''.</translate>
 +
 
 
  sm_update_client -U -c <client name>
 
  sm_update_client -U -c <client name>
 
  sm_update_client -U -c seagull
 
  sm_update_client -U -c seagull
  
*''All clients in SEP sesam database'' can be checked and/or updated by using the '''ALL_CLIENTS''' syntax. To update all clients, run the following:
+
*<translate>''All clients in SEP sesam database'' can be checked and/or updated by using the '''ALL_CLIENTS''' syntax. To update all clients, run the following:</translate>
 +
 
 
  sm_update_client -U -c ALL_CLIENTS
 
  sm_update_client -U -c ALL_CLIENTS
  
*The parameter <tt>-O</tt> can be used to select specific clients' operating systems. For example, the following command will update all – and only – ''Windows Server 2008'' based systems (R2 included):
+
*<translate>The parameter <tt>-O</tt> can be used to select specific clients' operating systems. For example, the following command will update all – and only – ''Windows Server 2008'' based systems (R2 included):</translate>
 +
 
 
  sm_update_client -U -c ALL_CLIENTS -O "Windows Server 2008"
 
  sm_update_client -U -c ALL_CLIENTS -O "Windows Server 2008"
 
</ol>
 
</ol>
  
=={{anchor|local}}Updating by using local packages ==
+
<translate>=={{anchor|local}}Updating by using local packages ==
  
If you would like to update your clients with the packages which are stored at your SEP sesam Server and can be accessed locally, you have to use the <tt>sm_update_client</tt> and the <tt>index.txt</tt> file. You will have to generate the <tt>index.txt</tt> file locally to get the list of all available packages at your SEP sesam Server.<br>The latest <tt>index.txt</tt> file with all available packages at SEP sesam repository can be retrieved from the [http://download.sep.de/ SEP sesam download center].
+
If you would like to update your clients with the packages which are stored at your SEP sesam Server and can be accessed locally, you have to use the <tt>sm_update_client</tt> and the <tt>index.txt</tt> file. You will have to generate the <tt>index.txt</tt> file locally to get the list of all available packages at your SEP sesam Server.</translate><br /><translate>The latest <tt>index.txt</tt> file with all available packages at SEP sesam repository can be retrieved from the [http://download.sep.de/ SEP sesam download center].</translate>
  
<ol><li>To create the <tt>index.txt</tt> file, open the command prompt and navigate to your SEP sesam installation packages directory. Depending on your OS, run the following command :</li>
+
<ol><li><translate>To create the <tt>index.txt</tt> file, open the command prompt and navigate to your SEP sesam installation packages directory. Depending on your OS, run the following command:</translate></li>
  
 
'''Windows'''
 
'''Windows'''
Line 119: Line 130:
 
  windows\sesam-cli-4.2.2.24-windows.x64.exe 25522 2013-12-13 17:22:22
 
  windows\sesam-cli-4.2.2.24-windows.x64.exe 25522 2013-12-13 17:22:22
  
<li>Leave the <tt>index.txt</tt> file in the directory where it has been generated and pass its location and the location of the packages to <tt>sm_update_client</tt>. For example, if the packages are located in the {{Sesamroot|work/packages}} folder on your SEP sesam Server, the command would be:</li>
+
<li><translate>Leave the <tt>index.txt</tt> file in the directory where it has been generated and pass its location and the location of the packages to <tt>sm_update_client</tt>. For example, if the packages are located in the {{Sesamroot|work/packages}} folder on your SEP sesam Server, the command would be:</translate></li>
  
 
'''Windows'''
 
'''Windows'''
Line 127: Line 138:
  
 
<!-- ? If you want to install a specific package, use the parameter -P to insert the package name.-->
 
<!-- ? If you want to install a specific package, use the parameter -P to insert the package name.-->
The automatic update of the SEP sesam Server is currently not supported.
+
<translate>The automatic update of the SEP sesam Server is currently not supported.</translate>
  
  Usage: sm_config_client
+
  <translate>Usage:</translate> sm_config_client
         -i timestamp = identifier of this call
+
         -i timestamp = <translate>identifier of this call</translate>
         -c client name
+
         -c <translate>client name</translate>
         -o operating system
+
         -o <translate>operating system</translate>
 
       [-l location_id] default=0
 
       [-l location_id] default=0
       [-a addr] ( TCPIP-adr. or 'via_nameserver' = default
+
       [-a addr] ( TCPIP-adr. or 'via_nameserver' = <translate>default</translate>
       [-m mode] ( CTRL(=default)|RSH|SSH ) configures client
+
       [-m mode] ( CTRL(=default)|RSH|SSH ) <translate>configures client</translate>
                 ( delete )                deletes client
+
                 ( delete )                <translate>deletes client</translate>
                 ( testsbc|testbackup )    tests connection to/from client
+
                 ( testsbc|testbackup )    <translate>tests connection to/from client</translate>
       [-O options
+
       [-O <translate>options</translate>
       [-s sender of this call]  default = sesam
+
       [-s <translate>sender of this call]  default = sesam</translate>
         -U update client package
+
         -U <translate>update client package</translate>
       [-P <package name> path name of package
+
       [-P <translate><package name> path name of package</translate>
+
  <translate>Example:</translate>
Example:
 
 
       sm_config_client -c kha-testius64 -U -O force
 
       sm_config_client -c kha-testius64 -U -O force
  
The last parameter <tt>-O force</tt> will push the installation even if the installed version is the same as the version of the update package. Note that the client name is case-sensitive, therefore make sure that it is inserted correctly if you want the update to work.</ol>
+
<translate>The last parameter <tt>-O force</tt> will push the installation even if the installed version is the same as the version of the update package. Note that the client name is case-sensitive, therefore make sure that it is inserted correctly if you want the update to work.</translate></ol>
 +
 
 +
<translate>== {{anchor|check}}Checking the updates ==
 +
 
 +
To check if the update was successful, proceed as follows:</translate>
 +
<ol><li><translate>Check the connection between a GUI client and SEP sesam Server. The connection should work.</translate></li>
 +
<li><translate>Open the SEP sesam GUI and from the menu bar select '''Help''' -> '''About SEP sesam'''. Both, SEP sesam GUI client and SEP sesam GUI Server must have the same build versions.</translate></li>
  
== Checking the updates ==
+
<translate>[[Image:About_SEP_sesam.png|600px|link=]]</translate>
To check if the update was successful, proceed as follows:
 
<ol><li>Check the connection between a GUI client and SEP sesam Server. The connection should work.</li>
 
<li>Open the SEP sesam GUI and from the menu bar select '''Help''' -> '''About SEP sesam'''. Both, SEP sesam GUI client and SEP sesam GUI Server must have the same build versions.</li>
 
[[Image:About_SEP_sesam.png|600px|left|link=]]
 
 
<br clear=all>
 
<br clear=all>
 
</ol></onlyinclude>
 
</ol></onlyinclude>
  
==See also==
+
<translate>==See also==
[[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Applying Service Packs on Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]]
+
[[Special:MyLanguage/Updating_SEP_sesam|Updating SEP sesam]] – [[Special:MyLanguage/Automatic_Installation_On_Windows|Automatic Installation on Windows]] – [[Special:MyLanguage/Applying_Service_Packs_on_Linux|Applying Service Packs on Linux]] – [[Special:MyLanguage/4_4_3:SEP_sesam_Quick_Install_Guide|SEP sesam Quick Install Guide]] – [[Special:MyLanguage/SEP_Sesam_CLI|SEP sesam CLI]]</translate>

Revision as of 18:20, 13 December 2017

Other languages:
Deutsch • ‎English

Copyright © SEP AG 1999-2019. All rights reserved.

Any form of reproduction of the contents or parts of this manual is allowed only with the express written permission from SEP AG. When compiling and designing user documentation SEP AG uses great diligence and attempts to deliver accurate and correct information. However, SEP AG cannot issue a guarantee for the contents of this manual.


Docs latest icon.png Welcome to the latest SEP sesam documentation version 4.4.3. For previous documentation version(s), check Documentation archive.


Overview

SEP sesam provides free updates from previous versions of SEP sesam to new versions and new features within the maintenance period. You can enable a SEP sesam Server to check for the relevant updates and remotely update your clients by using the CLI command sm_update_client.

Using sm_update_client for automatic updates

The sm_update_client command is used to automatically update all clients, RDS, and GUI (including a client). The sm_update_client command uses SEP sesam download center to check for new installation packages available for the configured clients.

The following applies for updating components:

  • On Linux, a specific component is always required for an update: a client can be updated using a SEP sesam Client package, updating GUI requires a GUI package, and RDS requires an RDS package.
  • On Windows, a client can be updated with any of the three installation packages, updating GUI can be done with either the GUI or SEP sesam Server package, and RDS requires a server package.

The sm_update_client executable is located in the <SESAM_ROOT>/bin/sesam/, for example c:\Program Files\SEPsesam\bin\sesam\ on Windows. The sm_update_client command is aware of the operating system of the component that needs to be updated and does not perform an update if the available update package is not supported on the respective system. For example, SEP sesam v. 4.4 does not work on Windows XP, therefore this client system will not be updated.

Usage of sm_update_client

The following options are available

Options:
   -U update clients
   -c <client name>
   -C <r|s> client <remote access|sbc connection> check
   -d download packages only
   -F force update by same version
   -L <location>
   -N <regex> uses only packages matching <regex>
   -n check available version (no update)
   -O <os> matches begin of operating system string
   -u <URL> Use 'URL' instead of 'http://download.sep.de'
      file:///<local directory> can be used
  1. To check which components (CLI/RDS/GUI) can be updated, run the following command:
  2. sm_update_client -n
    

    First, the list of all available packages, found in the SEP sesam download center, is displayed. Next, a list of your configured components and their currently installed SEP sesam packages is shown, followed by the available updates for the respective CLI/RDS/GUI.

  3. Now you can decide whether you want to update all CLI/RDS/GUI components, which were listed as update candidates, or you only want to update a specific component.
    • To update all listed update candidates, run the following command:
    sm_update_client -U
    
    • If you want to update the CLI/RDS/GUI component with the same package as the currently existing one, use the -F switch:
    sm_update_client -U -F
    
    • If you want to update only specific CLI/RDS/GUI, use the following command and replace the <client name> with the name of the target CLI/RDS/GUI component. The second line shows the example for updating a client named seagull.
    sm_update_client -U -c <client name>
    sm_update_client -U -c seagull
    
    • All clients in SEP sesam database can be checked and/or updated by using the ALL_CLIENTS syntax. To update all clients, run the following:
    sm_update_client -U -c ALL_CLIENTS
    
    • The parameter -O can be used to select specific clients' operating systems. For example, the following command will update all – and only – Windows Server 2008 based systems (R2 included):
    sm_update_client -U -c ALL_CLIENTS -O "Windows Server 2008"
    

Updating by using local packages

If you would like to update your clients with the packages which are stored at your SEP sesam Server and can be accessed locally, you have to use the sm_update_client and the index.txt file. You will have to generate the index.txt file locally to get the list of all available packages at your SEP sesam Server.
The latest index.txt file with all available packages at SEP sesam repository can be retrieved from the SEP sesam download center.

  1. To create the index.txt file, open the command prompt and navigate to your SEP sesam installation packages directory. Depending on your OS, run the following command:
  2. Windows

    cd C:\ProgramData\SEPsesam\var\work\packages
    dir /B >index.txt
    

    Linux/UNIX

    cd /var/opt/sesam/var/work/packages
    find . -name "*sesam*" -printf "%P %k %TY-%Tm-%Td %TH:%TM:%TM \n" >index.txt
    

    The following example shows the index.txt file where all Linux packages are in the Linux folder and all Windows packages are in the Windows folder.

    linux\sesam_gui-4.2.2-24.sles10.i586.rpm 65420 2013-12-13 16:26:26
    linux\sesam_rts-4.2.2-24.sles10.i586.rpm 23066 2013-12-13 16:26:26
    linux\sesam_cli-4.2.2-24.sles11.x86_64.rpm 16068 2013-12-13 16:22:22
    linux\sesam_gui-4.2.2-24.sles10.x86_64.rpm 66087 2013-12-13 16:23:23
    linux\sesam-srv_4.2.2-24.wheezy_i386.deb 90512 2013-12-13 16:20:20
    linux\sesam_cli-4.2.2-24.rhel6.x86_64.rpm 18350 2013-12-13 16:16:16
    linux\sesam_rts-4.2.2-24.rhel6.x86_64.rpm 60703 2013-12-13 16:16:16
    linux\sesam_rts-4.2.2-24.rhel5.x86_64.rpm 59335 2013-12-13 16:17:17
    windows\sesam-srv-4.2.2.24-windows.x86.exe 110739 2013-12-13 17:16:16
    windows\sesam-gui-4.2.2.24-windows.x86.exe 85511 2013-12-13 17:20:20
    windows\sesam-cli-4.2.2.24-windows.x86.exe 24803 2013-12-13 17:24:24
    windows\sesam-srv-4.2.2.24-windows.x64.exe 112918 2013-12-13 17:15:15
    windows\sesam-gui-4.2.2.24-windows.x64.exe 86261 2013-12-13 17:19:19
    windows\sesam-cli-4.2.2.24-windows.x64.exe 25522 2013-12-13 17:22:22
    
  3. Leave the index.txt file in the directory where it has been generated and pass its location and the location of the packages to sm_update_client. For example, if the packages are located in the <SESAM_ROOT>work/packages folder on your SEP sesam Server, the command would be:
  4. Windows

    sm_update_client -U -c clientname -u "file:///C:\ProgramData\SEPsesam\var\work\packages"
    

    Linux/UNIX

    sm_update_client -U -c clientname -u "file:///var/opt/sesam/var/work/packages"
    

    The automatic update of the SEP sesam Server is currently not supported.

    Usage: sm_config_client
           -i timestamp = identifier of this call
           -c client name
           -o operating system
          [-l location_id] default=0
          [-a addr] ( TCPIP-adr. or 'via_nameserver' = default
          [-m mode] ( CTRL(=default)|RSH|SSH ) configures client
                    ( delete )                 deletes client
                    ( testsbc|testbackup )     tests connection to/from client
          [-O options
          [-s sender of this call]  default = sesam
           -U update client package
          [-P <package name> path name of package
     Example:
          sm_config_client -c kha-testius64 -U -O force
    
    The last parameter -O force will push the installation even if the installed version is the same as the version of the update package. Note that the client name is case-sensitive, therefore make sure that it is inserted correctly if you want the update to work.

Checking the updates

To check if the update was successful, proceed as follows:

  1. Check the connection between a GUI client and SEP sesam Server. The connection should work.
  2. Open the SEP sesam GUI and from the menu bar select Help -> About SEP sesam. Both, SEP sesam GUI client and SEP sesam GUI Server must have the same build versions.
  3. About SEP sesam.png

See also

Updating SEP sesamAutomatic Installation on WindowsApplying Service Packs on LinuxSEP sesam Quick Install GuideSEP sesam CLI