Вопросы обновления или модернизации Портала возникают каждый раз, когда появляются очередные "заплатки" (patch) или новые версии. Риски связанные с этой операцией сведены к минимуму, но всё же они присутствуют и могут стать причиной "головной боли" для администратора, чтобы этого избежать необходимо ясно представлять всю картину и последовательность действий, которые необходимо соблюдать для получения успешных результатов. Обновление версий Kablink4, требует подготовительных действий т.к усложнилась архитектура и поменялась jdk, при этом остались неизменны основные действия которые требуются выполнить:

  • обновить операционную систему
  • проверить наличие резервной копии см.резервирование
  • скачать новую версию и распаковать
  • копировать файл сценария установок installer.xml
  • обновить jdk (необязательно)
  • сохранить пользовательские формы и представления
  • сохранить пользовательские шаблоны
  • сохранить шаблоны областей и папок
  • сохранить глобальные формы и определения
  • останавливать Kablink
  • обновить программные папки kablink
  • обновить и перестроить схему БД kablink
  • проверить временную зону jdk
  • выполнить старт kablink
  • запустить проверку индексации kablink
  • выполнить сброс глобальных форм и определений
  • выполнить сброс шаблонов областей и папок
  • проверить пользовательские формы
  • проверить пользовательские шаблоны
  • проверить наличие "старого" сертификата

Первое, что надо сделать это убедится в наличие резервной копии, проверить её сохранность и целостность. Скачать новую версию Kablink, проветрить контрольную сумму и распаковать в каталог, в примере указан путь к условному каталогу на стенде. Сохранить файл installer.xml , переписав его из каталога предыдущей установки, чтобы не вводить параметры конфигурации Kablink заново.

home]# md5sum kablink-vibe-4.0.1-linux.tar
md5: 59095748155ca853da96db09f496994f
home]# mkdir /home/kablink-4.0.1-linux
home]# tar xvf /home/kablink-4.0.1-linux.tar -C /home/kablink-4.0.1-linux
# cp /home/kablink-4.0.0-linux/installer.xml /home/kablink-4.0.1-linux
# /etc/init.d/teaming stop
$ rpm -qa|grep jdk
jdk1.8-1.8.0_181-fcs.x86_64

Сохранить локальные формы и определения, локальные шаблоны, это те формы и шаблоны, которые могут создавать(настраивать) сами пользователи, если прошли обучение, хранящиеся непосредственно в тех областях к которым они имеют права доступа, т.е их личные области. Администратору следует установить политику хранилищ для создаваемых пользователями шаблонов, форм и представлений, это предотвратит их "разбрасывание" по папкам Портала, где будет трудно их контролировать и обслуживать. Совет: сразу устанавливайте политику управления записями пользователей - предотвратит их бесконтрольное распространение. Добраться до локальных форм и определений можно по "шестерёнке" любой доступной папки, далее остаётся выполнить несколько кликов после чего шаблоны с формами и определениями будут сохранены на вашем ПК. Эти же действия необходимо выполнить для сохранения локальных шаблонов опытных пользователей.

Теперь надо сохранить шаблоны рабочих областей и папок, здесь могут оказаться шаблоны созданные администратором или членами группы администраторов, распространяемые на все рабочие области Портала.

Последнее, что надо сохранить, это  глобальные формы и определения, шаблоны хранят не только основные формы папок, рабочих областей, процессов и профилей пользователей но шаблоны созданные администратором или группой администраторов и распространяемые как глобальные т.е доступные всем пользователям Портала

остановить kablink

# /etc/init.d/teaming stop

обновить программные папки kablink, можно выбрать два варианта, третий с GUI не рассматривается, "безмолвный", один раз запускаем на все вопросы "отвечает" файл installer.xml 

# cd /home/kablink-4.0.1-linux
# ./installer-teaming.linux --silent --upgrade

# ./installer-teaming.linux --silent --upgrade
::softwareVersion
Data fsroot directory /var/opt/novell/teaming
Data fsroot directory /var/opt/novell/teaming
Removing obsolete Conferencing presence settings from installer.xml.
Starting installation...
Installation mode: 2   ... /home/kablink-vibe-4.0.1-linux/temp-installer/db
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/apache-tomcat
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/kablink-teaming-4.0.1-standalone.zip
JAVA_HOME is set to: /usr/java/jdk1.8.0_181-amd64
JRE_HOME is set to: /usr/java/jdk1.8.0_181-amd64/jre
        Backing up installDirectory is /opt/novell/teaming and root directory is apache-tomcat
        Backing up previous settings and webapps to /opt/novell/teaming/teaming-backup
        Backing up /opt/novell/teaming/apache-tomcat/bin
        Backing up /opt/novell/teaming/apache-tomcat/conf
        Backing up /opt/novell/teaming/apache-tomcat/lib
        Backing up webapps/ROOT
        Backing up webapps/mobile
        Backing up webapps/ssf
        Backing up webapps/ROOT
        Backing up webapps/ssr
        Backing up webapps/rest
Copying deployment kits to work directory...Installing into /opt/novell/teaming
Installing Kablink Vibe ...
--> Saving file owner and permissions for vibe.jmxremote.access, vibe.jmxremote.password and vibe.management.properties
Backing up /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Backing up /opt/novell/teaming/apache-tomcat/lib/custom-ext
Laying down files for StandAlone tomcat
copying the mobile webapp into /opt/novell/teaming/apache-tomcat/webapps/mobile into /opt/novell/teaming/apache-tomcat/webapps
copying the ssf webapp into /opt/novell/teaming/apache-tomcat/webapps/ssf
copying the ROOT webapp into /opt/novell/teaming/apache-tomcat/webapps/ROOT
copying the ssr webapp into /opt/novell/teaming/apache-tomcat/webapps/ssr
copying the rest webapp into /opt/novell/teaming/apache-tomcat/webapps/rest
copying the novl webapp into /opt/novell/teaming/apache-tomcat/webapps/novl
Remove Tomcat Work Dir
Laying down files for StandAlone tomcat
copying the bin dir into /opt/novell/teaming/apache-tomcat/bin into /opt/novell/teaming/apache-tomcat
copying the conf dir into /opt/novell/teaming/apache-tomcat/conf
copying the lib dir into /opt/novell/teaming/apache-tomcat/lib
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_servlet_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_bottom.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_css_init.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_middle.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_top.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_find_search_results.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_mobile_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring /opt/novell/teaming/teaming-backup/conf/.keystoreCompleted Software install successfully
Check to see if need to removeLifeRay configurationApplying installation settings...   Loading current configuration files...
   Default locale...
   Database settings...
      using database configuration: Installed
      Database type is: MySql
   Request and Connection settings:
      maxThreads:  200
      maxActive:  50
      maxIdle:  20
      schedulerThreads:  20
      maxRestRequests:  50
   File system settings...
      using configuration: basic
   File system root path: /var/opt/novell/teaming
   Email settings...
   Email notification timezone setting...
   Internal SMTP server email settings...
   Network settings...
   Lucene...
   WebDAV authentication settings...
      using WebDAV authentication method:  digest
   Disabling Reverse Proxy SSO...
   Fixing security files for SSO configuration.  Reverse Proxy SSO enabled state is now:  false
   Disabling IIS for Windows Authentication SSO...
   Fixing security files for SSO configuration.  IIS for Windows Authentication SSO enabled state is now:  false
   Fixing security files for WebDAV 'digest authentication'.
--> Removing memcached elements
   Custom settings...
   Startup files...
   Assuming Oracle JDK
Removing obsolete Conferencing presence settings from ssf-ext.properties.
Setting cluster wide encryption key...
   loading existing sec.properties file...
   using existing encryption.key from sec.properties...
   Writing all settings...
     Saved copy of installer.xml in /opt/novell/teaming/install-config
   Setting software file ownerships to: root ...
   Setting software file protections to: 750 (no access outside of group) ...
   Setting file permissions to 600 on vibe.jmxremote.password file (only the owner can read and write this file)
   Restoring file ownership for vibe.jmxremote.access
   Restoring file permissions for vibe.jmxremote.access
   Restoring file ownership for vibe.jmxremote.password
   Restoring file permissions for vibe.jmxremote.password
   Restoring file ownership for vibe.management.properties
   Restoring file ownership for vibe.management.properties
   Copied startup file /opt/novell/teaming/apache-tomcat/bin/teaming to /etc/init.d
Novell Messenger Presence integration disabled.
Analyzing self-signed 'tomcat' certificate status...
...checking for existance of a valid 'tomcat' certificate...
......existing 'tomcat' certificate exists and will not be overwritten...
Self-signed 'tomcat' certificate analysis complete.End: Apply SettingsSettings successfully applied.   Clearing JSP caches...Getting database creation scripts....
Installation completed.You can start Kablink Vibe by running the startup script:
  /opt/novell/teaming/apache-tomcat/bin/teaming start
#

или сценарий  с развёрнутыми вопросами и ответами из файла installer.xml, здесь можно внести необходимые исправления или просто проконтролировать процесс

# ./installer-teaming.linux
::softwareVersionInstalling this software requires agreement to the
terms and conditions set forth in the:
  Kablink LicenseYou can review this agreement again at the download site or
type "REVIEW" below.

Note: You must answer "YES" to install the software.

Have you read and agree with the license? : Yes

Kablink Vibe Installer 4.0.1
Select the action you want to perform
1. New installation
2. Update software and settings
3. Reconfigure settings
Selection?  [3]: 2
Your Vibe server must be shutdown to perform this operation.
Is your Vibe server shutdown [Y]:

Where is Kablink Vibe installed? (top-level directory)
Install directory: [/opt/novell/teaming]:
   Directory /opt/novell/teaming exists
   Directory /opt/novell/teaming is not empty
Select the type of installation you want to perform
1. Basic installation (select this if you do not have to configure any of the optional features)
2. Advanced installation (select this if you need to configure any of the optional features)
Selection?  [1]:
File system location [/var/opt/novell/teaming]:
Default locale
...
323. Europe/Moscow
...
Selection?  [323]:
Please enter the userid or userid:group under which to run Kablink Vibe:  [root]:
Network information
These settings control the way that Kablink Vibe appears on the networkHostname [kablink.dd]:

HTTP port [8081]:
Secure HTTP port [8443]:
Listen port (if different from Port) [8081]:
Secure listen port (if different from Secure port) [8443]:
Shutdown port [8005]:
AJP port [8009]:
Session timeout [240]:
Keystore file:
(Optional) Forward Proxy
ServerProxy server hostname:
Proxy server port [80]:
WebDAV Authentication Method
Select the authentication method to use for WebDAV access.
Two forms of WebDAV authentication are supported, basic and digest.  The choice of which one to select must take the following into consideration:

1) Windows 7 users may not be able to use WebDAV features if basic authentication is selected and the users access Vibe over HTTP;
2) Basic Authentication is recommended if Vibe server is set up to force HTTPS; and
3) Digest authentication will require user passwords to be stored using symmetric encryption.

WebDAV authentication method?
1. basic
2. digest
Selection?  [2]: Database selection

It is recommended that your database software be installed and running,
before proceeding

Which database are you using?
1. MySql
2. SQLServer
3. Oracle
Selection?  [1]:

Username for Vibe database [root]:
Password for Vibe database [kablink]:
JDBC URL for Vibe database [jdbc:mysql://localhost:3306/sitescape?useUnicode=true&characterEncoding=UTF-8]: *** Note ***
After the upgrade has finished, you will need to run the database upgrade scripts by hand.
Please refer to the installation guide for details.
**********
Enter Y to continue, enter N to cancel installation [Y]:
   Checking database settings...
   Database type is: MySql
   Checking MySql version and access for Kablink Vibe
--------------
mysql  Ver 14.14 Distrib 5.7.28, for Linux (x86_64) using  EditLine wrapper
Connection id:          12
Current database:
Current user:           root@localhost
SSL:                    Not in use
Current pager:          stdout
Using outfile:          ''
Using delimiter:        ;
Server version:         5.7.28-alt1 (ALT p8)
Protocol version:       10
Connection:             Localhost via UNIX socket
Server characterset:    utf8
Db     characterset:    utf8
Client characterset:    utf8
Conn.  characterset:    utf8
UNIX socket:            /var/lib/mysql/mysql.sock
Uptime:                 12 hours 16 min 19 sec
Threads: 1  Questions: 98073  Slow queries: 0  Opens: 18921  Flush tables: 1  Open tables: 29  Queries per second avg: 2.219
--------------
mysql: [Warning] unknown variable 'loose-chroot=/var/lib/mysql'
mysql: [Warning] Using a password on the command line interface can be insecure.
  NOTE: Minimum database requirement is 5.0.26
  We see Server version: 5.7.28
Please review above notes.
Enter Y to continue, enter N to cancel installation [Y]:
A Java JDK of version 1.7.0 or higher is required to run Kablink Vibe.
Path to JDK version 1.7.0 or higher [/usr/java/jdk1.8.0_181-amd64]:
JVM heap size to use [1g]:

The Java Cryptography Extension must be installed for Vibe to work. Please verify that this has been installed.
Outbound e-mail settings

There are features of Kablink Vibe that require an outbound e-mail server be configured.
Email protocol for outbound messages

1. smtp
2. smtps
Selection?  [1]:
Email host [kablink.dd]:
Port [25]:
Connection timeout [15000]:
Default time zone for outbound messages
..
323. Europe/Moscow
..
Selection?  [323]:
Username [Этот адрес электронной почты защищен от спам-ботов. Для просмотра адреса в вашем браузере должен быть включен Javascript.]:
Password:
Is authentication required to send? [No]:
Allow sending e-mail to all users? [No]:
Force HTTPS links in e-mails? [No]:
Enable STARTTLS? [No]:
From e-mail addresss override:
Use this from e-mail address for all outbound e-mail? [No]: Internal SMTP server e-mail settingsEnable internal SMTP e-mail server? [No]:
Data fsroot directory /var/opt/novell/teaming
Data fsroot directory /var/opt/novell/teaming
Removing obsolete Conferencing presence settings from installer.xml.Configuration saved in installer.xml.
Perform upgrade now? [Yes]:
Starting installation...
Installation mode: 2   ... /home/kablink-vibe-4.0.1-linux/temp-installer/db
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/apache-tomcat
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext
   ... /home/kablink-vibe-4.0.1-linux/temp-installer/kablink-teaming-4.0.1-standalone.zip
JAVA_HOME is set to: /usr/java/jdk1.8.0_181-amd64
JRE_HOME is set to: /usr/java/jdk1.8.0_181-amd64/jre
        Backing up installDirectory is /opt/novell/teaming and root directory is apache-tomcat
        Backing up previous settings and webapps to /opt/novell/teaming/teaming-backup
        Backing up /opt/novell/teaming/apache-tomcat/bin
        Backing up /opt/novell/teaming/apache-tomcat/conf
        Backing up /opt/novell/teaming/apache-tomcat/lib
        Backing up webapps/ROOT
        Backing up webapps/mobile
        Backing up webapps/ssf
        Backing up webapps/ROOT
        Backing up webapps/ssr
        Backing up webapps/rest
Copying deployment kits to work directory...Installing into /opt/novell/teaming
Installing Kablink Vibe ...
--> Saving file owner and permissions for vibe.jmxremote.access, vibe.jmxremote.password and vibe.management.properties
Backing up /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Backing up /opt/novell/teaming/apache-tomcat/lib/custom-ext
Laying down files for StandAlone tomcat
copying the mobile webapp into /opt/novell/teaming/apache-tomcat/webapps/mobile into /opt/novell/teaming/apache-tomcat/webapps
copying the ssf webapp into /opt/novell/teaming/apache-tomcat/webapps/ssf
copying the ROOT webapp into /opt/novell/teaming/apache-tomcat/webapps/ROOT
copying the ssr webapp into /opt/novell/teaming/apache-tomcat/webapps/ssr
copying the rest webapp into /opt/novell/teaming/apache-tomcat/webapps/rest
copying the novl webapp into /opt/novell/teaming/apache-tomcat/webapps/novl
Remove Tomcat Work Dir
Laying down files for StandAlone tomcat
copying the bin dir into /opt/novell/teaming/apache-tomcat/bin into /opt/novell/teaming/apache-tomcat
copying the conf dir into /opt/novell/teaming/apache-tomcat/conf
copying the lib dir into /opt/novell/teaming/apache-tomcat/lib
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_servlet_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_bottom.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_css_init.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_middle.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_sidebar_top.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_find_search_results.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring custom jsp /home/kablink-vibe-4.0.1-linux/temp-installer/backup-ext/custom_jsps/ss_call_out_mobile_head.jsp to /opt/novell/teaming/apache-tomcat/webapps/ssf/WEB-INF/jsp/custom_jsps
Restoring /opt/novell/teaming/teaming-backup/conf/.keystoreCompleted Software install successfully
Check to see if need to removeLifeRay configurationApplying installation settings...   Loading current configuration files...
   Default locale...
   Database settings...
      using database configuration: Installed
      Database type is: MySql
   Request and Connection settings:
      maxThreads:  200
      maxActive:  50
      maxIdle:  20
      schedulerThreads:  20
      maxRestRequests:  50
   File system settings...
      using configuration: basic
   File system root path: /var/opt/novell/teaming
   Email settings...
   Email notification timezone setting...
   Internal SMTP server email settings...
   Network settings...
   Lucene...
   WebDAV authentication settings...
      using WebDAV authentication method:  digest
   Disabling Reverse Proxy SSO...
   Fixing security files for SSO configuration.  Reverse Proxy SSO enabled state is now:  false
   Disabling IIS for Windows Authentication SSO...
   Fixing security files for SSO configuration.  IIS for Windows Authentication SSO enabled state is now:  false
   Fixing security files for WebDAV 'digest authentication'.
--> Removing memcached elements
   Custom settings...
   Startup files...
   Assuming Oracle JDK
Removing obsolete Conferencing presence settings from ssf-ext.properties.
Setting cluster wide encryption key...
   loading existing sec.properties file...
   using existing encryption.key from sec.properties...
   Writing all settings...
     Saved copy of installer.xml in /opt/novell/teaming/install-config
   Setting software file ownerships to: root ...
   Setting software file protections to: 750 (no access outside of group) ...
   Setting file permissions to 600 on vibe.jmxremote.password file (only the owner can read and write this file)
   Restoring file ownership for vibe.jmxremote.access
   Restoring file permissions for vibe.jmxremote.access
   Restoring file ownership for vibe.jmxremote.password
   Restoring file permissions for vibe.jmxremote.password
   Restoring file ownership for vibe.management.properties
   Restoring file ownership for vibe.management.properties
   Copied startup file /opt/novell/teaming/apache-tomcat/bin/teaming to /etc/init.d
Novell Messenger Presence integration disabled.
Analyzing self-signed 'tomcat' certificate status...
...checking for existance of a valid 'tomcat' certificate...
......existing 'tomcat' certificate exists and will not be overwritten...
Self-signed 'tomcat' certificate analysis complete.

End: Apply SettingsSettings successfully applied.
  
Clearing JSP caches...

Getting database creation scripts....

Installation completed.
You can start Kablink Vibe by running the startup script:
  /opt/novell/teaming/apache-tomcat/bin/teaming start

Обновление базы данных.

редактирование шаблона

cd /home/kablink-4.0.1-linux]# unzip teaming-4.0.1-db.zip           
# chmod -R 744 db
# cd db
db] # vim mysql-liquibase.properties
  driver: com.mysql.jdbc.Driver
  url:
  jdbc:mysql://localhost:3306/sitescape?useUnicode=true&characterEncoding=UTF-8
  username : root
  password : kablink

проверка кодировки

db]# mysql -uroot -pkablink
mysql> use sitescape;
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -ADatabase changed
mysql> SHOW VARIABLES LIKE "character_set_database";
+------------------------+-------+
| Variable_name          | Value |
+------------------------+-------+
| character_set_database | utf8  |
+------------------------+-------+
1 row in set (0,00 sec)
mysql> quit

перестраиваем схему базы данных Kablink

db] # ./manage-database.sh mysql updateDatabase  
INFO :liquibase: Successfully acquired change log lock
INFO :liquibase: Reading from `DATABASECHANGELOG`
INFO :liquibase: Reading from DATABASECHANGELOG
...
WARNING :liquibase: modifyDataType will lose primary key/autoincrement/not null settings for mysql.  Use and re-specify all configuration if this is the case
...
INFO :liquibase: ChangeSet scripts/changelog/mysql-changelog-quartz-1.8-to-2.2.xml::1-1::jong ran successfully in 9ms
INFO :liquibase: ChangeSet scripts/changelog/mysql-changelog-quartz-1.8-to-2.2.xml::1-2::jong ran successfully in 4ms
INFO :liquibase: ChangeSet scripts/changelog/mysql-changelog-quartz-1.8-to-2.2.xml::2-1::jong ran successfully in 36ms
...
INFO :liquibase: Marking ChangeSet: scripts/changelog/mysql-changelog-quartz-1.8-to-2.2.xml::5-7::jong::(Checksum: 3:a50e6cfc290ccee54f760206347e5036) ran despite precondition failure due to onFail='MARK_RAN':
          scripts/changelog/mysql-changelog-master.xml : Index FK_SSQRTZ_CRON_TRIGGERS_SSQRTZ_TRIGGERS does not exist
...
INFO :liquibase: ChangeSet scripts/changelog/mysql-changelog-quartz-1.8-to-2.2.xml::11-1::jong ran successfully in 42ms
INFO :liquibase: Successfully released change log lock
Liquibase Update Successful

 проверяем временную зону Tomcat

# /opt/novell/teaming/apache-tomcat/bin/catalina.sh
JAVA_OPTS=....-Duser.timezone=GMT ...-Duser.timezone=Europe/Moscow

 выполнить старт kablink, контролировать процессы загрузки

# /etc/init.d/teaming stop
# tail -f /opt/novell/teaming/apache-tomcat/logs/appserver.log

запустить проверку индексации kablink, может занять некоторое время

выполнить сброс глобальных форм и определений, проверить наличие и восстановление настраиваемых форм

выполнить сброс шаблонов областей и папок, проверить наличие и восстановление настраиваемых шаблонов

проверить пользовательские формы, если были созданы, при необходимости восстановить

проверить пользовательские шаблоны, если были созданы, при необходимости восстановить

Теперь рассмотрим другой тип обновления, который касается небольших исправлений, "заплаток", относящихся в основном к контейнеру apache-tomcat. Сам файл с обновлением выглядит примерно так, vibe-4.x.x-PX-xxxxxxxx.zip, где 'x' это цифровая номенклатура присвоенная файлу исправлений. Познакомится подробно с самим списком включенных обновлений можно прочитав страничку readme.txt внутри zip архива. Прежде чем произвести обновление сделаем небольшие подготовительные мероприятия, а именно резервную копию каталога apache-tomcat, так на всякий случай, хотя сценарий отрабатывающий установку заплатки и создаёт свой резервный архив.

# tar czfv apach_tom.tar /opt/novell/teaming    //резервная копия apache-tomcat

# vibe-4.x.x-PX-xxxxxxxx.zip //распаковываем архив заплатки
unzip vibe-4.x.x-PX-xxxxxxxx.zip

# /etc/init.d/teaming stop

# cd vibe-4.x.x-PX-xxxxxxxx
tclsh vibe-ftf-installer.tcl
Is Vibe shut down? [N]:Y
--------
# /etc/init.d/teaming start